FR-DSO-001 — Git-Based Workflow Integration

Go to C.3.8 DevSecOps Integration

Crucible SHALL integrate with Git-based workflows.

This requirement derives from:

• Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DSO-001

The Original Requirement states:

The system shall integrate with Git-based workflows.[C1]

FR-DSO-001:

• Replaces The system with the defined system name Crucible
• Changes shall to the established uppercase normative form SHALL
• Links Git to its controlling definition
• Retains the source behavior integrate with Git-based workflows

No other substantive normalization is required.

A Git-based workflow uses Git repositories, repository states, and change-history operations to coordinate controlled changes to managed content.

Integration with Git-based workflows enables Crucible operations to participate in workflows based on identifiable repository content and recorded changes.

Such workflows can involve:

• Repository cloning
• Repository synchronization
• Branches
• Commits
• Tags
• Merge operations
• Change review
• Repository-triggered automation
• Selection of an identified repository state

This requirement establishes integration with Git-based workflows without prescribing:

• A particular Git-hosting service
• A particular repository provider
• A branch strategy
• A merge strategy
• A review process
• A repository layout
• A commit-message format
• A triggering mechanism
• A CI/CD Pipeline
• GitOps behavior
• Automated build, deployment, or validation behavior

Separate requirements, architecture specifications, workflow definitions, and repository policies govern those subjects and behaviors.

This requirement applies to:

• Crucible
• Git repositories
• Git-based workflows
• Repository integration operations

Verification confirms that:

1. A Git repository and a Git-based workflow are selected for testing
2. The selected repository contains an identifiable repository state
3. Crucible participates in the selected Git-based workflow
4. Crucible accesses or receives the repository information required by the tested workflow
5. The tested Crucible operation uses the identified repository state
6. The resulting behavior demonstrates integration with the selected Git-based workflow

The following pages reference this requirement:

Implemented and Verified

Review and approve FR-DSO-001 as a leaf requirement.

Determine whether separate requirements identify the Git repository operations that Crucible must perform.

Determine whether separate requirements govern repository authentication, authorization, and credential management.

Determine whether separate requirements identify the repository state used by each Crucible operation.

This requirement page retains the stable requirement identifier FR-DSO-001.

This page is a leaf requirement page and omits a trailing :start from its namespace.

The Statement uses the controlling Terms and Definitions entry:

• Git

The Statement addresses integration with Git-based workflows. It does not require a particular Git-hosting service, repository provider, branch strategy, merge strategy, review process, or automation mechanism.

FR-DSO-002 governs GitOps workflow integration.

FR-DSO-003 governs CI/CD Pipeline integration.

FR-DSO-004 through FR-DSO-006 govern automated build, deployment, and validation execution.

Do not add particular repository operations, hosting services, branch policies, triggering mechanisms, authentication methods, or automated execution obligations unless the controlling requirement changes through an approved requirements process.

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

{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-08-devsecops-integration:fr-dso-001#Statement&noheader&nofooter&noeditbtn}}