Web-Based User Interface (Web UI) [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.
====== Web-Based User Interface (Web UI) ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

A Web-Based User Interface (Web UI) provides a graphical interface that a person accesses through a web browser to interact with a software system.

A Web UI can allow a user to:

  * Select operations
  * Supply input values
  * Review configuration
  * Initiate activities
  * Observe execution status
  * Review results
  * Examine logs
  * Inspect [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]]
  * Review findings and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]

A Web UI exchanges information with the underlying software through one or more defined software interfaces.

Within Crucible documentation, a Web UI provides one possible human-facing interface for configuring, initiating, observing, and reviewing Crucible operations.

===== Definition =====

//graphical user interface accessed through a web browser that enables a person to interact with a software system//

===== Source =====

DIDO-controlled term adapted from established web-application and user-interface practices.

===== Note =====

The term **Web UI** means **Web-Based User Interface**.

A Web UI differs from a [[dido:99_annexes:annex-b-terms-and-definitions:c:cli|Command-Line Interface (CLI)]]. A Web UI provides browser-based graphical interaction, while a CLI accepts textual commands, options, and arguments.

A Web UI differs from an Application Programming Interface. A Web UI supports interaction by a person, while an Application Programming Interface supports interaction between software components.

A Web UI can invoke the same underlying operations exposed through a CLI or Application Programming Interface.

The existence of a Web UI does not require every Crucible operation to be interactive. Automated [[dido:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflows]] and [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]] can use noninteractive interfaces.

===== Example =====

An operator accesses the Crucible Web UI through a browser, selects a Workspace, chooses a Baseline Composition operation, supplies the required parameters, initiates execution, and reviews the resulting status and Evidence.

----

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