Business or Mission Analysis Purpose
-define business or mission problem or opportunity
-characterize solution space
-determine potential solution classes that could address a problem or take advantage or
an opportunity
Prepare for business or mission analysis
-establish a strategy for business or mission analysis
-need for and requirements of any enabling system, products or services
Define the problem or opportunity space
-review identified gaps in the org strategy WRT org goals and objective
-analyze gaps across trade space
-describe problems or opportunities underlying the gaps
-obtain agreement on the problem/opportunity
Characterize solution space
-nominate stakeholders, business owners nominate major stakeholders
-define preliminary OpsCon
-define other preliminary life cycle concepts
-establish a comprehensive set of alternative solution classes
OpsCon
-operational concept
-how the system works from the operator's perspective
-needs, goals, and characteristics of the system's user and operator community
-system context and system interfaces
Evaluate alternate solution classes
-evaluate the set of alternative solution classes
-ensure that the preferred alternative solution classes have been validated in the
context of the proposed business
Manage the business or mission analysis
-establish and maintain traceability of analysis results (requirements, life cycle
concepts)
-provide baseline information for configuration management
Business or mission analysis inputs
-organizational strategic plan
-ConOps
-source documents
-life cycle constraints
- project constraints
-stakeholder requirements traceability
Business or mission analysis activities
-prepare for business or mission analysis
-define the problem or opportunity space
-characterize the solution space
-evaluate alternative solution classes
- manage the business or mission analysis
,Business or mission analysis outputs
-business or mission analysis strategy
-major stakeholder identification
-preliminary life cycle concepts
-problem or opportunity statement
-business requirements
-alternative solution classes
-preliminary validation criteria
-preliminary MOE needs and data
-business requirements traceablility
-business or mission analysis record
ConOps
-concept of operations
-leadership's intended way of operating the organization
-basis or the org to direct overall characteristics of the future business systems
-org's assumptions or intent for a certain operation
OpsCon
-what the system will do
-NOT how the system will do it
-user-oriented document
-system characteristics of future system
Acquisition Concept
-the way the system will be acquired
-stakeholder engagement, requirements definition, design, production, and verification
Deployment Concept
-the way the system will be validate, delivered, and introduced into operations
Support concept
-the desired support infrastructure and manpower considerations for supporting the
system
-operating support, engineering support, maintenance support, etc
Retirement concept
-the way the system will be removed from operation and retired
-disposal of any hazardous materials used
-any legal obligations
Stakeholder needs and requirements definition purpose
-define stakeholder requirements for a system that can provide the capabilities needed
by users in a defined environment
Prepare for stakeholder needs and requirements definition
-determine the stakeholders or classes of stakeholders who will develop and define the
stakeholder needs and translate them into requirements
-determine the need for and requirements of any enabling systems, products or services
Define stakeholder needs
-elicit stakeholder needs from identified stakeholders
-prioritize the stakeholder needs
-specify the stakeholder needs
Stakeholder needs and requirements definition inputs
, -source documents
-project contraints
-major stakeholder identification
-preliminary life cycle concepts
-problem or opportunity statement
-business requirements
-alternative solution classes
-validated requirements
-preliminary MOE needs and data
-business requirements traceablility
-life cycle constraints
-stakeholder needs
-system requirements traceability
Stakeholder needs and requirements definition activities
-prepare for stakeholder needs and requirements definition
-define stakeholder needs
-develop the operational concept and other life cycle concepts
-transform stakeholder needs into requirements
-analyze stakeholder requirements
-manage the stakeholder needs and requirements definition
Stakeholder needs and requirements definition outputs
-stakeholder needs and requirements definition strategy
-life cycle concepts
-system function identification
-stakeholder requirements
-validation criteria
-MOE needs and data
-stakeholder requirements traceability
-initial RVTM
-stakeholder needs and requirements definition record
develop the operational concept and other life cycle concepts
-identify the expected set of operational scenarios and associate capabilities, behaviors,
and responses of the system or solution
-define the interactions of the system or solution with the user and environment
transform stakeholder needs into stakeholder requirements
-identify constraints on the solution
-specify health, safety, security, environment, assurance, and other stakeholder
requirements and functions
-specify stakeholder requirements, consistent with scenarios, interactions, constraints,
and critical qualities
analyze stakeholder requirements
-define validation criteria
-includes MOE and measures of suitability (MOSs)
-analyze the set of requirements for clarity, completeness, and consistency
-negotiate modifications to resolve unrealizable or impractical requirements
manage the stakeholder needs and requirements definition