9.3 Web-Based User Interface [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.
====== 9.3 Web-Based User Interface ======

[[dido:02-crusible:09-crucible-interfaces:start|Go to 9. Crucible Interfaces]]

The [[dido:99_annexes:annex-b-terms-and-definitions:w:web_ui|Web-Based User Interface]] provides a browser-based interface for invoking supported [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] operations.

The Web-Based User Interface exposes the Shared Interface Operations described in [[dido:02-crusible:09-crucible-interfaces:09-01-shared-interface-operations|9.1 Shared Interface Operations]] through visual controls appropriate to the implemented interface.

The Web-Based User Interface does not establish separate lifecycle semantics or independent Crucible capabilities. Each user action invokes an underlying operation governed by its applicable requirements.

===== Operation Selection =====

An authorized user selects a supported Crucible operation through the Web-Based User Interface.

The interface can present operations through:

  * Navigation controls
  * Menus
  * Forms
  * Action controls
  * Resource views
  * Operation-specific pages

The available operations reflect the capabilities exposed by the implemented interface and permitted by the applicable access controls.

===== Operation Inputs =====

The Web-Based User Interface collects the information required by the selected Crucible operation.

Inputs can include:

  * Identifiers
  * Parameter values
  * Selected resources
  * Referenced artifacts
  * Uploaded input files
  * Baseline selections
  * Image selections
  * Deployment Target selections
  * Assessment-subject selections
  * Configuration values

The visual presentation of an input does not change the meaning of the value supplied to the underlying operation.

===== Input Validation =====

The Web-Based User Interface validates required inputs before submitting the operation.

Input validation can identify:

  * A missing required value
  * An unsupported value
  * An invalid identifier
  * An unreadable or unsupported input file
  * An incompatible combination of selections
  * An unresolved resource reference

Successful interface validation establishes that the request contains the information required for submission. It does not establish that the operation is authorized or that the operation will complete successfully.

===== Authorization =====

Web-Based User Interface operations remain subject to the same identity, access, Security Domain, and information-handling controls that govern the underlying Crucible capability.

The Web-Based User Interface does not permit a user to:

  * Invoke an unauthorized operation
  * Access an unauthorized resource
  * Bypass a Security Domain restriction
  * Override an information-handling rule
  * Avoid an applicable validation or approval activity

Access to the Web-Based User Interface does not imply access to every Crucible operation.

===== Operation Status =====

The Web-Based User Interface presents the status of an invoked operation through an interface-appropriate representation.

The status can indicate whether the operation:

  * Was accepted
  * Is in progress
  * Completed successfully
  * Completed with an incomplete result
  * Failed
  * Could not proceed
  * Requires corrected or additional input

The interface preserves the distinction between successful submission of a request and successful completion of the underlying Crucible operation.

===== Operation Results =====

The Web-Based User Interface provides access to the result produced by the underlying Crucible operation.

A result can include:

  * A completion status
  * An assigned identifier
  * A produced artifact
  * A Compliance Report
  * An assessment or validation result
  * A deployment result
  * A reference to related output
  * Error or failure information

The interface can present the result directly or provide access to a separately produced artifact.

The Web-Based User Interface does not change the meaning of the result produced by the underlying operation.

===== Error Information =====

When a request or operation cannot complete, the Web-Based User Interface presents information describing the observed condition.

Error information can identify:

  * The request that failed
  * The invalid or missing input
  * The operation that could not proceed
  * The affected subject or resource
  * The observed failure
  * Available corrective information

The interface does not present a failed or incomplete operation as successful.

===== Relationship to the Command-Line Interface =====

The Web-Based User Interface and the [[dido:02-crusible:09-crucible-interfaces:09-02-command-line-interface|Command-Line Interface]] provide different interaction models for supported Shared Interface Operations.

The interfaces can differ in:

  * Navigation
  * Input collection
  * Help and guidance
  * Progress presentation
  * Error presentation
  * Result presentation

Those differences do not change the meaning, authorization, inputs, status, or result of the underlying Crucible operation.

===== Web-Based Operation Result =====

A Web-Based User Interface interaction preserves the relationship among:

  * The selected Crucible operation
  * The supplied inputs and parameters
  * The applicable authorization decision
  * The operation status
  * The resulting output
  * Any error or incomplete condition

The underlying Crucible capability determines the operational result. The Web-Based User Interface provides the browser-based means of requesting and presenting that result.

===== Requirements Addressed =====

^ Requirement ^ Statement ^
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-11-management-interfaces:fr-ui-003]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-11-management-interfaces:fr-ui-003#Statement&noheader&nofooter&noeditbtn}} |

The linked leaf requirement page remains the canonical source.

----

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