Differences

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

--- dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:start [2026/07/21 09:57] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:start [2026/07/22 08:49] (current) – nick_dido
@@ Line 1: / Line 1: @@
+====== OR-001 — Operation by Identified User Categories ======
+[[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:start|Go to Operational Requirements]]
+===== Original Requirement =====
+> //The system SHALL support operation by://
+>> //Developers//
+>> //DevSecOps Engineers//
+>> //Platform Engineers//
+>> //System Administrators//
+>> //Security Engineers//
+>> //Compliance Officers//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
+===== Assessment of Original Requirement =====
+The Original Requirement preserves the approved intent that the identified categories participate in Crucible operation, but it does not express independently testable normative statements.
+The following Specification Discipline and Authoring findings apply:
+  * **The system** does not use the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
+  * **Support** is a weak verb that does not identify an observable Crucible behavior
+  * **Operation** does not identify the Crucible operations associated with the listed categories
+  * **Operation by** does not identify the relationship between each listed category and each Crucible operation
+The word **operation** is grammatically valid as a mass noun describing the general act of operating Crucible. For requirements purposes, however, the word does not identify an observable Crucible behavior.
+Changing **operation** to **operations** would indicate that multiple actions exist, but pluralization alone would not identify those actions or associate them with the listed categories.
+The Original Requirement identifies:
+  * Developers
+  * DevSecOps Engineers
+  * Platform Engineers
+  * System Administrators
+  * Security Engineers
+  * Compliance Officers
+The decomposition treats these categories as proposed Crucible roles so that Crucible operations can be allocated and verified separately for each role.
+The Original Requirement does not define these roles or identify the controlling source that allocates Crucible operations to them.
+The Original Requirement therefore requires:
+  * Replacement of **the system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
+  * Replacement of **support** with an observable Crucible behavior
+  * Classification or definition of each listed category
+  * Identification of the Crucible operations allocated to each proposed role
+  * Separation of the six independently testable roles
+  * Confirmation that the derived requirements collectively preserve the complete intent of OR-001
+The decomposition preserves ''OR-001'' as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page.
+===== Proposed Statements =====
+The Original Requirement is decomposed into the following proposed replacement requirements:
+{{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001#1|js navbar nocookie maxjs#1 id#crucible_or_001_requirements_nav}}
+===== Requirement Status =====
+<todo>Review and approve the classification of Developer, DevSecOps Engineer, Platform Engineer, System Administrator, Security Engineer, and Compliance Officer as Crucible roles.</todo>
+<todo>Determine whether OR-001a through OR-001f collectively supersede OR-001.</todo>
+<todo>If OR-001a through OR-001f are accepted as the complete replacement for OR-001, mark OR-001 as superseded and preserve this page as the parent Traceability record.</todo>
+----
+===== Issues =====
+The following unresolved issues affect the decomposition of OR-001:
+<todo>Confirm that Developer, DevSecOps Engineer, Platform Engineer, System Administrator, Security Engineer, and Compliance Officer identify Crucible roles rather than job titles, organizational functions, user categories, or another kind of actor.</todo>
+<todo>Define each proposed Crucible role or reference an authoritative definition.</todo>
+<todo>Identify the controlling source that allocates Crucible operations to each proposed role.</todo>
+<todo>Determine whether OR-001a through OR-001f provide complete coverage of the approved intent of OR-001.</todo>
+----
+===== Notes for Editors =====
+This page should retain the stable parent requirement identifier ''OR-001''.
+This page is a non-leaf requirement page and retains a trailing '':start'' in its namespace.
+The child requirements are leaf requirement pages and omit a trailing '':start'' from their namespaces.
+This page preserves:
+  * The Original Requirement
+  * The assessment of the Original Requirement
+  * The reason for decomposition
+  * Traceability to the proposed replacement requirements
+  * The unresolved cross-cutting issues affecting the decomposition
+  * The supersession decision
+The child requirements introduce proposed role names only to provide a precise allocation target for Crucible operations. The proposed role names do not establish:
+  * A role-assignment mechanism
+  * A role-based authorization model
+  * An access-control model
+  * Permission allocation
+  * Multiple-role assignment
+  * Role-assignment removal
+  * Recording of an authorizing role
+The Original Requirement should not be marked as superseded until the requirement owner:
+  * Approves the classification of the listed categories as Crucible roles
+  * Approves the six child requirements
+  * Confirms that the child requirements collectively preserve the complete approved intent of OR-001
+  * Confirms that no additional child requirements are required
+After supersession, this page should remain as the parent Traceability record and should continue to preserve the Original Requirement and its assessment.
+Material changes to the decomposition should update the child requirements, Requirement Status, Issues, and Traceability records.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>