Rail Way Ticket Reservation

Only available on StudyMode
  • Topic: Unified Modeling Language, Use case, Use case diagram
  • Pages : 9 (1970 words )
  • Download(s) : 144
  • Published : November 4, 2012
Open Document
Text Preview
2=HJ111

""&

Object Oriented Systems Analysis and Design (OOSAD)

15.3.3

OOA of Railway Ticket Reservation System
Assume that domain analysis is complete and DAD is ready for reference. The analyst also has a fair knowledge of the system and the system environment. For the sake of convenience and to reduce complexity at this stage in OOA, we are ignoring certain conditions, constraints and features that the real system may have. For example, we are not considering cancellation of tickets as a requirement. We assume all passengers irrespective of their type (senior citizen, military personnel, special category passengers etc.) are the same, and therefore are charged with the same fare. We begin with the statement of requirement of the system. ü System Requirement l The passenger has a prior knowledge of the reservation and ticketing system. The passenger arrives at the railway ticket counter and interacts with the counter clerk first through an enquiry and then follows the process of form filling, tendering, payment and collecting the tickets. l Passenger accepts the ticket or leaves the counter. l Passenger seeks information on fare, train timings and availability of tickets. l Passenger can have single ticket or multiple tickets. l Journey begins on a day and will be over with one break in between. l Passenger 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 Output of the system is ticket(s) with details. l The process is triggered through a form filled by the passenger detailing the requirements of tickets, train, date, etc. l A form is used for each train. If the journey requires use of multiple trains, separate forms are used for each train. ü Identify the Actors The actors in the system are the passenger, the counter clerk and the reservation system 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 user–actor who initiates the process and obtains the ticket(s), a goal of measurable value. The counter clerk is an active user–actor, who triggers the system and has the role of issuing 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 actor–user to ensure that ticket processing is done correctly and different system statuses are updated on issuing of tickets. This actor has an active role and responsibility at the back end. ü Develop Business Process Model – Reservation and Issue of Tickets Based on the system observation by the analyst, a high-level activity diagram is drawn modeling the process of reservation and issue of tickets to the passenger. The activity diagram brings everybody concerned with the system on the ground to a common understanding of the system as it functions.

Object Oriented Analysis (OOA)

+D=FJAH#

""'

We use this activity diagram of the process to develop use cases, which together achieves the goal of issuing the ticket. Fig. 15.3
Activity Diagram of Reservation and Issue of Tickets
Passenger Comes to the Counter Collects the Reservation Form & Writes Details Clerk Enters Form Details on the Screen Triggers Ticket Printing Process

Submits form to the Counter Clerk

Validates, Verifies Availability Not OK OK Triggers Fare Process, Arrives at the Fare Amount

Prints the Tickets

Form Modified

Not OK

OK

Issues Tickets

*We do not see this as
possibility in real world. Passenger may walk out of the system

Collects Fare Amount

Not OK *

Confirms OK with the Passenger Triggers Update Process

Attends To Next Passenger

ü Identify and Develop Use Cases

In the ticket reservation systems, users are the passenger, the counter clerk and the Reservation and Ticketing System (R&T...
tracking img