ePROJECT National Level Paper Presentation FPT APTECH

Project Name: National Level Paper Presentation RAR file contains: Database (folder): contains database file and sql srcipt file. Documentation (folder): contains documents for developer, Setup guide. Sources (folder): contains the source code. Program (folder): contains the data for setup and run app. Supports (folder): contains the JBoss and Tomcat server. Status_Report file Feedback file.

Ho Chi Minh City, 01/2013

This is to certify that

1 LE THANH BINH Student635001

2 VUONG QUOC HUNG Student557205

3 LE TUAN AN Student556489

4 NGUYEN TAT THIEN Student556203

5 TRAN NHUT QUANG Student522237

Has successfully Designed and Developed.

National Level Paper Presentation

TABLE OF CONTENTS

National Level Paper Presentation 1

National Level Paper Presentation 2

REVIEW 1 3

CHECKLISTS 83

REVIEW 1

Acknowledgements and Customer Requirement

Specification

Although, there have been many attempted but by the time the limited practice shouldnot be able to avoid the mistakes and omissions Hope is the understanding of eProject Team

at the Head Office And finally, we would like to offer many thanks to all my friends for theirvaluable suggestions and constructive feedback

KSC Technology and Sciences is the educational university which runs the classes forthe categories like Engineering, Pharmaceutical sciences, Literature, etc It is one of thefamous universities in the country They generally conduct Paper Presentations at state leveland national level They also conduct seminars, Techno-Feat, etc so as to entertain thestudents in the technical back grounds

Each time when they conduct seminars, symposiums, or paper presentation, etc theyused to send the invitations for the participation of the students of other colleges, etc so thatthe knowledge of the student can be enhanced and at the same time, the students who doesnot belong to this university can also have the opportunity in participating in these activities.While sending the invitations to the other colleges, universities, they quote someregistration fees for the gate pass and also they will provide the details like the topics forwhich seminars or paper presentations or symposiums or techno-feats are conducted For theseminars and the Techno-feats they also provide the names of the speakers who areconducting or providing this Along with the invitation they also send the format ofapplication, which is to be filled and sent back to the address as mentioned in the invitationfor participating in the activities

In general to participate in these activities, the students who do not belong to thisuniversity send their requests by filling in the application form as per the format sent and

send it along with the payment through courier or directly dropping it at the address inpersonal In case of the Paper presentations, along with the courier, they also used to submitboth the soft copy and the hard copy, so that they can reach the mentioned address beforethe end date of the participation After sending these copies, they used to verify and thenfinalize which students are to be participated in this paper presentation The selection ispurely based on the technology (like mostly they prefer the new implementations in thetechnology, etc.).

Now they want to provide a facility where the participants can register themselvesonline and as well the invitation can be displayed directly online itself in the specific portal.Once they are registered online they can send the details of the payment along with the printout of the application along with the signature of the participant and for the paperpresentation, the hard copy of the paper presentation will be sent along with it So they haveapproached us in order to help them

They want that the following steps to be incorporated in the website

1. There should be a logo indicating the brand of the institute on all the web pages.(Note: the logo can be of any institution or it can be designed by your own as well)

2. On the home page of the website the details of the upcoming activities, and thewinners of the recent activity conducted is to be displayed Also the details of theparticipants like how many are registered for the recent or for the latest activity conductedcan be displayed on the home page

3. The user can also create the account with the website, with his/her personal mail

id So that if any activity is going to be launched a mail will be marked to the mail id that ismentioned during the time of registration with the site

4. When a user tries to access the link of the activity like symposium, seminar,techno-feat, etc He/she should be able to view the details like

• Date and time of conducting

• The procedure for applying for the participation

• The fees details

• Payment options

• Eligibility criteria

• Speakers name or guest’s name

• Topics on which the activity is performed

• Prize details if any

• Address for sending the applications for the participation

• Terms and conditions, etc

5. The navigation bar should include the following

• Home Page

• Login Page

• Application or enroll Page

• Update/Edit Page

• Subscribe Page (through this one can create the account) and unsubscribe

• Page (through this one can deactivate the account created)

• About Us Page

• Contact Information Page

6. Through Login page, users and admin can login

7. Through the Enroll page one can enroll or apply for symposiums, seminars, Feat, etc

Techno-8. Through Un-Enroll for an event (symposiums/seminars/Techno-Feat)

9. Through Subscribe Page one can subscribe for the mailing lists and create theaccount with the site

