C.3.11 Management Interfaces

Go to Crucible Functional Requirements

The Management Interfaces requirements define how Crucible presents a web-based interface for managing multiple Infrastructure Environments and ensures that the web interface uses the same engine and command-line capabilities as the primary command-line interface.

Together, these requirements establish an additional management interface without replacing or duplicating the primary command-line execution path.

Contents

Notes for Editors

The individual requirement pages should retain the stable identifiers FR-UI-001 through FR-UI-002.

These requirements apply to Phase 2.

Individual requirement pages are leaf nodes and should not include a trailing :start in their namespaces.

The Source Statement on each requirement page should preserve the original wording from the controlling System Requirements Specification.

Normalized Statements should use direct, testable behavior and should identify the applicable interface, managed Infrastructure Environment information, shared engine capability, command-line operation, and required result.

The web-based management application should remain an additional interface. The command-line interface remains the primary interface.

Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.

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

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

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

Replace <namespace> with the namespace of the requirement leaf page.

The section name following # SHALL match the section heading verbatim on the requirement page.

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.