A repository (inclusive full access) is needed to support the reuse of model elements, collaboration in the team (collaboration), as well as to structure the repository (and our project).Ein wichtiges Kriterium für mich ist die Nutzung und der (volle) Zugriff zu einem Repository. The tools I know support several licensing models: Single Seat, Concurrent License, Subscription Models.Īn important criterion from my point of view is the use and (full) access to a repository. But consider that for very cheap solutions, the expectation of possible manufacturer support needs to be adjusted to the price. Price: Of course, the price question is always decisive.
Social Networks, events as "Process Solution Day" discuss the question. IGOE), proprietary representations, support for a role concept, and more. Other criteria are more important: ease of use of the solution, output formats and reports, the ability to easily add additional attributes not included in the standard notation (e.g. The implementation and support of new standard notations are often a temporary question. The standard notation is supported or not. No manufacturer can claim to own a better BPMN. This allows the exchange between tools and platforms. In addition, the OMG standard notations include an exchange format.
The meaning of the presentation and the elements are standardized. The primary or only measure is not, which notation is supported and is most suitable for my task? This is a big advantage of the standard notations. Which one has the higher priority depends on your project task. The answer is undoubtedly partially subjective. Users often ask which tool is the most suitable for me? The question cannot be answered without further ado. Examples are Adonis, Intellior, Semtalk, ARIS (), or BIC. For sure, you find more interesting solutions in the Web used by us in Projects too. These applications are used by us in Projects and Workshops. The book featured examples of several tools: Qualiware, Visual Paradigm, MagicDraw), Signavio, DecisionsFirst.