Rail Way Ticket Reservation

purpose lie corpses outline and Design (OOSAD) 15. 3. 3 OOA of Railway shred reserve agreement Assume that domain analysis is complete and DAD is ready for reference. The analyst also has a fair knowledge of the system of rules and the system environment. For the sake of convenience and to reduce complexity at this stage in OOA, we be ignoring certain conditions, cons dogts and features that the real system whitethorn crap. For example, we are not considering cancellation of fines as a sine qua non. We assume all passengers irrespective of their type (senior citizen, military personnel, additional category passengers etc. are the homogeneous, and therefore are charged with the same uttermoste. We begin with the statement of requirement of the system. u System Requirement l The passenger has a prior knowledge of the gamelog and ticketing system. The passenger arrives at the railway ticket incompatible and interacts with the homecoming clerk first by dint of an doubtfulness and then follows the address of arrive at filling, tendering, allowance and collecting the tickets. l rider accepts the ticket or retracts the counter.l passenger adjoinks information on out-of-the-way(prenominal)e, train timings and availableness of tickets. rider can get single ticket or multiple tickets. l Journey begins on a day and exit be over with unmatchable break in in the midst of. l rider is identified by name, age, sex and address. l Trains are identified by name and number. l No receipt is issued for money transacted. l outturn of the system is ticket(s) with details. l The process is triggered through a form change by the passenger detailing the requirements of tickets, train, booking, etc. l A form is utilizationd for distributively train. If the journey requires office of multiple trains, separate forms are used for each train. delineate the Actors The agents in the system are the passenger, the counter clerk and the reservation sy stem consisting of form processing, reservation, fare computation, ticket processing, ticket printing, collection of fare amount and posting as sub-systems. The passenger is a passive substance abuseractor who initiates the process and obtains the ticket(s), a goal of mensural value. The counter clerk is an active useractor, who triggers the system and has the role of publicize the tickets with the responsibility of collecting the correct fare amount from the passenger, which is a measurable value.Predesigned and deployed ticket reservation system at the back end is a system actoruser to ensure that ticket processing is do correctly and unalike system termes are updated on issuance of tickets. This actor has an active role and responsibility at the back end. u let Business surgical procedure Model mental reservation and Issue of tag ends Based on the system observation by the analyst, a high-level operation plot is drawn modeling the process of reservation and issue of tickets to the passenger. The activity draw put downs everybody concerned with the system on the ground to a common reason of the system as it functions. tendency point Analysis (OOA) +D=FJAH We use this activity diagram of the process to develop use plates, which together achieves the goal of issuing the ticket. Fig. 15. 3 Activity Diagram of Reservation and Issue of Tickets rider Comes to the foreclose Collects the Reservation Form Writes Details shop assistant graves Form Details on the Screen Triggers Ticket Printing work out Submits form to the foretell shop assistant Validates, Verifies handiness Not OK OK Triggers recognise act upon, Arrives at the hail Amount Prints the Tickets Form Modified Not OKOK Issues Tickets *We do not see this as possibility in real world. Passenger may paseo out of the system Collects Fare Amount Not OK * Confirms OK with the Passenger Triggers Update Process Attends To Next Passenger u Identify and Develop utilise Cases In the t icket reservation systems, users are the passenger, the counter clerk and the Reservation and Ticketing System (RT System). Take each user and identify the roles played, which would lead us to identify the roles played, which, in turn, would lead us to an identification of use case. Table 15. shows the result of the process of identifying the use cases. The system has three users, eight roles and eleven use cases. To illustrate the process of identifying the use cases, let us take the passenger (a user of the system). A passenger as a user may play one or more of three roles. The roles are 1. Enquiring about the availability of tickets on token dates to a destination and the fare per ticket. The role is enquiring. 2=HJ111 Object oriented Systems Analysis and Design (OOSAD) Table 15. 1 Users? Roles? Use Cases. User l Role l l lUse case l l l l l l l l l Passenger Enquiry Reservation and ticketing Cancellation Form data entry Requisition mainframe Ticket processor Data manager Sys tem server communicate ticket availability and other details. Reserve seats and berths, tickets Cancel tickets Enter Reservation Requisition Form Process requisition for booking Process ticket to print Submits ticket data for updation Process reservation data, process ticketing process cancellation Update the status by date, train, etc. l regaining clerk l l l l l Reservation and ticketing system l 2.Reserving the ticket(s) on a particular train on particular date for a destination by requisitioning through a reservation form The role is reserving and booking tickets. 3. Cancelling the tickets after issuing and payment The role is cancelling. As explained in the case of passenger, the roles are use cases. Similarly, one can probe into the roles and use cases for counter clerk and reservation and ticketing system. u Draw Interaction Diagrams Interaction diagrams are used to show the interactions between user/actor and the system. Use case is a scenario that develops through interac tion.Let us model different scenarios through interaction diagrams Use Case enquiring on ticket availability 1. Passenger submits information about the date and train, and requirement of tickets to the counter clerk 2. Clerk checks the availability of tickets on the date and train. 3. Communicates the availability status to the passenger. 4. If OK, the passenger proceeds to book the ticket through a requisition form. 5. If not OK, the passenger changes the date or train and requests availability. 6. step 2 to 4 are repeated. Figure 15. 4 shows the steps in the activity diagrams of use case question to issue of Tickets. Object Oriented Analysis (OOA) +D=FJAH Fig. 15. 4 Enquiry to Issue of Tickets Passenger Tells get wind Train and Tickets Data Entered into RT System Not acquirable Puts New Date and Train RT Checks Availability Passenger Exits Available Fills Requisition Form RT Processes the Form Prints Tickets Tickets Issued and Fare Amount Collected Let us draw use case scenar ios in use case diagrams for actor passenger. Use Case enquiry Fig 15. 5. Here use case goal is to convey the ticket availability status to the passenger on the requested date and train.If the status is available, the passenger proceeds to book the ticket or may leave the counter. If the status is not available, the passenger may leave the counter or seek availability for a new date or new train. l 2=HJ111 Object Oriented Systems Analysis and Design (OOSAD) Fig. 15. 5 Use Case Enquiry Enquiries on Availability Enters Requested Data in R&T System Passenger Uses R&T System to Check Reservation Counter Clerk Informs the attitude on Availability l Use Case reservation and ticketing Fig. 15. 6. Writes Reservation Requisition Form & SubmitsFig. 15. 6 Use Case Reservation and Ticketing Passenger Form Data Entered Form Processed for Reservation & Ticketing Triggers Ticket Printing Collects Fare Amount and Issues Ticket Uses R&T System Uses Uses Reservation Counter Clerk Updates R&T Ticket Status Steps involved in this use case are 1. Passenger writes reservation requisition form. 2. Submits to the counter clerk. 3. Counter clerk calls Form screen. 4. Counter clerk enters form data. 5. Triggers R and T processing. 6. On OK processing, triggers ticket printing. 7. Issues ticket to passenger. . Update the system status. So far we have realized two of the most common and frequently used use cases, i. e. enquiry and reservation and ticketing. The following use cases can be simulate on similar lines. l Cancellation l Process reservation data Object Oriented Analysis (OOA) l l +D=FJAH Form data entry l Process ticketing Form processing l Process cancellation l Ticket printing l Status updation When the analyst has end all use cases in the system, s/he has described and modeled the requirement of reservation and ticketing system.It is possible that in first go s/he may not be able to identify actors and hence use cases. But s/ he will come crosswise their presence in t he modeling exercise, and will then go back and analyse further to introduce more actors and use cases. OOA is an intuitive process. Use casedriven OOA up till now has given us broad system requirements in terms of use cases. The OOA model development use cases is to be packaged to model the system. Figure 15. 7 shows the encase of use cases considered in the R and T system.Fig. 15. 7 R and T System Packaging RT System Enquiry Ticketing Ticket Availability Processing and Printing Reservation Uses Uses Cancellation Reserving Seats Cancellation and Refund Process Realise that though there are eleven use cases, we have grouped them under four major use case groups, videlicet l Enquiry l Ticketing l Reservation l Cancellation The stay use cases are sub-use cases, or, in other words, these four use cases are further decomposed to bring uncloudedness to main use case scenario.How umteen case scenarios are necessary to represent the system and then to compose out the requirement? The re are no set rules or guidelines on this point. More use cases may not necessarily bring better understanding or more clarity. A lot depends on users and developers level of comfort. What is definitely required is a use case for each major scenario that is, for enquiry, reservation, ticketing and cancellation. Use cases for different scenarios arising out of smaller input variations make not be modeled.For example, cancellation could be part of a journey, 2=HJ111 Object Oriented Systems Analysis and Design (OOSAD) reduced number of tickets and so on. Amongst atomic number 23 recommended processes of analysis, use casedriven analysis for ascertaining system requirement is considered beat out as it considers users perspective of the system. When the system is modeled into different case scenarios it not only goes down to the level of function and features, but also reveals relationships and behaviours amongst different system components.Each use case scenario is an instance in th e system that has clarity regarding goals and how they are to be achieved. The system can be decomposed from major use case at higher level going down to last(a) level. This means that lower level use case scenarios together prepare the major scenario. In use casedriven analysis, so far we have only understood in addition to domain knowledge. l System scope (enquiry, reservation, ticketing and cancellation) l System players (users, actors) l Major functions and processes ground as use case scenarios. Some idea on publicity system components for deployment. l System requirements at functional and process level. In short, so far in OOA, we have reached to some extent a situation in which the requirement analysis made so far can be put into a formal RDD document. We still have not reached the specifications level. This is possible when we go further, identifying classes, their relationship, attributes and methods. Use casedriven analysis, displayed in use case models, is a basis for moving into the step of identifying classes and conception classes.