PAKISTAN 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
 ONLINE TICKET RESERVATION SYSTEM

Introduction:
A passenger who wishes to travel by train must book the tickets. In order to do so he
has to go to the railway station to book the tickets. The booking authority checks the
availability of seats and books the tickets if available. This process is tedious. Online ticket
reservation system is one which enables the passenger who wishes to travel book his tickets
via internet. This helps him to reduce the time delays by waiting in queues while booking the
tickets. He can also view the current booking status and the availability of tickets for
reservation. In olden days all the registration details were maintained in files which were very
tedious to maintain. It also occupies a lot of space. Also updating the files was very difficult.
All these problems can be easily eliminated by the use of the software. Thus software is
implemented in booking of tickets.

Objectives:

In the case of ticket reservation software for railway system we need to get the
passenger details and train details. After this the system specifies the availability of tickets by
checking the details relevant to the particular train or the number of tickets required by the
passenger. If there is a vacancy it books the tickets otherwise it displays that there are no seats
available for reservation. For this we have to store the necessary details of the train such as
the number of seats available, date and time of travel as certain trains travel only on particular
days. Once all this is done booking becomes easy. Also if the software is made available
online then the person who wishes to travel can check the necessary details online and make a
reservation suitably. This is the main objective in online ticket reservation.

Scope:

 Online ticket reservation system supports various features. Some of them are as
follows:
 Updating of seats become easier.
 Online booking of tickets is possible.
 Errors while entering the details can be minimized.
 Current status can be viewed.
 Cancellation can be made.
 It saves both time and energy.
Problem Statement and Description:

This system is designed for the online reservation of railway tickets for travel
between any destinations which is a part of Pakistan Railway network. This system enables
the Advance booking in any class, against general and ladies quota, on payment of fare in
full for adults and children, a maximum of six berths/seats at a time, for journey between any
two stations served by a train.
It also provides details about
1. Time table
2. Train fares
3. Current status of reservation position
4. Train available between a pair of stations
5. Accommodation available for a train/date combination

The user of this system should first register for any interaction with the system. Once
registered, he/she will be provided with a username and password for the user to log in. After
logging in the user should select the kind of activity he would like to perform like booking a
ticket, canceling a ticket, look out for help and so on. A person can check the train timings,
train fares and other trains information without login.
If he selects the booking the ticket option, then he/she should select the ‘to and from’
stations. After this step the user should select a particular train that runs between the specified
stations from a list of trains that is provided by the system. Once a particular train is selected,
the user should specify the class of travel and date of journey. Then he can view the vacancy
position in that train for that date. Depending upon the vacancy position, the user can proceed
to book his tickets. For reserving the ticket, the user should fill up the reservation form with
the details like name, age, sex, class of travel, preferred seats/berths and others. After filling
up this form, the user should submit this for reservation.
Then the mode of payment is selected and the user fills up the corresponding details.
Once these processes are over, the system automatically reserves the ticket for the user and it
deliver by post (TCS). The ticket number and PNR number details would be remembered to
the user for future reference. Thus the Online Train Ticket has been booked.
 Meeting Minutes(1)

Venue: F-11/3 Boys Hostel

Start Time: 4:20PM

End Time: 6:30PM

Date: August 15, 2008

 Yasir suggest to develop such a software which we can use in real life.
 We meet with our hostel fellows which more than 50 students of Telecom Engineering
and computer science to ask about some project names.
 They told us about a number of projects like hostel management system, chess game,
online ticket reservation system, car sales and services system, iPod running software.
 We select online ticket reservation system for Pakistan Railway.
 We discuss about problems of ticket reservation, then how can we solve these
problems.
 Ghazanfar finalize the document.
 Customer Visit

POTRS Site Train Timings

Goe Check
Chec
Booking Train Details
Typ Train Roots
Chec

Login To Register Check

To Seat Signup
Train Name

Cancelation Check

Check

Trains
Reserved To

