Expanded 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)

National University of Computer & Emerging

Sciences Islamabad
 Clean & Fair Designs

Table of Contents

Expanded Use Cases:…………………………………………………………………………………………………………………….3

Make Reservation……………………………………………………………………………...3
Make payment…………………………………………………………………………………4
Print Ticket…………………………………………………………………………………….5
View train information………………………………………………………………………...6
Cancel Reservation…………………………………………………………………………….7
Validate User…………………………………………………………………………………..8
Activity Diagrams: ………………………………………………………………………………………………………………………..9

Make Reservation………………………………………………………………………………9
Make payment…………………………………………………………………………………10
Print Ticket…………………………………………………………………………………….11
View train information………………………………………………………………………...12
Cancel Reservation…………………………………………………………………………….13
Validate User…………………………………………………………………………………..14
Meeting Minutes………………………………………………………………………………………………………………………….15
 Clean & Fair Designs

Expanded Use Cases:

Use Case No: 1

Use Case Name: Make Reservation

Define By: Ghazanfar Latif Last Updated By: Ghazanfar Latif

Define On: 19 September 2008 Last Updated On: 26 September 2008

Primary Actors: Traveler

Supporting Actor: Reservation Database System

Related Use Case: Make payment, Print Ticket

Overview: 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.

Priority: High

Triggering Event: Travelers requests train ticket reservation online by login on www.pottrs.com

Pre-Condition(s) The user must login before ticket reservation.

Flow of Events: Actor System

Basic Flow 1. Traveler requests for ticket

reservation.
2. Checks the database connectivity.
3. Traveler clicks on the desired date,
time, seat class and destination. 4. Generates the train and seat availability
request for reservation database system
5. Reservation database system sends
the required information’s.

7. Ok the seat conformation. 6. Send the information to the traveler.

8. Show fare of selected tickets and send

the details to reservation database system.

Alternate Flow: 2* System can not access the reservation database.

4* Traveler can not find out the required seats.
Post Condition(s): Traveler must do payment of the ticket.
 Clean & Fair Designs

Use Case No: 2

Use Case Name: Make payment

Define By: Yasir Arfat Last Updated By: Ghazanfar Latif

Define On: 19 September 2008 Last Updated On: 21 September 2008

Primary Actors: Traveler

Supporting Actor: Payment Authorization Service

Related Use Case: Make Reservation, Print Ticket

Overview: 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.

Priority: High

Triggering Event: Traveler makes reservation and pays the tickets fares by using credit cards.

Pre-Condition(s) The traveler must login before payment.

Flow of Events: Actor System

Basic Flow 1. The traveler communicates their

credit information for ticket payment
through credit card. 2. Generates a credit payment Request and
sends it to an external Credit
Authorization service.

3. Credit Authorization Service

authorizes the payment.
4. Receives a credit approval Reply from
the Credit Authorization Service (CAS).

5. POST (records) the credit payment and

approval reply information to the
reservation database system.

6. Display payment success message.

Alternate Flow: 2* The system can not access the Credit Authorization Service.
3* There will not be required amount in credit card.
Post Condition(s): Ticket required information’s sent to system so traveler can print the ticket.

Use Case No: 3

 Clean & Fair Designs

Use Case Name: Print Ticket

Define By: Yasir Arfat Last Updated By: Ghazanfar Latif

Define On: 19 September 2008 Last Updated On: 21 September 2008

Primary Actors: Traveler

Supporting Actor: Reservation Database System

Related Use Case: Make Reservation

Overview: 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.

Priority: High

Triggering Event: Traveler makes reservation and print the ticket

Pre-Condition(s) Traveler must have the printer availability.

Flow of Events: Actor System

Basic Flow 1. Request for print ticket.

2. Checks the printer connectivity with the

computer.

3. Send ticket to printer to print out the

ticket.
4. Collect the printed ticket which is
useful during the travel.

5. Request to save the ticket into his

computer. 6. Save the ticket in the computer system.

Alternate Flow: 2* Printer can not be properly connected with the system.

Post Condition(s): Traveler must take the ticket with him during the travel.

Use Case No: 4

Use Case Name: View train information

