The perpetual question for enterprise architects is, which is the best enterprise architecture management tool. I have my favourite based on the past years experience, which I selected after a careful analysis of potential candidates. One of my clients requested a comparison between two tools and I would share the results here. Shortly the two tools are SAMU from Atoll and EA from Sparx. The summary of the comparison is, that they have to exchange the name they have! SAMU (System Architecture Management Utility) is a real enterprise architecture management tool, with all necessary aspects, while EA (Enterprise Architect) is a great system design tool, with very limited capability to be extend to enterprise wide repository.

Referring back to article The structural strength of steel, I will share some practical examples to encourage architect colleagues to break out of the role of „boxes and lines“ - which is usually expected from us. All of us should know stones and bricks what our architecture is built from - still should not be the best bricklayer, but even not the worst!

This first article is an infrastructural task, building a Redis cluster in well-controlled Linux environment on a RHEL7 host.

Today, all companies wants to become agile. This is great. Most of them wants to be agile by applying one of the Agile methodologies. What is strange. Let’s go through the intention, what shrives this „agility movement“!

I saw and heard many times (certainly not at you), that professionality is over in the IT field. Quality falls, deadlines are missed, costs are increasing and the joy of creation lost somewhere on the road. In the past everything was better and so. 

What could be the reason? Large projects are still exists, empowering targets are still there, more money spent then ever - it seems to be a perfect situation to fly and still... I collected you some reasons for those cases when this bad feeling is right. Some ammo for the feeling of 'anno Domini'.

Without competition, the things will not improve. On the other hand multiple parties in a competitive situation may cause different problems. Let's go through these issues and get some tips to handle them.

If you never met this question you are living somewhere else but not in the IT industry! Here I collected some practical examples you may refer to when facing the question in the title. Here at the start my position about rules and principles: freedom is made by great rules and this is a basement to maximise ability to change! This article is the continuation of Rules and exceptions article.

What is the best development methodology? Waterfall? Agile? An iterative model? Something else? Companies and projects are looking to find the best approach to deliver on time and on budget and still keeping the scope. People are arguing in personal discussions and forums highlighting pros and cons about their best one, but I did not see the ultimate answer. Now I can help you to have it!

The eternal question is if size matters or not? One says it is important others think it is not, while there are people saying: it depends. What is the best size? Sure you may say the larger is better? You are maybe right. May be not... Come and read more to get the answer!

We reached the next staged to make Reactor to be more simple to demonstrate. Till now, it was possible to try it out through Swagger-ui and a chatbot, but from now on you can play with a browser based responsive UI to learn about Reactor. This UI enables all operations about cart based service manipulation: open a cart, order or remove product offerings or drop/commit a cart as you wish.

New year, new ideas. Look into the details of a new dimension of architecture measurements, extending the minds of The immortal temporary solutions article. The new dimension is Success, based on the definition described in new book from Albert-László Barabási: Formula - the Universal Laws of Success.

Reactor was made to serve each type of front-end applications, who want to handle multistep service manipulation carts. The interfaces have sophisticated data structure to minimise the API requests, like an add operation can respond with the new CurrentPortfolio state of Reactor transaction together with the update AvailableProductOfferings list. Other it is fine for many applications, others require simplified interfaces having predefined standard response structures. One example is chatbot.

Page 1 of 4

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