Ticket Info
Check Available
Fares Seats Check

Class

Payment by Done

Done
Credit Card

To

Check
Ticket Reserved Congratulation
Done

Card Validity
 Ready to

Print Logout

Conceptual Model
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.

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

Change Passw ord

Reserv
ud POTTRSation Database
Use Ca
. ..

«Actor»
Re serv ation
Da tabase System
View User Info

«extend»

Update User
View Train's Info Info
Admin

Update Train's Info

Use Case Diagram

 Meeting Minutes (2)

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 (3)

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.
Use Case No: 1

Use Case Make Reservation

Name:

Primary Actors: Traveler

Supporting Reservation Database System

Actor:

Related Use Make payment, Print Ticket

Case:

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 Travelers requests train ticket reservation online by login on www.pottrs.com

Event:

Pre- The user must login before ticket reservation.

Condition(s)

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 Traveler must do payment of the ticket.
Condition(s):
Use Case No: 2

Use Case Make payment

Name:

Primary Actors: Traveler

Supporting Payment Authorization Service

Actor:

Related Use Make Reservation, Print Ticket

Case:

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 Traveler makes reservation and pays the tickets fares by using credit cards.
Event:

Pre- The traveler must login before payment.

Condition(s)

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 Ticket required information’s sent to system so traveler can print the ticket.
Condition(s):
Use Case No: 3

Use Case Print Ticket

Name:

Primary Actors: Traveler

Supporting Reservation Database System

Actor:

Related Use Make Reservation

Case:

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 Traveler makes reservation and print the ticket

Event:

Pre- Traveler must have the printer availability.

Condition(s)

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 Traveler must take the ticket with him during the travel.
Condition(s):
Use Case No: 4

Use Case View train information

Name:

Primary Actors: Traveler, Administrator

Supporting Reservation Database System

Actor:

Related Use Nil

Case:

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 Traveler checks the train’s information’s online through internet.

Event:

Pre- The user must login before payment.

Condition(s)

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 Nil
Condition(s):
Use Case No: 5

Use Case Cancel Reservation

Name:

Primary Actors: Traveler

Supporting Reservation Database System

Actor:

Related Use Make Reservation

Case:

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 Traveler cancels the reservation before some fixed interval.

Event:

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

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

4. Reservation Database System required ticket from the database

delete the required ticket record. system.

5. Transfer the ticket amount to the

traveler credit card account.

Alternate Flow: 4* Time limit for cancel reservation has been passed over.
Post Nil
Condition(s):
Use Case No: 6

Use Case Validate User

Name:

Primary Actors: Traveler, Administrator

Supporting Reservation Database System

Actor:

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

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 Traveler comes open the site and login to reserve ticket.
Event:

Pre- Nil
Condition(s)

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 Nil
Condition(s):
1-Make Reservation:

Created By Yasir Arfat

2-Make Payment:
 Created By Suleman Sadiq

3-Print Ticket
 Created By Ghazanfar
Latif

4-

Cancel Reservation:
Created By Ghazanfar Latif
5-

Check User Validity

 Created By Ghazanfar Latif

6-Check Train’s Information

Created By Ghazanfar Latif

 Meeting Minutes (4)

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 Arfat.
 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.
Purpose of Document:

The purpose of this document is to decompose the domain of the project. During this
decomposition concept, attributes and association were identified. This helped us in better
understanding of the whole problem domain.

Identify Conceptual Classes by Category List:

No Conceptual Class Category Classes

1 Business Transactions  Reservations

 Cancelation
 Payments/ Credit
Card
 Print
2 Roles of People or Organizations  Store
related to the transaction  Traveler
 Credit Card check
 Admin
3 Descriptions of Things  Reserved Ticket info
 Train Details
 User Info
4 Where is the Transaction Recorded?  Register/ Sign Up
 Login
 Sign out
5 Place of Service  Class of Seat
 Fares

Assumption Made for Development of Domain Model:

