C.2 Operational Requirements [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== C.2 Operational Requirements ======

[[dido:02-crusible:99-annexes:annex-c-requirements:start|Go to Crucible Requirements]]

The [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_requirement|Operational Requirements]] define the actors, deployment environments, operational classifications, concurrency needs, and management scope within which [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] operates.

These requirements establish the operational conditions that constrain and guide the functional, security, reliability, performance, maintainability, data management, and interoperability requirements.

===== Contents =====

{{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements#1|js navbar nocookie maxjs#1 id#crucible_operational_requirements_nav}}

===== Notes for Editors =====

The individual requirement pages should retain the stable identifiers ''OR-001'' through ''OR-005''.

The source statements should preserve the wording from the controlling System Requirements Specification.

Normalized statements should replace weak verbs such as **support** with direct, testable behavior.

Incoming traceability should use the wiki Backlinks function rather than a manually maintained list.

To reference the requirement Statement from another wiki page, insert:

<code dokuwiki>
{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}
</code>

Replace ''<namespace>'' with the namespace of the requirement page to reference.

Do not rename requirement pages after an external citation unless a redirect or move plan is in place.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>