railways pakistan system
DESCRIPTION
Pakistan Railways System, Prestion UniversityTRANSCRIPT
2 | P a g e
Table of Contents
1 Project Description ............................................................................................................................ 03
1.1 Brief Description ........................................................................................................................ 03
1.2 Main Stakeholders ..................................................................................................................... 05
2 Software Feasibility Analysis ............................................................................................................. 06
3 Domain Model .................................................................................................................................... 18
4 Software Risk Management Plan ........................................................................................................ 20
5 Requirement Collection ...................................................................................................................... 27
6 Requirement Classification ................................................................................................................. 30
6.1 Requirement Categories .......................................................................................................... 30
7 Requirement Conflict Resolution ........................................................................................................ 32
7.1 Requirement Conflicts ............................................................................................................ 32
8 Requirement Prioritization .................................................................................................................. 33
8.1 Priority Assignment ................................................................................................................ 33
8.2 Prioritization Mechanism ........................................................................................................ 34
9 Software Process Model...................................................................................................................... 35
10 Project Schedule .................................................................................................................................. 35
11 Software Requirement Specification (SRS) ........................................................................................ 37
12 Function Category List with System Attributes .................................................................................. 56
13 VORD Method .................................................................................................................................... 62
14 Formal Specification Using Z language .............................................................................................. 78
15 Object Oriented Design ....................................................................................................................... 92
15.1 Noun Extraction Method ......................................................................................................... 94
15.2 Six Selection Characteristics ................................................................................................... 95
15.3 CRC Index Cards .................................................................................................................... 98
15.4 Conceptual Class Category List ............................................................................................ 111
15.5 Requirement Categorization Table ....................................................................................... 111
15.6 UML Diagrams ..................................................................................................................... 113
15.6.1 UML Structural Diagrams ............................................................................................... 113
3 | P a g e
15.6.1.1 Class Diagram ......................................................................................................... 114
15.6.1.2 Object Diagram ...................................................................................................... 116
15.6.1.3 Component Diagram .............................................................................................. 118
15.6.1.4 Deployment Diagram ............................................................................................. 121
15.6.1.5 Composiste Structure Diagram .............................................................................. 123
15.6.1.6 Package Diagram ................................................................................................... 126
15.6.2 UML Behavioral Diagrams .............................................................................................. 131
15.6.2.1 Use Case Diagram .................................................................................................. 132
15.6.2.2 Activity Diagarm .................................................................................................... 134
15.6.2.3 State Machine Diagram .......................................................................................... 137
15.6.3 UML Interaction Diagrams .............................................................................................. 139
15.6.3.1 Sequence Diagarm ................................................................................................. 140
15.6.3.2 Communication Diagram ....................................................................................... 145
16 Sample Test Cases ............................................................................................................................ 148
5 | P a g e
1. Project Description
Pakistan Railways (reporting mark PR) is a national state-owned rail transport service
of Pakistan. . It is administered by the federal government under the Ministry of Railways. . PR
provides an important mode of transportation throughout Pakistan. It is commonly referred to as
the "life line of the country", by aiding in large scale movement of people and freight throughout
Pakistan.
This Project describes the Pakistan Railway system named as “RailCop Pakistan Ltd.”. All railway
companies try to attain more regular and reliable train services, in order to be able to offer their customers
a higher reliability and flexibility. The present, expensive, strategy is increasing” physical” capacity. A
more cost effective alternative is to first, as far as possible, improve quality in the train control process
itself. The most important factor in this process is the train dispatcher, who from a control centre
supervise (monitor and control) the movements of trains. The dispatchers chances to, in an active way,
plan and control the train traffic is often crucial for how different disturbances effect train delays. We
present a brief overview of existing knowledge and research and some important findings from a survey
based on a set of interviews with dispatchers and train traffic experts. Also indicated are further studies
necessary in order to, at the end, be able to successfully implement a system of this kind. We also
improved the factor of passenger safety and in order to provide comfort to our customers we introduced
the concept of Graphical User Interface (GUI) and many more enhancements to the present environment
has been put forth.
1.1 Brief Description:-
As we all know that the present of our railway system which needs a lot of modifications
and improvements to ensure both safety and comfort for passengers, In order to increase
economy of our country railway transport should be undertaken in keen concentration.
Moreover, with a survey it is noticed that Pakistan Railways carries 65 million passengers
annually and daily operates 228 mails, express and passenger trains. Daily, PR carries an average
of 178,000 people. Pakistan Railways also operates special trains during occasions such as Eid ul
Fitr, Eid ul Azha and Independence Day. In our underlying project we proposed some basics
needs to improve the train transport and facilitate people. New technologies are introduced so
that our railway system is listed in world top transport system. As we all know that in current
system there is lack of passenger safety as well as proper guidance. Secondly, it took more time
to travel through train to reach desired destination. Also, there is no customer care department
that provides first aid, telephone, web hosting etc. So, that is the reason why most of the people
do not prefer to travel through train.
6 | P a g e
1.2 Main stakeholder
Main stake holder are:
Passengers
Our Supervisor Sir Saif-ur-Rehman Khan
Students
Customers
8 | P a g e
2.1 GENERAL INFORMATION
2.2 Purpose
A feasibility study was an evaluation of a proposal designed to determine the difficulty in
carrying out a designated task. Generally, a feasibility study precedes technical development and project
implementation. In other words, a feasibility study is an evaluation or analysis of the potential impact of a
proposed project.
The purpose is
to depict the outcomes of proposals
How our proposal will increase the overall performance of PR
How this will enhance the organization to increase the economic growth.
Can the system be organized using the latest Technologies?
2.3 Scope
Our scope is to facilitate the customers on order to enhance the public transport that is railway
system and to reduce the wastage of time. This will also enhance the economy of Pakistan. More over our
scope is to increase confidence level of people to travel in Railway rather busses, air etc. we are providing
the customers the latest equipment like Graphical User Interface In order to attract the customer to Rail
Travel.
9 | P a g e
2.4 System Overview
The system determines the problems and produces the best results in order to facilitate the
customer’s requirement. The online web application assure the efficiency and less consumption of time
moreover the phone application solves the passengers queries and also saves time as they need not to visit
the Station.
The system provides the daily information to the Administrator about the ticket selling on regular
basis.
Responsible organization Pakistan Railway System
System name or title RAILCOP Pakistan Ltd.
System code CIIT-Spring10-392-A
System category
Major application: Web application for Online Customers.
General support system: HTTP/FTP protocols, LAN networking and SQL
Operational status
Operational interfaces used by staff and Administrator
Under development web application
System environment or special conditions
– Web site application
– GUI
– TELEPHONE
– Scanners like metal detectors are required to scan Luggage and People.
2.5 Project References
i. http://en.wikipedia.org/wiki/Pakistan_Railways ii. http://www.pakrail.com/
iii. http://www.pakistanrail.com/
10 | P a g e
2.6.1 Acronyms and Abbreviations
PR – Pakistan Railway NTES – National Train Enquiry System IVRS – Interactive Voice Response system PRS – Passenger Reservation System GUI – Graphical User Interface DBMS – Database Management System
2.7 Points of Contact
2.7.1 Information
Questions and Queries are welcomed.
Zahid Mehboob
Contact # 0321-5020706
Email Address: [email protected]
Tahir Ayoub
Conatct # 0321-9569264
Email Address:
Contact # 0345-5112812
Email Adress : [email protected]
11 | P a g e
2.7.2 Coordination
Major Cooperation is required from
Project Supervisor and Manager
Current chairman of Pakistan Railway Authority.
Ticket Seller
Security In charge :
2.8 Management Summary
2.8.1 Environment
2.8.2 Organizations Involved
Sponsor:
The sponsor of this project is Pakistan Railway (PR)
Developers:
Zahid mehboob
Users:
Employees working in the organization
Passengers travelling by PR
Security Authorities
Computer:
Intel Pentium 4 is used and computers are interconnected to each other through LAN.
12 | P a g e
2.8.3 Input/output
Keyboard and mouse the primary I/O devices were used. Along with touch screens.
2.8.4 Processing
PR system needed the following requirements to increase efficiency and process
correctly.
P4 systems with 2GB ram and 3.20 GHz processors.
Central server with extra large hard disk space
Touch screen controller
Metal Detectors
Graphical User Interface
Internet
Database Management System
2.8.5 Security
PR provides an overwhelming security inorder to assure the safety of the customers.
Security is provided by the high resolution cameras and scanners like metal detectors. Security is
also applicable to database to ensure the privacy of passenger’s personal information.
13 | P a g e
2.9 System Interaction
Interaction is done by the web site and GUI.
2.9.1 Physical Environment
The system assures the efficiency performance by using web application in order to
calculate the fares and route costs of travelling. Phone application for reservance is another
facility that provides the safety of time.
2.9.2 Current Functional Procedures
In current system the customer is bound to visit the station inorder to get any kind of
information. Moreover there is no record of the passengers and no telephone facility to facilitate
the customers queries. In web site there is no efficiency of calculating fares for multiple
destinations.
2.9.3 Functional Objectives
As there is no facility of telephonic conveyance in PR so it is enhanced in our proposals.
In addition there is no security for the personals and their luggage checking more over there is no
concept of GUI so it is difficult for passenger to travel around and to reach their required
platform moreover there is no data record of the passengers.
14 | P a g e
2.9.4 Performance Objectives
Our enhanced version of the software will ensure the data redundancy of the passengers
and their travel record. Web site will ensure the time safety and will facilitate the passenger to
get Up-to-date information with respect to trains. Telephone facility will increase the customer
relations with the railway staff. This will motivate people to prefer trains rather busses or air etc.
2.10 Assumptions and Constraints
It is assumed that if a person’s is using the web application s/he should be well aware to
use the internet in efficient manner. And using telephonic conveyance there must be availability
of a valid telecom network. One should know how to use GUI.
2.10.1 Methodology
While this system we analyzed the various drawbacks of current system and tried to
overcome these problems by using simple but latest technologies like web application.
Introducing GUI and telephone department and increasing Security using Scanners. Medical
Department is a new concept that is not yet applied in Railways but our project introduces this
concept to meet any kind of emergency or taking care of patients or other unable persons.
2.10.2 Evaluation Criteria
The system provides an easy way to have telephonic conversation mechanism in order to
reduce the communication Gap also there is an attractive web site to view the schedule of the
train. Once the system is established there is no need of hiring more personals rather the system
itself will handle most of the operations. We have put cost in consideration and decided to
introduce the GUI concept which is a new feature to provide the attractive source of interaction.
15 | P a g e
2.10.3 Recommendation
Security and safety of the database is recommended also the GUI devices are placed in
such placed where there is no threat of theft. Security cameras should also be working properly.
All the services like web services and telephonic services should be available round the clock.
Security department should be active all the time in order to meet any kind of emergency.
Security checks like scanner should be available more than one. Only authorized staff is allowed
to access private things like database web server etc.
2.11 PROPOSED SYSTEM
Description of our proposed system is given as under.
2.11.1 Description of Proposed System
The modern concept of GUI is introduced that has the dynamic map installed and also
shows the current location of the train, its route and the schedule of departure/Arrival. It also has
a touch screen facility. There is also a web application that facilitates the customer who can use
net while sitting in his home. Moreover customer care department includes medical department
which has well qualified doctors and their team who are ready to meet any kind of emergency or
any patient. Also there is is a luggage department which saves the luggage of passengers under
strict environment. It not only allows luggage security rather passengers get free from the tension
of any kind of theft. This luggage department allows to transport goods from one place to
another with ease safety and security. This will be done with the generation of a coupen which
will be handover to the customer and the receiving party with the help of internet.
16 | P a g e
2.11.2 Improvements
Improvements are made in almost every aspect of the Railway. As it is well known that
current condition of railway presents a picture of highly unreliable and discomfort environment.
Major improvements includes
Web Hosting(includes online payment and reservation)
GUI
Database (required for backup and history)
Medical Department
Luggage Department
Customer Care Center
Friendly Environment
Enhanced Security (like scanners etc)
2.11.3 Time and Resource Costs
Our proposal is no doubt a bit expensive but it will ensure the reliability and customer’s security
which in turn not only make economic growth but also attract people to travel more by Rail.
3.12 Impacts
The proposals will put a great impact on the economy growth. The web application and telephone
services will save people as well as employee’s time. The dynamic map in GUI will also attract people to
have a clear understanding of their source and destination. The dynamic map concept will attract more
and more customers and thus this will grow the business of organization.
17 | P a g e
3.12.1 Equipment Impacts
Only access to internet is requires in web application and GUI.
3.12.2 Software Impacts
There is a web system that keeps the customers and staff interconnected and upto date.
3.12.3 Organizational Impacts
The system made by keeping in view the facility of customers so it is very user friendly so
there is no need of extra knowledge and information.
3.12.4 Operational Impacts
It is only applicable while viewing the website or making a phone call to get information.
3.12.5 Developmental Impacts
Developmental impacts are
No extra activities performed by the customer.
Basic Resources are required
Privacy and security are more enhanced
18 | P a g e
3.12.6 Site or Facility Impacts
No Impact.
3.12.7 Security and Privacy Impacts
Security is visualized while accessing the database or by paying online fares also in
Scanning System.
3.13 Rationale for Recommendations
Our proposals will increase the customer growth which in turn leads to economic growth
of Organization.
3.14 ALTERNATIVE SYSTEMS
In our opinion there is no such alternative system for enhanced Version.
20 | P a g e
Administrator
Department
Staff
TicketSelling SecurityDeptCustomerCareDept
TrainControlDept
-Monitor1
*
1
*
1
1
Passenger
+handle1..*
1..*
Train
Ticket
Invoice
Invoice Detail
1
*
Telephone Dept WebHost Dept GUI Control Dept
1
1
1
*
1
1
-Checks
1
*
-Buyer
1*
Co
ntro
lling
1
1
1
1
1
1
1
1
1
1
Co
ntro
ls
Has
Luggage
1
1
1
1
MedicalDept
Inventry
1
1
1
*
22 | P a g e
4.0 Introduction
4.1 Identification
This is Risk Management Plan (RMP) for RailCop Pakistan Ltd.
4.2 Objectives
A. The Project Management Plan (PMP, CIIT-Spring10-392-A) includes project-level
objectives for risk management
B. This Risk Management Plan has additional objectives within that framework:
1. To implement a methodology for identifying risks:
The failure of security like cameras, Metal Detector Scanner etc.
The failure of purchased device for Metal Detector Scanners, security cameras, GUI
devices etc
The failure of maintenance data on daily bases.
Corruption of Database
Medical Emergency
If the security or maintenance staff left suddenly due to any valid reason.
2. To implement a methodology for analyzing
We have applied methodology to analyze risk by setting new priorities to that
functional requirement.
The risk avoidance and contingency plans may be modified as new risk information
emerges
3. We implement a methodology for developing and executing responses to risks.
4. We implement a methodology for monitoring the status of each risk, from identification
through closure. The methodology involve regularly assessing each of the identify risk to
decide whether or not that risk is becoming more or less probable and whether the effect
of risk have changed. This is a continuous process and in every management progress
review we consider and discuss each of the key separately.
23 | P a g e
`
4.3 Risk Management Strategy
The strategies that we have think are first we have to identify the overall risk(s) that can
become hurdle/risks in our development, implementation and maintenance phase. Development
process. The main purpose of this RM Report is to first clearly identify all the risks and also give
the best appropriate solution of those problems/risks. We will use the different strategies to deal
with risks.
4.4 Project Risk Identification
Project Risk Identification is concerned with all the risk that can become a hurdle to
develop our project. In our project there are many risks that can decrease the progress of our
project
There may come a problem in budget for installing the GPRS activated device as they are
quite expensive.
As our project has a dynamic map in it so it requires a very experience graphic developer
which are not so easily available so there may be a risk of delay in the submission of this project
as we have only a few number of graphic designer. There may be a possibility that organization
cannot afford this project cost after sometimes. There may be a constant change of requirement
specification by the stake holder. There may be a possibility that the requirement engineer. May
not be able to gather the current viewpoints of different stake holders or there may be a miss
understanding occur between these two. There may be a risk that estimated cost which is
required to enhance the system may increase.
4.5 Project Risk Analysis
As we have done a great analysis on the above identified risk we are come up with the
probabilities of there occurrence.
The probability that the GUI activated device fails is very low ( < 10%)
The probability of loss of the graphic designer is moderate ( 25-50%)
There may be a constant change of requirement specification by the stake holder.
The probability that organization cannot afford this product is very low (< 10%)
There is high probability that the cost of the product increases as the project goes on. Its
probability is high ( 50-70%).
4.6 Project Risk Mitigation Approach
We will minimize the above stated problems by hiring more and more graphic developers
and try to use a high quality better equipped GPRS device so that there will be no risk of loss of
developer or the problem in the technology.
24 | P a g e
4.7 Project Risk Tracking Approach
We have a proper methodology of tracking risk and have different contingency plan such as
if the organization falls into financial crises. There is another plan to solve that issue if that GUI
activated device fails due to any reason we have another device which is of other brand. In this
way we can also check the quality of the device.
4.8 Risk Management Organization
4.8.1 Risk Management Roles and Responsibilities
The following table lists specific roles and responsibilities for risk management, as an
addition to the roles and responsibilities in the Project Management Plan.
RROOLLEE RREESSPPOONNSSIIBBIILLIITTYY
Program Management
Consultant Provide consultation and mentoring on an integrated risk
management methodology
Provide consultation and mentoring on a comprehensive suite of
risk management tools
Facilitate on-going project risk reporting for all projects
Act as liaison to ensure effective communication between the
agencies and the Georgia Technology Authority
Team Member Actively pursue the identification of risks.
Report identified risks.
Provide input into possible mitigation strategies
Project Manager Ensure contract deliverables are met in accordance with the
contract
Conduct comprehensive project risk assessment to indicate
accurate project risk status
Establish formal risk management plan
Present project risks as required to senior management
Ensure risk mitigation deadlines are calculated as efficient as
possible, established and adhered to
Develop and report progress for risk management tasks
25 | P a g e
RROOLLEE RREESSPPOONNSSIIBBIILLIITTYY
Risk Manager Oversee the Risk Management Process
Maintain risk Management Plan
Maintain Risk Assessment Report (RAR)
Support project communication of risks
Support project risk reviews
Establish and maintain risk management facilities in the Project
Management Database
Track Lessons Learned on risks
Provide reports and facilitate meetings for risks and risk
response action items
Support executive level reporting of risks
Risk Owner Maintain Risk Reports for risks within ownership
Perform qualitative analysis for risks within ownership
Monitor risks within ownership
Conduct Lessons Learned sessions for risks within ownership
Configuration Manager Establish configuration control numbering for risks
Maintain configuration control for all risk documentation
Identify risks to configuration management
Quality Assurance
(Oversight) Ensure risk management procedures are followed in accordance
with the Risk Management Plan.
Provide recommendations and suggestions for improvement of
Risk Management Plan
Verify use of risk management methodology and compliance of
risk management documentation with standards
Identify risks to quality
26 | P a g e
Online Purchasing Problem
Risk ID: P-3 Probability: Low Severity: High
DESCRIPTION:
There may be a risk that the customer who is purchasing product on net may face the
security crises office credit card.
ANALYSIS:
There are many hackers on the net who hack the information related to the customer on the
site. Which may consist of the users logging password or the credit card number.
PLAN:
The only solution to reduce this risk to high a networking developer who have an experience
to control hacking.
Dynamic Map Device
Risk ID: P-4 Probability: Low Severity: High
DESCRIPTION:
There may be a risk that the device on which the dynamic graph application is being implemented
may no work properly or may get fail.
ANALYSIS:
The failure of the devices will cause a delay in the submission of the product. As we have to
search for another quality device which is best suited for this type of application. This will
definitely increase the cost of the overall system.
PLAN:
The plan to solve the risk is to initially search three devices of different companies with
almost same prices. If one device fail there is an option to use any of the other two devices.
.
27 | P a g e
Requirement Risk
Risk ID: P-5 Probability: High Severity: High
DESCRIPTION:
The requirement of different stake holder in the organization continuously changes. As they are not
very much aware of the computers related information. The continuous change in the requirement may
lead to the failure of the project.
ANALYSIS:
It is the fact that the requirement of the stake holder changes at regular intervals of time.
Different stake holders may asking for the same functionality in different ways, Thus the
requirement process is to be done very effectively
PLAN:
This risk can be solved by making a team of highly professional and highly qualify
requirement engineer which solve these issues related to the requirement stake holder by taking
interviews and meeting with the stakeholders. This problem can also be solved by doing
brainstorming.
28 | P a g e
5 Requirement Collection:
In order to get well aware of what we are going to do in our, we conducted a series of
meetings with our supervisor Sir.Saif-ur-Rehaman Khan and our teacher including sir Tahir
Mustafa Madni. By conducting personal meetings with our friends and developing a questioner
we gather the thoughts of students that what they think of current Railway and what kind of
improvements are necessary to enhance current railway system.
5.1 Meeting Records
29 | P a g e
i. Functional Requirement
Train information and Route of train must be scheduled before entering data in GUI.
The system should be able to create staff account.
The system should be able to create customer account foe online use only.
The system should be able to add a new passenger record.
The system should be able to deactivate the staff record.
The system should be able to add record for customer ticket reservation.
The system should be able to search customer record.
The system should be able to edit customer record.
The system should be able to edit staff record.
The system should be able to add new customer complain.
The system should be able to make online payment for customers.
The system should be able to tell status of Boogie.
The system should be able to generate invoice.
The system should be able to save and retrieve data when required.
ii. Non-Functional Requirement
Data backup
Quick ticket generation
Interactive interface
User friendliness
Easy maintenance
30 | P a g e
7 Requirement Conflict Resolution
a. Conflict
C 1: It may happen that at same time two trains may follow the same
route hence there are chances of collision and other mishaps.
C 2: It also happens in some cases the luggage of passengers can get
interchanged or get lost.
C 3: Time scheduling of train route may not be properly understood
by the passengers hence conflict may occur which results in loss of
train.
b. Conflict Resolution:
CR 1: Time table and scheduling of trains should be done by the
computer in a realistic manner and after all testing it should be
implied on GUI.
CR 2: Luggage should be deposited to staff before entering the
train. Also, ticket contains the luggage copen number which is a
sure way of resolving this kind of conflict.
CR 3: GUI is introduced to remove such kind of conflicts.
Moreover, complete information of train arrival and departure
timings is mentioned not only on tickets but also on website.
31 | P a g e
8 Requirement Prioritization
8.1 Priority Assignment
i. High Priority Requirements
High priority is given to Database because it is not only handling the passenger
and staff record also it is maintaining a long history of passengers, their luggage
and other useful information.
High priority is given to our security system because it manages security in entire
station in form of various departments moreover security to passenger luggage
and personals is also provided.
High priority is given to train scheduling time table ensuring the two trains don’t
collide.
ii. Medium Priority Requirements
Medium Priority is given to online and manual reservation.
Medium Priority is given to searching operation that system will go to perform.
iii. Low Priority Requirements
Low Priority is given to understanding of system and user interfaces.
Low Priority is given to check for available boogie and seats.
Low Priority is given to availability of user guide.
32 | P a g e
8.2 Prioritization Mechanism
i. High priority
High priority is given those requirements which are very important for working of this
system. Without these requirements our system will be useless also highest possible priority
is given to user and business requirement.
ii. Medium priority
Medium priority is assigned to those requirements which if present will make the
performance of system better. The functional requirements are given the level of medium
priority.
iii. Low priority
Low priority is assigned to those requirements which have nothing to do with the system
but can be needed for help at any time. The non-functional are at the last level of priority.
34 | P a g e
Process Model using Gantt chart
Task Name Start Date Duration (Days)
Bussiness Modeling 2/18/2010 10
SRS 2/22/2010 73
Domain Model 2/25/2010 5
Risk Management 2/28/2010 21
Feasibility Analysis 2/26/2010 49
VORD Method 3/6/2010 23
Formal Specification 3/10/2010 10
Designing 3/13/2010 45
Implimentation 3/22/2010 45
Testing 3/27/2010 45
Deployment 5/29/2010 55
18/02/2010 10/03/2010 30/03/2010 19/04/2010 09/05/2010
Bussiness Modeling
SRS
Domain Model
Risk Management
Feasibility Analysis
VORD Method
Formal Specification
Designing
Implimentation
Testing
Deployment
Start Date
Duration ( Days)
36 | P a g e
11. Introduction
11.1 Purpose
All railway companies try to attain more regular and reliable train services, in order to be able to
offer their customers a higher reliability and flexibility. The present, expensive, strategy is increasing”
physical” capacity. A more cost effective alternative is to first, as far as possible, improve quality in the
train control process itself. The most important factor in this process is the train dispatcher, who from a
control centre supervise (monitor and control) the movements of trains. The dispatchers chances to, in an
active way, plan and control the train traffic is often crucial for how different disturbances effect train
delays. We present a brief overview of existing knowledge and research and some important findings
from a survey based on a set of interviews with dispatchers and train traffic experts. Also indicated are
further studies necessary in order to, at the end, be able to successfully implement a system of this kind.
11.2 Document Conventions
This document has same priority for all the requirements. In the starting, there is a view about Pakistan’s Current Railway System. Later in the document the system is analyzed in detail. Web Application Security Developers Touch Screen GUI (Graphic User Interface)
11.3 Key Word and Abbreviations
PR – Pakistan Railway PRMS- Pakistan Railway Management System DBMS- Database Management System NTES – National Train Enquiry System
IVRS – Interactive Voice Response system
PRS – passenger reservation system
Dr – Doctor
GUI- Graphical User Interface
PR M.S - Pakistan Railway Management System
CGI-Computer Generated Imagery
ODBC-Open Database Connectivity
Train traffic control, decision support, optimization algorithms, systems analysis.
37 | P a g e
11.4 Intended Audience and Reading Suggestions
This document is intended for the following users;
Developers/Tester/Document Writer:
Zohaib Sarfraz Tahir Ayoub
The Users:
Pakistan Railway System (Employees)
Government of Pakistan (GOP)
People of Pakistan
This document is organized in such a way that when a reader will read this document
then first she/he will get the overview of the project that what is it all about and then the purpose
of the software. The rest of this document includes the project scope, perspective, features and its
operating environment. Design and implementation constraints, user documentation,
assumptions, performance, safety, security requirements and software quality attributes.
There are some recommendations to read this document. These are written in a way that
will help to understand the overall ambition of the software. The operating environment, design
and implementation constraints are written for the developers. Any help regarding to the
software designing, testing or any other relative material are written in this section which will
help any new person if she/he is included in the middle of the project. The performance, safety,
software quality attributes and security requirement part. This requirement document contains
general information about Pakistan Railway System, main classes and functions and features.
38 | P a g e
11.5 Project Scope
Pakistan Railways (reporting mark PR) is a national state-owned rail transport service
of Pakistan. It is administered by the federal government under the Ministry of Railways. PR
provides an important mode of transportation throughout Pakistan. It is commonly referred to as
the "life line of the country", by aiding in large scale movement of people and freight throughout
Pakistan.
The software is very efficient and is able to compete all the leading software present at
market already.
The goal for this project is to facilitate the passengers to travel in a safe and
efficient manner.
Another goal of our project is to introduce and use modern technologies in order
to facilitate and enhance the current railway system.
Passenger safety is also one of the important concern in our project.
Secondly we are also providing the facility of Customer Care Center with which
any queries relating to passengers are solved also this department handle calls in
order to update and provide the asked information to the caller.\
To maintain the Passenger record, Staff record, Inventory record in database so
that the record is utilized whenever needed.
To enhance the current security system by using latest technologies like Security
cameras, Call Record, Metal detector.
In current system department Manager does not have the facility to check their
daily Sale and Daily Invoices. Our proposal makes it easy to visualize these
entities by department manager.
The Customer has the facility to reserve ticket(s) online and he can also pay
online through Credit Card.
We are provide a facility of Graphical User Interface by which it will be easy for
the individuals to look for there respective trains and the entire map of the station
and also the train routes and their corresponding timings are displayed.
11.5.1 References
i. http://en.wikipedia.org/wiki/Pakistan_Railways ii. http://www.pakrail.com/
iii. http://www.pakistanrail.com/
39 | P a g e
11.6 Overall Description
This section will provide the complete description of our product which has the following
characteristics.
11.7 Product Perspective
Pakistan Railway System consists of a database which contains data for all the staff and
passengers. Each customer’s data is divided into groups and subgroups so that they are organized
in a form that serves right the user. Every customer is assigned a username and passkey/Ticket#
when getting a ticket for travelling. This system provides the authorities to check maintain, add
or remove the customer record. The system will also provide the luggage scan system to save the
information relating the luggage of customers in order to provide security. The system also
facilitates the user to choose the desired class in which s/he wants to travel like VIP, economy,
business class etc. Also helps the customer to get help about the queries and problems. The
system will also facilitate the customer by having a booking on phone and s/he needs not to
waste time to get on the station and get the required information also a web protocol is provided
in order to have all descriptions and information about train, roots and timings.
11.7.1 Product Features
File Management System Database
The file management system provides the Administrator to maintain customer’s
as well as staff record. The staff member can only enter the database with the authorized
user name and password. As the staff member enter the database he/she can add new
record, can delete and search the existing record with unique id and the desired record
will be printed on the user request.
40 | P a g e
Service Management System :
The service Management system provides the user to manage the services such as
Saloon choice and Classes like air conditioned sleeper, Air conditioned Parlour, Air
conditions Business, Air conditioned Lower, First class sleeper, economy. The system
will provide a facility to the customer to know the fares and timings of the concerned
train.
Customer Management System
This system will provide the customer to have an online reservation with the usage of
Internet to access website of PR or by a phone call. A customer care representative
assigned by the management authority of Pakistan railway will be providing this facility
to the customers.
Register Passenger Remove Passenger
Ticket number Remove Passenger Record
On phone booking Customer call record
Video recording in station for
security
On web booking
Insert Employee Delete/ Edit Employee
Station Map on GUI Bill Documentation
Insert Passenger information Edit/Delete Passenger information
Call Record Retrive Call Record
Insert date/time information View root map of trains
41 | P a g e
11.8 User Classes and Characteristics
The user classes for this product is as followed
System administrators:
Administrators will monitor on computers that support a lot of accounts and
personal data of the passengers. Administrators will also keep an eye on the database that
any unauthorized person would not access the database.
Passenger:
Customers can only use the web based application for online booking. Customer
should have domain knowledge of computers and browsing. In either case h/she will get
information on a telephone call.
Ticket Seller:
Ticket seller uses the database to add a new record. Once a ticket is sold to a
person his name, ticket number, address, train code, train time, route map, luggage
information is added to the database by the ticket seller.
11.8.1 Operating Environment
Operating system: Widows Xp
Backhand Database: Sql
Voice call recorder
Graphical User Interface( GUI )
Insert Luggage info Like Weight etc
Insert type of booking Like vip, economy or business class
42 | P a g e
11.9 Design and Implementation Constraints
11.9.1 Software Constraints
The Railway system has the ability to save and view the records of passengers at any
time. The record contain information about the passenger’s every possible related information
like his luggage, balti number, boogie number, source and destination etc.
11.9.2 Hardware Constraints
Internet browser, such as Netscape 4.0 or above, or Internet Explore 4.0 or above, Sql
DBMS 2005 or above, must be installed in order to use this product.
Valid Telephone must be there to utilize the facility. GUI touch screen Interface should
be installed and maintained.
Input/output: One or two-button mouse and keyboard required. Network card required to make
communication with server possible.
11.9.3 User Documentation
Online help will be available to the users. The customer will provided by username and
password so he can check and found out the services. The customer can also have the facility of
online payments of his dues.
11.9.4 Assumption and Dependencies
It is assumed that the administrator/Staff can maintain the system and the database will be
set up properly. The customer ID and PIN will be distributed in a private way even the
Administrator can’t view it. It is also assumed that the user knows the basic use of the GUI
programs and the basic operation of the computer. The Printer device is fully functional and has
the capability to print. The software and web application must be used 24/7.
43 | P a g e
11.10 System Features
11.10.1 Description and priority
We have mentioned some of the features above in section number 2.2. Following are the
features that are given high priority.
Customer Management System
Service Management System
File Management System Database
11.10.2 Functional Requirements.
Create a Staff Account
FR # 1.1
Description The System shall allow staff to create accounts with a unique
username, email, personal password and personal address
Source. System Administrator
Evaluation
method
System will verify uniqueness of username and email address
prior to account creation.
44 | P a g e
Adding a new Passenger Record
FR # 1.2
Description. The System shall allow the staff to enter a new customer record
with the unique customer ID.
Source. Staff.
Evaluation
method
The System will verify the uniqueness of the customer ID and add
the record in the database
Remove Customer Record
FR # 1.3
Description. The System shall allow the staff to delete Passenger’s record.
Source. Staff
Evaluation
method
The System shall search the customer record and accepts the staff
request to delete it.
Deactivate Staff Record
FR # 1.4
Description. The system shall allow the administrator to Deactivate the staff
record
Source. System administrator
Evaluation
method
The system shall search the staff record and then accepts the
request of administrator to delete it
45 | P a g e
Adding new add record for customer ticket reservation.
FR # 1.5
Description. The System shall allow the Customer to get any kind of Service
he needs regarding Railway like reservation etc.
Source. Customer
Evaluation
method
The system shall verify the information provided by the customer
for the order of new service
Search Customer Record
FR # 1.6
Description. The system shall allow the staff to search the customer record for
which he/she requested for
Source. Staff
Evaluation
method
The staff shall enter the customer name / customer ID to search
the customer record.
46 | P a g e
Edit Customer Record
FR # 1.7
Description.
The system shall allow the staff to edit the customer record for
which he/she requested for.
Source. Staff
Evaluation
method
The staff shall enter the customer name / customer ID to change
the customer record like route, timings etc.
Edit Staff Record
FR # 1.8
Description. The system shall allow the Admin to edit the staff record for
which he/she requested for
Source. Administrator
Evaluation
method
The Admin shall search by the staff name / ID to make desired
changing’s.
47 | P a g e
Adding New Customer Complain
FR # 1.9
Description. The System shall allow the customer to enter the complain of
service along with complain type
Source. Customer
Evaluation
method
The System verify customer complain, its type and customer ID
who made that complain. And the complain id recorded
automatically.
Customer Online Payments Account
FR # 1.10
Description. The system shall allow the customer to pay his/her service dues
and bill online.
Source. Customer
Evaluation
method
The system shall verify the customer id, his/her account no and
the credit card no for the online payment of bills.
48 | P a g e
Users and Human Factors Requirements:
FR # 1.11
Description. The System shall allow people with minimal internet browser
experience to become users in the System and use its features and
functionalities.
Source. Customer/Staff
Evaluation
method
The customer shall Visit The Pakistan Railway Website to create
account and to book for any destination.
Checking Status of Boogie
FR # 1.12
Description. The System shall allow the Staff to get all the information like
seats availability, reserved seats etc.
Source. Staff
Evaluation
method
The system shall verify the Boogie Number and information will
be provided to staff.
49 | P a g e
Invoice Details
FR # 1.13
Description. The System shall allow the staff to generate invoice of the
passenger.
Source. Staff /Admin
Evaluation method The system will verify the ticket sold and then generate the
invoice which will be monitored by the Admin.
Luggage Deposit
FR # 1.14
Description. The System shall allow the staff to generate coupen for extra
luggage of the passenger.
Source. Staff /Admin
Evaluation
method
The system will verify the ticket sold and then generate the
invoice which will be monitored by the Admin.
50 | P a g e
11.11 External Interface Requirements
11.11.1 User Interfaces
A Graphic User Interface (GUI) with all menus, toolbars, dialog box, and buttons will be
user friendly so that the user can run the program more efficiently. The user will have all kinds
of facilities and control over the software. Moreover it will also be providing the complete map
of his desired route map and also the location of his Train with time schedule.
11.11.2 Hardware Interfaces
The “PR M.S” software includes two major hardware components: phones and regular
PC's provided with internet.
The telephone sets are used for the regular communication between the different
employees of the organization and also used by the customer of the Pakistan Railway to provide
the necessary information about the service which they wanted to acquire.
The second component involves the regular PC’s, which communicate with the server.
The server then communicates with the database. The protocol involved between the PC's and
the server is the HTTP protocol, which allows communication between the PC's and the Server.
The remote PC's, such as someone accessing the “View Train Schedule” from home using the
Internet, are able access the information through the CGI (Computer Generated Imagery). The
requests come in through the HTTP protocol, and using an ODBC (Open Database
Connectivity), the database results are returned and are given to web page. The format of the
output is displayed as web pages. Moreover, online reservation and payment can be done here.
51 | P a g e
11.11.3 Software Interfaces
MYSQL DBMS will be used to manage the database and any changes made to it. Furthermore,
the DBMS will make regular backups of the database and generate reports regularly. The server between
the client and the database will handle all communication, and the server will run on windows XP
operating system.
Information about the services and features of “PR Management System” is
i. DBMS.
i. Name: MYSQL
ii. Version: 2000 or greater.
iii. Source: Microsoft.
ii. Operating System
i. Name: Windows XP.
ii. Version: Professional Edition (Service pack 2 or Greater).
iii. Source: Microsoft.
iii. World Wide Web
i. Name: Internet Explorer.
ii. Version: I.E 5 or Greater.
iii. Source: Microsoft.
52 | P a g e
11.11.4 Communications Interfaces
The communication between the customer and organization will be entertained through electronic
mailing, phone calls and web portal that the customer will use. The e-mail will be delivered to network
System who will forward this request to the relevant department and give an update to the customer using
the same interface i.e. e-mail. The request will be forwarded to the relevant department by the network
administrator using a Network Server Communication Protocol or an FTP server that will work upon the
request and then reply to the network administrator so that he can give a reply to the customer about the
status of his request.
Communication within the Railway Organization is made by LAN, each computer is
interconnected with other. Web application is supported by HTTP protocol and is worldwide. Employees
can communicate to each other through intercom or telephones or through microphone.
11.12 Other Nonfunctional Requirements
11.12.1 Performance Requirements
In order to facilitate the employees and especially the customers, high level of performance is
required of the system. PR Management System should be able to handle a large number of staff records
and customer records without any ambiguity and redundancy. Moreover, the software should also be able
to retrieve the data as and when required by the customer and employees. The system should be well
equipped with all the basic features such as editing, updating and printing a record in order to facilitate
the user.
11.12.2 Safety Requirements
Safety is an important feature to be added to every software development especially for a system
having a database containing information of the whole organization. It is necessary for the database to be
safe so that in case of any accident the information on the database is safe. For this purpose, information
that has been changed by the employee is being saved on an online encrypted server which can be
retrieved by the authorized officials anytime the system is crashed or the database is corrupted. This
information can be downloaded directly to the system as and when required.
53 | P a g e
11.12.3 Security Requirements
Security is an important part of every software development now-a-days. In web application only
authorized staff is required to enter the database to add view and delete any record. Moreover this will
ensure that privacy of a passenger is sealed. Also there is a Metal Detector Scanner to scan the persons as
well as their luggage individually.
11.12.4 Software Quality Attributes
User friendly system
Only authorize person can manage the data
The data is highly protected and secure
Customer can use web application for online booking
This system can be enhance or modified later without changing in this system
11.13 Other Requirements
DBMS should be organized by a man who is fully expert in this system and familiar with
SQL. This system should be given back to the developers after every 2 years for the maintenance
and checking of its correctness. This system is made for use in the territory of Pakistan only and
is equipped with both the English and Urdu language.
55 | P a g e
12.1 Function Category List
Basic Function
Ref# Function Category
R1.1 Record the current sale – the tickets
Sold
Evident
R1.2 Calculate current sale total, including
tax
Evident
R1.3 Inventory market (buying/selling) Hidden
R1.4 Transaction detail( including credit
card etc)
hidden
R1.6 Ticket seller must login with an ID and
password in order to use system
Evident
R1.7 Provide a persistent storage mechanism Hidden
R1.8 Display ticket description and invoice
detail
Evident
Payment Functions
Ref# Function Category
R2.1 Handle cash payments, capturing amount
tendered and calculating balance due
Evident
R2.2 Handle credit payment, capturing credit
information from a card reader or by the manual
entry and authorizing payment with the store’s
(external) credit authorization service via a
modem connection
Evident
R2.3 Handle check payment, capturing drivers license
by manual entry, and authorizing payment with
the store’s (external) credit authorization service
via a modem connection
Evident
R2.4 Log credit payment to the accounts receivable
system, since the credit authorization service
owes the payment amount
hidden
56 | P a g e
System Attributes
Attribute Detail and Boundary Constraints
Response
time
(boundary constraint) when recording a sold ticket, the
description and price will appear in 5 seconds
Interface
metaphor
(detail) forms-metaphor windows and dialogue boxes
(detail) maximize for every keyboard navigation rather than
pointer navigation
Fault
Tolerance
(boundary constraint) must log authorized credit payments
to accounts received within 24 hours, even if power or
device failure
OS plat-
forms
(detail) Microsoft Windows Xp, 95 amd NT
System Attribute in Function Specification
Ref # Function Category Attribute Detail and
Constraints
Category
R.1 Login with a
valid username
and password
Evident Response Time 3 Seconds Must
R.1.1 Validation Hidden Fault
Tolerance
3 seconds Must
R.1.2 The system
should give
facility to
change
password
Evident Interface
metaphor
Form based
Colorful
Must
want
R.2 Passengers
Information
Hidden Response Time
Interface
metaphor
3 seconds
Form based
colorful
Must
Must
Want
R.3 Passengers
record
Hidden Fault
Tolerance
Secure records Must
57 | P a g e
Ref # Function Category Attribute Detail and
Constraints
Category
R.3.1 Adding/
deleting
passenger
Record
Evident Fault tolerance System update
record
Must
R.4 Passenger
Equipment Info
Evident Fault tolerance Information should
be right
Must
R.5 Providing
passenger his
allotted boogie
number
Evident Response Time
Fault
Tolerance
5 seconds
Correct mapping of
passenger with their
booked boogies and
seats
Must
Must
R.6 Record of Staff Hidden Fault
Tolerance
Secure
records
Must
R.7 Adding/
Deleting
records of Staff
Evident Fault tolerance System update
record
Must
R.8 Staff Allocation Evident Response Time
Fault
Tolerance
10 seconds
Staff should be
allocated to the
departments
according to
specialty and needs.
Must
Must
R.9 Display Staff
allocation with
duties
Evid
ent
Respon
se time
5 seconds Want
R.10 Train Attributes Evident Response Time
Fault
Tolerance
5 seconds
System should b
knowing all trains
attributes/condition
Must
Must
58 | P a g e
Ref # Function Category Attribute Detail and
Constraints
Category
R.11 Adding records
of trains
Evident Fault tolerance System update
record
Must
R.12 Information
about free train,
boogie# and
seats#
Frill Fault tolerance The information
should be correct
Want
R.13 Displaying
Schedule of
trains
Evident Response Time
Fault
Tolerance
10 seconds
Correct
overview of
trains
schedule
Must
Must
R.13.1 Print Schedule Evident Response time
Interface
metaphor
5 second
Form based
colorful
Want
Must
Want
R.13.2 Update time
table
Evident Fault tolerance System should
resolved train
clashes
Want
R.14 Graphical user
interface
Frill Interface
metaphor
colorful Must
R.15 Identification of
train clashes
Frill Response Time
Fault
Tolerance
3 seconds
Informations
hould be
correct
Must
Must
R.16 Display Error
message if
found clashes
Evident Fault tolerance System should
display clashes( i.e
time matching of
trains at same
station/ tracks)
Must
R.17 Display Error
message if any
other fault
occur
Evident Fault tolerance System should pin
point all faults
Must
R.18 Store the
information
Hidden Fault tolerance The system should
keep the information
Must
59 | P a g e
Ref # Function Category Attribute Detail and
Constraints
Category
R.19 Data Retrieval Hidden Response time 5 seconds
Data can be
retrieved when ever
desired
Must
R.20 System displays
whether
updated and
headline news
Evident Interface
metaphor
Form based
colorful
Must
Want
R.21 System should
resolve train
clashes
Hidden Fault tolerance System should know
the timing of every
train
Must
R.22 Searching
function
Evident Response time 10 seconds
System should allow
user to search train
attribute as well as
passengers
Must
R.23 Creating
Backup
Hidden Fault tolerance
Response Time
Interface
metaphor
Error free backup
3 seconds
Form based
Must
Must
Want
R.24 Adding records
of Inventory
Evident Fault tolerance System update
record
Must
R.25 System
takes
suggesti
on from
users
Frill Interface
metaphor
Form based Want
61 | P a g e
13.1 VIEW POINTS
Administrator Staff manager Staff
Ticket seller Security Manager Ticket Manager
Train control
Manager Customer Dept. Manager
62 | P a g e
Administrator
Reference Administrator
Attributes Username
Password
Events Start System
Close System
Webhost
Monitoring
Services Add Staff
Remove Staff
Edit Staff
Search Staff Record
View Train Attributes
Manage New train
Manage new Products
Remove Products
Edit Product (In case of repairing)
View Call Records
Monitor Video Records
Sub VPs No VPs
Department Manager
Reference Department Manager
Attributes Username
Password
Events Monitor Departments
Adviser
Manage Department
Control Management
Services Add new Dept
Edit Dept
View Department Services
Monitor Video Records
63 | P a g e
Manage Staff manager
Provide Inventory
Sub VPs Administrator
Staff Manager
Reference Staff Manager
Attributes Username
Password
Maintained Record
Events Monitor Staff
Assign Staff duty
View Online booking
View services
Services Add Staff
Edit Staff
Remove Staff
Attendance Record
Search Staff Record
Sub VPs Administrator
Staff
Reference Staff
Attributes StaffID
Name
Password
Department
Events Handle Staff
Handle Online booking
Manage/Provide Services
Services Add passenger/Staff
Edit passenger/Staff
Remove passenger/Staff
Search passenger/Staff Record
Sub VPs Staff Manager
64 | P a g e
Ticket Manager
Reference Ticket Manager
Attributes Username
Password
Events Manage Ticket
Manage Online Ticket
View Record
View Services
Services View passenger Info
Edit/Remove Passenger Info
Online Editing/Remove Ticket
View Invoice
Sub VPs Administrator
Ticket Seller
Reference Ticket Seller
Attributes SellerId
Password
Events Sell Ticket
Sell Online Ticket
Manage Record
Services Add passenger Info
Edit Passenger Info
Online selling Ticket
Generate Invoice
Sub VPs Ticket Manager
65 | P a g e
Staff/Passenger
Reference Staff/Passenger
Attributes ID
TicketId
Ticket Holder
Events View Webpage
View Services
Book ticket
Services Online Booking
Online Paying
Search services Records
View Dynamic Map
Sub VPs No VPs
Security Manager
Reference Security Manager
Attributes Username
Password
Events Monitor Security Issues
Monitor Staff
Monitor Passengers/Staff
Assign Security staff duty
Services Monitor camera
Manage Security camera
Mange Department Security
Sub VPs Administrator
66 | P a g e
Train Control Manager
Reference Train Control Manager
Attributes Username
UserId
Finger Print
Events Manage/Control Train
Control Train Rail
Monitor Passengers/Staff
Services Monitor train(s)
Monitor Route
Handle Rail w.r.t train
Allocate Train Arrival/ Departure
Sub VPs Administrator
Medical Department
Reference Medical Staff
Attributes Username
UserId
Events Monitor Passenger/Staff
Provide necessary First Aid
Services Ambulance
First Aid
Allocate necessary medical resources
Sub VPs Administrator
67 | P a g e
Luggage Department
Reference Luggage Department
Attributes Username
UserId
Events Monitor Passenger’s luggage
Scan Luggage
Services Provides passengers to transport their luggage with ease and comfort
Sub VPs Administrator
13.2 SERVICES
Add Staff
Reference Add Staff
Rationale Interview New member to work in Organization.
Specification Allocate a New selected member, a Unique username, Id, password and Allocate
department w.r.t spatiality.
Viewpoints Staff Manager
Administrator
Non
Functional
Requirement
Unique user id and username
Department
Associated Job
Provider
68 | P a g e
Remove Staff
Reference Remove Staff
Rationale Remove/suspend the staff who exceeds age limit or is not working or serving
the organization properly.
Specification The staff manager, Administrator or Dept. manager will first search the record of
the staff member by their unique Id and Delete the required person.
Viewpoints Staff Manager
Dept. Manager
Administrator
Non
Functional
Requirement
The system database will not delete the entire record rather it can display the
record when ever needed for any emergency. The system will deal him as a non
member person and disable his username, id and password
Provider
Edit Staff
Reference Edit Staff
Rationale Edit information of staff as required such as “promotion”, “Salary” etc
Specification The authorized person(s) will search the required staff with their unique Id so
that they can make the required changes.
Viewpoints Staff manager
Dept. Manager
Administrator
Non-
functional
requirements
They only can change the “promotion” status, Salary, Address etc But they
cannot change the StaffId.
Provider
69 | P a g e
Search Staff
Reference Search Staff
Rationale Search the required Information of the staff.
Specification The authorized person(s) will search the required staff with their unique Id so
that they can make the required changes.
Viewpoints Staff manager
Dept. Manager
Administrator
Non-
functional
requirements
Search queries can be:
1. Search by name
2. Search by Id
3. Search by department
Provider
View Train Attributes
Reference View Train Attributes
Rationale To search the Train information w.r.t route
Specification Staff searches the required train according to the passenger specification and
requirements and provide information to the passenger
Viewpoints Train Control manager
Staff + staff manager
Administrator
Non-
functional
requirements
Search queries can be:
1. Search by TrainId
2. Search by Route
3. Search by other attributes
Provider
70 | P a g e
Add New Inventory
Reference Add New Inventory
Rationale To add new Inventory into the organization.
Specification Adding new inventory according to the requirements, budgets and needs.
Viewpoints Administrator
Dept. Manager
Non-
functional
requirements
Assign inventory to the particular department
Add in system database (Productid, Name, Date/time etc)
Provider
Remove Inventory
Reference Remove Inventory
Rationale To remove any Out of order inventory.
Specification Remove inventory that is Out Of Order and replace it with the new one.
Viewpoints Administrator
Dept. Manager
Non-
functional
requirements
Assign new inventory to the particular department
Update system database (Productid, Name, Date/time etc)
Provider
71 | P a g e
View Call Records
Reference View Call Records
Rationale To listen/View to all calls received by the customer care center
Specification Staff Enter the database where all calls are automatically saved and than choose
any call to listen.
Viewpoints Security Manager
Administrator
Non
functional
Requirements
View queries will be:
1. Search by call date
2. Search by call time
3. Search by problem
Provider
View Video Records
Reference View Video Records
Rationale To watch the video recordings of the various cameras present at various nook
and corners of the organization for security purposes.
Specification Staff Enter the database where all videos are automatically saved and than
choose any video to watch.
Viewpoints Security Manager
Administrator
Non
functional
Requirements
Search by camera ID, date, time
Every media player is supported
Provider
72 | P a g e
Online Booking
Reference Online Booking
Rationale To have an online booking for any visit.
Specification Customer will logon to the organization’s website, view and select services and
than can fill the form to book the ticket. The uploaded information will be saved
to the database.
Viewpoints Customer\ passenger
Non
functional
Requirements
Form language will be formal and understandable be every individual.
Time consumption will be very small to have efficient.
Provider
Online Payment
Reference Online Payment
Rationale To make an online invoice payment after selecting the train and services.
This will be done by the Credit card. And it will be private and confidential.
Specification Once the customer buys the ticket he is assigned the id and password to check
status of the trip. He will use that id and password to avail online payment of
dues facility.
Viewpoints Customer/passenger
Non
functional
Requirements
The transaction will be done in very efficient way and the notification will be
sent to the customer as mail or mobile message as a proof.
Provider
73 | P a g e
Dynamic Map
Reference Dynamic Map
Rationale To help the customers present in station to look for the desired departments and
trains.
Specification Staff will use the GUI and resolve queries of the Customers.
Viewpoints Customer/ passenger
Non
functional
Requirements
Graphics and touch screen system.
Provider
Insert New Department
Reference Insert New Department
Rationale To inset a new department to Organization.
Specification Administrator will manage the staff and insert a new department to the
organization based on needs and requirements.
Viewpoints Administrator
Department Manager
Non
functional
Requirements
Unique Department id and name is given.
Provider
74 | P a g e
Edit Department
Reference Edit Department
Rationale To modify the information related to the department
Specification Dept manager will use dept id and name to edit the particular department.
Viewpoints Department Manager
Administrator
Non
functional
Requirements
Database updated
Provider
Provide Inventory
Reference Provide Inventory
Rationale To provide inventory to the department
Specification Dept manager will assign new inventory according to requirements
Viewpoints Department Manager
Administrator
Non
functional
Requirements
Database updated
Provider Administrator
75 | P a g e
Luggage Deposit
Reference Luggage Deposit
Rationale To deposit luggage to the staff in order to have a safe and sound transportation
of goods and precious luggage. It works like cargo in the train.
Specification Once the customer has bought the ticket than the next step is to check either he
has the luggage till the limit (in our case 25 kg) than he has to buy an extra ticket
call luggage Coupen to reserve a particular balti for their luggage.
Viewpoints Passenger
Non
functional
Requirements
Extra transaction will be done in an efficient manner and an online
acknowledgement will be sent to both sender and receiving party which will
include luggage detail and coupen number.
Provider
Medical Department
Reference Medical Aid
Rationale To provide a first aid to the passenger who are not well or disable. It is very
efficient in order to meet any kind of mishap and emergency.
Specification To provide an extra facility to our passengers of medical aid to those who are
traveling in train and they get any kind disease or casual problems. First aid is
present and a doctor with well trained staff is always ready to provide help
whenever demanded.
Viewpoints Customer/passenger/customers
Non
functional
Requirements
A very rapid and basic aid is provided without loss of any time to save life and
meet any unwanted circumstances.
Provider
77 | P a g e
RailCop Pakistan
Staff : P STAFF
Staff_ID:P S_ID
Staff_Name : P STAFF_NAME
Password : P PASSWORD
Staff_Authorization : STAFF_NAME (S_ID Password)
Ticket : P TICKETS
Ticket_Id :P T_ID
Ticket_Name :P (TRAIN_NAME TRAIN_ID)
TicketSold : seats PASSENGERS
SoldTo : P P_ID
Seat : P SEAT
Status : STATUS
Luggage_Id: T_Id P_Id
Passenger : P PASSENGER
P_Name : P P_NAME
Passenger_Id : P P_ID
Buy: TICKET SEAT
Passenger_Ticket: P_NAME T_ ID
Train : P TRAIN
Train_Name : P TRAIN_NAME
Train_Id : P TRAIN_ID
Route : TRAIN_ID TICKET
Train_Type : P Type
Department : P DEPARTMENT
Dept_Name : P DEPARTMENT_NAME
Dept_Id : P DEPT_ID
Manager : DEPARTMENT STAFF_NAME
Inventory : P INVENTORY
Inventory_Name : P INVENTORY_NAME
Inventory_Id : P INVENTORY_ID
Inventory_Price : P INVOICE
Inventory_Dept : INVOICE DEPARTMENT
Report : P REPORT
78 | P a g e
Initialization
Δ RailCop Pakistan Ltd.
Staff Ticket Passenger Train department Inventory =
Staff_Name = dom Staff_ID dom Password
Ticket = dom Ticket_id dom Ticket_Name dom
SoldTo dom seat
Passenger = dom Passenger_Id dom Buy dom P_Name
Train = dom Train_Id dom Train_Name dom Route dom
Train_Type
Department = dom Dept_Id dom Dept_Name dom Manager
Inventory = dom Inventory_Id dom Inventory_Price dom
Inventory_Dept
79 | P a g e
Add_Staff
Δ RailCop Pakistan Ltd
Name ? : STAFF_NAME
Staff_Id ? : S_ID
Password ? : PASSWORD
Staff_Id? Password? Staff_Authorization
STAFF_NAME’ = STAFF_NAME {Name?}
S_ID’ = S_ID {Staff_Id?}
PASSWORD’ = PASSWORD {Password?}
80 | P a g e
Add_Inventory
Δ RailCop Pakistan Ltd
Name? : INVONTERY_NAME
Inventory_Id? : INVENTORY_ID
Inventory_Price? : INVOICE
OUTPUT! : INVOICE
Staff_Id? Password? Staff_Authorization
INVENTORY_NAME’ = Inventory_NAME {Name?}
INVENTORY_ID’ = S_ID {Inventory_Id?}
Output! = Price? Invoice
81 | P a g e
Remove_ Staff by S_ID
Δ RailCop Pakistan Ltd
Staff_Id ? : S_ID
Password? : PASSWORD
Status ::=Deactivate
Staff_Id? Password? Staff_Authorization
Staff_Authorization’ = Status
staffed?Staff_Authorization
82 | P a g e
Search Passenger_by_Name
Ξ RailCop Pakistan Ltd
Name ? : P_NAME
OUTPUT! : P_NAME
Name? P_Name
Output!= Passenger
NewSID ? ∉ SID
Add_Passenger Info
Δ RailCop Pakistan Ltd
Name ? : P_NAME
Passenger_Id ? : P_ID
Password ? : PASSWORD
Luggage_id ? : Luggage_Id
Staff_Id? Password? Staff_Authorization
P_NAME’ = P_NAME {Name?}
Passenger_ID’ = Passenger_ID {Passenger_Id?}
Seat’ =Ticket (Train seat)
Luggage_Id’ = Ticket (Train Passenger_Id)
83 | P a g e
Search Staff_by_Id
Ξ RailCop Pakistan Ltd
Id ? : S_ID
OUTPUT! : STAFF_NAME
Id? Staff_Authorization
Output!= Staff
NewSID ? ∉ SID
Search Staff_by_Name
Ξ RailCop Pakistan Ltd
Name ? : STAFF_NAME
OUTPUT! : STAFF
Name? Staff_Authorization
Output!= Staff
NewSID ? ∉ SID
Search Passenger_by_Id
Ξ RailCop Pakistan Ltd
Id ? : P_ID
OUTPUT! : P_NAME
Id? Passenger_Id
Output!= Passenger
NewSID ? ∉ SID
84 | P a g e
Add_Department
Δ RailCop Pakistan Ltd
Name? : DEPATMENT_NAME
Dept_Id? : DEPT_ID
Output! = Invoice
Staff_Id? Password? Staff_Authorization
DEPT_NAME’ = DEPT_NAME {Name?}
DEPT_ID’ = DEPT_ID {Dept_Id?}
Output! = Invoice
85 | P a g e
DepartmentAlreadyExist
RailCop Pakistan Ltd
Name ? : DEPARTMENT_NAME
Dept_Id? : DEPT_ID
Output1! = REPORT
Name? Dept_Id Department
Output1! = “Department already exist”
86 | P a g e
PassengerRecordAlreadyExist
RailCop Pakistan Ltd
Pass_Id ? : P P_ID
Output1! = REPORT
Pass_Id? Passenger_Id
Output1! = “Passenger_Id already exist”
StaffRecordAlreadyExist
RailCop Pakistan Ltd
Staff_Id ? : P S_ID
Password? : P PASSWORD
Output1! = REPORT
Staff_Id? Password? Staff_Authorization
Output1! = “StaffAuthorization already exist”
87 | P a g e
RecordNotFound
RailCop Pakistan Ltd
Staff_Id ? : P S_ID
Password? : P PASSWORD
Passenger_Id? : P P_ID
Output1! = REPORT
Output2! = Report
Staff_Id? Password? Staff_Authorization
Output1! = “Is Not found Try Again or meet the coordinator”
Passenger_Id? P_ID
Output2! = “Sorry No Record Found”
Success
Output! : REPORT
Output! = “Successfully Done”
88 | P a g e
StaffInvalidEntry
RailCop Pakistan Ltd
Staff_Id ? : P S_ID
Password? : P PASSWORD
Output1! = REPORT
Output2! = REPORT
Staff_Id? Password? Staff_Authorization
Output1! = “Is Not Valid Try Again or meet the coordinator”
Output2! = “Also please check your spelling mistake”
89 | P a g e
ROBUST VERSION
R_Add_Staff (Add_staff Success) (StaffRecordAlreadyExist ) (InvalidEntry)
R_Add_Passeneger (Add_Passenger Success) (PassengerRecordAlreadyExist )
(StaffInvalidEntry)
R_ Remove _Staff ((StaffAuthorization Success) (RemoveStaff)) (RecordNotFound)
(StaffInvalidEntry)
R_Add_Department (Add_Department Success) (DepartmentAlreadyExist)
(StaffInvalidEntry)
R_Add_Inventory ((StaffAuthorization Success) (Add_Inventory Success)
(StaffInvalidEntry)
R_Search_Passenger_By_Name (Enter_Passenger_Name Success)
(PassengerRecordNotFound) (StaffInvalidEntry)
R_Search_Passenger_By_Id (Enter_Passenger_Id Success) (PassengerRecordNotFound)
(StaffInvalidEntry)
R_Search_Staff_By_Name (StaffAuthorization Success) (StaffRecordNotFound)
(StaffInvalidEntry)
R_Search_Staff_By_Id (StaffAuthorization Success) (StaffRecordNotFound)
(StaffInvalidEntry)
91 | P a g e
15.1 Project Scope
The goal for this project is to facilitate the passengers to travel in a safe and
efficient manner.
Another goal of our project is to introduce and use modern technologies in order
to facilitate and enhance the current railway system.
Passenger safety is also one of the important concern in our project.
Secondly we are also providing the facility of Customer Care Center with which
any queries relating to passengers are solved also this department handle calls in
order to update and provide the asked information to the caller.
To maintain the Passenger record, Staff record, Inventory record in database
so that the record is utilized whenever needed
To security system by using latest technologies like
Security cameras, Call Record, Metal detector.
In current system department Manager does not have the facility to check their
daily Sale and Daily Invoices. Our proposal makes it easy to visualize these
entities by department manager.
The Customer has the facility to reserve ticket(s) online and he can also pay
online through Credit Card.
Medical department is introduced to meet any kind of emergency and mishaps
and to facilitate the passengers who are unable of any body part or in any kind of
disease.
Luggage department is provided in order to transport goods from one place to
another. Extra payments is due on extra weighted luggage.
We are providing a facility of Graphical User Interface by which it will be easy
for the individuals to look for there respective trains and the entire map of the
station and also the train routes and their corresponding timings are displayed.
92 | P a g e
15.1 Noun Extraction Method
S.No Object and Classes
1) Passengers
2) Customers
3) Inventory
4) Ticket Seller
5) Metal Detector
6) Administrator
7) Customer Manager
8) Department Manager
9) Security Manager
10) Invoice
11) Credit Card
12) Credit card reader
13) Security
14) Daily Ticket Sale
15) Security Cameras
16) Call records
17) Control room
18) Website
19) Online Reservation
20) Online Payment
21) Medical Aid
22) Luggage Deposite
93 | P a g e
Categorization Method
External Entities Passenger, Staff, Metal Detectors, Credit Card, Security Cameras.
Things Graphical User Interface, Database, website.
Occurrence of
Events
Call records, Online Reservation, Daily Sale.
Roles Customer manager, department manager, Administrator, Ticket
Seller, security officer
Organizational
Units
Places Security Office, Control room, Ticket Office
Structures
15.2 Six Selection Characteristics
1. Retained Information
2. Needed Services
3. Multiple Attributes
4. Common Attributes
5. Common Operations
6. Essential Requirements
94 | P a g e
Potential
Object/Classes
Characteristics
Staff 1,2,3,4,5,6
Administrator 1,2,3,5,6
Passengers 1,2,3,4,5,6
Department 1,2,3,4,5,6
Department
Manager
1,2,3,4,5,6
Inventory 1,2,3,4,5,6
Ticket Seller 1,2,3,4,5,6
Daily Sale
Security 1,2,3,4,5,6
Call Records 1,2,3,4,5,6
Security Cameras 1,2,3,4,5,6
GUI 2,3,6
Scanners 2
Invoice 1,2,3,4,5,6
Credit Card 6
Online
Reservation
1,2,3,6
Online Payment 1,2,4,5,6
95 | P a g e
Verb Or Verb Clause Extraction Method
Our project scope and SRS provides the following verb or verb clauses
1. Entering Passenger Record
2. Making Online Reservation
3. Entering Passenger record
4. Entering Staff record
5. Entering Inventory Record
6. Managing Record
7. Generating Invoice
8. Call recording
9. Security Cameras
10. Metal Detector Scanning
11. Searching/Editing record
12. Using GUI
Physical Location or Placement:
Data is located and stored in SQL database.(For all classes above except (10, 13)
96 | P a g e
15.3 CRC Index Cards
i. Entering Passenger Record :
Owner:
This verb or action belongs to the Passenger class.
Attributes:
The main important attributes are first name, last name, sex, address, religion,
NIC number, cell number and many others.
Communication:
The communication of this operation is with the online Paying and generating its invoice.
ii. Making Online Reservation:
Communication:
The communication of this operation is with the online Paying and generating its invoice.
Owner:
This verb or action belongs to the Passenger class.
Attributes:
The main important attributes are first name, last name, sex, address, religion, NIC
number, cell number and many others.
97 | P a g e
iii. Entering Passenger Record:
Owner:
This verb or action belongs to the Passenger class.
Attributes:
The main important attributes are first name, last name, sex, address, religion, NIC
number, cell number and many others.
Communication:
The communication of this operation is to record data for future usage if needed for
security purpose.
iv. Entering Staff Record :
Owner:
This verb or action belongs to the Passenger class.
Attributes:
The main important attributes are first name, last name, Staff_Id, password, sex, address,
religion, NIC number, cell number and many others.
Communication:
The communication of this operation is to record data for future usage if needed.
98 | P a g e
v. Adding Inventory Record :
Owner:
This verb or action belongs to the Inventory class.
Attributes:
The main important attributes are Staff_Id, Password, Dealer, Product_Id, Department
and many others.
Communication:
The communication of this operation is with the department class.
vi. Record Management :
Owner:
This verb or action belongs to the every above class except (class Number 10, 13).
Attributes:
All attributes of Staff, Passenger and Inventory are in it (Shown above).
Communication:
The communication of this operation is with the (Passenger, Staff and inventory) classes.
99 | P a g e
vii. Generating the invoice :
Owner:
This verb or action belongs to the INVOICE class.
Attributes:
The main important attributes are Invoice_Id, Staff_Id, Ticket_Id, Inventory_Id and
many other.
Communication:
The communication of this operation is with the (Passenger, Staff and inventory) classes.
viii. Call Recording :
Owner:
This verb or action belongs to the Calls class.
Attributes:
The main important attributes are call number, date/time, passenger_Id, Place and many
other.
Communication:
There is communication with customer Care class.
100 | P a g e
ix. Security Cameras :
Owner:
This verb or action belongs to the Videos class.
Attributes:
The main important attributes are Videos number, date/time, Place and many others.
Communication:
There is communication with Security class.
x. Metal Detector Scanning :
Owner:
This verb or action belongs to the security class.
Attributes:
The main important attributes are Luggage scanning, Personal scanning.
Communication:
There is communication with Security class.
101 | P a g e
xi. Searching/Editing Record :
Owner:
This verb or action belongs to the Staff, Passenger, Inventory classes.
Attributes:
All attributes of Staff, Passenger and Inventory are in it (Shown above).
Communication:
The communication of this operation is with the (Passenger, Staff and inventory) classes.
xii. Using GUI :
Owner:
This verb or action belongs to the GUI classes.
Attributes:
The main Important Attributes are Train_Route, Locate_Map, Visualize_Station,
Train_Location and many more.
Communication:
There is communication with GUI class which is the part of customer care.
102 | P a g e
xiii. Luggage Deposite :
Owner:
This verb or action belongs to the Luggage Department.
Attributes:
The main Important Attributes are providing an easy and comfortable way of
transporting goods from one place to another. Works like cargo, and extral luggage(i.e. more
than 20kg) will be transferred to the cargo. And extra expenditure will we issued.
Communication:
There is communication with ticket department.
103 | P a g e
15.3 CRC INDEX CARDS
Class Online Reservation
Responsibilities Collaborator
Passenger open the home page
Enter email and password Web Page
Class Administrator
Responsibilities Collaborator
Enter Administrator_Id and password Staff
Monitor Staff
Passenger
Customer
Department
Videos
Calls
104 | P a g e
Class Department Manager
Responsibilities Collaborator
Enter username and password
Monitor Staff
Inventory
Department
Class Ticket Seller
Responsibilities Collaborator
Enter Staff_Id and password Staff
Sells Ticket
Generate invoice Customer
Invoice
Inventory
105 | P a g e
Class Passenger
Responsibilities Collaborator
Passenger Reserve the tickets Web Page
Passenger Pay For tickets Online
Class Inventory
Responsibilities Collaborator
Request base operation
Class Department
Responsibilities Collaborator
Request base operation
Class Staff
Responsibilities Collaborator
Request base operation
106 | P a g e
Class Invoice
Responsibilities Collaborator
Detail description of purchased Tickets Inventory
Staff
Passenger
Ticket(s)
Class Medical
Responsibilities Collaborator
Provide Medical aid to passenger in case of
any emergency
Staff
Doctor
Monitors Staff
Passenger
Customer
107 | P a g e
Class Online Payment
Responsibilities Collaborator
Enter Email and password Passenger
Open the website Home Page
15.4 Finding Concepts with Concept Category List
Concept Category Examples
Physical or Tangible
Objects
Train(Boogie/seat etc), GUI, Metal
Dictator, Security Cameras,
Specification, design or
Description of things
Train Schedule and arrival/departure
description, Inventory Details
Places Railway Station
Transaction Ticket Reservation, Online Payment
Role of people Train Operator/driver, Ticket Seller
Container of othr things Train
Things in container Passengers, luggage, Fuel, Security
Other computer or
electromechanical
system external to our
system
TrainControlRoom
Abstract noun concepts Cancelation policy, Refund Policy *
Organization Ticket Sale Department, Security
Department, Customer Care DepT
Events Sale, Robbery/theft, arrival/departure
crash, luggage misplace
Processes Booking (Seat, Boogie, Buy Tickets
108 | P a g e
* Ticket Refundable policy is according to rule in which all payment will be given back
if the ticket is returned before 24 hours else half payment will be returned.
etc) Reservation, Online payment
(Credit Card etc)
Rules and Policies CancelationPolicy,
LuggageMisplacePolicy,
FirstComeFirstGetPolicy,RefundPolicy
Catalogs Parts Catalogue with detail
Manual Book Repair manual, Train driving manuals,
Control Room Manuals
Records of finance,
contract, work, legal
matters
Maintenance Log, Employment
Contract, Invoices
Financial Instrument
and services
Stock, Inventory
109 | P a g e
15.5 Requirement Categorization Table
A is a physical part of B Boogie – Train
Seat – Boogie
A is a logical part of B DepartureLog –
departureRoute
Ticket – Reservation
A is a physically contained in/on B Passenger – Train
Luggage – Boogie
A is a logically contained in B Departure –
DepartureSchedule
Inventory –
InventoryCatalogue
A is description for B DepartureDescription –
Departure
InventoryDescription –
Inventory
A is a line item of a transcription or
report B
MaintenanceJob –
Maintenance
TicketSale – Sale
A is known/logged/recorded/captured
in B
Reservation –
departureManifest
A is a member of B Locomotive engineer –
Train
TicketSeller – Staff
TrainRouteOperator –
ControlUnit
A is an organization subunit of B Maintenance – Train
Departments – Station
A uses or manages B Locomotive engineer –
Train
TicketSeller – Tickets
A communicates with B ReservationAgent –
Passengers
110 | P a g e
DepartmentManager –
Staff
A is related to a transaction B Passenger – Ticket
Invoice – Sale
A is a transaction related to another
transaction B
Reservation – Cancellation
Invoice – Sale
A is next to B City – City
Boogie – Boogie
Seats – Seats
Department – Department
A is owned by B Train – RailwayMinistry
Inventory – Administrator
113 | P a g e
#S_Id : Int
-Username : String
-Password : char
#NIC : Int
-Address : String
-Phone# : Int
Staff
-S_Id : String
-Login : String
-Password : Int
-Sub_D_Id : Int
-Duty_timings : Times
CustomerCare
#Train_Id : Int
#S_Id : Int
-Login : String
-Password : Int
+Trian Name : String
+Route : String
+Duty Timings : Times
TrainControl
-Monitor1
*
1
*
1
1
#P_ID : Int
-F_Name : String
-L_Name : String
#Route : String
#T_Id : Int
-Phone : Int
-Lug_Id : Int
-Destination : String
Passenger
+h
an
dle
1..*
1..*
+Train_Id : Int
+Train_Route : String
## of Boogies : Int
+Train_Name : String
-
Train
#TIC_Id : Int
-TrainName : String
-Boggie # : int
-Type : String
-Seat # : Int
-Route : String
-P_Id : Int
-L_Id : Int
Ticket
#TIC_Id : Int
#Invoice_Id : Int
#P_Id : Int
-D_Id : Int
Invoice
-Invoice_Id : Int
-D_Id : int
InvoiceDetail
1
*
#S_Id : Int
-Login : String
-password : char
+# of telephones : Int
+Duty_Timings : Times
TelephoneDept
#S_Id : Int
-Login : String
-Password : char
WebHostDept
#S_Id : Int
-Login : String
-Password : char
-
GUI_ControlDept
1
1
1
*
-Checks
1
*
-Buyer
1*
Co
ntro
lling
1
11
1
1
1
Co
ntro
l
1
1 1
1
Co
ntro
ls
Has
-Name : String
-NIC : Int
-Login : String
-Password : char
-Address : String
-Phone # : Int
Administrator
-D_Id : Int
-Name : String
-Type : String
-D_Manager : String
Department
#TIC_Id : Int
#S_Id : Int
-Login : String
-Password : char
+Duty_Timings : Times
TicketHouse
#S_Id : Int
-Login : String
-Password : char
+Duty_Timings : Times
Security
#Inventory_Id : int
-Name : String
-Price : Float
-Quantity : Int
Inventory
1
1
*
*
-#Lug_Id : Int
-#TIC_Id : Int
-#P_Id : Int
-#Weight : float
Luggage
1
1
1
1
#Dr_Id : Int
-Login : string
-Passwords : char
MedicalDept
1
1
Generates
1
1
115 | P a g e
#S_Id : 0023
-Username : abc
-Password : xxx
#NIC : 67856
-Address : dhokh khabba
-Phone# : 45676
staff:Staff
#S_Id : 125
-Login : abc
-Password : xxx
-Sub_D_Id : 564
+Duty_timings : morning
cc:CustomerCare #Train_Id : 453
#S_Id : 437
-Login : abc
-Password : xxx
+Trian Name : damaka
+Duty Timings : night
tc:TrainControl
#P_ID : 999
-F_Name : Ali
-L_Name : Ali
#Route : Lahore
#T_Id : 01
-boogie# : 6
-seat# : 65
-Luggage_Id : 000
-Destination : karachi
-Phone : 12345
pass:Passenger
+Train_Id : 453
+Train_Route : lahore
## of Boogies : 12
+Train_Name : damaka
-
:Train
#TIC_Id : 01
-TrainName : damaka
-Boggie # : 254
-Type : String
-Seat # : Int
-Route : Lahore
-P_Id : 999
-L_Id : 000
:Ticket
#TIC_Id : Int
#Invoice_Id : Int
#P_Id : Int
:Invoice
-Invoice_Id : 123
-D_Id : 99
:InvoiceDetail
#S_Id : 2243
-Login : abc
-password : xxx
+# of telephones : 1000
+Duty_Timings : noon
td:TelephoneDept
#S_Id : 321
-Login : abc
-Password : xxx
whd:WebHostDept
#S_Id : 545
-Login : abc
-Password : xxx
-
gui:GUIControlDept
-Name : Ali
-NIC : 1234
-Login : abc
-Password : xxx
-Address : G-10
-Phone # : 1234
admin:Administrator
-D_Id : 456
-D_Manager : Ali
dept:Department
#S_Id : 789
-Login : abc
-Password :xxx
+Duty_Timings : Noon
th:TicketHouse
#S_Id : 453
-Login : abc
-Password : xxx
+Duty_Timings : evening
sec:Security
#Inventory_Id : 121
-Name : camera
-Price : 40,000
-Quantity : 5
inv:Inventory
#Dr_Id : 0011
-Login : abcc
-Password : xxx
med:MedicalDept
#Lug_Id : 000
#Tic_Id : 01
#P_Id : 999
#Weight : 30
lugg:Luggage
117 | P a g e
Administrator
Departments
Database
OnlinePayment
Invoice
WebHost
Inventory
OnlineReservation
Staff
Administrator Monitors all above mentioned attributes
118 | P a g e
TicketSeller Invoice Passenger
AdministratorRites
customer
OnlineReservation
Website
Database
OnlineReservation
customer
Website
OnlinePayment
Database
OnlinePayment
Bank
120 | P a g e
ServerDataBase
SQL/Oracle Data
Base
WebServer
wamp5_1.4.5
Website
* *
*
*Software
*
*
MS Visual
Studio2008
Reserve Ticket
SignOut
SignIn
OnlineInvoicePay Via
CreditCard
Customer
122 | P a g e
+/InTrain {Union}1
+/powerSource {Union}1
/source {Union} /transmitter {union}
Train
+/InTrain {Union}1
+/powerTransmitter {Union}1..*
PowerSource powerTransmitter
Engine
Wheels
Pistons
Source {R
edifines Source}
Transmitter {Redifines Transmitter}
Source {R
edifines Source}
Tra
nsm
itter
{R
edifi
nes
Tra
nsm
itter
}
1
0..16
1
0..2
123 | P a g e
TicketSeller
Invoice
Inventory
DataBase
Administrator
OnlinePayment
OnlineReservation
OnlineInvoice
Customer
Staff
125 | P a g e
GUI
Invoice
DataBase
Customer
Staff
OnlinePayment
OnlineReservation
WebHost
Inventory
OnlineInvoice
Bank
Ticket
131 | P a g e
Online Reserve
Tickets
Make Payment
Deposit
LuggageCustomer
Login
Login
Generate
Invoice
Handle
Customer(s)
Feed Back
Maintain
Inventory
Data
base
System
Train Control
Unit
Staff
Manager/
Administrator
Generate Ticket
Web hosting
GUI
Monitor/Handle
Staff
Manage
Inventory
Luggage Depart./
Boogie
Admin/
Bank
1
1
1
1
1
1
1
1
1
1
1
1
11
1
1
0..*
1..*
0..*
0..1
1
1..*
1..*
1..*
1..*
1..*
1..*
1..*
1..*
1..*
133 | P a g e
i. Customer Care
ii. Luggage Boarding
[else]
[have phone] Customer
Care
Telephone help Make a
Phone call
Go to
PCO Dial
Number
Wait to get
phone call
attended
Take
required
Help
Close
connection
Online Help
Go to
Website
Go to Net
Club
Search for
help/query
Type in
search box
Get the
required help
Close web
page
Terminate
connection
departure
Cry on your Luck
[else]
[have ticket(s)] Luggage
Boarding
Equal or less than 40 KG Get into
Train
Buy the
Ticket Go To
Booge
Search for
Seat#
Place
Luggage
Wait for
Train
departure
Net/Pc Crash Change yourLuck
More than 40 KG
Goto luggage
department
Weight for
exact luggage
Pay for extra
weight
Pay via credit
card or cash
Handover
luggage to staff Wait for train
departure
Get into
train
departur
e
Cry on your Luck Go home
Cry on your Luck Net/Pc Crash
134 | P a g e
iii. Reserving Ticket
iv. Doctor Activity
[else]
[have Net] Reserve
Ticket
Online Reservation TurnOn pc Go to Net
Club Go To
Website
Search for
Route train
Confirm
Booking
Date/Time
Reserve #
of seats
Make
payment
Net/Pc Crash Change yourLuck
[Else]
Manual Reservation
Go To Station
with FNF
Buy the
Ticket
Reserve #
of seats
Confirm
Booking
Go to Home Wait for train
departure
Get into
train
departur
e
Cry on your Luck
FNF goes
home
[else] [else]
[have FirstAidKit] Medical
Aid
Doctor On Train Goto Desired
boogie
Pick First Aid Kit
from cabin
Check the
Patient
Inform to the
upcoming station
In extreme
emergency
Treat him/her
normally
Luck of Patient
Doctor On station
Waiting for
emergency in
office
Patient call Dr
for emergency
situation
Dr pick the
First Aid Box
Dr reached at
desired place
Treat the
patient
Give patient
required medicine
In case of extreme
emergency call Ambulance
Cry on your Luck
136 | P a g e
Train Stopped
Train Door
(protocol)
Door Opened Door Closed
Door LockTrain Started
DoorWay->IsEmpty())Close
Locks
Open
Ticket Generate
(Protocol)
Computer On Connect To DB Check Avability Of Tickets Printer On
Print Ticket(s)Printer OffComputer Off
Ticket Generate
(Protocol)
TicketGenerate ReceivePayment PrintTicket
CheckLuggage WeightLuggage BoardLuggage
AttendPhone SolveQuery
CheckTicket
SendHome
Done
Done
Done
Done
Pass
Done
Fail
Done
Checked
Done
139 | P a g e
LogIn
Sd Login
Login
User Validation
Confirmed
:System:systemDataBase
ChangePassword
Updating
Changed
Acknowledgment
Validating
Updating
140 | P a g e
Reservation
Sd Reservation
Login
User
Validation
:System DataBase
Confirmed
Information
Detail
Request for Reservation
CheckAvalibility
Status
ReserveTickets
Confirmed
Update
Logout
Confirmed
TicketIdAlloted
141 | P a g e
Online Payment
Sd OnlinePayment
ReserveTicketUser Validation
:System DataBase
Confirmed
CreditCardInformation
Validation
Detail
Update
:Bank
Confirmation
CreditInfo
confirmed
TicketReceiptGenerated
Login
Validation
Logout
Confirmed
142 | P a g e
Deposite Luggage
Sd DepositLuggage
ShowTicket
User
Validation
System
Confirmed
HandoverLuggage
List
Confirmed
Update
Copen
Staff
LuggageDetail
:SystemDataBase
Detail
GenerateInvoice
ClearPayment
144 | P a g e
Online Payment
Customer
1 OnlinePayment
WebApp:
UserInterface
Creditcard:
Validation
1.1 Validation
Bank
1.2 Validating
DataBase
1.3 Updating
Deposite Luggage
Customer
1 Deposit Luggage
LuggageDept
DataBase
1.1 Depositing
Staff
1.2 Updating
145 | P a g e
Online Reservation and payment
Customer
1 OnlineReservation
2 Change Password
WebApp:
UserInterface
Creditcard:
Validation1.1 Validation
2.1 Validation
DataBase
1.2 Updating
2.2 Updating
147 | P a g e
Add Passenger Record
Method Add Passenger Record
Signature Void add_passenger(p_id)
Description This function will add the passenger record to the DataBase.
Parameter Input: passenger_id, which is a unique identifier for passenger
Output: message prompt
Calling Service Update DB
Delete Passenger Record
Method Delete Passenger Record
Signature Void delete_passenger(p_id)
Description This function will delete the passenger record from the DataBase.
Parameter Input: p_id, which is a unique identifier for passengers
Output: message prompt
Calling Service Update DB
Add Staff Record
Method Add Staff Record
Signature Void add_staff(s_id)
Description This function will add the staff record to the DataBase.
Parameter Input: s_id, which is a unique identifier for staff
Output: message prompt
Calling Service Update DB
148 | P a g e
Update Staff Record
Method Update Staff Record
Signature Void update_staff(s_id)
Description This function will update the staff record to the DataBase.
Parameter Input: s_id, which is a unique identifier for staff.
Output: Editable form of that customer ill be displayed
Input: Update the information
Calling Service Update DB
Search Passenger Record
Method Search Passenger Record
Signature Void search_passenger(p_id)
Description This function will search the passenger record from the DataBase.
Parameter Input: p_id, which is a unique identifier for passengers
Output: message prompt with entire details of the passenger
Calling Service Update DB
149 | P a g e
Reserve Ticket
Method Reserve Ticket
Signature Void Reserve_Ticket(Tic_id)
Description This function will reserve the ticket for the passenger and add the
information to the datanbase.
Parameter Input: Tic_id, which is a unique identifier for ticket.
Output: Editable reservation form for the passenger will be
displayed
Input: Update the information
Calling Service Update DB, Ticket selling department staff
Add Luggage Info
Method Add passenger luggage Information
Signature Void add_lugg(lugg_id)
Description This function will add the luggage detail of the passenger to the
database and generate a coupen having the coupen number and all
luggage detail provided.
Parameter Input: lug_info, complete details.
Output: passenger coupen will be generated
Calling Service Luggage deposit staff