10. Through Unsubscribe Page one can subscribe for the mailing lists

11. Through Update page that is available after login one can Manage PersonalInformation

12. It should also include the About Us and Contact information

13. The payment options to be included are

• Payment through Demand Draft

• Payment through Cheque

- Require loged in

- Select subcribe on menu bar

- Select categories of event that you prefer and want to get news

Process:

- Add UserID and CategoryID to table EmailRecieverEventCategory

Output:

- User receiver email for each news

4.2- User enroll on online system:

Input:

- User ID (User must loged in)

- Event ID (user can search by event info)

Process:

- Add user ID and event info to database (table EnrollEvent)

Output:

- Details of enrollment with printing support

4.3- Employee create enrollment for user:

Input:

- Case 1: Users go to the university to register directly The employee creates

enrollment for them

- Case 2: Users send the enrollment (hard copy) to the university The employee creates the enrollment for them

Process:

- Employee enter user info to create enrollment form When he enter email, program check the existence of this email If this email isn’t existed, new user will create and user info is send to this email, otherwise, the user info has this email auto fill to this form

- The status of enrollment is paid (IsPayment field on EnrollEvent = true)

5 HARDWARE/ SOFTWARE REQUIREMENT:

5.1- Hardware & OS

1 A minimum computer system that will help you access all the tools in the courses

is a Pentium 166 or better

2 64 Megabytes of RAM or better

3 Windows 98 (or higher if possible)

4 Java Virtual Machine

TASK SHEET OF REVIEW 1

27-Dec-

REVIEW 2 Analysis & Design

6 ARCHITECTURE & DESIGN OF THE PROGRAM:

The standard 3-tier architecture consists of presentation and application logic in theclient, application and business logic in a middle tier application server, and data managed bydatabase servers in the 3rd tier The application is typically controlled by user interface in theclient with substantial application processing taking place in the middle tier application server.The middle tier code typically drives 3rd tier data queries, updates, and transactions andimplements shared business logic Data manipulation performed by the application is typicallydone on object representations of 3rd tier data fetched through queries, or through datamanipulation APIs or SQL code that operates in the database server

From actual operation of the leaning and management, the entities are identified andmust be stored are:

6.1- Requirements Storage:

 Information about Users (such as the user id, password of the user, role of user,full name, email, address, phone number etc)

 Information about Role of User (role id, role name)

 Information about Events (event id, event name, category of event, date ofcreated, date of begin, date of end, address, fees detail, prize, image intro, detailsetc)

 Information about Categories (category id, category name)

 Information about Enrollment for an event (enroll id, event id, user id, date ofenroll)

 Information about Winners (winner id, enroll id, date of paid, payment option,employee)

 Information about Payment Option (option id, option name)

 Information about Subcribes for the mailing lists (subcribe id, category id, user id)

6.2- Requirements Functions:

a) Function of the User:

• Create the account with the website

• Login to the website

• Update user information himself/herself

• View list of events and details of an event

• Enroll or Unenroll for an event

• Subcribe or Unsubcribe for the mailing lists

b) Function of the Admin:

• Login to administrator pages

• Send email to any users

• Update the About Us and Contact information

c) Function of the Employee:

• Login to administrator pages

• Create enrollment for the end-user

• Update information of end-user.

• Send email to any users

• Implement payment for winners

7 DATA FLOW DIAGRAM (DFD):

7.1- DFD Level 0: Context diagram

Figure 1 DFD Context diagram

7.2- DFD Level 1: Website process

Figure 2 DFD Website process

7.2.1- DFD Level 1.1: Event management

Figure 3 DFD Event management

7.2.2- DFD Level 1.2: Enrollment management

Figure 4 DFD Enrollment management

7.2.3- DFD Level 1.3: Subcribes management

Figure 5 DFD Subcribes management

7.2.4- DFD Level 1.3: User management

Figure 6 DFD User management

Project Team: 06 Prepared by: All members Page 19 of 83

8 ALGORITHMS (FLOW CHARTS DIAGRAM):

Figure 7: Flow Chart for Login Object

Figure 8: Flow Chart for Add Object

Figure 9: Flow Chart for Edit Object

Figure 10: Flow Chart for Delete Object

Figure 11: Flow Chart for Search Object

9 USE CASES:

9.1- ACTOR:

Actor Name Description

Users 1 Create the account with the website.

2 Login to the website

3 Update user formation himself/herself

4 View list of events and details of an event

