1. CASE STUDY ON SOFTWARE ENGINEERING TOPIC:ONLINE RAILWAY RESERVATION SYSTEM SUBMITTED BY: SHRUTI DHARMADHIKARI-06 TEJAL JADHAV-16 DEPARTMENT OF INFORMATION TECHNOLOGY V.G.VAZE COLLEGE OF SCIENCE MITHAGAR RD,MULUND(E) MUMBAI 400081 DATE OF SUBMISSION: 24 TH FEB’ 2010

2. WHAT IS SOFTWARE ENGINEERING? Software engineering is a layered technology. The bedrock that supports software engineering is a quality focus. The foundation for software engineering is the process layer. Software engineering process is the glue that holds the technology layers together and enables rational and timely development of the computer software. Software engineering methods provide the technical “how to’s” for building software. Methods encompass a broad array of tasks that include communication, requirements analysis, design , modeling, program construction, testing and support. Software engineering methods rely on a set of basic principles that govern each area of the technology and include modeling activities and other descriptive techniques.

3. INTRODUCTION TO THE RAILWAY RESERVATION SYSTEM: The Indian Railways (IR) carries about 5.5 lakhs passengers in reserved accomodation every day.The Computerised Passenger Reservation System(PRS) facilates the booking and cancellation of tickets from any of the 4000 terminals(i.e. PRS bookin window all over the countries). These tickets can be booked or cancelled for journeys commencin in any part of India and ending in any other part, with travel time as long as 72hours and distance upto several thousand kilometers. The project of PRS was launched on 15 th 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.

7. SPIRAL MODEL DIAGRAM:

9. Figure depicts a spiral model that contains six task regions: • Customer communication —tasks required to establish effective communication between developer and customer. • Planning —tasks required to define resources, timelines, and other projectrelated information. • Risk analysis —tasks required to assess both technical and management risks. • Engineering —tasks required to build one or more representations of the application. • Construction and release —tasks required to construct, test, install, and provide user support (e.g., documentation and training). When you encounter a difficult deadline that cannot be changed, the incremental model is a good paradigm to consider. 6 Figure depicts a spiral model that contains six task regions: • Customer communication —tasks required to establish effective communication between developer and customer. • Planning —tasks required to define resources, timelines, and other project related information. • Risk analysis —tasks required to assess both technical and management risks. • Engineering —tasks required to build one or more representations of the application. • Construction and release —tasks required to construct, test, install, and provide user support (e.g., documentation and training). • Customer evaluation —tasks required to obtain customer feedback based on evaluation of the software representations created during the engineering stage and implemented during the installation stage.

12. CLASS DIAGRAM: class a private: int c, n, a, i, s; char id[50]; char pasw[50]; char date[10]; char d1[15], d2[15]; public: getLogin(); train();

13. USE CASE DIAGRAM: user Enter user id and password system verify password and user id Make a reservation Verify payments Update reservations cancellation of reservation administrator

14. : User : Administrator Log in Secure communication {verify user} :System SEQUENCE DIAGRAM: Enter date {verify date} Request confirmation Enter desired destination Choose desired express Enter the no of tickets Request confirmation Confirm purchase Place order {execute order} {verify funds}

15. Verify credit cards detail Debit account Settle transaction Send confirmation Close transaction Send invalid notice (success) (invalid) ACTIVITY DIAGRAM

16. Online reservation system Enter user id and password Make reservation Confirm reservation Make payments Cancellation of reservation invalid For cancellation exit STATE TRANSITION DIAGRAM

17. Transaction Process User website 0 LEVEL DFD DIAGRAM:

18. Online train reservation system Enter userid and password verify userid and password Enter no of tickets 1 LEVEL DFD DIAGRAM: Enter express name Check for the availability of date Make purchases Enter date