SYS.2 System Requirements Analysis

Get Started. It's Free
or sign up with your email address
Rocket clouds
SYS.2 System Requirements Analysis by Mind Map: SYS.2 System Requirements Analysis

1. The purpose of the System Requirements Analysis Process is to transform the defined stakeholder requirements into a set of system requirements that will guide the design of the system.

1.1. SYS.2.BP1: Specify system requirements

1.1.1. Agree on the attributes required for capturing the System Requirements Specification.

1.1.2. Derive System Requirements from Customer Requirements Specification as input.

1.1.3. Document the System Requirements in SysRS

1.1.4. Outcomes: Traceability record, Change control record, Analysis record, Interface Requirements Specification, System Requirements Specification

1.2. SYS.2.BP2: Structure system requirements

1.2.1. Grouping of System Requirements into different clusters - for ex: the requirements can be grouped by features - Lane Keep Assist, Adaptive Cruise Control, Forward collision warning etc..

1.2.2. Categorize the Requirements as Functional and Non-Functional Requirements

1.2.3. Prioritize the Requirements - Follow MOSCOW (Must have, Should Have, Could Have or Would Have) or ideal will be assign it to release milestone Sample A1, B1, C, D etc..

1.2.4. Outcomes: Analysis record

1.3. SYS.2.BP3: Analyze system requirements

1.3.1. Analyze the Requirements - Identified dependencies or interrelated requirements , Technical feasibility , verifiability, risks, cost and schedule

1.3.2. Outcomes: Analysis record

1.4. SYS.2.BP4: Analyze the impact on the operating environment

1.4.1. Analyze the Impact on Internal Interfaces and External Interfaces ex: Signals, Environment ex: Temperature, Performance ex: Response time etc

1.4.2. Outcomes: Analysis record

1.5. SYS.2.BP5: Develop verification criteria

1.5.1. Identify Verification criteria for all Requirements - Pre-conditions, inputs, outputs , use cases , post conditions etc

1.5.2. Outcomes: Analysis record, Verification criteria

1.6. SYS.2.BP6: Establish bidirectional traceability

1.6.1. Establish Traceability - System and Customer Requirements

1.6.2. Outcomes: Traceability record

1.7. SYS.2.BP7: Ensure consistency

1.7.1. Establish Traceability - System Requirements to Customer Requirements

1.7.2. Review the System requirements and Traceability

1.7.3. Outcomes: Traceability record, Review record

1.8. SYS.2.BP8: Communicate agreed system requirements

1.8.1. Communication the System Requirements as per Communication Plan

1.8.2. Outcomes: Communication Record

2. Input : System Requirements and System AD