public:99_annexes:annex-b-terms-and-definitions:m:mission_objective

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:m:mission_objective [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:m:mission_objective [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Mission Objective ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Mission Objective states a high-level result that a system is required to achieve in furtherance of its mission.
 +
 +A Mission Objective establishes the outcome toward which operational, functional, quality, security, data, and other lower-level requirements contribute.
 +
 +A Mission Objective may identify:
 +
 +  * A required mission result
 +  * A required operational capability
 +  * A required system-wide characteristic
 +  * A required improvement to an existing process or condition
 +  * A required boundary for system behavior
 +
 +A Mission Objective differs from a lower-level requirement:
 +
 +  * A Mission Objective states a high-level required result
 +  * A lower-level requirement specifies behavior, information, performance, quality, or constraints that realize or refine that result
 +
 +A Mission Objective differs from a key value proposition:
 +
 +  * A Mission Objective states a result the system is required to achieve
 +  * A key value proposition states the value expected from achieving one or more mission results
 +
 +A Mission Objective may be realized by multiple lower-level requirements. A lower-level requirement may contribute to more than one Mission Objective.
 +
 +===== Definition =====
 +
 +//high-level required result that a system achieves in furtherance of its mission//
 +
 +===== Source =====
 +
 +Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +===== Note =====
 +
 +A Mission Objective should:
 +
 +  * Identify the system or subject responsible for the result
 +  * State the required result
 +  * Remain independent of unnecessary implementation detail
 +  * Provide a traceability target for lower-level requirements
 +  * Permit evaluation through the requirements that realize it
 +
 +A Mission Objective may remain broader than a directly testable functional requirement. Verification of the Mission Objective depends on verification of the lower-level requirements that collectively realize it.
 +
 +A Mission Objective does not replace the detailed requirements needed to define system behavior, constraints, acceptance conditions, or evidence.
 +
 +===== Example =====
 +
 +A Mission Objective requires Crucible to manage each Infrastructure Environment throughout its Operational Lifecycle from initial Infrastructure Deployment through Retirement. Configuration Management, Deployment Orchestration, Reliability, Maintainability, Logging, and Data Management requirements collectively realize that objective.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>