Electronic Ticket System

8/3/2019 Electronic Ticket System

1/29

King Saud UniversityCollege of Computer and Information Sciences

Department of Information Systems

----------------------------------------------------------------------------------------------------------------------------

E-Ticket System

----------------------------------------------------------------------------------------------------------------------------

-Student Name-

Mahdi alqarni427104683

Mohammed alqarni427104683

Abdulhameed alateeq

426105248----------------------------------------------------------------------------------------------------------------------------

Supervisor: MR. Mohammed KhanIS496 Report

1431/1432H (2019 / 2011 G(


2/29

Table of ContentsAbstract page

1. Planning

1.1Introduction

1.2 Background1.3 Literature Survey1.4 Problem Statement1.5 Project Schedule

2. Project Requirements

2.1 UML overview2.2 Use Case Diagram2.3 Sequence Diagram

2.4 Class Diagram3. Project Design

OverviewER DiagramData Dictionary

4. Implementation

4.1 Sample Code

4.2 System ScreensSummary

Conclusion

Future Work

References


3/29

.

.

.

.

Abstract

This project aims to launch information portal on the Internet to Reserve

Tickets for a Stadium, which is needed to watch events and football

matches in the stadium.

This project involves an important part of the business, which is the E -

Ticketing, An electronic ticket is used to represent the purchase of a seat

in the stadium through the website. Once a reservation is made, an e-

ticket exists only as a digital record in the stadium computers. Customers

would print out a copy of their receipt which contains the reservation

number and the e-ticket number and used it to login the stadium.


4/29

Chapter 1 : INTRODUCTION


5/29

1.1 Introduction

E - Ticketing, an electronic ticket is used to represent the purchase of a

seat in the stadium through the website, which is the once a reservation ismade, an e-ticket exists only as a digital record in the stadium computers.

Customers would print out a copy of their receipt which contains the

reservation number and the e-ticket number and used it to login the

stadium.

This project aims to launch information portal on the internet to reserve

tickets for stadium, which is needed to watch football matches in thestadium.

1.2 Problem Definition:

Limit the definition of the problem on several points:

There is no effective system to provide ticket reservations to

customers online.

A difficult to have detailed information about the vacancy

seats and their class or location in the stadium.

Therefore, this project came to solve all these problems and reduce thetime and effort to the stadium staff in access to all ticket sales with

customers.


6/29

1.3 System requirements:

From the view point of end user, our project should

provide the following functions:

o Registration : The main objective of this

function is to create an account for the customer.

o Log in : Every user must have a username and a

password to log in the system, if the user insert his

username and password the system will check it , if it

is correct then he will be logged.

o Update Class: The main objective of this

function is to allow the administrator to update class

information he added in the website.

o Display Reservations: The main objective of

this function is to allow the administrator to view the

reservations the customers make.

o View Classes: The main objective of this

function is to view the Classes information by the

customer before he makes reservation.


7/29

o Make Reservations: The main objective of

this function is to allow the customer to select seat

and request to reserve it.

o Payment: The main objective of this function

is to allow the customer to pay the costs of the

reservation.


8/29

1.4 Project Scope

The solution is developing a website that allows the reservation of e-tickets online.

The customer can use the web site to view matches in the stadium. Then

the customer can select seat and pay the costs for his ticket online by

credit cart.

When the customer chooses the payment method the information of it

will go to a system to check the validity. If it is valid, adjusts the

customer balance and give the customer a confirmation number of the

process and display a copy of the ticket to print.


9/29

Chapter 2 : ANALYSIS


10/29

2.1 Overview

In our project we will use the UML to model our system. We will modelthe data ER diagram and will model the activities using use cases and

sequence diagram.

2.2 UML Overview

The Unified Modeling Language (UML) is a started language for

specifying, visualizing, constructing, and documenting the artifacts of thesoftware systems, as well as for business modeling and other non-

software systems. The UML represents a collection of the best

engineering practices that have proven successful in the modeling of large

and complex systems. The UML is very important part of developing

object oriented software and software development process. The UML

uses mostly graphical notations to express the design of software projects.

2.2.1 Use case Diagram

A use case is a set of scenarios that describing an interaction between a

user and a system. A use case diagram displays the relationships among

actors and use cases. The two main components of a use case diagram are

use cases and actors. An actor is represents a user or another system that

will interact with the system you are modeling. A use case is a external

view of the system that represents some action the user might perform in

order to complete a task.


11/29

2.2.2Use Case Diagram:

Customer

Login

Administrator

Register

View Customers

extends

Print Ticket

Update Event

Payment

Make Reservation

View Reservations

Add Event

View Events

FIGURE 1: USECASE DIAGRAM


12/29

2.3 Scenarios:

Scenarios:

1. Use Case Name: Login

Actor: Customer, Administrator

Purpose: the user must log in to enter the system.

Precondition: The customer and admin users should have an

account in the system.

Scenario:

1. The user fills login information.

2. The system checks this input.

3. The system gives an authorization to enter on the system or

show an error message.

2. Use Case Name: Register

Actor: Customer

Purpose: To use specific system services.

Precondition: The customer user should open the website and select to

register in the website.

Scenario:1. The customer Fill the registration form information.

2. The system checks this input.

3. The system gives a confirmation or tells the user to refill wrong

information.

4. The system Create customer Account


13/29

3. Use Case Name: View Events

Actor: Customer

Purpose: To view the available events in the stadium.

Precondition: The customer user should login in the website

and select to view the available events.

Scenario:

1. The Customer Open Events window and Choose event.

2. The system displays available information for this event.

3. Show available information.

4. Use Case Name: Make Reservation

Actor: Customer

Purpose: To select seat and request to reserve it.


and select Class.

Scenario:

1. The Customer Open Reservation window and Choose Seat.

2. The system displays costs for this seat.

3. Show confirmation.


14/29

5. Use Case Name: Payment

Actor: Customer

Purpose: To pay the reservation costs for the ticket.


and selected seat.

Scenario:

1. The Customer Open Payment window and Review Cost.

2. The system displays costs to pay.

3. The customer enters credit card information.

3. The system gives a confirmation or tells the user to refill

wrong information.

6. Use Case Name: Add EventActor: Administrator

Purpose: To add new event information.

Precondition: The customer user should login in the website.

Scenario:

1. The User Open Add Event window.

3. The user adds event information.

3. The system saves the updated information or gives an error

message.

7. Use Case Name: View Customers

Actor: Administrator


15/29

Purpose: To view the customer's information.

Precondition: The Admin user should login in the website.

Scenario:

1. The Administrator Open View Customers window.

2. The system displays the customer's information.

3. Show Customer's information.

8. Use Case Name: Update Event


Purpose: To update event information.

Precondition: The Admin user should login in the website and

select event.

Scenario:

1. The Administrator Open Update Event window.

2. The system displays the event information.

3. The Administrator updates the event information.

4. The system saves the updated information or gives an error

message.

9. Use Case Name: View Reservations


Purpose: To view the reservations information.

Precondition: The Admin user should login in the website.


16/29

Scenario:

1. The Administrator Open View Reservation window.

2. The system displays the Reservation information.

3. Show Reservation information.

10. Use Case Name: Print Ticket

Actor: Customer

Purpose: To print the ticket.Precondition: The customer user should login in the website

and reserve ticket.

Scenario:

1. The Customer Open Ticket window.

2. The system displays ticket information.

3. The customer could print a copy of the ticket.


17/29

Chapter 3 : DESIGN


18/29

2 .4 Sequence Diagram

Loginwindow : System

Login (Username ,Password )

Successfull Login ()

Admin /Customer

Or Error Message ()

Figure (1): Login Sequence diagram.


19/29


20/29

Makereservation : aReservation

CustomerMakerereservation ()

ReservationInfo ()

: aReservationDA

Makerereservation ()

ReservationInfo ()

Figure (): Sequence diagram shows the make reservation operation.


21/29

Payment Window : PaymentDA

MakePayment ()

Customer

: aPayment

Payment Confirmation ()

Payment Confirmation ()

Figure (): Sequence diagram shows the Payment operation.


22/29

Print Ticket Window : TicketDA

Print Ticket ()

Customer

: aTicket

PrintedTicket ()

PrintedTicket ()

Figure (): Sequence diagram shows the Print Ticket operation.


23/29

ViewReservationWindow : ReservationDA

Viewreservations (Date )

Reservationsinformation ()

Administrator

Figure (): Sequence diagram shows the View reservations operation.


24/29

AddEvent Window : EventDA

AddEvent ()Administrator

:aEvent

Confirmation ()

Confirmation ()

AddEvent ()

Figure (): Sequence diagram shows the Add Event operation.


25/29

UpdateEvent Window : EventDA

UpdateEvent ()

Administrator

:aEvent

Confirmation ()

Confirmation ()

UpdateEvent ()

Figure (): Sequence diagram shows the Update Event operation.


26/29

ViewCustomersWindow : UserDA

ViewCustomers ()

Customersinformation ()

Admin

Figure (): Sequence diagram shows the View Customers operation.


27/29

3.2 Class Diagram

+AddITicket()

+CalculateTotal()

Reservation

-ID

-Date

-SeatsNo

-State

-Location

+Login()

Person

-Firstname-LastName

-email

-Username

-Password

+GenerateReports()

+DisplayReservations()

+ViewComments()

Administrator

+Register()

+MakeReservation()

+SendComment()

Customer

-Address

-City

1

0..*

Ticket

-TicketID-Location

-SeatNo

Class

-ClassId-Title

-Capacity

-Cost

0..1

1..*

10..*

1

0..*

+AddChampion()+UpdateChampion()

+DeleteChampion()

Champion

-Id

-Title

+AddEvent()+UpdateEvent()

+DeleteEvent()

Event

-Id-Title

-Date

-Time

0..1

1..*

0..1

1..*

Comment

-Commentid

-Title

-Date

-CommentTxt

1

0..*

FIGURE 3.2: CLASS DIAGRAM


28/29

3.3 ER Diagram

Ticket

TicketNOLocation

Reservation

ReservationID

ReservationDateSeatsNoState

Customer

CustomerIDNamePhoneCityAddressEmailUserNamePassword

Class

ClassID

TitleCostCapacity

Bill

BillNODateAmountPaymentMethod

Bill Line

Event

EvendID

EventNameDateTime

Champion

ChampionIDTitle

CommentCommentIDDateNameEmailCommentTxt

Fig () ER Diagram


29/29

References:

1. "Modern Systems Analysis and Design": Jeffery A. Hoffer; The

Benjamin/Cummings Publishing Company, Inc. 2002, Second

edition.

2. http://www.uml.org

3. Object Oriented Analysis and Design Using

the UML

Electronic Ticket System

Documents

Transcript of Electronic Ticket System