Sms Proposal

SUPERIOR UNIVERSITY LAHORE
Faculty of Computer Science & IT
RAILWAY MANAGEMENT SYSTEM
Team
Student Name Student ID Program Contact Number Email Address
Ayesha Ahoor BSEM-F16-159 BSSE Bsem-f16-159@superior.edu.pk
Zaeema Rabeet BSEM-F16-160 BSSE Bsem-f16-160@superior.edu.pk
Bakhtawar Liaquat BSEM-F16-242 BSSE Bsem-f16-242@superior.edu.pk
Supervisor
Mr. Muhammad Ahmed Kahloon
Project Report: Railway Reservation System
Project Report
Railway Management System
Change Record
Author(s) Version Date Notes Supervisor’s Signature
1.0
APPROVAL
Faculty of CS&IT, Superior University Lahore, Pakistan ii

PROJECT SUPERVISOR
Comments: ___________________________________________________________________
_____________________________________________________________________________
Name:______________________________
Date:_______________________________ Signature:__________________________
PROJECT MANAGER
Comments: ___________________________________________________________________
_____________________________________________________________________________
Date:_______________________________ Signature:__________________________
HEAD OF THE DEPARTMENT

Comments: ___________________________________________________________________
_____________________________________________________________________________
Date:_______________________________ Signature:__________________________
Faculty of CS&IT, Superior University Lahore, Pakistan iii

1 Dedication
We dedicated our dissertation to our beloved parents, who taught us that even
the largest task can be accomplished if it is done with sincerity and devotion and
given us all of their resources for our study. We want to dedicate this to our
teachers also who enlightened us with knowledge.
Faculty of CS&IT, Superior University Lahore, Pakistan iv

2 Acknowledgements
First of all we are very grateful to Almighty ALLAH who gave us strength and guidance to carry
out our research project. We take immense pleasure in thanking Assistant Professor Sir Ahmed
Kahloon , our project supervisor (The Superior University Lahore) for having permitted us to
carry out this project work.
We would like to express our heartfelt thankful to our beloved parents for their blessings.
Our friends for their help and wishes for the successful completion of this project.
Faculty of CS&IT, Superior University Lahore, Pakistan v

3 Executive Summary
The project is about Railway Management. It's all about to solve the current problems of
railway management. Through this you can check the schedule of trains from departure to
arrival time and the stations from which train has to pass by. You can reserves seats online,
check the availability of seats also you can discriminate seats for male and females. Through
this we can improve our system and our file system. File system will be finished and the system
become online. By using database we can arrange data properly according to our requirements.
Faculty of CS&IT, Superior University Lahore, Pakistan vi

4 Table of Contents
1 Dedication ............................................................................................................................... iv
2 Acknowledgements ................................................................................................................. v
3 Executive Summary................................................................................................................ vi
5 List of Tables .......................................................................................................................... ix
6 List of Figures ......................................................................................................................... xi
Chapter 1 ....................................................................................................................................... 12
Introduction ................................................................................................................................... 12
1.1. Background .................................................................................................................... 14
1.2. Goals and Objectives ...................................................................................................... 14
1.3. Literature Review/Existing Solutions ............................................................................ 15
1.4. Proposed Solution .......................................................................................................... 15
1.5. Project Plan .................................................................................................................... 16
1.5.1. Work Breakdown Structure ........................................................................................ 16
1.5.2 Gant Chart ........................................................................................................................ 17
Figure 1.5.2 ............................................................................................................................... 17
1.5.3 Roles & Responsibility Matrix ........................................................................................ 18
Table 1.5.3 ................................................................................................................................ 18
1.6. Report Outline ................................................................................................................ 18
Chapter 2 ....................................................................................................................................... 20
Software Requirement .................................................................................................................. 20
Specifications ................................................................................................................................ 20
2.1. Introduction .................................................................................................................... 21
2.1.1. Purpose ....................................................................................................................... 21
2.1.2. Document Conventions .............................................................................................. 21
2.1.3. Intended Audience and Reading Suggestions ............................................................ 21
2.1.4. Product Scope ............................................................................................................. 21
2.1.5. References .................................................................................................................. 22
2.2Overall Description .............................................................................................................. 22
2.1.1 Product Perspective .......................................................................................................... 22
2.1.2Product Functions ............................................................................................................. 23
2.2 Operating Environment ....................................................................................................... 24
2.2.1 Design and Implementation Constraints .......................................................................... 24
2.2.2 User Documentation ........................................................................................................ 24
2.2.3 Assumptions and Dependencies ...................................................................................... 25
2.2.4 User Classes and Characteristics ..................................................................................... 25
2.3 External Interface Requirements......................................................................................... 26
2.3.1 User Interfaces .................................................................................................................... 26
2.3.1 Hardware Interfaces .................................................................................................... 26
2.3.2 Software Interfaces ..................................................................................................... 27
2.3.3 Communications Interfaces ........................................................................................ 27
2.4 System Features.............................................................................................................. 28
2.4.1 System Feature ................................................................................................................ 28
2.4.1.2.1 Functional requirement 1: .............................................................................................. 28
2.4.1.2.3 Functional requirement 3:.................................................................................................. 29
Faculty of CS&IT, Superior University Lahore, Pakistan vii

