Comprehensive and Detailed Explanation
In TOGAF, Architecture Contracts are agreements between development partners and sponsors that define:
The quality expectations.
The fitness-for-purpose of the architecture.
The responsibilities of each party and the governance arrangements.
Architecture Contracts are a key part of Phase G: Implementation Governance, where they are used to manage and control architecture implementation. They help ensure that implementation projects remain aligned with the approved Target Architecture and business objectives.
They serve as the formal mechanism for:
Providing a measurable basis for conformance assessment.
Supporting architecture governance by linking architectural intent with project execution.
Why the other options are incorrect
B. The Statement of Architecture Work: This defines the scope, approach, resources, and schedule for architecture work, but it is not a joint agreement on deliverables and fitness-for-purpose.
C. Service Level Agreements (SLAs): These are agreements about operational service levels (e.g., availability, performance), not architecture deliverables.
D. Non-disclosure Agreement (NDA): This protects confidentiality of information but does not address deliverables, quality, or fitness-for-purpose of an architecture.
References
The Open Group, TOGAF® Standard, Version 9.2, Part II: ADM — Phase G: Implementation Governance, Architecture Contracts.
The Open Group, TOGAF® 9 Certified Study Guide — explanation of Architecture Contracts as a governance tool.
