The primary goal of this stage is to develop a basis of mutual understanding between the business owner/users and the project team about the requirements for the project. The result of this understanding is an approved Requirements Specification that becomes the initial baseline for product design and a reference for determining whether the completed product performs as the system owner requested and expected. All system requirements, (e.g., software, hardware, performance, functional, infrastructure, etc.) should be included.
This stage involves analysis of the business owner/users' business processes and needs, translation of those processes and needs into formal requirements, and planning the testing activities to validate the performance of the product.
Input:
The following work products provide input to this stage.
SEM Templates:
- Software Configuration Management Plan
- Maintenance Plan
PMM Templates:
- Business Case
-
Concept Document (i.e., Feasibility Study)
-
Project Charter (Statement of business objectives)
-
Project Plan (includes Quality Management Plan)
-
Security Plan
Other Inputs:
High-Level Activities:
The remainder of this chapter is divided into sections that describe specific high-level activities performed during this stage.
4.1 Requirements Management
4.2 Select Requirements Analysis Technique
4.3 Define System Requirements
4.4 Compile and Document System Requirements
4.5 Develop System Test Requirements
4.6 Develop Acceptance Test Requirements
4.7 Establish Functional Baseline
Touch Points:
The following touch points are involved in Requirements Definition Stage:
Contracts and Procurement
-
Completion of DIT-0015a, if procuring commodities (e.g., servers, software)
-
Completion of DIT-0015b (including Statement of Work and Requirements Traceability Matrix), if procuring services (e.g., project management, application developers)
-
Utilize the services of the assigned Contract Liaison, if procuring services
E-Michigan
Enterprise
Architecture (EA)
-
Use relevant EA materials (e.g., roadmaps, solution patterns) while developing Technical Requirements
-
Revise/complete EA Solution Assessment for each alternative
-
Refer to the EA TechTalk portal site
Infrastructure Services
Security
-
Review MDIT and Agency security policies
-
Review
State
and Federal laws and regulations
-
Begin Infrastructure/Network and Data Flow Diagram
Output:
Several work products are developed during this stage. The work products listed below are the minimum requirements for a large systems project. Deviations in the content and delivery of these work products are determined by the size and complexity of a project. Explanations of the work products are provided under the applicable activities described in the remainder of this chapter.
SEM Templates:
-
Requirements Specification (initial)
-
Requirements Management Checklist
-
Requirements Traceability Matrix (initial)
-
Maintenance Plan (revised)
-
Software Configuration Management Plan (revised)
PMM Templates:
-
Project Plan (revised)
-
Security Plan (revised)
Other Outputs:
-
Application Hosting document (initial)
-
Business Continuity Plan (revised)
-
EA Solution Assessment (final)
-
Infrastructure Services Request (final)
Once the requirements are baselined, changes must be managed through the established change process, which may include a change control board.
Review Process:
Quality reviews are necessary during this stage to validate the product and associated work products. The activities that are appropriate for quality reviews are identified in this chapter and Chapter 2.0, Lifecycle Model.
Structured Walkthrough (SWT)
Requirements for a peer review or a more formal structured walkthrough are documented under Review Process at the end of each Task, Subtask, or Activity section in this stage. The State of
Michigan
guide titled Structured Walkthrough Process Guide provides a procedure and sample forms that can be used for SWTs. This document is available on the MDIT SUITE website.
Stage Exit
Schedule a Stage Exit as the last activity of the Requirements Definition Stage to enable the project approvers to review project deliverables and provide a concur/non-concur position to the project manager. The State of
Michigan
guide titled Stage Exit Process Guide provides a procedure and sample report form that can be used for stage exits. This document is available on the MDIT SUITE website.
Complete Requirements Definition Stage of the SEM
Printer Friendly
Text Version 
Email Page
