Railway Reservation System PDF

Preview

Summary

Software EngineeringSubmitted By:-Keshav Gupta (2K18/CO/173)Lakshay (2K18/CO/183)Railway ReservationSystemOverviewIn this modern world of computer and AI(Artificial Intelligence) almost all the manual system has been replaced. For example consider amazon for delivery process Swiggy, Zomato for food ...

Description

Software Engineering

Submitted By:Keshav Gupta (2K18/CO/173) Lakshay (2K18/CO/183)

Railway Reservation System Overview In this modern world of computer and AI(Artificial Intelligence) almost all the manual system has been replaced. For example consider amazon for delivery process Swiggy, Zomato for food delivery and much more. The main advantage of this computerized world is it reduces human effort and time to a great extent. We are developing the “Online Railway Reservation System” with the help of model presentation even with reducing the drawbacks. We use the computer technology with the highspeed communication network. We interconnected railway offices administration and engineering offices online. To solve the problems of user. Now the users can connect through this system online via internet to get updated on every information related to railways.

Introduction: Current System India, With having larger population with the larger geographical size. There is very need for long distance transportation service. Long distance roads are not properly developed in India. Very large volume of traffic is carried out over long distance by the Indian Railways. It is very important for transportation facilities for long distance in India where long distance transportation is very common. This will reduce the time and effort for going to railway office and applying for this facilities for transportation. Like for ticket reservation a person goes to railway reservation office and stands in queue for their turn just for booking or reserving seats to spare the time we created Online Reservation system now we can hold, search or drop even assemble data about other train just by a tap or click. Need of proposed system: To diminish complexity of existing system. Successful administration of time. To make work simple, straightforward and blunder free. Compelling use of accessible asset. To improve the productivity and enhancement of administrations exercises.  Easy to use.  Intelligent graphical UI

    

Selection of Model: A software-process-model is a brief representation of how a software process works. It helps to develop a software as per under the functionality of the user keeps a sequence of steps followed for a good software. A process model is chosen based on the nature of the project and application, the methods and tools to be used for functionalities that are required as per user. For the Railway Reservation system we choose spiral model.

Spiral Model The spiral model is a very beneficial and efficient model. It is the combination of the prototyping model and the waterfall model. The spiral model is mostly used for large, Risky, expensive, and complicated projects as best suits for railway reservation system. A big advantage which is risk management is the highlight of this model, it is one of the best SDLC model available for the risk analysis and risk management at each part. User requirements can be changed at later phases so it is flexible as well. The steps in the spiral lifecycle model are follows:The system requirements are gathered in detailed from users. It can be done with gathering information from a number of users. 2. 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 applied during creation and alternatives are founded. This stage assists with recognizing and resolve all the potential risks in the undertaking development. If any uncertain functionality meets in requirements, with the sufficient data software proceeds, changes are made to meet the remove the uncertain data. 1.

With the help of the preliminary design first prototype of new system is developed. A second prototype is evolved as follows: 1. Evaluate the strength weakness and risks of first prototype. 2. Defining requirements for the second prototype. 3. Plan and design for the second prototype.

4.

Develop and test the second prototype.

Spiral Model:-

