| |
| dido:99_annexes:annex-b-terms-and-definitions:s:software_factory [2026/07/13 09:40] – created nick_dido | dido:99_annexes:annex-b-terms-and-definitions:s:software_factory [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| A Software Factory integrates the people, processes, tools, services, infrastructure, policies, controls, and information required to develop, build, test, package, release, deploy, maintain, and govern software products. | A Software Factory integrates the people, processes, tools, services, infrastructure, policies, controls, and information required to develop, build, test, package, release, deploy, maintain, and govern software products. |
| |
| A Software Factory coordinates activities across the software lifecycle through repeatable workflows and controlled interfaces. It may include source control, build automation, testing, artefact management, dependency management, security analysis, compliance assessment, deployment automation, monitoring, and configuration management. | A Software Factory coordinates activities across the software lifecycle through repeatable workflows and controlled interfaces. It may include source control, build automation, testing, artifact management, dependency management, security analysis, compliance assessment, deployment automation, monitoring, and configuration management. |
| |
| The factory concept includes more than a collection of development tools. It includes the operating model, responsibilities, controls, information flows, and managed environments that produce and maintain software artefacts. | The factory concept includes more than a collection of development tools. It includes the operating model, responsibilities, controls, information flows, and managed environments that produce and maintain software artifacts. |
| |
| An [[dido:99_annexes:annex-b-terms-and-definitions:a:accredited_software_factory|Accredited Software Factory]] is a Software Factory that operates within an approved accreditation boundary under an applicable operational approval. | An [[dido:99_annexes:annex-b-terms-and-definitions:a:accredited_software_factory|Accredited Software Factory]] is a Software Factory that operates within an approved accreditation boundary under an applicable operational approval. |
| ===== Source ===== | ===== Source ===== |
| |
| Generalised from software engineering, DevSecOps, continuous delivery, platform engineering, and software-factory usage and specialised for the Crucible architecture and operational model. | Generalised from software engineering, DevSecOps, continuous delivery, platform engineering, and software-factory usage and specialized for the Crucible architecture and operational model. |
| |
| ===== Note ===== | ===== Note ===== |
| ===== Example ===== | ===== Example ===== |
| |
| A Software Factory combines source-control services, build workers, test services, artefact repositories, dependency repositories, security scanners, compliance services, deployment automation, and controlled operating procedures to produce and maintain deployable software. | A Software Factory combines source-control services, build workers, test services, artifact repositories, dependency repositories, security scanners, compliance services, deployment automation, and controlled operating procedures to produce and maintain deployable software. |
| |
| ---- | ---- |