Enterprise Architecture – Modeling Tool

When thinking about modeling enterprise architecture, the choice of a modeling tool is very often considered.

One of the natural candidates is Enterprise Architect. The Enterprise Architect’s candidacy usually comes from the fact that it is used by broadly understood IT.

IT often attempts to implement elements of enterprise architecture as part of a bottom-up initiative.

The aforementioned situation is not, in my opinion, completely perfect. In my opinion, enterprise architecture should go from the level of the organization’s management. The world, however, is not perfect.

In addition, there are different visions of the importance of enterprise architecture in the organization. Knowledge of issues related to enterprise architecture is also different. Quite often the so-called “Business” is “attacked” by enterprise architecture by IT. The effects are different. However, you can try to sort out the topic somehow.

From my perspective, before you start choosing a tool for modeling enterprise architecture, it is worth considering a few issues.

  1. Why do I want to have models describing enterprise architecture? How will it help? What will make it easier?
  2. Will the enterprise architecture models reflect the company’s strategies? Will it be tools for members of the board or management? (I do not write that decision makers will model J)
  3. Who will deal with the models of their updating and maintenance?
  4. What perspectives will be maintained in the architectural model?
  5. How artifacts and activities related to enterprise architecture models will be integrated with the current mechanisms regarding business processes and software development ?

There is no simple answer to this question. There is no, because each organization is different. In one model, business processes are modeled, and no one, including IT, knows about them (I have simplified things a bit). In another organization, you do not model at all, and JIRA and Word reign supreme. Still in another business processes are modeled in a tool quite different from what IT uses.

Question: Why have I always exchanged business and IT processes?

Well, there is no chance of successful long-term action that does not connect these two worlds. Business needs IT help and IT needs business to exist.

Enterprise architecture can be such a binder that, through a description at a higher level of abstraction, will help to understand the organization.

So, what is the tool for modeling enterprise architecture to choose? The answer is the one that will allow integration of the business world with the world of IT. If “business” and IT model in the same tool and the tool has the appropriate functionality, the matter is clear. If ‘business’ and IT are modeled in different tools and no party wants to change their software, then they need to be filled with a methodology that will ensure coexistence. If, however, one of the pages does not model it, then the tool will probably be the tool that is used by the modeling page.

While the first and third variants are quite simple and very obvious, the second option is not necessarily the case. Secondly, not every tool for business process modeling or application design allows modeling of enterprise architecture. Personally, I would use the tools noticed by Gartner.

A list of such tools is available at: https://www.gartner.com/reviews/market/enterprise-architecture-tools. Apart from the list of tools, there are also reviews on this page. It is worth taking into account that the enterprise architecture modeling tool would be useful in our organization.

More from my site

  • Partially Done Work In the previous posts, I discussed the tasks and the board in Kanban. In order to be productive, you must focus on one task at a time. Kanban facilitates this process and defines the term […]
  • Implementation of the Methodology – Selection of a Modeling Tool In many companies there is a discussion about formalizing the software development process. Spontaneous creation of diagrams by broadly understood analysts and designers does not build […]
  • Requirements Management – Best Practices Ian Sommerville and Pete Sawyer in "Requirements Engineering: A Good Practice Guide" described, over 15 years ago, the method of assessing and improving requirements engineering […]
  • Maintenance Diagram in Enterprise Architect Very often thinking about software engineering we are thinking about software development. And what about its maintenance, development? It does not say about it too much. UML or BPMN […]
  • User Stories vs Requirements When writing any specification of requirements and the product register and sprint register, non-functional requirements should be included in this specification. While the user's […]

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top