Workflow

Go up to Terms and Definitions

A Workflow organizes activities performed to achieve an identified result.

A Workflow identifies how work progresses from an initiating condition through one or more activities to a completion condition. The Workflow can identify:

• Inputs
• Activities
• Activity dependencies
• Execution order
• Decision points
• Participants
• Automated processes
• Manual activities
• Triggering events
• Entry conditions
• Completion conditions
• Intermediate results
• Final outputs
• Failure conditions

Activities within a Workflow can execute:

• Sequentially
• Concurrently
• Conditionally
• Repeatedly
• In response to an event

A Workflow can coordinate human participants, automated processes, software systems, or combinations of them.

Within Crucible documentation, Workflows coordinate operations involving:

• Git repositories
• Repository changes
• Build operations
• Security evaluation
• Compliance evaluation
• Deployment
• Validation
• Evidence generation
• Artifact transfer
• Operational feedback

coordinated arrangement of activities, dependencies, conditions, inputs, and outputs through which work progresses toward an identified result

DIDO-controlled term adapted from:

• ISO 9001 process-approach guidance
• ISO 12651-2, Electronic Document Management — Vocabulary — Part 2: Workflow Management
• National Institute of Standards and Technology definition of Workflow Management System

A Workflow can include manual activities, automated activities, or both.

A Workflow differs from an individual activity. An activity performs a bounded unit of work, while a Workflow coordinates the progression and relationships among activities.

A Workflow does not require complete automation.

A Workflow definition identifies the structure or rules governing the work. A Workflow instance represents one execution of that definition.

A Git-based Workflow uses Git repository states or operations to coordinate work.

A GitOps Workflow applies GitOps principles to the management of software systems, applications, infrastructure, or services.

A repository commit initiates a Workflow that retrieves the identified repository state, builds an Artifact, performs security and compliance evaluations, records the results, deploys the Artifact, and validates the resulting deployment.