Software Engineering

Name: Farhan Ahmed

Reg no: 50800
Instructor: Saira Khurram

Railway Reservation System

The Railway Reservation System Facilitates the passengers to enquiry about the trains that are available
on the basic of their source and destination, booking and cancellation of tickets, enquiry about the status
of booked tickets, enquiry about the status of booked ticket etc. The aim of case study is to design and
develop a database maintaing records of different trains, trains status and passengers. This project
contains introduction to the railway reservation system. It is computerized system of reserving the seat of
train seat in advance. Online Reservation system has made the process of reservation very much easier
than ever before.
Railway Reservation System, has described above can lead to error free, secure, reliable, and fast
management system. It will help organization in better utilization of resources. Administrator of the
project, with the help of password, can enter new train record, display all train records, modify train
records and days on which it is available, whereas records of train status includes dates for which tickets
can be booked, total numbers of seats available and number of seats already booked.

Methodology:
The spiral model is very much beneficial method. It is the combination of prototyping model & waterfall
Model. The spiral model is used for large, Risky, Expensive & Complicated project as best suits for
railways reservation system. A big Advantage which is risk Management is the highlight of this model,
the best SDLC model that is available changed so this one. User Requirements can be changed so it is
flexible as well. In this system following are the Benefits:

 The system Requirements are gathered in detail from users. It can be done with gathering
information form number of users.
 An Elementary Design is created for the system. It is the most important phase of spiral model.
To create a cost effective project, strategies are founded. This stage assists with recognition of
functionality meets in requirements, with the sufficient data software, proceeds, changes are made
to meet and remove the uncertain data.
Functional requirement:
1. Keeping records of affirmation of clients.
2. Storing and managing the data items.
3. Keeping the day by day sell.
4. Keeping insights regarding the items it is covered or not and so forth.

Non-Functional requirement:
1. Secure access of private information.
2. Better and accurate segment configuration to improve execution at top time.
3. Twenty Four – 1 accessibility.
4. Adaptable help based design will be exceptionally alluring for future expansion.