Domain model is start from top and goes downward depending on the attributes of the
classes. It will goes from top to bottom and left to right. The associations are made between
different classes by checking their relationships.
cd POTTRS Domain Model

1 1
Admin
Trav eler
Checks

1..*
1
1..* 1..*
Goes to Start with 1..*
Online Users
Make 1..* - Name:
Register - Age:
1..* 1 Signin - Sex:
- Login Name:
- User Name: - User Name:
- Password: - Password:
- Sex: Can Perform
- Date of Birth: Initiate 1
Checks Check

1
Reserv ation LogOut
1 User Detais
+ Train Name:
- User Name:
- Root:
- Address:
- Time:
- Date of Birth:
- Class: Checks
- Booth No: - Sex: 1
1
- Quota:
- Seat No:
Update Train Details
1
1 Can - Upadate Train Timing:
Pay Perform
T icket
Fares 1..* 1..*
1
Train Details
Payment 1..*
- Train Roots:
- Train T imings: Update User Details

1
Done By

Credit Card

- Balance: Veldity
1 Checked by

Payment Autorization Serv ice

1
Preform
Reservation

Check

Fares Dedection
1
- Ticket Amount:
- Tax:
Then Create
Resev ationSlip
1
1 1

Cancellution 1 1

- Ticket Number:
Save Store
Print 1 -
T ake Location:
1..*

Domain Model Diagram

 Meeting Minutes (5)

Venue: F-11/3 Hostel

Start Time: 1:00PM
End Time: 2:10PM
Date: October 5, 2008

Agenda:
 Selection Conceptual Classes
 Identifying Concepts and attributes
 Draw Domain Model Diagram

Main Points Discussion:

○ We read the lecture 16, 17 carefully to understand initial concepts of domain model.
○ Find out the concepts and attributes of project by using conceptual diagram and expended
use case.
○ Do some practice to make use domain model diagram on the paper.
○ Finalize the domain model diagrams on the paper.

Work Distribution:
 Assign to draw Domain Model diagram in Enterprise Architect 6.5 to Ghazanfar.
 Ask to document Conceptual Classes by Category List.
 Assign to write minutes of that meeting to Yasir Afrat.
SSD1 Make Reservation:
 S
SD2 Make Payment:
SSD3 Print Ticket:
SSD3 Cancel Reservation:
SSD5 Validate User:
 Contract No 1
Name: EnterBookingRequirements (Destination: String, Source: String,
date: Date, class: String)

Responsibility: Keep all the records like seat no, class, date, source and
destination information.

Type: System

Cross Reference: Function 3

Use case: Make Reservation.

Note: Use good database.

Exception: Show the error if any requirement is missing.

Output: Process is completed.

Precondition: The user must login before ticket reservation.

Post condition:  Booking requirements was created.

 Booking information was saved in database.
 System generated the instance of ticket.
 Contract No 2
Name: BookTicket (T_Name: String, Gander: String, Age:
Number, Seat/BirthNo: Number)

Responsibility: Saves the Traveler Name, his Gander, Age, Number/ Birth no.

Type: System

Cross Reference: Function 5

Use case: Make Reservation.

Note: Use good database.

Exception: Generate error if any information is missing.

Output: --

Precondition: Traveler must select the related train.

Post condition:  Ticket slip was created.

 Ticket was also saved in the passenger account indox .

 Contract No 3
Name: TicketFare (TicketAmount: Number or Quantity, ServiceCharges:
Number or Quantity)

Responsibility: Calculate the ticket fare.

Type: System

Cross Reference: Function 1

Use case: Make Payment

Note: Use the good data base.

Exception: --

Output: Show the ticket fares on screen.

Precondition: Complete reservation process before payment.

Post condition:  Ticket fare was calculated.

 Amount was transferred to railway account.
 Contract No 4
Name: CreditCardDetils (AccountID: Number, Owner_Name: String)

Responsibility: Check the Credit Card information.

Type: User

