Free sections from Ultra Transcenders OGEA-102: Enterprise Architecture Practitioner, on the comparisons and decisions the exam keeps asking about.
What each architecture state means, why candidate work cannot govern change, and a practical way to organise states and recency in the repository.
Why security architecture is not a separate domain, why every stakeholder has security concerns, and how security services differ from a control framework.
How to identify stakeholders beyond the organisation chart, classify their positions, place them on the power/interest grid and tailor what each group receives.
Why more than one option is worth showing, the criteria used to judge them, and how the choice is made jointly with stakeholders at a formal review.
The three basic approaches to change, the implementation methodologies that follow them, and how readiness and risk evidence point to the right fit.
What an Architecture Contract settles, the points in the cycle where contracts arise, and the three kinds of contract with the parties each one binds.
How the governance body decides how large a response a change deserves, the three categories of change and the stakeholder guideline for redesign.
The three classes of standard, the five lifecycle states from proposed to retired, and what a deprecated standard does and does not require.