Modeling Toolset

Animate business process and compare as-is and to-be processes to identify enhancements.
Model refactoring

Move project data (i.e. model elements/diagrams) from current to referenced project through model refactoring. This ease the sharing of common project data, improves readability as well as to reduce complexity of project. A typical usage is to refactor pool and lane to referenced project, to make it possible to share across different current projects.
- Move pools and lanes to base project
Tutorial
- How to Perform Refactoring
Know-how
Visual Diff

Compare as-is business process diagram and to-be business process diagram. Identify new, deleted and updated tasks between diagrams. The latest release supports exporting differences to PDF for reporting purpose.
Reference other project model elements

It is not possible to put everything in a single visual paradigm project in enterprise scale project. Business Process Visual ARCHITECT allows visualizing different projects' model elements in a single diagram. The following movie shows how to configure referenced project and show the model elements in diagram.
- Reusing Model Element with Referenced Projects (Free)
Online training
Mirror other project model elements

Mirror model elements feature are similar to reference model elements feature that allows visualizing model elements from other projects. The referenced model element will not keep a local copy of the model element in the project and not allow adding child to the model elements. Mirror model elements feature keeps copies of the model elements in local project and allows adding child model elements to the mirrored model elements.
Design pattern

Reusing, refining, elaborating or transcribing portion of previous project's diagram can increase modeling efficiency dramatically. Business Process Visual ARCHITECT supports the use of Design Pattern, which enables you to define diagram or portion of the diagram as pattern, and apply the pattern in future. The defined patterns are highly configurable and customizable to fulfill any needs. All diagrams in Business Process Visual ARCHITECT supports design pattern. The defined patterns can be shared within the team through VP Teamwork Server, Subversion, Perforce or CVS.
Model element nicknaming
Nick name:

Business Process Visual ARCHITECT's market-unique Nicknamer feature lets you define multiple set of name and documentation in a single model. In this connection, it allows a diagram to be presented in different languages without keeping multiple copy of the diagrams or project files. You can maintain one business process diagram with different languages for different branches of your company around the world. Besides, you can put a human readable name for each entity in ERD to increase the readability. The following movie shows you how to maintain two languages of business process diagram and make a human readable ERD. You can see the nicknamer in action by changing the combo box at the right hand side.
- Translate business process diagram
Tutorial
Traceability and model transitor

Traceability between model elements helps to identify and locate the source of origin of specify model element in project. For example, "Order Process" in process map diagram is derived from a task called "Process Order" in a business process diagram. Business Process Visual ARCHITECT supports model transitor to manage and maintain the traceability between model elements.






Tell Us What You Think