ePROJECT National Level Paper Presentation FPT APTECH

Centre Name: ACE-HCMC-3-FPT

National Level Paper Presentation
Documentation

Group Member

LE THANH BINH - Student635001
VUONG QUOC HUNG - Student557205
LE TUAN AN - Student556489
NGUYEN TAT THIEN - Student556203
TRAN NHUT QUANG - Student522237

Group Name

Group 6

Instructor

Trang Hong Son

Batch

F5-10-1106-T1

Semester

4

Ho Chi Minh City, 01/2013

Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

This is to certify that
1.
2.
3.
4.
5.

LE THANH BINH ...............................................Student635001
VUONG QUOC HUNG ......................................Student557205
LE TUAN AN ....................................................Student556489
NGUYEN TAT THIEN .........................................Student556203
TRAN NHUT QUANG ........................................Student522237

Has successfully Designed and Developed.

National Level Paper Presentation
Submitted by: Le Thanh Binh
Date of issue: 15 – Jan – 2013
Authorized Signature:
Binh Le

01-2013

Project Team: 06

Prepared by: All members

Page 2 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

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

Project Team: 06

Prepared by: All members

Page 3 of 83

Project: National Level Paper Presentation

1.

Document: Development Guide

Approved by: Faculty

ACKNOWLEDGEMENTS:

We would like to acknowledge all those who have given moral support and helped us make
the project a success.
We wish to express our gratitude to the eProject Team at the Head Office, who guided and
helped us. Particular thanks to Mr. Trang Hong Son, who suggested the "debugging is
parallelizable" formulation, and helped to develop the analysis that proceeds from it. I would
also like to express my gratitude to all the student members of my centre (HCM, Aptech Fat3)
for not only providing me with the opportunity to work with them on this project, but also for
their support and encouragement throughout the process.
Although, there have been many attempted but by the time the limited practice should
not 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 their
valuable suggestions and constructive feedback.

2.

INTRODUCTION:

KSC Technology and Sciences is the educational university which runs the classes for
the categories like Engineering, Pharmaceutical sciences, Literature, etc. It is one of the

famous universities in the country. They generally conduct Paper Presentations at state level
and national level. They also conduct seminars, Techno-Feat, etc. so as to entertain the
students in the technical back grounds.

3.

PROBLEM DEFINITION:

Each time when they conduct seminars, symposiums, or paper presentation, etc. they
used to send the invitations for the participation of the students of other colleges, etc. so that
the knowledge of the student can be enhanced and at the same time, the students who does
not 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 some
registration fees for the gate pass and also they will provide the details like the topics for
which seminars or paper presentations or symposiums or techno-feats are conducted. For the
seminars and the Techno-feats they also provide the names of the speakers who are
conducting or providing this. Along with the invitation they also send the format of
application, which is to be filled and sent back to the address as mentioned in the invitation
for participating in the activities.
In general to participate in these activities, the students who do not belong to this
university send their requests by filling in the application form as per the format sent and
Project Team: 06

Prepared by: All members

Page 4 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

send it along with the payment through courier or directly dropping it at the address in
personal. In case of the Paper presentations, along with the courier, they also used to submit
both the soft copy and the hard copy, so that they can reach the mentioned address before
the end date of the participation. After sending these copies, they used to verify and then
finalize which students are to be participated in this paper presentation. The selection is
purely based on the technology (like mostly they prefer the new implementations in the
technology, etc.).
Now they want to provide a facility where the participants can register themselves
online 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 print
out of the application along with the signature of the participant and for the paper
presentation, the hard copy of the paper presentation will be sent along with it. So they have
approached 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 the
winners of the recent activity conducted is to be displayed. Also the details of the
participants like how many are registered for the recent or for the latest activity conducted
can 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 is
mentioned 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

Project Team: 06

Prepared by: All members

Page 5 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

• Page (through this one can deactivate the account created)
• About Us Page
• Contact Information Page

Through Login page, users and admin can login.
Through the Enroll page one can enroll or apply for symposiums, seminars, TechnoFeat, etc.
8.
Through Un-Enroll for an event (symposiums/seminars/Techno-Feat)
9.
Through Subscribe Page one can subscribe for the mailing lists and create the
account 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 Personal
Information
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
• Payment by cash
14.
The application can be done in both the ways
• Online application

Note: The payment can be sent through the courier or dropped at the address. Once the
payment is cleared, then only the enrollment will be activated.
6.
7.

• Taking the print out of the application and filling it up and sending it through
courier to the address mentioned.

4.

CUSTOMER REQUIREMENT SPECIFICATION (CRS):

4.1- User subcribe:
Input:
- 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.

Project Team: 06

Prepared by: All members

