Architecture Principles
(
)
Et governance verktøy - * General rules and guidelines * Should be enduring and seldom amended * Should be clearly related to business objectives * Architecture principles cover the four architecture domains (BDAT) Examples: Application Interfaces Are Explicitly Defined Template * Should be succinctly and unambiguously communicate the fundamental rule * Navn som representerer essensen * Should represent the essence of the rule, and be memorable * Should not mention specifc technology platform * Should avoild ambiguous words Rationale * Should highligh the business benifits of adhering to the principle, using business terminology * Shoud describe the relationship to other principles Implications * Should hightlight the requirement for the business and for IT for carrying out the principle * Should state the business impact and consequences of adopting the principle HOW? * Understandable (they can be quickly grasped. Intent is clear and unambigious) * Robust (a principle must be precise to support consistent decision making in complex situations) * Complete (principles cover every situation percieved) * Consistent (principles must be expressed in a way that allows a balance of interpretations and should not be contradictory) * Stable (principles must be enduring, yet able to accomodate change)