Jun
12
Mike Walker wrote and interesting post on a discussion he had on “Making Sense of Architecture Standards" which resulted in the following image:
- Taxonomy and Ontology: Such as IEEE 1471, “. . .an architecture is a conception of a system. There may be many conceptions of a system… What this provides to the enterprise architect, solutions architect or domain architect is a way to have a constant set of terms for describing what it is they are building. This should be at the core to your architecture activities.”
- Information Model and Decision Support: Decision support help us to "..focus more on … What are the right questions … How do I organize those questions … What do those answers mean … Meaning what is the process in which I get the information, consume it, process it and ultimately make it actionable."
- Process Framework: "… when talking about decision support, there is a need for a process to wrap how we make our decisions…. Having this higher level process framework is essential to architects. There are a series of benefits for the organization … Constancy in how solutions are created … The right people are selected for the right job … Proper metrics can be obtained to gauge health of the EA process … Predictability of results which lends to being able to apply some level of risk management to decisions"
- Actors: These are people with the appropriate skills and competencies.
- Manage: The ability to effectively execute strategy and tactics "…This aspect covers PMO based processes, service management and IT Governance aspects. In the service management area specifically we are seeing closer alignment with EA. The latest version of ITIL has alignment with EA practices."
This is a great overview of the enterprise architecture standards and how they relate and interact.
Technorati Tags: EA, Enterprise Architecture, Framework, Standards, ITIL, TOGAF, IAF, Zachman, IEEE 1457, PMO, Process