2.6 Functional Requirements ................................................................................................... 42

2.7 Other Nonfunctional Requirements ................................................................................... 42
2.7.1 Performance Requirements .............................................................................................. 42
2.7.2 Safety Requirements ........................................................................................................ 43
2.7.3 Security Requirements ..................................................................................................... 43
2.7.4 Software Quality Attributes ............................................................................................. 43
2.8 Availability ........................................................................................................................ 43
2.9 Reliability........................................................................................................................... 44
2.10 Web Page ......................................................................................................................... 44
2.11 Quality Record ................................................................................................................. 44
2.11.1Business Rules ................................................................................................................ 44
2.12 Other Requirements .......................................................................................................... 45
2.13 DFD Of website ................................................................................................................ 46
Chapter 3 ....................................................................................................................................... 51
Use Case Analysis......................................................................................................................... 51
3.1. Use Case Model ............................................................................................................. 52
3.2. Fully Dressed Use Cases ................................................................................................ 67
Figure 3.2.1 ............................................................................................................................... 68
Chapter 4 ....................................................................................................................................... 69
System Design .............................................................................................................................. 69
4.1 Entity Relationship Diagram with data dictionary.............................................................. 70
4.2 Sequence / Collaboration Diagram 1 ................................................................................. 71
4.3 Sequence / Collaboration Diagram ..................................................................................... 71
4.4 Data Flow diagram .............................................................................................................. 72
4.5Development diagram: ............................................................................................................. 76
4.6 component diagram:................................................................................................................ 77
CHAPTER 5 ................................................................................................................................. 78
IMPLEMENTATION ................................................................................................................... 78
5.1. Tools and Techniques..................................................................................................... 79
REFRENCES ................................................................................................................................ 80
AND .............................................................................................................................................. 80
BIBLIOGRAPHY ......................................................................................................................... 80
Appendix ....................................................................................................................................... 82
Appendix A: To Be Determined List ........................................................................................ 83
Faculty of CS&IT, Superior University Lahore, Pakistan viii

5 List of Tables
6.1 Table no 3.1.1 .................................................................................................................... 52

6.2 Table no 3.1.2 .................................................................................................................... 53
6.3 Table no 3.1.3 .................................................................................................................... 54
6.4 Table no 3.1.4 .................................................................................................................... 54
6.5 Table no 3.1.5 .................................................................................................................... 55
Faculty of CS&IT, Superior University Lahore, Pakistan ix

6.6 Table no 3.1.6 .................................................................................................................... 56

6.7 Table no 3.1.7 .................................................................................................................... 56
6.8 Table no 3.1.8 .................................................................................................................... 57
6.9 Table no 3.1.9 .................................................................................................................... 57
6.10 Table no 3.1.10 ................................................................................................................. 58
6.11 Table no 3.1.11 ................................................................................................................. 59
6.12 Table no 3.1.12 ................................................................................................................. 59
6.13 Table no 3.1.13 ................................................................................................................. 60
6.14 Table no 3.1.14 ................................................................................................................. 60
6.15 Table no 3.1.15 ................................................................................................................. 61
6.16 Table no 3.1.16 ................................................................................................................. 62
6.17 Table no 3.1.17 ................................................................................................................. 62
6.18 Table no 3.1.18 ................................................................................................................. 63
6.19 Table no 3.1.19 ................................................................................................................. 64
6.20 Table no 3.1.20 ................................................................................................................. 64
6.21 Table no 3.1.21 ................................................................................................................. 65
6.22 Table no 3.1.22 ................................................................................................................. 66
6.23 Table no 3.1.23 ................................................................................................................. 66
6.24 Table no 3.1.24 ................................................................................................................. 67
Faculty of CS&IT, Superior University Lahore, Pakistan x

6 List of Figures
1.5.1. Work Breakdown Structure ........................................................................................ 16

1.5.2 Gant Chart ........................................................................................................................ 17
2.4.1 Login ........................................................................................................................................... 46
Diagram 1: ................................................................................................................................ 46
2.4.2 Train info .................................................................................................................................... 47
Diagram:2 ................................................................................................................................. 47
2.4.3 Train schedule ............................................................................................................................ 47
Diagram 3: ................................................................................................................................ 47
2.4.4 Train diagram............................................................................................................................. 48
Diagram 4: ................................................................................................................................ 48
2.4.5 Drop a train reservation ............................................................................................................. 48
Diagram:5 ................................................................................................................................. 49
2.4.6 Make a reservation .................................................................................................................... 49
Diagram:6 ................................................................................................................................. 49
2.4.7 Report diagram .......................................................................................................................... 49
Diagram:7 ................................................................................................................................. 50
2.4.8 Payment of reservation .............................................................................................................. 50
Daigram:8 ................................................................................................................................. 50
4.1 Entity Relationship Diagram with data dictionary .............................................................. 70
Figure 4.1 .................................................................................................................................. 70
4.2 Sequence / Collaboration Diagram 1 ................................................................................. 71
Figure 4.2 .................................................................................................................................. 71
4.3 Sequence / Collaboration Diagram ..................................................................................... 71
Figure 4.3 .................................................................................................................................. 72
Faculty of CS&IT, Superior University Lahore, Pakistan xi

