The Approval Committee reviewed the Requirements Definition that you submitted in Module 3, and you have been directed to proceed on course with the development of the inventory management system project. You will now use the data from the Requirements Definition to create two Casual Format Use Cases.
A Use Case illustrates an activity performed by the user of an information system to make an input or request an an output. Analysts create Casual Format Use Cases first and later add more detail to create Fully Dressed Use Cases.
The Casual Format Use Cases that you create here will be utilized in Module 6 to create two DFD Fragments.
Requirements
Create two Casual Format Use Cases utilizing Microsoft Word®. Before you begin to work on this activity, refer to the Casual Format Use Case example in the textbook. After reviewing the example, consider the Actors, Triggers, etc., that might be present in an aviation-related inventory management system. For example, an Actor such as a user of the fictitious ‘Easy-Spray Aircraft Corrosion Application System’ would have a trigger such as the user requires the fictitious AAA Aviation AntiCorrosion Spray Formula 55 product to do a job.
Use this Casual Format Use Case Template (DOCX) to complete this activity.
Create two Casual Format Use Cases in a document that address the following:
The following data must be present:
- Use Case Name
- ID
- Priority
- Actor (Actor refers a person, another software system, or a hardware device that interacts with the system to achieve a useful goal)
- Description
- Trigger
- Type:
- External
- Temporal
Preconditions:
- Precondition #1
- Precondition #2
- Precondition #3
Normal Course:
- 1.0
- 1.
- 2.
- 3.
Postconditions:
- Postcondition #1
- Postcondition #2
- Postcondition #3
Attachments –
1 = template
2= data from the required definition
3= example from textbook
