Release date: January 21, 2013 (Latest Build: 20130507)View release notes
A truly functional information system has to be business oriented. Features must be designed and developed base on users’ needs, with system behaviors following the business rules strictly. Decision table provides a compact way to represent complicated business rules. Thanks to the easy to comprehend layout, decision table can be understood by developers and end-users easily. Decision table involves three sections - conditions, actions and rules. From developer’s point of view, decision table is pretty much like the tabular form of an if-then-else statement. Business users use decision table to document business rules, while system developers study a decision table to think about the right way to implement those rules.
The use of ArchiMate in software development allows software developers to view the system in macro point of view, rather than to work in silos. This enables the production software systems that align closely to the business.
As a software design tool that complies with the ArchiMate 2.0 specification, VP-UML supports enterprise architecture modeling with all the ArchiMate notations, plus all the improvements issued in version 2.0, which includes the two optional language extensions: the Motivation extension and the Implementation and Migration extension.
During requirement capturing and design stage, system analyst often needs to present screen designs to customer and for discussion within development team. Traditional screen designers usually tie up screen design with specific programming language that inherits a lot of constraints when designing and annotating screens. Visual Paradigm for UML provides a full featured screen designer for you to illustrate and annotate screen designs without limitation. The following movie shows how to use user interface designer to design form-based application with text field, menu, table and tree.
Visual Paradigm for UML provides a full featured web page designer for system analyst to illustrate and annotate screen designs. With the web page designer, you can design web forms, web pages and present the transition of pages. The following movie shows how to use web page designer to design a web form.
Overview dependencies between model elements by matrix diagram. The latest version supports exporting matrix diagram to Microsoft Excel for further analysis. The following movie demonstrates basic matrix diagram usage.
Generate and fill Responsibility Assignment Matrix base on any type of model elements.
Step 1 of 4: Open the project
Open the project file for creating chart.
Step 2 of 4: To create a chart
Click on Impact on toolbar, and select Chart Diagram from the drop down menu.
Step 3 of 4: Configuring row and column
Specify the type of element to appear in row and column. Click OK.
Step 4 of 4: Fill in chart content
Click on the cells in chart and select the appropriate relationship.
Convert your design to report by few mouse click. The generated report can preview and compare with the design side by side.
By usage, entity relationship diagrams (ERD) presents persistent structure of database and class diagrams presents object structure in memory. There is an alignment between ERD and class diagram - Database column in entity can map to attribute in class. Visual Paradigm for UML supports generating class diagram from ERD and synchronizing changes between them, and vice versa.
It is not possible to put everything in a single visual paradigm project in enterprise scale project. Visual Paradigm for UML 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.
Chat with the analysts, designers, software developers or whoever in your team directly inside VP-UML, right in a diagram. PostMania, a private social networking platform designed for software development teams, facilitates easy discussion of software designs. It enables team members to post and reply discussions to a diagram or a shape. Just make a post to ask for change, and moments later you receive a reply from your teammate, saying "Done" and with a smiley face. PostMania simply breaks communication barrier and improves the bonding of development team.
Add or edit your project terms and their definitions in Glossary Grid. Let the terms say what you mean. And when others use them in the same project, they mean what you say. Guard consistency, but flexible to manage variations of a term with Alias to accommodate lingoes used by different groups, such as "refund" for the customer service department and "debit" for the accounting folks. Bundle up terms by tagging them with a Label. In fact, tag multiple labels for a popular term if you need to. Then zero in on relevant terms only through filtering by label in what could well be a lengthy glossary.
Let your software development team work together smoothly and efficiently. Combining with the use of Visual Paradigm Teamwork Server (Teamwork Server), your entire team can design software collaboratively and concurrently. Teamwork Server is a central repository with version control capabilities that allows development team to checkout, commit and update design projects. Keep drawing and committing diagrams, your teammates will get them instantly. And thanks to the sophisticated merging and conflict resolution capabilities, everyone can work concurrently without being locked by anyone else. With Teamwork Server, you save a great deal of time in lining up your team because it has done everything essential yet daunting for you.
Having a model with multiple levels of abstraction is highly desirable, not only because it allows developers to focus fewer concepts at a time, but since it makes model refinement easier. In VP-UML, model can have unlimited levels of abstraction layers whereby different perspectives of system and different amounts of details are exposed to developers. For example, use case diagram represents high level system requirements, while the way to accomplish individual use case can be represented by sub sequence diagrams of use cases. Another example would be to add sub state machine diagrams to controller classes to show how objects change their state.
There are plenty of reasons you might want to link up different diagrams, shapes and model elements, for example, including the mockup of screens that are designed around a use case, relating a business model with a software design, etc. The reference feature enables you to make internal links between different kinds of project data. Those references do not just work inside VP-UML, but additionally in any document and Web contents generated from your design.
Write detail description to model elements with rich formatted text. The latest release highlights and links glossary terms from documentation to glossary grid. The following movie shows you how to write rich text documentation and reuse a predefined template.
Visual Paradigm plug-in provides an extendable platform for developers to add functions to Visual Paradigm for UML. Developer can reference to the plug-in development guide to build their own plug-in to read, create, update and delete diagrams and model elements. Developer can use Java to develop plug-in. The following screenshots outline the steps to create plug-in for Visual Paradigm for UML.
Plug-in support (Java)
Step 1 of 5: Develop the plugin
Setup the environment for developing plugin and start developing the plugin. You need to first include the openapi.jar to the build path, which can be found under the lib folder of VP Suite installation directory. You may read the User's Guide to learn about how to develop plugin.
Step 2 of 5: Prepare the plugin configuration file
Create a file, name it as plugin.xml and place at the root of plugin. You need to fill in this file to provide information such as classpath, toolbar/menubar configuration, etc.
Step 3 of 5: Deploy the plugin
Create a folder "plugins" under the VP Suite installation directory. Copy the developed plugin to that folder.
Step 4 of 5: Using the plugin
Start the tool. If the implementation and configuration are both correct, you should be able to run the plugin.
Step 5 of 5: Using the plugin (Cont.)
With plugin, you may iterate the project data to perform operations such as create, read, remove and update of project data.