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
Reference: "Implications - Should highlight the requirements, both for the business and IT, for carrying out the principle - in terms of resources, costs, and activities/tasks. "
link: https://pubs.opengroup.org/architecture/togaf8-doc/arch/chap29.html
upvoted 4 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Jodash
3 weeks, 2 days agonoureldin
8 months agoPrashanttheCloudMaster
1 year, 2 months agoRVR
2 years, 6 months ago