Page 6 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

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.
Output:
- The enrollment for user

4.4- Payment:
Input:
- Enrollment info.

Process:
- The employee searches the enrollment by enrollment info and changes payment
status.
Output:
- The status of enrollment is paid. (IsPayment field on EnrollEvent = true).

Project Team: 06

Prepared by: All members

Page 7 of 83


Project: National Level Paper Presentation

5.

Document: Development Guide

Approved by: Faculty

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.

5.2- Software
1.
2.
3.
4.
5.
6.
7.
8.

Notepad/HTML editor/Java editor
Dream weaver/JavaScript
j2sdk1.4.1_02 (or later) / .Net / J2EE
JSP / Servlets
EJB / Struts
JDBC
SQL Server 2000 (or later) / Oracle 9i / MS Access
JDBC Driver

Project Team: 06

Prepared by: All members

Page 8 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

TASK SHEET OF REVIEW 1
Project
Ref. No.

Project Name:

02

REVIEW 1

Sr.
Task
No.

01

Date of Preparation of Activity Plan

National Level Paper
Presentation
Description

Start
Date

Complete
Date

Team member

Status

Problem Definition &
Solution

25-Dec2012

26-Dec2012

All

Completed

Customer
Requirement
Specification

27-Dec2012

31-Dec2012

All

Completed

Signature of Team Leader

Signature of Instructor

Le Thanh Binh

Trang Hong Son

Project Team: 06

Prepared by: All members

Page 9 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

REVIEW 2
Analysis & Design

Project Team: 06

Prepared by: All members

Page 10 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

6. ARCHITECTURE & DESIGN OF THE PROGRAM:
The standard 3-tier architecture consists of presentation and application logic in the
client, application and business logic in a middle tier application server, and data managed by
database servers in the 3rd tier. The application is typically controlled by user interface in the
client 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 and
implements shared business logic. Data manipulation performed by the application is typically
done on object representations of 3rd tier data fetched through queries, or through data
manipulation APIs or SQL code that operates in the database server.

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

Project Team: 06

Prepared by: All members

Page 11 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

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 of
created, date of begin, date of end, address, fees detail, prize, image intro, details
etc).
Information about Categories (category id, category name).
Information about Enrollment for an event (enroll id, event id, user id, date of
enroll).
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.
• Manage Users.
• Manage UserRole.
• Manage Categories.
• Manage Events.
• Manage Enrollments.
• Manage Subcribes.
• Manage PaymentOption.
• 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):
Project Team: 06

Prepared by: All members

Page 12 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

7.1- DFD Level 0: Context diagram

Figure 1. DFD Context diagram

Project Team: 06

Prepared by: All members

Page 13 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

7.2- DFD Level 1: Website process

Figure 2. DFD Website process

Project Team: 06

Prepared by: All members

Page 14 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

7.2.1- DFD Level 1.1: Event management

Figure 3. DFD Event management

Project Team: 06

Prepared by: All members

Page 15 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

7.2.2- DFD Level 1.2: Enrollment management

Figure 4. DFD Enrollment management

Project Team: 06

Prepared by: All members

Page 16 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

7.2.3- DFD Level 1.3: Subcribes management

Figure 5. DFD Subcribes management

Project Team: 06

Prepared by: All members

Page 17 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

7.2.4- DFD Level 1.3: User management

Figure 6. DFD User management

Project Team: 06

Prepared by: All members

Page 18 of 83


Project: National Level Paper Presentation

Project Team: 06

Document: Development Guide

Prepared by: All members

Approved by: Faculty

Page 19 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

8. ALGORITHMS (FLOW CHARTS DIAGRAM):

Figure 7: Flow Chart for Login Object

Project Team: 06

Prepared by: All members

Page 20 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

Figure 8: Flow Chart for Add Object

Project Team: 06

Prepared by: All members

Page 21 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

Figure 9: Flow Chart for Edit Object

Project Team: 06

Prepared by: All members

Page 22 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

Figure 10: Flow Chart for Delete Object

Project Team: 06

Prepared by: All members

Page 23 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

Figure 11: Flow Chart for Search Object

Project Team: 06

Prepared by: All members

Page 24 of 83


Project: National Level Paper Presentation

Document: Development Guide

Approved by: Faculty

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.
1. Login to administrator pages.
2. Manage Users.
3. Manage UserRole.
4. Manage Categories.
5. Manage Events.
6. Manage Enrollments.
7. Manage Subcribes.
8. Manage PaymentOption.
9. Send email to any users.
10. Implement payment for winners.
11. Update the About Us and Contact information.
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.

Admin

Employee

Project Team: 06

Prepared by: All members

Page 25 of 83