eProject EasyTickets (Database+Code+Feeback Form)

- Check username and password from database- If correct, show welcome message and redirect to admin control panel - If information is not exist, show failure message message if data is e

EasyTickets

-APROTRAIN APTECH

(285 Doi Can – Hanoi -Vietnam)

Group Members NGUYEN DINH QUYEN

PHAM QUANG HIEP ( Member) Student408180 NGUYEN VUONG ANH ( Member) Student399819NGUYEN CONG TUAN ( Member) Student408531

December 2012

2.1.1 Client: 5

2.1.2 Project/Business Objective: 5

2.1.3 Hardware requirements 6

2.1.4 Software requirements 6

2.2 System Functions 6

2.2.1 Admin-site : 6

2.2.2 Client-site 8

3 System Design 10

3.1Data Flow Diagram 10

3.1Entity – Relationship Diagram 26

3.3 Table Design 26

3.3.0 Table tblAccount: Store information about of tblAccount 26

3.3.1 Table tblCity s: Store information tblCity 27

3.3.2 Table tblClass: Store information of tblClass 27

3.3.3 Table tblEvent_type: Store information of tblEvent_type 27

3.3.4 Table tblEvent: Store information about of tblEvent 27

3.3.5 Table tblRole: Store information about of tblRole 28

3.3.6 Table tblTicket: Store information of tblTicket 28

3.3.7 Table tblTicket_booking: Store information of tblTicket_booking 28

3.3.8 Table tblVenue: Store information of tblVenue 29

3.3.9 Table tblFeedback: Store information of tblFeedback 29

3.4 Flow Chat 29

3.4.1 Add new record 29

3.4.2 Edit record 31

3.4.3 Search information 31

3.4.4 Delete record 32

4 Database Design 33

4.0tblAccount 33

4.1tblCity 34

4.2tblClass 34

4.3tblEvent 34

4.4tblEvent_type 34

4.5tblRole 35

4.7tblTicket_booking 35

4.8tblVenue 36

4.9tblFeedback 36

5.GUI design 36

1 Problem Definition Term Description DFD Data Flow Diagram ERD Entities-Relationships Diagram Abbreviations

1.1 Problem Definition:

‘Showbiz‘is the company is principally into ticket sales, marketing and

distribution of event tickets The services include providing information on multiple event categories, providing ticketing facilities for several leading

multiplexes, arenas and stadiums They are thinking of the concept of

developing a web portal, where a customer can book movie tickets in theatres

showbiz customer.

1 Customer Requirement Specification

2.1 Customer Requirement Specifications Details

2.1.1 Client:

Aptech Ltd.

2.1.2 Project/Business Objective:

Generic:

 Register with the site

 Change the password after login to the application

 View See his/her details and change it

 Help from the system

 View all interviews scheduled to be taken

 View the details of the applicants details

 View the details of the vacancy

 Search

 Access to change the Interview details- Date/Time, Status

Admin :

 Create a new vacancy

 Change any of the editable details for the vacancy

 Create a new applicant

 Change any of the editable details for the applicant

 Postpone or remove the interview

 Search

2.1.3 Hardware requirements

Hard-disk 20MB space avaiable 20MB space avaiable

Browser Firefox,IE8

2.1.4 Software requirements

 Operating System: Microsoft Windows XP, Vista, or 7

 Intergrated Development Environment : NetBeans 6.9.1

 Technology Platform: J2EE

 Web Server : Apache Tomcat

 Database Management System: Microsoft SQL Server 2005

 Client Browser : Internet Explorer 8+, Mozilla Firefox 3.5+

- Check username and password from database

- If correct, show welcome message and redirect to admin control panel

- If information is not exist, show failure message

message (if data is exist) and redirect

to admin panel

- Show failure message (if data is not exist)

2 Change Profile - Password

- Update to database (if satisfy all conditions)

- If correct, show successful message

- If not, show failure message

Show successful message (if the

information was updated into database)

- Show failure message (for each wrong case)

3 View applicant

details

- Select applicant -- Check loginGet data from

database and show

it to user’s details panel

- Show user’s details

4 View interview

details

- Select interview -- Check loginGet data from

database and show

it to building ‘s details panel

(reservation id, customers)

- Check login

- Find data from database

according the option was chosen.

- Show the fetched data to result panel

- Show data into table detail

7 Logout function - Click to button

logout -- Remove sessionRedirect to admin

login panel

2.2.2 Client-site

1 Register - User name

- Check username and e-mail (existent in the database)

- If all are correct, insert data into database and show successful message.

Redirect to client homepage

- If not, show failure message and redirect to register page

- Show successful message (if data was inserted into database)

- Show failure message (for each wrong case)

- Password

- Validate information

- Check username and password from database (existent)

- If user is exist, login to system, change session username as this username.