Cross Reference: Function 3

Use case: Make Payment

Note: --

Exception: Authorization agency checks card validity.

If Credit Card is not valid generate an error.

Output: Show credit card ok message.

Precondition: Complete reservation process before payment.

Post condition:  Ticket fare was paid.

 Fare was transferred to railway account.
 Remaining balance was transferred to user account.
 Meeting Minutes (6)

Venue: F-11/3 Hostel

Start Time: 8:00PM
End Time: 9:30PM
Date: November 5, 2008

Agenda:
 Draw five main System Sequence Diagrams
 Draw their important contracts related to SSD’s.

Meeting Main Points:

○ We read the book chapter 17 carefully to understand initial concepts of how to draw
system sequence diagrams.
○ Draw the system sequence diagrams on the paper.
○ We do some practice of how to draw system sequence diagram in Visio and EA.
○ Find out the most important contracts of selected system sequence diagrams.

Work Distribution:
 Assign to draw main System Sequence Diagrams to Yasir in Microsoft Office Visio 2007.
 Assign to write their contracts to Suleman.
 Assign to compile the complete document file to Ghazanfar.
SD1 Make Reservation:
SD2 Make Payment:
SSD3 Register New User:

Registeration

Traveler

:Register
MakeRegiseration ()
:DataSelect

EnterUserDetails (Id,Name ,Pass,Add)

EnterUserDetails (Id,Name,Pass ,Add)

SSD3 Cancel Reservation:

SSD5 Validate User:
CD-1 Ticket Reservation

od Business Process Model

Enter the reservation detail(D_station 2:[TrainAvailable] create()

A_station Date, Class)
:TicketReserv ation
_________________________________________ :BookTicket

1:T:=Show(traininfo) If the trains are available for the

required destination then It create the
new object for ticket reservation.

:TrainInfo

get the info of available

train for reservation from
the SelectData Class

CD-2 Passenger Details for Reservation:

od Ticket Reserv ation

By creator
If the trains are available for
required destination then
enter the passanger details

EnterPDetail(name,seatno,class,trainID,Date)
_________________________ 3:[new] Create()
:Ticket reserv ation g:insertData

1:seatno:=convert(seatno) 3.1:insertpdetail()
2:TrainId:=convert(TrainId)

Message for insert passenger

By controller informantion in to the data
Message to check that base through InsertPDetails
the trains are avail able
or not...
:DataSelect :InsertPDetail
CD-3 Validity for Cancel Reservation:
o d B us in e s s P ro c e s s M ode l

C a n ce lR e se rva ti o n ()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _:C
_ _a n c e la tio n 1 :cre a te () 1 .2 C re a te ()
:U s e rIn fo :M a k e C a nc e l

It w i l l cre a te th e o b j e c t
o f U se ri n fo Fo r l o g i n
b e fo re ca n ce l
re srva ti o o n
1 .1 :In fo := fi n d (i d ,n a m e )
If th e p ro v id e d i n fo rm a ti o n
a re co rre ct th e n i t w il l cre a te
th e o b j e c t o f m a ke ca n c e l
a n d g o e s to n e xt ste p .
T o v a l i d a te th e u se r i t w i ll
S e le c tD a ta
g o e s to se l e c t cl a ss to g e t
u se ri n fo fro m th e d a ta b a se
fo r co m p a ri sio n

CD-4 Reservation
od Communication

2 Cancel Reservation(Ticket id,seat num)

2:PDetails(PName,TId,Source,Destination)
_______________________________________ :Cancelation :Remov e Info

1:TicketInfoSelect(TId,Date) DeleteTDetails(TID)
If the provided information
are correct and date is not
expired then it will create the
object Remeove info.
User insert the ticket info
to check that ticket is
booked are not
:DataSelect :UpdateData

Go tho the update data and

delete the book ticket
information update the
database
CD-5 Register New User
cd Communication

