The Architecture Crystal Ball: Predictions for 2012

I have had the opportunity to read several documents containing estimations on what the chief architects and CIOs should expect of the concept of Enterprise Architecture in 2012. As a result I have made some thoughts of my own, and my thoughts have been delimited to what could happen in Scandinavia. There are reasons for when or where the organization should develop. Most of the articles that I have read in order to identify the potential development of Enterprise Architecture in 2012 were developed by American organizations and my assumption is that American organizations usually apply an American approach to … Continue reading The Architecture Crystal Ball: Predictions for 2012

Developing Frameworks: Five Things To Do and Five Things To Avoid.

The Essentials While working with the concept of Enterprise Architecture it usually becomes a necessity to chose and implement a framework. As such the chief architect can either implement a standard framework, and as such commence the project of documenting the AS – IS situation1. It is an option to adapt the standard framework in order to make it suitable for the enterprise as such make it work better in the implementation process. An alternative to deal with a standard framework the chief architect could develop his or her own framework that from the start has been developed in mind … Continue reading Developing Frameworks: Five Things To Do and Five Things To Avoid.

The IGIA-Framework

During the summer of 2010 I worked with a literature review that basically dealt with how Enterprise Architecture (through Coherency Management) could be addressing the issue of rewiring the form of leadership which exists in the enterprise. The IGIA-Framework is a form of synthesis of various theories within the field of corporate governance, IT strategy, IT governance, Workforce planning, Enterprise Architecture and Coherency Management. The edition of the framework that is released with this blog post is advocating a big bang change approach which demands a lot of resources and a long term commitment. This will be altered with the … Continue reading The IGIA-Framework

A Compendium for Understanding Enterprise Architecture.

I hereby publish the notes I have taken during the course in Enterprise Architecture that I have attended at the IT University of Copenhagen in the spring of 2010. The compendium is published under creative commons SA, BY, NC which means that it can be used for most purposes; however the purposes have to be non-commercial. The notes are centered on Bernard’s EA Cube and the statement “EA = Business + Strategy+ Technology” and that has been the key organizer for how the notes are presented in the compendium. You can download the compendium here. Continue reading A Compendium for Understanding Enterprise Architecture.

The Foundation for Coherency Management: A Framework for Change.

A Framework for Organization to Embrace Coherency Management When an organization choses to pursuit the implementation of Coherency Management then it the organization have to focus on organizational change. The idea of the organizational change is when the managers, middle managers and the employees will have to work in a different way and humans and organization culture have a tendency to be conservative and react hostile against change. For this the Coherency Architect should focus on how create the proper form of change within the organization. A Quick Summary of Coherency Management Coherency Management deals with how to achieve alignment, … Continue reading The Foundation for Coherency Management: A Framework for Change.

Extending and formalizing the framework for Information Systems Architecture

The Concept of the Framework The framework can in some ways be compared to techniques such as the flowchart (that was introduced by John von Neumann back in 1945. The flowchart is fine for many different issues and a flowchart is good to illustrate algorithms and flow of goods and processes. Entity – relationship diagrams are used to show entities among various objects, processes and databases. The purpose of the framework is to show how everything fits together and how they interacts. There are 30 boxes that are organized in six columns. The 30 cells or boxes are indeed intended … Continue reading Extending and formalizing the framework for Information Systems Architecture

The EA Management Program: From the perspective of a Coherency Architect.

Why a Program and not a Project Enterprise Architecture is dealing with configuring many different components of an organization (Bernard) and these components can rarely be configured properly through a big bang change as a project would usually be. A program can be defined as a series of projects that will change different components in a evolutionary approach. Since Enterprise Architecture and Coherency Management is dealing with more than people then it the changes can’t be implemented with a big bang approach since it will either fail by the people will go back to the old way of doing things … Continue reading The EA Management Program: From the perspective of a Coherency Architect.