Tell Us What You Think
Sending...
Thank you for your feedback
Team Collaboration
Edit the same diagram concurrently and keep all revisions in a central repository.
Concurrent modeling with Perforce server
Perforce is a popular commercial source code and files repository. The integration of Perforce allows all team members to view and edit the same project or even same diagram simultaneously. Business Process Visual ARCHITECT employ local workspace concept for collaborative modeling. The normal usage usage is to checkout project from Perforce server, then modify project and commit changes to Perforce server. Thanks to the concept of local workspace, you may bring your notebook to customer's office, and start working with the project without connecting to the Perforce server. After all, you will commit the changes to Perforce server when you back to the office.
View and compare old revision with Perforce server
Perforce keeps all histories of changes of diagrams and model elements. With Perforce you can review and compare change histories of specific diagram and model element visually with the "Revision History" function. You can also export and open full project of old revisions.
Detect and resolve conflicts with Perforce server
Business Process Visual ARCHITECT helps merge changes from different team members during commit or update. Let's say when two or more team members have modified the same model element, and performed commit or update one after the other, the merge engine will detect that there is a conflict occurred, and prompt to resolve the conflict. Conflicts can be resolved by overwrite (keep local change) or revert (keep server change).
Project baseline with branching and tagging with Perforce server
Business process improvement and software development is a continuous process. There are several milestone and release points throughout the process. In Business Process Visual ARCHITECT you may create a baseline for milestone or release, by creating tag of project - a frozen revision of project. You may compare changes of business process, static design, behavioral design and database design between releases with few mouse clicks. Sometimes, your team may need to examine risky idea on the model, or to carry out long term development tasks, and want to isolate the work from stable trunk, branch is what you need. There is a branch feature for creating an isolated revision of project. Your team can keep modifying the branch and merge the branch to trunk after the development is completed and tested.
Tell Us What You Think