Less Is More

In my last post I have written about the concept to compare Enterprise Architecture with the Matrix. In short: free your mind and open up for all the possibilities. There is no reason to stay inside the boundaries provided by the various frameworks and models. They are helping, but not the answer. The real change happens by working with the people and there is the place where the real Enterprise Architecture is happening. With and through the people.

Today I have read an interesting post of Tom Graves where he brought Ric Philipps and his definition of Enterprise Architecture being an antipattern to my awareness. The result is that I follow (just another) Enterprise Architect, which is great. The concept in that particular post is interesting, because Enterprise Architecture adds another level of complexity which might easily outweight its benefit. I personally see Enterprise Architecture (as any other form of Architecture) as waste.

via Social Enterprise Architecture.

Posted in EA | Tagged | Leave a comment

Business Needs To Take A Moneyball View On Performance | Forrester Blogs

I recently finished reading Moneyball, the Michael Lewis bestseller and slightly above-average Hollywood movie. It struck me how great baseball minds could be so off in their focus on the right metrics to win baseball games. And by now you know the story — paying too much for high batting averages with insufficient focus where it counts —metrics that correlate with scoring runs, like on-base percentage. Not nearly as dramatic — but business is having its own “Moneyball” experience with way too much focus on traditional metrics like productivity and quality and not enough on customer experience and, most importantly, agility.

 

Posted in BPM | Tagged , , , , , | Leave a comment

How to elaborate a Business Model with Enterprise Architecture?

How does an Enterprise Architecture and a Business Model work together?

Successful organisations are those that improve and innovate their Business Models to find a profitable niche against their competitors.

But a new Business Model alone is not enough. It needs to be implemented and executed. This is where an Enterprise Architecture comes in.

If organisations do not align their Business Model and their Enterprise Architecture then how can they be certain of making it work?

The first step is integrating the Business Model with the Business Architecture part of the Enterprise Architecture. This is described below.

via How to elaborate a Business Model with Enterprise Architecture? « on Enterprise Architecture.

Posted in Capability, Model | Tagged , , | 2 Comments

TOGAF® and BIAN – A strong proposition for the Banking Industry | The Open Group Blog

TOGAF® and BIAN – A strong proposition for the Banking Industry By Thomas Obitz, KPMGEarlier this year, a working group led by Paul Bonnie, ING and I published a white paper on the integration of TOGAF® and BIAN, the framework of the Banking Industry Architecture Network. Gartner even suggested that the white paper greatly aids the big problem of arriving at a consistent reference model for banks. So how does a white paper help practicing architects in banks?

via TOGAF® and BIAN – A strong proposition for the Banking Industry | The Open Group Blog.

Posted in EA, Model | Tagged , , | Leave a comment

MEGA – Do you know the value of enterprise architecture?

MEGA International invites you to view a brief video to get an executive perspective on the benefits of embracing enterprise architecture.
While enterprise architects have long been aware of the broad business value of EA, not all potential stakeholders have a clear grasp on how it can improve different aspects of their operations.

Posted in EA | 5 Comments

10 things to consider when buying a modeling tool

1: It must have a repository (a real repository)

Many tools can create drawings, e.g. Visio, but for a modeling tool to be efficient, it must have a repository to save, reuse and analyze the objects that is being created on the drawings. The repository makes sharing models and objects between multiple users possible. Also sharing of objects and the re-use of objects across different models is possible.

The repository must be based on meta-model defining the different possible relationships between objects.

2: The meta-model must be extendable

Modeling projects are always different from project to project and from company to company. Having a meta-model that can easily be extended is crucial – with new relationships or objects. Extending the meta-model should be easy and preferbaly done in a graphical way by using models in the modeling tool.

3:  User friendly interface

In order to create models efficiently it’s important that the interface is user-friendly, making it easy to re-use and insert, e.g. by using drag and drop, objects in models.

4: Out-of-the-box frameworks

The tool should have out-of-the-box frameworks like TOGAF, Zachman, NAF, DoDaf etc. making it easier for a user to start-up a new project.

5: Importing and exporting data

Most projects, at least Enterprise Architecture projects, start by importing a long list of data, e.g. Applications, Services, and Capabilities etc. into the repository. This import should be done in an efficient way preferably directly from tools like Excel, since most of the needed information is stored in Excel list, before companies are taking a repository based tool into use. Also exporting information from the repository into list in Excel is also a needed functionality.

6: Visualizations of models

Models are created and communicated most efficiently by using graphics and drawings. Most often the information stored in the repository has to be presented to non-technical stakeholders where diagrams is quite often the best way of communicating.

7: Analysis capabilities

The value of a modeling tool is no longer coming from creating drawings and models, but from extracting and representing information for different stakeholders. Being able to analyze different aspects of data in the repository, is today perhaps one of the most critical capabilities in a repository based tool.

8: Quality of Data

For users to find the models and information extracted from the repository credible, the data quality in the repository must be high. To achieve this, the tool must have good technical reporting capabilities as well as good search capabilities. Search capabilities is also crucial for making sure that objects and building blocks can be re-used across different models. It’s no good to enter a lot of information into a repository if the data cannot be found again when needed.

9: Interfaces to other tools

No tool is an island – and this goes especially for modeling tools that are quite often depending on information stored in other tools. A modeling tool should therefore support interfaces to other tools like ERP systems, CMDBs etc. preferably by having a strong API making these interfaces possible.

10: Good vendor support

Maintaining and supporting an Enterprise Architecture repository is a serious ongoing business. Having a credible vendor support, with a roadmap of regular updates is crucial. New methods, frameworks and solutions are constantly popping up, and having a good vendor that, based on a vast experience, can distinguish what is sound and what is not sound to put into the roadmap is important.

Posted in EA, Model, Repository | Tagged | Leave a comment

Conceptual, Logical, Physical: It is Simple by: John A. Zachman

I don’t know why everybody has so much trouble figuring out the difference between Conceptual, Logical and Physical… let me explain this one more time…

via Conceptual, Logical, Physical: It is Simple by: John A. Zachman.

Posted in EA, Model | Tagged , , , | Leave a comment