4.4 Data Flow diagram ............................................................................................................. 72

Figure 4.4.1 ............................................................................................................................... 73
Figure 4.4.2 ............................................................................................................................... 74
Figure 4.4 .................................................................................................................................. 75
4.5Development diagram: ............................................................................................................ 76
Figure 4.5 .................................................................................................................................. 76
4.6 component diagram:............................................................................................................... 77
Figure 4.6 .................................................................................................................................. 77
Chapter 1
Introduction
Faculty of CS&IT, Superior University Lahore, Pakistan 12

Chapter 1: Introduction
This document is all about the requirements for the railway management system for the
Pakistan railway. This project is will be very helpful in making the things fast and reliable. It
decreases the work load and man power and also the government assets once it is deployed it
will save a lot of governments assets and made our country progressive and railway system
more efficient. Thing which is going to be done in hours happens in minutes with the help of this.
Through this way we can easily find the schedule of trains arrival time, we can also check the
reservation of seats by online system. In this project we use database system management for
arranging data.

1.1. Background
Railway system is the most important way of transportation. It is very useful for the business
and trade purpose. The background of the railway management system is in 13 May 1861 the
first railway system line was started for people and public transportation.
We find the problems in the current railway management system that we have not appropriate
records of passengers and employs, though we thought that there should be something that can
make records of all these things so we made our system more fast and easy to use.
1.2. Goals and Objectives

Our main objectives and goals of this project of railway management system are to make the
railway system more efficient, easier, comfortable and reliable. This project is only for the use of
administrators. In this project we will come to know how technology system can solve our
problems. The main goals of this project is to managed the arrivals and departures of trains on
time, to managed the seats booking, buy tickets, buy pre-booked seats and also to managed the
cargo tracking.
The objectives of this development efforts are:
• it provides new environment to make reservations.
• To provide an avenue for customers to get their tickets in a more
convenient way
• To regain control of the railway tickets sales to avoid scalping and
overselling of tickets.
• To implement a prototype of a scaled down version of the final system to
test the solution and further develop requirements.
• To collect statistics in a more efficient manner for future railway
development and construction.
• To increase efficiency of railway.

1.3. Literature Review/Existing Solutions

The literature review of the railway management system is to computerized the primer system
by the help of software and database management system. So the data can be stored in the
database for long periods.
Railway management system provide us user friendly, reliable, dependent.
1.4. Proposed Solution

As this project is only for the use of administrators , railway managers and railway customers to
manage the overall approval of a plan or statements for railway system. This system is user
friendly so the railway customers can easily customize and mutate the database.
The railway management system gives us proper security and overcome the written and primer
work.
• Increase the security of Data
• Enhance the efficiency
• provide the better services
• user friendly and correlative or dependent
• Should be interchangeable
• certify the data validity
• overcome the manual entries of data
• take the less time

1.5. Project Plan

The system will be provide us electronic media content (it may be in the form of
printed output) of the railway reservation system in Pakistan. The system will have a
user friendly. This software designed to aid the calculated planning. It will be more
cost effective compared to the current non electronic media content of the reservation
system.
1.5.1. Work Breakdown Structure
• Schedule structure : it manage the timetable of arrival and departure of the trains
• Login system : it used to manage the login details
• customer system : it manage the information and details of customers
• user system : it use to manage the user details and information
• fare and booking : they manage the information about fare and booking system

1.5.2 Gant Chart
Project
Schedule MARCH APRIL MAY JUNE JULY AUGUST SEPTEMBER OCTOBER Summery
2018 2018 2018 2018 2018 2018 2018 2018
TASKS Hours Percent
Requirements 12 12 12 9 45 22.20%
Design 5 7 12 8 32 14.90%
Code and 3 7 4 2 4 5 6 8 2 6 47 13.20&
Unit Test
Test and 3 6 9 12 15 15 12 9 6 3 90 6.60%
integrate
User Manual 16 12 8 4 38 21.10%
Write
Report 2 4 6 8 10 12 14 16 72 1.90%
Writing
Demonstrate 8 8 20.20%
Hours 12 12 10 9 10 12 14 18 10 12 20 10 8 20 21 12 332 100.00%
Figure 1.5.2

1.5.3 Roles & Responsibility Matrix
Zaeema Rabeet Ayesha Ahoor Bakhtawar

Liaquat
Documentation Documentation
and Coding and Coding Documentation
and Coding
Responsibility Responsibility • Introduction

• Use case • Marketing • System
• Use case Material Design
model • Visiting card • Use analysis
• Introductions • Standee • DFD
• Software • Posters • System
• Requirement • Banners Architecture
s • Designing • CODING
• specifications
Table 1.5.3
1. User Roles:
• Can reserve the seats according to their will.
• Can buy tickets online
• Can buy pre-booked seats
• Can do cargo tracking
• Can complains about the system.
1.6. Report Outline

• All the system inputs are validated and don't accept the invalid values.

• It produce or create the report of customers, users, schedule of train timetable and
trains.
• It generates the pure and clear report of fare, booking and trains.
• PDF reports of trains, schedule of timetable, customer and fare also generates.
• It also produce excel export report for train, customer, schedule.