5 Enroll or Unenroll for an event

6 Subcribe or Unsubcribe for the mailing lists

Admin 1 Login to administrator pages.

9 Send email to any users

10 Implement payment for winners

11 Update the About Us and Contact information

Employee 1 Login to administrator pages

2 Create enrollment for the end-user

3 Update information of end-user.

4 Add new winner of an event.

5 Send email to any users

6 Implement payment for winners

9.2- USE CASE DESCRIPTION:

9.2.1- Register

USE CASE SPECIFICATION

Main Success Scenario:

User enters all required info and submit.

New user will be created in database.

The successful message is display.

Notifier email is send to this email.

USE CASE SPECIFICATION

No

Main Success Scenario:

User enters user id and password.

There is a user in database has the same user id and password.

User loged in successfully.

9.2.3- Update user information

USE CASE SPECIFICATION

Use-case Name Update user information

Actor:

User

Summary:

User will enter new information and submit

Main Success Scenario:

User will choose the fields, enter new information and submit.

New informarion will be saved in database.

USE CASE SPECIFICATION

Date 10-Jan-2013 Priority Hight

Main Success Scenario:

UserID and CatID is added Subcribes table

And user will receives email for each changes of prefered category.

9.2.5- Unsubcribe

USE CASE SPECIFICATION

Main Success Scenario:

User ID corresponding with CatID is removed from Subcribe table

Requied loged in.

Business Rules:

No

9.2.6- View Events

USE CASE SPECIFICATION

Use-case Name View Events

Main Success Scenario:

Get list of events from database and display on events page.

USE CASE SPECIFICATION

Use-case Name Details Event

Main Success Scenario:

User chooses an even.

The details info of that event will be display full on web page.

Alternative Scenario:

USE CASE SPECIFICATION

Main Success Scenario:

User chooses event and submit.

The enroll info will be appear on website with printing support.

USE CASE SPECIFICATION

No

Post Conditions:

No

Main Success Scenario:

The enrollment’s status is set to unenroll

9.2.10- Create enrollment for guest

USE CASE SPECIFICATION

Use-case Name Create enrollment for guest

Create enrollment for participant

Main Success Scenario:

Employee will enter user info to create enrollment form with selection an event When

he type email, program check the existence of this email If this email isn’t existed, new user will create and user info is send to this email, otherwise, the user info has this email auto fill to this form.

9.2.11- Add new winner of an event

USE CASE SPECIFICATION

Use-case Name Add new winner of an event

Date 10-Jan-2013 Priority Hight

Main Success Scenario:

Search for enrollment by userid and eventid Select a payment option and submit.

USE CASE SPECIFICATION

Author Le Thanh Binh

Main Success Scenario:

Search for winner Select date of paid and submit.

Date of paid will be update in the database to confirm the payment.

USE CASE SPECIFICATION

Use-case No. UC013 Use-case Version <1.0>

Use-case Name Manage Users

Main Success Scenario:

Enter information and submit, after the result message will appears.

9.2.14- Manage UserRoles

USE CASE SPECIFICATION

Use-case Name Manage UserRoles

Main Success Scenario:

Enter information and submit, after the result message will appears.

Requied loged in and is admin

Business Rules:

No

9.2.15- Manage Categories

USE CASE SPECIFICATION

Use-case Name Manage Categories

Main Success Scenario:

Enter information and submit, after the result message will appears.

USE CASE SPECIFICATION

Use-case Name Manage Events

Main Success Scenario:

Enter information and submit, after the result message will appears.

USE CASE SPECIFICATION

Use-case Name Manage Subcribes

No

Main Success Scenario:

Enter information and submit, after the result message will appears.

USE CASE SPECIFICATION

Use-case Name Manage Enrollments

No

Post Conditions:

No

Main Success Scenario:

Enter information and submit, after the result message will appears.

USE CASE SPECIFICATION

Use-case Name Manage PaymentOption

Create, remove, update payment option.

Main Success Scenario:

Enter information and submit, after the result message will appears.

USE CASE SPECIFICATION

Use-case Name Manage Winners

Actor:

Admin

Main Success Scenario:

Enter information and submit, after the result message will appears.

9.3- CONTEXT DIAGRAM:

9.3.1- USER:

9.3.2- ADMIN:

9.3.3- EMPLOYEE:

10 ENTITIES:

Project Team: 06 Prepared by: All members Page 53 of 83

Project Team: 06 Prepared by: All members Page 54 of 83