session 3 Software Requirement Specification

Software Requirement Specification

Introduction-

Purpose-

The purpose of Railway Reservation System is to create Reservation, Cancel Reservation, Viewing Train Information, Viewing Reservation Details, Updating Train Information, Updating Reservation Details and Generate Reports.

Definition -

This is a project, which is used to Book and Cancel Reservation and to update the Train and Reservation details.

Product & its functions –

The Product of this project is Railway Reservation System, which is to Book Tickets, Cancel Reservation, Viewing Train Information, Viewing Reservation Details, Updating Train Information, Updating Reservation Details and Generate Reports.

Benefits and Goals -

The Benefit of this project is to reduce the work of Reservation Clerk and it is easy to check the remaining seats present in the Train and easily view the Reservation Status of the Train and tells to the passenger. The Goals of this project is that, from any Railway Station we can Create Reservation, which is updated automatically in all the stations. Hence, there is no confusion to the Reservation System in all the stations to create the Reservation.

Overall Description-

Product Description –

·         The reservation system takes the detail from the passenger.

·         The reservation system checks whether the seats are remaining or not.

·         If seats are available, reservation clerk create the reservation and  updates the reservation details.

·         If seats are not available, he places the reservation in waiting list.

·         The reservation system cancels the reservation and update the reservation details.

·         The manager updates the train information and generates the report. 

Functional Requirements –

    Some of the examples of functional requirements are listed below—

  • Keeping records of affirmation of clients.
  • Storing and managing the data of items.
  • Keeping the day by day sell.
  • Storing the criticism/review given by the client.
  • Keeping insights regarding the item it is conveyed or not and so forth
  • Storing the things chosen by the client in the temporary storage.

  Non-functional requirements in this project are-

 Following Non-functional necessities will be there in the Insurance on web:

  • Secure access of private information (client's subtleties).
  • Twenty-four-7 accessibility.
  • Better and accurate segment configuration to improve execution at top time.
  • Adaptable help-based design will be exceptionally alluring for future expansion. 

Product Perspective-   It will empower us to manage the railway train info like their journey time, Arrival/Departure time, Seat availability and reservation billing and cancellation of the tickets.

Product Functions- It will have two users interface layers, first one is user interface and second one is Train management interface.

        The functionalities provided by the Railway Reservation System.

View Train Details: Provision should be given to see information related to the train schedules for the entire train network. The user should be able to see the train name, train number, boarding and destination stations, duration of journey etc.

Find Trains: The system will have a search function. User can request train based on starting and ending station from the database and the needful would be provided accordingly.

Book Ticket: the system will allow client to buy the train ticket from user interface. the system will show all the train info. the framework will show the date time and cost of the ticket. the framework will have confirmed booking button. At the instant when confirm booking button is pressed/clicked, the framework will provoke client to login or enlist account. If customer haven't login prompt customer to login and create account. The system will also ask the details such as Train no, starting destination, Arrival Destination, Booking date etc.

Transaction History: the customer can view all the transaction history from this function. All the payment details like any transaction failed, information about the money would be recorded here and whenever the user requests for it would be sent to the user.

 Update Train Info: Only the administrator or manager enters any changes related to the train information like change in the train name, train number, train route etc. in the system.

 Generate Report: Provision for generation of different reports should be given in the system. The system should be able to generate reservation chart, monthly train report etc.

Verify login: For security reasons all the users of the system are given a user id and a password. Only if the id and password are correct is the user allowed entry to the system and select from the options available in the system.

View Reservation Status: All the users should be able to see the reservation status of the train online. The users needs to enter the train number and the pin number printed on his ticket so that the system can display his current reservation status like confirmed, RAC or Wait – Listed.

 Cancel Reservation: A passenger wishing to cancel a reservation is required to fill a form. The passenger then submits the form and the ticket to the admin. The admin then deletes the entries in the system and changes the reservation status of that train. The clerk crosses the ticket by hand to mark as cancelled.

 

Users of Project:

User: This person uses this system to create reservation, cancel reservation, view reservation status, update reservation details, view train schedule.

Admin: This person uses this system to update train information and to generate reports.

Specific Requirements

Interface Requirements:

The interface requirements of Railway Reservation System include

·        Easy to Navigate.

·        Less Graphics

·        Display Error Messages and Relevant Dialogue Boxes.

·        Providing high security such that not to be modified by irrelevant users.

·        It must provide options such that (to reduce the input actions by users). 

User Requirements:

After a brief study of requirements of clients, the requirements of this system are given as follows:

·        Login information

·        Reservation details

·        Train details

Hardware Requirements:

The hardware requirements of this system is given by

·        8 GB RAM

·        512 GB SSD

·        Printer

·        LAN Cable 

Software Requirements:

The software requirements of this are as follows:

·        Windows 2000 OS

·        Browser required

·        Notepad++

·        SQL

Logical Database Requirements:

The following information is to be stored in the database

·        Passenger details

·        Reservation details

·        Train details

·        Login details

Basic Processing Actions of the System -

The basic actions that are performed by the system is given as follows:

·        Verification of user

·        Maintain Reservation details

·        Maintain Train detail


Comments

Post a Comment

Popular posts from this blog

Session 4: DFD, ERD, and Data Dictionary

Image
Session 4: (a) Draw DFDs up to appropriate levels for the RRS.  DFD: DFD is the abbreviation for Data Flow Diagram. The flow of data of a system or a process is represented by DFD. It also gives insight into the inputs and outputs of each entity and the process itself. DFD does not have control flow and no loops or decision rules are present. Specific operations depending on the type of data can be explained by a flowchart. 0 level,1 level and 2 level DFD for the RRS is given below: 0-LEVEL DFD- 1-LEVEL DFD-   2-LEVEL DFD- (b) Draw ERDs for the RRS. Describe the relationships between different  entities.  Entity Relationship Diagram: ERD is a graphical representation that depicts relationships among people, objects, places, concepts or events within an information technology (IT) system. E R DIAGRAM- (c) Design Data Dictionary for RRS.  Data Dictionary consists of database metadata. It has records about objects in the database . ...
Read more

Session 13

  Session 13: Develop “Railway Reservation System” as per specifications given in Sessions 1, 3,   4,5 and 6.   Project Proposal  The Project “Railway Reservation” deals with the automation of the reservation and enquiry of the railway reservation system.  It maintains all information starting from reservation to cancellation of tickets. It also acts as an enquiry system about the different trains available. It gives the details of the distance, arrival time and departure time of the different trains. The computerization is aimed at job simplification and reducing the manual work and effective record maintenance. Introduction The introduction of the Software Requirements Specification (SRS) provides an overview of the entire SRS purpose, scope, definitions, acronyms, abbreviations, references and overview of SRS.A Software Requirements Specification (SRS) - a requirements specification for a softw...
Read more

Session-1 Scope Statement for the Online Railway Reservation System

Scope Statement for the Online Railway Reservation System- The Railway Reservation System is used to Create Reservation, Cancel Reservation, Viewing/updating Train Information, viewing reservation status, generating reports, Updating/Viewing train schedule, updating reservation details, Managing journey time, Arrival/Departure time, Seat availability etc. online. This System will reduce the time and effort for going to railway office and applying for these facilities for transportation.   Reservation is created from any Railway Station which is updated automatically in all the stations. Hence, there is no confusion to the Reservation Clerk in all the stations to create the Reservation. This can be possible by maintaining Global Database. Representatives present at different stations can access the global database and can easily understand the remaining reservation seats. It provides the ability to create reservation from different places for a train and the clients can easily be ...
Read more