Requirement Analysis
Requirement Analysis
Requirement Analysis
Introduction
1.1 Purpose of Document
This is a Requirements Specification document for Railway Reservation System, a
Mini project in Database Management System. This Project contains Introduction to
Railways Reservation System. It is the computerized system of reserving seats of the
train in advance. It is mainly used for long routes. This document describes the scope,
objectives and goal of the new system. In addition to describing non-functional
requirements, this document models the functional requirements with use cases,
interaction diagrams, and class diagram. This document is intended to direct the
design and implementation of the system in an object oriented language.
Those who will primarily benefit from the new system and those who will be affected
by the new system include
Passengers:
Upon implementation of the new system, passengers will find site navigation,
bookings and cancelation and enquiry easier. Passengers will be able to
navigate through it easily and will be easy to see the updation and status of
their tickets.
Admin:
The new system will provide admins with more detailed, accurate and up-to-
date product information. They will be informed of potential customers more
quickly and they can easily see the availability of seats and if there is increase
of trains on a particular route.
1.5.2 Location
The system will be available to any passenger using the Internet in near future.
1.5.3 Responsibilities
2. Functional Requirements
1.User Satisfaction- The system should stand upto the user expectations and
should have a user friendly interface.
2. Response Time- The response of all operation should be good which can
be made possible by careful programming.
3. Non-Functional Requirements
1. Reliability
The system shall be completely operational for at least 90% of time
The backup of the system should be continuously maintained and updated to
reflect most changes.
The overall project depends on the reliability of separate components.
The overall stability of project depends on overall stability oof container and its
underlying operating system
2. Availability
The passenger should be able to access the status of his ticket and the final data
of his travelling.
The System should be available at all times , meaning the user can access it
easily. The access should be restricted by the down time of server on which the
system runs.
In case of hardware failure the backup of database should be retrieved to
maintain proper functioning of system.
3. Performance
The system should be able to support simultaneous passengers.
The system should be able to update information in database in real time
4. Security
The system shall provide protection to Passenger details and monetary
information.
Transaction data must be transmitted in encrypted form.
The system must automatically log out all customers after period of inactivity.
The system back end server should only be accessible to authenticated
management.
5.Supportability
The code and supporting modules of the system should be well documented.
Easy to understand
Train Ticket
Management Management
Railway
Reservation
System
Login
Management
Train
Train Generate
GenerateTrains
Trains
Management
Management Report
Report
Booking
Booking Generate
Management
Management Booking Report
Ticket
Ticket Generate Ticket
Management
Management Railway
Railway Report
Reservation
Reservation
System
System Generate Route
Route
Management Report
Login
Login Check User Login
Management
Management Details
System
SystemUser
User Generate System
Management
Management User Report
2 Level DFD-
Login to Check
Admin System Roles Of
Access