Each knowledge base about architecture faces the same challenge: find the balance between details and accuracy. The less details would mean simpler maintenance of data while it certainly less usable. If you have limited resources for future maintenance you have to make compromises. This article shows the way you can built up-to-date usable knowledge base with no bad compromises about scope and usability.

All we know applications, which are well design implemented on the right way but need continuous caring; and yes, we met those ones, the "temporary" solutions, which are surviving everything with no caring and no way to be killed. What could be the reason?

"Early bird gets the warm, the second mouse gets the cheese."
(W Nelson)

Which one would you be? The certain answer is: it depends...

One of the most famous topics today is Automation in the IT era. There are many different interpretations - as usual - therefore it is so important to define some levels of automation and the most interesting fields to focus on.

There are two main areas of automations: business function automation and systems operation automations. Another differentiation is if the process which is automated means the it is running with zero touch or the automation means that users of the process gets predefined steps, tasks to execute.

All we dream about simple architecture. Everything you always wanted to know about Complexity article described an approach to measure how complex our architecture is. The next question is to find the simplest solution in a multi-variable situation, which usually called project. This article shows an approach which ensures that all functions you implement will be on the best place from overall complexity point of view for greenfield cases, while we will discuss about brownfield situations also.

The most frequent criticism about product portfolios is: too complex! Based on the articles, which describes the problems of measuring complexity in general take a look to the product portfolios. A marketing manager defined me in the past: "Making a simple portfolio is an easy task; define a profitable one is the same. Creating one, which is simple and profitable is almost impossible." I do not know the medicine of the problem, but the method described here will help you to simplify using an exact measure same as financial calculations.

"The law of entropy tells us that the battle for simplicity is never over."
Roger Sessions.

All we now similar laconism about the problem of complexity. On the other hand, each Enterprise Architect knows, that our focus is to have a simple architecture. The real challenge behind this mission is that we are trying to optimise something what we cannot measure. The missing measure is the persistent doubtfulness if we go to the right direction. What is the solution?

How to calculate the cost of project delays? This article describes an approach, which shows the cost of delays in the percentage of net present value  (NPV) of projects. The theory is not prepared to use on a single project. The target is to show the cost of delays generally for a given organisation, which runs several project in parallel, since the method uses generalities. The result is usable to help avoid or eliminate the bottlenecks in the company or organisation.

The calculation prescinds from the every day’s business but still focuses to the real problem, which is the accurate delivery of project targets, by effective resource allocation.

The topic which enterprise architects are working on is architecture management. This is a standing locution. Do we really know the meaning of the two words? Let's look behind the scenes and define properly what we are speaking about! The article uses common definitions of architecture and management then interprets the management functionalities from architects point of view.

Ignaz Semmelweis was the "saviour of mothers". He was early pioneer of antiseptic procedures. He was referred to a mental institution - the place he died later. The linked article shows the details of his invention and invoke some thoughs of us about our "hygienic" work about managing Enterprise Architecture. Let's see some aspects, examples from EA practice when we work on something strange to our environment.

The Enterprise Architects as every professionals naturally would like to know how effective their work and how big their contributions in the business success. The maturity assessment of your Enterprise Architecture could answer these questions - and should be the basis of your improvements in the future and helps showing the provided values today.

Page 4 of 5

Architect Archers

Architect Archers are Enterprise Architect professionals and mentors.

Our mission is to build Your Archers team while defining, aiming and hit your Enterprise Targets.

© 2017 Architect Archers