Business Patterns and EA

I’ve just finished writing a fascinating Report for Cutter Consortium about Business Patterns and EA. For some time now I’ve been working with EA practitioners who are taking advantage of information that has already been gathered by people from backgrounds other than EA. The EA role then becomes one of converting or translating this information into architectural constructs or language.

In many situations there is a wealth of knowledge that architects can draw upon. The trick is to add value through good architectural thinking.

In this case, there is plenty of research and studies that have identified common, generic business patterns. And the correspondence between these business patterns and the relevant architecture components is very high.

Not only that, but the criteria used to find these business patterns are also very useful in EA, as the criteria for segmenting the architecture into meaningful chunks, or as criteria for deciding the most appropriate ways to improve the architecture. For example, business patterns might be differentiated by scope, scale and speed – which are all important considerations for designing an architecture. These business patterns and criteria often help identify the most important business capabilities, as a focus for architectural efforts.

If you haven’t already done so, I would certainly recommend looking into business patterns and how they might inform your EA work.