Chapter 2
Software Requirement
Specifications

Chapter 2: Software Requirement Specifications
2.1. Introduction
2.1.1. Purpose
This document is all about the requirements for the RMS for the Pakistan railway. This
project is will be very helpful in making the things fast and reliable. It decreases the work load
and man power and also the government assets once it is deployed it will save a lot of
governments assets and made our country progressive and railway system more efficient. Thing
which is going to be done in hours happens in minutes with the help of this.
2.1.2. Document Conventions

RMS Railway Management System
RRSS Railway Reservation System Server

DB Data Base
Pst Pakistan Standard Time
Rs Rupees
PKR Pakistani Rupees
2.1.3. Intended Audience and Reading Suggestions

This document is just only for client not for public. The document is planned for , project
managers, developers, marketing staff, users, testers and documentation writers.
2.1.4. Product Scope

The system will be provide us electronic media content (it may be in the form of printed
output) of the railway reservation system in Pakistan. The system will have a user friendly. This
software designed to aid the calculated planning. It will be more cost effective compared to the
current non electronic media content of the reservation system.

The objectives of this development efforts are:

• To provide an avenue for customers to get their tickets in a more convenient way
• To regain control of the railway tickets sales to avoid scalping and overselling of
tickets.
• To implement a prototype of a scaled down version of the final system to test the
solution and further develop requirements.
• To collect statistics in a more efficient manner for future railway development and
construction.
• It provides the printing of Tickets
• To increase efficiency of railway
2.1.5. References
3. [1] SOFTWARE ENGINEERING Tenth Edition Ian Sommerville
2.2Overall Description
2.1.1 Product Perspective
Existing system has these features
Data is stored in papers ,is not secured due to natural calamities
• As the data is on paper so it is unable to update ,delete ,add or view data
• Existing system is more time consuming
• Existing system consumes more men power
• Existing system has to deal with large volume of data to deal
• Existing system has to deal with a lot of calculations
• Existing system is manual which involves a lot of paper work
This product proposed the following

• To provide an avenue for customers to get their tickets in a more convenient way

• To regain control of the railway tickets sales to avoid scalping and overselling of
tickets.
• To implement a prototype of a scaled down version of the final system to test the
solution and further develop requirements.
• To collect statistics in a more efficient manner for future railway development and
construction.
• To increase efficiency of railway.
2.1.2Product Functions
Functionalities of this project are
• It will provide searching facility
• It manages the customer details ,online fare details ,booking details and trains details
• It gives all the information about timetables
• It shows the description of trains
• It also monitors the transactions of fare
• Editing ,adding and updating of records
• Editing, adding and updating of fare
• Integrity of all records of booking
• Simple status and resolutions
• Decrease the person load involved in existing manual system
• Individual access to any information
• Reports are well designed
• It will provide multi level priorities
• Better storage capacity
• Updation is more easy
• work speed is increased
• retrieval of information is easy and fast
• to maintain the security user accounts are being secured

2.2 Operating Environment

Software:
• Language: C++
• Database: SQL server
• Browsers: All the browsers
Hardware:
• Ram
• Hark disk
• Processor
• Monitor
• Keyboard
• Mouse
2.2.1 Design and Implementation Constraints

• The software design (maintainability) will not be responsibility of developer or company.
• It will be the responsibility of the admin
• In case of any mishap in the software the developer or company will not be
responsible for that lose
• Developer or company gives a first trail of the software and after that they will not entertain
their quires.
• After delivering the project any increment in the software will be charged by per hour
.
2.2.2 User Documentation

• User can reserves their seats
• User can cancel their seats
• User can see the whole train to get the desire seats

• User can pay online

• User can view the timings of trains easily
• User can track a cargo
• User can view the routes
• User can buy tickets online
• User have access to its wallet (PKR)
• User can have a personal log In account
2.2.3 Assumptions and Dependencies

Assumptions
• It is assumed that the requirements are in its complition phase.
• It is assumed that user is used to the internet browser
• It is assumed that user is familiar with mouse and keyboard use
• It is assumed that user has a decent internet connectivity
Dependencies
• User’s levels are previously determined for all the users
• Access to the system is restricted to the user name
• Restrictions and limitations of all the levels are known by the higher level users
• Security personnel have access to any user’s account
2.2.4 User Classes and Characteristics

1 It will provide searching facility
2 It manages the customer details ,online fare details ,booking details and trains details
3 It gives all the information about timetables
4. It shows the description of trains

5. It also monitors the transactions of fare
6. Editing ,adding and updating of records
7. Editing, adding and updating of fare
8. Integrity of all records of booking

9. Simple status and resolutions

10. Decrease the person load involved in existing manual system
11. Individual access to any information
12. Reports are well designed
13. It will provide multi level priorities
14. Better storage capacity
15. Updation is more easy
16. work speed is increased
17. retrieval of information is easy and fast
18. to maintain the security user accounts are being secured
2.3 External Interface Requirements
2.3.1 User Interfaces

