20.3 Components of Architecture Principles Table 20-1: Recommended Format for Defining Principles Implications Should highlight the requirements, both for the business and IT, for carrying out the principle - in terms of resources, costs, and activities/tasks. It will often be apparent that current systems, standards, or practices would be incongruent with the principle upon adoption. The impact to the business and consequences of adopting a principle should be clearly stated. The reader should readily discern the answer to: "How does this affect me?". It is important not to oversimplify, trivialize, or judge the merit of the impact. Some of the implications will be identified as potential impacts only, and may be speculative rather than fully analyzed. https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap20.html

Correct Answer 20.3 Components of Architecture Principles Name - Should both represent the essence of the rule as well as be easy to remember. Statement - Should succinctly and unambiguously communicate the fundamental rule. Rationale - Should highlight the business benefits of adhering to the principle, using business terminology. 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/togaf92-doc/arch/index.html