Events:
1. Customer submits a complaint about lost luggage
- Use Case: Record lost luggage complaint
2. Flight is delayed due to weather conditions
- Use Case: Notify customers of flight delay
3. Customer requests wheelchair assistance
- Use Case: Arrange wheelchair assistance for customer
4. Customer provides feedback on their airport experience
- Use Case: Collect and store customer feedback
Use Case Description: Record lost luggage complaint
1. Brief Description:
- This use case involves recording and documenting complaints from customers about lost luggage.
2. Actors:
- Customer Relations Staff
3. Preconditions:
- Customer has submitted a complaint about lost luggage
4. Basic Flow of Events:
- Customer Relations Staff receives the complaint from the customer
- Staff member logs the details of the complaint, including customer information, flight details, and description of the lost luggage
- Complaint is assigned a unique reference number for tracking purposes
- Staff member ensures that the complaint is escalated to the appropriate department for resolution
5. Alternative Flows:
- If customer does not provide enough information, staff member may need to follow up with the customer for more details
- If the complaint is complex or requires additional investigation, it may be escalated to a higher level of management for resolution
6. Postconditions:
- Complaint is recorded in the system and can be tracked for progress and resolution
- Customer is notified of the status of their complaint and any updates on the resolution process.
Using the event decomposition technique, identify any four events and their resulting use cases for the Airport Customer Relations Management System.
(10)
(Marks: 20)
18)
Q.3.2 Create a use case description for any one of the use cases identified in Question
3.1
1 answer