Software Engineering
PHASE 4: REQUIREMENTS ANALYSIS PHASE
The Requirements Analysis Phase begins when the previous phase objectives have been achieved. Documentation related to user requirements from the Concept Development Phase and the Planning Phase shall be used as the basis for further user needs analysis and the development of detailed requirements. Multiple-release projects require only one iteration of the Requirements Analysis Phase, which should involve requirements definition for all planned releases. 1.0
OBJECTIVE/GOALS
Objectives Successful completion of the Requirements Analysis Phase should comprise: • Definition of approved requirements • Creation of the System Requirements Document and Requirements Traceability Matrix • Development of planned test activities • Approval to progress to the Design Phase Goals The purpose of the Requirements Analysis Phase is to transform the needs and high-level requirements specified in earlier phases into unambiguous (measurable and testable), traceable, complete, consistent, and stakeholder-approved requirements. 2.0
DELIVERABLES AND APPROVALS
SDLC deliverables help State agencies successfully plan, execute, and control IT projects by providing a framework to ensure that all aspects of the project are properly and consistently defined, planned, and communicated. The SDLC templates provide a clear structure of required content along with boilerplate language agencies may utilize and customize. State agencies may use formats other than the templates, as long as the deliverables include all required content. . The development and distribution of SDLC deliverables: • Ensure common understanding among Planning Team members and stakeholders, • Serve as a reminder of specified plans as projects become increasingly complex, • Provide agency senior management and other State officials insight into project risks and ongoing performance, • Encourage the execution of repeatable and consistent processes, • Facilitate the implementation
The Requirements Analysis Phase begins when the previous phase objectives have been achieved. Documentation related to user requirements from the Concept Development Phase and the Planning Phase shall be used as the basis for further user needs analysis and the development of detailed requirements. Multiple-release projects require only one iteration of the Requirements Analysis Phase, which should involve requirements definition for all planned releases. 1.0
OBJECTIVE/GOALS
Objectives Successful completion of the Requirements Analysis Phase should comprise: • Definition of approved requirements • Creation of the System Requirements Document and Requirements Traceability Matrix • Development of planned test activities • Approval to progress to the Design Phase Goals The purpose of the Requirements Analysis Phase is to transform the needs and high-level requirements specified in earlier phases into unambiguous (measurable and testable), traceable, complete, consistent, and stakeholder-approved requirements. 2.0
DELIVERABLES AND APPROVALS
SDLC deliverables help State agencies successfully plan, execute, and control IT projects by providing a framework to ensure that all aspects of the project are properly and consistently defined, planned, and communicated. The SDLC templates provide a clear structure of required content along with boilerplate language agencies may utilize and customize. State agencies may use formats other than the templates, as long as the deliverables include all required content. . The development and distribution of SDLC deliverables: • Ensure common understanding among Planning Team members and stakeholders, • Serve as a reminder of specified plans as projects become increasingly complex, • Provide agency senior management and other State officials insight into project risks and ongoing performance, • Encourage the execution of repeatable and consistent processes, • Facilitate the implementation