OG0-093 · Question #281
Which of the following reasons best describes why the ADM numbering scheme for versioning output is an example and not mandatory?
The correct answer is B. To permit adaptation as required. This question explores the rationale behind the ADM's versioning numbering scheme being an example rather than a mandatory standard.
Question
Which of the following reasons best describes why the ADM numbering scheme for versioning output is an example and not mandatory?
Options
- ATo show the evolution of deliverables
- BTo permit adaptation as required
- CTo enable use with the Architecture Content Framework
- DTo support change management
How the community answered
(36 responses)- A3% (1)
- B94% (34)
- C3% (1)
Why each option
This question explores the rationale behind the ADM's versioning numbering scheme being an example rather than a mandatory standard.
While showing the evolution of deliverables is a purpose of versioning, it does not explain why the ADM's specific scheme is an example rather than mandatory; an example scheme can still fulfill this purpose.
The ADM numbering scheme for versioning architecture output is provided as an example to offer guidance, explicitly allowing organizations to adapt it to best suit their specific architectural practice, existing version control systems, and project needs without being constrained by a rigid standard.
The non-mandatory nature of the ADM's numbering scheme is primarily about organizational flexibility, not specifically about enabling its use with the Architecture Content Framework, which defines content structure.
Supporting change management is a key benefit of any versioning scheme, but it does not explain the specific reason why TOGAF's scheme is an example and not mandatory, as a mandatory scheme would also support change management.
Concept tested: ADM Versioning Scheme Flexibility
Source: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap06.html
Topics
Community Discussion
No community discussion yet for this question.