Release Date: March 5, 2007
Concurrent Versions System (CVS) is a popular version control system that store artifacts centrally and keep track of changes and histories. All Visual Paradigm client products are integrated with CVS to facilitate collaborative modeling. Your team can use CVS repository to store project files, keep track of changes and perform modeling concurrently.
Subversion (SVN) is a popular version control system that store artifacts centrally and keep track of changes and histories. All Visual Paradigm client products are integrated with Subversion to facilitate collaborative modeling. Your team can use Subversion repository to store project files, keep track of changes and perform modeling concurrently.
UML is theoretically a modeling language independent to particular programming language(s). Yet, it is possible to transform between UML models to a software applications or systems. While the pre-defined data-type set works well in the UML world, there is enormous need to ensure the design can be applied to programming source code. Problems comes from the fact that programming languages, by nature, are unlikely to share the same set of data-types suggested by UML.
UML2 is an EMF-based (EMF: Eclipse Modeling Framework) implementation of the UML 2.x metamodel for the Eclipse platform. Visual Paradigm supports importing and exporting UML2 model through XMI, which is the default serialized form of EMF.
Textual Analysis is a useful technique for identifying candidate objects from a textual representation of users' problem. In previous versions, it is possible to extract candidate actors, classes, use cases, and work flows from problem statement. Starting from this version onwards, the Textual Analysis feature is improved such that more kinds of candidate objects can be extracted from the problem statement. They include BPMN objects such as Task and Sub-process.
Element sorting is always essential in modeling. Take the various diagram and model trees as example. One can easily locate an element from Model Tree if the listing of elements follows certain order such as by type or by name in alphabetical order. As representation of models, element sorting in report is as important as that in modeling.
Visual Paradigm supports different way of sorting the elements in generated report. The sorting will affect the sequence of elements appear in the PDF, HTML and Word report.
Visual Paradigm supports a broad range of diagrams that suit different kind of users, and thus different modeling needs. The types of diagrams that Visual Paradigm supports can be generally categorized into UML Diagrams, Requirements Capturing, Database/Data Modeling, Business Process Modeling and Others.
Visual Paradigm supports reverse engineering database into Entity Relationship Diagram (ERD). In the past versions, if you generate database from ERD, make changes to the database such as removing columns, and then reverse the database back into ERD, there may be columns that are removed from the database but keep existing in the ERD. This lead to inconsistency between data design and the database schema. In the new version, the reverse database feature is enhanced such that the ERD is conformed to the database by reversing database into ERD.
In Business Process Diagram, participants can be defined for a messages to represent the sender and receiver of that message. In the previous version, the information of participant was not appear in generated reports. But from now on, participants will be shown as a separate model under the Detail section in generated report.
Business use case is used for representing observable business goals in a business. Visual Paradigm supports business use case modeling. Business use case diagrams can be drawn to represent business processes, with the help of business actors and business use cases.
Visual Paradigm now supports FrontBase database! With the FrontBase support, you can draw an ERD in VP, and generate the database to FrontBase. Also, you can reverse engineer the FrontBase database into ERD for further editing. Besides this, you can generate the persistence object tier for communicating with FrontBase database.
Diagram Summary here refers to the table blocks shown in a generated report. A diagram summary table lists out the models that appear on a diagram, and provides linkage to them. While the summary table provides fast access to models, it may not be desired, especially for users who have certain predefined rules that guide the layout of reports. Now, it is possible to make the generated HTML, PDF and Word reports not to include the summary table.