FUNCTIONAL REQUIREMENTS: In software engineering, a useful prerequisite characterizes an element of a product system or segment. A capacity is depicted as a bunch of data sources, the conduct of it and its yields.They might be estimations, specialized information, information control and handling and other explicit usefulness that show how a utilization case to be satisfied. Useful prerequisites portray what the product needs to do. They are regularly called Product features. The center of the prerequisite is the depiction of the necessary conduct, which must be a reasonable and intelligible portrayal of the necessary conduct. This conduct may come from authoritative or business rule, or it very well might be found through elicitation meetings with clients, partners and different specialists inside the association. Programming necessities must be clear, right and unambiguous, explicit and obvious.

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 systems designing and specifications, non-functional prerequisites are prerequisites which indicate models that can be utilized to pass judgment on the activity of framework, as opposed to explicit practices. Non-functional necessities are regularly called characteristics of a framework. Different expressions for non_functional prerequisites are "imperatives", "quality ascribes", "quality objectives" and "quality of administration necessities" . Characteristics of non functional requirements can be separated into 2 fundamental classifications: 1. Execution characteristics, for example, security and convenience, are perceptible at runtime. 2. Evolution characteristics, for example, extensibility and versatility, encapsulate in the static structure of the product framework. The nonfunctional requirements in this project are:Following Non-functional necessities will be there in the Insurance on web: I). Secure access of private information (client's subtleties). ii). Twenty four-7 accessibility. iii). Better and accurate segment configuration to improve execution at top time. iv). Adaptable help based design will be exceptionally alluring for future expansion. Non-func. req. characterizes system properties and imperatives. It emerges through client needs, due to spending requirements or hierarchical approaches, or because of the outer factors, for example, well-being guidelines, protection enlistment, etc. Different other Non-practical necessities are: 1.Security 2.Reliability 3.Maintainability 4.Portability 5.Extensibility 6.Reusability 7.Application Affinity/Compatibility 8.Resource Utilization

Software Requirements Specification for

RAILWAY RESERVATION SYSTEM Table of content 1. Introduction 1.1 Purpose 1.2 Document Conventions 1.3 Intended Audience and Reading Suggestions 1.4 Product Scope 1.5 Scope 2.Overall description 2.1 Product Perspective 2.2 Product Function 2.3 Guest Interface 2.4 Train Management Interface 2.5 Operating Environment 2.6 Operations 2.7 User Interface 2.8 Hardware Interface 2.9 Software Interfaces

2.10 Assumptions, Dependencies & Limitations 3.System Features 3.1 Functional Requirements 3.1.1 View Train Details 3.1.2 Search Train 3.1.3 Create Account 3.1.4 Customer Login 3.1.5 Purchase Ticket 3.1.6 Purchase History 3.1.7 Login Function 3.1.8 Staff Module 3.1.9 Reservation Module 3.1.10 Ticket Module 3.1.11 Membership Module 3.1.12 Train Module 3.1.13 Pricing Module 3.1.14 Availability Module 3.1.15 Branch Module 3.1.16 Report Module 3.1.17 Access Type

4.

External Interface Requirements 4.1 User Interface 4.2 Hardware Interfaces 4.3 Software Interfaces 4.4 Communication Interface

5. Non-functional Requirements 5.1 Performance Requirements 5.2 Safety Requirements 5.3 Security Requirements 5.4 Design Constraint

1.1 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.

1.2

Document Conventions:

This Document was created based on the IEEE template for System Requirement Specification Documents.

1.3 INTENDED AUDIENCE AND READING SUGGESTIONS: The different types of readers are ฀ Customers ฀ Developers ฀ Management ฀ Passengers ฀ Counter clerk 1.4 Product Scope: The extent of this system in making Reservation is that, from any Railway Station we can Create Reservation, which is refreshed naturally in all the stations. Subsequently, there is no perplexity in the mind of the Reservation Clerk in all the stations to make the Reservation. This can be conceivable by keeping up the Global Database. Representatives present at various stations can get to the worldwide information database and the clients can without much of an effort or stretch can easily be able to book reservation seats. It provides various options and diversity to the customer as well as more time to book tickets.

1.5 Scope: The extent of venture characterize the undertaking achievability the innovation , account , time and assets best characterize in innovation whether the imperfections can be decreased in the task and up which level monetarily, climate the general venture cost is moderate. Time portrays whether the projection completing point will be accomplish on schedule or before time assets required should be accessible at the pace of cost and time.

2.OVERALL DESCRIPION

2.1 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. 2.2 PRODUCT FUNCTIONS: It will have two users interface layers, first one is user interface and the second one is Train Management Interface.

2.3 GUEST INTERFACE: ฀ View_Train_Info ฀ Search_Train ฀ Create_Account ฀ Customer_Login ฀ Purchase_Ticket ฀ Purchase_History

2.4 TRAIN MANAGEMENT INTERFACE: ฀ Login_Function ฀ Staff_Module ฀ Reservation_Module ฀ Ticket_Module ฀ Membership_Module ฀ Train_Module ฀ Cost_Module ฀ Availability_Module ฀ Branch_Module ฀ Report_module ฀ Access_Type

2.5 OPERATING ENVIRONMENT: ฀ Linux-8 ฀ Windows-7 ฀ Windows-8 ฀ Windows-10 ฀ Mac Os

2.6 OPERATIONS: ฀ Book at ticket counter from 6 am to 11 pm anytimr. ฀ Book well before 50 days of travel. ฀ One-form for 4 people only. ฀ To spare time and long lines of people at the booking counter, online reservation is a great tool.

2.7 User Interfaces: The system will give an assistance (clarification) link from each showed HTML page to disclose how to utilize that page. The Web page of RRS will allow total route, train choice, ticket reservation and ticket/train data queries using input devices be it keyboard, mouse or touch screen in Smart-phones.

2.8 Hardware Interfaces: Nothing special Interface is required.

SYSTEM DESIGN USECASE ANALYSIS: Use Case Analysis is an article situated technique for planning data frameworks by separating necessities into client capacities. Each case is an exchange or grouping of occasions performed by client. Use cases are concentrated to figure out what items are needed to achieve them and how they connect with different articles.

GOALS OF USE CASE ANALYSIS: Design system from user’s perspective. Communicate system behavior in user terms.

CHARACTEISTICS OF USE-CASE ANALYSIS: USE-CASE: The certain ways in which the system is being used. Each use case represents a “complete idea” or end-to-end transaction of user/server request.

SOME KEY COMPONENTS OF USE CASE ANALYSIS: ACTORS: In software model actors are basically people who interact with the system in any way. Each actor has a different purpose and one serves the purpose for the other one. They are interdependent on each other. CONNECTIONS: Relationship from actors to use cases. RELATIONSHIPS: Links among actors or among use cases.

DATA FLOW DIAGRAM : DFD graphically speaking to the capacities, or cycles, which catch, control, store, and convey information between a framework and its current circumstance and between segments of a framework. The visual portrayal makes it a decent specialized device among User and System creator. Structure of DFD permits beginning from a wide outline and extend it to an order of definite charts. DFD has regularly been utilized because of the accompanying reasons: 

Logical flow of information in the system



Determination of actual system development specifications.



Easable in maintaining records.



Foundation of manual and automated system requirements

Level-0 DFD

LEVEL-1 DFD

Different Functionalities in the system • View Train Details: The system will help users or guests to see timings, PNR number, Train Name , Journey time etc of trains.

• 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.

•

Sign up: the system will request the user to Register an account in the system to proceed further for the reservation. In the registration process all the user’s details will be recorded and saved in the database. The details to be entered are listed below as follows:

a. Username b. Password c. Confirm Password d. First_name e. Last_name f. Card_number g. Address h. Zip_code i. City j. State k. Country l. Mobile_no.

• Sign In: When the user has already registered he/she just needs to enter the username and password which he/she has created during registration process. The entered details would be requested from the database server if it is found the user will be logged in to the system and if the entered details are wrong the database server will not be able to find the details and would prompt invalid details or record does not exist. • 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 confirm 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 Quota(General OR Tatkal), 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 etc would be recorded here and whenever the user requests for it would be sent to the user. • Staff Login: The system will allow only staff username and password to access the system. Access to this module is decided by account-type and branch/department address. When the staff has been logged in the system admin will have given the permission to the staff to perform CRUD operations. CRUD means Create, Read, Update and Delete. Railway administration will have to login first to get to this module. the system admin has the permission to add staff, update staff and erase staff. the system will request the following details to be entered for the record : a. Staff_Username b. password c. Account d. First_Name e. Last_Name f. Address g. City h. State

• Reservation Module the system will permit counter representative, station director and station manager of the specific station to get to this module. They ought to login first. The framework will restrict the admittance to branch level in sequential manner.

TESTING:

We have done Black-Box testing only. FORM NAME

INPUT

MAIN MENU FORM

Menu Option

TICKET AVAILIBILITY FORM RESERVATION FORM

CANCELLATION FORM

EXPECTED OUTPUT

Required form must be displayed. Train route or Train seats Train name availability must be displayed. Ticket must Personal details Were be booked Entered and database updated. Ticket must Ticket number were be cancelled entered and database must be updated.

ACTUAL OUTPUT

STATUS

Required form was displayed. Train seats availability are displayed.

pass

Ticket was booked and database was updated. Ticket was cancelled and database must be updated.

pass

pass

pass

We have used Robustness testing technique in the following tests: Robustness testing- It is just an extension of boundary value analysis. What happens in this is we assume a single value fault assumption in which we chose a value of a test case outside the domain of the input that is just above maximum and just below minimum which was not the case in boundary value analysis. A bunch of invalid data sources or odd/distressing climate is set up. Now and then it so happens that on giving certain data sources the program may crash . It gets critical to catch those mistakes and amend it as per the prerequisite determinations. Consequently reasonable experiments are created to perform testing in a proper test climate. There are different ways to deal with this testing strategy.Robust test cases are 6n+1....