• It will be standard viewing protocols
• It will maintain high contrasts
• It will have high visibility to get best results
• It will have dark colored background
• It will have light colored font o increase the visibility
• Icons will be of bright color
• Layout will be according to the display and scope of the device on which software is being used
• User interface for the application will be in the form of forms, that it will easy to read
2.3.1 Hardware Interfaces

• Ram
• Hark disk
• Processor
• Monitor
• Keyboard
• Mouse

2.3.2 Software Interfaces

Software requirements are the requirements which are required for the building of the project. At
which software the project is been made up
Language: C++
Database: SQL server
Browsers: All the browsers
2.3.3 Communications Interfaces

Communication interfaces are the interfaces through which user and product stackeholders are
connected . For the communication purposes developers uses many ways such as
• Fax
• Telephone
• Mobile phone
• Email
• FAQs
• Live calls
• Live Chats

2.4 System Features
2.4.1 System Feature
2.4.1.1 Description and Priority

These are the features of the system that are really important to write there in such a way a that
if developer start its work from first requirement to the last it will not face any problem of like this
requirement should in first now I have to change all the code to fulfill that requirements such
problems will cause a great time lose
2.4.1.2 Functional Requirements
Functional requirements are the requirements which is necessary for completion of the
details given by the client. In this some requirements are putted by software engineer
which is necessary for proper functionality
2.4.1.2.1 Functional requirement 1:
Description:
It should store information about entry of trains
Input:
enter the time when the train enters at the terminal
Output:

Stores trains entry time with train number in database
Description:
Should keep the record of station
Input:
Enter all the stations from where train has to pass
Output:
Will be displayed at the time of reservation(via)
Description:
It should update the records on instructions
Input:
Update the record when needed
Output:
Show that updation on the user interface

Description:
It should delete the records on instruction
Input:
Delete the record when needed
Output:
Will not show that record from user interface
Description:
It should have passengers’ personal login account
Input:
Should enter an email and a password
Output:
Login to the account
Description:
It should have a admin’s login account
Input:

Should enter admin’s or staff id and password
Output:
Loged in to the admin’s account
Description:
It should have a guest’s login account
Input:
Need no id and password
Output:
Enables to see timings and availability of trains unable to reserve
Description:
It should have a reservation system
Input:
Enter the seat number and numbers of seats you want to reserve
Output:

A message will appear on the screen “Mr Ali reserved the seat number 1,2,3 of train
LE1473 lahore to Karachi of 21:00 pst. Do you want to buy tickets now”
Description:
It should have visuality of full train so that passengers can select desired seat
Input:
Should select the seat

Output:
Display a message “ Do You want to confirm seat?”
Description:
It should have a mobile application
Output:
Should display on the phone’s format
Description:
It should add money to the wallet system
Input:

Add money to user’sr account if user wants
Output:
Add money and display a message “ rs added to your wallet ”
Description:
It should withdraw money from your wallet
Input:
Withdraw money from user’s account if user wants
Output:
Withdraw money and display a message “ ts withdrawn from your wallet”
Description:
It should give a view of money in user’s wallet
Input:
Should select the view button to view wallet
Output:

Will display the money in user’s wallet
Description:
It should have a cargo tracking system
Input:
Should enter cargo number and destination of cargo
Output:
Will get the position of cargo on user’s screen
Description:
It should have a online payment option
Input:
enter user bank account number and password

Output:
Transfer money from user’s account to the management’s account
2.4.1.2.16Functional requirement 16:

Description:
User should get the notifications from product
Input:
user reserve any seat or bookmark the seat

Output:
User get the notification from the product to their respective devices
Description:
User should get the alerts from the product
Input:
Automated to their accounts and given numbers and emails

Output:
User get alerts of new offers, new timmings, delays of trains and other discount offers
from the product to their respective devices
Description:
For new users, it should have a guide book “how to use this forum”
Input:

Click to that link where guide book is placed

Output:
Open ups the guide book and explain it briefly
Description:
It should have a language option
Input:
Language of the product is change for that user

Output:
It should display a messege “you want to change language” and switch to that desired
language
Description:
For the new users it should have a video tutorials
Input:
Click to the links where videos are placed for the users
Output:
video of the clicked link will start playing and its voice and print is as clear as it should
b listen to every one easily

Description:
It should have a video tutorials in every language
Input:
First select the language in which you want to see video

Output:
Video is displayed in the desired language of user
Description:
It should have a search area for a complete forum
Input:
Write there what user wants to search

Output:
Searched results are displayed in a dropdown list
Description:
It should have a priority levels in search bar

Input:
Compare the words of user with the words in the forum

Output:
Best matched word will be on top number and rest are as down below
Description:
It should have a option of cancelletion
Input:
Cancel the reservation according to the needs of the user’s

Output:
Cancel the reservation and display a message “your reservation has been cancelled”
Description:
It should have a concession option
Input:
Enter at the concession option

Output:
Open up to concession form

Description:
It should have a concession form
Input:
Enter the concession type

Output:
Dropdown the concession list
Description:
It should have a concession types
Input:
Enter if user is disable

Output:
Will get the 50 % off on all types of reservations
Description:
It should have a concession type

Input:
If the user is bellow 9

Output:
Will get the seat for free in all types of reservations
Description:
It should have a concession type
Input:
If user is a government employee

