eProject : Easy Tickets
FPT-APTECH EDUCATION CENTER
*** *
eProject Documentation
Easy Tickets
Project on 4nd semester HDSE course
Class :
Ha Noi, 04/04/ 2011
Teachers: Group member:
Page 1
eProject : Easy Tickets
Các b n c n sourceCode pm mail hungdt138@outlook.com ạ ầ
Page 2
eProject : Easy Tickets
18 USE CASE # ......................................................................................................
18 USE CASE NAME .............................................................................................
18 ACTOR ..............................................................................................................
PURPOSE 18 .........................................................................................................
PRECONDITIONS 18 .............................................................................................
POSTCONDITIONS IN WORDS 18 ........................................................................
19 USE CASE # ......................................................................................................
19 USE CASE NAME .............................................................................................
19 ACTOR ..............................................................................................................
PURPOSE 19 .........................................................................................................
PRECONDITIONS 19 .............................................................................................
POSTCONDITIONS IN WORDS 19 ........................................................................
20 USE CASE # ......................................................................................................
20 USE CASE NAME .............................................................................................
20 ACTOR ..............................................................................................................
PURPOSE 20 .........................................................................................................
PRECONDITIONS 20 .............................................................................................
POSTCONDITIONS IN WORDS 20 ........................................................................
22 USE CASE # ......................................................................................................
Page 3
eProject : Easy Tickets
22 USE CASE NAME .............................................................................................
22 ACTOR ..............................................................................................................
22 PURPOSE ........................................................................................................
PRECONDITIONS 22 .............................................................................................
POSTCONDITIONS IN WORDS 22 ........................................................................
23 USE CASE # ......................................................................................................
23 USE CASE NAME .............................................................................................
23 ACTOR ..............................................................................................................
PURPOSE 23 .........................................................................................................
PRECONDITIONS 23 .............................................................................................
POSTCONDITIONS IN WORDS 23 ........................................................................
24 USE CASE # ......................................................................................................
24 USE CASE NAME .............................................................................................
24 ACTOR ..............................................................................................................
PURPOSE 24 .........................................................................................................
PRECONDITIONS 24 .............................................................................................
POSTCONDITIONS IN WORDS 24 ........................................................................
25 USE CASE # ......................................................................................................
25 USE CASE NAME .............................................................................................
25 ACTOR ..............................................................................................................
Page 4
eProject : Easy Tickets
PURPOSE 25 .........................................................................................................
PRECONDITIONS 25 .............................................................................................
POSTCONDITIONS IN WORDS 25 ........................................................................
26 USE CASE # ......................................................................................................
26 USE CASE NAME .............................................................................................
26 ACTOR ..............................................................................................................
26 PURPOSE ........................................................................................................
PRECONDITIONS 26 .............................................................................................
POSTCONDITIONS IN WORDS 26 ........................................................................
28 USE CASE # ......................................................................................................
28 USE CASE NAME .............................................................................................
28 ACTOR ..............................................................................................................
PURPOSE 28 .........................................................................................................
PRECONDITIONS 28 .............................................................................................
POSTCONDITIONS IN WORDS 28 ........................................................................
29 USE CASE # ......................................................................................................
29 USE CASE NAME .............................................................................................
29 ACTOR ..............................................................................................................
PURPOSE 29 .........................................................................................................
PRECONDITIONS 29 .............................................................................................
Page 5
eProject : Easy Tickets
POSTCONDITIONS IN WORDS 29 ........................................................................
30 USE CASE # ......................................................................................................
30 USE CASE NAME .............................................................................................
30 ACTOR ..............................................................................................................
PURPOSE 30 .........................................................................................................
PRECONDITIONS 30 .............................................................................................
POSTCONDITIONS IN WORDS 30 ........................................................................
31 USE CASE # ......................................................................................................
31 USE CASE NAME .............................................................................................
31 ACTOR ..............................................................................................................
31 PURPOSE ........................................................................................................
PRECONDITIONS 31 .............................................................................................
POSTCONDITIONS IN WORDS 31 ........................................................................
33 USE CASE # ......................................................................................................
33 USE CASE NAME .............................................................................................
33 ACTOR ..............................................................................................................
PURPOSE 33 .........................................................................................................
PRECONDITIONS 33 .............................................................................................
POSTCONDITIONS IN WORDS 33 ........................................................................
34 USE CASE # ......................................................................................................
Page 6
eProject : Easy Tickets
34 USE CASE NAME .............................................................................................
34 ACTOR ..............................................................................................................
PURPOSE 34 .........................................................................................................
PRECONDITIONS 34 .............................................................................................
POSTCONDITIONS IN WORDS 34 ........................................................................
35 USE CASE # ......................................................................................................
35 USE CASE NAME .............................................................................................
35 ACTOR ..............................................................................................................
PURPOSE 35 .........................................................................................................
PRECONDITIONS 35 .............................................................................................
POSTCONDITIONS IN WORDS 35 ........................................................................
36 USE CASE # ......................................................................................................
36 USE CASE NAME .............................................................................................
36 ACTOR ..............................................................................................................
36 PURPOSE ........................................................................................................
PRECONDITIONS 36 .............................................................................................
POSTCONDITIONS IN WORDS 36 ........................................................................
38 USE CASE # ......................................................................................................
38 USE CASE NAME .............................................................................................
38 ACTOR ..............................................................................................................
Page 7
eProject : Easy Tickets
PURPOSE 38 .........................................................................................................
PRECONDITIONS 38 .............................................................................................
POSTCONDITIONS IN WORDS 38 ........................................................................
39 USE CASE # ......................................................................................................
39 USE CASE NAME .............................................................................................
39 ACTOR ..............................................................................................................
PURPOSE 39 .........................................................................................................
PRECONDITIONS 39 .............................................................................................
POSTCONDITIONS IN WORDS 39 ........................................................................
40 USE CASE # ......................................................................................................
40 USE CASE NAME .............................................................................................
40 ACTOR ..............................................................................................................
PURPOSE 40 .........................................................................................................
PRECONDITIONS 40 .............................................................................................
POSTCONDITIONS IN WORDS 40 ........................................................................
41 USE CASE # ......................................................................................................
41 USE CASE NAME .............................................................................................
41 ACTOR ..............................................................................................................
PURPOSE 41 .........................................................................................................
PRECONDITIONS 41 .............................................................................................
Page 8
eProject : Easy Tickets
POSTCONDITIONS IN WORDS 41 ........................................................................
42 USE CASE # ......................................................................................................
42 USE CASE NAME .............................................................................................
42 ACTOR ..............................................................................................................
PURPOSE 42 .........................................................................................................
PRECONDITIONS 42 .............................................................................................
POSTCONDITIONS IN WORDS 42 ........................................................................
43 USE CASE # ......................................................................................................
43 USE CASE NAME .............................................................................................
43 ACTOR ..............................................................................................................
PURPOSE 43 .........................................................................................................
PRECONDITIONS 43 .............................................................................................
POSTCONDITIONS IN WORDS 43 ........................................................................
46 1 . USERS ..........................................................................................................
46 2 . CATEGORIES ..............................................................................................
46 3 . CITYS ...........................................................................................................
46 4 . THEATERS ...................................................................................................
5 . TICKETTYPES 46 .............................................................................................
6 . SEATREGISTERS 47 ........................................................................................
7 . SCHEDULES 47 ................................................................................................
Page 9
eProject : Easy Tickets
47 8 . PRICES .........................................................................................................
9 . CARDS 47 .........................................................................................................
47 10 . ITEMS .........................................................................................................
48 11 . TICKETS .....................................................................................................
48 12 . ORDERS .....................................................................................................
13 . ORDERDETAILS 48 ........................................................................................
14 . COMMENTS 48 ...............................................................................................
48 15 . FAQS ..........................................................................................................
Page 10
eProject : Easy Tickets
Page 11
eProject : Easy Tickets
Review 1
Introduction
In today’s busy world, people find it hard to find the time for entertainment. It is
really pretty time consuming to find out the various entertainment shows/movies and any
other such shows in and around the city. And on the top of it is more irritating to go
physically and book the ticket.
E-commerce can be thought as the best solution for this. Due to which the people can
buy the tickets right from home. No more buying in black. Moreover one can find the
information just with a click and get the booking done.
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. Everyone must take place to sell tickets to buy tickets. Invoices, vouchers are
made manually.
Proposed Solution
They are thinking of the concept of developing a web portal, where a customer
Page 12
eProject : Easy Tickets
can book movie tickets in theatres that are made available in the site. They wish to launch
the website by the name ‘www.easytickets.com’ where they can provide convenient,
secure, and fair access to the best possible tickets offered by the clients. Showbiz aims at
making events happening across the city more accessible-just a click away. Booking
tickets can now an effortless, fun and exciting experience for every showbiz customer.
Customer Requirement Specification (CRS)
System Requirement Specification :
Guest. Client. Administration.
Functionality for Guest :
1. View Information : Open website visitors can view the brief description about the company, about the services, the movie, the show information, and tickets of them. 2. Register or Login : The user must be able to either register with the site (if new user), else the user can login into his/her account.
3. Contact Us : Guest may contact the company through address, phone number, etc. of the company are to be provided, as per the details entered by the admin. 4. FAQs : Guest can view the FAQ’s as created by the admin.
Functionality for Client(The user logs into the Application) :
1. View Information : Open website visitors can view the brief description about the company, about the services, the movie, the show information, and tickets of them.
2. Search movie, show, ticket of them. 3. Booking : User can book the ticket for movie/drama/music show/sport event. 4. Check the availability of tickets on mentioned date and time in specified City. Get the information of the shows running in theatres. Know the special offers and discounts.
5. Comment of the movie or show. 6. Display, edit information of personal. 7. Contact Us : Guest may contact the company through address, phone number, etc. of the company are to be provided, as per the details entered by the admin. 8. FAQs : Guest can view the FAQ’s as created by the admin.
Functionality for Admin(After administer logs into the Application) :
Page 13
eProject : Easy Tickets
1. View and maintain information : Admin can view the brief description about
the company, about the services, about the users, the movie, the show information, and tickets of them. Also the administrator must be able to insert, edit and delete the detailed of information. 2. User management : Admin must be able to maintain (insert, update and delete) the users.
3. Movie and show management. 4. Ticket management. 5. Schedule management. 6. Seat management. 7. Theater management. 8. City management. 9. Category management. 10. Order and Order detail management. 11. Comment management. 12. Contact Us management : The contact details like address, phone number, etc.
of the company are to be maintained (insert, update, delete) by the administrator. 13. FAQs management : Admin must be able to maintain (insert, update, delete) the details of the FAQ’s with the questions and the answers.
14. Payment management : The payment details pertaining to the bill generated is to be maintained. And only after the total payment is received for the service request, after it is accepted, the service will be started at that place.
Hardware and software requirement
Minimum Requirements :
- Hardware: CPU Intel Pentium IV 2.0 Ghz, Ram 1 Gb, Hdd space require: 2 Gb. - Software: Window 2000,XP, NetBean 6.9, MS SQL Server 2005, Microsoft Office 2003 Recommended Requirements :
- HardWare: CPU Intel CoreDure 2.4 Ghz, Ram 2Gb, Hdd space require: 5 Gb. - SoftWare: Window XP,7,NetBean 6.9 , MS SQL Server 2005. Microsoft Office 2003
Page 14
eProject : Easy Tickets
Page 15
eProject : Easy Tickets
Review 2
Architecture and Design Model of the Project
The application will be made of a Web-based distributed three-tier and Three-Layer architecture to support multiple user transactions at the same time.
Presentation
Business Logic
Database
Web-based Distributed 3-Tier Architecture of the Project
Page 16
eProject : Easy Tickets
Presentation tier
Browser s
GU I
Local clients
Application
Web Server Web
Web Server
Business logic
Business tier
Data Access
Data
Data tier
Architecture 3-Tier , 3-Layer Model Use Case Diagram
System Administration :
Page 17
eProject : Easy Tickets
Manager Users :
Create new User
USE CASE # UC01_01 USE CASE Name
Create New User Admin Add new user to the System Admin login A new user is added to the System Admin enable function add new account
System Action ACTOR Purpose Preconditions Postconditions in words Trigger Extended Use Cases MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function user management
2. System display function user management
Page 18
eProject : Easy Tickets
3. Admin select function Add new user 4. Form Add new is display
5. Admin enter information into form add new user 6. Click Button Submit
7. System processing information and then saved to the database Branching Action Step
OTHER SUCCESSFUL SCENARIOS UNSUCCESSFUL SCENARIOS
Conditions 6a. When you click the button submit,inspection data is invalid Actions Display warning, check information until valid data is transferred to the next step
DuongPV 03/19/2011 Developer Creation date and last modified date
USE CASE #
Edit User UC01_02
USE CASE Name
Edit User Admin Edit information user in System Admin login to the System User information will be update add new information Admin enable function Edit user information
ACTOR Purpose Preconditions Postconditions in words Trigger Included Use Cases Search user Extended Use Cases
System Action MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function user management
2. System display function user management
3. Admin select search function user needs change
Page 19
eProject : Easy Tickets
4. System display user information to needs change
5. Admin change user information 6. Admin click button Edit
7. The System display a message asking Admin select Yes or No.
8. Admin conduct selection
9. System processing information was change then saved to the database End Use Case Branching Action Step OTHER SUCCESSFUL SCENARIOS Next to step 9 8a. Admin Click Button Yes
System Reset Information 8b.Admin Click Button No
UNSUCCESSFUL SCENARIOS
Conditions 6a. When you click the button edit,inspection data is invalid Actions Display warning, check information until valid data is transferred to the next step
DuongPV 03/19/2011 Developer Creation date and last modified date
USE CASE #
Delete User UC01_03
USE CASE Name
Delete User Information Admin Delete information user Admin login to the System One or more user will be removed from the System Admin enable function Delete user information
ACTOR Purpose Preconditions Postconditions in words Trigger Included Use Cases Search User
Page 20
eProject : Easy Tickets
Extended Use Cases
System Action MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function user management
2. System display function user management
3. Admin select search function employee needs delete
4. System display user information to needs delete
5. Admin Click Button Delete
6. The System display a message asking Admin select Yes or No 7. Admin conduct selection
8. System remove user information in database End Use Case Branching Action Step OTHER SUCCESSFUL SCENARIOS 5a. Admin click button yes
5b. Admin click button no
System processing information was removed then saved to the database System exit delete function then back the user management Actions Conditions
DuongPV 03/19/2011 UNSUCCESSFUL SCENARIOS Developer Creation date and last modified date
Search User
Page 21
eProject : Easy Tickets
USE CASE # UC01_04 USE CASE Name
Search User Information Admin Search user Information Admin login to the System System display user information needs search Admin enable function Search user information
ACTOR Purpose Preconditions Postconditions in words Trigger Extended Use Cases
System Action MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function user management
2. System display function user management
3. Admin use search function
4. System display user information to needs search End Use Case Branching Action Step OTHER SUCCESSFUL SCENARIOS 3a. Click button search
3b. Click button close
System display user information to needs search. System exit search function then back the user management
Conditions Actions
DuongPV 03/19/2011 UNSUCCESSFUL SCENARIOS Developer Creation date and last modified date
Manager Items :
Page 22
eProject : Easy Tickets
Create new Item
USE CASE # UC02_01 USE CASE Name
Create New Item Admin Add new Item to the System Admin login A new Item is added to the System Admin enable function add new Item
System Action ACTOR Purpose Preconditions Postconditions in words Trigger Extended Use Cases MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function Item management
2. System display function Item management
3. Admin select function Add new Item 4. Form Add new is display
5. Admin enter information into form add new Item 6. Click Button Submit
Page 23
eProject : Easy Tickets
Step 7. System processing information and then saved to the database Branching Action
OTHER SUCCESSFUL SCENARIOS UNSUCCESSFUL SCENARIOS
Conditions 6a. When you click the button submit,inspection data is invalid Actions Display warning, check information until valid data is transferred to the next step
LoiPT 03/19/2011 Developer Creation date and last modified date
USE CASE #
Edit Item UC02_02
USE CASE Name
Edit Item Admin Edit information Item in System Admin login to the System Item information will be update add new information Admin enable function Edit Item information
ACTOR Purpose Preconditions Postconditions in words Trigger Included Use Cases Search Item Extended Use Cases
System Action MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function Item management
2. System display function Item management
3. Admin select search function Item needs change
4. System display Item information to needs change
5. Admin change Item information 6. Admin click button Edit
Page 24
eProject : Easy Tickets
7. The System display a message asking Admin select Yes or No.
8. Admin conduct selection
9. System processing information was change then saved to the database End Use Case Branching Action Step OTHER SUCCESSFUL SCENARIOS Next to step 9 8a. Admin Click Button Yes
System Reset Information 8b.Admin Click Button No
UNSUCCESSFUL SCENARIOS
Conditions 6a. When you click the button edit,inspection data is invalid Actions Display warning, check information until valid data is transferred to the next step
LoiPT 03/19/2011 Developer Creation date and last modified date
USE CASE #
Delete Item UC02_03
USE CASE Name
Delete Item Information Admin Delete information Item Admin login to the System One or more Item will be removed from the System Admin enable function Delete Item information
ACTOR Purpose Preconditions Postconditions in words Trigger Included Use Cases Search Item Extended Use Cases
System Action MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function Item management
Page 25
eProject : Easy Tickets
2. System display function Item management
3. Admin select search function Item needs delete
4. System display Item information to needs delete
5. Admin Click Button Delete
6. The System display a message asking Admin select Yes or No 7. Admin conduct selection
8. System remove Item information in database End Use Case Branching Action Step OTHER SUCCESSFUL SCENARIOS 5a. Admin click button yes
5b. Admin click button no
System processing information was removed then saved to the database System exit delete function then back the user management Actions Conditions
LoiPT 03/19/2011 UNSUCCESSFUL SCENARIOS Developer Creation date and last modified date
Search Item
USE CASE # UC02_04 USE CASE Name
Search Item Admin Search Item Information Admin login to the System System display Item information needs search Admin enable function Search Item information
ACTOR Purpose Preconditions Postconditions in words Trigger Extended Use Cases
System Action MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function Item management
Page 26
eProject : Easy Tickets
2. System display function Item management
3. Admin use search function
Step 4. System display Item information to needs search End Use Case Branching Action OTHER SUCCESSFUL SCENARIOS 3a. Click button search
3b. Click button close
System display Item information to needs search. System exit search function then back the Item management
Conditions Actions
LoiPT 03/19/2011 UNSUCCESSFUL SCENARIOS Developer Creation date and last modified date
Manager Schedules:
Page 27
eProject : Easy Tickets
Create new Schedule
USE CASE # UC03_01 USE CASE Name
Create New Schedule Admin Add new Schedule to the System Admin login A new Schedule is added to the System Admin enable function add new Schedule
System Action ACTOR Purpose Preconditions Postconditions in words Trigger Extended Use Cases MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function Schedule management
2. System display function Schedule management
3. Admin select function Add new Schedule 4. Form Add new is display
5. Admin enter information into form add new Schedule 6. Click Button Submit
Page 28
eProject : Easy Tickets
Step 7. System processing information and then saved to the database Branching Action
OTHER SUCCESSFUL SCENARIOS UNSUCCESSFUL SCENARIOS
Conditions 6a. When you click the button submit,inspection data is invalid Actions Display warning, check information until valid data is transferred to the next step
TrangPTK 03/19/2011 Developer Creation date and last modified date
Edit Schedule
USE CASE # UC03_02 USE CASE Name
ACTOR Purpose Preconditions Postconditions in words
Edit Schedule Admin Edit information Schedule in System Admin login to the System Schedule information will be update add new information Admin enable function Edit Schedule information
Trigger Included Use Cases Search Schedule Extended Use Cases
System Action MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function Schedule management
2. System display function Schedule management
3. Admin select search function Schedule needs change
4. System display Schedule information to needs change
5. Admin change Schedule information 6. Admin click button Edit
Page 29
eProject : Easy Tickets
7. The System display a message asking Admin select Yes or No.
8. Admin conduct selection
9. System processing information was change then saved to the database End Use Case Branching Action Step OTHER SUCCESSFUL SCENARIOS Next to step 9 8a. Admin Click Button Yes
System Reset Information 8b.Admin Click Button No
UNSUCCESSFUL SCENARIOS
Conditions 6a. When you click the button edit,inspection data is invalid Actions Display warning, check information until valid data is transferred to the next step
TrangPTK 03/19/2011 Developer Creation date and last modified date
Delete Schedule
USE CASE # UC03_03 USE CASE Name
Delete Schedule Admin Delete information Schedule Admin login to the System One or more Schedule will be removed from the System Admin enable function Delete Schedule information
ACTOR Purpose Preconditions Postconditions in words Trigger Included Use Cases Search Schedule Extended Use Cases
System Action MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function Schedule management
Page 30
eProject : Easy Tickets
2. System display function Schedule management
3. Admin select search function Schedule needs delete
4. System display Schedule information to needs delete
5. Admin Click Button Delete
6. The System display a message asking Admin select Yes or No 7. Admin conduct selection
8. System remove Schedule information in database End Use Case Branching Action Step OTHER SUCCESSFUL SCENARIOS 5a. Admin click button yes
5b. Admin click button no
System processing information was removed then saved to the database System exit delete function then back the user management Actions Conditions
TrangPTK 03/19/2011 UNSUCCESSFUL SCENARIOS Developer Creation date and last modified date
Search Schedule
USE CASE # UC03_04 USE CASE Name
Search Schedule Admin Search Schedule Information Admin login to the System System display Schedule information needs search Admin enable function Search Schedule information
ACTOR Purpose Preconditions Postconditions in words Trigger Extended Use Cases
Actor Action System Action
Page 31
eProject : Easy Tickets
MAIN SUCCESSFUL SCENARIO 1. Admin access system select function Schedule management
2. System display function Schedule management
3. Admin use search function
Step 4. System display Schedule information to needs search End Use Case Branching Action OTHER SUCCESSFUL SCENARIOS 3a. Click button search
3b. Click button close
System display Schedule information to needs search. System exit search function then back the Schedule management
Conditions Actions
TrangPTK 03/19/2011 UNSUCCESSFUL SCENARIOS Developer Creation date and last modified date
Manager Tickets :
Page 32
eProject : Easy Tickets
Create new Ticket
USE CASE # UC04_01 USE CASE Name
Create New Ticket Admin Add new Ticket to the System Admin login A new Ticket is added to the System Admin enable function add new Ticket
System Action ACTOR Purpose Preconditions Postconditions in words Trigger Extended Use Cases MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function Ticket management
2. System display function Ticket management
3. Admin select function Add new Ticket 4. Form Add new is display
5. Admin enter information into form add new Ticket 6. Click Button Submit
Page 33
eProject : Easy Tickets
Step 7. System processing information and then saved to the database Branching Action
OTHER SUCCESSFUL SCENARIOS UNSUCCESSFUL SCENARIOS
Conditions 6a. When you click the button submit,inspection data is invalid Actions Display warning, check information until valid data is transferred to the next step
AnhDV 03/19/2011 Developer Creation date and last modified date
USE CASE #
Edit Ticket UC04_02
USE CASE Name
Edit Ticket Admin Edit information Ticket in System Admin login to the System Ticket information will be update add new information Admin enable function Edit Ticket information
ACTOR Purpose Preconditions Postconditions in words Trigger Included Use Cases Search Ticket Extended Use Cases
System Action MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function Ticket management
2. System display function Ticket management
3. Admin select search function Ticket needs change
4. System display Ticket information to needs change
5. Admin change Schedule information 6. Admin click button Edit
Page 34
eProject : Easy Tickets
7. The System display a message asking Admin select Yes or No.
8. Admin conduct selection
9. System processing information was change then saved to the database End Use Case Branching Action Step OTHER SUCCESSFUL SCENARIOS Next to step 9 8a. Admin Click Button Yes
System Reset Information 8b.Admin Click Button No
UNSUCCESSFUL SCENARIOS
Conditions 6a. When you click the button edit,inspection data is invalid Actions Display warning, check information until valid data is transferred to the next step
AnhDV 03/19/2011 Developer Creation date and last modified date
Delete Ticket
USE CASE # UC04_03 USE CASE Name
Delete Ticket Admin Delete information Ticket Admin login to the System One or more Ticket will be removed from the System Admin enable function Delete Ticket information
ACTOR Purpose Preconditions Postconditions in words Trigger Included Use Cases Search Ticket Extended Use Cases
System Action MAIN SUCCESSFUL SCENARIO
Actor Action 1. Admin access system select function Ticket management
Page 35
eProject : Easy Tickets
2. System display function Ticket management
3. Admin select search function Ticket needs delete
4. System display Ticket information to needs delete
5. Admin Click Button Delete
6. The System display a message asking Admin select Yes or No 7. Admin conduct selection
8. System remove Ticket information in database End Use Case Branching Action Step OTHER SUCCESSFUL SCENARIOS 5a. Admin click button yes
5b. Admin click button no
System processing information was removed then saved to the database System exit delete function then back the user management Actions Conditions
AnhDV 03/19/2011 UNSUCCESSFUL SCENARIOS Developer Creation date and last modified date
Search Ticket
USE CASE # UC04_04 USE CASE Name
Search Ticket Admin Search Ticket Information Admin login to the System System display Ticket information needs search Admin enable function Search Ticket information
ACTOR Purpose Preconditions Postconditions in words Trigger Extended Use Cases
Actor Action System Action
Page 36
eProject : Easy Tickets
MAIN SUCCESSFUL SCENARIO 1. Admin access system select function Ticket management
2. System display function Ticket management
3. Admin use search function
Step 4. System display Ticket information to needs search End Use Case Branching Action OTHER SUCCESSFUL SCENARIOS 3a. Click button search
3b. Click button close
System display Ticket information to needs search. System exit search function then back the Ticket management
Conditions Actions
AnhDV 03/19/2011 UNSUCCESSFUL SCENARIOS Developer Creation date and last modified date
Function of User :
Page 37
eProject : Easy Tickets
Register
USE CASE # UC05_01 USE CASE Name
Register User Register new user to the System
A new user is added to the System Admin enable function Register user
System Action ACTOR Purpose Preconditions Postconditions in words Trigger Extended Use Cases MAIN SUCCESSFUL SCENARIO
Actor Action 1. User access website system select function Register 2. Form Register is display
3. User enter information into form register
Page 38
eProject : Easy Tickets
4. Click Button Submit
Step 5. System processing information and then saved to the database Branching Action
OTHER SUCCESSFUL SCENARIOS UNSUCCESSFUL SCENARIOS
Conditions 4a. When you click the button submit,inspection data is invalid Actions Display warning, check information until valid data is transferred to the next step
TrangTV 03/19/2011 Developer Creation date and last modified date
Login
USE CASE # UC05_02 USE CASE Name
Login User Login to the website System
Login to website Admin enable function Login
System Action ACTOR Purpose Preconditions Postconditions in words Trigger Extended Use Cases MAIN SUCCESSFUL SCENARIO
Actor Action 1. User access website system select function Login 2. Form Login is display
3. User enter information into form login 4. Click Button Submit
5. System processing information and display successful. Branching Action Step OTHER SUCCESSFUL SCENARIOS Conditions Actions
Page 39
eProject : Easy Tickets
UNSUCCESSFUL SCENARIOS 4a. When you click the button submit,inspection data is invalid Display warning, check information until valid data is transferred to the next step
TrangTV 03/19/2011 Developer Creation date and last modified date
Edit Profile
USE CASE # UC05_03 USE CASE Name
Edit Profile User Edit information User in System User login to the website System User information will be update add new information Admin enable function Edit User information
ACTOR Purpose Preconditions Postconditions in words Trigger Included Use Cases Extended Use Cases
System Action MAIN SUCCESSFUL SCENARIO
Actor Action 1. User access website system select function Profile management
2. System display function Profile management
3. User select function Edit profile 4. System form edit profile
5. User change user information 6. User click button Edit
7. The System display a message asking User select Yes or No. 8. User conduct selection
9. System processing information was change then saved to the database End Use Case Branching Action Step OTHER SUCCESSFUL SCENARIOS
Page 40
eProject : Easy Tickets
Next to step 9 8a. User Click Button Yes
8b.User Click Button No System Reset Information
UNSUCCESSFUL SCENARIOS
Conditions 6a. When you click the button edit,inspection data is invalid Actions Display warning, check information until valid data is transferred to the next step
TrangTV 03/19/2011 Developer Creation date and last modified date
Search Movie or Show
USE CASE # UC05_04 USE CASE Name
Search Item User Search information Item in System
Search item
ACTOR Purpose Preconditions Postconditions in words Trigger Included Use Cases Extended Use Cases
System Action MAIN SUCCESSFUL SCENARIO
Actor Action 1. User access website system select function search Item
2. System display function search Item 3. System display Category Selection 4. User selectcategory
5. System display City Selection 6. User select city
7. System display Theater Selection 8. User select Theater
Page 41
eProject : Easy Tickets
9. System display Item selection 10. User select Item
11. System display Item information End Use Case
TrangTV 03/19/2011 Developer Creation date and last modified date
Search Ticket
USE CASE # UC05_05 USE CASE Name
Search Ticket User Search information Ticket in System
Search ticket
Search Item
ACTOR Purpose Preconditions Postconditions in words Trigger Included Use Cases Extended Use Cases
System Action MAIN SUCCESSFUL SCENARIO
Actor Action 1. User access website system select a Item
2. System display information of Item 3. System display Booking Selection 4. User select booking
5. System display Theater Selection 6. User select Theater
7. System display Date Selection 8. User select Date
9. System display Time selection 10. User select Time
11. System display Ticket type selection
Page 42
eProject : Easy Tickets
12. User select ticket type
13. System display Seat selection 14. User select Seat
15. System display Order infomation End Use Case
TrangTV 03/19/2011 Developer Creation date and last modified date
Payment
USE CASE # UC05_06 USE CASE Name
Payment User Payment User login to website system Payment Admin enable function Payment
System Action ACTOR Purpose Preconditions Postconditions in words Trigger Extended Use Cases MAIN SUCCESSFUL SCENARIO
Actor Action 1. User access website system select function Payment 2. Form Payment is display
3. User enter information into form payment 4. Click Button Submit
Step 5. System processing information and then saved to the database Branching Action
OTHER SUCCESSFUL SCENARIOS UNSUCCESSFUL SCENARIOS
Conditions 4a. When you click the button submit,inspection data is invalid Actions Display warning, check information until valid data is transferred to the next step Developer TrangTV
Page 43
eProject : Easy Tickets
03/19/2011 Creation date and last modified date
Function of Guest
Page 44
eProject : Easy Tickets
Review 3
Page 45
eProject : Easy Tickets
Database Structure(Table Details)
Null Key PK
1 . Users Field Name Username Password Fullname Address YearBorn Phone Email Role Status Data Type Varchar(100) No Varchar(100) No Nvarchar(100) No Nvarchar(200) No No Integer Varchar(20) No Varchar(100) No No Integer No Bit Description Stores the Username of Users Stores the Password of Users Stores the Fullname of Users Stores the Address of Users Stores the YearBorn of Users Stores the Phone of Users Stores the Email of Users Stores the Role of Users Stores the Status of Users
PK Stores the ID of Category
2 . Categories Field Name ID CategoryName Status Null Key Description Data Type Integer No Nvarchar(100) No No Bit Stores the Name of Category Stores the Status of Category
PK Stores the ID of City
3 . Citys Field Name ID CityName Status Data Type Null Key Description No Integer Nvarchar(100) No No Bit Stores the Name of City Stores the Status of City
PK Stores the ID of Theater Stores the Name of Theater
FK Stores the ID of Category FK Stores the ID of City
4 . Theaters Field Name ID TheaterName CategoryID CityID SeatTotal Status Null Key Description Data Type No Integer Nvarchar(200) No No Integer No Integer No Integer No Bit Stores the Seat number of Theater Stores Status of Theater
PK Stores the ID of TicketType
5 . TicketTypes Field Name ID TypeName Status Null Key Description Data Type Integer No Nvarchar(200) No No Bit Stores the name of TicketType Stores the Status of TicketType
Page 46
eProject : Easy Tickets
PK Stores the ID of Register PK Stores the ID of Theater PK Stores the ID of TicketType
6 . SeatRegisters Field Name ID TheaterID TicketTypeID StartSeat EndSeat Data Type Integer Integer Integer Integer Integer Null Key Description No No No No No Stores the number start of Register Stores the number end of Register
PK Stores the ID of Schedule FK Stores the ID of Theater FK Stores the ID of Item
7 . Schedules Field Name ID TheaterID ItemID Date Time Status Data Type Integer Integer Integer Datetime Varchar(10) Bit Null Key Description No No No No No No Stores the Date of Schedule Stores the Time of Schedule Stores the Status of Schedule
PK Stores the ID of Price FK Stores the ID of Schedule FK Stores the ID of TicketType
8 . Prices Field Name ID ScheduleID TicketTypeID Price Status Data Type Integer Integer Integer Integer Bit Null Key Description No No No No No Stores the Price of Price Stores the Status of Price
Null Key Description
9 . Cards Field Name Number Pin Fullname Balance Status Data Type Varchar(50) No Varchar(50) No Varchar(100) No No Float No Bit PK Stores the Number of Card Stores the Pin of Card Stores the Fullname of Card Stores the Balance of Card Stores the Status of Card
PK Stores the ID of Item FK Stores the ID of Category
10 . Items Field Name ID CategoryID Title ReleaseDate Runtime Genre Starring Director Null Key Description Data Type No Integer Integer No Nvarchar(200) No Datetime No Nvarchar(50) No Nvarchar(100) No Nvarchar(200) No Nvarchar(200) No Stores the Title of Item Stores the ReleaseDate of Item Stores the Runtime of Item Stores the Genre of Item Stores the Starring of Item Stores the Director of Item
Page 47
eProject : Easy Tickets
Producer Writer Studio Images Trailer Status Nvarchar(200) No Nvarchar(200) No Nvarchar(200) No Varchar(100) No Varchar(100) No No Bit Stores the Producer of Item Stores the Writer of Item Stores the Studio of Item Stores the Image of Item Stores the Trailer of Item Stores the Status of Item
PK Stores the ID of Ticket FK Stores the ID of Prices
11 . Tickets Field Name ID PriceID SeatNumber Status Data Type Integer Integer Integer Bit Null Key Description No No No No Stores the seat number of Ticket Stores the Status of Ticket
PK Stores the ID of Order FK Stores the Username of User FK Stores the Number of Card
12 . Orders Field Name ID Username NumberCard TotalPrice Date Status Null Key Description Data Type Integer No Varchar(100) No Varchar(50) No No Integer No Datetime No Bit Stores the TotalPrice of Order Stores the Date of Order Stores the Status of Order
PK Stores the ID of OrderDetail FK Stores the ID of Order FK Stores the ID of Ticket
13 . OrderDetails Field Name ID OrderID TicketID Amount Status Data Type Integer Integer Integer Integer Bit Null Key Description No No No No No Stores the number of ticket Stores the Status of OrderDetail
PK Stores the ID of Comment FK Stores the Username of User FK Stores the ID of Item
14 . Comments Field Name ID Username ItemID Contents Date Null Key Description Data Type Integer No Varchar(100) No No Integer No Ntext No Datetime Stores the Content of Comment Stores the Date of Comment
PK Stores the ID of FAQS 15 . FAQS Field Name ID Question Null Key Description Data Type Integer No Nvarchar(200) No Stores the Question of FAQS
Page 48
eProject : Easy Tickets
Answer Ntext No Stores the Answer of FAQS
Entity Relationship Diagram (ERD)
Screen Design
Page 49
eProject : Easy Tickets
Task Sheet
Project Ref. No.: Date of Preparation of Activity Plan: Project Title:
Activity Plan Prerare d By: Sr.No. Task Actual Actual T e a m Status
Page 50
eProject : Easy Tickets
1
Start Date Days M e m b e r Names
2 3
Complete
4
03/05/2011 03/05/2011 03/07/2011 03/07/2011 All Member All Member Complete Complete
5
03/05/2011 03/07/2011 All Member Complete
6
7
03/07/2011 03/10/2011 All Member Complete Task Sheet eProject Analysis Problem definition Customer Requirement Specification Database Design Structure Easy Tickets Design 03/07/2011 03/15/2011 Complete
interface Manager Items 03/11/2011 03/20/2011 Complete
8
Manager Schedules 03/11/2011 03/20/2011 Complete
9 10 11 12
Manager User Manager City
13
03/11/2011 03/11/2011 03/15/2011 03/15/2011 03/20/2011 03/15/2011 03/20/2011 03/20/2011 Complete Complete Complete Complete
14 15 16 17 18 19
03/11/2011 03/15/2011 Complete
Manager Theater Manager Ticket Manager Ticket Type Manager order Manager FAQS Manager Comment Manager Prices Report Test 03/20/2011 03/20/2011 03/20/2011 03/23/2011 04/02/2011 04/03/2011 03/23/2011 03/25/2011 03/27/2011 03/28/2011 04/03/2011 04/05/2011 All Member Complete Complete Complete Complete Complete Complete
Page 51
