Jan
20
Andy Willmot writes on his view of enterprise architecture and he believes that enterprise architecture is best described as a set of principles, as follows:
- Framework driven - "….The important lesson is one of ensuring conformity to a framework, whatever that framework be. All organisations are different, and it’s up to the EA community to identify, base upon or create a fresh the most appropriate framework to use. Without a framework driving EA activity, the deliverables are often inconsistent and have little understanding beyond the EA community."
- Abstractional and Dimensional - "Our current thinking on an organisation generally leads us to perceive in two main ways. Firstly, in differing levels of abstraction. That is, the level of depth viewed of an organisation. E.g. a CTO’s level of abstraction is far different to that of a Developer.
Secondly, by dimension. This is the vertical facet of the organisation we’re wanting to perceive. This could be information, people, function, etc. This will be very much dependent on the objectives of the EA activity." - Vertically and horizontally interdependent - "Interdependency is key to EA. Without it EA activities become individual, siloed analysis streams that cannot relate to one another. One of the clear benefits of EA is to align these activities across an enterprise and produce architectural insight that benefits the development of the organisation."
- Purposeful - "Many EA activities today do not have clear purpose…… It’s therefore very important we remember to set clear objectives for any EA tasks and ensure we stick to them throughout."
- Measureable - "There aren’t many projects within major business today that don’t have a business case to back up the benefits of completing the project…. It’s important though to think of any EA activity as we would any other project and ensure we measure benefits to the organisation throughout."
A great list of the attributes of enterprise architecture. What attributes do you feel are missing from this list?

