Railway Reservation Using Spiral Model
Railway Reservation Using Spiral Model
Railway Reservation Using Spiral Model
ON
SOFTWARE ENGINEERING TOPIC:ONLINE RAILWAY RESERVATION SYSTEM
DEPARTMENT OF INFORMATION TECHNOLOGY V.G.VAZE COLLEGE OF SCIENCE MITHAGAR RD,MULUND(E) MUMBAI 400081 DATE OF SUBMISSION: 24TH FEB 2010
The project of PRS was launched on 15th November 1985, over Northern Railway with the installation of Integrated Multiple Train Passenger Reservation System(IMPRESS), an online transaction processing system developed by Indian Railways in association with Computer Maintenance Corporation Ltd., at New Delhi. The objective was to provide reserved accomodations on any train from any counter,preparation of train charts and accounting of the money collected. The application was implemented in 1987 Mumbai,Chennai,Kolkata,Secunderabad subsequently.
PROBLEM DEFINITION:
Railway passengers frequently need to know about their ticket reservation status, ticket availability on a particular train or for a place,train arrival or departure details, special trains etc.. Customer information centers at the railway stations are unable to serve such queries at peak periods. The number of the reservation counters available to the passengers and customers are very less. On most of the reservation systems there are long queues, so it takes a long time for any individual to book the ticket. As now there are no call centers facilities available to solve the queries of the passengers.
ANALYSIS:
1. In Online Railway Reservation System,for booking the tickets online the intended user has to enter details like username and password. 2. Once the username and passwords are verified then he is allowed to enter the main system wherein he can select the destination, date and no of tickets.
3. For the purchase of the tickets he is asked for payment details (like credit card details etc).
4. The user is also provided with a provision of canceling the reservation where in the entire amount is credited back to his account. The analysis part also comprises of the UML diagrams that boost the program.
Customer communicationtasks required to establish effective communication between developer and customer.
Planningtasks required to define resources, timelines, and other project related information. Risk analysistasks required to assess both technical and management risks. Engineeringtasks required to build one or more representations of the application. Construction and releasetasks required to construct, test, install, and provide user support (e.g., documentation and training). Customer evaluationtasks required to obtain customer feedback based on evaluation of the software representations created during the engineering stage and implemented during the installation stage.
As the evolutionary process begins, software team performs activities that are implied by a circuit around the spiral in a clockwise direction, beginning at the center. The first circuit around the spiral might result in the development of a product specification; subsequent passes around the spiral might be used to develop a prototype and then progressively more sophisticated versions of software. Unlike other process models that end when software is delivered, the spiral model can be adapted to apply throughout the life of the computer software.
Every new step is dependent on the previous step and moves spirally outwards.
At any point in the system we can return back to the previous step. Because software evolves as the process progresses, both we and customers can better understand and react to the risks at evolutionary level.
In the case of errors we can easily trace the root cause of errors.
Spiral model is very realistic approach towards the process development.
system
Make a reservation
user
Verify payments
Update reservations
cancellation of reservation
administrator
SEQUENCE DIAGRAM:
:User
Log in Secure communication Enter date Request confirmation Enter desired destination Choose desired express Enter the no of tickets Request confirmation Confirm purchase {verify funds} Place order {execute order} {verify user} {verify date} :System
:Administrator
ACTIVITY DIAGRAM
Close transaction
Cancellation of reservation
Make payments
exit
User
Transaction Process
website
TESTING:
Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design, and code generation. The types of the testing are as follows: 1. Unit testing 2. System testing 3. Validation testing and etc etc. But however due to the time constraint we could not perform various types of testing. Hence we just applied alpha testing which is a part of validation test to our project.
CONCLUSIONS:
Our project is only the gist of the online reservation system. Due to time constraints it was not possible to incorporate all the concepts related to the topic. So the program created is just an instance of the Original Online Railway Reservation System.