Possible Pre-conditions for the Check Availability of Seats - Essay Example

Use case and Activity diagram Part A a. Identify preconditions and post conditions for this use case. Use case preconditions This section will outline some of the possible pre-conditions for the Check Availability of Seats use case. Precondition 1 To check “Availability of Seats” user must provide the customer details. Then system will create a customer profile through system check for availability of seats. In case of unavailability of customer details system shows a message “insert all the possible details”. Precondition 2 To check “Availability of Seats” user needs to enter the customer’s final destination for excursion. In case of destination that is not in the company tour list, system will deny the request to proceed further. Precondition 3 To check “Availability of Seats” user must enter number of possible seats that he/she wants to book for the tour. In case of unavailability of user requested seats system will show an error message to enter the number of needed seats. Precondition 4 To check “Availability of Seats” user needs to open the system section that is related to the booking of seats. In that section user needs to take care of all parameters regarding the data validity. Use case post conditions This section will outline some of the possible post-conditions of the Check Availability of Seats use case. Post condition 1 In case of unavailability of number of seats system will send a message to save the request. In this case customer request will be processed later when seats are available regarding the any excursion. Post condition 2 In case of any wrong entry in the system data fields, system will send an error message and indication of wrong values need to be resolved. Post condition 3 In case of bus unavailability system will send the request to pending (waiting) list that will be preceded later on system user confirmation. Post condition 4 To check “Availability of Seats” user needs to fill all the fields using a proper way. In case of any wrong entry system will show an error message. b. Write the main success scenario for this use case using the two-column format. Actor Intention System Responsibility 1. Checking available seats for an Excursion I. Check the seats in bus II. Indicate available seats 2. Entering new customer record I. Check the record validity II. Save record III. Update record 3. Booking for a new customer I. Checking seats availability II. Saving request III. Issuing invoice IV. Update record 4. Send out invoices I. Calculate cost II. Print invoice III. Record payment details 5. Payment I. Validate customer record II. Record payment details III. Issue booking details IV. Update record 6. Cancellation I. Validate booking details II. Check Payment details III. Cancel request IV. Update record c. Write at least one alternative (extension) scenario with success end condition and at least one alternative scenario with fail end condition for this use case. Below there are some of the alternative scenarios for the system regarding Check Availability of Seats use case. A#1- In case on unavailability of 50 passengers seats bus user can select 70 passenger seats bus for reservation. A#2- In case of exceeding number of 50 passengers seats user can reserve the seats in 70 passengers seats bus. A#3- In case of new bus assignment booking clerk needs to consider the old pending requests of the customer regarding the reservation. b. Write a complete description use case (including the main success scenario and all identified extensions) using the modified Cockburn template. Use-Case Use-Case# 1.0 Use case Title Check Availability of Seats Description This use case is for checking the availability of the seats for the excursion. In this use case system is intended to check the availability of the bus seats, that involves the checking the pre-established reservation for the bus tour. Actors Primary Actor: Booking Clerk Secondary Actor: Customer, Visitor, Any common person Assumptions The main assumption regarding this use case that user has already filled the whole information about the customer and system allows him to proceed further. Failed End Condition In case of wrong parameters regarding the customer and tour program displays the error message and exits. DESCRIPTION Steps Description 1 User opens the system 2 Enters the customer details 3 Enters the customer tour details 4 Check for the availability of seats 4a Check for bus available for specific destination 4b Add new reservation 5 If bus or seat not available 5a Add new bus 5b Book seat Issues - In case of any wrong entry regarding the customer information system will be not able to proceed further. Use case 2. Draw an activity diagram for the Check Availability of Seats including all identified scenarios. Part II 1. Draw an activity diagram for the use case Cancel Booking. 2. Analysis the case study The Road Adventure Company. Identify significant events and use cases that are system’s responses to these events. Present your findings in a table. No System Event Use Cases 1 Customer Booking Request Booking Use case 2 Adding customer details Booking Use case 3 Checking Seats availability Request Check Availability of Seats Use case 4 Change booking Request Check Availability of Seats Use case 5 Invoices Processing request Booking Payment Use case 6 Payment request Booking Payment Use case 7 Cancellation Request Cancel Booking 8 Processing wanting list processing Check Availability of Seats Use case 9 Request for bus and tour information Booking Use case Bibliography Hofmeister, C., Nord, L.R. & Soni, a., 1999. Describing software architecture with UML. In in Proceedings of the TC2 1st Working IFIP Conference on Software Architecture (WICSA1). San Antonio, TX, USA, 1999. Jawadekar, W.S., 2004. Software Engineering: Principles and Practice. New York: McGraw Hill. Pressman, R.S., 2001. Software Engineering: A Practicioner's Approach, 5th Edition. London: McGraw Hill. Sage, P., Andrew & & Palmer, J.D., 1990. Software Systems Engineering. New York: John Wiley & Sons. Sommerville, I., 2004. Software Engineering, 7th Edition. New York: Pearson Education (Addison Wesley). Read More