Comprehensive and Detailed Explanation
In the TOGAF ADM, deliverables go through a lifecycle of development, review, approval, and usage. TOGAF distinguishes between draft deliverables (work-in-progress) and final deliverables (those that have been formally reviewed and signed off).
Draft deliverables are produced as working versions of the required outputs in each ADM phase. These may carry version labels such as 0.1, 0.5, 0.9, etc., and are subject to stakeholder review and refinement.
Once the document has been reviewed and approved by the relevant stakeholders (e.g., Architecture Board, governance bodies), it becomes a final deliverable.
Final deliverables are baseline-controlled items and are formally stored in the Architecture Repository as an approved architecture artifact.
Thus, the correct term for a deliverable that has completed review and is approved is “final”.
Why the other options are incorrect
B. Approved: While true in general language, TOGAF uses the formal term “final deliverable”, not “approved deliverable.”
C. Ratified: This term is not used in TOGAF to describe the state of a deliverable.
D. Version 0.9: This is a draft numbering convention, not the status of an approved deliverable.
References
The Open Group, TOGAF® Standard, Version 9.2, Part II: ADM — description of deliverables, artifacts, and building blocks.
The Open Group, TOGAF® 9 Certified Study Guide — explanation of draft vs. final deliverables in the ADM lifecycle.
