1 Case Study Purchase Ticket 2 Purchase Ticket

  • Slides: 8
Download presentation
1 Case Study: Purchase Ticket

1 Case Study: Purchase Ticket

2 Purchase Ticket by Check Use case Actor: Customer (initiator), clerk Purpose: Reserve seats

2 Purchase Ticket by Check Use case Actor: Customer (initiator), clerk Purpose: Reserve seats on an airplane and capture their check payment. Overview A customer arrives at the counter requesting to purchase tickets. The clerk finds a suitable flight and reserves seats on it for himher. The customer pays for the tickets with check. When done, the customer leaves with purchased tickets Type: Primary and Essential

3 Expanded Use Case Format: Use Case: Purchase Ticket by Check Use case Typical

3 Expanded Use Case Format: Use Case: Purchase Ticket by Check Use case Typical course of actions:

4 Expanded Use Case Format: Use Case: Purchase Ticket by Check Use case Typical

4 Expanded Use Case Format: Use Case: Purchase Ticket by Check Use case Typical course of actions: Alternatives: Line 3, if there are no available flights on the specified date, the system displays flights on the day before and the day after. Line 7, if the customer asks for more tickets than seats available on the chosen flight; ask himher to change either flight or number of tickets.

5 Conceptual Model: What are the objects (concepts) the real things in my domain

5 Conceptual Model: What are the objects (concepts) the real things in my domain ? Candidate concepts: • • • • Customer Ticket Clerk Dep_city Des_city Date Flight info Num of passengers Passenger Flight class Sale transaction. seat • • • Special Request: handicap access, meal Airline Total Check Travel agency Customer ID

6 Conceptual Model: What are the objects (concepts) the real things in my domain

6 Conceptual Model: What are the objects (concepts) the real things in my domain ? Candidate concepts: • • • • Customer (Concept) • Special Request: handicap access, meal Ticket (Concept) (Attribute or concept ? ! ) Clerk (Concept) • Airline (flight Attribute or concept ? ! ) Dep_city (Flight Att) • Total (attribute of sale transaction or derived ) Des_city (Flight Att) • Check (attribute of sale transaction or concept Date (Flight Att) or payment concept) Flight (Concept) • Travel agency Flight info • Customer ID (customer Att) Num of passengers Attribute of ? or derived ? Passenger ( same as customer) because passenger names not specified in this use case Flight class (Ticket Att) Sale transaction. (Attribute or concept ? ! ) Seat ? ?

7 Conceptual Model: Clerk_id Name Customer Ticket Cus_id Name Phone num Pass_name Class Handicap

7 Conceptual Model: Clerk_id Name Customer Ticket Cus_id Name Phone num Pass_name Class Handicap Meal Price Check Sale Transaction check_id Amount Date Time Airline Flight name Num Dep-city Des-ciyt Date Seat S_num status

8 Conceptual Model: Clerk_id Name Customer Ticket Name Phone num Pass_name Class price Cus_id

8 Conceptual Model: Clerk_id Name Customer Ticket Name Phone num Pass_name Class price Cus_id 1 1 Involved in requests * * Check check_id Amount 1 1 Paid by Airline 1 Belongs to Sale Transaction Seat Date Time Handicap meal * Is_complete S_num class Book_status * Flight Associates with 1 name 1 has * * Num Dep-city Des-ciyt Date includes 1