Section 2. Software Requirements Analysis CILO2 (20 Marks) Case study: High-speed Train Ticketing System When an Adult Customer wants to buy a high-speed train ticket through online booking system, the conduct ticket booking use-case/function usually includes two use-cases/functions: the consumer will request the desired type of tickets and payout those tickets. + For the request ticket use-case, the consumer should specify the price type (for example, business seat, first-class seat or second-class seat). What's more, IF the customer requests specific location type (for example, window seat or aisle seat), THEN the system should then book the desired location type seat. After all the selections are completed (Note that the customer can choose multiple tickets), he/she may proceed to the Checkout use-case, which will include (1) Calculate the total amount, and then (2) proceed to the Payment screen, where he/she will be given two options: (hint: use-case inheritance): a. PayByOctopus, the inserted cash will be validated by a OctopusValidation System b. PayByCreditCard, the inserted credit card will be processed by a CardPaymentSystem In both two use-cases, IF any error occurs, THEN the system must be able to handle it via ExceptionHandling, there are three different error exceptions (hint: use-case inheritance):- a. TransactionAbort (i.e. the customer chooses to cancel without completing the transaction) b. OutOfStock (i.e. the booking system runs out of Tickets) C. OtherErrors (i.e. this is to handle any other error not covered above) IF the payment is successfully completed, THEN it will issue the purchased tickets. The customer can now pick up the ticket(s) purchased. A. Draw a complete use case diagram (10 Marks) Based on the above, draw a use case diagram for Ticketing System. Whenever possible, your use case diagram MUST use > or > to provide a good use case diagram. H B. Requirements Specifications (10 Marks) Based on the same case study described above, complete the following table from step 3 to describe the Request ticket use case under typical course of events, and alternative course of events. The situation involves the Customer actor. Note that you should consider "OutOfStock and TransactionAbort exception at the Alternative course of events. Use Case Name: Request ticket Actor(s): consumer Description: This use case describes the process of a customer request the desired ticket type to the system Reference ID: HK-TICKETING-1.04 Typical course Actor Action System Response of events: Step 1: The consumer shows the intention of booking the ticket Step 2: The system asks for the price type of the ticket Step 3: Step 4: 4 Step 5: - Alternative course of events: Precondition: Postcondition: The consumer shows the intention of booking the tickets Section 2. Software Requirements Analysis CILO2 (20 Marks) Case study: High-speed Train Ticketing System When an Adult Customer wants to buy a high-speed train ticket through online booking system, the conduct ticket booking use-case/function usually includes two use-cases/functions: the consumer will request the desired type of tickets and payout those tickets. + For the request ticket use-case, the consumer should specify the price type (for example, business seat, first-class seat or second-class seat). What's more, IF the customer requests specific location type (for example, window seat or aisle seat), THEN the system should then book the desired location type seat. After all the selections are completed (Note that the customer can choose multiple tickets), he/she may proceed to the Checkout use-case, which will include (1) Calculate the total amount, and then (2) proceed to the Payment screen, where he/she will be given two options: (hint: use-case inheritance): a. PayByOctopus, the inserted cash will be validated by a OctopusValidation System b. PayByCreditCard, the inserted credit card will be processed by a CardPaymentSystem In both two use-cases, IF any error occurs, THEN the system must be able to handle it via ExceptionHandling, there are three different error exceptions (hint: use-case inheritance):- a. TransactionAbort (i.e. the customer chooses to cancel without completing the transaction) b. OutOfStock (i.e. the booking system runs out of Tickets) C. OtherErrors (i.e. this is to handle any other error not covered above) IF the payment is successfully completed, THEN it will issue the purchased tickets. The customer can now pick up the ticket(s) purchased. A. Draw a complete use case diagram (10 Marks) Based on the above, draw a use case diagram for Ticketing System. Whenever possible, your use case diagram MUST use > or > to provide a good use case diagram. H B. Requirements Specifications (10 Marks) Based on the same case study described above, complete the following table from step 3 to describe the Request ticket use case under typical course of events, and alternative course of events. The situation involves the Customer actor. Note that you should consider "OutOfStock and TransactionAbort exception at the Alternative course of events. Use Case Name: Request ticket Actor(s): consumer Description: This use case describes the process of a customer request the desired ticket type to the system Reference ID: HK-TICKETING-1.04 Typical course Actor Action System Response of events: Step 1: The consumer shows the intention of booking the ticket Step 2: The system asks for the price type of the ticket Step 3: Step 4: 4 Step 5: - Alternative course of events: Precondition: Postcondition: The consumer shows the intention of booking the tickets
