E-ticket System

Document Sample
E-ticket System Powered By Docstoc
					           E-ticket System Object-Oriented Analysis & Design with UML
                                          Group 3 Lai Chi Wa 03011674
                                          Chung Wang Leong 03011615
                E-ticket System

Object-Oriented Analysis & Design with Unified
             Modeling Language




                           by




                 Lai Chi Wa
                  03011674
              Chung Wang Leong
                  03011615
               Group Number: 3




                COMP 2221
          Lecturer: Prof. Jiming Liu
             December 4 , 2004


                                                                 -1-
                    E-ticket System Object-Oriented Analysis & Design with UML
                                                   Group 3 Lai Chi Wa 03011674
                                                   Chung Wang Leong 03011615
Table of Contexts

0 Notation                                                                 -3-
  0.1 Notation of Use Case Diagram                                         -3-
  0.2 Notation of Class Diagram                                            -4-
  0.3 Notation of Sequence Diagram                                         -5-
1 Introduction                                                             -6-
  1.1. Goals and Objectives                                                -6-
    1.1.1 Goals and Objectives                                             -6-
    1.1.2 About this project                                               -6-
  1.2 System Statement of Scope                                            -7-
    1.2.1 General Requirements(functional)                                 -7-
    1.2.2 Interface Enhancements                                           -8-
  1.3 System Context                                                       -8-
  1.4 Major Constraints                                                    -8-
2 Use case diagram                                                         -9-
  2.1 Overview                                                             -9-
  2.2 Use case diagram for buying ticket                                  -10-
3 Class diagram                                                           -11-
  3.1 Class diagram for buying ticket                                     -11-
4 Sequence diagram                                                        -12-
  4.1 Sequencediagram for buying ticket                                   -13-




                                                                          -2-
                    E-ticket System Object-Oriented Analysis & Design with UML
                                                   Group 3 Lai Chi Wa 03011674
                                                   Chung Wang Leong 03011615
0.0 Notation

0.1 Notation of Use Case Diagram




                                    The user of the system

        User



      Use Case                     The use case of the system




     System
                                     The system boundary




                             The generalization of each use case



                            The relationship between two use cases



                                   The communication between
                                    the user and the use case
                         Figure 5.1




                                                                          -3-
                       E-ticket System Object-Oriented Analysis & Design with UML
                                                      Group 3 Lai Chi Wa 03011674
                                                      Chung Wang Leong 03011615

0.2 Notation of Class Diagram


       ClassName
    -Attribute                              The structure of a class
    +Operation()



                                         The aggregation (containing)
                                            between two classes

      1            1
                                         The aggregation (composition)
                                             between two classes


                                     The aggregation (dependency)
                                         between two classes


                                         The relationship (association)
                                             between two classes
                            Figure 5.2




                                                                             -4-
                    E-ticket System Object-Oriented Analysis & Design with UML
                                                   Group 3 Lai Chi Wa 03011674
                                                   Chung Wang Leong 03011615

0.3 Notation of Sequence Diagram




                            Figure 5.3




                                                                          -5-
                       E-ticket System Object-Oriented Analysis & Design with UML
                                                      Group 3 Lai Chi Wa 03011674
                                                      Chung Wang Leong 03011615
1 Introduction

1.1 Goals and Objectives

1.1.1 Goals and Objectives

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, but there is no refund method found in the
existing system. The goals of our system are:

1   To provide a anytime anyplace service for the customer
2   To provide refund which is not available in the existing system
3   To minimize the number of staff at the ticket box
4   To promote the film on the internet
5   To increase the profit
6   To obtain statistic information from the booking record.

1.1.2 About this project

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.




                                                                                 -6-
                    E-ticket System Object-Oriented Analysis & Design with UML
                                                   Group 3 Lai Chi Wa 03011674
                                                   Chung Wang Leong 03011615
1.2 System Statement of Scope

1.2.1 General Requirements(functional)

    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.

    4.   A way in which the customer can modify its own data.

    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.

    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.

    9.   The system can verify the data before transaction.

    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)




                                                                                  -7-
                     E-ticket System Object-Oriented Analysis & Design with UML
                                                    Group 3 Lai Chi Wa 03011674
                                                    Chung Wang Leong 03011615
1.2.2 Interface Enhancements

Our web-based system needs about 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
          To make the system more user-friendly, customer need not to enter lots of
          data. An order will be commit step by step with guideline (request about 7
          webpage for an order).




1.3 System Context

Our online E-Ticket System (ETS) is a web-based system. The customers can buy
ticket online and cancel the seat at a suitable time (2 days before the show to 1hour
before the show). 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.


1.4 Major Constraints

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.

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.



                                                                                   -8-
                      E-ticket System Object-Oriented Analysis & Design with UML
                                                     Group 3 Lai Chi Wa 03011674
                                                     Chung Wang Leong 03011615
2 Use case diagram
  2.1 Overview

       For the following Diagram, we will show overall view of our system. We just
show the basic function of our system without any detail.




                                                                               -9-
                    E-ticket System Object-Oriented Analysis & Design with UML
                                                   Group 3 Lai Chi Wa 03011674
                                                   Chung Wang Leong 03011615
2.2 Use case diagram for buying ticket

        In the following diagram, a sequence of buying ticket will be shown. Some
alternative choice are also shown in the diagram.




                                                                               - 10 -
                      E-ticket System Object-Oriented Analysis & Design with UML
                                                     Group 3 Lai Chi Wa 03011674
                                                     Chung Wang Leong 03011615

3 Class diagram
  3.1 Class diagram for buying ticket

        In the following diagram, we will show relation between classes when buying
ticket. The attributes and the functions are also shown.




                                                                              - 11 -
                       E-ticket System Object-Oriented Analysis & Design with UML
                                                      Group 3 Lai Chi Wa 03011674
                                                      Chung Wang Leong 03011615
4 Sequence diagram
  4.1 Sequence diagram for buying ticket

       In the following diagram, a sequence of buying ticket are demonstrated . There
is some more things I need to state, this is just one of the sequences of buying ticket.
There are some more alternative sequence for buying ticket. For example, we can
choice cinema before choice movie. But the overall structures of all buying ticket
sequence are similar, so, others sequence will not be shown.




                                                                                  - 12 -
E-ticket System Object-Oriented Analysis & Design with UML
                               Group 3 Lai Chi Wa 03011674
                               Chung Wang Leong 03011615




                                                     - 13 -