The importance of Frameworks

I'll continue my Frameworks and Enterprise Architecture series for a short while.

The framework importance is de-emphasized deliberatelysometimes. But without a framework though, it is impossible to have foreseeable,  repeatableand integrated outcomes. Same development would have a different path and differentoutcomes at different times. Every development might link the same parts in differentways. Two teams may come at very different results for the same development.

A framework describes the architecture of the architecture, that is themeta-architecture of a system or an Enterprise.

Stakeholders' views must all relate  back to the framework. Otherwise, one ends up with a simple folder ofunrelated, unnavigable artifacts whose sum does not reveal the whole. Impactsof change cannot be analysed.

An extend framework has to cover not only the structure, operation, and layeredresources but the development process, governance, value measurement, ... allaspects of a development. You do not have to do this framework work again and again.Such a framework would enable navigation.
A framework should have at least:

* a business  process map (like eTOM ) to describe structure

* an Information map (like SID) to establish key entities and vocabulary

* a business flows map to describe the behaviour

* the key layers/domains  (process, information, applications, technology, people...)

* a  development method/process with steps, deliverables...

Adrian

---

Posted 02-15-2010 9:14 AM by Adrian Grigoriu