OOAD

Assignment 1
Submitted by:
Kamran Aqeel Reg; No 14pwbcs0430
Sohial khan Reg; No 14pwbcs0424
Section A
Department CS&IT

Submitted to DR. Owais Mehmodi

Use Case Train Ticket reservation

Primary actor: Clerk
Stakeholders and Interests:
Clerk: Wants accurate, fast entry, and no payment errors, as cash
drawer short ages are deducted from his/her salary.
Traveler: Wants easy way of reservation, facility of online booking
and cash payment through credit card or online transfer. Also a facility
of cancellation of ticket in a specific time period
Company: Wants to accurately record transactions and satisfy
Traveler interests. Wants to ensure that Payment Authorization Service
payment receivables are recorded. Wants some fault tolerance to allow
record data even if server components (e.g., remote credit validation)
are unavailable. Wants automatic and fast update of accounting and
inventory.
Government Tax Agencies: Want to collect tax from every
Traveler. May be multiple agencies, such as national, state, and county.
Payment Authorization Service: Wants to receive digital
authorization requests in the correct format and protocol. Wants to
accurately account for their payables to the company.

Preconditions: Clerk is identified and authenticated.

 Success Guarantee (Postconditions): Booking is saved. Tax is
correctly calculated. Accounting and Inventory are updated. Commissions
recorded. Receipt is generated. Payment authorization approvals are
recorded.

Main Success Scenario (or Basic Flow):

1. Traveler arrives at reception or visits online to railway website
and reserve seat for his/her self.
2. Clerk checks the database to check if seats are available.
3. Clerk open new receipt form.
4. Clerk enter the travelers data.
5. Clerk repeats step 2-5 if the traveler need more tickets.
6. System record the data and calculate tax according to tax
rules and return the grand total as a receipt.
7. Clerk tells costumer total amount.
8. Traveler pays amount.
9. System presents receipt.
10. Traveler leaves/logout (in case he is booking online) with
tickets.
Extensions (or Alternative Flows):
1. At any time, System fails: To support recovery and correct accounting,
ensure all transaction sensitive state and events can be recovered from
any step of the scenario.

Clerk restarts System, logs in, and requests recovery of prior state.
System reconstructs prior state.
System detects anomalies preventing recovery
System signals error to the Cashier, records the error, and enters a
clean state.
Clerk starts a new sale

2. Invalid identifier:
System signals error and reject entry.

3. Traveler asks clerk for cancellation of ticket:

Cashier enters ticket number for removal from booked seats.
System cancel reservation of given ticket number. Sets the seat free
and update the database.
4. Discount:
 Traveler says they are eligible for a discount (e.g., employee, preferred
customer):

Clerk signals discount request.

Clerk enters Traveler identification.
System presents discount total, based on discount rules.

5. System Failure:
System detects failure to communicate with external tax calculation
system service:

System restarts the service, and continues.

System detects that the service does not restart.
System signals error.
Clerk may manually calculate and enter the tax, or cancel the booking.

6. Payment by Cash:
Clerk enters the cash amount tendered.
System presents the balance due, and releases the cash drawer.
Clerk deposits cash tendered and returns balance in cash to Traveler.
System records the cash payment.

7. Payment by Credit:
Traveler enters their credit account information.
System sends payment authorization request to an external Payment
Authorization Service System, and requests payment approval.
System detects failure to collaborate with external system: System
signals error to Clerk.
Clerk asks Customer for alternate payment.
System receives payment approval and signals approval to Cashier.
System receives payment denial: System signals denial to Clerk.
Clerk asks traveler for alternate payment.
System records the credit payment, which includes the payment
approval. System presents credit payment signature input mechanism.
Clerk asks Customer for a credit payment signature.
Customer enters signature.

Special Requirements:
An authentication device or scanner required to check the authenticity
of traveler to check whether he is not a terrorist.
 Touch screen Ul on a large flat panel monitor.
Text must be visible from 1 meter.
Credit authorization response within 30 seconds 90% of the time.
Somehow, we want robust recovery when access to remote services
such the inventory system is failing.

Frequency of Occurrence: could be nearly continues.

Open issues:
What are the tax law variations?
Explore the remote service recovery issue.
Must a cashier take their cash drawer when they log out?