Page 130 - DCAP308_OBJECT_ORIENTED_ANALYSIS_AND_DESIGN
P. 130

Object Oriented Analysis and Design




                    Notes


                                     Case Study  Problem Statement for Railway Reservation System


                                          oftware has to be developed for automating the manual railway reservation system.
                                          The system should be distributed in nature. It should be designed to provide
                                     Sfunctionalities as explained below:
                                     1.   Reserve Seat: A passenger should be able to reserve seats in the train. A reservation
                                          form is filled by the passenger and given to the clerk, who then checks for the
                                          availability of seats for the specified date of journey. If seats are available then the
                                          entries are made in the system regarding the train name, train number, date of
                                          journey, boarding station, destination, person name, sex and total fare. Passenger is
                                          asked to pay the required fare and the tickets are printed. If the seats are not available
                                          then the passenger is informed.
                                     2.   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 clerk. The clerk 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.
                                     3.   Update Train Information: Only the administrator enters any changes related to the
                                          train information like change in the train name, train number, train route, etc. in the
                                          system.

                                     4.   Report Generation: 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.
                                     5.   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.
                                     6.   View Reservation Status: All the users should be able to see the reservation status of
                                          the train online. The user 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.
                                     7.   View Train Schedule: 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.

                                     Question
                                     Discuss the case.
                                   Source: http://www.egyankosh.ac.in/bitstream/123456789/16412/3/SECTION%201.pdf

                                   10.3 Summary

                                       System conception is considered as a requirement analysis phase.

                                       Requirements describe how system behaves from the user’s point of view. True customer
                                       requirements should be separated from design decisions.
                                       Elaboration is the point where you want to have a better understanding of the problem.




          124                               LOVELY PROFESSIONAL UNIVERSITY
   125   126   127   128   129   130   131   132   133   134   135