Which section of the TOGAF template for Architecture Principles should highlight the business benefits for adhering to the principle?
Which section of the TOGAF template for Architecture Principles should highlight the business benefits for adhering to the principle?
The 'Rationale' section of the TOGAF template for Architecture Principles should highlight the business benefits for adhering to the principle. This section uses business terminology to explain why the principle is important and how it benefits the organization. It also describes the relationship to other principles and the conditions under which some principles might take precedence over others. The other sections like 'Name', 'Statement', and 'Implications' serve different purposes: the 'Name' simply labels the principle, the 'Statement' provides a brief and explicit summary of the principle, and the 'Implications' outline the requirements and consequences of following the principle.
Should highlight the business benefits of adhering to the principle, using business terminology. Point to the similarity of information and technology principles to the principles governing business operations. Also describe the relationship to other principles, and the intentions regarding a balanced interpretation. Describe situations where one principle would be given precedence or carry more weight than another for making a decision.
Correct answer: C A recommended template defining principles: 1. *Name* - Name of principle. 2. *Statement* - Should briefly and explicitly communicate the *fundamental rule*. 3. *Rationale* - Should highlight the *business benefits* of adhering to the principle, using business terminology. Also, describe the relationship and precedence to other principles. 4. *Implications* - Should highlight the *requirements, both for the business and IT*, for carrying out the principle – in terms of resources, costs, and activities/tasks. https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap20.html
https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap20.html A recommended template defining principles: 1. *Name* - Name of principle. 2. *Statement* - Should briefly and explicitly communicate the *fundamental rule*. 3. *Rationale* - Should highlight the *business benefits* of adhering to the principle, using business terminology. Also, describe the relationship and precedence to other principles. 4. *Implications* - Should highlight the *requirements, both for the business and IT*, for carrying out the principle – in terms of resources, costs, and activities/tasks. - The impact on the business and consequences of adopting a principle should be clearly stated.