Go to Crucible Functional Requirements
The Crucible Interfaces requirements define how Crucible exposes its operations through a Command-Line Interface (CLI) and a Web-Based User Interface (Web UI).
Together, these requirements establish shared interface operations and separate command-line and web-based access paths. They do not require the interfaces to duplicate the underlying implementation of those operations.
Review and approve the decomposition of the Crucible Interfaces requirements into shared interface operations, a Command-Line Interface, and a Web-Based User Interface.
Confirm whether the Command-Line Interface remains the primary interface or whether the architecture treats the Command-Line Interface and Web-Based User Interface as equivalent access paths.
Confirm whether the controlling source requires behavioral parity between the Command-Line Interface and Web-Based User Interface or requires both interfaces to use the same underlying engine implementation.
Determine whether the operations exposed through both interfaces require a separately defined controlled term.
The individual requirement pages retain the stable identifiers FR-UI-001 through FR-UI-003.
Individual requirement pages are leaf nodes and omit a trailing :start from their namespaces.
The Source Statement on each requirement page preserves the original wording from the controlling System Requirements Specification.
Normalized Statements should use direct, testable behavior and distinguish:
FR-UI-001 should specify shared externally observable operations unless the controlling source explicitly requires a common internal engine implementation.
FR-UI-002 should address the Command-Line Interface without adding Web-Based User Interface behavior.
FR-UI-003 should address the Web-Based User Interface without adding Command-Line Interface behavior.
The category title Crucible Interfaces does not establish Management or Management Interface as separate controlled terms. Individual Statements should identify the actual Crucible operations exposed through each interface.
Verification criteria should test only the behavior stated in each normalized Statement and should not introduce additional normative obligations.
Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.
Do not rename a requirement page after an external citation unless a redirect or move plan is in place.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.