INHOUD
Terug naar community
Magazine
Proceedings
Blogarchief
Scripties
Zoeken
THEMAS
De CIO spreekt
De architect antwoordt
De business bepaalt
Effect van architectuur
SOA
BPM
Methoden
Architectuurprincipes
Financiële sector
Overheidssector
Zorg sector
Meest gelezen artikelen
 
 
BLOGS
The Framework is the Meta-Architecture of an Enterprise Architecture
Adrian Grigoriu   
zaterdag, 06 maart 2010

"If you have ever watched a house being built, or if you have ever had an addition put onto an existing house, you know that the standard method of communication is a big piece of paper called a blueprint. Blueprinting is the standard method used to copy large architectural and construction drawings. A blueprint used to consist of white lines on a blue background. A more recent process uses blue lines on a white background." (from here).

The blueprint is designed by the architect and used by the plumber, electrician, owner, potential buyer... It comes with guidance documentation, when necessary. A plan of transformation is the result of strategy executed as (a portfolio of) projects transforming the blueprint components.

The blueprint reflects the structure that changes in time with its purpose. The architecture could be classic or baroque, depending on the architectural style. The relationship between structure and its purpose is shaped by the architectural style.

Similarly, the EA blueprint is not static. It should be constantly updated to reflect the change in structure result of all on-going projects in an Enterprise. That may not always happen but this is the role of the EA architect.

The EA blueprint is the base of all conversations on changing the structure to fit the purpose or fitness for purpose, maintenance, renovation and transformation. It should be the basis of change in the Enterprise, be it operational, tactical or strategical. Without a blueprint, the transformation cannot be properly managed; the Enterprise would grow organically until a point when nothing works properly any longer and its decay starts.

The EA, as a blueprint, should be seen as the cornerstone of any Enterprise transformation, as a strategy, as in the title of a well known but less practical EA book.

But the core of any EA development is the framework, i.e. its meta-architecture.The framework is the glue between components and artifacts. Without a good framework, there is no navigation between artifacts and their components.

Adrian PS: you may find on this blog a good list of EA book reviews http://www.angryarchitect.com/




Reacties (3)
RSS comments
Geschreven door Dit e-mail adres is beschermd door spambots, u heeft Javascript nodig om dit onderdeel te kunnen bekijken op 06-03-2010 11:13
 
 
Here is the missing link for blueprints 
http://science.howstuffworks.com/question321.htm

  
Geschreven door Ton Eusterbrock op 09-03-2010 11:33
 
 
Another nice articel about blueprints: http://research.paauwe.info/downloads/Paauwe_Research_Enterprise_Architecture_Blueprint.pdf 
 
Using posters in communication is very useful. More on how to create one: http://research.paauwe.info/downloads/Paauwe_Research_presentatie_Mooie_architectuurposters_maken.pdf 
 
I do agree, The style of communication is one thing, the content is another. And we need some EA-framework that guides us to create the content itself.

  
Geschreven door Dit e-mail adres is beschermd door spambots, u heeft Javascript nodig om dit onderdeel te kunnen bekijken op 09-03-2010 17:13
 
 
Thanks Ton. Good sites. I also think that a blueprint should be hierarchical though so one can stop at the level of decomposition one is comfortable with.  
I do an One Page Business Architecture first; then I leave the domain experts to do (and own) the designs that link into its components, within the constraints imposed by the framework, architecture principles and guidelines. The poster would be always to small to reveal the detail some EA stakeholders would need. I describe this in my EA book. 
Adrian

  

Alleen geregistreerde gebruikers kunnen reacties geven.
Log in of registreer.
 
[ terug ]

Via Nova Architectura is not responsible for the content of blogs, but authors and readers are asked to adhere the following guidelines. Authors are strongly encouraged to check facts, cite sources, present balanced views, acknowledge and correct errors. Respect copyright, fair use and financial disclosure laws. Please do not disparage organizations, or individuals. Being critical of someone's practice is acceptable, when it is done in a professional manner. Prevent usage of marketing statements. Comments should be relevant to the specific post they are attached to. Spam, flaming, personal attacks, and off-topic comments are not permitted. Readers are requested to notify Dit e-mail adres is beschermd door spambots, u heeft Javascript nodig om dit onderdeel te kunnen bekijken of any violations. The editor holds the right to remove any statements that, in the editors opinion, infringe the above guideline(s). The author receives a notification of this action.