registerUser()
:Register 1:NewUserInfo(ID,Name,Pass,Age,Add) :UserInfo
_________________

1.1 InsertNewUserInfo(ID,Name,Pass,Age,Add)

Message sent by controller

It is used to get new user Store the New User
info Informations into the
:InsertData database by calling the
InsertData
cd POTTRS Class Diagram

Traveler
Admin
- ----: 1
- ---:
1..*
+ ----()
1 + ---()
1..* 1..* 1
Make 1
1..*
Can Perform
Goes to
Register Check

- DOB: int
- ID: char 1
1..* 1
- Name: char
- Pass: char Update Train Details
- Sex: char User Detais
Initiate - Distance: int
- Address: char - Source: char
+ RegrNewUser(ID,Pass,Name,PNo,Sex,DOB)() : void - DOB: char - T_Time: int
1 - Name: char - TID: char
- Sex: char
Checks
+ UpdateT_timings(TID,Time)() : void
+ CheckUserDetails() : void
Reservation Checks 1
1 1
Can
- Date: int
Perform
- Desti: char
1..*
+ Source: char
- TrainID: int
UpdateUserDetails
+ CheckAvailableTrsins(Source,Dest)() : void - :
1..* 1..*
+ UpdateUDetails(ID,Pass)() : void
1
Enters the Train Details
1
1 - Source: char
Find
- TID: int
PDetails - TTimings: int
Pay Ticket
- Class: char Fares + ViewTDetails() : void Stores
- PName: char
- TicketNo: int 1
1 1..*
- TrainID: int 1 Update
Payment
+ EnterPDetails() : void
- ...:
1 1 1
1 Get
+ MakePayment() : void
POTTRSDataSelect
Done By 1 1
1 0..*

Credit Card 1
Preform
- Balance: int 1 1..*
Reservation

+ EnterCDInfo() : void Update Connect

1 1
Veldity 1..*
Cancellution Checked by
Stores POTTRSDBAccess
1
- Ticket Number: 1
PaymentAutorizationService
+ CancelReser()() : void
Compute
- ---:
1 1
+ CkeckCDVaildity() : void
Fares Dedection
1 1
1 - 1 TAmount: int 1
Compare - Tax: int Create ResevationSlip
1
+ CutOffFare() : void - ---:

+ MakeReserSlip() : void
CDDataSelect

- ----: 1
Connect
CDDataAccess
+ closeConnection() : void
+ Connection() : void 1 - ----:

+ AccessCardInfoclose() : void

Class Diagram
pd Package Diagram

User Interface

WEB Pages (Sw ing)

Serv let

Controler

Actuall y in EA there wil l be

no opti on for the depdancey
so i have not made them in
Domain/Business a good manner. T he are the
ruff dependincies.

User Register UserDetails TrainDetails

TricketReserv ation Av ailableTrains TicketFare Payment

Reserv ationSlip UpdateTrainDetails UpdateUserDetails

Techinical Serv ices

CDDataSelect SelectData InsertData

JDBCAccess CreditCardAccess

Database Store

POTTRS Database (ODBC) CD Database (ODBC)

Package Diagram
 Meeting Minutes (7)

Venue: F-11/3 Hostel

Start Time: 9:00PM
End Time: 10:30PM
Date: November 20, 2008

Agenda:
 Draw five main Sequence Diagrams
 Draw their Communication Diagrams
 Draw the Class Diagram
 Draw the Package Diagrams

Meeting Main Points:

○ We read the book chapter 15, 16, 36 carefully to understand initial concepts of how to
draw sequence diagrams.
○ Draw the sequence diagrams and communication diagrams on the paper.
○ We do some practice of how to draw system sequence diagram in Visio and EA.

Work Distribution:
 Assign to draw five main Sequence Diagrams to Yasir Arfat in Microsoft Office Visio 2007.
 Assign to draw their Communication Diagrams to Suleman EA.
 Assign to draw the Class Diagram and Package Diagrams in EA to Ghazanfar.