Use Case Model

ONLINE TRAIN TICKET RESERVATION SYSTEM

A Project of Clean & Fair Designs Pakistan

Submitted To:
Madam Amna Basharat Haider
Submitted By:
Ghazanfar Latif (06-0384_A)
Yasir Arfat
(06-0385_A)
Suleman Sadiq
(06-0192-B)
Actors:
Primary Actors:

 Traveler

 System Administrator

Secondary Actors:

 Payment Authorization Service

 Reservation Database System

Offstage Actors:

 Ministry of Pakistan Railway

Actors Goals List:

Actor Goals

Traveler Process ticket reservation, View trains related

information’s, Process cancel reservation.
System Manage System security, Manage Reservation
Administrator Database, Update train’s information’s, Add
user, Delete user.
Reservation Analyze ticket reservation related data,
Database System Manage data appropriately.
Payment Process Card Validity, Process with draw ticket
Authorization amount, and Transfer to railway account.
Service
Ministry of Checks traveler’s interests,
Pakistan Railway Make decisions on the bases of travelers interests.
High Level Use Cases:

Use case No: 1

Use case Name: View train information
Actors: Traveler, Admin
Priority: Medium
Description: A traveler opens the website www.pottrs.com check the
train information. He checks the train timings, train
routs, train type, general information about Pakistan
railway, public notices etc.

Use case No: 2

Use case Name: Validate User
Actors: Traveler, Admin
Priority: High
Description: Traveler opens the website for reservation of train ticket.
Validate user’s login his account and reserve the required
train ticket. After reservation of ticket they logout their
account.

Use case No: 3

Use case Name: Register
Actors: Traveler, Admin.
Priority: Medium
Description: The user (customer, Adman’s) which is not register must
register to perform their required action. For registration
they fill up the registration form with accurate
information’s and submit it.
Use case No: 4
Use case Name: View user information.
Actors: Traveler, Admin
Priority: Medium
Description: User open website by using internet and login. He checks
his information which is recorded in database. If he want
to change his information, than he can update his
information.

Use case No: 5

Use case Name: Make Reservation
Actors: Traveler
Priority: High
Description: Traveler comes to site and login. He checks the seat
availability at required time, date and root. He also
selects the class of ticket. After fulfilling the
requirements, he reserves the ticket and leaves the site.

Use case No: 6

Use case Name: Make payment

Actors: Traveler, Payment Authorization Service

Priority: High
Description: Traveler arrives and login on website. Reserve his train
ticket. Do Payment by using the credit card. Payment
authorization service checks the card validity and with
draws the fare of the ticket.
Use case No: 7
Use case Name: Print Ticket
Actors: Traveler
Priority: High
Description: Traveler login on the web site and does seat reservation.
Now ticket is ready for print. He prints the ticket which is
used during his journey. He may save his ticket in his
account draft.

Use case No: 8

Use case Name: Cancel Reservation
Actors: Traveler
Priority: High
Description: Due to some problem, traveler can cancel his ticket with
in time limit. He login on the website. Cancel his
reservation if the lime limit is not passed over.

Use case No: 9

Use case Name: Change password
Actors: Traveler, Admin
Priority: Medium
Description: User has to remember his password; he can change his
password at any time. He login on his account and
change his password by setting new password. He logout
and leave.
Use case No: 10
Use case Name: Update Train’s Information
Actors: Admin
Priority: Medium
Description: Administrator has the rights to change the trains’ related
information. He opens his account and goes to trains
information’s. Do required changes and logout his
account.

Assumption made for Choice of System Boundary:

We know that Actors are outside the system and use cases are inside the
system. We define the use cases on the bases of actor’s goals fulfillment and
put them inside the system boundary and all actors are put outside the
system boundary.
Use Case Diagram:
ud POTTRS Use Case M odel

Online T rain T icket Reservation System

M ake Payment

Print Ticket

«include»

Check Seat
Av ailibilty Payment
Trav eller Make Reserv ation «include» Authoraization Serv ice

«include» Check Class

Av ailibilty
«include»
Chech Date
«include» «include» Av ailibilty

Check Time
Cancel
Av ailbilty
Reserv ation

Register

<<Uses>>
Velidate
<<Uses>> Passw ord
Validate User
u d P O TTR S U s...
e Ca

« A c t o r»
R e s e r v a ti o n
Change Passw ord
D a ta b a s e S ys te m

Reserv ation Database

View User Info

«extend»

Update User
View Train's Info Info
Admin

Update Train's Info

 Meeting Minutes (1)
Venue: F-11/3 Boys Hostel
Start Time: 8:20PM
End Time: 9:00PM
Date: September 11, 2008

 Ghazanfar suggests, first we try to define the system boundary.

 We define the system boundary on the bases of proposal report.

 We check the conceptual diagram formed in deliverable 3 and try to find out the Primary Actors
as well as Secondary Actors.

 We make a ruff model of Actor goals.

 We start to find out the use cases names on the bases of Actors and their goals.

 We find out 12 use cases.

 Assign to write high level uses cases into document form to Yasir and Suleman individually.

 Decide to meet again on September 13, 2008 at 4:00PM

 Meeting Minutes (2)
Venue: F-11/3 Boys Hostel
Start Time: 4:40PM
End Time: 6:00PM
Date: September 13, 2008

 We discuss about both “high level use cases” written by Yasir and Suleman.

 Solve the issues faced in writing use cases and make final use case model.

 Do some practice to make use case diagram on the paper.

 Model the use case diagram of “online train ticket reservation system” on paper.

 Make use case diagram in “Enterprise Architect” software.

 Assign to finalize the documentation of use cases and use case diagram to Ghazanfar.
 No Use Case Name Actor

1 View train information Traveler, Admin

2 Validate User Traveler, Admin
3 Register Traveler, Admin
4 View user information Traveler, Admin
5 Make Reservation Traveler
6 Make payment Traveler, Payment Authorization Service
7 Print Ticket Traveler
8 Cancel Reservation Traveler
9 Traveler Traveler, Admin
10 Traveler, Admin Admin
ud POTTRS Use Case Model

Online T rain Ticket Reservation System

Make Payment

Print Ticket

«include»

Check Seat
Av ailibilty Payment
Trav eller Make Reserv ation «include» Authoraization Serv ice

«include» Check Class

Av ailibilty
«include»
Chech Date
«include» «include» Av ailibilty

Check Time
Cancel
Av ailbilty
Reserv ation

Register

<<Uses>>
Velidate
<<Uses>> Passw ord u d P O TTR S U s. e.. C a
Validate User

« A c t o r»
R e s e r v a ti o n
D a ta b a s e S ys te m
Change Passw ord

View User Info

«extend»

Update User
View Train's Info Info
Admin

Update Train's Info