Define By: Suleman Sadiq Last Updated By: Ghazanfar Latif

 Clean & Fair Designs

Define On: 19 September 2008 Last Updated On: 21 September 2008

Primary Actors: Traveler, Administrator

Supporting Actor: Reservation Database System

Related Use Case: Nil

Overview: 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.

Priority: Low

Triggering Event: Traveler checks the train’s information’s online through internet.

Pre-Condition(s) The user must login before payment.

Flow of Events: Actor System

Basic Flow 1. User clicks on the desired trains

info button to view the their
information. 2. Generate a request for required trains
information to the Reservation Database
System.

3. Reservation Database System sends

the required information’s.
4. Show the information’s to the user on
the computer screen.

Alternate Flow: 2* System can not access the reservation database.

Post Condition(s): Nil

Use Case No: 5

Use Case Name: Cancel Reservation

Define By: Suleman Sadiq Last Updated By: Ghazanfar Latif

Define On: 19 September 2008 Last Updated On: 21 September 2008

 Clean & Fair Designs

Primary Actors: Traveler

Supporting Actor: Reservation Database System

Related Use Case: Make Reservation

Overview: Due to some problem, traveler can cancel his ticket with in time limit. He login on
the website. Cancel his reservation if the time limit is not passed over.

Priority: Medium

Triggering Event: Traveler cancels the reservation before some fixed interval.

Pre-Condition(s) The traveler must resave the ticket and must login before cancel reservation.

Flow of Events: Actor System

Basic Flow 1. Traveler login his account for

reserved ticket cancelation.

2. Enter reservation information.

3. Request to delete the record of required

ticket from the database system.
4. Reservation Database System
delete the required ticket record.

5. Transfer the ticket amount to the

traveler credit card account.

Alternate Flow: 4* Time limit for cancel reservation has been passed over.

Post Condition(s): Nil

Use Case No: 6

Use Case Name: Validate User

Define By: Suleman Sadiq Last Updated By: Ghazanfar Latif

Define On: 19 September 2008 Last Updated On: 21 September 2008

Primary Actors: Traveler, Administrator

 Clean & Fair Designs

Supporting Actor: Reservation Database System

Related Use Case: Make Reservations, Update user information’s, Update train’s information’s

Overview: 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.

Priority: High

Triggering Event: Traveler comes open the site and login to reserve ticket.

Pre-Condition(s) Nil

Flow of Events: Actor System

Basic Flow 1. User enters their name and

password.

2. Click to the send login button.

3. Generate request to check the validity
of user and password to reservation
database system.

4. Reservation database system

checks the user validity. 5. Display the user information main
page.

Alternate Flow: 4* Incorrect user name or password.

Post Condition(s): Nil

 Clean & Fair Designs

Activity Diagrams:
1-Make Reservation:

Created By Yasir Arfat

 Clean & Fair Designs

2-Make Payment:

Created By Suleman Sadiq

 Clean & Fair Designs

3-Print Ticket

Created
By Ghazanfar
Latif

4-

Cancel Reservation:
Clean & Fair Designs

Created By Ghazanfar Latif

 Clean & Fair Designs

5-Check User Validity

Created By Ghazanfar Latif

 Clean & Fair Designs

6-Check Train’s Information

Created By Ghazanfar Latif

 Clean & Fair Designs

Meeting Minutes

Venue: F-11/3 Boys Hostel

Start Time: 8:00PM
End Time: 9:30PM
Date: September 11, 2008

Agenda:
 Selection of Use Case Model
 Write Expended Use Case Model
 Create Activity Diagram

Main Points Discussion:

 Ghazanfar suggests, first we should try to select 6 use cases to write in expended format.
 We read the lecture OOAD 14 to understand how to write expended use cases carefully.
 We design a ruff model to write expended use cases.
 Do some practice to make use activity diagram on the paper.
 Make all 6 activity diagrams on the paper.

Work Distribution:
 Assign to write 3 use cases in expended format to Yasir Afrat.
 Assign to write other 3 use cases in expended format to Suleman.
 Ask to document use cases in final required format and to remove errors to Ghazanfar.
 Assign to draw 2 activity diagrams to each.