Requirements Definition
The work developing the Inventory Management System in-house continues in this activity.
The project team has finished working in the SDLC Planning Phase. Now it is time to begin working in the Analysis Phase. As you will recall from the required readings, before we can design and create a new information system, systems analysts must first determine who the system users will be and how they will use the system.
The first step in solving these riddles is to engage in a Requirements Determination process and develop a Requirements Definition.
Create a Requirements Definition utilizing Microsoft Word®. Before you begin to work on this activity, refer to the Requirements Definition example in Figure 3-3 in the textbook. Please note that all the Functional Requirements data and most of the Non-Functional Requirements data are complete sentences that begin with “The system …”
Fill in the sections below with hypothetical data, overwriting the yellow-highlighted data. Remove the yellow highlights before submitting your assignment document. When you evaluate the various requirements that might be present when developing the Inventory Management System, be sure to consider those that are related to an aviation-related company.
Requirements Definition
Functional Requirements
1. Functional requirement #1: Insert the type of functional requirement here (Note: Three requirements in each criterion as shown. Delete this note data and yellow highlighting before you submit your document.)
1.1. XXX
1.2. XXX
1.3. XXX
2. Functional requirement #2: Insert the type of functional requirement here
2.1. XXX
2.2. XXX
2.3. XXX
Non-Functional Requirements (Note: Two requirements in each criterion as shown. Delete this note data and yellow highlighting before you submit your document.)
1. Operational
1.1. XXX
1.2. XXX
2. Performance
2.1. XXX
2.2. XXX
3. Security
3.1. XXX
3.2. XXX
4. Cultural & Political
4.1. XXX
4.2. XXX