Output:
Will get the 50 % off on all types of reservations
Description:
It should have a class option
Input:
Enter the class type

Output:
Will get the visuality of that class block of train not the complete train

Description:
It should have a class types
Input:
Class types are on the bases of fares

Output:
Description:
class types
Input:
Class types are of three types A, B, C

A for business class and expensive with more facilities
B for normal class and less expensive
C for local travelers like students and per day wagers
Output:

2.6 Functional Requirements

These are the features of the system that are really important to write there in such a way a
that if developer start its work from first requirement to the last it will not face any problem of
like this requirement should in first now I have to change all the code to fulfill that
requirements such problems will cause a great time lose
In this document the requirements are written first as of first priority and last of that least
priority
Functional Requirements
Functional requirements are the requirements which is necessary for completion of the
details given by the client. In this some requirements are putted by software engineer which is
necessary for proper functionality.
2.7 Other Nonfunctional Requirements

2.7.1 Performance Requirements
• Its performance should be accurate
• It should be available all the time to customers
• Its server’s link should never be down
• To get best speed ,should best internets to servers
• It should bear the load of as many users at a time, can login to site system should not be
crashed
• System should not be slow on having load on site.

2.7.2 Safety Requirements

• Servers should b e placed where the temperature is low
• System should have a backup server all the time stand by
• System should have a backup database in case of any lose or damage
• Systems should be well updated
2.7.3 Security Requirements

• Security should be of fool proof
• It should have logins
• It should have a password
• It should have pin option
• It should have face id.
• It should have a finger print scanner
• Account should be integrated
• Personal information of a client should not be leaked out
• Password should not be shown on the URL
2.7.4 Software Quality Attributes

Quality Service Requirements are the Requirements which are necessary to maintain your product
quality for the sake of your repute
Quality service requirements are as follow
• First select the test factor and rank them
• Identify the phase of development
• Identify the business risk
2.8 Availability
System should be available all the 24 hours so that it could not be have any difficulty in
reserving the seats for the trains

2.9 Reliability
System should be reliable so that client can give their personal information to the product easily
and trust them that their information is not leaked out for any purpose
2.10 Web Page

System should have a web page for its software with the layout and features of web page
so that system is connected to the internet and has the best updating and editing on all the
systems at once. It reduces the chances of confusions and that make it less complex
2.11 Quality Record

System should have quality record of their data so that when ever record is needed it is easy
to read and understand for that record should be managed
Record can be managed in different ways , by years , by alphabets and many more ways
2.11.1Business Rules
• The software design (maintainability) will not be responsibility of developer or
company.
• It will be the responsibility of the admin.
• In case of any mishap in the software the developer or company will not be
responsible for that lose
• Developer or company gives a first trail of the software and after that they will not
entertain their quires.
• After delivering the project any increment in the software will be charged by per hour.

2.12 Other Requirements

2.12.1 Architectural Requirement:
Architectural requirements are the requirements which are necessary to for
the making of a product . Architectural requirements are the building blocks for the project.
These requirements are the concerns of the clients
There are some architectural requirements for project
• Clarify and understand the project Request
• Size of a project should be determined
• Cost should be calculated
• Should know about the technical and operational feasibility of alternative
approaches
2.12.2 User Requirements:

User Requirements are the Requirements which are to be fulfilled by software
engineer. In this Clients gave software engineer some details of what he wants in
his project
There are some User requirements
• User should know about what to do next.
• Screen should be formatted.
• Messages ,instructions and information should stay as long as it could be
readable
• Without correcting errors , users are not allowed to proceed
• User should never get the programming errors
• Should know about authenticated details
• For concession , concession requirements and percentages should be
given for the execution of programming logics

2.13 DFD Of website
2.13.1 Login
Diagram 1:

2.13.2 Train info
Diagram:2
2.13.3 Train schedule
Diagram 3:

2.13.4 Train diagram
Diagram 4:
2.13.5 Drop a train reservation

Diagram:5
2.13.6 Make a reservation
Diagram:6
2.13.7 Report diagram

Diagram:7
2.13.8 Payment of reservation
Daigram:8

Chapter 3
Use Case Analysis

Chapter 3: System Analysis
3.1. Use Case Model
Reference: 2.4.1.2.1
Use Case Name: Store Information about entry time of train
Priority 5
Trigger When note the time train entrance at the
terminal
Precondition Train should just arrived
Basic Path 1-RRSS send the data to the DB of RRS and
stores the data
2-DB resend the data to the RRSS
Alternate Path N/A
Post Condition It will displayed at the time of reservations
with the route
Exception Path If there is any connection failure RRSS returns
to the wait state
Other
Table no 3.1.1

Use Case Name: Record of stations
Priority 5
Trigger Enter all the stations from where train has to
pass
Precondition Train route is decided
stores the data
Alternate Path N/A
Post Condition It will displayed at the time of reservations
with the route
to the wait state
Other
Table no 3.1.2
Use Case Name: Update record
Priority 5
Trigger When any admin login update the record
Precondition 1-Admin account is logged in.
2-Admin clicks on the update button
updates the data
Alternate Path N/A

Post Condition It shows that update is made on the user

