Create TWO Casual Format Use Cases utilizing the Functional Requirements data from the Attachment 1, Requirements Definition deliverable. Utilize Microsoft Word®.
After reviewing the Attachment 2, consider the possible Use Case Names, actors, descriptions, triggers, and the normal course interactions of the actors with the hypothetical aviation-related Inventory Management System. For example, consider the case of an Airframe Shop Mechanic who uses a fictitious “AAA Aviation AntiCorrosion Spray” in her work. When the mechanic notices that the product is running low in the inventory, she might interact with the IMS to reorder the product.
In a Use Case associated with the above interaction, the Use Case Name is “Order Product.” The actor is “Airframe Shop Mechanic.” The description is “Airframe Shop Mechanic wants to order AAA Aviation AntiCorrosion Spray.” The trigger is “The AAA Aviation AntiCorrosion Spray product is running low in the inventory.” The Normal Course 1.0 title is “Order a product.”
Use Case names are verb-related because a Use Case describes an action taken by a user, such as making an input or requesting an output. Use Case names are NOT noun-related because Use Case names are NOT things. The actor is the user of the Inventory Management System. The actor is a person, a hardware device, or a software system that uses or integrates with the Inventory Management System to achieve a useful goal. For example, besides a clerk, manager, etc., (person), an actor could be a warehouse bar code scanning device or Point of Sale system that integrates with the Inventory management System.
Fill in the sections with your hypothetical data, overwriting the yellow-highlighted data. Submit the TWO Casual Format Use Cases in ONE document. Do NOT submit any exceptions data. A Casual Format Use Case does not contain exceptions data.
