dido:99_annexes:annex-b-terms-and-definitions:a:accreditation_boundary

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

dido:99_annexes:annex-b-terms-and-definitions:a:accreditation_boundary [2026/07/13 09:28] – created nick_didodido:99_annexes:annex-b-terms-and-definitions:a:accreditation_boundary [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 19: Line 19:
 ===== Source ===== ===== Source =====
  
-Generalised from security-accreditation, authorization-boundary, conformity-assessment, and risk-management usage and specialised for the Crucible architecture and operational model.+Generalised from security-accreditation, authorization-boundary, conformity-assessment, and risk-management usage and specialized for the Crucible architecture and operational model.
  
 ===== Note ===== ===== Note =====
Line 29: Line 29:
 ===== Example ===== ===== Example =====
  
-The Accreditation Boundary for a Software Factory includes source-control services, build services, hardened build workers, dependency repositories, artefact repositories, compliance services, deployment automation, administrative processes, and approved interfaces to external infrastructure providers.+The Accreditation Boundary for a Software Factory includes source-control services, build services, hardened build workers, dependency repositories, artifact repositories, compliance services, deployment automation, administrative processes, and approved interfaces to external infrastructure providers.
  
 ---- ----
  • dido/99_annexes/annex-b-terms-and-definitions/a/accreditation_boundary.1783960101.txt.gz
  • Last modified: 2026/07/13 09:28
  • by nick_dido