Duplicate Question
The question on this page has been marked as a duplicate question.
Original Question
Q.3.1 Using the event decomposition technique, identify any four events and their resulting use cases for the Airport Customer...Question
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..write the answer in a table form of use case description Also provided one for system which is under flow of activites
(10)
(Marks: 20)
18)
Q.3.2 Create a use case description for any one of the use cases identified in Question
3.1..write the answer in a table form of use case description Also provided one for system which is under flow of activites
Answers
There are no human answers yet.
Answered by
GPT 3.5
Event: Customer submits a complaint
Use Case: Record customer complaint
Event: Customer requests information on flight status
Use Case: Display flight status
Event: Customer provides feedback
Use Case: Record customer feedback
Event: Customer requests assistance with booking
Use Case: Assist customer with booking
Use Case Description:
Use Case Name: Record customer complaint
Primary Actor: Customer
Secondary Actors: Customer Service Representative
Preconditions: The customer must have a valid complaint to submit
Postconditions: The complaint is successfully recorded and stored in the system
Normal Flow:
1. Customer accesses the complaint submission feature
2. Customer enters their complaint details
3. System validates and stores the complaint
4. System sends confirmation to customer
Alternative Flows:
- If the complaint is incomplete, system prompts the customer to provide all necessary information
- If the system encounters an error, it notifies the customer and logs the issue for resolution
Use Case: Record customer complaint
Event: Customer requests information on flight status
Use Case: Display flight status
Event: Customer provides feedback
Use Case: Record customer feedback
Event: Customer requests assistance with booking
Use Case: Assist customer with booking
Use Case Description:
Use Case Name: Record customer complaint
Primary Actor: Customer
Secondary Actors: Customer Service Representative
Preconditions: The customer must have a valid complaint to submit
Postconditions: The complaint is successfully recorded and stored in the system
Normal Flow:
1. Customer accesses the complaint submission feature
2. Customer enters their complaint details
3. System validates and stores the complaint
4. System sends confirmation to customer
Alternative Flows:
- If the complaint is incomplete, system prompts the customer to provide all necessary information
- If the system encounters an error, it notifies the customer and logs the issue for resolution
Submit Your Answer
We prioritize human answers over AI answers.
If you are human, and you can answer this question, please submit your answer.