Redirect to client

- Welcome message (if login success)

- Show failure message (for each wrong case)

username as null

- Redirect to client homepage

- Hide logout, profile.

- Show register and login options.

4 Change profile - Click to change profile

option

- New information of profile

- Check login

- Validate profile information

- If all are correct, update data into database Show successful message and redirect to profile page

- If not, show failure message and redirect to profile page

- Show successful message and new profile if data was updated to database

- Show failure message (for each wrong case)

5 Change

password

- Click to change password button

- Old password

- New password (2 times)

- Check login

- Validate

- Check old password

- If all are correct, change password and update into database Show successful message and redirect to profile page

- If not, show failure message and redirect to change password page

- Show successful message (if data was updated into database)

- Show failure message (for each wrong case)

6 Forget

password

- Click to forget password option (in login page)

- Username

- E-mail

- Check username and e-mail from database

(existent)

- If correct, send password to this e-mail Show report page.

- If not, show failure message

- Show report page (your password is sent to your e- mail)

- Show failure message (for each wrong case)

and redirect to forget password page

7 View profile - Click to view profile

option -- Check loginGet the

information of this user from database and show it to profile page

- Information of user

- If all are correct, get the information and show for user

- Check login

- If login is correct then send contact to admin else recommend register

- Contact success

3 System Design

3.1 Data Flow Diagram

3.1.1 DFD – Level 0 (Context Diagram)

DFD level 0: Context Diagram

DFD Level-0: Context diagram of Book Store Online System includes:

 Two external entities: The User and Administrator.

 One main process: Book Store Online.

The operation of the system: When two external entities have got requirement information from the system, they will send the information request and have results, the system will return these results for these two external entities.

3.1.2 DFD – Level 1

DFD level 1: Application process

Data Flow Diagram at the top-level (DFD Level-1) of the this system includes:

There are two external entities: The User and Administrator

There are 4 Process:

1. Change Information

2. Login

3. User Function

4. System Function

3.1.3 DFD – Level 2 for User Function: Enquiry Information

DFD Level 2-1: Enquiry Information

3.1.3.DFD – Level 2 for User Function: Order Tickets

DFD Level 2-2: Order Tickets

3.1.4.DFD – Level 2 for Admin Function: View Detail of User

DFD Level 2-3: View Details of User

3.1.5.DFD – Level 2 for Admin Function: Edit Detail of User

DFD Level 2-4: Edit Details of User

3.1.6.DFD – Level 2 for Admin Function: Create New User

DFD Level 2-5: Create New User

3.1.7.DFD – Level 2 for Admin Function: View Detail of Ticket

DFD Level 2-6: View Detail of Ticket

3.1.8.DFD – Level 2 for Admin Function: Edit Detail of Ticket

DFD Level 2-7: Edit Detail of Ticket

3.1.8.DFD – Level 2 for Admin Function: Create New Ticket

DFD Level 2-8: Create New Ticket

DFD Level 2-9: View Detail Category

3.1.10.DFD – Level 2 for Admin Function: Edit Detail Category

DFD Level 2-10: Edit Detail Category

DFD Level 2-11: Create New Category

3.1.12.DFD – Level 2 for User: Change Information Function

DFD Level 2-12: Change User Information

DFD Level 2-13: Login

3.1 Entity – Relationship Diagram

Database Diagram

ID int Not null Primary key

3.3.1 Table tblCity s: Store information tblCity.

2 tblCity

Column Data type Size Allow null Description

3.3.2 Table tblClass: Store information of tblClass

3 tblClass

Column Data type Size Allow null Description

3.3.3 Table tblEvent_type: Store information of tblEvent_type

4 tblEvent_type

Column Data type Size Allow null Description

3.3.4 Table tblEvent: Store information about of tblEvent

5 tblEvent

Column Data type Size Allow null Description

3.3.5 Table tblRole: Store information about of tblRole.

6 tblRole

Column Data type Size Allow null Description

3.3.6 Table tblTicket: Store information of tblTicket

7 tblTicket

Column Data type Size Allow null Description

3.3.7 Table tblTicket_booking: Store information of tblTicket_booking

7 tblTicket_booking

3.3.8 Table tblVenue: Store information of tblVenue

8 tblVenue

Column Data type Size Allow null Description

3.3.9 Table tblFeedback: Store information of tblFeedback

9 tblFeedback

Column Data type Size Allow

null

Description

3.4 Flow Chat

3.4.1 Add new record

3.4.2 Edit record

3.4.3 Search information

4 Database Design

4.0 tblAccount

4.1 tblCity

4.2 tblClass

4.3 tblEvent

4.5 tblRole

4.6 tblTicket

4.7 tblTicket_booking

4.8 tblVenue

4.9 tblFeedback

Admin GUI