Registration of Problems Identified During the Analysis

I received an interesting question by e-mail:

According to your knowledge, is there an object in EA that would be best suited for registering problems identified during business or system analysis (AS-IS)? I mean an object in which the parameters of the problem identified during the workshop would be registered, e.g. name, description, connection to the process, cause of occurrence, etc., and after registration it would be easy to export all registered problems in the form of a table to RTF , using the previously prepared template?

I have one answer. This is the place in Enterprise Architect that allows you to register such elements. This space is the property of each of the Maintenance elements.

In this element you can save, and I do it routinely: glitches, defects, problems, and planned tasks.

Each project team can define its application of the specified tabs.

The important thing is that among the templates we have a maintenance template that allows you to generate a report from the above elements.

I use the maintenance property not only when analyzing business processes but also when analyzing requirements and designing information systems.

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 […]
  • Kanban Reports Process management is a midway to success. The second midway is process monitoring and drawing conclusions. In Kanban, there are indicators, which enable process monitoring. They […]
  • Managing Relationships Between Requirements Requirements management is an important element of the software development process. One of its elements is building and managing relationships between requirements. The most common is […]
  • 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 […]
  • Architect in Agile Team In the last post I described what I think about the role of an analyst in agile team. The second role that I would like to mention is the role of the architect. This role is defined in […]

Leave a Comment

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

Scroll to Top