Chapter 4 - INCOSE CSEP Test Prep 2023 Complete
6 Elements of the Stakeholder Requirements Definition Process
1 - ID users/Statkeholders
2 - Define Need
3 - Capture Source Documents
4 - Initialize Requirements Database
5 - Establish Conops
6 - Generate Systems Requirment Document/RFP/SOW
Stakeholder Requirements Definition Process Outputs
1 - Concept Documents
2 - Stakeholder Requirements
3 - MOE Need
4 - MOE Data
5 - Validation criteria
6 - Initial RVTM
7 - Stakeholder Rqmnts Trace
4.1
Configuration Item Definition
-Hardware, S/W, or composite item
-any level in the systems
-designated for configuration management
Objective of ConOps
-communicate with end user during early stages
-ensure needs are clearly understood and incorporated into the design decision
database
What is in a ConOps Document?
-Define critical performance requirements, qualitatively
-define system rationale
-contains preliminary functional flow block diagrams
4 Characteristics of a Configuration Item
-defined functionality
-replaceable as an entity
-unique specifications
-formal control of form, fit, function
Purpose of Stake Holders Requirements Definition Process
Define requirements for a system that can provide the services needed by users and
other stakeholders in a defined environment
Activities in the Stateholder Requirements definition process
-Elicit stakeholder reqmnts
-Define stakeholder reqmnts
-Analyze and maintain stakeholder reqmnts
Inputs of stakeholder requirements definition process
-Source Documents
-Stakeholder need
-Project constraints
, Purpose of having traceability
-Improve integrity and accuracy of requirements
-Allows tracking of reqmnts and allocation
-easier maintenance and change implementation
Quality Function Deployment
technique where voice of customer is not clear
Systems Specification attributes
-baseline
-complete, accurate, non-ambiguous
-recorded in reqmnts database
-accessible by all
Requirements Analysis Process Activities
-Define System Requirements
-Analyze and Maintain system requirements
Requirements Analysis Process Inputs
-Concept Documents
-Stakeholder Requirements
-Measures of effectiveness
-Initial RVTM
-Stakeholder Requirements Traceability
Purpose of Requirements Analysis Process
Transform stakeholder reqmnts into technical reqmnts
Outputs of Requirements Analysis Process Outputs
-System reqmnts
-Measures of Performance Need
-MOP - Data
-System Functions
-System Functional Interfaces
-Verification Criteria
-Specification Tree
-Systems Specification
-Updated RVTM
-System Requirements Trace
4.2
10 Characteristics of a good requirement
-Necessary
-Implementation Independent
-Clear & Concise
-Complete
-Consistent
-Achievable
-Traceable
-Verifiable
-Affordable
-Bounded
4.2
6 Elements of the Stakeholder Requirements Definition Process
1 - ID users/Statkeholders
2 - Define Need
3 - Capture Source Documents
4 - Initialize Requirements Database
5 - Establish Conops
6 - Generate Systems Requirment Document/RFP/SOW
Stakeholder Requirements Definition Process Outputs
1 - Concept Documents
2 - Stakeholder Requirements
3 - MOE Need
4 - MOE Data
5 - Validation criteria
6 - Initial RVTM
7 - Stakeholder Rqmnts Trace
4.1
Configuration Item Definition
-Hardware, S/W, or composite item
-any level in the systems
-designated for configuration management
Objective of ConOps
-communicate with end user during early stages
-ensure needs are clearly understood and incorporated into the design decision
database
What is in a ConOps Document?
-Define critical performance requirements, qualitatively
-define system rationale
-contains preliminary functional flow block diagrams
4 Characteristics of a Configuration Item
-defined functionality
-replaceable as an entity
-unique specifications
-formal control of form, fit, function
Purpose of Stake Holders Requirements Definition Process
Define requirements for a system that can provide the services needed by users and
other stakeholders in a defined environment
Activities in the Stateholder Requirements definition process
-Elicit stakeholder reqmnts
-Define stakeholder reqmnts
-Analyze and maintain stakeholder reqmnts
Inputs of stakeholder requirements definition process
-Source Documents
-Stakeholder need
-Project constraints
, Purpose of having traceability
-Improve integrity and accuracy of requirements
-Allows tracking of reqmnts and allocation
-easier maintenance and change implementation
Quality Function Deployment
technique where voice of customer is not clear
Systems Specification attributes
-baseline
-complete, accurate, non-ambiguous
-recorded in reqmnts database
-accessible by all
Requirements Analysis Process Activities
-Define System Requirements
-Analyze and Maintain system requirements
Requirements Analysis Process Inputs
-Concept Documents
-Stakeholder Requirements
-Measures of effectiveness
-Initial RVTM
-Stakeholder Requirements Traceability
Purpose of Requirements Analysis Process
Transform stakeholder reqmnts into technical reqmnts
Outputs of Requirements Analysis Process Outputs
-System reqmnts
-Measures of Performance Need
-MOP - Data
-System Functions
-System Functional Interfaces
-Verification Criteria
-Specification Tree
-Systems Specification
-Updated RVTM
-System Requirements Trace
4.2
10 Characteristics of a good requirement
-Necessary
-Implementation Independent
-Clear & Concise
-Complete
-Consistent
-Achievable
-Traceable
-Verifiable
-Affordable
-Bounded
4.2