interface
to the wait state
Other
Table no 3.1.3
Use Case Name: Delete record
Priority 5
Trigger When any admin login delete the record
Precondition 1-Admin account is logged in.
2-Admin clicks on the delete button
updates the data
Alternate Path N/A
Post Condition It shows that update is made on the admin
interface
to the wait state
Other
Table no 3.1.4

Use Case Name: Passenger’s login account
Priority 5
Trigger When enter a correct email and password
Precondition Passenger’s device is connected to internet
matches with the data
Alternate Path N/A
Post Condition User should have a home page
to the wait state
Other
Table no 3.1.5
Use Case Name: Admin’s login account
Priority 5
Trigger When enters correct Admin’s or Staff id and
password
Precondition Admin’s device is connected to the internet
matches the data
Alternate Path N/A

Post Condition Loged into admin’s account and go to the

admin’s panel
to the wait state
Other
Table no 3.1.6
Use Case Name: Guest’s login account
Priority 3
Trigger When clicks on the guests account icon
Precondition User’s device should connect to internet
Basic Path 1-RRSS send the data to the DB of RRS
Alternate Path N/A
Post Condition It shows that update is made on the user
interface
to the wait state
Other
Table no 3.1.7
Use Case Name: Reservation System
Priority 5
Trigger When enters the seat number and number of
seats you want to reserve
Precondition 1-User account is logged in.
2-User’s device is connected to the internet


reserves the seats
Alternate Path N/A
Post Condition generates a message on user’s interface
to the wait state
Other
Table no 3.1.8
Use Case Name: Visuality of train
Priority 4
Trigger When enters the seat number and number of
seats you want to reserve
3-user clicks on the desired seat/seats
reserves the seats
Alternate Path N/A
to the wait state
Other
Table no 3.1.9

Use Case Name: Mobile Application
Priority 5
Trigger When clicks on the mobile application icon
Precondition 1-User should connect to the internet
2-Mobile application is downloaded on user’s
device
Alternate Path N/A
Post Condition Go to the user’s panel home page
to the wait state
Other
Table no 3.1.10
Reference: 2.4.1.211
Use Case Name: Wallet System
Priority 4
Trigger Add money to the wallet of user
3-user’s account is connected to the bank
service
Basic Path 1-RRSS send the data to the DB of RRS and add
the money
Alternate Path N/A


to the wait state
Other
Table no 3.1.11
Use Case Name: Withdraw money from Wallet
Priority 4
Trigger When withdraw the money from the wallet
3-user’s wallet has money
withdraw money
Alternate Path N/A
to the wait state
Other
Table no 3.1.12
Use Case Name: View of wallet
Priority 5
Trigger When clicks on the view of wallet


Alternate Path N/A
Post Condition Will display the money on user’s interface
to the wait state
Other
Table no 3.1.13
Use Case Name: Cargo tracking system
Priority 4
Trigger When enters the cargo number and
destination of cargo
reserves the seats
Alternate Path N/A
Post Condition Will get the position of cargo on user’s
interface
to the wait state
Other
Table no 3.1.14

Use Case Name: Online payment System
Priority 5
Trigger When user enters its bank account number
and password
3-User has bank account
connect to the BOPS
2-DB resend the data to the RRSS and add
money to RRS account
Alternate Path N/A
Post Condition Transfer money from user’s account to the
management’s account
to the wait state
Other
Table no 3.1.15
Use Case Name: Notification
Priority 4
Trigger When user reserve any seat on bookmark the
seat

3-User should have network on their device

reserves the seats
Alternate Path N/A
Post Condition generates a notification on their respective
devices
to the wait state
Other
Table no 3.1.16
Use Case Name: Alert System
Priority 4
Trigger When any change happens on the user’s panel
by the admin’s panel
2-DB resend the data to the RRSS and RRSS
send the alert to the device
Alternate Path N/A
Post Condition User gets the alert on user’s devices
to the wait state
Other
Table no 3.1.17

Use Case Name: Guide Book
Priority 3
Trigger When Clicks to that link where guide book is
placed
refer to that link
Alternate Path N/A
Post Condition Open ups the guide book on user’s interface
to the wait state
Other
Table no 3.1.18
Use Case Name: Language option
Priority 3
Trigger When clicks to the language option change
link

Alternate Path N/A

Post Condition generates a message on user’s interface and
switch to that desired language
to the wait state
Other
Table no 3.1.19
Use Case Name: Video tutorials
Priority 3
Trigger When Click to the link where videos are places
for the users
Alternate Path N/A
Post Condition Video is start playing on user’s interface
to the wait state
Other
Table no 3.1.20
Use Case Name: Search area

Priority 5
Trigger Write there what user want to search
search from the complete forum
Alternate Path N/A
Post Condition Searched results are displayed in a dropdown
list on user’s interface
to the wait state
Other
Table no 3.1.21
Use Case Name: Cancellation System
Priority 5
Trigger When cancel the reservation
Precondition 1-User’s account is logged in.
cancel the reservation
Alternate Path N/A


to the wait state
Other
Table no 3.1.22
Use Case Name: Concession option
Priority 5
Trigger When click on the concession option
Alternate Path N/A
Post Condition Open up the concession form on user’s
interface
to the wait state
Other
Table no 3.1.23
Use Case Name: Class Option
Priority 5
Trigger When enters the class type to reserve the seat


