Escolar Documentos
Profissional Documentos
Cultura Documentos
TMA 01 T471
Fuad AL- Smadi ID 020888
Tarek AL-Soudani ID 020782
2 Introduction -3-
2.1.1 Goals and Objectives -3-
2.1.2 About this project -3-
2.2 System Statement of Scope -4-
2.2.1 General Requirements(functional) -4-
2.2.2 Interface Enhancements -5-
2.3 System Context -5-
2.4 Major Constraints -5-
4 Environmental Modeling -6-
4.1.1 Context Diagram -6-
4.1.2 Event List -7-
4.2 Functional Modeling(The System Basic component(Subsystem) -10-
4.2.2.1 Data Flow Diagram Level 1 -11-
4.2.2.2 Data Flow Diagram Level 2 -12-
4.2.2.3 Data Flow Diagram Level 3 -13-
4.2.3 Data Flow Diagram For Member_login -14-
4.2.4 Process Specification -16-
4.2.4.1 Process Detail For The Member_login -16-
4.2.4.2 Process Detail For The Buy_ticket -19-
4.2.4.3 Process Detail For Other Unnamed Processes -22-
5 Use Case Diagram -26-
5.1 Overview -26-
5.2 Use Case Diagram For Buying Ticket -27-
5.3 Class Diagram -28-
5.3.1Class Diagram For Buying Ticket -28-
5.4 Sequence Diagram -29-
5.4.1Sequence Diagram For Buying Ticket -29-
6 Behavioral Modeling -31-
6.1 State Transition Diagram -31-
7 Data Modeling -33-
7.1 Entity Relationship Diagram -33-
7.2 Scheme -34-
7.3 Data Dictionary -35-
7.3.1 Table In The Database -35-
7.3.2 Each Field (Attribute) In The Database -40-
8 Implementation Modeling -67-
8.1 Structural Chart -67-
9 Appendix -68-
9.1 Mind Map -68-
E-ticket System Analysis and Design Specification3
2 Introduction
The main purpose of our online ticket booking system is to provide another way for the
customer to buy cinema ticket. It is an automatic system. After inserting the data to
database, staff need not to due with the order receive through the system. In fact, there is
similar system on the internet,
The goals of our system are:
In this project, we will illustrate our system by providing DFD, STD on some functions.
And we will also provide some process description and data dictionary. For simply, we
just focus on two processes (Buy_ticket & Member_login) in our project.
E-ticket System Analysis and Design Specification4
1. The web page (e.g. The time table page, the main page) will be generated
automatically according to the data in database.
2. A way in which the customer can create its own account(member registration).
3. A way in which the users (both customer and staff) can login to the system to
perform different operation.
5. A way in which the customer can commit order by just clicking the seat (which
is shown on the screen) and insert some card data.(some simple operation)
6. A way in which the customer can cancel the order and get the refund before
one day from the show.
7. A way in which the customer can check the ticket record according to the
transaction number.
8. A way in which the staff can use the system to add data(e.g. film description) to
the database.
10. The system can generate the time table automatically(by just input the length of
the film) or the time table is set by the staff.(2 operating mode for the staff to
insert data).
11. The system can generate some statistic information according booking and
ticket selling record.
12. Users can check film data by clicking on a certain film on main page(e.g. The
cinema which will show this films).
13. Users can check a cinema data by clicking on a certain cinema on main
page(e.g. which film is now showing)
E-ticket System Analysis and Design Specification5
Our web-based system needs about from (15 to 30) interfaces to handle all the functions.
Staff
One of the main purpose of our system is to reduce the number of staff in the
ticket box. So, most of the job is done by the system automatically. Staff only
need to insert new film data and due with the refund part.
Customer:
• Member:
can be browsing on the Web site and inquire about all the films that will be
presented in theaters and ticket prices and can booking a ticket and purchase it.
Our online E-Ticket Cinema System (ETCS) is a web-based system. The customers can
buy ticket online and cancel the seat at a suitable time. To enhance the refund function,
all the customers have to registration become a member before buying ticket.
Staff can use the system to insert and delete data (e.g. film description , time table) which
will update the webpage(webpage are dynamic page, changing according to the data in
database). Also, staff can check the statistic information from the system.
Data concurrence
Since two or more customers may request for the same seat at the same time. So, the
system needs to remove the chance for two customer get the same seat.
Transaction
We cannot have a real bank account for the transaction. We can just simulate the process.
Time
Lots of the customer will buy tickets in ticket box and the customer use our web-based
system still need to take the ticket in ticket box. So, the online ticket booking service and
refund service will be stopped 1 hour before the show time. To do so, we can reduce the
chance of 2 people book the same seat, also reduce the time for buying a ticket.
E-ticket System Analysis and Design Specification6
Compatibility
The new system need to be compatible with the existing ticket selling system(original) in
the ticket box, because the web-base system and the original system will run on the same
time and use the same database.
Program language:
The Project code will make by Visual basic 2005 (Asp.net) the web site design with
Visual basic tools and the database with MS SQL server 2005.
E-ticket System Analysis and Design Specification7
4 Environmental Modeling
There are three parts in our context diagram; we will deal with a kind of user in a part.
We hope it is more clear to identify the functions of each user.
E-ticket System Analysis and Design Specification8
The following are the events triggered by users. For these events, some output action will
be given by the system.
The dotted line”-- --” represent the function will be further decomposed.
The dotted line”- - -” represent the function has been decomposed from the above level.
We also didn’t show any detail for all obtain processes, cause obtain data just get data
through web page.
END
For the following Diagram, we will show overall view of our system. We just
show the basic function of our system without any detail.
E-ticket System Analysis and Design Specification28
In the following diagram, we will show relation between classes when buying
ticket. The attributes and the functions are also shown.
E-ticket System Analysis and Design Specification30
6 Behavioral Modeling
E-ticket System Analysis and Design Specification32
For the activity Diagram, we just illustrate the state transition of Buy_ticket
process and Member_login process. In the following diagram, we show the process state
step by step.
6.1 activity Diagram Diagram
activity Diagram of Buy_ticket
E-ticket System Analysis and Design Specification33
7 Data Modeling
Our E-ticket system is highly related to the database, most of the fields and variables used
in the webpage will also appear in the database (except some flags and temporary
variables ). So, in our Data Modeling part, we will only concern about the data appear in
the database.
E-ticket System Analysis and Design Specification35
7.2 Scheme:
E-ticket System Analysis and Design Specification36
Range N.A.
E-ticket System Analysis and Design Specification37
Name Record
Range N.A.
E-ticket System Analysis and Design Specification38
Name Staff
Range N.A.
Name Ticket
Range N.A.
E-ticket System Analysis and Design Specification39
Name Sale
Range N.A.
Name Cinema
Range N.A.
E-ticket System Analysis and Design Specification40
Name Movie
Range N.A.
Name Vacancy
Range N.A.
E-ticket System Analysis and Design Specification41
Name Customer_id
Name Customer_name
Name Customer_tel
Range 8 digit
Name Customer_address
Name Customer_email
Name Customer_password
Name Customer_amount
Range 4 digit
E-ticket System Analysis and Design Specification46
Name Customer_creditcard
Range 16 digit
E-ticket System Analysis and Design Specification47
Record table
Name Record_seat
Range 3 char
Name Record_id
Range 20 char
E-ticket System Analysis and Design Specification48
Name Customer_id
Name Sale_id
Range 20 char
Name Ticket_type_id
Range -
E-ticket System Analysis and Design Specification50
Ticket Table
Name Ticket_type_id
Range -
Name Ticket_type_name
Range -
E-ticket System Analysis and Design Specification51
Name Ticket_price
Purpose Save the price of each ticket type(easy to calculate the total
price)
Related/connected From: insert_db
process To: N.A
Related: return_ticket,buy_ticket,check_ticket
Related data A part of: Record
object/item Decomposed into:
Related item:
Record_seat
Record_id
Customer_id
Sale_id
Type Number , an attribute in table
Range -
E-ticket System Analysis and Design Specification52
Sale Table
Name Sale_id
Range 8 char
Name Sale_time
Range [00:00-23:59]
E-ticket System Analysis and Design Specification53
Name Cinema_id
Range 8 char
Name Movie_id
Range 8 char
E-ticket System Analysis and Design Specification54
Vacancy table
Name Sale_id
Range 20 char
Name Vacancy_sold
Range [0-300]
E-ticket System Analysis and Design Specification55
Movie table
Name Movie_id
Range 8 char
E-ticket System Analysis and Design Specification56
Name Movie_name
Name Movie_director
Name Movie_casting
Name Movie_duration
Range [0:00-6:00]
E-ticket System Analysis and Design Specification60
Name Movie_category
Name Movie_language
Cinema Table
Name Cinema_id
Range 8 char
Name Cinema_name
Name Cinema_hall_no
Range 1 char
E-ticket System Analysis and Design Specification65
Staff Table
Name Staff_id
Range 8 char
Name Staff_name
Name Staff_password
Range 8 char
Name Cinema_id
Range 8 char
E-ticket System Analysis and Design Specification67
8 Implementation Modeling
9 Appendix
• Data Dictionary
o Customer
Customer detail
o Record
Each booking ticket record
Keep the booking record, To check the available seat
Record_id Customer_id Sale_id Ticket_type_id Record_seat
o Staff
Keep staff login name and password
Validate the login
Staff_id Staff_password Staff_name Cinema_id
o Ticket
About ticket type and price
To specify the price and type of ticket
Ticket_type_id Ticket_type_name Ticket_price
o Sale
Sale detail about each movie
To keep track of each movie record in each time slot
Sale_id Sale_time Cinema_id Movie_id
o Cinema
Cinema and hall number
Keep record of each hall
Cinema_id Cinema_name Cinema_hall_no
o Movie
Movie detail(not include time table)
o Vacancy
Each show’s vacancy
Keep each show’s ticket selling record
Sale_id Vacancy_sold
• Process Specification
o Member Login
Login process of member
Customer
o Client_check_data
Check data on client side
Customer_id and Customer_password
Boolean (T or F)
Customer
BEGIN IF (Check_empty==TRUE &&Check_range==TRUE) RETURN TRUE ELSE
RETURN FALSE ENDIF END
o Server_check_data
Check data on Server side
Boolean (T or F)
Customer
o Check_range
Check whether the field out of range
Boolean (T or F)
Customer
o Check_existance
Check existence of Customer_id
Customer_id
Boolean (T or F)
Customer
BEGIN IF (Customer_id exist in database) RETURN TRUE ELSE RETURN
FALSE ENDIF END
o Check_concurrence
Check the password obtain from user match the password in database or not(for a
particular user)
Boolean (T or F)
Customer
E-ticket System Analysis and Design Specification70