This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:start [2026/07/16 02:19] – nick_dido | dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:start [2026/07/16 12:10] (current) – [C.1 Mission Objectives] nick_dido |
|---|
| [[dido:02-crusible:99-annexes:annex-c-requirements:start|Go to Crucible Requirements]] | [[dido:02-crusible:99-annexes:annex-c-requirements:start|Go to Crucible Requirements]] |
| |
| The Mission Objectives identify the high-level outcomes that guide the [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] requirements, architecture, implementation, operation, and [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]]. | The [[dido:99_annexes:annex-b-terms-and-definitions:m:mission_objective|Mission Objectives]] identify the high-level outcomes that guide the [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] requirements, architecture, implementation, operation, and [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]]. |
| |
| These objectives address infrastructure creation, deployment duration, platform independence, connected and disconnected operation, reusable and version-controlled infrastructure, and lifecycle management. | These objectives address infrastructure creation, deployment duration, platform independence, connected and disconnected operation, reusable and version-controlled infrastructure, and lifecycle management. |