Assignment: Consider the following scenario then complete the exercises below:

AirBird is a domestic airline company that is building a Customer Relationship Management (CRM) system that focuses on providing a personalized experience to all customers. The system would be deployed on mobile phones, tablets and desktop. Customers will be allowed to search for flights, view flight routes and itineraries, filter flights based on price, destination, duration, number of stops, class (basic economy, economy, business and first class). Customers will need an account with AirBird to book a trip or purchase flights. They should be able to view past trips, print the itinerary for an upcoming trip and modify or cancel trips. If a customer wants to modify a flight, there is no service charge, except that the customer will have to pay a price difference if the prices on the new date are higher. If the prices have gone down, the customer will receive a gift card from AirBird called AirBird Wallet. The wallet has no expiry and the money in the wallet can be used for future purchases.

AirBird also has a rewards program based on flyer miles and miles expire after 5 years since they were accrued. Both the wallet and the rewards can be used to purchase tickets, make upgrades (economy to business class), avail discounts at lounges and purchase in-flight items. The main difference is that the wallet has no expiry and the miles expire after 5 years. The CRM system will allow the customer to select preferences on seating, food and drinks. The system should include the Language Change functionality that allows the customer to choose the preferred language. Customer should get promotional emails based on their search history. The system should allow the customer to make payments via credit cards, PayPal and AirBird wallet.

Exercises:

1. Develop a Use Case diagram for the scenario covering all major and important supporting use cases from the above case. No hand drawings please. (15 points)
   1. User cases should be features of the system and the name should indicate an action or feature. For example, Transaction is a thing. It is an entitiy and not an action. You should state it as Perform Transaction or Record Transaction clearly indicating the meaning of the use case. When someone sees your use case diagram, they should clearly understand what you are referring to. Use case names should be a verb and indicate a feature of the system or an action it performs when invoked.
   2. You should identify all major use cases for this case and try to create other use cases as relevant (supporting use cases). Use cases should be linked using extends and includes where applicable. Remember, this is not a flow chart.
   3. Where can I go wrong? Wrong names for use cases, wrong use of extends and includes, incorrect notations used, use cases not linked to an actor or another use case and sticking alone in the diagram, not performing exhaustive analysis to cover other supporting use cases, not marking actors properly, using includes/ extends between an actor and a usecase, etc.

2. Create two Use Case Descriptions for any two major use cases from your use case diagram. The use case description should include the use case name, actor, brief description, normal flow of events, and exception flow of events. (20 points)
   1. Remember: Each use case in a use case diagram should have a corresponding use case description written specifically for that use case. You can choose any two use cases and write the description for them. You cannot combine the description for multiple use cases in one template. For each use case, you must write the description separately.

Use Case Name:	required
Primary Actor:	required
Brief Description:	required
Stakeholders:	optional
Trigger:	optional
Normal flow of events:	required (be sure to be very specific, list each step in detail)
Subflows:	optional
Alternate/Exception flow:	required (be sure to be very specific, list each step in detail)

Note:

1. Submit your completed assignment as an attachment (.doc, .docx, or .pdf) via eLearning.
2. No hand drawings please. You must generate the UML diagrams using a tool and it should be done professionally.
3. Verify if the assignment looks good and the images are clear enough after your submission. If the submission is not of acceptable quality no third attempt will be given.