reserves the seats
Alternate Path N/A
Post Condition Will get the visuality of that class block of train
on user’s interface
to the wait state
Other
Table no 3.1.24
3.2. Fully Dressed Use Cases

Figure 3.2.1

Chapter 4
System Design

4.1 Entity Relationship Diagram with data dictionary
Figure 4.1

4.2 Sequence / Collaboration Diagram 1
Figure 4.2
4.3 Sequence / Collaboration Diagram

Figure 4.3
4.4 Data Flow diagram
LOGOUT/LOGIN/REGISTER

Figure 4.4.1

Figure 4.4.2
4.3 state transition chart

4.4.State transition diagram
Figure 4.4

4.5Development diagram:
Figure 4.5

4.6 component diagram:
Figure 4.6

CHAPTER 5
IMPLEMENTATION

Chapter 5: Implementation
It's all about components, libraries, web services and stubs. In this chapter we will see the
important flow control and pseudo codes. We also see development environment in this chapter
in which we see the flow
5.1. Tools and Techniques

Tools which are used in development of RMS.These tools are as follow
• Microsoft Word
• Draw.io
• SQL
• Visual Studios
And Techniques which are used in this project

• Software Engineering
• Project Management

REFRENCES
AND
BIBLIOGRAPHY

Reference and Bibliography
[1] SOFTWARE ENGINEERING Tenth Edition Ian Sommerville

[2] SOFTWARE ENGINEERING A Practiotner's Approach by Roger S. Pressman

Appendix

Appendix A: To Be Determined List

We have chose the V model for this prodct as we want a flawless product in the end
without any fault. As we finalize the requirement from the client we create a test for that
requirement and write it as its test and after the completion of the product we can validate the
product through those test

Sms Proposal

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Sms Proposal

Hochgeladen von

Copyright:

Verfügbare Formate

SUPERIOR UNIVERSITY LAHORE

Faculty of Computer Science & IT

RAILWAY MANAGEMENT SYSTEM

Faculty of CS&IT, Superior University Lahore, Pakistan ii

HEAD OF THE DEPARTMENT

Faculty of CS&IT, Superior University Lahore, Pakistan iii

Faculty of CS&IT, Superior University Lahore, Pakistan iv

Faculty of CS&IT, Superior University Lahore, Pakistan v

Faculty of CS&IT, Superior University Lahore, Pakistan vi

Faculty of CS&IT, Superior University Lahore, Pakistan vii

2.6 Functional Requirements ................................................................................................... 42

Faculty of CS&IT, Superior University Lahore, Pakistan viii

6.1 Table no 3.1.1 .................................................................................................................... 52

Faculty of CS&IT, Superior University Lahore, Pakistan ix

6.6 Table no 3.1.6 .................................................................................................................... 56

Faculty of CS&IT, Superior University Lahore, Pakistan x

1.5.1. Work Breakdown Structure ........................................................................................ 16

Faculty of CS&IT, Superior University Lahore, Pakistan xi

4.4 Data Flow diagram ............................................................................................................. 72

Faculty of CS&IT, Superior University Lahore, Pakistan 12

Faculty of CS&IT, Superior University Lahore, Pakistan 13

1.2. Goals and Objectives

Faculty of CS&IT, Superior University Lahore, Pakistan 14

1.3. Literature Review/Existing Solutions

1.4. Proposed Solution

Faculty of CS&IT, Superior University Lahore, Pakistan 15

1.5. Project Plan

1.5.1. Work Breakdown Structure

Faculty of CS&IT, Superior University Lahore, Pakistan 16

1.5.2 Gant Chart

Faculty of CS&IT, Superior University Lahore, Pakistan 17

1.5.3 Roles & Responsibility Matrix

Zaeema Rabeet Ayesha Ahoor Bakhtawar

Responsibility Responsibility • Introduction

1.6. Report Outline

Faculty of CS&IT, Superior University Lahore, Pakistan 18

• It also produce excel export report for train, customer, schedule.

Faculty of CS&IT, Superior University Lahore, Pakistan 19

Faculty of CS&IT, Superior University Lahore, Pakistan 20

Chapter 2: Software Requirement Specifications

2.1.2. Document Conventions

RRSS Railway Reservation System Server

2.1.3. Intended Audience and Reading Suggestions

2.1.4. Product Scope

Faculty of CS&IT, Superior University Lahore, Pakistan 21

The objectives of this development efforts are:

This product proposed the following

Faculty of CS&IT, Superior University Lahore, Pakistan 22

Faculty of CS&IT, Superior University Lahore, Pakistan 23

2.2 Operating Environment

2.2.1 Design and Implementation Constraints

2.2.2 User Documentation

Faculty of CS&IT, Superior University Lahore, Pakistan 24

• User can pay online

2.2.3 Assumptions and Dependencies

2.2.4 User Classes and Characteristics

3 It gives all the information about timetables

4. It shows the description of trains

Faculty of CS&IT, Superior University Lahore, Pakistan 25

9. Simple status and resolutions

2.3 External Interface Requirements

2.3.1 User Interfaces

2.3.1 Hardware Interfaces