Architectures matrix might be useful in enterprise architecture process.

Friday, September 24, 2004

Enterprise Architecture

Enterprise architecture is actually combination of several architectures that together forms the enterprise architecture. The process of creating and maintaining enterprise architecture is quit complicated, therefore there are several architecture framework to help us build enterprise architectures. Some of those frameworks are using methodic attitude and other use more pragmatic one (TOGAF).

One of the convenience and efficient way that I use is creating matrix of all of the enterprise architectures. That matrix helps a lot to map the architecture by the enterprise needs, constraints etc. this matrix mapping not just supply a map of enterprise demands and architecture points that meet enterprise demands it also helps us to see how and what architecture decision effect the business. I usually use that matrix to compare different architecture attitude to see which one of them answer most of the business demands.

How to build architecture matrix? Well the X axis holds the output of business architecture which is actually all business demands, needs, vision, constraints etc’. the Y axis is split into several categories as the number of enterprise architectures that make together the enterprise architecture. I use to do work on 5 different architectures that include: Information, Application, Software, Engineering and technological. Every category holds rows for each architecture point together with indication when certain architecture point fulfilling one of the business demands (mark in the right cell). If one architectural point conflict with one of the enterprise business needs and indication for that conflict should me mark as well.

Just for demonstration purpose here is partly imaginary matrix :

Business needs / other Arc. points	7*24 systems	User can move between systems build by diff teams without being aware of	Using existing products	Minimize distribution to user machines from technical and financial reasons	No private or un-retrieval data storage will be build	No duplication of data or code.	Minimize systems maintains
Information
Entity oriented		+			+	+
One entity the only responsible for handle entity data.						+
Application
Application connect different information entities into given context					+	+
Web development	+	+		+
Software
OO development.							+
Using design patterns.	+		+				+
Engineering
Server consolidation.	+						+
Grouping as much as possible system components on single server.	+						+
Technological
Purchase of controls / products			+

No Comments