VP-UML Users Guide
VP-UML Users Guide
Visual Paradigm for UML (VP-UML) is a powerful, cross-platform and yet the most easy-to-use visual UML modeling and CASE tool. VP-UML provides
software developers the cutting edge development platform to build quality applications faster, better and cheaper! It facilitates excellent interoperability
with other CASE tools and most of the leading IDEs which excels your entire Model-Code-Deploy development process in this one-stop-shopping
solution.
UML modeling
You can draw all kinds of UML 2.x diagrams in VP-UML, which include:
• Class diagram
• Use case diagram
• Sequence diagram
• Communication diagram
• State machine diagram
• Activity diagram
• Component diagram
• Deployment diagram
• Package diagram
• Object diagram
• Composite structure diagram
• Timing diagram
• Interaction overview diagram
Requirement modeling
Capture requirements with SysML Requirement Diagram, Use Case Modeling, Textual Analysis, CRC Cards, and create screen mock-up with User
Interface designer.
Database modeling
You can draw the following kinds of diagrams to aid in database modeling:
• Entity Relationship Diagram
• ORM Diagram (visualize the mapping between object model and data model)
You can model not only database table, but also stored procedure, triggers, sequence and database view in an ERD.
Besides drawing a diagram from scratch, you can reverse engineer a diagram from an existing database.
Apart from diagramming, you can also synchronize between class diagram and entity relationship diagram to maintain the consistency between them.
SQL generation ane execution feature is available for producing and executing SQL statement from model instantly.
Business process modeling
You can draw the following kinds of diagrams to aid in business process modeling:
• Business process diagram
• Data flow diagram
• Event-drive process chain diagram
• Process map diagram
• Organization Chart
You can also export Business process diagram to BPEL.
Object-Relational mapping
Object-Relational Mapping enables you to access relational database in an object relational approach when coding. VP-UML generates object-
relational mapping layer which incorporates features such as transaction support, pluggable cache layer, connection pool and customizable SQL
statement.
Team collaboration
For users that work as a team, team collaboration support lets you perform modeling collaboratively and concurrently with any one of the following tools
or technologies:
• VP Teamwork Server (Need to buy Visual Paradigm Teamwork Server additionally)
• CVS
• Subversion
• Perforce
Interoperability
Import Export
Telelogic Modeler
Rational Rose
Rational DNX
Visio drawing
Microsoft Excel
XML (native)
VP project
Code engineering
Java
C++
XML Schema
PHP
Python Source
Objective-C
XML (structure)
JDBC
Hibernate
C#
VB.NET
ODL
ActionScript
Delphi
Perl
Ada95
Ruby
IDE integration
Support full software development life-cycle, from analysis to design, and from design to implementation with your most favorite IDE. Below are the
supported IDEs:
• Eclipse
• NetBeans/Sun ONE
• IntelliJ IDEA
Documentation generation
Share your design with your customers in popular document formats, including:
• HTML (report generation)
• HTML (project publisher)
• PDF
• Word
UML Modeling
Requirement Diagram
Glossary Grid
Mind Mapping
UML Profile
Design Pattern
Visual Diff
Animacian
Simulacian
Impact Analysis
The filled circle indicates the support of certain feature in certain edition
Editions P. 4
A summary of features supported by VP-UML
Editions P. 5
Features
UML support
Improve modeling efficiency with this easy-to-use, feature-rich and reliable UML 2.1 modeling tool.
Class diagram
Sequence diagram
Communication diagram
Activity diagram
Component diagram
Deployment diagram
Package diagram
Object diagram
Timing diagram
Features P. 6
Requirements management
Capture requirements with SysML Requirement Diagram, Use Case Modeling, Textual Analysis, CRC and more!
Requirement diagram
Textual analysis
CRC Cards
Organization chart
Features P. 7
Animacian
A set of tools to help animating paths in a diagram, or to export animation to flash for further analysis.
Mind mapping
Database modeling
Enhance database documentation quality with sophisticated ERD and Object-Relational Mapping diagrams.
ORM diagrams
Features P. 8
Foreign key auto-naming
Features P. 9
Object-Relational mapping
Know how to manipulate objects in Java, .NET and PHP? Then you now know how to access relational databases. No more tedious database
programming! Just leave it to us.
Visual modeling
Improve the user-friendlyness of drawing diagrams, thus speed up the time need to spend on diagramming.
Features P. 10
Layer support to show/hide set of shape with single click
Bookmark support
Handi-Selection tool
Overview diagrams
Resource-centric interface
Model sharing
Mouse gestures
Model commenting
Diagram locking
Features P. 11
Tagged value display toggling for diagram elements
In-line editing
Spell checking
Features P. 12
Visual diff
A set of tools that help to compare diagrams, and identify their differences.
Features P. 13
Model transitor
Setup and maintain transition between models through the Model Transitor
Features P. 14
Team collaboration with VP teamwork server
Perform modeling collaboratively and concurrently with the VP Teamwork Server.
Features P. 15
Team collaboration with CVS repository
Perform modeling collaboratively and concurrently with CVS.
Features P. 16
Team collaboration with Subversion repository
Perform modeling collaboratively and concurrently with Subversion.
Features P. 17
Team collaboration with Perforce
Perform modeling collaboratively and concurrently with the Perforce.
Documentation generation
Share your design with your customers in popular document formats (PDF, HTML and MS Word).
Project publisher
Features P. 18
Printing
Print out diagrams using the Print features.
Fit-to-pages option
Fit-to-ratio option
The feature is available but the single watermark will be shown when the project has one diagram per diagram type. And the pattern watermark will
be shown when the project has more than one diagram per diagram type.
IDE integrations
Support full software development life-cycle, from analysis to design, and from design to implementation with your most favorite IDE.
Features P. 19
Reverse engineering
Reverse engineer UML models from source code.
Features P. 20
Code generation
Generate various kind of source code from class models.
Features P. 21
Java round-trip engineering
Update between UML class models and Java source code with the round-trip engineering functionalities.
Shape editor
Create domain specific shapes with Shape Editor to use in diagrams.
Layout facilities
Tidy up diagram content by performing layout with several mouse actions.
Interoperability
Exchange UML diagrams and models with other tools with industrial standard representation.
Command-line operations
Features P. 22
Import ERwin data modeler project files [2]
Import and export Microsoft Excel file for use case diagram
Import and export Microsoft Excel file for state machine diagram
Import and export Microsoft Excel file for composite structure diagram
Import and export Microsoft Excel file for interaction overview diagram
Import and export Microsoft Excel file for crc card diagram
Import and export Microsoft Excel file for entity relationship diagram
Import and export Microsoft Excel file for business process diagram
Import and export Microsoft Excel file for data flow diagram
Features P. 23
Import and export Microsoft Excel file for epc diagram
Import and export Microsoft Excel file for process map diagram
Import and export Microsoft Excel file for mind mapping diagram
Flexible zooming
Palette-style toolbar
Collapsible toolbar
Numerous looks-and-feels
Multilingual support
Searchable options
Features P. 24
Automatic updates
Keep VP-UML up-to-date with the automatic updates features.
Open architecture
Extend VP-UML's functionalities using plug-in
Features P. 25
Licensing
VP-UML need to run with a valid license key. A license key of a higher edition can be used on a lower edition. For example, you can run Standard
Edition of VP-UML with Professional Edition of VP-UML key.
VP-UML also provides a 30-days evaluation key for trial. After the evaluation key expires, you can purchase the full license from our website or
resellers, or un-install the program.
The license key for Community Edition will not expire. However, Community Edition cannot be used for commercial purposes.
NOTE: To start License Key Manager in VP-UML, select Tools > Key Manager... from the main menu.
To import a single-seat key, select License Keys > Import... from the menu. In the Import License Key dialog box, specify the filepath of the key and
press OK to confirm.
Licensing P. 26
If the imported key is valid, information of key will appear in the License Key Manager.
NOTE: To start License Key Manager in VP-UML, select Tools > Key Manager... from the main menu.
Licensing P. 27
In the configuration page, specify the host IP and adjust the port (if necessary). You may need to specify the access code if it has been defined in
floating license server. You should contact your administrator about this matter.
In order to verify the connection, press Test Connection. Alternatively, you may click on the View Keys button to see how many keys are available in
server.
Once the configuration is done correctly, license key will be acquired from license server. By closing the License Key Manager, VP-UML will start.
Licensing P. 28
To export floating license key, start the License Key Manager by selecting Tools > Key Manager... in the main menu of VP-UML, and select License
Keys > Floating License > Export Floating License... in the menu of License Key Manager.
In the Import Floating License Key dialog box, select the key you need to import and click OK to confirm.
Licensing P. 29
2. Start the License Key Manager by selecting Tools > Key Manager... from the main menu.
NOTE: If your evaluation has expired, you can skip this step as the License Key Manager was shown when starting VP-UML (step 1) due to no
valid license key was found.
3. Remove all license keys by selecting License Keys > Remove All Keys from the menu of License Key Manager.
This cause all the keys to be removed from the License Key Manager. Therefore, you should not see any entry in the manager.
4. You can import the purchased license key now. For single-seat key user, select License Keys > Import..., then specify the filepath of the
purchased license key. For floating license user, configure the license server connection by selecting License Keys > Floating License >
Configure... from the menu. For details, refer to the previous section.
Floating license
The floating license supports sharing of the pool of licenses among your team. Instead of purchasing a single-seat license for each team member,
optimize your budget by purchasing floating licenses for the maximum number of simultaneous software users or access points. This approach allows
greater flexibility in using our software. Users can then export the license files to a laptop to use the software offsite (to deliver a presentation, for
example), and then import the license back to the server at a later time.
In order to work with the floating license, installation of a floating license server that stores the license key file(s) and also automatically manages
access requests from clients is required. The client must enable the connection to the license server when requesting access to the software.
For more information about floating licenses, please visit
http://www.visual-paradigm.com/shop/floatinglicense.jsp .
Academic license
Academic licenses are available for higher education, with the aim of providing free site licenses for the teaching of software engineering. Educational
institutions that join the Academic Partners Program are entitled to free licenses for the Standard Edition of Visual Paradigm's software, which can
then be used solely for educational purposes. The academic license is not limited to use on campus, but can also be used at home by students and
teachers.
For more information about academic licenses, please visit
http://www.visual-paradigm.com/partner/academic/ .
Licensing P. 30
Software maintenance
The Visual Paradigm Software Maintenance package includes both version upgrades and technical support services for our customers. The following
benefits are all included in the Visual Paradigm Software Maintenance package.
Version upgrades
From time to time, Visual Paradigm releases new versions of its software. Normally there are two or three versions released every year, with each
new version having around five to ten distinct new features as well as a number of improvements. The easiest way to get the latest version from Visual
Paradigm is to purchase the software maintenance package. Both minor upgrade (e.g., 6.1 to 6.1 SP1) and major upgrade (e.g., 7.0 to 7.1 or 8.0) of
Visual Paradigm products are included in the software maintenance package, thus entitling you to get all of the version upgrades issued within the
software maintenance period.
Technical support
You and your team members can submit technical support tickets to our Technical Support Team at http://www.visual-paradigm.com/support/
technicalsupport.jsp
Our Technical Support Team will respond to your message within one working day. Normally, you will receive our response by email within a few
hours.
Visual Paradigm is committed to delivering extraordinary technical support to our customers. Our Technical Support Team employs the following
technologies to back up our products.
Email with text and screen shot attachments
In most cases we can provide assistance by guiding you with the aid of screen shots.
LIVE help
Our Technical Support Team uses a real-time, web-based chat program to discuss the problem with you directly.
Flash demo
Sometimes, a short movie is more descriptive than a thousand words. If the answer to your question is complex, we can prepare a short Flash
demonstration to guide you in resolving your difficulty.
Secure online sessions
We can schedule an online meeting with you to take an interactive look at your issue. Online meetings are held using a secure Internet connection.
During the meeting, our team can remotely access and operate your PC while speaking with you by telephone or while chatting with you using the built-
in chat program.
Telephone
You can leave a callback request at the following URL. Our Technical Support Team will return your call as soon as possible. To make a call, visit:
http://www.visual-paradigm.com/support/callme.jsp
Price
Software maintenance is purchased in year-long terms (e.g., June 20, 2007 to June 19, 2008).
If you decide to purchase the software maintenance package with your product, or if you decide to extend a current maintenance contract, the yearly
cost is 20% of the product list price. To take advantage of this 20% offer, you must extend your maintenance contract at least one week prior to its
expiration date.
If you decide to purchase a software maintenance package separately, the yearly cost is 30% of the product list price.
You can purchase software maintenance to cover up to three years from the date of purchase.
Detailed software maintenance package pricing is listed below.
Single seat license
Prices are provided in US dollar
Floating license
Software Maintenance P. 31
Prices are provided in US dollar
Software Maintenance P. 32
System requirements
Hardware requirements
• Intel Pentium III Compatible Processor at 1.0 GHz or higher.
• Minimum 512MB RAM, but 1.0 GB is recommended.
• Minimum 800MB disk space.
• Microsoft Windows (98/2000/XP/2003/Vista/7), Linux, Mac OS X, Solaris or all other Java-enabled platforms.
System Requirements P. 33
Installing Visual Paradigm for UML on Windows 2000/NT/2003/XP/Vista
Having downloaded the installer of Visual Paradigm Suite (VP Suite), you can execute it, run through the installation to install the suite as well as VP-
UML. If you are using the no-install zip version, you just need to unzip it, launch the suite and install VP-UML. In this chapter, we will go through the
installation of VP-UML both with installer (.exe) and no-install (.zip).
8. VP-UML features vary by product edition. For more details on the features supported by different editions, click the hyperlink Edition
Comparison which brings you to the web page of VP-UML feature comparison for different editions.
Pre-configure floating license server connection and enable product selector for floating license user
10. Select Download Online Help if you want to be able to access the Help contents from within the tool. Select Download PDF/HTML Version if
you wish to read the documentation in this two types of formats. Press Next > to proceed to the license import page.
Download documentation
NOTE: For evaluation, the key should be sent to your email box (unless you have chosen not to receive it before download). If you have not
received the email with key yet, and if you have selected to receive the key as attachment, the email might be treated as spam by
mistake. Click on Request Evaluation Key to ask for another one. This time, try not to select sending the key as attachment.
Launching VP Suite
3. Select Visual Paradigm for UML. Click Next > to proceed to the product configuration page.
5. Select Download Online Help if you want to be able to access the Help contents from within the tool. Select Download PDF/HTML Version if
you wish to read the documentation in this two types of formats. Press Next > to proceed to the license import page.
Download documentation
NOTE: For evaluation, the key should be sent to your email box (unless you have chosen not to receive it before download). If you have not
received the email with key yet, and if you have selected to receive the key as attachment, the email might be treated as spam by
mistake. Click on Request Evaluation Key to ask for another one. This time, try not to select sending the key as attachment.
7. Upon finishing, you can select whether to start VP-UML or not. Keep Visual Paradigm for UML selected and click Finish will run VP-UML right
away.
4. Specify the directory for installing VP Suite. Click Next > to proceed to the next page.
6. Select Visual Paradigm for UML. Click Next > to proceed to the product configuration page.
8. For users who are going to run VP-UML with floating license, the Pre-Configuration File section enables you to configure the connection(s) to
floating license server by providing a configuration file. The pre configuration is optional. If you do not define the connection here, you will need
to do so when starting VP-UML the first time. Below is the pre-configuration file file content:
?xml version="1.0" encoding="UTF-8"?>
<LicenseServer>
<Server accessCode="" host="" port=""/>
<Server accessCode="" host="" port=""/>
<Server accessCode="" host="" port=""/>
<Server accessCode="" host="" port=""/>
</LicenseServer>
Selecting Enable Product Selector for Product Selection will result in creating a shortcut under the Start Menu for starting the Product Selector,
a utility that lets you realize the installed products with available keys in the floating license server.
9. Select Download Online Help if you want to be able to access the Help contents from within the tool. Select Download PDF/HTML Version if
you wish to read the documentation in this two types of formats. Press Next > to proceed to the license import page.
Download documentation
NOTE: For evaluation, the key should be sent to your email box (unless you have chosen not to receive it before download). If you have not
received the email with key yet, and if you have selected to receive the key as attachment, the email might be treated as spam by
mistake. Click on Request Evaluation Key to ask for another one. This time, try not to select sending the key as attachment.
Launching VP Suite
4. VP-UML features vary by product edition. For more details on the features supported by different editions, click the hyperlink Edition
Comparison which brings you to the web page of VP-UML feature comparison for different editions.
5. Select Download Online Help if you want to be able to access the Help contents from within the tool. Select Download PDF/HTML Version if
you wish to read the documentation in this two types of formats. Press Next > to proceed to the license import page.
Download documentation
NOTE: For evaluation, the key should be sent to your email box (unless you have chosen not to receive it before download). If you have not
received the email with key yet, and if you have selected to receive the key as attachment, the email might be treated as spam by
mistake. Click on Request Evaluation Key to ask for another one. This time, try not to select sending the key as attachment.
7. Upon finishing, you can select whether to start VP-UML or not. Keep Visual Paradigm for UML selected and click Finish will run VP-UML right
away.
4. Specify the directory for installing VP Suite. Click Next > to proceed to the next page.
6. Select Visual Paradigm for UML. Click Next > to proceed to the product configuration page.
8. For users who are going to run VP-UML with floating license, the Pre-Configuration File section enables you to configure the connection(s) to
floating license server by providing a configuration file. The pre configuration is optional. If you do not define the connection here, you will need
to do so when starting VP-UML the first time. Below is the pre-configuration file file content:
?xml version="1.0" encoding="UTF-8"?>
<LicenseServer>
<Server accessCode="" host="" port=""/>
<Server accessCode="" host="" port=""/>
<Server accessCode="" host="" port=""/>
<Server accessCode="" host="" port=""/>
</LicenseServer>
Selecting Enable Product Selector for Product Selection will result in creating a shortcut under the Start Menu for starting the Product Selector,
a utility that lets you realize the installed products with available keys in the floating license server.
9. Select Download Online Help if you want to be able to access the Help contents from within the tool. Select Download PDF/HTML Version if
you wish to read the documentation in this two types of formats. Press Next > to proceed to the license import page.
Download documentation
NOTE: For evaluation, the key should be sent to your email box (unless you have chosen not to receive it before download). If you have not
received the email with key yet, and if you have selected to receive the key as attachment, the email might be treated as spam by
mistake. Click on Request Evaluation Key to ask for another one. This time, try not to select sending the key as attachment
Launching VP Suite
4. VP-UML features vary by product edition. For more details on the features supported by different editions, click the hyperlink Edition
Comparison which brings you to the web page of VP-UML feature comparison for different editions.
5. Select Download Online Help if you want to be able to access the Help contents from within the tool. Select Download PDF/HTML Version if
you wish to read the documentation in this two types of formats. Press Next > to proceed to the license import page.
Download documentation
NOTE: For evaluation, the key should be sent to your email box (unless you have chosen not to receive it before download). If you have not
received the email with key yet, and if you have selected to receive the key as attachment, the email might be treated as spam by
mistake. Click on Request Evaluation Key to ask for another one. This time, try not to select sending the key as attachment.
Installation FAQ
Question: What is the difference between Installer and "No Install Version"?
Answer: Installer version creates shortcut and registers the menus that make the system more easy to use. We suggest user to use installer version for
a long term usage. The No Install version is good for evaluation and testing the release candidate.
Question: I cannot complete the installation due to a file is missing when copying files. What can I do?
Answer: This can be caused by a corrupted installer file. Please download the installer file again with a different mirror site and run it again to solve the
problem.
Question: I cannot start the application after installing the software. What can I do?
Answer: There are several possible causes of the problem. If you are sure that your installation was performed correctly, contact Visual Paradigm's
support team ( [email protected] ) for assistance. It is recommended to include the vp.log file, which can be found at the bin folder
of VP Suite installation directory, for our team to diagnose in further.
Question: Can I change the Edition without re-install the software?
Answer: Yes, you can. Product edition can be changed by running VP Suite Product Edition Manager under the bin folder of VP Suite installation
directory. Change of edition takes effect after the restart of affected products. For more details, please read the section Switching Edition a few pages
later.
Question: The installer file is detected to contain a virus. What can I do?
Answer: Our installer files are all packed by ourselves in a secure environment, and are scanned for virus before releasing to public. If a virus is
detected, please update to the latest virus profile first. After that, we recommend you perform a full system scan, download the installer file from our
official site, and run the installation again. If the problem remain, please contact us ( [email protected] ) or the virus scanner vendor
for assistance.
Switching edition P. 63
Uninstalling Visual Paradigm for UML
Uninstalling VP-UML will cause VP-UML to be removed from VP-Suite.
1. Close VP-UML if it is running.
2. Execute uninstall_vpuml under the uninstaller folder of VP Suite installation folder.
Uninstalling VP-UML
Alternatively, you can start VP-UML by executing the launcher run_vpuml in the launcher folder of VP Suite installation directory. Users in all operating
system can start VP-UML in this way.
Starting Visual Paradigm for UML in Linux using the icon in desktop
Starting Visual Paradigm for UML (for floating license client whose host is IP-4-enabled)
If you are a floating license client, and if your host is IP-4 enabled, you need to start VP-UML with a startup script in order to connect to the server.
Here are the steps:
1. Copy VP-UML.bat under the scripts folder of VP Suite installation directory to become Startup.bat
2. Edit Startup.bat
3. Add -Djava.net.preferIPv4Stack=true to the script
4. Save
5. From now on, execute Startup.bat to run VP-UML
Select workspace
A workspace is a directory used to store all settings, user interface perspectives and other preferences defined for the working environment (settings
can be configured via Tools > Options... in VP-UML). A workspace also stores all the teamwork login information and local copies of teamwork
projects. In the case of switching computers, you simply need to copy the whole workspace directory to the new computer and specify the new
workspace when starting VP-UML. All your teamwork information and settings will then be transferred to the new computer.
The Workspace Launcher appear when running VP-UML.
Workspace Launcher
1 Menu bar The menu bar at the top of the window allows you to select and perform various operations in Visual Paradigm for UML.
2 Toolbar Toolbar, which is below the menu bar, is the extension of menu. All buttons are presented as groups of icons that handily
placed for users.
3 Diagram A place where diagrams are listed, and where you can create and access diagrams base on their types.
navigator
4 Property pane The properties of chosen model/ shapes will be shown on properties pane upon selection.
Interface Overview P. 68
Main menu
The main menu, which is on the top of the window, allows you to select and perform various operations in Visual Paradigm for UML.
File menu
Edit menu
Menu bar P. 69
The Edit menu
View menu
Menu bar P. 70
The View menu
Tools menu
Menu bar P. 71
The Tools menu
Menu bar P. 72
• Launch License Key Manager
• Configure application options through the Options dialog box
Window menu
Help menu
Menu bar P. 73
Toolbar
Showing/Hiding toolbar(s)
A toolbar can be shown or hidden. To show a toolbar, right-click on any toolbar, and select the toolbar to show. Similarly, you can uncheck a toolbar to
hide it.
Repositioning toolbars
A toolbar can be repositioned by pressing on the handle of toolbar, which appears on the left hand side of a toolbar, and dragging to your target
position.
Locking toolbar
To freeze toolbars' position and make the toolbars not movable, right click on any toolbar and uncheck Rearrangable from the pop-up menu.
Standard toolbar
Print... Select and print diagram(s) after configure the advanced printing set up.
Print Active Diagram... Select and print diagram(s) after configure the advanced printing set up.
Quick Print... Print the active diagram after configure the advanced printing set up.
Copy within VP-UML Copy selected diagram elements ready to be used within VP-UML.
Copy to Clipboard as Image (JPG) Copy selected diagram elements as JPG image.
Copy to Clipboard as Image (EMF) Copy selected diagram elements as EMF image.
Toolbar P. 74
Copy to Clipboard as XML Copy selected diagram elements as XML data.
Paste View Paste copied diagram elements as view of original model element.
Paste Model Element Paste copied diagram elements as a new model element.
UML Modeling Select and create a diagram type under UML Modeling, including: Use Case Diagram, Use
Case Grid, Actor Grid, Class Diagram, Composite Structure Diagram, Object Diagram,
Sequence Diagram, Communication Diagram, Activity Diagram, State Machine Diagram,
Timing Diagram, Interaction Overview Diagram, Component Diagram, Deployment Diagram
and Package Diagram.
Business Process Modeling Select and create a diagram type under Business Process Modeling, including: Business
Process Diagram, Conversation Diagram, Data Flow Diagram, Event-driven Process Chain
Diagram, Process Map Diagram, Organization Diagram and ArchiMate Diagram.
Database Modeling Select and create a diagram type under Database Modeling, including: Entity Relationship
Diagram and ORM Diagram.
Requirement Modeling Select and create a diagram type under Requirement Modeling, including: Textual Analysis,
Requirement Diagram, Basic Diagram, Open Requirements Grid, Open Glossary Grid and CRC
Card Diagram.
Diagrams Select and create other diagrams, including: EJB Diagram, Overview Diagram, User Interface
and Mind Mapping Diagram.
Format Click it to open Formats dialog box. You can format font name, font style, font size, font color,
line style, shape's foreground and background color and style, etc.
Copier Copy the selected diagram element's format and apply on another shape.
Modeling Click it to perform the following: Visual Diff, Animacian, Simulacian, Nicknames, Apply Design
Pattern and Transit to New Diagram.
Visual Diff: Launch Visual Diff for comparing diagrams.
Animacian: Launch Animacian for animating the active diagram.
Simulacian: Launch Simulacian for simulating the execution of business process.
Nicknames: Manage and select the nickname to be applied on the working project.
Apply Design Pattern: Apply the defined design pattern to the target diagram.
Transit to New Diagram: Transit the current diagram to a new diagram.
Generate HTML Report Open the Generate HTML dialog box to generate HTML report.
Generate PDF Report Open the Generate PDF dialog box to generate PDF report.
Generate Word Report Open the Generate Word dialog box to generate Word report.
Report Writer Open Report Writer where you can create and edit your report(s).
Toolbar P. 75
Branch Create a branch.
Instant Reverse Reverse Engineering Class Diagram from many kinds of source code, including: Instant
Reverse, Java, C++ Source, .Net dll or exe files, CORBA IDL Source, Ada 9x Source, XML,
XML Schema, JDBC, Hibernate, PHP 5.0 Source, Python Source, Objective-C and Java to
Sequence Diagram.
Instant Generator Generate source code from the opening project, including: Instant Generator, Java, C#,
VB.NET, PHP, ODL, ActionScript, IDL, C++, Delphi, Perl, XML Schema, Python, Objective-C,
Objective-C 2.0, Ada95 and Ruby.
Reverse DDL... Reverse data definition language file and form ERD.
Generate Code... Select Code > Java Round-trip > Generate Code....
Generate Java from class diagram for the whole project.
Reverse Code... Select Code > Java Round-trip > Reverse Code....
Reverse Java back into the opening project.
Generate Code... Select Code > C++ Round-trip > Generate Code....
Generate C++ from class diagram for the whole project.
Reverse Code... Select Code > C++ Round-trip > Reverse Code....
Reverse C++ back into the opening project.
Generate Code... Select Code > State Machine Code > Generate Code...
Generate state machine code from class diagram and state machine diagram.
Reverse Code... Select Code > State Machine Code > Reverse Code....
Reverse state machine code back into the opening project.
Interoperability Import: VP-UML Project...: Import a VP-UML project into the opening project.
Rose Project...: Import diagrams and model elements from a Rose model.
XMI...: Import diagrams and model elements from XMI.
XML...: Import diagrams and model elements from XML.
ERwin Project (XML)...: Import diagrams and model elements from ERwin Project.
Telelogic Rhapsody Project...: Import diagram and model elements from Telelogic Rhapsody
Project.
Telelogic System Architect...: Import diagram and model elements from Telelogic System
Architect.
Rational Model...: Import diagram and model elements from Rational Model.
Rational DNX...: Import diagram and model elements from Rational DNX.
MS Word to Use Case Model...: Import Use Case Report (MS Word) back into the opening
project.
PowerDesigner DataArchitect...: Import diagram and model elements from Power Designer
Data Model.
Visual UML...: Import diagram and model elements from Visual UML XML file.
Excel...: Import Excel file back into the working project.
Visio...: Import Visio diagrams into VP-UML.
NetBeans UML Project...: Import NetBeans UML diagrams into VP-UML.
Linked Project...: Import dependent projects into the opening project.
Export: VP-UML Project: Export the open project into a VP-UML project file.
XMI: Export XMI from the opening project.
XML: Export XML from the opening project.
Active Diagram as Image: Export active diagram as image file.
Diagrams as Image: Export any diagram(s) as image file(s).
Selection as Image: Export selection on active diagram as image file.
Use Case Model to MS Word: Export Use Case Report (MS Word) from Use Case diagrams
and use case models.
Active Diagram to Excel: Export active diagram into Excel report.
Excel: Export any diagram(s) into Excel report(s).
Toolbar P. 76
Database Configuration... Open the Database Configuration dialog box to configure database connections.
Reverse Enterprise Object Framework... Reverse engineering from Enterprise Object Framework.
Synchronize to Class Diagram Synchronize from Entity Relationship Diagram to Class Diagram.
Synchronize to Entity Relationship Diagram Synchronize from Class Diagram to Entity Relationship Diagram.
Ignore Entities when Synchronizing... Open Ignore Entities when Synchronizing dialog box to select entities to ignore during
synchronizing.
Ignore Classes when Synchronizing... Open Ignore Class when Synchronizing dialog box to select classes to ignore during
synchronizing.
Generate Database... Open the Database Code Generation dialog box to generate database.
Generate Code... Open the Database Code Generation dialog box to generate code.
Toolbar P. 77
Dockable user interface
VP-UML adapts a Dockable User Interface which allows you to drag UI components around to customize your favorite working environment. You can
save the environment as a perspective which you can reopen later. It allows you to use different perspectives for different purposes.
You will notice a gray outline appears while you are dragging a frame/tab. This outline tells you where the dockable frame/tab will be docked to.
You can also drag a frame/tab and dock it into another tabbed pane. You will see the outline changed to a tab shape if you drag over a tab pane.
The toolbar
Name Icon Description
New diagram Create a new diagram through the New Diagram dialog box.
Show Diagram View Overview the diagram elements in the selected diagram.
Sort Diagram Element By Sort diagram elements by their name in alphabetical order.
Name
Sort Diagram Element By Sort diagram elements by their type, disregard their name.
Type
Pop-up menu
Pop-up menu of diagram navigator
Diagram navigator P. 81
The pop-up menu of diagram navigator
Filter Model Element... Open the Model Element Filter dialog box to filter the diagram elements to appear in the diagram navigator.
Show Carriage Return Display line breaks of multi-lined diagram name as carriage return character.
Character
Show Diagram View Make the Diagram Navigator to expand all diagram types' nodes to show the diagrams nodes, but do not display
any diagram element nodes.
No View Model Elements... It lists the model element(s) that either has not been visualized (no view) or has no master view.
Diagram navigator P. 82
Rename... Rename the project.
Configure Programming Change to another programming language or configure the type mapping for a language.
Language...
Show Diagram Make the Diagram Navigator to expand all diagram types' nodes to show the diagrams nodes, but do not display any diagram
View element nodes.
Diagram navigator P. 83
Menu Title Description
Sort [diagram type] by Sort the diagram nodes of the selected type node in specific way.
name
Open [diagram name] Specification... Open the specification of the selected diagram.
Lock Set a password to lock the diagram. On the other hand, you can type the password to unlock the diagram.
Edit Nickname... A pop-up a dialog box for defining the nickname of model elements will appear in the diagram. This option is
available only after you have configured a nickname.
Diagram navigator P. 84
Create Matrix Diagram... Create a Matrix Diagram from [diagram name].
Analysis An analysis diagram will be formed to analyze the selected diagram with others and the result will be seen.
Relationship like diagram transition can also be found.
Creating a diagram
Approach 1 – Direct creation
If you want to create a diagram in a quick way and don't need to supply the documentation of diagram (for time-saving), use this approach. To create a
diagram:
1. Right click on the diagram type that you want to create.
2. Select New diagram type from the pop-up menu. Here, diagram type means the type of diagram you want to create.
NOTE: You can immediately enter the diagram name at the top left corner of diagram
Diagram navigator P. 85
In the New Diagram dialog box, you can enter the name and documentation of diagram, and click OK button to proceed.
Opening a diagram
Double click in the diagram you want to view in the diagram tab.
To sort by type, click Sort Diagram Element by Type button. As a result, the elements will be listed by type.
NOTE: The sort function applies to the entire diagram tree instead of the selected node.
Reordering diagrams
Select the diagram(s) you want to reorder. If there are multiple diagrams you want to select, just click one while pressing Ctrl button and make the
other selection.
Click Move Selected Diagram Up button to move the selection upwards, or Move Selected Diagram Down button to move the selection downwards.
Diagram navigator P. 86
2. Select the types of model element(s) you want to be displayed by checking to the type. Otherwise, uncheck the one you don't want to be
displayed.
NOTE: You can check Display model element types in-use to list only types of model elements used in project. The text box Filter enables you
to filter model element type base on the type name (e.g. enter class to list only class)
Diagram navigator P. 87
2. Uncheck Show Group Category if there is a tick in the box, and then all diagram types will be ungrouped.
Ungrouped diagrams
Perform teamwork
NOTE: This option applies to all diagram nodes, but not just the selected one.
Diagram navigator P. 88
Model Explorer
It would be much more efficient to make use of Model Explorer for your middle to large scale project which has considerable numbers of diagrams and
model elements, rather than using Diagram Navigator.
The toolbar
Name Icon Description
Move Selected Model Move the selected model elements down or up.
Element This option only works within the same model element type when there are multiple model elements.
Popup menu
Model explorer P. 89
Popup menu of model explorer
The Model Explorer lists all the model elements in the project.
Model Element... Create a new Model Element or select a default model in Model Explorer.
Filter Model Element... Open the Model Element Filter dialog box to filter the diagram elements to appear in the Diagram Navigator.
Show Relationships Show also Relationship model elements in Model Explorer (default hidden).
Show Sub Diagrams Show Sub Diagrams in Model Explorer so that user can browse and open Sub Diagrams in Model Explorer.
Show Data Types Show Data Types in Model Explorer (default hidden).
Show Carriage Return Display line breaks of multi-lined diagram name as carriage return character.
Character
Model explorer P. 90
The popup menu of project node in Model Explorer
No View Model Elements... It lists the model element(s) that either has not been visualized (no view) or has no master view.
Model Element Create a new Model Element in Model Explorer without the need of creating through diagramming.
Configure Programming Change to another programming language or configure the type mapping for a language.
Language...
Show Relationships Show also Relationship model elements in Model Explorer (default hidden).
Show Sub Diagrams Show Sub Diagrams in Model Explorer so that user can browse and open Sub Diagrams in Model Explorer.
Show Data Types Show Data Types in Model Explorer (default hidden).
Creating a model
A model is a package like UML element that can store model elements and diagrams. Users are recommended to structure project by using model in
order to maintain a clear structure for accessing project data and improve the application performance.
Model explorer P. 91
Right click on the root node in Model Explorer and select Model from the popup menu. You can either create a custom model by selecting New
Model..., or create a pre-defined model by selecting it in the list.
Model explorer P. 92
To sort by name, click Sort by Name button. The elements will be listed by name, in alphabetical order.
To sort by type, click Sort by Type button. As a result, the elements will be listed by type. To arrange model elements without sorting, click No sorting.
NOTE: This option only works within the same model element type when there are multiple model elements.
Model explorer P. 93
NOTE: Instead of displaying all types of model elements, checking Display model element types in-use to display the types of model elements
used in the project.
Perform teamwork
Model explorer P. 94
Class Repository
Class repository is a pane where classes and container that contain classes, such as packages or subsystems, are listed. Further to accessing
classes, you can also form class diagram by dragging classes from class repository to class diagram.
The toolbar
Name Icon Description
Reverse Code... To reverse a code as class model for the whole project.
Instant Reverse... To reverse different types of source into UML class models.
Pop-up menu
Pop-up menu of class repository
Model Element... Create a new Model Element in Class Repository without the need of creating through diagramming.
Show Carriage Return Display line breaks of multi-lined diagram name as carriage return character.
Character
Class repository P. 95
Teamwork Perform teamwork activities.
No View Model Elements... It lists the model element(s) that either has not been visualized (no view) or has no master view.
Model Element Create a new Model Element in Class Repository without the need of creating through diagramming.
Configure Programming Change to another programming language or configure the type mapping for a language.
Language...
Creating a model
A model is a package like UML element that can store model elements and diagrams. Users are recommended to structure project by using model in
order to maintain a clear structure for accessing project data and improve the application performance.
Class repository P. 96
Right click on the project root node in Class Repository and select Model > New Model... from the pop-up menu.
Class repository P. 97
1. Right click on the Class Repository's background.
2. Select Teamwork> Open Teamwork Client... from the pop-up menu.
Perform teamwork
Class repository P. 98
Logical view
The logical view provides a hierarchical view of a project's structure. With the logical view, users can create and customize the diagrams in their project
with meaningful categorization by adding domain specific view(s).
In addition, users can customize a default logical view for their preference, rather than re-creating a new logical view for every new project. The logical
view can be exported to xml files which can be used in other projects or distributed among the development team. Different views, thereby, can be
merged automatically through the teamwork server.
The toolbar
Name Icon Description
Set Logical View Structure as Default To set default structure for logical view in all projects.
Pop-up menu
Pop-up menu of logical view
Show Carriage Return Display line breaks of multi-lined diagram name as carriage return character.
Character
Logical view P. 99
Collapse All Collapse all tree nodes.
Set Logical View Structure as Default Set the current view structure as default so that another project that will be created under the same
workspace will share the same structure.
Add Existing Diagram... Add an existing diagram under the selected view.
You can enter the name for the new view node in the Input dialog box and then click OK button to confirm editing and close the dialog box.
A new view node is, therefore, created under the chosen node.
In Select Diagrams Dialog, check the diagrams you would like to insert in the view node.
In the pop-up Message dialog box, click OK button. The logical view structure in the new project will then follow the default style you have just
customized.
NOTE: The sort function applies to the entire logical view instead of the selected node.
Performce teamwork
The toolbar
Name Icon Description
Classpath Configuration Only available in class view, classpath configuration enables you to add or remove directories where
Java class files are stored. Classes in class paths will be listed in the pane.
Refresh By updating the class paths or database configuration, you can refresh the pane to show the updated
class or entity listing.
Database Configuration Only available in entity view, database configuration enables you to set the connection to database, so
that ORM pane can connect to that database to read the schema to form the entity list.
Database view
Database view lists tables from a chosen database. The tables are listed in a tree form. You can browse for its columns, and drag entities from tree to
diagram, to form an entity relationship diagram.
By confirming the configuration, tables, if any, will be listed in the ORM pane. You may form an entity relationship diagrams by dragging entities from
the pane and releasing in diagram.
Class view
Class view lists classes from chosen classpaths. The main function is to let you convert source code of domain classes into class models that can be
used to synchronize an ERD, to generate database in further. In other words, with the class view you can convert domain class (code) into database
tables.
Adding classpaths
By confirming the classpath selection, classes, if any, will be listed in the ORM pane. You may form a class diagram by dragging classes from the
pane and releasing in diagram. You can see the classes created will be extending the ORM Persistable stereotype. This means that they can be
synchronized to an entity relationship diagram.
The toolbar
Name Icon Description
Select Customer -
Pool in dropdown menu
To sort by category, click Categorized View button. As a result, all properties will be listed by category.
2. As a result, the part of diagram will be subsequently shown on the diagram pane.
On the contrary, the larger you drag the purple rectangle, the more the part of diagram will be dwindled.
The toolbar
Name Icon Description
HTML It enables you to read and edit 3 different types of content. The 3 types of content include HTML, HTML Source
and Plain Text.
HTML: Read and edit the original content.
HTML Source: Read and edit the HTML source of content.
Plain Text: Read and edit content without formats.
Table Add a table. A few formats of insertion for rows and columns can be selected, including: Insert Row Above,
Insert Row Below, Insert Column on Left and Insert Column on Right.
Insert Row Above: Insert a row above the row you selected.
Insert Row Below: Insert a row below the row you selected.
Insert Column on Left: Insert a column on the left of the column you selected.
Insert Column on Right: Insert a column on the right of the column you selected.
Clear formats Clear formats of whole editor to convert the content to plain text.
2. In Glossary Grid, click Open Specification... button in order to fill more details about the new item.
4. Further information about the new item can be given by typing in the space under Documentation.
Type in text
5. Finally, click OK to confirm editing. The window will then return to Glossary Grid.
6. Moreover, you can insert as many new terms as you prefer. In Glossary Grid, click Create Term (Insert) to create another new term.
Checking spelling
When you type an incorrect word carelessly, documentation pane can offer you a help.
Moreover, you can add a new word to the dictionary if the word you typed is a rare word or a new created word. Right click the new word and select
Add to dictionary from the pop-up menu. When you type the word next time, it won't be marked as an incorrect word again.
In Record Voice dialog box, enter the name for the audio clip. Click Record to start recording while click Stop to terminate. Click OK if you want to
save the voice recording; click Cancel, and vice verse.
The toolbar
Name Icon Description
Add Stencil Select a stencil to create a new shape. Different sorts of stencil are categorized into two folders: Computers and Shapes
and a large amount of subfolders are subdivided into these two folders.
Import Stencil... Import a stencil that created externally in Microsoft Visio to VP-UML.
Creating a stencil
Instead of keeping the existing shapes, users can create a stencil to replace an existing one.
Click Add Stencil button on the top of stencil pane and select a subfolder from the pop-up menu.
Editing a stencil
A stencil can be customized according to users' preference in Shape Editor.
Right click on the stencil pane's background and select Open Shape Editor from the pop-up menu.
Importing a stencil
The function of importing stencil enables you to import a stencil which is created in Microsoft Visio externally and send it to VP-UML by making using of
the plug-in "VisioSendToVP".
Note that you are able to execute this function only after you have installed Microsoft Visio and have sent a stencil from Visio.
1 UML version Select the version of UML notation for the project. Normally you would select UML 2.1 so you can create UML
diagrams of the latest standard. However if you want to create diagrams with older notation you should select UML
1.x.
2 Language The Language combo box lets you select the programming/scripting language for the project. The language you
selected mainly affects the class modeling. For example, the selectable visibilities and primitive types vary among
languages.
3 Properties A page for specifying basic information of project like the project name, author, company and description.
5 Other CASE Tools A page for you to specify either a Rose or XMI file path for creating a new project.
Project
Properties
To create a blank project, ensure the Properties page is being selected, and then click the Create Blank Project button.
1 UML version Select the version of UML notation for the project. Normally you would select UML 2.1 so you can create UML diagrams of
the latest standard. However if you want to create diagrams with older notation you should select UML 1.x.
5 Project description The project description. You can make use of the toolbar on top of the description pane to add formatted content.
Template
If you often create projects of similar structure, you can save the project as a template and use it for creating project later. For example, you can save
a project with a use case diagram and a class diagram as template called "Static Modeling Template". When we create project from this template, the
project will have the same structure as the template automatically.
2 Template preview By selecting a template from the template list, you can read the structure in the Template preview pane.
3 Rose import The selection controls what to import. There are two modes:
mode
Model element and diagram -Import both model elements (e.g. use case, class...) and diagrams (e.g. use case diagram, class
diagram...)
Model element only - Import only model element but not diagram. In the new project you can find the imported model
elements in Model Explorer.
4 Import from Select this option if you want to create a new project by importing a XMI file.
XMI
Creating model
To create a Model, right-click on the project node in Model Explorer and select Model from the pop-up menu. You can either create a custom Model
by selecting New Model..., or create a pre-defined Model (e.g. Analysis Model) by selecting it in the list.
NOTE: When you create a shape, its model element will be put under the same model as diagram.
Select the diagrams you want to move in the Add Sub Diagrams dialog box and click OK button.
NOTE: If you move a diagram which has the master view of model element(s), the model element(s) will be moved together with the diagram to
the new model.
NOTE: You can only reference to a project that was saved under the same version of VP-UML you are opening. For example, if you are running
VP-UML 7.1, you can only reference to a project saved by version 7.1 of VP-UML.
4. Click Close.
NOTE: By selecting the first selection (Current), model elements in the current project will be listed.
NOTE: Alternatively, you can right-click on the model elements and select Create View in Active Diagram from the popup menu.
NOTE: Views for dependent project are read-only (i.e. non edit-able).
After that, you can see the indicator, which is a small arrow, appear at the shapes that are referencing a dependent project.
You can visualize an existing model element by dragging and dropping a model element from Model Explorer to diagram. We call the visualized form
of model element a view, or a shape, depending on whether we want to emphasis the differences against model element, or we want to focus on
diagramming operations.
Creating a view from an existing model element through drag and drop
When developing context-based diagrams, you will reuse a model element in different diagrams, resulted in creating multiple views. Each model
element can associate with zero to multiple views. When you make specification-level change, such as changing of name, on any view, the change will
be applied to all views.
Enter name for the newly created use case diagram in the text field of pop-up box on the top left corner.
Drawing a system
To create a system, select System on the diagram toolbar and then click it on the diagram pane. Finally, name the newly created system when it is
created.
Create a system
Create an actor
NOTE: Alternatively, you can press Alt + Enter to force a new line.
Create a package
Option Description
Prefix The prefix you enter in Prefix text field will be inserted before the number.
Num of The number of digits for the number. For example, when digit is 3, ID "1" will become "001".
digits
Suffix The suffix you enter in Suffix text field will be inserted behind the number.
Showing ID on diagram
By default, ID is just a text property. It usually doesn't appear on diagram. However, you can make it shown within a use case.
Right click on the diagram background, select Presentation Options and the specific model element display option from the pop-up menu.
Show ID on diagram
NOTE: The feature of showing ID does only support for use case, but not for actor.
ID assignment
There are several ways that you can assign an ID to a model element, including:
• Through the specification dialog box (Right click on the selected model element and select Open Specification... from the pop-up menu)
• Through the Property Pane
2. After selected, an extra slash will be shown on the left edge of the use case.
Business model
Entering details
Details are predefined and detailed fields of a use case, which includes level, complexity, status, implementation status, preconditions and post-
conditions, author and assumptions. Select an option for Level, Complexity, Use Case Status and Implementation Status from the drop-down
menu.
2. When the Select Requirement dialog box pops out, select the requirement you want to link to and click OK to confirm. The searching scope
of selecting requirement may be narrow down if you find too many requirements in your project. Select a specific diagram from the drop-down
menu at the top left corner of dialog box, or enter its name at the Filter field directly at the top right corner.
Select a requirement
3. Once the link is inserted in the text field, you can right click to navigate it through its pop-up menu.
Adding requirements
Requirements of a use case can be added in the Requirements page.
Select a requirement
NOTE: The Requirements page is for adding existing requirements as requirements. If you want to define a new requirement, read the next
section Adding a sub-diagram. Information about how to add a requirement diagram as sub-diagram and define the requirements in the
diagram is provided. Requirements are made in Diagrams page will be automatically added to the use case's requirements.
Managing sub-Diagrams
You can make use of another diagram for elaborating a use case. The Diagrams page enables you to add and open sub-diagrams of a use case.
When you select a diagram on the list on the left, you may preview it on the right if Show preview is checked.
Adding a sub-diagram
Add a sub-diagram
Opening a sub-diagram
Select a sub-diagram on the list to open and click the Open button at the bottom of Diagrams page.
Drop-down menu of Flow of Events You may select Manage... from the drop-down menu to create new flow of
events.
Add menu Select an existing use case/ actor/ requirement in the current project and insert
it in the selected step for referenced link.
Font Select font effect for the highlighted text: Bold, Italic and Font Color.
Synchronize to Activity Diagram Synchronize the flow of events to activity diagram. If no activity diagram has
created previously, a new activity diagram will be generated.
Model Element Link Presentation Options To select the presentation for use case link/ actor link/ requirement link.
Name : To display the name of model element only.
ID : To display the ID of model element only.
ID: Name: To display both the name and ID of model element.
Drop-down menu of Testing Procedure Select Main to create testing procedure while select Manage... to create a new
testing procedure. Columns of procedures and expected results will be shown
respectively on the step pane for editing testing procedure.
NOTE: To add a sub event, click on the row of sub event, and either press the Tab/Ctrl-Period button or click on the button at the toolbar to
indent the event row. On the contrary, press Shift-Tab/Ctrl-Comma or click on the button to decrease the indentation.
Select Actor...
When the Select [model element] dialog box pops out, select a specific one and then click OK button to insert.
As a result, the actor/ usecase/ requirement link will show on the specific event.
The presentation of link can be customized by pressing Model Element Link Presemtatopm Options button. Select Name, ID or ID: Name from
the corresponding drop-down menu in Model Element Link Presentation Options dialog box. Selecting Name refers to display the name of model
elements only while selecting ID refers to display the ID of model element only. Selecting ID: Name refers to display both the name and ID of model
element.
NOTE: The searching scope of selecting actor/ usecase/ requirement in the dialog box can be limited by selecting a specific diagram from the
drop-down menu.
Fill extensions
NOTE:
To add a sub item, click on the row of sub event, and click at the toolbar to indent the event row. On the contrary, click to
decrease the indentation.
Select Main
2. Enter the testing procedure for the event that we need to test in Procedures text field.
4. Repeat the previous steps until finish documenting the testing procedure.
2. When the Flow of Events dialog box pops out, click the New Flow of Events button to create a new flow of events.
3. Enter the name of flow of events in Input dialog box. Click OK to confirm.
4. Click OK button to close the Flow of Events dialog box. As a result, the newly created flow of events will be available from the drop-down
menu.
NOTE: If you want to view the specific event in an activity diagram, right click on the event and select Open "[step]" Activity Action from the
pop-up menu.
3. Start editing the steps under flow of events pane. After finish editing, right click on the background of flow of events and select Synchronize to
Activity Diagram from the pop-up menu.
Field Description
Click this button to reveal Name and Model Element. To hide these them, click this button again.
To filter actors by name. The rubber on the right hand side is for clearing the filter content.
Creating actor
1.
Click on above the grid.
2. Name the actor. You may optionally reset the ID by double-clicking on the ID cell and entering a new one.
Name actor
NOTE: The actors created in actors grid are automatically put under the Actors model. You may move to another model through dragging and
dropping in Model Explorer.
Visualizing an actor
You can form a diagram with actor, or show it in an existing diagram by visualizing it in actors grid. To visualize an actor:
1. Select the actor to visualize.
2.
Click on above the grid.
If you want to visualize actor in an existing diagram, check Show in existing diagram and select a diagram in the diagram list.
Finding actor
To find out actors that match specific naming or documentation pattern:
1.
Click above the grid.
Find an actor
2. In the Search Text text box, enter the text to search. Specify whether to search the names and/or documentation of actors. Click Find button.
As a result, the grid is updated to highlight the matched actor(s).
Configure Grid Click this button to reveal Name and Model Element. To hide these them, click this button
again.
Open Use Case Detail To open the use case details of use case selected in grid.
Project To filter use cases by selecting the diagram(s) (or all diagrams) that contain the use
casesuse case.
Use Case's name To filter use cases by name. The rubber on the right hand side is for clearing the filter
filter content.
2. Name the use case. You may optionally reset the ID by double-clicking on the ID cell and entering a new one.
NOTE: The use cases created in use cases grid are automatically put under the Use Cases model. You may move to another model through
dragging and dropping in Model Explorer.
2.
Click on above the grid.
If you want to visualize use case in an existing diagram, check Show in existing diagram and select a diagram in the diagram list.
2. In the Search Text text box, enter the text to search. Specify whether to search the names and/or documentation of use cases. Click Find. As a
result, the matched use case(s) will be highlighted.
Enter use case name, check Name and click Find button
Creating swimlane
You can click either Horizontal Swimlane or Vertical Swimlane on the diagram toolbar.
Create swimlane
Swimlane created
Rename partition
A partition is inserted.
Partition inserted
Creating action
Mouse over the initial node until its resources are visible. Click on the Control Flow -> Action resource and drag.
Create action
Move the mouse to where you want to place the action to, and then release the mouse button. An action is created and is connected to the initial node
with a control flow.
Action created
A new action is created and is connected to the action with a control flow.
Action created
Edit scenarios
2. In the Edit Scenarios dialog box, click Add... button at the bottom left corner.
Add a scenario
NOTE: A path is a continuous flow of actions in the diagram, with an initial node placed at the beginning of the actions. Multiple paths are
obtained by determining the existence of decision nodes within the flow.
5. The actions being involved in the flow are listed in the Path table. For actions that have sub-diagram(s), pick up the sub-diagram in Diagram
column, or just create a new one. You may, however, leave it unspecified, which cause that action to be ignored when producing scenario.
Updating scenario
Whenever the sub-diagram(s) of action(s) are updated, you can update the scenario to make it represents the latest information of interaction. To
update scenario, right click on the activity diagram that have scenario produced before, select Scenarios, then the name of scenario from the popup
menu.
Drag it to your preferred place and then release the mouse to confirm the place. As a result, a state is created and is connected to the initial pseudo
state with a transition.
Similarly, you can use the Transition -> Final State resource to create a final state.
When the Transition Specification dialog box pops out, you can edit its name, effect and guard. Next, click Edit... button of the Effect property.
In Activity Specification (Effect) dialog box, change its name, and then click OK button to apply the change.
Click OK in the Transition Specification dialog box to close it. The name and effect are shown on the transition caption.
Double click on the top left corner of the frame to rename it.
Rename frame
Frame renamed
Add lifeline
Repeat the step to add as many as time units you need. Double-click on a time unit to rename it.
Add state/condition
You can also move a group of time instances that are at the same state/condition. Mouse over the time instances and you will see a blue line above
them, click and drag on the blue line.
Release the mouse button when reached the target state/condition. The group of time instances is moved at once.
Edit frame
In the Edit Frame dialog box, open the Time Messages tab and click Add... button.
Time message
Enter name for the newly created sequence diagram in the text field of pop-up box on the top left corner.
Creating actor
To create actor, click Actor on the diagram toolbar and then click on the diagram.
Create actor
Creating lifeline
To create lifeline, you can click LifeLine on the diagram toolbar and then click on the diagram.
Alternatively, a much quicker and more efficient way is to use the resource-centric interface. Click on the Message -> LifeLine resource beside an
actor/lifeline and drag.
Create lifeline
Move the mouse to empty space of the diagram and then release the mouse button. A new lifeline will be created and connected to the actor/lifeline
with a message.
Sweeper
Click on empty space of the diagram and drag towards top, right, bottom or left. Shapes affected will be swept to the direction you dragged.
The picture below shows the actor Inspector Assistant is being swept towards right, thus new room is made for new lifelines.
Sweep downwards
You can also use magnet to pull shapes together. To use magnet, click Magnet on the diagram toolbar (under the Tools category).
Magnet
Click on empty space of the diagram and drag towards top, right, bottom or left. Shapes affected will be pulled to the direction you dragged.
Editing lifelines
There are two panes, Lifelines and Messages. The Lifelines pane enables you to create different kinds of actors and lifelines.
Ctrl-L To link with the diagram, which cause the diagram element to be selected when selecting an element in editor, and vice versa
Editing messages
The Messages pane enables you to connect lifelines with various kinds of messages.
If you choose Single Level, all sequence messages will be ordered with integers on diagram base. On the other hand, if you choose Nested Level, all
sequence messages will be ordered with decimal place on diagram base.
Single level
When you set the way of numbering sequence messages on frame base, the sequence messages in frame will restart numbering sequence message
since they are independent and ignore the way of numbering sequence message outside the frame.
Creating actor
To create actor, click Actor on the diagram toolbar and then click on the diagram.
Create actor
Creating lifeline
To create lifeline, you can click LifeLine on the diagram toolbar and then click on the diagram.
Alternatively, a much quicker and more efficient way is to use the resource-centric interface. Click on the Message -> LifeLine resource beside an
actor/lifeline and drag.
Create lifeline
Move the mouse to empty space of the diagram and then release the mouse button. A new lifeline will be created and connected to the actor/lifeline
with a link (the line) and a message (the arrow).
Reorder messages
When the Communication Diagram Specification dialog box appears, the Message tab is opened by default. Double click on the Sequence # cell of
a message to edit it. Click OK button to apply the changes.
An initial node is created. The caption of initial node is hidden by default, to show it, right-click on the diagram and select Presentation Options >
Show Shape Caption > Initial Node from the pop-up menu.
Generic resource
If you want to show the caption of decision node, right click on the diagram background and select Presentation Options > Show Shape Caption >
Decision Node from the pop-up menu.
Drag it to your preferred place and then release the mouse button. An interaction use is created and connected to the shape you selected with a control
flow.
You can make the interaction use refer to a diagram by right clicking on it and select Refers to > New Sequence Diagram from the pop-up menu.
Rename
sequence diagram
Drag it to your preferred place and then release the mouse button. A fork node is created and connected to the shape you selected with a control flow.
The fork node created is vertical by default. If you want to change it to horizontal, right click on the fork node and select Orientation > Horizontal from
the pop-up menu.
Moreover, if you want to show the caption of fork node, right click the diagram and select Presentation Options > Show Shape Caption > Fork Node
from the pop-up menu.
Creating interaction
To create an interaction, move the mouse over a shape and press its resource icon Control Flow -> Interaction.
Create interaction
Drag it to your preferred place and then release the mouse button. An interaction is created and connected to the shape you selected with a control
flow.
Sequence diagram
When you return to the interaction overview diagram, you can see the interaction shows the thumbnail of the sequence diagram.
Drag it to your preferred place and then release the mouse button. A join node is created and connected to the shape you selected with a control flow.
The join node created is vertical by default, to change it to horizontal, right-click on the join node and select Orientation > Horizontal from the pop-up
menu.
Moreover, if you want to show the caption of join node, right click the diagram background and select Presentation Options > Show Shape Caption >
Join Node from the pop-up menu.
If you want to show the caption of activity final node, right click on the diagram background and select Presentation Options > Show Shape Caption
> Activity Final Node from the pop-up menu.
Continue to complete the diagram.
Completed diagram
Creating class
To create class, click Class on the diagram toolbar and then click on the diagram.
Create class
Class created
Creating association
To create association from class, click the Association -> Class resource beside it and drag.
Create association
Drag to empty space of the diagram to create a new class, or drag to an existing class to connect to it. Release the mouse button to create the
association.
Association created
Create aggregation
To edit multiplicity of an association end, right-click near the association end, select Multiplicity from the popup menu and then select a multiplicity.
Edit multiplicity
To show the direction of an association, right click on it and select Presentation Options > Show Direction from the pop-up menu.
Show direction
Direction shown
Creating generalization
To create generalization from class, click the Generalization -> Class resource beside it and drag.
Create generalization
Drag to empty space of the diagram to create a new class, or drag to an existing class to connect to it. Release the mouse button to create the
generalization.
Generalization created
Creating attribute
To create attribute, right click the class and select Add > Attribute from the pop-up menu.
Create attribute
An attribute is created.
Attribute created
Create operation
An operation is created.
Operation created
Similar to creating attribute, you can press the Enter key to create multiple operations continuously.
To copy a class member, select it and drag to the target class while keep pressing the Ctrl key, you will see a thick black line appears indicating where
the class member will be placed. A plus sign is shown beside the mouse cursor indicating this is a copy action.
Press up or down key to select class in the list, press Enter to confirm. Upon selecting an existing class, all class members and relationships are shown
immediately.
Completed diagram
Generalization set
A generalization set defines a particular set of generalization relationships that describe the way
in which a general classifier (or superclass) may be divided using specific subtypes. To define a generalization set, select the generalizations to
include, right click and select Generalization set > Create Generalization Set... from the popup menu.
The selected generalizations are grouped. Adjust the connector to make the diagram tidy.
Adjust connector
Per diagram
This applies to classes in specific diagram. To change the setting:
1. Right click on the class diagram to set the option.
2. Select Presentation Options > Attribute Display Options / Operation Display Options from the pop-up menu.
Per class
This applies to specific class. To change the setting:
1. Right click on the class to set the option.
2. Select Presentation Options > Attributes / Operations from the popup menu.
3. Select Hide All / Show All / Show Public Only.
NOTE: In order to select the attribute of another class to be the default value, make sure the attribute you want to select is static (i.e. set to be in
classifier scope) and is public (so that other classes can access).
3. Click OK to confirm.
Selecting classifiers
To specify classifiers for an instance specification, right-click it and select Select Classifier > Select Classifier... from the pop-up menu.
Select classifier
Click OK button to close the specification dialog box. The selected classifiers are assigned to the instance specification.
Classifiers assigned
Defining slots
To define slots for an instance specification, right-click it and select Slots. .. from the pop-up menu.
Defining slots
Enter the value when prompted. Close the specification dialog boxes to apply the changes, defined slots will be shown in the instance specification.
Creating link
To create link from instance specification, click the Link -> Instance Specification resource beside it and drag.
Create link
Drag to empty space of the diagram to create a new instance specification, or drag to an existing instance specification to connect to it. Release the
mouse button to create the link.
Link created
Completed diagram
Creating package
To create package, click Package on the diagram toolbar and then click on the diagram.
Create package
Package created
Assigning stereotypes
Right click on the package and select Stereotypes > Stereotypes... from the pop-up menu.
Assign stereotypes
When the Package Specification dialog box pops out, the Stereotypes tab is opened by default. The list on the left shows the selectable stereotypes.
Edit stereotypes
Add stereotype
Close the specification dialog box. Stereotypes will be applied to the package.
Stereotypes assigned
Completed diagram
Creating class
To create class, click Class on the diagram toolbar and then click on the diagram.
Create class
Class created
Creating part
To create part, move the mouse over the target class, press its resource icon New Part.
Create part
Part created
Creating port
To create port, move the mouse over the target class, press its resource icon New Port.
Create port
Port created
Select type
Click OK button to apply the changes. Type will be shown on the caption of the port.
Creating connector
To create connector, click Connector on the diagram toolbar.
Create connector
Drag from the source shape, move the mouse over the target shape and then release the mouse button to create the connector.
Connector created
Completed diagram
Creating component
To create component, click Component on the diagram toolbar and then click on the diagram.
Create component
Component created
Assigning stereotypes
Right click on the package and select Stereotypes > Stereotypes... from the pop-up menu.
Assigning stereotypes
Edit stereotypes
Add stereotype
Close the specification dialog box. Stereotypes will be applied to the package.
Stereotypes assigned
Drag it to your preferred place to create a new interface, or drag to an existing interface to connect to it. Release the mouse button to create the
required interface.
Creating dependency
To create dependency, click Dependency on the diagram toolbar.
Create dependency
Drag from the source shape, move the mouse over the target shape and then release the mouse button to create the dependency.
Dependency created
Completed diagram
In the New Model Element dialog box, type Node (Deployment) in Model element type, type the node name in Model element name. Click OK to
confirm.
Create node
Node created
Selecting classifiers
To specify classifiers for an instance specification, right-click it and select Select Classifier > Select Classifier... from the pop-up menu.
Select classifier
Click OK button to close the specification dialog box. The selected classifiers are assigned to the instance specification.
Classifiers assigned
Creating link
To create link from instance specification, move the mouse over the target shape and press its resource icon Link -> Instance Specification.
Create link
Drag to empty space of the diagram to create a new instance specification, or drag to an existing instance specification to connect to it. Release the
mouse button to create the link.
Link created
Instance of component
Create dependency
Drag from the source shape, move the mouse over the target shape and then release the mouse button to create the dependency.
Dependency created
Completed diagram
2. Press on the Verify <- Test Case resource of requirement and drag.
2. Press on the Verify -> Requirement resource of test case and drag.
2. In the Test Plans tab, fill in the Steps, Procedures and Expected Results.
Creating requirement
To create a Requirement, click the Requirement button on the diagram toolbar and then click on the diagram.
Create requirement
Decomposing requirement
To decompose a Requirement, click the Containment -> Requirement resource and drag.
Decomposing Requirement
Requirement Specification
Move the mouse over a Requirement and then release the mouse button, a Verify relationship will be created from the Test Case to the Requirement.
Configure Requirements
The Configure Requirements dialog box appears. Click Add to add a new requirement type.
Name the newly created attribute. Create as much as attribute you need by following the previous step.
NOTE: If you select Enumeration Attribute from the drop-down menu, Edit Enumeration... button will appear. Click Edit Enumeration... button
to edit it.
Besides defining attributes, you can format the requirement type with fill, line and font. Click the ... button of Fill if you want to customize a color for the
requirement type.
NOTE: Click the ... button of Line if you want to customize its line property while click the ... button of Font if you want to customize its font
property.
Finished configuring
Finally, you can see the customized requirement type is available on the diagram toolbar. You can select and click it on the diagram to create the
shape.
Field Description
Click this button to reveal Name and Model Element. To hide these them, click this button again.
To filter requirements by selecting the diagram(s) (or all diagrams) that contain the requirements.
To filter requirements by name. The rubber on the right hand side is for clearing the filter content.
Creating requirement
1.
Click on above the grid.
Create a requirement
2. Name the requirement. You may optionally reset the ID by double-clicking on the ID cell and entering a new one.
Name requirement
NOTE: The requirements created in requirements grid are automatically put under the Requirements model. You may move to another model
through dragging and dropping in Model Explorer.
Visualizing a requirement
You can form a diagram with requirement, or show it in an existing diagram by visualizing it in requirements grid. To visualize a requirement:
1. Select the requirement to visualize.
2.
Click on above the grid.
Create visualize
If you want to visualize requirement in an existing diagram, select Show in existing diagram and select a diagram in the diagram list.
Finding requirement
To find out requirements that match specific naming or documentation pattern:
1.
Click above the grid.
Find a requirement
Finding result
When the Open dialog box pops out, select a text file to import. As a result, the imported problem statement will be shown on the text area.
2. When the Glossary Grid page unfolds, enter name for the glossary grid and then right click on the newly created term and select Open Term
Editor from the pop-up menu.
NOTE: If the Aliases column is hidden, you can click Configure Columns... button. Open Properties tab and select it under Details folder.
Extract words
As soon as a candidate object is created on the right-hand side, all occurrences of the candidate object name are highlighted on the left-hand side.
Alternatively, you can create a candidate object and select your preferred type of model element simultaneously. Highlight a word/ phrase on the left-
hand side editor, right click to select add text with your preferred type of model element from the pop-up menu.
As a result, a candidate object with your selected type of model element will be shown on the right-hand side.
When the Visualize Model Element dialog box pops out, check Create new diagram if you want the model element to be shown on a new diagram or
check Show in existing diagram if you want the model element to be shown on a specific existing diagram. Finally, click the Show button to proceed.
Edit description
Add attribute
Enter the name and description. Repeat this step until all attributes are added.
Attribute added
Adding responsibilities
Right-click on the Responsibilities heading and select Add > Responsibility from the pop-up menu. Similar to creating an attribute, enter the name
and collaborator of each responsibility to show the relationship with other parties.
Add responsibility
NOTE: Alternatively, you can create a User Interface diagram with the steps below:
• Select New Diagram > Others > User Interface from the main menu.
• Click on the New User Interface button under Diagramsicon on toolbar
• Click on New User Interface in Start Page
3. Press Enter to confirm the diagram name. As a result, the name for User Interface diagram is created.
Creating a frame
1. Select the Frame tool from the diagram toolbar.
Select Frame
2. Press on diagram to set the position of the frame. Drag diagonally from the starting point to expand the frame.
A frame is created
Frame properties
The appearance of frame can be changed by editing its properties. To configure a frame, right click on the Frame and select Open Specification...
from the popup menu. The UI tab is where user can configure a frame.
Property Description
Title Title refers to the text that appear at the top of frame, which use to be the caption of application or the function of opening frame.
Icon Icon is the tiny image that appear at the top left of frame. Users are required to provide a valid image file as icon.
Iconifiable The Iconifiable state controls whether the minimize button is shown or not. When Iconifiable is set, the minimize button is shown,
otherwise hidden.
MaximizableThe Maximizable state controls whether the maximize button is shown or not. When Maximizable is set, the maximize button is shown,
otherwise hidden.
Closable The Closable state controls whether the close button is shown or not. When Closable is set, the close button is shown, otherwise
hidden.
Frame P. 250
Label
A label is a text component that appears on a screen. The text "User", "Password", "Address" appear on a registration form are examples of labels.
Creating a label
1. Select the Label tool from the diagram toolbar.
A label is created
Label properties
The appearance of label can be changed by editing its properties. To configure a label, right click on the label and select Open Specification... from
the popup menu. The UI tab is where user can configure a label.
Property Description
Mnemonic
Mnemonic is a key which enables users to select a label by simultaneously pressing the Alt key and the mnemonic key on the keyboard.
Label P. 251
Text field
Text Field is a component that allows the editing of a single line of text. Fields in a registration form are typical examples of text fields.
2. Press to set the position of the text field. Drag diagonally from the starting point to expand the text field.
Property Description
Text Text refers to the text that appears in the text field.
Creating a scrollbar
1. Select the Horizontal/Vertical Scrollbar tool from the diagram toolbar. You can change between a horizontal or a vertical scrollbar tool by
clicking on the tiny reverted triange, and selecting the preferred type of scrollbar from the popup menu.
2. Click on a container (e.g. a Frame) or diagram background to create a scrollbar. If you create inside a container, and if it has no scrollbar with
same orientation exists, the scrollbar will be docked to the bottom or the right of the container, depending on the scrollbar orientation.
Scrollbar is created
Scrollbar P. 253
Scrollbar properties
The appearance of scrollbar can be changed by editing its properties. To configure a scrollbar, right click on the scrollbar and select Open
Specification... from the popup menu. The UI tab is where user can configure a scrollbar.
Property Description
Block Amount the value changes when the scrollbar track is clicked on either side of the knob.
increment
Unit increment Amount the value changes when the end arrows of the scrollbar are clicked.
Value Value which controls the location of the scroll bar knob.
Scrollbar P. 254
Combo box
Combo box is a component that combines a button and a drop-down list. The user can select a value from the drop-down list, which appears at the
user's request.
2. Click to set the position of the combo box. Drag diagonally from the starting point to expand the combo box.
Property Description
Creating a list
1. Select the List tool from the diagram toolbar.
2. Press to set the position of the list. Drag diagonally from the starting point to expand the list.
List is created
List P. 257
4. Repeat step 2 and 3 to create all the list items.
List properties
The appearance of list can be changed by editing its properties. To configure a list, right click on the list and select Open Specification... from the
popup menu. The UI tab is where user can configure a list.
Property Description
Horizontal scroll bar Determines when a horizontal scrollbar will appear in a list.
Vertical scroll bar Determines when a vertical scrollbar will appear in a list.
List P. 258
Table
Table is used to display and edit regular two-dimensional tables of cells.
Creating a table
1. Select Table from the diagram toolbar.
2. Press to set the position of the table. Drag diagonally from the starting point to expand the table.
Table is created
Table P. 259
2. In the UI tab of the UITable Specification dialog box, click either Insert Column to Left or Insert Column to Right to insert the first column.
3. Enter the column name in Input dialog box and click OK to confirm.
4. Repeat step 2 and 3 to create all columns.
5. Click Insert Row Below to insert a row. Note that a row can be inserted only when a column exists.
6. A row is created with empty cell(s). Fill in the cell(s) if necessary. Cell can be edited by double clicking or by pressing the F2 key.
7. Repeat step 5 and 6 to create all rows.
Table P. 260
8. Click OK to confirm editing.
Removing a column
To remove a column in a table, open UITable Specification dialog box, open the UI tab, right click on a cell of a column and select Remove Column
in the pop-up menu.
Table P. 261
Removing a row
To remove a row in a table, open UITable Specification dialog box, open the UI tab, right click on a row and select Remove Row in the pop-up menu.
Reordering rows
To reorder rows, open UITable Specification dialog box, open the UI tab,select the row(s) to reorder, and click on the Move Selected Rows Up or
Move Selected Rows Down button.
Table P. 262
Table properties
The appearance of table can be changed by editing its properties. To configure a table, right click on the table and select Open Specification... from
the pop-up menu. The UI tab is where user can configure a table.
Property Description
Determines how the widths of columns will be affected when other columns in the table are being resized.
Off: Disable auto resizing.
Next column: When a column is being resized, all columns on the right and left of margin are updated.
Subsequent columns: When a column is being resized, all columns on the right are resized at the same time.
Last column : When a column is being resized, width of the right-most column are updated.
All columns: When a column is being resized, widths of all columns are changed.
Table P. 263
Tree
A Tree is a component that displays a set of hierarchical data as an outline.
Creating a tree
1. Select the Tree tool from the diagram toolbar.
2. Press to set the position of the tree. Drag diagonally from the starting point to expand the tree.
Tree is created
Tree P. 264
2. In the UI tab of the UITree Specification dialog box, click either Insert Node Below or Insert Node Above to insert the first column. Note that
Insert Node Below/Above means to create an adjacent node.
3. Enter the node name in Input dialog box and click OK to confirm.
4. To add a child node, select an existing node.
Tree P. 265
5. Click Add Child Node.
6. Enter the node name in Input dialog box and click OK to confirm.
7. Repeat step 2 to 6 to create all nodes.
8. Click OK to confirm editing.
Tree P. 266
Removing a node
To remove a node in a tree, open the specification dialog box of the tree, open the UI tab, right click on the node(s) to remove and select Remove
Node in the popup menu.
Tree P. 267
Reordering nodes
To reorder nodes, open the specification dialog box of the tree, open the UI tab, select the node(s) to reorder, and click on the Move Up or Move
Down button.
Tree properties
The appearance of tree can be changed by editing its properties. To configure a tree, right click on the tree and select Open Specification... from the
popup menu. The UI tab is where user can configure a tree.
Property Description
Show root handles Determines whether the expand/collapse button for root will appear.
Horizontal scroll bar Determines when a horizontal scrollbar will appear in a tree.
Vertical scroll bar Determines when a vertical scrollbar will appear in a tree.
Node icons Set the image icon to appear for a node when at different state.
Default node icon: Icon for all nodes when default icon for collapsed and expanded nodes
are not set.
Default collapsed icon: Icon for collapsed nodes. It overwrites the default node icon
setting.
Default expanded icon: Icon for expanded nodes. It overwrites the default node icon
setting.
Tree P. 268
Web Label
A web label is a text component that appear on a screen. The text "User", "Password", "Address" appear on a registration form are examples of labels.
Creating a label
1. Select the Web Label tool from the diagram toolbar.
2. Click on a container (e.g. a Web Panel) or diagram background to create a web label.
3. Enter the label caption and press Enter to confirm the caption of label.
A label is created
Label properties
The appearance of web label can be changed by editing its properties. To configure a web label, right click on the label and select Open
Specification... from the popup menu. The UI tab is where user can configure a label.
Property Description
A button is created
Property Description
2. Press to set the position of the text input. Drag diagonally from the starting point to expand the text input.
Property Description
Value Value refers to the text that appears in the text input.
2. Press to set the position of the combo box. Drag diagonally from the starting point to expand the combo box.
Property Description
Options The items that can be selected by users. You can optionally mark the default item's Selected to be
true.
Creating a list
1. Select the Web List tool from the diagram toolbar.
2. Press to set the position of the list. Drag diagonally from the starting point to expand the list.
List is created
List properties
The appearance of web list can be changed by editing its properties. To configure a list, right click on the list and select Open Specification... from the
popup menu. The UI tab is where user can configure a list.
Property Description
ID ID of list in form.
Options The items that can be selected by users. You can optionally mark the default item's Selected to be
true.
Multiple Determine whether the list supports single or multiple item selection.
2. Press to set the position of the password input. Drag diagonally from the starting point to expand the password input.
3. Release the mouse button to confirm the size of password input and press Enter to confirm the title of password input.
Property Description
2. Press to set the position of the file input. Drag diagonally from the starting point to expand the file input.
3. Release the mouse button to confirm the size of file input and press Enter to confirm creation.
Property Description
2. Click on the diagram to create a Callout shape. Enter the content of annotation. Formatting can be applied through the buttons at the bar above
the callout shape.
3. We need to attach the pointer of Callout shape to the User Interface component that needs to be annotated. Drag on the end of Callout shape's
pointer towards the User Interface component.
4. Release the mouse button to confirm the pointer position when reached the component.
5. Click on the diagram background to confirm editing.
2. When the Glossary Grid page is opened, right click on the newly created term and select Open Term Editor from the pop-up menu.
5. As a result, the columns of Aliases and Documentation are filled when you return Glossary Grid page.
Glossary grid
2 Model Element You can select the model element you want to be listed in grid from the drop-dwon menu.
3 Configure Grid Click this button to reveal Name and Model Element. To hide these them, click this button again.
5 Find To search a term/ phrase, click this button. Enter the keyword of your term/ phrase in Search Text text field and check
the searching field: Name, Aliases, Label or Documentation.
6 Open Term Editor Click this button to open Term Editor page of the selected term. In Term Editor page, you can define the term,
stereotypes and tagged values.
7 Open Specification... Click this button to open the specification dialog box of the selected term. In Term Specification dialog box, you can
define aliases, assign label and enter documentation.
8 Export to Excel To save and export the selected term into a new Excel.
10 Show View Click this button to show the orginal model element of the selected term.
11 Visualize... Click this button to duplicate the selected model element on the chosen digram (in either new diagram or existing
diagram).
12 Manage Label Label can be defined to categorize terms. This button is for adding, editing and deleting labels.
15 Project To select the scope for showing mdoel elements on Term list.
16 Filter Term To enter the keyword of your target term with *, you can find it in shortcut.
Defining label
1. After you have selected a term in any textual documentation to add it to glossary, the glossary grid is opened. Click Manage Label button.
Add a label
3. In the Glossary Label Specification dialog box, name the label and select a color for it. Click OK button to confirm.
Assigning label
1. Let's assign a specific label to the corresponding term. Click the small plus button under Labels column of your target term.
NOTE: If the Labels column doesn't show on the grid, you can click the Configure columns... button. Open Properties tab and select it under
Others folder..
Check a label
NOTE: You can apply multiple labels to a term. Check the applicable labels in the Add Label dialog box.
Check Membership
2. In the Export Excel dialog box, enter the output directory. Click Export button.
Business actor
Business role
Business process
Business function
Business interaction
Business event
Junction
Business service
Business interface
Business object
Product
Contract
Representation
Meaning
Value
Application collaboration
Application component
Application service
Application function
Application interaction
Data object
Node
Device
System software
Infrastructure interface
Infrastructure service
Artifact
Communication path
Network
2. When the Grid Diagram is opened, enter name for the grid.
The model element of selected type will then be shown on the grid.
2. Enter name for the newly created model element and then press Enter to confirm.
Enter name
2. In the Configure Columns dialog box, select your preferred property under Properties tab and then click OK button.
As a result, the deselected property column will be removed from the grid.
Select scope
NOTE: Within Model or Package: Select this when you want to show all selected model element types within a particular model/ package.
Root Model Element: Select this when you want to show all selected model element types under root node.
All Diagrams: Select this when you want to show all selected model element types within all diagrams.
Within Diagram: Select this when you want to show all selected model element types within a particular diagram.
No Diagram: Select this when you want to show all selected model elements without diagram.
2. As a result, grid content is updated to list the model elements that fit the selected scope.
Filtering
1. Type the word/ phrase in filter.
2. Model element(s) matching the word/ phrase you typed will be shown in the grid subsequently.
Finding
1. Click Find button.
2. Type the word/ phrase in Search Text and then check either Name or Documentation (or both) . Check Name if you want to search the name
model elements matches the word/ phrase you typed while check Documentation if you want to search the documentation of model elements
matches the word/ phrase you typed. Check both if you want to search the name or the documentation of model elements matches the word/
phrase you typed.
Check Name
Model element(s) matching the word/ phrase you typed will be highlighted in the grid subsequently.
Enter the name for the diagram. At the same time, a Data Model selection box appears on the top right corner of the diagram.
All model elements created on diagram will follow this Data Model setting. Only Physical Model will be able to generate SQL. Leave it as default
(Physical Model).
Drawing entity
Click Entity from diagram toolbar and drag it on the diagram pane.
Create entity
Rename an entity
Create column
The column can be set with primary key by right clicking the column and selecting Include in primary key from the pop-up menu.
Drawing relationships
Point on the entity and either click or drag its resource icon to create another entity.
Create relationship
As a result, a new entity is created with foreign key column(s), referencing the original entity's primary key column(s).
Rename relationship
Follow the same steps to create other entities and relationship until the diagram looks like the picture below.
Complete ERD
Many-to-Many relationship will auto convert to two One-to-Many relationships and a join table. The primary key both tables will be used to create
foreign key columns in join table as composite primary key.
Now, when you create an entity on the diagram, the entity will be under the default schema.
NOTE: In order to move entities in a diagram to a schema, define default schema on the owning entity relationship diagram, right click on the
diagram and select Apply Default Schema from the pop-up menu. This will make all entities that have master view on the erd to share
the schema defined.
Create sequence
Rename sequence
Right click on the sequence and select Open Specification... from the pop-up menu. In Sequence Specification dialog box, specify sequence
attributes.
When using Object-Relational Mapping feature, the primary key value will be inserted automatically from the sequence.
Specify the name for the newly created stored procedures and press Enter.
Rename
procedure shape
NOTE: Procedure shape is a virtual container to group a set of stored procedures. It is not a stored procedure.
Creating procedure
Right click on the stored procedures and select New Procedure from the pop-up menu, or press Alt+Shift+P.
After the new procedure is created, right click on it and select Open Specification... from the pop-up menu. In Procedure Specification dialog box,
specify the create statement and create parameters if necessary.
3. If you want to duplicate the procedures, press on the Ctrl key and release the mouse button. If you want to move them from source to target
procedure container, just release the mouse button.
After specify the name for the newly created resultset, press Enter.
The way of creating resultset column is the same as creating entity column.
After specify the name for the newly created triggers, press Enter.
3. If you want to duplicate the triggers, press on the Ctrl key and release the mouse button. If you want to move them from source to target trigger
container, just release the mouse button.
ID Generator Description
assigned lets the application to assign an identifier to the object before is called.
hilo uses a hi/lo algorithm to efficiently generate identifiers of type , or , given a table and column as a source of hi values. The
hi/lo algorithm generates identifiers that are unique only for a particular database.
identity supports identity columns in DB2, MySQL, MS SQL Server, Sybase and HypersonicSQL. The returned identifier is of type ,
or .
increment generates identifiers of type , or that are unique only when no other process is inserting data into the same table. Do not
use in a cluster.
native (default) picks , or depending upon the capabilities of the underlying database.
seqhilo uses a hi/lo algorithm to efficiently generate identifiers of type , or , given a named database sequence.
sequence uses a sequence in DB2, PostgreSQL, Oracle. The returned identifier is of type , or
An ID generator class
2. Rigth click on the primary key column that you want to select an ID generator for and select Open Specification... from the pop-up menu.
3. In the Column Specification dialog box, select the class in the ID Generator.
4. Click OK to confirm.
Creating view
Naming a view
To create a column in view, right click on the view and select New Column from the pop-up menu, or press Alt+Shift+C.
Create column
Column created
ERD
2. Right click on the diagram's background and select Synchronize to Class Diagram from the pop-up menu.
4. If there are new ERD model elements created since last synchronize, a Synchronize to Class Diagram dialog box will show for you to rename
the generated model elements. Click OK button after finish renaming.
2. Click on the diagram to name it as Supplier, create attributes and association as follow.
Create attribute
4. Right click on diagram, select Synchronize to Entity Relationship Diagram from the popup menu.
Synchronized ERD
2. Select Diagramming from the list on the left and open ERD & ORM tab.
6. Create a relationship from the target entity to the newly created entity. As you can see, a foreign key column named is created automatically.
Creating pool
To create pool, click Horizontal Pool on the diagram toolbar and then click on the diagram.
Create pool
Create lane
Creating task
To create task from a start event, click on the Sequence Flow -> Task resource beside it and drag.
Create task
Drag from the source shape, move the mouse over the target shape and then release the mouse button to create the message flow.
Click OK button to accept the correction. The sequence flow is changed to message flow automatically.
Creating gateway
To create gateway from a task, click on the Sequence/Message Flow -> Gateway resource beside it and drag.
Create gateway
Move the mouse to where you want to place the shape to and then release the mouse button. An intermediate event is created and connected to the
task with a sequence flow.
Move the mouse to where you want to place the shape to and then release the mouse button. A text annotation is created and connected to the task
with an association.
Sweeper
Click the Split with Shape resource beside the sequence flow.
Completed diagram
Define format of ID
Option Description
Num of digits The number of digits of the number. For example, when digit is 3, ID "1" will become "001"
Show ID Whether or not to show ID on diagram, and whether to show it as label that attach to a shape, or as text below caption
option
Showing ID on diagram
By default, ID is just a text property that won't appear on diagram. However, you can make it appear either near or within a shape.
Different looks of a task when ID is not shown, ID is shown as label and ID is shown below caption
To configure how to show ID (or not to show ID), you can either set the global option (refer to the previous section), or set it through diagram's option
by right clicking on the business process diagram, selecting Presentation Options >Configure Show ID Options from the popup menu.
Show ID on a diagram
If you selected to show as label, you can adjust in further the position of ID, relative to the shape (e.g. Top right of task) and the rotation.
ID assignment
There are several ways that you can assign an ID to an element, including:
• Through the specification dialog box (Right click on it and select Open Specification... from the pop-up menu)
• Through the ID label (available only when ID is shown as label on diagram)
• Through the Property Pane
Creating process
To create process from external entity, click the Data Flow -> Process resource beside it and drag.
Create process
Move the mouse to empty space of the diagram and then release the mouse button, a process will be created and connected to the external entity with
a data flow.
To edit properties of the process, right click on it and select Open Specification from the pop-up menu.
Process updated
Move the mouse to empty space of the diagram and then release the mouse button, a data store will be created and connected to the process with a
data flow.
Completed diagram
Creating event
To create event, click Event on the diagram toolbar and then click on the diagram.
Create event
Event created
Creating function
To create function from event, click the Control Flow -> Function resource beside it and drag .
Create function
Move the mouse to empty space of the diagram and then release the mouse button, a function will be created and connected to the event with a
control flow.
Create operator
Move the mouse to empty space of the diagram and then release the mouse button, an operator will be created and connected to the function with a
control flow.
Move the mouse to empty space of the diagram and then release the mouse button, a process path will be created and connected to the event with a
control flow.
An information resource will be created. To connect the information resource with a function using information flow, click the Information Flow ->
Function resource and drag.
Mouse over a function and then release the mouse button, an information flow will be created.
Completed diagram
Creating receive
To create receive, click Receive on the diagram toolbar and then click on the diagram.
Create receive
Receive created
Creating process
To create process from receive, click the Process Link -> Process resource beside it and drag .
Create process
Move the mouse to empty space of the diagram and then release the mouse button, a process will be created and connected to the receive with a
process link.
Process created
Create send
Move the mouse to empty space of the diagram and then release the mouse button, a send will be created and connected to the process with a
process link.
Send created
Completed diagram
Creating a subordinate
Subordinate, which is subject to the superior, is belonging to a lower rank. To create a subordinate under a superior unit:
1. Move mouse pointer on a unit and press its resource icon New Subordinate.
Create subordinate
2. Name the newly created subordinate unit and press Enter to confirm editing.
Creating a coworker
The coworker is a fellow worker of the same rank to the branch next to it. To create a coworker next to an existing unit:
Create coworker
2. Name the newly created coworker unit and press Enter to confirm editing.
NOTE: Clicking left resource icon will create coworker on the left of the unit, while clicking right resource icon will create coworker on its right.
Relocating a branch
A unit can be relocated even when it has been placed under the subordination of another unit.
1. Press on a branch you want to relocate and drag it to the preferred branch.
Moving a unit
NOTE: If you are not satisfied the relocation, press Esc to cancel the movement.
2. Right click on the diagram's background and select jPDL Diagram in the popup menu.
Generate jPDL
4. Select the folder to generate jPDL to. When generation is done, you should see the following files in the chosen folder:
• A zip file containing the deployable process archive
• gpd.xml (The graphical process definition)
• processdefinition.xml (The process definition)
• processimage.jpg (The image file of business process diagram)
Now, you can deploy the jPDL.
Key concepts
Very often, the allocation of resource is critical to the efficiency of a business process. For example, if there are more available staffs and counters, this
helps increase the efficiency of customer service. But of course, if the available staffs and counters are more than enough, those non-used resources
are wasted. With simulacian, you can determine the optimal resource allocation by evaluating the resource consumption of current process.
Duration
Duration is the time elapsed from the entering of flow object until the leaving of that flow object. It is understandably that the duration of flow object has
significant effect to the efficiency of a business process. Imagine if it takes 5 minutes to complete the process of just one payment in a supermarket,
there will accumulate a long queue waiting for paying.
Input
Input is a way of simulating a given business process. It has a name that describe the input, and an instance, which is a number that represent the
number of time the input will happen at a particular instant. If you have modeled a general order processing system, you can add an input public
holiday, with instance 100 to represent the case that in public holiday there will be 100 customers that need to undergo payment. In order to help you
improve your process, you must set input that reflect the reality. If you set 10000 as instance of input public holiday which will never happen, you will
not obtain useful information to aid in process improvement.
Simulation
Once you have specified the available and required resources, the duration of flow objects and added input(s), you can run simulation. During
simulation, diagram will be locked to avoid collision between your edit action and the simulation operation. Executing jobs are represented by a running
green gear shape, with a number indicating the number of running job, and are attached to the task where the job is being processed. Pending jobs are
represented by inverted triangles, with a number indicating the number of pending jobs.
NOTE: You can open simulacian control panel only for diagram that has selected Simulacian as diagram type. To check/edit diagram type, right
click on the background of business process diagram and select Diagram Type from the popup menu.
1 Start / Pause Click to start simulation when paused or stopped, base on the resource, duration and input settings, or to pause a simulation
when it is playing.
3 Clock Displays the time elapsed from the beginning of simulation until the current moment. It is for reflecting the duration of the
execution of business process, and is based on the selection of time scale.
4 Time scale Control the speed of simulation. For example, a selection of 10 mins scale simulates the business process in speed 10 min
per second.
6 Close Click to close the simulacian control panel. You can open it again by right clicking on the business process diagram and
selecting Show Simulacian Control Panel from the popup menu.
1 Instance When you model a business operation in business process diagram, you use pools and lanes to represent
participants and sub-participants of the process, such as Client and Receptionist. No matter how many actual
participants are there, you will still use a single pool (or lane) to represent all of them. For example, you will draw a
pool Receptionist to represent all receptionists instead of drawing 5 pools for representing the fact that there are 5
receptionists.
Here the Instance field let you set the number of instances of selected pools or lanes. If there are 5 receptionists,
enter 5 for instance of pool/lane Receptionist.
Provided that there are sufficient resources for performing jobs, the number of instances affects the performance
of process - The more instances, the more efficient. During process improvement, you can adjust the instance to
evaluate the impact of increasing or decreasing the number of staff to handle certain job.
2 Show inputs Inputs are the expected way of executing a business process during simulacian. Click Show Inputs to list the inputs,
and add/remove inputs in further.
3 Available resources The table of available resources list the resources needed by the business process. For example, a process of body
checking has resources X-Ray room and reception counter. Each resource has a name, a type and its amount.
4 Add available resource Click to add an available resource by giving its name, selecting/entering its type and setting its amount.
5 Remove available Select an available resource and click this button to remove it.
resource
1 Duration The time the selected flow object need to take to process and complete a job. The 4 boxes d, h, m and s mean day,
hour, minute and second, respectively. For example, it takes five 5 minutes to present a report to client in a body
check operation, set the business task Present Report's duration to be 5 m, meaning 5 minutes.
The duration setting affects the performance of process - The less time needed, the more efficient. However, do not
forget that the less time it takes to complete a task may affects the quality of work. During process improvement, you
need to keep the balance between efficiency and quality of work, and adjust the duration accordingly.
2 Show inputs Inputs are the expected way of executing a business process during simulacian. Click Show Inputs to list the inputs,
and add/remove inputs in further.
3 Required resources The resources the participant needed in order to complete a job when processing the selected flow object. The
Resource column shows the names of resources. The Amount column shows the number of resource needed to
use in completing the task per participant. For example, to present report to client, you need one resource Meeting
Room, and one resource Projector.
4 Add required resource Click to add the resource the participant needed in order to complete a job when processing the selected flow object.
Make sure you have available resources defined in order to select a required resource. Also note that you cannot
set an amount that exceed the amount set in available resource. For example, if you have 6 available projector
(resource), the maximum of projector a flow object can require is from 0 to 6.
5 Remove required Select a required resource and click this button to remove it.
resource
6 Available resources The table of available resources list the resources needed by the business process. For example, a process of body
checking has resources X-Ray room and reception counter. Each resource has a name, a type and its amount.
7 Add available resource Click to add an available resource by giving its name, selecting/entering its type and setting its amount.
8 Remove available Select an available resource and click this button to remove it.
resource
An overview of simulacian control panel while selected diagram background or showing inputs
1 Inputs Inputs are the definitions of how to execute a business process during simulation. An input consists of a selection
of possible execution path formed by flow objects in diagram, with the number of instances, which represents the
number of time the path will be executed at a specific instant.
For example, if you want to simulate the case that there are 10 clients needed to perform body checking in a
business process of body checking, to see if the process can handle this situation well, you will add an input
Performing body check, with 10 as number of instances.
2 Add input Click this button to add an input with name and number of instances.
3 Remove input Select an input and click this button to remove it.
4 Path The flow objects involved in an input. If there is a gateway in your diagram, you need to make a decision to the
outgoing path of the gateway object.
5 Highlight in diagram Check this button to make the diagram highlight the path involved in the input selected in Inputs table.
7 Add available resource Click to add an available resource by giving its name, selecting/entering its type and setting its amount.
8 Remove available Select an available resource and click this button to remove it.
resource
Description of simulacian control panel while selected diagram background or showing inputs
When simulating
3 Clock Displays the time elapsed from the beginning of simulation until the current moment. It is for reflecting the duration of the execution of
business process, and is based on the selection of time scale.
4 Inputs A list of inputs with their completeness throughout the simulation. The Processing column shows the jobs under processing by the
simulating process. The Instances column shows the amount of non-completed jobs. It should keep decreasing, and become 0 at the
end of simulation.
5 ResourcesA list of resources with the status of consumption throughout the simulation. The Processing column shows the amount of resources
be consumed by the simulating process. The Instances column shows the total amount of resources. You can observe this table to
study the current resource allocation.
6 Results A list of completed inputs. The Instances column shows the amount of completed inputs.
2. In the Simulacian Control Panel, click Add under Available resources to define the resources that can be used by the flow objects in the
business process diagram in order to complete the tasks. If you want to know more about resources, please refer to the chapter What is
simulacian?.
3. For each of the flow objects, select it in diagram, and click Add under Required Resources in Simulacian Control Panel to add the
resource(s) the participant needed to complete the job when reaching the selected flow object.
5. For each lane and pool (without lane), select it in diagram, and set its instance in Simulacian Control Panel, which represents the number of
participants that take part in the process.
6. Click on the background of diagram or click Show Inputs in Simulacian Control Panel.
7. Click Add under Inputs in Simulacian Control Panel to add the paths to be executed during simulation. For each input, set the name that
describe the path, and the number of instances for the number of copies of the path to execute.
To add input
Start simulation
Now, you can watch the simulation in diagram, to see the executions of inputs and identify bottlenecks.
Simulation is running
Completion chart
The completion chart primarily shows the status of inputs completion against time.
4 Auto refresh Check to let the chart body auto update against chart settings such as time scale and selection of inputs. Uncheck to
update manually by clicking Refresh.
5 Refresh Click to update the chart body against the chart settings such as time scale and selection of inputs. This button is
available only when Auto Refresh is unchecked.
6 Not yet started inputs Check or uncheck the inputs to show or hide in chart the change of the amount of not-yet-started inputs throughout
simulation.
7 Processing inputs Check or uncheck the inputs to show or hide in chart the change of the amount of processing inputs throughout
simulation.
8 Completed inputs Check or uncheck the inputs to show or hide in chart the change of the amount of completed inputs throughout
simulation.
10 Export Click to export the opening chart to Microsoft Excel or image file.
11 OK Click to close the simulacian charts window and go back to the diagram.
5 Auto refresh Check to let the chart body auto update against chart settings such as whether to show by resource or resource type, time scale
and selection of resources and resources type. Uncheck to update manually by clicking Refresh.
6 Refresh Click to update the chart body against the chart settings such as whether to show by resource or resource type, time scale and
selection of resources and resources type. This button is available only when Auto Refresh is unchecked.
7 Resources Check or uncheck the resources to show or hide their usage in chart. This pane is active only when Resource is selected in the
drop down menu Show By.
8 Resource Check or uncheck the resource types to show or hide their usage in chart. This pane is active only when Resource Type is
types selected in the drop down menu Show By.
10 Export Click to export the opening chart to Microsoft Excel or image file.
11 OK Click to close the simulacian charts window and go back to the diagram.
4 Auto refresh Check to let the chart body auto update against chart settings such as time scale and selection of nodes. Uncheck to update
manually by clicking Refresh.
5 Refresh Click to update the chart body against the chart settings such as time scale and selection of nodes. This button is available only
when Auto Refresh is unchecked.
6 Nodes Check or uncheck flow objects nodes to show or hide their queue time in chart.
8 Export Click to export the opening chart to Microsoft Excel or image file.
9 OK Click to close the simulacian charts window and go back to the diagram.
2. This create a mind mapping diagram with a central idea node appear in it. Immediately name the central idea node and press Enter to confirm.
You can then start drawing the diagram by branching nodes from the central idea nodes.
To create a node
A node is created
3. Name the node and press Enter to confirm. Create the other nodes by repeat the same steps.
To format nodes
3. Select either Line..., Fill... or Font... from the popup menu to change specific type of format. (Read the coming sub-sections for details about
line, fill and font settings)
Once you have confirmed your selection, your choice will be memorized. When you want to apply the settings on other nodes, you can select the new
nodes, re-open the same popup menu, and select the setting through the popup menu.
Line
Line settings control the appearance of border around node(s). You can adjust the style (e.g. dash, solid), the weight, which is the thickness of line, the
color and the level of transparency.
Fill
Fill settings control the background color of node(s). You can apply solid and gradient colors, as well as to control the transparency.
Font
Font settings control the font style, size, type and color of text appear on a node.
3.
NOTE: Unlike the usage of traditional resource icons, the Link resources must be released on an existing node. Releasing on diagram will not
result in creating a new node.
2. In the node specification, open the References tab. Right click on the center of pane and select the type of reference to add from the popup
menu.
Shape A shape in the opening project, such as a use case shape on a use case diagram.
Model element A model element in the opening project, such as a use case.
3. Supply the information of reference such as the file path of a file reference, a diagram for a diagram reference.
4. Click OK to confirm.
Once a reference has been added, you can open it from the References tab by right clicking on it and selecting Open... from the popup menu.
Diagram based
By performing a diagram based layout, all idea nodes in diagram are included in the range of layout. To perform a diagram based layout, right click on
the central idea node and select Layout Node from the popup menu.
Node based
By performing a node based layout, only the chosen node and its descendant nodes are included in the range of layout. To perform a node based
layout, right click on the idea node and select Layout Node from the popup menu.
An animating path
2. In the Filter Configuration dialog box, conditional flows, if any, are listed. Click on a drop down menu to select the expected outgoing flow of a
condition. By doing so, only paths that cover the selected flow are identified, the rest will be ignored.
Configure filter
NOTE: A condition can have more than two outgoing flows. You can allow multiple outgoing flows by pressing the ... button next to the drop
down menu, and selecting the flows in the Select Multiple Values dialog box.
you control the animation. Besides pausing, playing and stopping the animation, you can also move a shape backward or forward by pressing the
and button. By making use with the forward and backward buttons, you can walk through a path shape by shape.
Launching an animation
1. Select Tools > Animacian... from the main menu.
2. In Business Process Diagram Animacian dialog box, select a path and then click Play.
NOTE: Animacian can also be started by using any of the ways below:
• Right-click on the diagram background and select Utilities > Animacian... from the popup menu.
• Click the drop-down menu of Modeling Tools and select Animacian... on the toolbar.
6 Paths It provides two ways of producing animation for the possible paths.
Automatic: It is chosen by default. This helps you to detect all possible paths automatically.
Manual: Choose this option when you want to select the possible path(s) manually.
7 Paths list It lists all possible ways of executing a business process. By default, paths are named as Path1, Path2, and so forth.
You can rename them by double clicking on them and giving meaningful names.
8 Components list It displays all components of the selected path. Pressing on a component will highlight the first shape of the chosen
path until the chosen shape in the diagram.
9 Refresh It is used for re-identifying the paths base on filter assignment and diagram content.
10 Filter... It helps removing the non-selected paths by specifying the end result of fork nodes.
11 Filter invisible shapes A shape can be set invisible on a diagram, or become invisible due to belonging to an invisible layer. By checking this
option, invisible shapes will be ignored when calculating paths. By unchecking, invisible path will be included when
calculating paths. By unchecking, you will see a black ball fly on diagram without attaching to the invisible shape(s)
when executing a path.
12 Flow It provides three options for viewing the possible paths in Paths list.
All Flow: Make a path continue when reaching sequence and message flow.
Sequence Flow Only: Ignore message flows on diagram. When a path reaches a message flow, end the path.
Message Flow Only: Ignore sequence flows on diagram. When a path reaches a message flow, end the path.
13 Export to Flash... Select an output path for exporting this diagram's animation to Adobe Flash.
16 Advanced Options... It provides the color and speed options for animation.
18 Cancel Click this button to close Animacian without saving the editing.
Advanced options
Name Description
Visited error fill color The background color of visited shape that cause an error. An error means the flow object that causes a
path invalid.
Active shape initial fill color When playing an animation, a tiny black ball will traverse the chosen path, from one shape to another.
When it reaches a shape, the shape will render with a transition effect that means transiting from an initial
color to visited fill color. This option manages the initial background color for visiting shape.
Ball color The color of ball that goes through a path during animation for indicating the progress of flow.
Flash progress bar background color 1 The background color for the top of progress bar in exported Flash movie.
Flash progress bar background color 2 The background color for the bottom of progress bar in exported Flash movie.
Reviewing an animation
1. When everything is ready, click Play to start the animation of the selected path.
2. After click Play, Business Process Diagram Animacian dialog box will be minimized to the bottom of your diagram, with several buttons and a
slider revealing on it.
Button Name Description
MaximizeMaximize Animacian.
3. When the animation starts, a black ball will appear at beginning of path and traverse through the path until the end.
Launching an animation
1. Select Tools > Animacian... from the main menu.
2. In Sequence Diagram Animacian dialog box, select a path and then click Play.
NOTE: Animacian can also be started by using any of the ways below:
• Right-click on the diagram background and select Utilities > Animacian... from the popup menu.
• Click the drop-down menu of Modeling Tools and select Animacian... on the toolbar.
6 Paths It provides two ways of producing animation for the possible paths.
Automatic: It is chosen by default. This helps you to detect all possible paths automatically.
Manual: Choose when you want to select the possible path(s) manually.
7 Paths list It lists all possible ways of executing a sequence. By default, paths are named as Path1, Path2, and so forth. You can
rename them by double clicking on them and giving meaningful names.
8 Components list It displays all components of the selected path. Pressing on a component will highlight the first shape of the chosen
path until the chosen shape in the diagram.
9 Refresh It is used for re-identifying the paths base on filter assignment and diagram content.
10 Filter... It helps removing the non-selected paths by specifying the end result of fork nodes.
11 Filter invisible shapes A shape can be set invisible on a diagram, or become invisible due to belonging to an invisible layer. By checking this
option, invisible shapes will be ignored when calculating paths. By unchecking, invisible path will be included when
calculating paths. By unchecking, you will see a black ball fly on diagram without attaching to the invisible shape(s)
when executing a path.
12 Export to Flash... Select an output path for exporting this diagram's animation to Adobe Flash.
15 Advanced Options... It provides the color and speed options for animation.
17 Cancel Click this button to close Animacian without saving the editing.
Advanced options
Name Description
Visited error fill color The background color of visited shape that cause an error. An error means the flow object that causes a
path invalid.
Active shape initial fill color When playing an animation, a tiny black ball will traverse the chosen path, from one shape to another.
When it reaches a shape, the shape will render with a transition effect that means transiting from an initial
color to visited fill color. This option manages the initial background color for visiting shape.
Ball color The color of ball that goes through a path during animation for indicating the progress of flow.
Flash progress bar background color 1 The background color for the top of progress bar in exported Flash movie.
Flash Progress Bar background color 2 The background color for the bottom of progress bar in exported Flash movie.
Naming a path
The Paths list displays all possible animation paths of your diagram. Each path represents a possible way to go through the diagram. By default, paths
are named as Path1, Path2, and so forth. It is recommended to name to the path(s) for better clarification.
Reviewing an animation
1. When everything is ready, click Play to start the animation of the selected path.
2. After click Play, Sequence Diagram Animacian dialog box will be minimized to the bottom of your diagram, with several buttons and a slider
revealing on it.
Button Name Description
MaximizeMaximize Animacian.
3. When the animation starts, a black ball will appear at beginning of path and traverse through the path until the end.
2. In Activity Diagram Animacian dialog box, select a path and then click Play.
NOTE: Animacian can also be started by using any of the ways below:
• Right-click on the diagram background and select Utilities > Animacian... from the popup menu.
• Click the drop-down menu of Modeling Tools and select Animacian... on the toolbar.
6 Paths It provides two ways of producing animation for the possible paths.
Automatic: It is chosen by default. This helps you to detect all possible paths automatically.
Manual: Choose when you want to select the possible path(s) manually.
7 Paths list It lists all possible ways of executing an Activity. By default, paths are named as Path1, Path2, and so forth. You can
rename them by double clicking on them and giving meaningful names.
8 Components list It displays all components of the selected path. Pressing on a component will highlight the first shape of the chosen
path until the chosen shape in the diagram.
9 Refresh It is used for re-identifying the paths base on filter assignment and diagram content.
10 Filter... It helps removing the non-selected paths by specifying the end result of fork nodes.
11 Filter invisible shapes A shape can be set invisible on a diagram, or become invisible due to belonging to an invisible layer. By checking this
option, invisible shapes will be ignored when calculating paths. By unchecking, invisible path will be included when
calculating paths. By unchecking, you will see a black ball fly on diagram without attaching to the invisible shape(s)
when executing a path.
12 Export to Flash... Select an output path for exporting this diagram's animation to Adobe Flash.
15 Advanced Options... It provides the color and speed options for animation.
17 Cancel Click this button to close Animacian without saving the editing.
Advanced options
Name Description
Visited error fill color The background color of visited shape that cause an error. An error means the flow object that causes a
path invalid.
Active shape initial fill color When playing an animation, a tiny black ball will traverse the chosen path, from one shape to another.
When it reaches a shape, the shape will render with a transition effect that means transiting from an initial
color to visited fill color. This option manages the initial background color for visiting shape.
Ball color The color of ball that goes through a path during animation for indicating the progress of flow.
Flash progress bar background color 1 The background color for the top of progress bar in exported Flash movie.
Flash progress bar background color 2 The background color for the bottom of progress bar in exported Flash movie.
Naming a path
The Paths list displays all possible animation paths of your diagram. Each path represents a possible way to go through the diagram. By default, paths
are named as Path1, Path2, and so forth. It is recommended to name to the path(s) for better clarification.
Reviewing an animation
1. When everything is ready, click Play to start the animation of the selected path.
2. After click Play, Activity Diagram Animacian dialog box will be minimized to the bottom of your diagram, with several buttons and a slider
revealing on it.
Button Name Description
MaximizeMaximize Animacian.
3. When the animation starts, a black ball will appear at beginning of path and traverse through the path until the end.
The Business Process Diagram Animacian dialog box pops out. You can select an execution path to play an animation in the dialog box.
2. From the Paths list, select the execution paths to export as Flash movie.
Path The path of the exported HTML file. Flash movie file (.swf) will also be exported to the same folder as the HTML file.
Launch When checked, default web browser will automatically start and play the exported Flash movie.
Viewer
Available Available paths that can be selected to export to Flash movie for animation.
4. An HTML web page will be exported. Specify the path of the HTML file. Note that the Flash movie files (.swf) will be exported to the same folder
as the HTML file.
5. Choose or enter the dimension of movie if necessary. Note that the dimension determins the size of viewable region instead of the size of
diagram.
Animation is playing
8. If there are more then one path being selected, you can click on the drop down menu at top right corner and select another path to play with.
Button Description
Pause. Temporary stop playing the movie. Can play again by pressing the
button.
You can also click on the slider to move the animation to a desired position.
3. In the Open dialog box, choose the Agilian project file (*.vpp) to reference to and click Open.
4. When you return the Manage Dependent Projects dialog box, click Close button.
NOTE: By selecting the first selection (Current), model elements in the current project will be listed.
2. In the model element list, drag the target model element(s) and drop it/ them on diagram. This creates views from them. In addition, you may
continue modeling with the referenced elements. Note that Views for dependent project are read-only (i.e. non edit-able).
NOTE: Alternatively, you can right click on the model elements and select Create View in Active Diagram from the pop-up menu.
After that, you can see the indicator, which is a small arrow, appear at the shapes that are referencing a dependent project.
By doing so, you can use it in your project and add shapes in it. If you have already created a view for a non-mirrored element and you want to create a
mirror, you may right click on the shape and select Convert to Mirror from pop-up menu.
The duplicated element can be found in Model Explorer, under current project.
Original name
After you define a nickname and rename model element, the diagram will be switched to the selected nickname.
Select a nickname
You can create a French nickname and rename the model elements:
Now you can switch between English (Original) and Traditional Chinese anytime, or even creating more nicknames.
1 Original user The language (e.g. English) of the Original nickname The selection only affects the outcome of translation.
language
7 Export Click to export an XML file that contains information about the original name and nickname of the name and
documentation of model elements that are named differently in nickname.
8 Import Click to import the XML exported from Configure Nickname dialog box.
9 OK Click to apply the nickname configuration and close this dialog box.
10 Cancel Click to close the dialog box without applying the changes.
Adding nickname
Configure Nicknames
NOTE: If you do not see this drop down menu, it could be due to the toolbar is being turned off. You can show it by right clicking on the empty
space on the toolbar and selecting Nickname from popup menu, or simply, access the same function by selecting View > Nicknames >
Configure Nicknames... from the main menu.
2. The current working copy is by default in Original nickname, with English as user language. Click Add in the Configure Nickname dialog box.
3. In the Input dialog box, enter the name of the nickname set and click OK to confirm. Click OK to close the Configure Nickname dialog box.
Renaming nickname
Configure Nicknames
NOTE: This is If you do not see this drop down menu, it could be due to the toolbar is being turned off. You can show it by right clicking on
the empty space on the toolbar and selecting Nickname from popup menu, or simply, access the same function by selecting View >
Nicknames > Configure Nicknames... from the main menu.
2. In the Configure Nickname dialog box, select the nickname to rename. Click Rename.
3. In the Input dialog box, enter the name of the nickname set and click OK to confirm. Click OK to close the Configure Nickname dialog box.
Removing nickname
1. Click on the drop down menu of Modeling Tools on the toolbar and select Nicknames > Configure Nicknames....
Configure Nicknames
NOTE: This is If you do not see this drop down menu, it could be due to the toolbar is being turned off. You can show it by right clicking on
the empty space on the toolbar and selecting Nickname from popup menu, or simply, access the same function by selecting View >
Nicknames > Configure Nicknames... from the main menu.
2. In the Configure Nickname dialog box, select the nickname to remove. Click Remove. Click Yes when you are asked for confirmation
To add a nickname in specific language, click on the Add User Language... button and select a language.
2. Start renaming model elements and updating their documentation. The changes you make will only be applied to the selected nickname.
Switch nickname
NOTE: Make sure you are working under a nickname in order to see the Translate menu.
Translation P. 405
2. In the Translate dialog box, the left hand side displays the name and documentation of the chosen shape in the language set for original
nickname, which is English by default, while the right hand side displays name and documentation in the language of the active nickname.
Translation outcome
3. Review and make necessary correction to the translated outcome. You can change to translate to another language by selecting a different
language from the drop down menu at the bottom right corner of dialog box, and then click the Translate button. Click OK button to proceed
with translation.
Translation P. 406
What is visual diff?
The situation of comparing two diagrams is common. For example, comparing an ERD of conceptual model with an ERD of physical model and
comparing a domain class diagram with a class diagram ready for implementation. VP-UML allows you to compare the differences between diagrams
in order to trace the changes between them.
Diagram comparison
With the feature of Visual Diff, two diagrams can be compared to recognize their differences. Changes, such as modification of properties (e.g. name)
and addition/removal of containing models, thereby can be found easily.
Strategy Description
ID Shapes will be matched base on their internal ID. Differences between shapes that have same ID will be displayed in the result pane. This
strategy is usually used to visualize the changes of same shapes in two projects.
Name Shapes will be matched base on their names. This strategy is useful when visualizing differences for external works. One of typical
examples is to compare databases and class models.
Transitor Shapes will be matched base on their transition established by Model Transitor. This way of comparison is usually used to visualize the
differences between model elements.
Compare All
Compare View
3. Select the To-be Process diagram to compare with from the drop-down menu of Diagram.
The two diagrams are shown side by side on display pane. However, the ways of comparison has not yet been configured. Let's configure them
one by one in the following steps.
Select a strategy
Select a compare
Choose a base
Select a filter
8. Once everything is set, the differences of the two diagrams will be shown on the result pane.
9. If you want to view a specific shape, you may click its node on the result pane, and then the selected shape will be painted in dark purple on the
display pane.
3. Select the Physical ERD to compare with from the drop-down menu of Diagram.
Select a diagram
The two diagrams are shown side by side on display pane. However, the ways of comparison has not yet been configured. Let's configure them
one by one in the following steps.
Select a strategy
Select a compare
Select a base
Select a filter
8. Once everything is set, the differences of the two diagrams will be shown on the result pane.
9. If you want to view a specific shape, you may click its node on the result pane, and then the selected shape will be painted in dark purple on the
display pane.
3. A design pattern is needed to save as a file. In the Define Design Pattern dialog, specify the name and file name for the pattern, with .pat as
extension. You can save the pattern file to workspace for ease of sharing with other projects that will be opened in current workspace. Besides,
you can save to another directory and share the .pat file with your team member for reusing. Click OK button to finish defining design pattern.
3. In Design Pattern dialog, you can see a list of defined patterns, select Factory from the list.
Select pattern
If you have a .pat file, click Add button to import into the list.
Add pattern
Fill in values
You can also click on the shape or select a diagram element from the Diagram Element combo box to filter the list.
5. Finally, click OK button. The pattern will be applied to the diagram.
4. In the Pattern Synchronization dialog box, verify your desired design pattern and action and click OK button to continue. The pattern will be
committed to teamwork server.
Commit pattern
Update pattern
6. Open an existing diagram where you want to apply a design pattern or create a new diagram. Right click on the diagram background and select
Utilities > Apply Design Pattern... from the pop-up menu. The design pattern is available on the list of Design Pattern dialog box. You can
now select the pattern and apply to your project.
2. If you are right clicking on the source shape, select Related Elements > Transit To > Manage Transit To... from the popup menu. If you are
right clicking on the target shape, select Related Elements > Transit To > Manage Transit From... from the popup menu.
To manage transition
3. In the Manage Transit To/From Model Elements dialog box, select the shape(s) you want to transit to/from. You can select multiple shapes to
transit to/from. For example, an initial Purchase Order class will be transited to an Order class and an OrderItem class.
The second method is to make use of the resource centric interface. Here are the steps:
1. Move the mouse pointer over the shape that you want to navigate to its transited shape.
2. Press on the Model Transitor resource icon below the shape. Select Transit From/To, then the shape to navigate to.
Removing a transition
To remove a transition between shapes:
1. Right click on a shape and select Related Elements > Transit From/To > Manage Transit From/To from the popup menu.
2. In the Manage Transit To/From Model Elements dialog box, de-select the shapes that you do not want to transit with. Click OK to confirm.
2. The Select Parent Model of New Diagram dialog box appears, enabling you to select a model for storing diagram. Visual Paradigm
encourages structuring project with model for easier accessing of model elements and increasing application performance. If you want to place
the new diagram in a model, select one or click New Model button at the top right to create one and select it. If you do not want to store diagram
inside any model, do not make any model selection. Click OK button to continue.
The second method is to make use of the resource centric interface. Here are the steps:
1. Move the mouse over the shape that you want to navigate to its transited shape.
2. Press on the Model Transitor resource icon below the shape. Select Transit From/To, then the shape to navigate to.
To select a stereotype
Depending on the type of model element you are selecting, there may be a list of suggested stereotypes listing in the menu popped up. It
consists of both the recently used stereotypes and stereotypes that place at the top of stereotype list. If you see the stereotype you want to
apply, select it. Otherwise, select Stereotypes... at the bottom of the menu to look for others.
2. In the Stereotypes tab of specification dialog box, select the stereotype you want to apply, then click > to assign it to the Selected list.
NOTE: While clicking on > applies the selected stereotype to model element, you can click < to remove a stereotype selected in Selected list.
If you want to apply ALL available stereotypes to model element, click >>, and likewise, clicking on << removes all the applied
stereotypes.
3. Click OK to confirm. The stereotype will then be shown within a pair of guillemets above the name of the model element. If multiple stereotypes
are applied, the names of the applied stereotypes are shown as a comma-separated list with a pair of
guillemets.
NOTE: If you want to let a class display as traditional class shape instead of robustness analysis icons, right click on the class and de-select
Presentation Options > Display as Robustness Icon from the popup menu.
Different presentations of a model element with a stereotype that has icon defined
Configure stereotypes
2. Click on the drop down menu Scope at the top left corner of the Configure Stereotypes dialog box, select whether to configure stereotypes in
workspace or in the opening project.
NOTE: Initially, stereotypes exist in workspace rather than in project. When you apply a stereotype to any model element, a copy of that
stereotype will be made from workspace to project.
By modifying stereotype in workspace, changes will not be applied to current project nor any project that has used the stereotype
because the stereotype copied to project is being followed. If you want to configure stereotype only in current project, you must select
Project as scope, or select Workspace but let the option Apply changes to stereotypes in current project on to make changes apply
on both workspace and project.
3. Select the type of model element that you want to add stereotype or edit its existing stereotypes.
5. If you are adding or editing a stereotype, update its specification and click OK to confirm editing. For details about editing a stereotype, read the
coming section.
6. Click OK to confirm.
1 Scope Initially, stereotypes exist in workspace rather than in project. When you apply a stereotype
to any model element, a copy of that stereotype will be made from workspace to project.
By modifying stereotype in workspace, changes will not be applied to current project nor
any project that has used the stereotype because the stereotype copied to project is being
followed. If you want to configure stereotype only in current project, you must select Project
as scope, or select Workspace but let the option Apply changes to stereotypes in
current project on to make changes apply on both workspace and project.
2 Model element list A list of categorized model element types. You can select a type to configure its stereotypes.
4 Apply changes to stereotypes in current project Available only when scope is Workspace, this option cause the stereotype configuration
applies to both stereotypes in workspace and project, when pressing OK .
6 Import Click this to import stereotype configuration (an XML) produced by others. Once clicked,
the Import Stereotypes dialog box will popup. You need to choose the XML file to import.
At the bottom of the dialog box, there is an option Add and update only (do not delete
stereotypes). When checked, VP-UML will only add and update stereotypes from XML.
When unchecked, VP-UML will add and update stereotypes, and additionally delete
stereotypes that are not defined within the XML.
8 Add Click this to add a stereotype for the selected type of model element.
12 Cancel Click to discard the changes (if any) and close the dialog box.
Editing stereotype
By applying a stereotype that has icon defined to a model element, the icon above the name of model element, near the stereotype. You can optionally
make the model element show as the icon. For details, read the previous chapter. To specify icon, click on the ... button near the preview of Icon. Then,
select the image file of icon.
Fill, line and font styles will be applied automatically to model elements that have the stereotype applied. To adjust fill/line/font, check the corresponding
Use button. Then, click on the ... button to edit the settings.
Adding a tag
Text The most common and general type of tagged value that consists of words.
Enumeration The value of tag can be chosen from a list of possible values. For example, to select "red" out of values red, green
and blue.
Floating point The value of tag must be a number that consists of one or more digits.
number
Type of tags
6. You can assign a default value to a tag by editing the Default Value cell. Usually, you give a tag a default value when the value is true in most
cases. For example, a tag "in-door-temperature" can have "25" as default value.
To configure buttons
2. In the Configure Buttons dialog box, expand the node(s) of model element type(s) that you want to add shortcut for. Select the stereotype that
you need to apply to that type of model element in future. Click > or double click on it to assign. Click OK to confirm.
3. After all, you can find the shortcuts in diagram toolbar, under the selected type(s) of model elements. By selecting a stereotyped model element
type and click on diagram, you can create a shape with stereotype applied.
Creating a profile
2. Name the profile in Profile Specification and click OK to confirm. The naming should be clear enough to identify the part of the domain
you want to create a profile for. For example, a Vehicle profile for managing stereotypes around different car types; a Transaction profile for
managing stereotypes related to trading and loaning of cars.
A profile consists of domain-specific stereotypes and tagged values definition. To develop a profile, you need to create a profile diagram. For details
about how to create and draw a profile diagram, read the next chapter.
2. Name the diagram and press Enter to confirm. By default, the name of profile is applied as the name of diagram. If you attempt to create only
one profile diagram for a profile, and if your profile was well-named, you can keep using the profile name as diagram name.
Drawing a stereotype
To draw a stereotype in profile diagram:
1. Select Stereotype in diagram toolbar.
Selecting Stereotype
in diagram toolbar
NOTE: You can check Display model element types in-use to list only types of model elements used in project. The text box Filter enables you
to filter model element type base on the type name (e.g. enter class to list only class)
4. Click OK. Name the stereotype and press Enter to confirm creation.
To add a tag
Text The most common and general type of tagged value that consists of words.
Enumeration The value of tag can be chosen from a list of possible values. For example, to select "red" out of values red, green
and blue.
Floating point The value of tag must be a number that consists of one or more digits.
number
Type of tags
4. Double click the name cell and enter the name of tag. Repeat step 3 and 4 to add all tagged values for this stereotype.
5. You can assign a default value to a tag by editing the Default Value cell. Usually, you give a tag a default value when the value is true in most
cases. For example, a tag "in-door-temperature" can have "25" as default value. By confirming changes, you can see the stereotype show on
diagram, with tagged values show below the stereotype name.
Relating stereotypes
Stereotypes can be related with each other by composition or generalization. Relating stereotypes not just affect the modeling in profile, but also the
model elements that the stereotypes will be applied to.
To create a composition
2. Drag it out. Release at the position you want to create the composed stereotype. Select base class, name the stereotype and press Enter.
Since composition models a "part of" relationship, when you apply a composite stereotype to a model element, you can add tagged value defined in
composed stereotype in the model element. For example, stereotype Vehicle is composed of stereotype Wheel. If you apply stereotype Vehicle to a
class, you can specify the properties of tagged values as defined by both stereotype Vehicle and Wheel.
Generalization
A generalization relationship shows a "kind of" relationship between stereotypes.
A generalization relationship
2. Drag it out. Release at the position you want to create the specialized stereotype. Select base class, name the stereotype and press Enter.
Since generalization models a "kind of" relationship, when you apply a specialized stereotype to a model element, you can add tagged value defined
in general stereotype in the model element. For example, stereotype Vehicle is a generalized stereotype of Truck. If you apply stereotype Truck to a
class, you can specify the properties of tagged values as defined by both stereotype Vehicle and Truck.
2. When the New Diagram dialog box pops out, select a category under Categories and select a diagram type on the right-hand side. Specify the
newly created diagram's name and also the documentation.
Drawing shapes
After creating a new diagram, diagram elements can be created as well through the diagram toolbar. In this section, these techniques of drawing
shapes will be explicated:
• Creating Shapes
• Creating Connectors
• Creating Self-Connection
Creating shapes
To create a shape, click a diagram element from the diagram toolbar and click it on the diagram pane for creating. The generated element will appear
to have a default size.
For defining a specific shape size, drag a specific boundary with the mouse after clicking a diagram element from the diagram toolbar.
In addition, you can add a shape through the pop-up menu of diagram. Right click on the diagram background, select Add Shape and then a specific
shape from the pop-up menu.
Creating connectors
To create a connector, select the desired connector from the diagram toolbar, drag the connector from the source shape to the destination shape.
Since VP-UML provides a continuous UML syntax checking, if you create an invalid connection, a stop sign will be pop-out. For instance, you are not
allowed to connect an actor and a use case with a generalization relationship.
If the connection is valid, a blue rectangle surrounding the destination shape can be seen.
If you release the mouse on an empty space, a new shape will be created with a connector.
Creating self-connection
Some shapes can make a connection for itself, for example, Self-Association of a Class in class diagram and Self-Link of an Object in
communication Diagram. To create a self-connection, select the connector from the diagram toolbar and then click on the target shape. Alternatively,
you can press the target shape's resource icon directly.
Self-Connection is created
You can also create a turning point when creating a creator through the resource centric interface. When dragging out a resource-icon, press the Shift
button at where you want to create the turning point.
If you try to create connector by clicking on a resource icon, click at where you want to create a turning point to create it.
Connection resource
It is designed for creating elements and making connections.
Manipulation resource
You can use Manipulation Resource to modify properties or appearance of elements. For example, you can show or hide compartments, add
references, add sub-diagram and fit size.
Branching resource
Branching Resource helps you to create decision structure in diagram.
Pencil
Word Art
After entering the name of parent package, you will find that the diagram name is the same as the name of parent package.
The diagram name can be renamed. However, the name of parent package won't be changed following with the diagram name.
You can open specification of parent package by pressing the Open Specification button on the right-hand side of the parent package name.
Open Specification
You can rename the parent package of the diagram by double clicking on it.
A new package will be created if you enter a completely new package name. If the previous parent package does not contain elements, it will be
deleted. That means the documentation (or other properties) of previous parent package will be lost.
2. As a result, all shapes' name in the whole diagram will turn into the alignment option you set previously.
Apart from the whole diagram setting, a specific shape can also be set:
2. As a result, the specific shape will turn into the alignment option you set previously.
In addition to the current diagram, future diagrams can also be set:
1. Select Tools > Options... from the main menu.
2. In the Options dialog box, select the Diagramming category, check an option out of Model Element Name Alignment section under the
Appearance tab.
On the other hand, the names of container shapes are not available for positioning. Since their “bodies” are used for containing other
shapes, thereby, they have a limited scope of displaying names. Package, State and System are example of this kind of shape.
Container shape
The minimum size of a shape can be determined by pressing its fit size button
Now, it is possible to disable such setting, so that shapes can be resized to extremely small in size, despite their minimum size:
1. To disable the function of the minimum size checking, select Tools > Options... from the main menu.
2. In the Options dialog box, select the Diagramming category and uncheck Enable minimum size under Appearance tab. Click OK to
confirm.
3. After that, you can resize a shape to the size as small as you want.
5. As a result, other shapes will turn into the same size as the shape you have done previously.
Undo
You can roll back undesirable changes by performing Undo. Undo function can be executed in the following three ways:
• Select Edit > Undo from the main menu.
•
Click the Undo button on toolbar.
• Press Ctrl-Z.
Redo
This feature is to re-perform actions that have just been undone. Redo function can be executed in the following three ways:
• Select Edit > Redo from the main menu.
•
Click the Redo button on toolbar.
On the other hand, you can also find the action name of undo/ redo on toolbar button's tooltip. Move the mouse over the Undo or Redo button and
then a tooltip with Undo/ Redo action name will appear.
NOTE: To check or uncheck the options (including Resources, Group Resources, Extra Resources and Generic Resources Only) on
resource centric interface, select View > Resource Centric from the main menu.
2. Drag the resource icon and release it until reaching to your preferred place.
3. As a result, another shape is created and linked with the previous shape.
2. Drag the resource icon and release it until reaching to another shape.
3. As a result, two shapes are linked together.
Release the mouse to create Association connecting with the Use Case
2. You can either create a new shape or select an existing shape by typing its name in the text field of Quick Connect dialog box. To select an
existing shape, enter its full name directly or just type the first letter of its name. As a result, a list of shapes which match with the word(s) you
typed will display.
3. After you click a shape's name on the drop-down list, the shape will be spotlighted on the diagram immediately.
4. Confirm the selection, press Enter. The two shapes will be linked automatically.
NOTE: You should click the resource icon in accordance with the existing shapes on your diagram. If the shape does not exist on the diagram,
the Quick Connect dialog box will not pop out even when you click the resource icon.
NOTE: Transition does apply not only on two shapes on the same diagram, but also two shapes in different diagrams.
3. After adding reference, you can click resource icon Resources again and the reference you have just created will be revealed on the pop-up
menu.
2. Drag the resource icon and release it until reaching to your preferred place.
3. As a result, two shapes and a decision node are created and connected.
3. Press the reversed triangle of Align Top and select an alignment option from the drop-down menu.
2. In Specification dialog box, select Tagged Values tab and click Add button to select an option of value type.
Add text
Multi-line Text
Multi-line Text supports multi-line string.
1. In Specification dialog box, select Tagged Values tab, click Add button and select Multi-line Text from the pop-up menu. Click the ... button
of Value.
Model Element
Model Element supports reference(s) of model element.
1. In Specification dialog box, select Tagged Values tab, click Add button and select Model Element from the pop-up menu. Click the reverse
triangle button of Value.
2. When the Select Model dialog box pops out, check Model and select a model element. Click OK button to confirm.
Integer
Integer supports values with numbers only.
Add integer
HTML
HTML is a hidden tagged value. To reveal this option, select Tools > Options... from the main menu. When the Options dialog box pops out, select
Diagramming > Environment tab and check Stereotype support HTML tagged value.
In Specification dialog box, select Tagged Values tab, click Add button > HTML Text from the pop-up menu and click ... button in Value when the
option for HTML is revealed.
When Edit Value dialog box pops out, enter the text. You can format the HTML text content with the toolbar, for example, changing the font color of
selected text and underlining selected text.
The value of stereotype can be edited, however, its name and its type cannot be edited as they are defined in stereotype.
If it is defined, the tagged values will be seen within the shape(s) on the diagram.
Correcting a word
If you type an incorrect word mistakenly, you can:
• Either re-type the word correctly or
• Right click on the wrong word and then select one out of the suggest words.
NOTE: There are a few more languages in dictionary that can be used, such as French and German.
Process Specify the part of the process where the editing element is involved. Three sub-properties for further specification. They include:
Iteraction, Phase and Discipline.
Version The stage of the editing element. For example, you may have two class diagrams for modeling the a system from design and
implementation angles respectively. The two diagrams will have version 1.0 and 2.0, to show the progress of work.
Status The status of editing element. It is particular useful for use case and BPMN activity shapes, for setting their status such as
Proposed, Planned, Tested, etc.
Difficulty How difficult it is to complete the goal as modeled by the edting element.
Author The person who created the editing element. This is particular useful in a team working environment. Once the author is known
you can contact that person in case you have questions about a part of a model.
Create date The date and time when the editing element was created. This property is a read-only property that is filled automatically to all
time elements when creation.
Last modified The date and time when the editing element was modified. This property is a read-only property that is filled automatically to all
elements when the project file is being saved .
Further to recording project management properties, you can print those properties in report, too.
2. In the Project Management Look-ups dialog box, open the tab of the property that you want to edit its look-ups.
3. If you want to rename a value, double click and re-enter its value. If you want to add a lookup value, click Add at the bottom right corner.
To add a version
Open specification
Alternatively, click the Documentation pane after select a specific model element on the diagram pane.
Documentation pane
Documentation editor
The documentation pane is where you can describe the selected model element. With the editor's toolbar, you can format the content, save as
template, reuse the existing template, add model elements and print the content.
5 Alignments Set the alignment of highlighted text to the left, the center or the right.
13 Clear formats Clear formats of the whole editor to convert the content to plain text.
Editing documentation
Saving a template
2. In the Input dialog box, enter the template name and click OK button to confirm.
Reusing a template
1. In the documentation editor, an existing template can be reused. Select a saved template from the drop-down menu of Template.
Select a template
Printing documentation
1. After clicking the Print button, the Page Setup dialog box will pop out.
Open specification
Alternatively, click the Documentation pane after select a model element on the diagram.
Documentation pane
Recording voice
1. Right click on a model element and select Open Specification... from the pop-up menu.
2. In Specification dialog box, click Record... button on the bottom left corner of dialog box.
3. In the Record Voice dialog box, click the Record button to start recording.
Start recording
NOTE: Make sure your audio input device is active before operate voice documentation.
4. Click the Stop button when you want to end the recording.
NOTE: Play the recorded voice by pressing the Play button; record again by pressing the Clear button, and rerun the previous steps.
3. In the Manage Voice dialog box, click the Add button, and choose either Embedded or Link to File.
4. If you choose Embedded, record a voice clip when the Record Voice dialog box pops out; if you choose Link to File, select an audio file when
the Open dialog box pops out.
You can change the following settings from the Formats dialog box:
• Changing shapes foreground style
• Changing shapes font style
• Changing shapes background style
Font section
After change the font color, the preview will update automatically.
Field Description
Font Select different types of font. The number of fonts depends on the fonts available in your computer.
Name
Font Select the style of font. You can select one of the 4 styles, a preview will be shown for each of the style items.
Style
Font Select the size of font. You may either click on the default sizes or enter the font size in the text fields.
Size
The Preview pane displays the selected font format.
In the Background tab, it allows you to select a solid fill color or a gradient fill color as well as define its transparency.
Field Description
Fill Style Select the fill style of the fill color. It can either be Solid (a single color) or Gradient (a fill color that is mixed by two colors).
Transparency Specify the transparency of the fill color. The greater the value, the more transparent is the shape. 0 (zero) transparency makes
the fill color completely opaque, while 100 (one hundred) transparency makes the fill color completely transparent.
You can adjust the transparency by dragging the slider, or by typing the value in the text field.
Alternatively, you can click the Opaque button to set the fill color to opaque, or click the Transparent button to set the fill
color to transparent.
Preview The Preview pane displays a rectangle that is filled with the editing fill color. The background is checked so that you can also
preview the transparency of the fill color as well.
Save as Save the current fill color as the default fill color for new shapes, click the Set as Default button.
Default
Reset to Reset the current fill color to the default fill color, click the Reset to Default button.
Default
Field Description
Color 1 You can select the first color of the gradient from the Color 1 field. To select a color click the ... button or double-click on the
color editor. A color chooser will appear for you a select a color.
Color 2 You can select the second color of the gradient from the Color 2 field. To select a color click the ... button or double-click on
the color editor. A color chooser will appear for you to select a color.
Gradient Color The Gradient Color Themes pane displays a list of pre-defined gradient color themes.
Themes To add a new color theme select Color 1 and Color 2 then click the Add to Themes... button. Please note that you must
select a combination of colors that does not already exist in the color themes.
To rename a theme click on the Rename... button or double-click on the desired theme. An input dialog will appear for you to
enter a new name.
To remove a theme select the theme and click on the Remove button, or use the Delete key instead.
Gradient Style The Gradient Style pane allows you to select the gradient style of the gradient fill color (the angle of how the gradient color is
drawn). There are sixteen pre-defined gradient styles, which are shown as toggle button in the Gradient Style pane. To select
a gradient style to use click on one of the styles.
Click OK button to confirm editing. As a result, the shape is changed into formatted style.
You can format the line style in the line section. It allows you to adjust weight (thickness), color and transparency.
Line section
Field Description
Weight Adjust the weight (thickness) of a line. The greater the value, the thicker the line. You can use the up/down button to increase/decrease
the line weight, or you can type directly into the text field. The line weight ranges from 1 to 20.
Color Specify the line color. Click on the ... button beside the Color field to select a color, either from the Default page (which shows
predefined colors) or from the Custom page (which shows a larger variety of colors, and allows you to define any custom colors).
NOTE: Only integer values can be used for line weight. If you type 2.8 in the text field, 2 will be applied instead.
TransparencySpecify the transparency of the line. The greater the value, the more transparent the line. 0 (zero) transparency makes the line
completely opaque, while 100 transparency makes the line completely transparent.
You can adjust the transparency either by dragging the slider, or by typing the value in the text field. Alternatively you can click on the
Opaque button to set the fill color to opaque, or click on the Transparent button to set the fill color to transparent.
Preview The Preview pane displays a rectangle surrounded by the line with the selected line format applied.
Adding style
To open the style dialog box, Select View > Styles... from the main menu.
In the Style dialog box, click Add... to create and edit a new style.
Style added
Applying style
Upon keeping the Style dialog box open, select a target shape on the diagram and click Apply in the Style dialog box.
Name Sample
Rectilinear
Curve
Round Oblique
Round
Rectilinear
Set Arc
Arc sample
NOTE: The line jumps options are available only when two connectors are overlapped.
Name Sample
Off
Gap
Square
Set Large
2. The line jump(s) on the current diagram will turn into the size you selected.
To customize the caption orientation option of a specify connector, select the connector, right click and select Style and Formatting > Connector
Style, and then select one out of four options under Caption Orientation.
Follow Connector Angle and Keep Text Up Right The caption of connector is aligned the diagonal
angles of both shapes, but keeps top right.
Right Click on the diagram background, select Connectors and select one out of four options under Caption Orientation from the popup menu.
Click Copier
NOTE: If you don't want the format properties to be cloned to other shapes any more, you should cancel cloning by clicking Format copier once
again.
NOTE: You can only copy format to shapes within the same diagram.
Auto layout
Selecting auto layout signifies that the most suitable layout is arranged for shapes automatically. It is the best choice for users when they have no
preference in selecting a specific layout. To apply Auto Layout to the diagram, right click on the diagram and select Layout > Auto Layout from the
pop-up menu.
Activity diagram
Communication diagram
Other diagrams
Hierarchic Layout
Organic Layout
NOTE: The size of shapes can be fixed automatically by right clicking on the diagram's background and checking Diagram Content> Auto Fit
Shapes Size.
To fit several shapes' size, select those shapes, right click on a selected shape and then select Selection > Fit Size from the pop-up menu.
Each shape will be adjusted to its fit size in accordance with its content, instead of fixing all selected shapes into the exactly same size.
All the shapes are subsequently fitted size and they will become non-sizable.
If the content of shape is changed, the shape itself will be resized automatically.
You can also check Auto Fit Size for future usage.
1. Select Tools > Options... from the main menu to unfold Options dialog box.
Handi-Selection
In some cases, the shapes are too complicated and more seriously, the whole diagram is extremely enormous that neither selecting a range of shapes
with the mouse nor clicking shapes with pressing Ctrl or Shift key are the most suitable application. It is hard to drag the mouse on the large diagram,
or is troublesome to click on many shapes. Using Handi-Selection is probably the best choice for you in this situation.
Inverse selection
Shapes can be selected inversely. Right click on a shape that you don't want to be selected and select Selection > Select Inverse from the pop-up
menu. As a result, all shapes will be selected except the shape you right clicked on previously.
Selection is inversed
2. After you switch to the destination diagram, right click on the diagram background and select either Paste View or Paste Model from the pop-up
menu. The feature of Paste view refers to present the same model element in another view under a new context. The shape is pasted without
creating model; while the feature of Paste Model refers to duplicate the shape and present it in a new view. The model will be copied and
pasted on the diagram. The new model will be named with appending a sequential number.
3. You should select a destination document (e.g. MS Word) for pasting the copied shape(s) to do further documentation. After you switch to the
destination document, right click on the desired place and select Paste from the pop-up menu.
4. As a result, your selected shape(s) will be pasted on the destination document.
Copying as XML
You can convert selected shapes into XML which contain the data of selected shapes in XML format. The XML data can then be imported into another
project.
1. Right click on the selected shapes and select Copy > Copy as XML from the pop-up menu.
2. Open a text editor and create a new text file. Paste the XML there and save it as an XML file.
3. After that, the file can be imported to another project by selecting File > Import > XML.
4. When Import XML dialog box pops out, select the xml file path. Finally, click OK button to proceed.
Copying to Diagram
1. You can also copy the selected shape(s) to either a new diagram or an existing diagram. Right-click on the selected shapes, select Copy >
Copy to Diagram... from the pop-up menu.
3. Click Copy to button. As a result, the selected shape(s) will be duplicated on the selected diagram.
Duplicating
With the feature of duplicate, shapes can be duplicated on the same diagram instantly.
1. Right click on the selected shape(s) and select Duplicate from the pop-up menu.
Drag upward
Similarly, when you drag a shape to the left or the right, two vertical lines will reveal on the both edge of the shape.
Drag upward
Similarly, when you drag a shape to the left or the right, a vertical line will reveal in the center of the shape.
3. The option for alignment guide is checked as default. The next step you need to do is to choose either Show edges or Show center for your
diagrams.
4. Uncheck Show diagram alignment guide if you do not want the assistance of alignment guide when dragging shapes.
Connector is reversed
NOTE: The function of reverse connector is not only for reverting the connector's direction, but also for repositioning the information contained
by the end of connection. For connectors like association, each end contains specific information like multiplicity, role name, visibility, etc.
Reverting connector will also swap the information.
NOTE: Connectors, such as create message in sequence diagram, are not reversible.
2. Hold on the mouse and drag it on the diagram pane. As a result, the views of the selected model element(s) will be shown on diagram.
2. When Visualize Related Model Element dialog box, check the related element(s) you want to be shown with the corresponding relationship on
the diagram in Visualize. Click Visualize button to proceed.
Open specification
2. In Specification dialog box, select Comments tab and click Add... button to create a comment.
Add comment
4. As a result, the comment you entered previously is shown on Specification dialog box.
Comment is shown
Open specification
3. In Comment Specification dialog box, modify information and select OK to confirm changing.
Modify information
2. The connector is temporarily pinned. A dialog box will be shown on the top right corner of diagram to instruct you how to pin the connector.
3. Since the connector that links from shape and to shape together is temporarily pinned, either from shape or to shape is moved, the connector
between them will be unpinned.
Connector is unpinned
3. Moving either from shape or to shape will not unpin the connector.
Selected shapes
Select Edit > Align Shapes > Right from the main menu
3. For turning the non-selected shape into the last selected shape, click a shape with pressing Ctrl key.
2. Choose the placement, which is the position of caption. For some of the placement options, you can choose additionally the rotation of
placement. You can preview the changes in the preview pane.
3. Click OK to confirm.
Sweeper
The sweeper is one of the useful features for editing your diagrams. If you have ever experienced of moving the diagram elements without any tools,
you probably understand how hard it is to manage the space between the diagram elements. Using sweeper to extend the space between the diagram
elements allows you to move your diagram elements conveniently.
You can move the diagram elements by following the simple steps below:
1. Click Sweeper button from the diagram toolbar.
Click Sweeper
2. Move the mouse on the diagram pane where you would like to move diagram elements.
3. Hold onto your mouse and move the line horizontally or vertically.
Magnet
The magnet is another convenient feature for you to move your diagram elements. If you want to move a few diagram elements, you should try
magnet. Its function is to diminish the space between the diagram elements and make your diagrams much tidier for printing. The steps of applying
magnet on your diagram are shown as follows:
Click Magnet
2. Move the mouse on the diagram pane where you would like to move diagram elements.
3. Hold onto your mouse and move the line horizontally or vertically.
Drawing shapes
1. To start using a mouse gesture, press the right mouse button and drag it until finish drawing a shape.
2. When the shape is done, release the mouse. After the shape is created, the action description will be shown on top right corner of the diagram.
Class created
Creating an attribute
1. To create attribute, draw a line from the right to the left within the class. As a result, an attribute is created.
Attribute is created
2. If you draw the line until outside the class, an attribute with <<Property>> stereotype will be created.
<<Property>> is created
Creating an operation
1. To create operation, draw a line from the left to the right within the class, an operation with protected visibility is created.
Operation is created
Connecting shapes
1. Draw a line from one shape to another.
Association created
Icon Description
Layout diagram
Close Diagram
Activity diagram
Icon Description
Action
Activity
Decision Node
Initial Node/Finial Node (If there is no Initial Node, an Initial Node will be created. Else if there is no Final Node, a Final Node will be created.)
Icon Description
Action State
Sub-Activity
Swimlane
Initial State/Final State (If there is no Initial State, an Initial State will be created. Else if there is no Final State, a Final State will be created.)
Icon Description
Pool/Task
Horizontal
Lane
Vertical Lane
Class diagram
Icon Description
Sync. to ERD
Class
Package
Add attribute (Add an attribute to class. If mouse released outside the class, getter and setter property will be set to true.)
Add operation (Add an operation to class. If mouse released inside the class, visibility will be protected, otherwise it will be public.)
Communication diagram
Icon Description
Sync. To Sequence
Diagram
Lifeline
Actor
Package
Component diagram
Icon Description
Component
Instance Specification
Package
Icon Description
Class
Interface
Collaboration
Collaboration Use
Icon Description
Process
External Entity
Data Store
Deployment diagram
Icon Description
Node
Instance Specification
Package
EJB diagram
Icon Description
Entity Bean
Message-Driven
Bean
Session Bean
Package
Icon Description
Entity
Add column
Icon Description
Interaction
Decision Node
Icon Description
Node
Object diagram
Icon Description
Instance Specification
Class
Package
ORM diagram
Icon Description
Class
Entity
Package
Overview diagram
Icon Description
Diagram
Overview
Package diagram
Icon Description
Package
Sequence diagram
Icon Description
Sync. to Communication
Diagram
Lifeline
Actor
Alt
Loop
Icon Description
State
Submachine State
Initial Node/Final Node (If there is no Initial State, an Initial State will be created. Else if there is no Final State, a Final State will be created.)
Icon Description
State
Concurrent State
Initial State/Final State (If there is no Initial State, an Initial State will be created. Else if there is no Final State, a Final State will be created.)
The description of mouse gestures for state machine diagram (UML 1.x)
Timing diagram
Icon Description
Frame
Icon Description
Use Case
Actor
Package
2. Apart from jumping to element in active diagram, you can also jump to any element within the project. You may select Edit > Jump to
Element... from the main menu or press Ctrl+Shift+J to unfold Jump to dialog.
3. In Jump to dialog box, if you want all elements within project to be searched, uncheck the Active diagram only checkbox. In some cases, the
checkbox is disabled because no diagram is opened.
5. Press Down key to search for the model element's name if the list is too long. Click your preferred model element's name and it will be spot-
lighted on the active diagram.
Shape is spot-lighted
Jumping to diagram
2. Jump to dialog box is shown with selected Diagram in combo box. It means Jump to dialog box will search all diagrams within the project.
3. Enter a word out of the whole diagram's name will show a list of diagrams' names similar with the word you typed . Select the diagram and press
Enter will open the diagram.
3. When you move a shape, other shapes within the same group will also be moved.
Click Ungroup
NOTE: To hide a shape will also make the connectors that attached to it hidden.
NOTE: To hide a container shape (e.g. package) will also make the contained shapes hidden.
NOTE: If a shape is selected from Show list, the related shape(s) of the selected shape will be also removed to Hide list
Creating a layer
1. Right click on the diagram background and select Layers... from the pop-up menu.
2. In Diagram Layers dialog box, click Create new layer button to create a new layer.
Layer P. 585
3. Finally, define the name for the newly created layer.
As a result, the shape you selected will be sent to the new layer.
Layer P. 586
Hiding shapes on a layer
In Diagram Layers dialog box, you can make a layer invisible on diagram. To do so, uncheck Visible of the layer.
Layer P. 587
Selecting shapes on a layer
You can also select all shapes of the selected layer. To do so, click Select shapes in selected layers button in Diagram Layers dialog box.
Layer P. 588
Making shape non-selectable
If you find it annoying to move some shapes carelessly or select some shapes accidentally, the function of selectable/non-selectable would be your
ideal trouble-shooter. This page is going to teach you how to make shapes non-selectable or even change them back to selectable with only few clicks.
2. After the shape is non-selectable, click the shape cannot make it to be selected. Neither will the shape be selected by mouse dragging on
diagram.
3. Therefore, the non-selectable shape(s) will not be moved when other shapes are moved.
Select Selectable
After it is locked, the diagram toolbar is disabled subsequently. As a result, no shapes can be selected and the diagram becomes read-only. As you
can see the Diagram Locked dialog box is shown at the bottom left of the diagram, however, close this dialog box will not unlock the diagram.
Diagram is locked
Alternatively, you can right click on the diagram background and select Diagram Content > Lock Diagram from the pop-up menu.
Alternatively, you may copy and paste the selected model element(s) as view in destination diagram. Right click on the selected model element(s) in
the source diagram and select Copy > Copy with VP-UML from the pop-up menu.
When you switch to the destination diagram, right click on the preferred place that you want the copied model element(s) to be pasted on and select
Paste View from the pop-up menu.
NOTE: Choosing Paste Model means a new model element will be created and shown on the destination diagram.
The relationship between the model elements may not be shown on diagram. If you want their relationship to be revealed, right click on the model
element, select Related Elements > Visualize Related Model Element... from the pop-up menu.
When the Visualize Related Model Element dialog box pops out, check a relationship for the model element(s) and then click the Visualize button to
proceed.
Relationship is visualized
NOTE: If the shape you right click on is already the master view, the option of Set as Master View won't be shown on the pop-up menu.
As a result, an empty overview diagram is created. Create overviews of diagrams and relate them to illustrate their relationship with each other.
The new diagram will be opened subsequently. Enter a name for new diagram and start working on it.
If you go back to the overview diagram, the preview of newly created diagram can be seen. If you realize that the diagram in diagram overview is too
small and vague for previewing, you may resize the diagram overview by dragging its bottom right corner.
2. Right click on the diagram overview and select Associate to Diagram... from the pop-up menu.
4. As a result, the selected diagram will be shown on diagram overview. If you realize that the diagram in diagram overview is too small and vague
for previewing, you may resize the diagram overview by dragging its bottom right corner.
Visualizing sub-diagram
When a diagram overview you created has a sub-diagram, you can connect them together and make them shown on the current overview diagram.
Move the mouse over a diagram overview and click its resource icon Visualize Related Diagrams.
3. Release the mouse. The shape is connected with the newly created note.
Note created
Start editing
Resizing
3. The pointer can be adjusted to point out a more specific position, such as pointing to the name of diagram element, or a specific class member
(attribute/operation) out of a class.
NOTE: You can not only adjust the pointer's direction, but also its length.
NOTE: The callout shape will be moved but the position of its pointer won't be changed if you only drag the + icon. This helps you to remain the
pointing and move the callout shape simultaneously.
Pencil
Pen
Calligraphic Tool
Connector
Line
Label Line
Path Rectangle
Rectangle
Round Rectangle 2
Diamond
Parallelogram
Trapezoid
Isosceles
Trapezoid
Path Ellipse
Ellipse
Arc
Chord
Pie
Regular Polygon
Hexagon
Arrow
Spiral
Text
Word Art
NOTE: Freehand can be switched on by clicking on diagram toolbar and select Category > Freehand from the pop-up menu.
2. Release the mouse and new freehand shape will then be created.
2. To create a curve, press and move the mouse. The indication line will appear. Release the mouse button when finishing editing. On the other
hand, the last stroke can be cancelled by right clicking on the diagram.
Creating curve
3. To confirm editing of the freehand shape, double click on diagram and a new freehand shape will be created. If the point returns to the starting
point, it will form a closed path.
A close path
2. By combining several other calligraphic shapes, you can create a complete diagram.
Calligraphy example
Connecting shapes
2. Release the mouse and a new connector will be created between them.
A line is created
A curve connector
Splitting line
Line created
2. Press on the straight line. Drag it to bend into your preferred direction.
Splitting line
3. Double click on the line. Enter the name for the line.
4. Press Enter to confirm editing.
Label Line
5. You may drag the yellow selector to modify the line's outline.
Drawing rectangle
Click on the diagram to create a rectangle.
Drawing diamond
Click on the diagram to create a diamond shape.
Drawing parallelogram
Click on the diagram to create a parallelogram shape.
Drawing trapezoid
1. Click on the diagram to create a trapezoid shape.
Drawing ellipse
Click on the diagram to create an ellipse shape.
Drawing arc
1. Click on the diagram to create an arc shape.
Drawing chord
1. Click on the diagram to create a chord shape.
2. You can extend the arc of chord by dragging on the fine editing selectors in yellow.
Drawing pie
1. Click on the diagram to create a pie shape.
2. You can extend the arc of pie by dragging on the fine editing selectors in yellow.
Drawing hexagon
Click on the diagram to create a hexagon shape.
Drawing spiral
1. Click on the diagram to create a spiral shape.
Inserting text
1. Click on the diagram to create a text shape, and input the text. You can press Enter to insert line break.
2. When the specification dialog box pops out, enter the referenced file path or select the file path by clicking ... button. You may also enter the
description for the file in Description.
3. When Select Directory dialog box pops out, select a folder to be referenced and click OK button.
4. You may enter the description for the folder. Finally, click OK button to confirm the creation for folder.
2. When the specification dialog box pops out, enter the URL path. You may also enter the URL name and the description for the URL.
Editing references
1. Move the mouse over a shape and press it resource icon References and select Edit References... from the pop-up menu.
2. When the specification dialog box pops out, double click on the row of reference you want to enter its description or modify it.
3. Enter the description or modify it under Description column.
Removing a reference
1. Move the mouse over a shape which has references, click its resource icon References and select Edit References... from the pop-up menu.
2. When the specification dialog box pops out, select a reference to be removed on the list and press Remove button to delete the selected
reference.
Reference to diagrams
1. Move the mouse over a shape, press its resource icon References and select Edit References... from the pop-up menu.
2. When the specification dialog box pops up, click Add Diagram... button.
3. In Select Diagram dialog box, check an existing diagram or create a new diagram by clicking the icon under Diagrams.
Enter description
Reference to shapes
1. Move the mouse over a shape, press its resource icon References and select Edit References... from the pop-up menu.
2. When the specification dialog box pops up, click Add Shape... button.
3. In Select Shape dialog box, check a shape to be referenced and click OK button.
Check a shape
4. Enter the description for the shape in the specification dialog box. Finally, click OK button to confirm the creation of shape.
Opening a reference
Move the mouse over a shape, press its resource icon References and select a shape/ a diagram to open from the pop-up menu. If you select a
shape to open, it will switch to the diagram where the shape belongs to and the shape will be selected by filled-selector. If you select a diagram to
open, it will switch to the selected diagram immediately.
Removing a reference
1. Move the mouse over a shape which has references, click its resource icon References and select Edit References... from the pop-up menu.
2. When the specification dialog box pops out, select a reference to be removed on the list and press Remove button to delete the selected
reference.
NOTE: Inserting a sub diagram on a model element, all child model elements of the sub diagram will also be attached.
2. In the specification dialog box, select a sub diagram that you want it to be removed from the list and click Remove button. When the Confirm
Remove dialog box pops out, click Yes button to confirm the deletion.
3. Finally, click OK button to proceed.
2. As a result, references resource icon and sub-diagrams resource icon are shown.
NOTE: The indicator of sub-diagrams and references can be hidden by clicking Always Show Reference, Sub Diagram, Model Transitor and
Documentation Resource button once again.
Shape Editor
To add a gallery
3. Enter the gallery name and press the Enter key to confirm editing.
Naming a gallery
4. To create a category, right click on a gallery and select Add Category in the popup menu.
To add a category
5. Enter the category name in the Input dialog box and click OK button to confirm.
To add a stencil
7. Enter the stencil name and press the Enter key to confirm editing.
Naming a stencil
8.
To create a shape, click on the ( New Shape) button in the bottom part of the Stencil pane to create a blank drawing for drawing the shape.
Add a shape
10. Save the drawing by selecting File > Save from the main menu.
Shapes created in Shape Editor can be used in VP-UML. For details, please refer to the next section.
Add a stencil
3. Press on a shape in the Stencil pane and drag it out of the Stencil pane and drop it on the diagram to create the shape.
4. You can also use generic connector to connect built-in notations shapes and stencil shapes. To do so, select Generic Connector in the
diagram toolbar, under the Common category.
5. Press on the source shape, hold the mouse button, move the mouse cursor to the target shape and release the mouse button.
2. In the Customize UI dialog box, select the menu(s)/toolbar button(s)/pop-up menu(s) to hide, and click on the > button to hide them.
3. Click OK button to confirm. By restarting the application, the selected user interface componenets will be hidden.
5. Click OK.
NOTE: You can reverse multiple source paths by adding them one after the other. You can add different kinds of source. For example, you can
reverse a jar as well as a folder of source file at the same time.
3. You can place reversed classes to specific model. For example, to place legacy code to a model named Old, to place system prototype to a
model named Prototype and so forth. To do this:
1. Click on the ... button at the end of the Reverse to Model row.
2. In the Select Parent Model dialog box, either select an existing model, or create one by clicking New Model.
3. Click OK to confirm.
4. By default an on-demand reverse engineering will be carried out, which means to form indexes to the added path(s) instead of actually reversing
them. For details about on demand reverse engineering, refer to the section below. If you want to carry out actual reverse engineering, uncheck
Reverse source on demand.
5. Click OK to start reversing.
6. Upon finishing, the class repository will be popped up, listing the reversed classes (or indexes of classes if you are running an on-demand
reverse engineering).
NOTE: By cancelling from forming diagram, it just means you do not want to form diagram with the reversed classes for the time being. You can
still look for the classes in Model Explorer or Class Repository, and possibly form diagram later on manually.
4 Add class folder Add a path of Java class folder for reversing.
6 Add source folder Add a path of Java source folder for reversing.
7 Set model Set the model for placing the reversed UML classes into.
8 Remove Remove selected source path(s) from the list of source paths.
9 Up Move selected source path(s) upward in the path list. It just affects the order of reversing, and have no impact on the
reversed UML classes.
10 Down Move selected source path(s) downward in the path list. It just affects the order of reversing, and have no impact on
the reversed UML classes.
11 Reverse source on By checking, this means to form indexes to the source path(s) instead of actually reversing them. For details about on
demand demand reverse engineering, refer to the section below.
12 Reverse package Analyze the sources and form package diagram when reverse. For details about reversing package diagram, refer to
diagram the section below.
When finished instant reverse, you can lookup the index tree in class repository. Then, right click on the class you want to reverse and select Reverse
Resources to where Resources are the classes you have selected, and select either New Class Diagram or Class Repository from popup menu.
Both options will result in reversing the selection to UML classes, while the option New Class Diagram will create a class diagram and place the
classes in it.
NOTE: The Form Diagram dialog box will only pop up when you were reversing source with on-demand turned off. If you have performed an on-
demand reverse engineering, you need to form diagram manually. For details, read the previous section.
Select Class
The classes listing in the tree are those reversed from your code-base. You must select at least one class in order to form a class diagram. Notice that
forming diagram can be a costly operation if you have selected too many classes in forming diagram.
Option Description
Show superclasses Show the generalization relationships between the selected elements and their super classes (ancestors) in the
new diagram.
Show subclasses Show the generalization relationships between the selected elements and their subclasses (descendants) in the
new diagram.
Show suppliers (interface) Show the realization relationships between the selected elements and their suppliers (interfaces) in the new
diagram.
Show clients Show the realization relationships between the selected elements and their clients (classes that implements
them) in the new diagram.
Show navigable classes Show the association relationships between the selected elements and their navigable classes (targets) in new
diagram.
Show non-navigable classes Show the association relationships between the selected elements and their non-navigable classes (sources) in
the new diagram.
Show containers Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Show residents Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Single level only - Show one level residents only in the new diagram.
All levels in single diagram - Show all level residents in the new diagram.
All levels in sub diagrams - Show all level residents in the new diagrams (multiple single level diagrams).
Show as containment relationships Show the containment relationships as connectors in the new diagram.
Notes: The containment relationships between classes are shown as connectors.
Presentation Options
Option Description
Attribute options Show all - Show all attributes of classes in the new diagram.
Public only - Show all public attributes of classes only in the new diagram.
Hide all - Hide all attributes of classes in the new diagram.
Initial values - Show initial values of attributes of classes in the new diagram.
Operation Show all - Show all operations of classes in the new diagram.
options
Public only - Show all public operations of classes only in the new diagram.
Hide all - Hide all operations of classes in the new diagram.
Initial values - Show initial values of operations of classes in the new diagram.
3. You can place reversed classes to specific model. For example, to place legacy code to a model named Old, to place system prototype to a
model named Prototype and so forth. To do this:
1. Click on the ... button at the end of the Reverse to Model row.
2. In the Select Parent Model dialog box, either select an existing model, or create one by clicking New Model.
3. Click OK to confirm.
NOTE: By cancelling from forming diagram, it just means you do not want to form diagram with the reversed classes for the time being. You can
still look for the classes in Model Explorer or Class Repository, and possibly form diagram later on manually.
2 Update type Determine how to handle duplicated classes by selecting the Update Type. Below is a description of the update types:
Update duplicate class(es) - Update existing class(es) by source.
Replace duplicate class(es) - Discard existing class(es), overwrite by reversed source.
3 Path The path of source to reverse. You can click + to add multiple paths.
4 Exclude The paths to exclude when reverse. Click + to add a path to exclude, or click - to remove a chosen path.
6 Reverse to model Place reversed classes to specific model. For example, to place legacy code to a model named Old, to place system
prototype to a model named Prototype and so forth.
7 Advanced options Click to configure any detailed options related to reverse in a new dialog box.
8 Reverse package Whether or not to reverse engineering package diagram from source files. UML packages and the relationships in
diagram between will be produced.
NOTE: If you do not want VP-UML to ask you for forming diagram next time you perform instant reverse, uncheck Show this dialog after instant
reverse.
Select Class
The classes listing in the tree are those reversed from your code-base. You must select at least one class in order to form a class diagram. Notice that
forming diagram can be a costly operation if you have selected too many classes in forming diagram.
Option Description
Show superclasses Show the generalization relationships between the selected elements and their super classes (ancestors) in the
new diagram.
Show subclasses Show the generalization relationships between the selected elements and their subclasses (descendants) in the
new diagram.
Show suppliers (interface) Show the realization relationships between the selected elements and their suppliers (interfaces) in the new
diagram.
Show clients Show the realization relationships between the selected elements and their clients (classes that implements
them) in the new diagram.
Show navigable classes Show the association relationships between the selected elements and their navigable classes (targets) in new
diagram.
Show non-navigable classes Show the association relationships between the selected elements and their non-navigable classes (sources) in
the new diagram.
Show containers Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Show residents Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Single level only - Show one level residents only in the new diagram.
All levels in single diagram - Show all level residents in the new diagram.
All levels in sub diagrams - Show all level residents in the new diagrams (multiple single level diagrams).
Show as containment relationships Show the containment relationships as connectors in the new diagram.
Notes: The containment relationships between classes are shown as connectors.
Presentation Options
Option Description
Attribute options Show all - Show all attributes of classes in the new diagram.
Public only - Show all public attributes of classes only in the new diagram.
Hide all - Hide all attributes of classes in the new diagram.
Initial values - Show initial values of attributes of classes in the new diagram.
Operation Show all - Show all operations of classes in the new diagram.
options
Public only - Show all public operations of classes only in the new diagram.
Hide all - Hide all operations of classes in the new diagram.
Initial values - Show initial values of operations of classes in the new diagram.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.
NOTE: By cancelling from forming diagram, it just means you do not want to form diagram with the reversed classes for the time being. You can
still look for the classes in Model Explorer or Class Repository, and possibly form diagram later on manually.
2 Update type Determine how to handle duplicated classes by selecting the Update Type. Below is a description of the update types:
Update duplicate class(es) - Update existing class(es) by source.
Replace duplicate class(es) - Discard existing class(es), overwrite by reversed source.
3 Path The path of source to reverse. You can click + to add multiple paths.
4 Reverse to model Place reversed classes to specific model. For example, to place legacy code to a model named Old, to place system
prototype to a model named Prototype and so forth.
5 Reverse package Whether or not to reverse engineering package diagram from source files. UML packages and the relationships in
diagram between will be produced.
NOTE: If you do not want VP-UML to ask you for forming diagram next time you perform instant reverse, uncheck Show this dialog after instant
reverse.
Select Class
The classes listing in the tree are those reversed from your code-base. You must select at least one class in order to form a class diagram. Notice that
forming diagram can be a costly operation if you have selected too many classes in forming diagram.
Option Description
Show superclasses Show the generalization relationships between the selected elements and their super classes (ancestors) in the
new diagram.
Show subclasses Show the generalization relationships between the selected elements and their subclasses (descendants) in the
new diagram.
Show suppliers (interface) Show the realization relationships between the selected elements and their suppliers (interfaces) in the new
diagram.
Show clients Show the realization relationships between the selected elements and their clients (classes that implements
them) in the new diagram.
Show navigable classes Show the association relationships between the selected elements and their navigable classes (targets) in new
diagram.
Show non-navigable classes Show the association relationships between the selected elements and their non-navigable classes (sources) in
the new diagram.
Show containers Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Show residents Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Single level only - Show one level residents only in the new diagram.
All levels in single diagram - Show all level residents in the new diagram.
All levels in sub diagrams - Show all level residents in the new diagrams (multiple single level diagrams).
Show as containment relationships Show the containment relationships as connectors in the new diagram.
Notes: The containment relationships between classes are shown as connectors.
Presentation Options
Option Description
Attribute options Show all - Show all attributes of classes in the new diagram.
Public only - Show all public attributes of classes only in the new diagram.
Hide all - Hide all attributes of classes in the new diagram.
Initial values - Show initial values of attributes of classes in the new diagram.
Operation Show all - Show all operations of classes in the new diagram.
options
Public only - Show all public operations of classes only in the new diagram.
Hide all - Hide all operations of classes in the new diagram.
Initial values - Show initial values of operations of classes in the new diagram.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.
NOTE: By cancelling from forming diagram, it just means you do not want to form diagram with the reversed classes for the time being. You can
still look for the classes in Model Explorer or Class Repository, and possibly form diagram later on manually.
2 Update type Determine how to handle duplicated classes by selecting the Update Type. Below is a description of the update types:
Update duplicate class(es) - Update existing class(es) by source.
Replace duplicate class(es) - Discard existing class(es), overwrite by reversed source.
3 Path The path of source to reverse. You can click + to add multiple paths.
4 Reverse to model Place reversed classes to specific model. For example, to place legacy code to a model named Old, to place system
prototype to a model named Prototype and so forth.
5 Reverse package Whether or not to reverse engineering package diagram from source files. UML packages and the relationships in
diagram between will be produced.
NOTE: If you do not want VP-UML to ask you for forming diagram next time you perform instant reverse, uncheck Show this dialog after instant
reverse.
Select Class
The classes listing in the tree are those reversed from your code-base. You must select at least one class in order to form a class diagram. Notice that
forming diagram can be a costly operation if you have selected too many classes in forming diagram.
Option Description
Show superclasses Show the generalization relationships between the selected elements and their super classes (ancestors) in the
new diagram.
Show subclasses Show the generalization relationships between the selected elements and their subclasses (descendants) in the
new diagram.
Show suppliers (interface) Show the realization relationships between the selected elements and their suppliers (interfaces) in the new
diagram.
Show clients Show the realization relationships between the selected elements and their clients (classes that implements
them) in the new diagram.
Show navigable classes Show the association relationships between the selected elements and their navigable classes (targets) in new
diagram.
Show non-navigable classes Show the association relationships between the selected elements and their non-navigable classes (sources) in
the new diagram.
Show containers Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Show residents Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Single level only - Show one level residents only in the new diagram.
All levels in single diagram - Show all level residents in the new diagram.
All levels in sub diagrams - Show all level residents in the new diagrams (multiple single level diagrams).
Show as containment relationships Show the containment relationships as connectors in the new diagram.
Notes: The containment relationships between classes are shown as connectors.
Presentation Options
Option Description
Attribute options Show all - Show all attributes of classes in the new diagram.
Public only - Show all public attributes of classes only in the new diagram.
Hide all - Hide all attributes of classes in the new diagram.
Initial values - Show initial values of attributes of classes in the new diagram.
Operation Show all - Show all operations of classes in the new diagram.
options
Public only - Show all public operations of classes only in the new diagram.
Hide all - Hide all operations of classes in the new diagram.
Initial values - Show initial values of operations of classes in the new diagram.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.
NOTE: By cancelling from forming diagram, it just means you do not want to form diagram with the reversed classes for the time being. You can
still look for the classes in Model Explorer or Class Repository, and possibly form diagram later on manually.
2 Update type Determine how to handle duplicated classes by selecting the Update Type. Below is a description of the update types:
Update duplicate class(es) - Update existing class(es) by source.
Replace duplicate class(es) - Discard existing class(es), overwrite by reversed source.
3 Path The path of source to reverse. You can click + to add multiple paths.
4 Reverse to model Place reversed classes to specific model. For example, to place legacy code to a model named Old, to place system
prototype to a model named Prototype and so forth.
5 Reverse package Whether or not to reverse engineering package diagram from source files. UML packages and the relationships in
diagram between will be produced.
NOTE: If you do not want VP-UML to ask you for forming diagram next time you perform instant reverse, uncheck Show this dialog after instant
reverse.
Select Class
The classes listing in the tree are those reversed from your code-base. You must select at least one class in order to form a class diagram. Notice that
forming diagram can be a costly operation if you have selected too many classes in forming diagram.
Option Description
Show superclasses Show the generalization relationships between the selected elements and their super classes (ancestors) in the
new diagram.
Show subclasses Show the generalization relationships between the selected elements and their subclasses (descendants) in the
new diagram.
Show suppliers (interface) Show the realization relationships between the selected elements and their suppliers (interfaces) in the new
diagram.
Show clients Show the realization relationships between the selected elements and their clients (classes that implements
them) in the new diagram.
Show navigable classes Show the association relationships between the selected elements and their navigable classes (targets) in new
diagram.
Show non-navigable classes Show the association relationships between the selected elements and their non-navigable classes (sources) in
the new diagram.
Show containers Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Show residents Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Single level only - Show one level residents only in the new diagram.
All levels in single diagram - Show all level residents in the new diagram.
All levels in sub diagrams - Show all level residents in the new diagrams (multiple single level diagrams).
Show as containment relationships Show the containment relationships as connectors in the new diagram.
Notes: The containment relationships between classes are shown as connectors.
Presentation Options
Option Description
Attribute options Show all - Show all attributes of classes in the new diagram.
Public only - Show all public attributes of classes only in the new diagram.
Hide all - Hide all attributes of classes in the new diagram.
Initial values - Show initial values of attributes of classes in the new diagram.
Operation Show all - Show all operations of classes in the new diagram.
options
Public only - Show all public operations of classes only in the new diagram.
Hide all - Hide all operations of classes in the new diagram.
Initial values - Show initial values of operations of classes in the new diagram.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.
NOTE: By cancelling from forming diagram, it just means you do not want to form diagram with the reversed classes for the time being. You can
still look for the classes in Model Explorer or Class Repository, and possibly form diagram later on manually.
2 Update type Determine how to handle duplicated classes by selecting the Update Type. Below is a description of the update
types:
Update duplicate class(es) - Update existing class(es) by source.
Replace duplicate class(es) - Discard existing class(es), overwrite by reversed source.
3 Path The path of source to reverse. You can click + to add multiple paths.
4 Reverse to Place reversed classes to specific model. For example, to place legacy code to a model named Old, to place system
model prototype to a model named Prototype and so forth.
NOTE: If you do not want VP-UML to ask you for forming diagram next time you perform instant reverse, uncheck Show this dialog after instant
reverse.
Select Class
The classes listing in the tree are those reversed from your code-base. You must select at least one class in order to form a class diagram. Notice that
forming diagram can be a costly operation if you have selected too many classes in forming diagram.
Option Description
Show superclasses Show the generalization relationships between the selected elements and their super classes (ancestors) in the
new diagram.
Show subclasses Show the generalization relationships between the selected elements and their subclasses (descendants) in the
new diagram.
Show suppliers (interface) Show the realization relationships between the selected elements and their suppliers (interfaces) in the new
diagram.
Show clients Show the realization relationships between the selected elements and their clients (classes that implements
them) in the new diagram.
Show navigable classes Show the association relationships between the selected elements and their navigable classes (targets) in new
diagram.
Show non-navigable classes Show the association relationships between the selected elements and their non-navigable classes (sources) in
the new diagram.
Show containers Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Show residents Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Single level only - Show one level residents only in the new diagram.
All levels in single diagram - Show all level residents in the new diagram.
All levels in sub diagrams - Show all level residents in the new diagrams (multiple single level diagrams).
Show as containment relationships Show the containment relationships as connectors in the new diagram.
Notes: The containment relationships between classes are shown as connectors.
Presentation Options
Option Description
Attribute options Show all - Show all attributes of classes in the new diagram.
Public only - Show all public attributes of classes only in the new diagram.
Hide all - Hide all attributes of classes in the new diagram.
Initial values - Show initial values of attributes of classes in the new diagram.
Operation Show all - Show all operations of classes in the new diagram.
options
Public only - Show all public operations of classes only in the new diagram.
Hide all - Hide all operations of classes in the new diagram.
Initial values - Show initial values of operations of classes in the new diagram.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.
NOTE: By cancelling from forming diagram, it just means you do not want to form diagram with the reversed classes for the time being. You can
still look for the classes in Model Explorer or Class Repository, and possibly form diagram later on manually.
2 Update type Determine how to handle duplicated classes by selecting the Update Type. Below is a description of the
update types:
Update duplicate class(es) - Update existing class(es) by source.
Replace duplicate class(es) - Discard existing class(es), overwrite by reversed source.
3 Path The path of source to reverse. You can click + to add multiple paths.
4 Reverse to model Place reversed classes to specific model. For example, to place legacy code to a model named Old, to
place system prototype to a model named Prototype and so forth.
5 Turn on getter/setter for attributes Set all attributes' getter and setter options to be true.
6 Reverse package diagram Whether or not to reverse engineering package diagram from source files. UML packages and the
relationships in between will be produced.
NOTE: If you do not want VP-UML to ask you for forming diagram next time you perform instant reverse, uncheck Show this dialog after instant
reverse.
Select Class
The classes listing in the tree are those reversed from your code-base. You must select at least one class in order to form a class diagram. Notice that
forming diagram can be a costly operation if you have selected too many classes in forming diagram.
Option Description
Show superclasses Show the generalization relationships between the selected elements and their super classes (ancestors) in the
new diagram.
Show subclasses Show the generalization relationships between the selected elements and their subclasses (descendants) in the
new diagram.
Show suppliers (interface) Show the realization relationships between the selected elements and their suppliers (interfaces) in the new
diagram.
Show clients Show the realization relationships between the selected elements and their clients (classes that implements
them) in the new diagram.
Show navigable classes Show the association relationships between the selected elements and their navigable classes (targets) in new
diagram.
Show non-navigable classes Show the association relationships between the selected elements and their non-navigable classes (sources) in
the new diagram.
Show containers Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Show residents Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Single level only - Show one level residents only in the new diagram.
All levels in single diagram - Show all level residents in the new diagram.
All levels in sub diagrams - Show all level residents in the new diagrams (multiple single level diagrams).
Show as containment relationships Show the containment relationships as connectors in the new diagram.
Notes: The containment relationships between classes are shown as connectors.
Presentation Options
Option Description
Attribute options Show all - Show all attributes of classes in the new diagram.
Public only - Show all public attributes of classes only in the new diagram.
Hide all - Hide all attributes of classes in the new diagram.
Initial values - Show initial values of attributes of classes in the new diagram.
Operation Show all - Show all operations of classes in the new diagram.
options
Public only - Show all public operations of classes only in the new diagram.
Hide all - Hide all operations of classes in the new diagram.
Initial values - Show initial values of operations of classes in the new diagram.
3. You can place reversed classes to specific model. For example, to place legacy code to a model named Old, to place system prototype to a
model named Prototype and so forth. To do this:
1. Click on the ... button at the end of the Reverse to Model row.
2. In the Select Parent Model dialog box, either select an existing model, or create one by clicking New Model.
3. Click OK to confirm.
NOTE: By cancelling from forming diagram, it just means you do not want to form diagram with the reversed classes for the time being. You can
still look for the classes in Model Explorer or Class Repository, and possibly form diagram later on manually.
4 Reverse to Place reversed classes to specific model. For example, to place legacy code to a model named Old, to place system
model prototype to a model named Prototype and so forth.
NOTE: If you do not want VP-UML to ask you for forming diagram next time you perform instant reverse, uncheck Show this dialog after instant
reverse.
Select Class
The classes listing in the tree are those reversed from your code-base. You must select at least one class in order to form a class diagram. Notice that
forming diagram can be a costly operation if you have selected too many classes in forming diagram.
Option Description
Show superclasses Show the generalization relationships between the selected elements and their super classes (ancestors) in the
new diagram.
Show subclasses Show the generalization relationships between the selected elements and their subclasses (descendants) in the
new diagram.
Show suppliers (interface) Show the realization relationships between the selected elements and their suppliers (interfaces) in the new
diagram.
Show clients Show the realization relationships between the selected elements and their clients (classes that implements
them) in the new diagram.
Show navigable classes Show the association relationships between the selected elements and their navigable classes (targets) in new
diagram.
Show containers Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Show residents Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Single level only - Show one level residents only in the new diagram.
All levels in single diagram - Show all level residents in the new diagram.
All levels in sub diagrams - Show all level residents in the new diagrams (multiple single level diagrams).
Show as containment relationships Show the containment relationships as connectors in the new diagram.
Notes: The containment relationships between classes are shown as connectors.
Presentation Options
Option Description
Attribute options Show all - Show all attributes of classes in the new diagram.
Public only - Show all public attributes of classes only in the new diagram.
Hide all - Hide all attributes of classes in the new diagram.
Initial values - Show initial values of attributes of classes in the new diagram.
Operation Show all - Show all operations of classes in the new diagram.
options
Public only - Show all public operations of classes only in the new diagram.
Hide all - Hide all operations of classes in the new diagram.
Initial values - Show initial values of operations of classes in the new diagram.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.
NOTE: By cancelling from forming diagram, it just means you do not want to form diagram with the reversed classes for the time being. You can
still look for the classes in Model Explorer or Class Repository, and possibly form diagram later on manually.
2 Update type Determine how to handle duplicated classes by selecting the Update Type. Below is a description of the update types:
Update duplicate class(es) - Update existing class(es) by source.
Replace duplicate class(es) - Discard existing class(es), overwrite by reversed source.
3 Path The path of source to reverse. You can click + to add multiple paths.
4 Reverse to model Place reversed classes to specific model. For example, to place legacy code to a model named Old, to place system
prototype to a model named Prototype and so forth.
5 Reverse package Whether or not to reverse engineering package diagram from source files. UML packages and the relationships in
diagram between will be produced.
NOTE: If you do not want VP-UML to ask you for forming diagram next time you perform instant reverse, uncheck Show this dialog after instant
reverse.
Select Class
The classes listing in the tree are those reversed from your code-base. You must select at least one class in order to form a class diagram. Notice that
forming diagram can be a costly operation if you have selected too many classes in forming diagram.
Option Description
Show superclasses Show the generalization relationships between the selected elements and their super classes (ancestors) in the
new diagram.
Show subclasses Show the generalization relationships between the selected elements and their subclasses (descendants) in the
new diagram.
Show suppliers (interface) Show the realization relationships between the selected elements and their suppliers (interfaces) in the new
diagram.
Show clients Show the realization relationships between the selected elements and their clients (classes that implements
them) in the new diagram.
Show navigable classes Show the association relationships between the selected elements and their navigable classes (targets) in new
diagram.
Show non-navigable classes Show the association relationships between the selected elements and their non-navigable classes (sources) in
the new diagram.
Show containers Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Show residents Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Single level only - Show one level residents only in the new diagram.
All levels in single diagram - Show all level residents in the new diagram.
All levels in sub diagrams - Show all level residents in the new diagrams (multiple single level diagrams).
Show as containment relationships Show the containment relationships as connectors in the new diagram.
Notes: The containment relationships between classes are shown as connectors.
Presentation Options
Option Description
Attribute options Show all - Show all attributes of classes in the new diagram.
Public only - Show all public attributes of classes only in the new diagram.
Hide all - Hide all attributes of classes in the new diagram.
Initial values - Show initial values of attributes of classes in the new diagram.
Operation Show all - Show all operations of classes in the new diagram.
options
Public only - Show all public operations of classes only in the new diagram.
Hide all - Hide all operations of classes in the new diagram.
Initial values - Show initial values of operations of classes in the new diagram.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.
NOTE: By cancelling from forming diagram, it just means you do not want to form diagram with the reversed classes for the time being. You can
still look for the classes in Model Explorer or Class Repository, and possibly form diagram later on manually.
2 Update type Determine how to handle duplicated classes by selecting the Update Type. Below is a description of the update
types:
Update duplicate class(es) - Update existing class(es) by source.
Replace duplicate class(es) - Discard existing class(es), overwrite by reversed source.
3 Path The path of source to reverse. You can click + to add multiple paths.
4 Remove '$' prefix Ignore the dollar sign prefix for attributes.
6 Reverse to model Place reversed classes to specific model. For example, to place legacy code to a model named Old, to place
system prototype to a model named Prototype and so forth.
7 Reverse package diagram Whether or not to reverse engineering package diagram from source files. UML packages and the relationships in
between will be produced.
NOTE: If you do not want VP-UML to ask you for forming diagram next time you perform instant reverse, uncheck Show this dialog after instant
reverse.
Select Class
The classes listing in the tree are those reversed from your code-base. You must select at least one class in order to form a class diagram. Notice that
forming diagram can be a costly operation if you have selected too many classes in forming diagram.
Option Description
Show superclasses Show the generalization relationships between the selected elements and their super classes (ancestors) in the
new diagram.
Show subclasses Show the generalization relationships between the selected elements and their subclasses (descendants) in the
new diagram.
Show suppliers (interface) Show the realization relationships between the selected elements and their suppliers (interfaces) in the new
diagram.
Show clients Show the realization relationships between the selected elements and their clients (classes that implements
them) in the new diagram.
Show navigable classes Show the association relationships between the selected elements and their navigable classes (targets) in new
diagram.
Show non-navigable classes Show the association relationships between the selected elements and their non-navigable classes (sources) in
the new diagram.
Show containers Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Show residents Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Single level only - Show one level residents only in the new diagram.
All levels in single diagram - Show all level residents in the new diagram.
All levels in sub diagrams - Show all level residents in the new diagrams (multiple single level diagrams).
Show as containment relationships Show the containment relationships as connectors in the new diagram.
Notes: The containment relationships between classes are shown as connectors.
Presentation Options
Option Description
Attribute options Show all - Show all attributes of classes in the new diagram.
Public only - Show all public attributes of classes only in the new diagram.
Hide all - Hide all attributes of classes in the new diagram.
Initial values - Show initial values of attributes of classes in the new diagram.
Operation Show all - Show all operations of classes in the new diagram.
options
Public only - Show all public operations of classes only in the new diagram.
Hide all - Hide all operations of classes in the new diagram.
Initial values - Show initial values of operations of classes in the new diagram.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.
NOTE: By cancelling from forming diagram, it just means you do not want to form diagram with the reversed classes for the time being. You can
still look for the classes in Model Explorer or Class Repository, and possibly form diagram later on manually.
2 Update type Determine how to handle duplicated classes by selecting the Update Type. Below is a description of the update types:
Update duplicate class(es) - Update existing class(es) by source.
Replace duplicate class(es) - Discard existing class(es), overwrite by reversed source.
3 Path The path of source to reverse. You can click + to add multiple paths.
4 Reverse to model Place reversed classes to specific model. For example, to place legacy code to a model named Old, to place system
prototype to a model named Prototype and so forth.
5 Reverse package Whether or not to reverse engineering package diagram from source files. UML packages and the relationships in
diagram between will be produced.
NOTE: If you do not want VP-UML to ask you for forming diagram next time you perform instant reverse, uncheck Show this dialog after instant
reverse.
Select Class
The classes listing in the tree are those reversed from your code-base. You must select at least one class in order to form a class diagram. Notice that
forming diagram can be a costly operation if you have selected too many classes in forming diagram.
Option Description
Show superclasses Show the generalization relationships between the selected elements and their super classes (ancestors) in the
new diagram.
Show subclasses Show the generalization relationships between the selected elements and their subclasses (descendants) in the
new diagram.
Show suppliers (interface) Show the realization relationships between the selected elements and their suppliers (interfaces) in the new
diagram.
Show clients Show the realization relationships between the selected elements and their clients (classes that implements
them) in the new diagram.
Show navigable classes Show the association relationships between the selected elements and their navigable classes (targets) in new
diagram.
Show non-navigable classes Show the association relationships between the selected elements and their non-navigable classes (sources) in
the new diagram.
Show containers Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Show residents Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Single level only - Show one level residents only in the new diagram.
All levels in single diagram - Show all level residents in the new diagram.
All levels in sub diagrams - Show all level residents in the new diagrams (multiple single level diagrams).
Show as containment relationships Show the containment relationships as connectors in the new diagram.
Presentation Options
Attribute options Show all - Show all attributes of classes in the new diagram.
Public only - Show all public attributes of classes only in the new diagram.
Hide all - Hide all attributes of classes in the new diagram.
Initial values - Show initial values of attributes of classes in the new diagram.
Operation Show all - Show all operations of classes in the new diagram.
options
Public only - Show all public operations of classes only in the new diagram.
Hide all - Hide all operations of classes in the new diagram.
Initial values - Show initial values of operations of classes in the new diagram.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.
NOTE: By cancelling from forming diagram, it just means you do not want to form diagram with the reversed classes for the time being. You can
still look for the classes in Model Explorer or Class Repository, and possibly form diagram later on manually.
2 Update type Determine how to handle duplicated classes by selecting the Update Type. Below is a description of the update
types:
Update duplicate class(es) - Update existing class(es) by source.
Replace duplicate class(es) - Discard existing class(es), overwrite by reversed source.
3 Path The path of source to reverse. You can click + to add multiple paths.
4 Reverse to Place reversed classes to specific model. For example, to place legacy code to a model named Old, to place system
model prototype to a model named Prototype and so forth.
NOTE: If you do not want VP-UML to ask you for forming diagram next time you perform instant reverse, uncheck Show this dialog after instant
reverse.
Select Class
The classes listing in the tree are those reversed from your code-base. You must select at least one class in order to form a class diagram. Notice that
forming diagram can be a costly operation if you have selected too many classes in forming diagram.
Option Description
Show superclasses Show the generalization relationships between the selected elements and their super classes (ancestors) in the
new diagram.
Show subclasses Show the generalization relationships between the selected elements and their subclasses (descendants) in the
new diagram.
Show suppliers (interface) Show the realization relationships between the selected elements and their suppliers (interfaces) in the new
diagram.
Show clients Show the realization relationships between the selected elements and their clients (classes that implements
them) in the new diagram.
Show navigable classes Show the association relationships between the selected elements and their navigable classes (targets) in new
diagram.
Show non-navigable classes Show the association relationships between the selected elements and their non-navigable classes (sources) in
the new diagram.
Show containers Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Show residents Show the containment relationships between the selected elements and their containers (e.g. packages) in the
new diagram.
Single level only - Show one level residents only in the new diagram.
All levels in single diagram - Show all level residents in the new diagram.
All levels in sub diagrams - Show all level residents in the new diagrams (multiple single level diagrams).
Show as containment relationships Show the containment relationships as connectors in the new diagram.
Notes: The containment relationships between classes are shown as connectors.
Presentation Options
Option Description
Attribute options Show all - Show all attributes of classes in the new diagram.
Public only - Show all public attributes of classes only in the new diagram.
Hide all - Hide all attributes of classes in the new diagram.
Initial values - Show initial values of attributes of classes in the new diagram.
Operation Show all - Show all operations of classes in the new diagram.
options
Public only - Show all public operations of classes only in the new diagram.
Hide all - Hide all operations of classes in the new diagram.
Initial values - Show initial values of operations of classes in the new diagram.
NOTE: You can reverse multiple source paths by adding them one after the other.
3. Click Next.
4. Select the operation you want to analyze its content and form sequence diagram.
7. Click Finish. When the process is completed, you can obtain the result in sequence diagram.
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Allow From Linked Project Check to generate also classes in referenced project.
Generate unnamed attribute When two classes are associated, checking this option will generate attributes in both classes with
each other as type. When unchecked, attributes will not be generated to both of them.
Unnamed attribute Pattern will be applied when generating name for those attribute without name.
Invalid char replacement Invalid char refers to characters that will result in a compile error when compiling code. This option is
for replacing those invalid characters by given one.
Default attribute type Attribute type that will be used when attribute has no type specified.
Default parameter type Parameter type that will be used when parameter has no type specified.
Default operation return type Operation return type that will be used when operation has no return type specified.
Import Fully Qualified Whether to state in import statement the class to import, or use asterisk to present an import on all
classes in a package.
Generate hashCode and equals operations Whether or not to generate hashCode() and equals() for each class.
Generate Ant build file Whether or not to generate Ant build file.
Implement abstract operations Whether or not to generate operations for implementing abstract operations defined in super class.
Generate association operations If you check this box, when a role is selected to provide setter/getter, the corresponding operation(s)
will be generated for the role's attribute.
Generate simple collection operations Whether or not to generate setter and getter for accessing attribute of associated class, when getter
and setter are checked.
Generate additional collection operations Whether or not to generate add, remove and to methods for accessing attribute of associated class,
when getter and setter are checked.
Pre/Post Condition generation You can defined pre and post conditions in class, attribute and operation specification. Check this
option to generate them as comment in code.
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Default attribute type Attribute type that will be used when attribute has no type specified.
Default parameter type Parameter type that will be used when parameter has no type specified.
Allow From Linked Project Check to generate also classes in referenced project.
Default operation return type Operation return type that will be used when operation has no return type specified.
Auto implement base class abstract method Whether or not to generate operations for implementing abstract operations defined in super class.
Follow Microsoft naming convention Make the code convention follow Microsoft
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Default attribute type Attribute type that will be used when attribute has no type specified.
Allow From Linked Project Check to generate also classes in referenced project.
Default parameter type Parameter type that will be used when parameter has no type specified.
Auto implement base class abstract method Whether or not to generate operations for implementing abstract operations defined in super class.
Follow Microsoft naming convention Make the code convention follow Microsoft
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Allow From Linked Project Check to generate also classes in referenced project.
Invalid char replacement Invalid char refers to characters that will result in a compile error when compiling code. This option is
for replacing thsoe invalid characters by given character.
Implement abstract operations Whether or not to generate operations for implementing abstract operations in subclass.
Generate association operations If you check this box, when a role is selected to provide setter/getter, the corresponding operation(s)
will be generated for the role's attribute.
Generate simple collection operations Whether or not to generate setter and getter for accessing attribute of associated class, when getter
and setter are checked.
Generate additional collection operations Whether or not to generate add, remove and to methods for accessing attribute of associated class,
when getter and setter are checked.
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Allow From Linked Project Check to generate also classes in referenced project.
Generate unnamed attribute When two classes are associated, checking this option will generate attributes in both classes with
each other as type. When unchecked, attributes will not be generated to both of them.
Unnamed attribute Pattern will be applied when generating name for those attribute without name.
Invalid char replacement Invalid char refers to characters that will result in a compile error when compiling code. This option is
for replacing those invalid characters by given one.
Default attribute type Attribute type that will be used when attribute has no type specified.
Default parameter type Parameter type that will be used when parameter has no type specified.
Default operation return type Operation return type that will be used when operation has no return type specified.
Implement abstract operations Whether or not to generate operations for implementing abstract operations defined in super class.
Generate association operations If you check this box, when a role is selected to provide setter/getter, the corresponding operation(s)
will be generated for the role's attribute.
Generate simple collection operations Whether or not to generate setter and getter for accessing attribute of associated class, when getter
and setter are checked.
Generate additional collection operations Whether or not to generate add, remove and to methods for accessing attribute of associated class,
when getter and setter are checked.
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Allow From Linked Project Check to generate also classes in referenced project.
Generate unnamed attribute When two classes are associated, checking this option will generate attributes in both classes with
each other as type. When unchecked, attributes will not be generated to both of them.
Unnamed attribute Pattern will be applied when generating name for those attribute without name.
Default attribute type Attribute type that will be used when attribute has no type specified.
Default parameter type Parameter type that will be used when parameter has no type specified.
Default operation return type Operation return type that will be used when operation has no return type specified.
Implement abstract operations Whether or not to generate operations for implementing abstract operations defined in super class.
Generate association operations If you check this box, when a role is selected to provide setter/getter, the corresponding operation(s)
will be generated for the role's attribute.
Generate simple collection operations Whether or not to generate setter and getter for accessing attribute of associated class, when getter
and setter are checked.
Generate additional collection operations Whether or not to generate add, remove and to methods for accessing attribute of associated class,
when getter and setter are checked.
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Allow From Linked Project Check to generate also classes in referenced project.
Generate unnamed attribute When two classes are associated, checking this option will generate attributes in both classes with
each other as type. When unchecked, attributes will not be generated to both of them.
Unnamed attribute Pattern will be applied when generating name for those attribute without name.
Invalid char replacement Invalid char refers to characters that will result in a compile error when compiling code. This option
is for replacing those invalid characters by given one.
Default attribute type Attribute type that will be used when attribute has no type specified.
Default operation return type Operation return type that will be used when operation has no return type specified.
Pointer for composition When checked, generate attribute for linking composited class using pointer (by reference).
Implement abstract operations Whether or not to generate operations for implementing abstract operations defined in super
class.
Generate association operations If you check this box, when a role is selected to provide setter/getter, the corresponding
operation(s) will be generated for the role's attribute.
Generate simple collection operations Whether or not to generate setter and getter for accessing attribute of associated class, when
getter and setter are checked.
Generate additional collection operations Whether or not to generate add, remove and to methods for accessing attribute of associated
class, when getter and setter are checked.
Force first attribute character to lower case Force the first character in attribute name to be in lower case.
Force first operation character to lower case Force the first character in operation name to be in lower case.
Force first parameter character to lower case Force the first character in parameter name to be in lower case.
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Allow From Linked Project Check to generate also classes in referenced project.
Generate unnamed attribute When two classes are associated, checking this option will generate attributes in both classes with
each other as type. When unchecked, attributes will not be generated to both of them.
Unnamed attribute Pattern will be applied when generating name for those attribute without name.
Default attribute type Attribute type that will be used when attribute has no type specified.
Default parameter type Parameter type that will be used when parameter has no type specified.
Default operation return type Operation return type that will be used when operation has no return type specified.
Implement abstract operations Whether or not to generate operations for implementing abstract operations defined in super class.
Generate association operations If you check this box, when a role is selected to provide setter/getter, the corresponding operation(s)
will be generated for the role's attribute.
Generate simple collection operations Whether or not to generate setter and getter for accessing attribute of associated class, when getter
and setter are checked.
Generate additional collection operations Whether or not to generate add, remove and to methods for accessing attribute of associated class,
when getter and setter are checked.
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Allow From Linked Project Check to generate also classes in referenced project.
Generate unnamed attribute When two classes are associated, checking this option will generate attributes in both classes with
each other as type. When unchecked, attributes will not be generated to both of them.
Unnamed attribute Pattern will be applied when generating name for those attribute without name.
Invalid char replacement Invalid char refers to characters that will result in a compile error when compiling code. This option is
for replacing those invalid characters by given one.
Generate association operations If you check this box, when a role is selected to provide setter/getter, the corresponding operation(s)
will be generated for the role's attribute.
Generate simple collection operations Whether or not to generate setter and getter for accessing attribute of associated class, when getter
and setter are checked.
Generate additional collection operations Whether or not to generate add, remove and to methods for accessing attribute of associated class,
when getter and setter are checked.
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Allow From Linked Project Check to generate also classes in referenced project.
Generate unnamed When two classes are associated, checking this option will generate attributes in both classes with each other as type.
attribute When unchecked, attributes will not be generated to both of them.
Unnamed attribute Pattern will be applied when generating name for those attribute without name.
Invalid char replacement Invalid char refers to characters that will result in a compile error when compiling code. This option is for replacing those
invalid characters by given one.
Default attribute type Attribute type that will be used when attribute has no type specified.
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Allow From Linked Project Check to generate also classes in referenced project.
Generate unnamed attribute When two classes are associated, checking this option will generate attributes in both classes with
each other as type. When unchecked, attributes will not be generated to both of them.
Unnamed attribute Pattern will be applied when generating name for those attribute without name.
Invalid char replacement Invalid char refers to characters that will result in a compile error when compiling code. This option is
for replacing those invalid characters by given one.
Generate association operations If you check this box, when a role is selected to provide setter/getter, the corresponding operation(s)
will be generated for the role's attribute.
Generate simple collection operations Whether or not to generate setter and getter for accessing attribute of associated class, when getter
and setter are checked.
Generate additional collection operations Whether or not to generate add, remove and to methods for accessing attribute of associated class,
when getter and setter are checked.
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Explicit Type in Declaration hen checked, will generate attribute/parameter type with specified type or just id.
Allow From Linked Project Check to generate also classes in referenced project.
Generate unnamed attribute When two classes are associated, checking this option will generate attributes in both classes with
each other as type. When unchecked, attributes will not be generated to both of them.
Unnamed attribute Pattern will be applied when generating name for those attribute without name.
Invalid char replacement Invalid char refers to characters that will result in a compile error when compiling code. This option is
for replacing those invalid characters by given one.
Default attribute type Attribute type that will be used when attribute has no type specified.
Default parameter type Parameter type that will be used when parameter has no type specified.
Default operation return type Operation return type that will be used when operation has no return type specified.
Implement abstract operations Whether or not to generate operations for implementing abstract operations defined in super class.
Generate association operations If you check this box, when a role is selected to provide setter/getter, the corresponding operation(s)
will be generated for the role's attribute.
Generate simple collection operations Whether or not to generate setter and getter for accessing attribute of associated class, when getter
and setter are checked.
Generate additional collection operations Whether or not to generate add, remove and to methods for accessing attribute of associated class,
when getter and setter are checked.
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Allow From Linked Project Check to generate also classes in referenced project.
Generate unnamed attribute When two classes are associated, checking this option will generate attributes in both classes with each other as
type. When unchecked, attributes will not be generated to both of them.
Unnamed attribute Pattern will be applied when generating name for those attribute without name.
Invalid char replacement Invalid char refers to characters that will result in a compile error when compiling code. This option is for replacing
those invalid characters by given one.
Default attribute type Attribute type that will be used when attribute has no type specified.
Default parameter type Parameter type that will be used when parameter has no type specified.
Default operation return type Operation return type that will be used when operation has no return type specified.
Implement abstract operations Whether or not to generate operations for implementing abstract operations defined in super class.
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
This Parameter Name The name of the pointer which for accessing object itself.
Default attribute type Attribute type that will be used when attribute has no type specified.
Default parameter type Parameter type that will be used when parameter has no type specified.
Allow from linked project Check to generate also classes in referenced project.
Pointer type name The name of the pointer for accessing object's associated class.
Internal type name suffix The name of the type which is generated for internal use.
Private component name The name of the type which is used for containing the private member.
2. In the Instant Generator dialog box, fill in the Path field, which is the directory where you want the code to generate to.
3. In the element tree, select the packages and classes to generate code.
4. Optionally configure the generator options. Read the section below for a description of options.
5. Click Generate to generate code.
2 Model element tree A list of packages and classes that can be selected for code generation. You must select classes for code
generation.
3 General options Some of the common configurable options are shown here. You can configure them in advanced options.
4 Output path The folder where you want the code files to be generated.
5 Template directory Template governs how code will be generated from model to code. You can customize the template to
suit your needs, such as to print company specific headers to each code file. If you want to use your own
template, provide the template directory here. If you want to keep using the build in template, leave this
option unchanged to let VP-UML generate with build in template. To learn more about customization, read
the final chapter of this part.
6 Advanced options Click this button to configure any options related to code generation in a new dialog box.
7 Prompt to confirm overwrite file If a code file instant generator going to generate is already exist, by checking this option you will be asked
whether to overwrite that file or not. If you uncheck this option, it will help you overwrite the existing file
automatically.
8 Output pane Any warning, error or progress about generation will be printed here.
9 Open output folder Open the output path with system browser.
10 Preview Click to preview the code content. It is just a preview and code will not be generated to the output path by
previewing.
Generator options
On the Instant Generator dialog box you can configure some of the common code options at the right of dialog box. You can also configure the
advanced options for more detailed settings by clicking the Advanced Options... button.
Option Description
Allow From Linked Project Check to generate also classes in referenced project.
Generate unnamed attribute When two classes are associated, checking this option will generate attributes in both classes with
each other as type. When unchecked, attributes will not be generated to both of them.
Unnamed attribute Pattern will be applied when generating name for those attribute without name.
Invalid char replacement Invalid char refers to characters that will result in a compile error when compiling code. This option is
for replacing those invalid characters by given one.
Implement abstract operations Whether or not to generate operations for implementing abstract operations defined in super class.
Generate association operations If you check this box, when a role is selected to provide setter/getter, the corresponding operation(s)
will be generated for the role's attribute.
Generate simple collection operations Whether or not to generate setter and getter for accessing attribute of associated class, when getter
and setter are checked.
Generate additional collection operations Whether or not to generate add, remove and to methods for accessing attribute of associated class,
when getter and setter are checked.
Preparation
Text editor
The customization of template requires the use of a text editor. A suggestion of text editor would be JEdit, a powerful, yet free of charge text editor.
More important, it provides syntax highlighting, which helps you read the template content easier by styling different parts with different colors. You can
download JEdit from its official site at:
http://www.jedit.org/
To install JEdit:
1. Run the downloaded setup program.
2. Press Next > in the Welcome screen.
3. Accept the license agreement and press Next >.
4. Select the installation folder and press Next >.
5. Select the components to be installed. The editing of template does not require the API documentation, macros and batch files. Depending on
your interest, you may decide to install them or not.
6. Select the Start Menu folder and press Next >.
7. Select whether to create desktop icons and quick launch icon and press Next >.
8. Confirm by pressing Install.
Copy folder
At the beginning, you may find the template a bit complex. But once you start working on it for a while, you’ll find the syntax easy to
understanding. In fact, it just composes of common programming construct like if-then-else statements, foreach and variables that programmers
should find intuitive.
3. Make change.
Add variable
3. Select the classes to generate. Specify the output path. Click Generate to generate code. You may refer to previous chapters for details about
instant generator.
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
propertyArray() Object[]
propertyAt(int) AnnotationProperty
propertyCount() int
propertyIterator() Iterator
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDocumentation() String
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getValue() String
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
associationClassAt(int) AssociationClass
associationClassCount() int
associationClassIterator() Iterator
commentArray() Comment[]
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
fromAssociationClassArray() Object[]
fromAssociationClassAt(int) AssociationClass
fromAssociationClassCount() int
fromAssociationClassIterator() Iterator
getDocumentation() String
getFromElement() Object
getFromEnd() AssociationEnd
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getToElement() Object
getToEnd() AssociationEnd
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isAbstract() boolean
isDerived() boolean
isFromLinkedProject() boolean
isLeaf() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
toAssociationClassArray() Object[]
toAssociationClassAt(int) AssociationClass
toAssociationClassCount() int
toAssociationClassIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDocumentation() String
getFromElement() Object
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getToElement() Object
getVisibility() String
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getAggregationKind() String
getDocumentation() String
getName() String
getNavigable() int
getReferencedAttribute() Attribute
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getTypeModifier() String
getVisibility() String
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
isOrdered() boolean
isProvideGetterMethod() boolean
isProvideSetterMethod() boolean
isUnique() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
annotationAt(int) Annotation
annotationCount() int
annotationIterator() Iterator
commentArray() Comment[]
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDeclarativeAttribute() String
getDocumentation() String
getFieldType() Object
getInitialValue() String
getMetadataTag() String
getName() String
getScope() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getStorage() int
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getTemplateTypeBindInfo() TemplateTypeBindInfo
getType()
getTypeModifier() String
getVisibility() String
getXmlSchemaFieldType() Object
hasGetter() boolean
hasSetter() boolean
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
hasXmlSchema() boolean
isAbstract() boolean
isConst() boolean
isDefault() boolean
isExtern() boolean
isFinal() boolean
isFromLinkedProject() boolean
isHasGetter() boolean
isHasSetter() boolean
isIndexer() boolean
isNew() boolean
isOrdered() boolean
isOverload() boolean
isOverride() boolean
isReadonly() boolean
isShadow() boolean
isTransient() boolean
isUnique() boolean
isUnsafe() boolean
isVirtual() boolean
isVisible() boolean
isWithEvent() boolean
propertyParameterArray() Object[]
propertyParameterAt(int) Parameter
propertyParameterCount() int
propertyParameterIterator() Iterator
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDocumentation() String
getFixed() String
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getUse() String
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
annotationCount() int
annotationIterator() Iterator
associationArray() Association[]
associationAt(int) Association
associationClassArray() AssociationClass[]
associationClassAt(int) AssociationClass
associationClassCount() int
associationClassIterator() Iterator
associationCount() int
associationIterator() Iterator
attributeArray() Attribute[]
attributeAt(int) Attribute
attributeCount() int
attributeIterator() Iterator
commentArray() Comment[]
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
containmentClassArray() Class[]
containmentClassAt(int) Class
containmentClassCount() int
containmentClassIterator() Iterator
fromAssociationArray() Object[]
fromAssociationAt(int) Association
fromAssociationClassArray() Object[]
fromAssociationClassAt(int) AssociationClass
fromAssociationClassCount() int
fromAssociationClassIterator() Iterator
fromAssociationCount() int
fromAssociationIterator() Iterator
generalizationArray() Generalization[]
generalizationAt(int) Generalization
generalizationCount() int
generalizationIterator() Iterator
getDeclarativeAttribute() String
getDocumentation() String
getManageType() int
getMetadataTag() String
getName() String
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getTemplateTypeBindInfo() TemplateTypeBindInfo
getType() Object
getTypeModifier() String
getVisibility() String
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isAbstract() boolean
isActive() boolean
isFinal() boolean
isFromLinkedProject() boolean
isInterface() boolean
isLeaf() boolean
isNew() boolean
isNotInheritable() boolean
isRoot() boolean
isSealed() boolean
isShadow() boolean
isStatic() boolean
isStereotypeInterface() boolean
isStereotypeTypedef() boolean
isTypedef() boolean
operationArray() Operation[]
operationAt(int) Operation
operationCount() int
operationIterator() Iterator
realizationArray() Realization[]
realizationAt(int) Realization
realizationClassArray() Object[]
realizationClassAt(int) Class
realizationClassCount() int
realizationClassIterator() Iterator
realizationCount() int
realizationIterator() Iterator
stereotypeArray() Stereotype[]
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
templateParameterArray() TemplateParameter[]
templateParameterAt(int) TemplateParameter
templateParameterCount() int
templateParameterIterator() Iterator
toAssociationArray() Object[]
toAssociationAt(int) Association
toAssociationClassArray() Object[]
toAssociationClassAt(int) AssociationClass
toAssociationClassCount() int
toAssociationClassIterator() Iterator
toAssociationCount() int
toAssociationIterator() Iterator
commentArray() Comment[]
commentAt(int) Comment
commentIterator() Iterator
getAuthor() String
getContent() String
getDateTime() String
getDocumentation() String
getName() String
getSummary() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeCount() int
stereotypeArray() Stereotype[]
stereotypeIterator() Iterator
taggedValueCount() int
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDocumentation() String
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
templateParameterArray() Object[]
templateParameterAt(int) TemplateParameter
templateParameterCount() int
templateParameterIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getBlock() String
getDocumentation() String
getForm() String
getNillable() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDocumentation() String
getFromElement() Object
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getTemplateTypeBindInfo() TemplateTypeBindInfo
getToElement() Object
getVisibility() String
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
isSubstitutable() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getCode() String
getDocumentation() String
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDocumentation() String
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
annotationAt(int) Annotation
annotationCount() int
annotationIterator() Iterator
commentArray() Comment[]
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getAlias() String
getCharset() int
getDeclarativeAttribute() String
getDllName() String
getDocumentation() String
getImplModel() ImplModel
getMetadataTag() String
getMethodKind() int
getName() String
getOperatorType() int
getProcedureName() String
getReturnType() Object
getReturnTypeDocumentation() String
getReturnTypeModifier() String
getScope() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getTemplateTypeBindInfo() TemplateTypeBindInfo
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isAbstract() boolean
isConst() boolean
isDeclare() boolean
isDelegate() boolean
isExtern() boolean
isFinal() boolean
isFriend() boolean
isFromLinkedProject() boolean
isInline() boolean
isNative() boolean
isNew() boolean
isNotOverridable() boolean
isOverload() boolean
isOverridable() boolean
isOverride() boolean
isQuery() boolean
isReturnTypeConst() boolean
isSealed() boolean
isShadow() boolean
isSynchronized() boolean
isUnsafe() boolean
isVirtual() boolean
isVisible() boolean
parameterArray() Object[]
parameterAt(int) Parameter
parameterCount() int
parameterIterator() Iterator
postConditionArray() Object[]
postConditionAt(int) Text
postConditionCount() int
postConditionIterator() Iterator
preConditionArray() Object[]
preConditionAt(int) Text
preConditionCount() int
preConditionIterator() Iterator
raisedExceptionAt(int) Object
raisedExceptionCount() int
raisedExceptionIterator() Iterator
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
templateParameterArray() Object[]
templateParameterAt(int) TemplateParameter
templateParameterCount() int
templateParameterIterator() Iterator
classAt(int) Class
classCount() int
classIterator() Iterator
commentArray() Comment[]
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDocumentation() String
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
packageArray() Object[]
packageAt(int) Package
packageCount() int
packageIterator() Iterator
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
templateParameterArray() Object[]
templateParameterAt(int) TemplateParameter
templateParameterCount() int
templateParameterIterator() Iterator
annotationAt(int) Annotation
annotationCount() int
annotationIterator() Iterator
commentArray() Comment[]
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDeclarativeAttribute() String
getDefaultValue() String
getDirection() String
getDocumentation() String
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getTemplateTypeBindInfo() TemplateTypeBindInfo
getType() Object
getTypeModifier() String
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isConst() boolean
isFinal() boolean
isFromLinkedProject() boolean
isOptional() boolean
isParamArray() boolean
isParams() boolean
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDocumentation() String
getFromElement() Object
getMapping() String
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getTemplateTypeBindInfo() TemplateTypeBindInfo
getToElement() Object
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDocumentation() String
getName() String
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDocumentation() String
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getType() int
getValue() Object
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDefaultValue() String
getDocumentation() String
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
templateTypeBindInfoArray() Object[]
templateTypeBindInfoAt(int) TemplateTypeBindInfo
templateTypeBindInfoCount() int
templateTypeBindInfoIterator() Iterator
typeArray() Object[]
typeAt(int) Object
typeCount() int
typeIterator() Iterator
typeModifierArray() Object[]
typeModifierAt(int) String
typeModifierCount() int
typeModifierIterator() Iterator
TemplateTypeBindDetailscommentArray() Comment[]
commentAt(int) Comment
commentCount() int
getArguments() TemplateTypeBindInfo
getDocumentation() String
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getWildcard() int
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
detailsArray() Object[]
detailsAt(int) TemplateTypeBindDetails
detailsCount() int
detailsIterator() Iterator
getBindedType() Object
getDocumentation() String
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
getTypeModifier() String
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDocumentation() String
getName() String
getStereotype(String) Stereotype
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
commentAt(int) Comment
commentCount() int
commentIterator() Iterator
getDocumentation() String
getName() String
getStereotypeIgnoreCase(String) Stereotype
getTaggedValue(String) TaggedValue
getTaggedValueIgnoreCase(String) TaggedValue
hasStereotype(String) boolean
hasStereotypeIgnoreCase(String) boolean
hasTaggedValue(String) boolean
hasTaggedValueIgnoreCase(String)boolean
isFromLinkedProject() boolean
stereotypeArray() Stereotype[]
stereotypeAt(int) Stereotype
stereotypeCount() int
stereotypeIterator() Iterator
taggedValueArray() TaggedValue[]
taggedValueAt(int) TaggedValue
taggedValueCount() int
taggedValueIterator() Iterator
templateParameterArray() Object[]
templateParameterAt(int) TemplateParameter
templateParameterCount() int
templateParameterIterator() Iterator
Velocity syntax
The following lists the syntax that of statements that can be used in the template.
## ===== If =====
#if(...)
...
#end
## ===== If-then-Else =====
#if(...)
...
#else
...
#end
## ===== For-each =====
#foreach
...
#end
## ===== Continue with the template defined in (...) at the point where the call is made =====
#parse(...)
#set(...)
## ===== Comment =====
## ...
## ===== Comment =====
#* ... *#
## ===== Variable=====
${...}
3. Optionally, configure the advanced code generation options by clicking Advanced Options.... Read the section Advanced Options in this
chapter for details about the options.
4. Click OK to proceed with generation.
NOTE: If you have generated code for once, the Generate Code dialog box will not appear next time you generate/update code for any diagram.
If you want to configure the model-to-source-path mapping or to configure options, you can run a code generation for project (refer to the
previous section for detail).
3. Optionally configure the advanced code generation options by clicking Advanced Options.... Read the section Advanced Options in this
chapter for details about the options.
4. Click OK to proceed with generation.
2. In the Generate Code dialog box, specify the source path where you want the code to be generated. Model is a UML element that acts as a
container of other elements. Notice that source path is set for model, not for diagram. Classes and packages under a model will be generated to
the mapped source path. You can add multiple model-to-source-path mapping by pressing the + button. If you are not using model to structure
your project, or if you want to generate all classes in project to the same folder, regardless of their parent model, keep model to be <root>.
NOTE: If you have generated code for once, the Generate Code dialog box will not appear next time you generate/update code for any class
selection. If you want to configure the model-to-source-path mapping or to configure options, you can run a code generation for project
(refer to the previous section for detail).
2 Add model-to-source-path mapping Click to add a new mapping between UML model and the source path where code will be generated
to.
4 Move model-to-source-path mapping up Click to move chosen model-to-source-path mapping one item upward.
5 Move model-to-source-path mapping Click to move chosen model-to-source-path mapping one item downward.
down
6 Model-to-source-path mapping A list of mapping between UML model and source path.
7 Advanced options Click to configure advanced code generation options. For details, read the section Advanced Options
in this chapter.
8 Ignore classes Click to organize the ignore list of classes to ignore in code generation. For details, read the section To
ignore classes in generation in this chapter.
10 Cancel Click to close the Generate Code dialog without generating code.
Advanced options
You can configure the advanced options for more control of the code by clicking the Advanced Options... button in Generate Code dialog box. In the
Code Synchronization dialog box popped up, there are four categories (tabs) of settings you can configure. Below is a description.
Code
Option Description
Default attribute type (default int) Type that will be assigned to Attribute upon code generation
when type is unspecified
Default operation return type (default void) Return Type that will be assigned to operation upon code
generation when return type is unspecified
Default parameter type (default int) Type that will be assigned to Parameter upon code generation
when type is unspecified
Auto realize interface (default false) Generate operations defined in interface in sub-classes
Remove method body after changed to abstract method (default true) When an operation is set from non-abstract to abstract,
updating code will remove the related method's body
Use "is" prefix for getters that return boolean (default true) Generate getter's name as isXXXX() for getters that return a
boolean value
Add import statement instead of using fully qualified type name (default true) Add import statement for referencing classes in another
package/namespace instead of using fully qualified name inline
Import fully qualified type name for referenced type (default false) Use fully qualified type name in import statements instead of
using wildcard character * to represent importing all classes in package
Generate annotation in code convention (default true) Generate annotation in code convention
Text File Encoding • System default - (default) The default system encoding will be selected
as encoding for source files
• Other -Specify an encoding for source files
Option Description
Class declaration • Same line - (default) Brace for class declaration appear at the same line as the declaration
• Next line - Brace for class declaration appear at the line after the declaration
Constructor declaration • Same line - (default) Brace for constructor appear at the same line as the declaration
• Next line - Brace for constructor appear at the line after the declaration
Method declaration • Same line - (default) Brace for method appear at the same line as the declaration
• Next line - Brace for method appear at the line after the declaration
Enum declaration • Same line - (default) Brace for enumeration appear at the same line as the declaration
• Next line - Brace for enumeration tor appear at the line after the declaration
Annotation type declaration • Same line - (default) Brace for annotation type appear at the same line as the declaration
New Lines
Option Description
Before package declaration Number of blank lines to appear before Package declaration
After package declaration Number of blank lines to appear after Package declaration
Before import declaration Number of blank lines to appear before import statements
After import declaration Number of blank lines to appear after import statements
Before first declaration Number of blank lines to appear before the first declaration within Class declarations
Before different kind declaration Number of blank lines to appear before a different kind of declaration
Before field declaration Number of blank lines to appear before field declaration
Before method declaration Number of blank lines to appear before method declaration
Before inner type declaration Number of blank lines to appear before inner type declaration
Number of lines to empty body Number of blank lines to appear in empty method body
Template
Template configuration
Option Description
Operation Defines a template of method body that will be applied when generating operations.
Template
Getter Template Defines a template of getter that will be applied when generating getter methods. Getter will be generated to attribute
stereotyped as Property, or with property getter selected.
Setter Template Defines a template of setter that will be applied when generating setter methods. Setter will be generated to attribute stereotyped
as Property, or with property setter selected.
3. By default an on-demand reverse engineering will be carried out, which means to form indexes to the added path(s) instead of actually reversing
them. For details about on demand reverse engineering, refer to the section below. If you want to carry out actual reverse engineering, uncheck
Reverse source on demand.
4. Click OK to proceed with reversal.
NOTE: In order to trigger this function, make sure you have performed round-trip engineering at least for once, and the diagram has at least one
class.
4 Move source-path-to-model mapping up Click to move chosen source-path-to-model mapping one item upward.
5 Move source-path-to-model mapping Click to move chosen source-path-to-model mapping one item downward.
down
6 Model-to-source-path mapping A list of mapping between UML model and source path.
7 Reverse source on-demand By checking, this means to form indexes to the source path(s) instead of actually reversing them. For
details about on demand reverse engineering, refer to the section below.
9 Cancel Click to close the Reverse Code dialog without reversing code.
When finished reverse, you can lookup the index tree in class repository. Then, right click on the class you want to reverse and select Reverse
Resources to where Resources are the classes you have selected, and select either New Class Diagram or Class Repository from popup menu.
Both options will result in reversing the selection to UML classes, while the option New Class Diagram will create a class diagram and place the
classes in it.
2. In the Generate Code dialog box, specify the mapping between model and source path. Model is a UML element that acts as a container of
other elements. Classes and packages under a model will be generated to the mapped source path. You can add multiple model-to-source-
path mapping by pressing the + button. If you are not using model to structure your project, or if you want to generate all classes in project to the
same folder, regardless of their parent model, keep model to be <root>.
3. Optionally configure the advanced code generation options by clicking Advanced Options.... Read the section Advanced Options in this
chapter for details about the options.
4. Click OK to proceed with generation.
NOTE: If you have generated code for once, the Generate Code dialog box will not appear next time you generate/update code for any diagram.
If you want to configure the model-to-source-path mapping or to configure options, you can run a code generation for project (refer to the
previous section for detail).
3. Optionally configure the advanced code generation options by clicking Advanced Options.... Read the section Advanced Options in this
chapter for details about the options.
4. Click OK to proceed with generation.
2. In the Generate Code dialog box, specify the source path where you want the code to be generated. Model is a UML element that acts as a
container of other elements. Notice that source path is set for model, not for diagram. Classes and packages under a model will be generated to
the mapped source path. You can add multiple model-to-source-path mapping by pressing the + button. If you are not using model to structure
your project, or if you want to generate all classes in project to the same folder, regardless of their parent model, keep model to be <root>.
NOTE: If you have generated code for once, the Generate Code dialog box will not appear next time you generate/update code for any class
selection. If you want to configure the model-to-source-path mapping or to configure options, you can run a code generation for project
(refer to the previous section for detail).
3. Optionally configure the advanced code generation options by clicking Advanced Options.... Read the section Advanced Options in this
chapter for details about the options.
2 Add model-to-source-path mapping Click to add a new mapping between UML model and the source path where code will be generated
to.
4 Move model-to-source-path mapping up Click to move chosen model-to-source-path mapping one item upward.
5 Move model-to-source-path mapping Click to move chosen model-to-source-path mapping one item downward.
down
6 Model-to-source-path mapping A list of mapping between UML model and source path.
7 Advanced options Click to configure advanced code generation options. For details, read the section Advanced Options
in this chapter.
8 Ignore classes Click to organize the ignore list of classes to ignore in code generation. For details, read the section To
ignore classes in generation in this chapter.
10 Cancel Click to close the Generate Code dialog without generating code.
Advanced options
You can configure the advanced options for more control of the code by clicking the Advanced Options... button in Generate Code dialog box. In the
Code Synchronization dialog box popped up, there are four categories (tabs) of settings you can configure. Below is a description.
Code
Option Description
Default attribute type (default int) Type that will be assigned to Attribute upon code generation when type is unspecified
Default operation return type (default void) Return Type that will be assigned to operation upon code generation when return type is unspecified
Default parameter type (default int) Type that will be assigned to Parameter upon code generation when type is unspecified
Text File Encoding • System default - (default) The default system encoding will be selected as encoding for source files
• Other -Specify an encoding for source files
Option Description
Class declaration • Same line - (default) Brace for class declaration appear at the same line as the declaration
• Next line - Brace for class declaration appear at the line after the declaration
Constructor declaration • Same line - (default) Brace for constructor appear at the same line as the declaration
• Next line - Brace for constructor appear at the line after the declaration
Method declaration • Same line - (default) Brace for method appear at the same line as the declaration
• Next line - Brace for method appear at the line after the declaration
Enum declaration • Same line - (default) Brace for enumeration appear at the same line as the declaration
• Next line - Brace for enumeration tor appear at the line after the declaration
New Lines
Option Description
Before first declaration Number of blank lines to appear before the first declaration within Class declarations
Before different kind declaration Number of blank lines to appear before a different kind of declaration
Before field declaration Number of blank lines to appear before field declaration
Before method declaration Number of blank lines to appear before method declaration
Template
Option Description
Operation Defines a template of method body that will be applied when generating operations.
Template
Getter Template Defines a template of getter that will be applied when generating getter methods. Getter will be generated to attribute
stereotyped as Property, or with property getter selected.
Setter Template Defines a template of setter that will be applied when generating setter methods. Setter will be generated to attribute stereotyped
as Property, or with property setter selected.
2. In the Reverse Code dialog box, specify the mapping between source path and model. Model is a UML element that acts as a container of other
elements. You can place the UML classes to be produced to specific model for better categorization. For example, you may create a Prototype
model and an Implementation model for storing classes developed in prototype and implementation phrases respectively. Once a mapping is
defined, round-trip engineering will be performed between the model and path as defined. You can add multiple Source-path-to-model mapping
by pressing the + button. If you do not use model to structure your project, keep model to be <root>.
3. By default an on-demand reverse engineering will be carried out, which means to form indexes to the added path(s) instead of actually reversing
them. For details about on demand reverse engineering, refer to the section below. If you want to carry out actual reverse engineering, uncheck
Reverse source on demand.
4. Click OK button to proceed with reversal.
NOTE: In order to trigger this function, make sure you have performed round-trip engineering at least for once, and the diagram has at least one
class.
2 Add source-path-to-model mapping Click to add a new mapping between source path where code will be reversed from and UML model.
4 Move source-path-to-model mapping up Click to move chosen source-path-to-model mapping one item upward.
5 Move source-path-to-model mapping Click to move chosen source-path-to-model mapping one item downward.
down
6 Model-to-source-path mapping A list of mapping between UML model and source path.
7 Reverse source on-demand By checking, this means to form indexes to the source path(s) instead of actually reversing them. For
details about on demand reverse engineering, refer to the section below.
9 Cancel Click to close the Reverse Code dialog without reversing code.
When finished reverse, you can lookup the index tree in class repository. Then, right click on the class you want to reverse and select Reverse
Resources to where Resources are the classes you have selected, and select either New Class Diagram or Class Repository from popup menu.
Both options will result in reversing the selection to UML classes, while the option New Class Diagram will create a class diagram and place the
classes in it.
Database configuration
Select database
You can select multiple databases, and set one of them as default database. The default database is used for rendering the column type and
generating SQL. To set a database as default, right click on the database and select Set as default from the pop-up menu.
The Download dialog shows the URL, file size, speed, progress information. Click Close button after downlond is completed.
The Driver file field shows the driver downloaded by VP-UML.
Testing connection
After configure the database setting, click the Test Connection button to confirm the setting is valid.
Test connection
Generate SQL
The generate DML is a template for select, insert, update, delete statements, you are required to modify the statement before execute.
Selecting database
Click the Database Configuration button to open the database configuration dialog.
Database configuration
If you selected multiple database, you can select one of the database from the database combo box.
SQL updated
• Delimiter - append to end of each statement, used for separate two statement. If you change it to \\, the SQL will become:
Delimiter
• Case - the case for the keyword. If you change it to Upper, the SQL will become:
Upper SQL
Formatted SQL
Using toolbar
There is a toolbar above each group of statements.
Generate database
• Generate Database:
• Create Database - generate create statements only.
• Update Database - query existing object in database, generate create and alter statement depends on object not exists or outdated in
database, or do nothing if database is up-to-date.
• Drop and Create Database - generate drop statements first, then generate create statements.
• Drop Database - generate drop statements only.
• Table Charset (Only available for MySQL) - the charset used for database connection.
Connection
3. In the Database Code Generation dialog box, select Database only in Generate, Update Database in Generate Database, uncheck Export
to database, check Generate DDL, Upper Case SQL, Formatted SQL and select JDBC in Connection.
4. Click Database Options button to configure JDBC.
Database options
Alter statements
3. Click the Export... button and specify the filen ame to save the setting.
Caption Here
Then, select in diagram the entity you want to enter its default data.
Caption Here
Enter the data in the editor. Double click on a cell to start editing. Click Enter to end editing.
Caption Here
Caption Here
Sometimes, you may be uncertain to what the foreign values represent. You can click on the ... button to show the additional pane, and select the
proper record from the pane.
Caption Here
Removing a record
To remove a record, select the record you want to remove and click on the Delete record button.
Caption Here
Caption Here
If anything wrong is detected, the Message pane will popup and a message will appear in it.
Caption Here
Caption Here
3. Click OK to continue.
Reverse database
3. In the Database to Data Model dialog box, select Reverse Table and click Next > button to continue.
Database setting
5. Select the Selected Schema and check the schema containing your tables, and then click Next > button.
Select schema
Select tables
7. After reverse, a new Entity Relationship Diagram is created automatically with a Reversed Entities dialog box.
Reversed entities
9. The tables were created on the diagram, click Close button to finish reversing database.
Reversed ERD
Reverse DDL
3. Fill in the filename of DDL and select database in Reverse DDL dialog box. Click OK button to continue.
Reversed ERD
Generate code
• Error Handling:
• Return false/null - query method error return null, save/update/delete error return false.
• Throw PersistentException - throw PersistentException when error occurs.
• Throw RuntimeException - throw RuntimeException when error occurs.
• Throw User Defined Exception - throw the exception specified in User Defined Exception field when error occurs.
• Exception Handling:
• Do not Show - do nothing when exception throw.
• Print to Error Stream - print the exception to System.err.
• Print to log4j - log the exception to log4j.
Static methods
Static methods generate all persistent methods in the persistent class, client can access the methods in the same persistent object.
Static methods
Factory class
DAO
DAO generate all persistent methods in DAO class, a DAO class is generate for each persistent class.
DAO
POJO
POJO generate persistent object in Plain Old Java Object style, without generating any persistent methods. Client can access persistent methods in
PersistentManager object.
POJO
Mapping only
Mapping only does not generate any code, it only generates the XML mapping file required for ORM.
Inserting records
1. Create persistent object with factory create method.
2. Save persistent object with save method.
The following code demonstrate how to insert a Product record:
Selecting records
Factory method provides a convinent listByQuery method, accept condition and order by as parameter, and return array of persistent object.
The following code demonstrate how to select a list of Product records, null for condition parameter will select all records, null for order by parameter
does not sort in any order:
Another useful method to select a persistent object by ID is loadByORMID. The follow code demonstrate how to select a l Prouct record by ID.
Updating records
1. Select a persistent object from database.
2. Update the persistent object.
3. Save persistent object with save method.
The following code demonstrate how to update a Product record:
Deleting records
1. Select a persistent object from database.
2. Delete persistent object with delete method.
The following code demonstrate how to delete a Product record:
A part of the generated code, showing the getters and setters generated from attributes of an ORM Persistable class
When you generate code, you will see the entered code appended to the generated getter or setter.
Customized setter
A controller class
You can create a controller class by selecting Class from diagram toolbar and click on the diagram. Name the class properly to represent the nature
of controller class. Very often people name controller class as SomethingController where the Something refers to a use case, or the model that the
controller need to manage. For example, a PhoneController is for controlling operations of a telephone and managing its states like waiting, dialing, etc.
You can add attributes to the class by right clicking on it and selecting Add > Attribute from the popup menu. Attributes defined will be generated to
code. However, you do NOT need to add attributes for states nor attributes for remembering states. Everything about states will be managed by the
state machine in state machine diagram.
Add operations to the class by right clicking on it and selecting Add > Operation from the popup menu. There should be operations that may update
the state.
Step 2 - Modeling state machine
You need to create a sub state machine diagram from the controller and model the state machine there. To create a sub state machine diagram, move
the mouse pointer over the controller class, click on the resource icon at bottom right corner and select Add > State Machine Diagram from the popup
menu.
In the state machine diagram, draw the states as well as the transition of states. Since the states will be generated to source code, you are adviced to
consider the naming convention of the programming language you want to generate when naming states.
A state machine
You do not need to name the transitions as we will assign operations to them. But if you want you can do this. It will not affect the code that will be
generated.
Step 3 - Assigning operations to transitions
A transition is a relationship between two states, representing the update of states. Previously you have defined operations in controller class. Now,
you need to assign those operations to the transitions to indicate the cause of state change. To assign an operation to transition:
1. Right click on a transition and select Open Specification... from the popup menu.
2. In the Generate State Machine dialog box, select the controller class for generating state machine.
3. Select the state machine in the drop down menu State Diagram for generating code.
4. Select the programming language of the code.
5. Specify the output path to save the generated code to.
6. Optionally configure the generator options.
7. Click OK to generate.
NOTE: There must be at least one class that contain sub state machine diagram in order to open the Generate State Machine Code dialog box.
2 State The state machine (in the form of state machine diagram) to generate. It must be a sub-class of the chosen controller class.
Diagram
7 Cancel Click to close the Generate State Machine Code dialog box.
NOTE: You can analyze a model element in Model Explorer by right clicking on the desired element node in Model Explorer, and selecting
Analysis... from the popup menu.
Type Description
Transitor The transited element of the chosen element, or the element where the chosen element was transited from
Parent- The parent (e.g. package) or the child of the chosen element
Child
Relationship The relationship(s) of the chosen element, such as association, dependencies, sequence flow, etc
Used The connection with the chosen element, other than any other kinds of relationship types. For example, requirement owned
by use case added through use case description is a kind of Used relationship.
View The view(s) of a model element, which can be seen as the shapes of a model element
An analysis diagram
The oval node at the center of diagram represents the element you have chosen to analyze, the connectors branching out are the relationships with the
analyzing element and the nodes at the opposite end of connectors are the related elements.
Inside a node of a related element, you can see a tag (e.g. <<View>>), which represents the type of that related element. At the bottom part of a node
box is the name of the related element.
By reading the diagram, you can identify the relationship of a model element, and determine the impact that may act upon the model when modifying
the model element.
NOTE: Besides the central node, you may update/show the relationships of other Model nodes on diagram, too.
To click on Analyse
To ungroup, simply deselect the node type by walking through the same popup menu path.
3. If the target model has only one view, that view is opened. If there a multiple views, the Show View dialog box is presented. Select a view to
open, and click Go to View at the bottom right of dialog box.
Configure matrix
Field Description
Diagram Name The name of diagram which is also the name of matrix.
Scope The source of model elements to compare in matrix, in Project (all model elements), Diagram (only model elements in
specific diagrams which are selected by users) or under Model/Package.
Template Template offers a default setup to Models on Column, Models on Row and By. It is available according to the project
content. For example, template "Use Case <-> Requirement" appear for selection when a project have use case and
requirement.
Available All available models in your selected scope are listed here. You can select a model to add it in the target Models on
Models Row and/or Models on Column.
Models on The type of model element to list at the column side of matrix. In order to list multiple types of model element, select it/
Column
them on Available Models and click button to insert it/them in here.
Models on Row The type of model element to list at the row side of matrix. In order to list multiple types of model element, select it/them
By The way how matrix will match against rows and columns.
Sub Diagram - The column/row model element is placed in a sub diagram of the matching model element.
Child - The column/row model element is a child of the matching model element.
Relationship - The column/row model element is related with the matching model element.
Reference - The column/row model element is referencing the matching model element.
As Classifier - The column/row model element takes the matching model element as classifier.
Dependent - The column/row model element has properties that depend on the matching model element.
1 Show only rows/columns with Matrix lists only rows and columns with matches by default. Uncheck it when you want to show entries
matches without matches as well.
2 Filter row Type the full name of a model element or part of it that you are looking for to narrow down the searching
field in rows when too much data is displayed.
3 Filter column Type the full name of a model element or part of it that you are looking for to narrow down the searching
field in columns when too much data is displayed.
4 Refresh You can update the content of matrix by clicking this button manually, for reflecting the changes you have
made in models.
5 Export to Excel Click this button to export the opening matrix to Excel.
8 Rows The model elements have been chosen will be displayed in rows.
9 Move up and move down Rows and columns are ordered alphabetically by default. They help to re-order rows and columns in
moving vertically.
10 Swap rows and columns It helps to change the presentation between rows and columns, but not switch the actual relationships
between model elements being represented by them.
11 Move left and move right Rows and columns are ordered alphabetically by default. They help to re-order rows and columns in
moving horizontally.
12 Columns The model elements have been chosen will be displayed in columns.
2. In the Export Excel dialog box, specify the output destination and click Save.
Generate report
2. In the Generate HTML/PDF/Word dialog box, fill in the output path where the report should be generated to.
NOTE: For HTML report, specify the folder of the HTML files to be generated.
For PDF report, specify the file path of PDF file (*.pdf) to be generated.
For MS Word report, specify the file path of the document file (*.docx) to be generated.
4. Make any necessary configuration such as the page layout, cover page, etc. For details about configuration, refer to the next chapter.
5. Click Generate to proceed with generation.
The bottom part of report generaition dialog box for MS Word report
1 Content The main page of report generation that lets you select the diagram(s) to generate report.
6 Template You can define a template for report generation by clicking on the drop down menu next to Template, and selecting
<New>. Once a template is defined, you can select it from the same drop down menu, and proceed with generation with
the template. For details about report customization, read the next chapter.
8 Edit template Click to edit the template selected in the drop down menu of Template.
9 Delete template Click to delete the template selected in the drop down menu of Template.
10 Import template Click to import a template file into the current project.
17 Reset to default Reset changes made in this dialog box to default settings.
21 Apply Click to apply the changes made in report, causing reopening of this dialog box to restore the applied settings.
23 Word template path Available only to MS Word report generation, this option enables you to specify the path of MS Word document file that
you want the generator to use as template. Report generator will append the template file content in front of generated
report. In other words, you can prepare a file for cover page. Apart from this, style will also follow the definition in
template file. For details, please read the section Generating MS Word report with template (MS Word report only).
Reorder diagram
Sort shapes
Automatic sorting
1. Select the diagram to sort and click to expand it.
Automatic The way of sorting elements is automatically managed. The order is often based on the flow and/or position of elements,
which is the most logical order, following most users' understanding of that kind of diagram.
Sort by Tree Sort diagram elements by following the order defined in Diagram Navigator.
Sort by Sort diagram elements alphabetically base on their name, in ascending order.
Name
Custom The way of sorting elements is controlled by user, through selecting elements and pressing or .
Options
Options
Option Description
Generate table of contents If this option is selected, table of content for this document will be generated to the
report
Generate table of figures If this option is selected, table of figures for this document will be generated to the
report
Generate diagrams If this option is selected, the image of the selected diagrams will be generated to
the report.
For PDF report, you can select the type of diagram. Here are the possible
selections:
• PNG - Images will look exactly the same as the diagrams in your project, but
not scalable against zooming.
• SVG - Due to its scalable nature, image content will remain clear regardless
of the level of zooming. However, image may look a bit different from the
original diagram as there is a conversion re-construction from raster graphic
data to SVG image.
• SVG (text as shape) - Base on SVG, this option makes any text on diagram
become text object, making it possible to select them in report content.
Generate diagram properties If this option is selected, the properties of the selected diagrams will be generated
to the report.
Generate diagram summary If the option is selected, the summary of the selected diagrams will be generated to
the report.
Include extra details If the option is selected, information like ID and stereotypes will be generated to the
summary table of report.
Suppress element with blank documentation in summary table If the option is selected, diagram elements without documentation defined will not
be generated to summary table.
Generate model elements/diagrams link Select to generate links for navigating to related models and diagrams.
Skip heading for empty model element section If this option is selected, heading for empty model element section will be skipped.
Convert multiline model heading to single line If this option is selected, multiline model heading will be converted to single line.
Show multiline model name If this option is selected, non heading multiline model name will remain in multiline,
instead of being converted to single line.
Treat HTML content as HTML source If this option is selected, HTML content will be treat as HTML source.
Suppress details if duplicated If this option is selected, duplicated details will be suppressed.
Table cell keep together with page If this option is selected, table cell will try to show on a page completely instead of
breaking into separate pages.
Shape type style Icon - using Icon to represent the type of shape and diagram elements
Text - using text to represent the type of shape and diagram elements
RTF content appearance Preserve formatting - using original formatting for RTF content
Make font size consistent with the rest of the report - using same font size for RTF
content in whole report
Display in plain text - using plain text for RTF content
Copy reference files If this option is selected, referenced files will be copy to output folder of report.
With this option, you can copy the whole report folder to another machine and read
there, without having broken file linkage for references.
Font Determines the font family of report content. This option is only available to PDF
report.
Encoding Determines the encoding of HTML file to be generated. This option is only available
to HTML report.
Page setup
Option Description
Page This option is used to select the orientation of the report (portrait/landscape). This option is only available to PDF and MS Word
orientation report.
Page margin To specify the page margins of the report. This option is only available to PDF and MS Word report.
Cover page
Option Description
Generate cover page (PDF and MS If this option is selected, there will be a cover page generated to the report.
Word)
Generate front page (HTML)
Logo image path An image that appear at the report. You are expected to supply the file path of the image file. The drop
down menu at the right hand side is for controlling the position of image.
Logo scale Control the scale of logo image. This option is only available to PDF and MS Word report.
Header/Footer
Header and footer refers to the content that appear in the top and bottom of every page in report. For MS Word report, there are two text boxes for
you to edit the header and footer. For PDF report, there are six boxes, three for each of header and footer. Each of the text box represent a region in
header/footer, such as the top left text box refers to the left region of header, while the bottom right text box refers to the right region of footer.
Header/Footer
Align to left Align content to the left of header/footer. This option is available only to MS Word report.
Align to center Align content to the center of header/footer. This option is available only to MS Word report.
Align to right Align content to the right of header/footer. This option is available only to MS Word report.
Add image Insert an image to the position where the text cursor is placing.
Insert page number Insert page number to the position where the text cursor is placing.
Insert page count Insert page count to the position where the text cursor is placing.
Insert date Insert the date of when the report is generated to the position where the text cursor is placing.
Insert time Insert the time of when the report is generated to the position where the text cursor is placing.
Insert project name Insert the project name to the position where the text cursor is placing.
Insert report file name Insert the name of report file to the position where the text cursor is placing.
Insert user name Insert the name of the user logging into the system to the position where the text cursor is placing.
Document info
Option Description
Author The author of the report. This option is only available to PDF report.
Info header The info header of the report. This option is only available to PDF report.
Info header The info header content of the report. This option is only available to PDF report.
content
Allow modify Select to allow modification on the report. This option is only available to PDF report.
NOTE: Report templates are shared among HTML, PDF and Word reports. If you just want to design template, but have no preference on the
type of report to generate yet, just select either HTML, PDF or Word.
2. Press on the Template drop down menu and select <New> from the popup menu to open the report template editor and start editing template.
To create a template
3. In the Report Template dialog box, enter the template name at the top of dialog box.
4. Construct the report template. A report template is formed by different kinds of components that put together in a hierarchical structure. A
common way of building a template is to start with a diagram loop, which can be created from the editor toolbar. Then, select the diagram loop
and create children components through its toolbar, such as to create an image component or a element loop for accessing diagram elements
on diagrams being looped. To learn how to use the tools in detail, refer to the coming chapters.
A sample template showing the use of diagram loop, element loop, property and custom text components
Exoprt To export the opening template to a report template file (.vpr). You can import the file to other machines for
reusing it.
Add diagram summary To add a component to template editor, indicating the need of looping specific type(s) of diagram for constructing
a tabular diagram summary.
Add diagram paragraph To add a component to template editor, indicating the need of looping specific type(s) of diagram for printing its
properties in paragraph form.
Add element loop (Model) To add a component to template editor, indicating the need of looping Model.
Add root level element loop To add a component to template editor, indicating the need of looping specific type(s) of model element that are
at project root (i.e. not being contained).
Add element summary To add a component to template editor, indicating the need of looping specific type(s) of model element for
constructing a tabular element summary.
Add element paragraph To add a component to template editor, indicating the need of looping specific type(s) of model element for
printing its properties in paragraph form.
Add all level element loop To add a component to template editor, indicating the need of looping model elements of specific type(s) in whole
project.
Add custom content To add a component to template editor, indicating the placement of text written by user.
Preview template content Preview the template against the project content for report content. Rendering of report is costly especially when
the project is large. If your project is large, be patient when waiting for outcome.
Preview template structure Preview the template against the project content for report structure.
To edit a template
To edit an existing report template, select it in the generate dialog box such as Generate PDF, then click on the edit button.
To edit a template
To delete a template
To delete an existing report template, select it in the generate dialog box such as Generate PDF, then click on the delete button.
To delete a template
2.
Click on the button at the top of template editor to export template.
3. In the Export dialog box, enter the file name and click Save.
4. Open the project that you want the template to import to. Open the report dialog box by selecting Tools > Generate HTML/PDF/Word Report
from the main menu.
5.
Click on the button.
6. In the Import dialog box, select the report template file and click Open.
NOTE: Make sure you are clicking on the button from the toolbar of element loop. If you are clicking on the button at editor toolbar, you will
create a loop at template root.
3.
On the right hand side of the template editor, select the type of sub-diagram(s) to loop and click to confirm the selection.
3. If you generate report with a template like this, you will obtain a table of diagram names, provided that there exists diagram(s) of the chosen
type(s). If you need to print specific diagram properties in table other than just name, click on the Add Property Column button in the toolbar of
diagram summary, then select the property(ies) to add into the table as column(s). For more details about the use of property, read the chapter
Property.
3. If you generate report with a template like this, you will obtain a list of diagram types and names, provided that there exists diagram(s) of the
chosen type(s). If you need to print specific diagram properties other than just name, click on the Add Property Value button in the toolbar of
diagram paragraph, then select the property(ies) to show. For more details about the use of property, read the chapter Property.
Add Element Loop (Model) To loop through all models in the project root. In other words, model being contained by other model
element will not be accessed. This is a shortcut for creating a root level element loop whose chosen
element type is model.
Add Element Loop To loop through all packages in the project root. In other words, package being contained by other
(Package) model element will not be accessed. This is a shortcut for creating a root level element loop whose
chosen element type is package.
Add Root Level Element To loop through any kind of model element in project root. By selecting this option, you can choose
Loop the type of model element to be looped.
Add All Level Element Loop To loop through any kind of model element within the project, regardless of their leveling. By
selecting this option, you can choose the type of model element to be looped.
2. If you have chosen to add a model or a package loop, you do not need to perform any actions in further.
If you have chosen to add either root level or all level element loop, select the type of element(s) to loop on the right hand side of the template
editor and click to confirm the selection.
NOTE: You can switch between a root level and a all-level loop by changing the option Root Level above the element list. Notice that changing
the value of Root Level is not about changing available element selection, but also the end result, whether to access only root level
elements or not.
NOTE: Make sure you are clicking on the button from the toolbar of diagram loop. If you are clicking on the button at editor toolbar, you will
create a loop at template root.
3.
On the right hand side of the template editor, select the type of diagram element to loop and click to confirm the selection.
NOTE: By default, element summary added to project root enables the looping of root level elements. If you want to change to access elements
in all levels, change the option Root Level above the element list. Notice that changing the value of Root Level is not about changing
available element selection, but also the end result, whether to access only root level elements or not.
3. If you generate report with a template like this, you will obtain a table of element names, provided that there exists element(s) of the chosen
type(s). If you need to print specific element properties in table other than just name, click on the Add Property Column button in the toolbar of
element summary, then select the property(ies) to add into the table as column(s). For more details about the use of property, read the chapter
Property.
2.
Click on the button at the top of template editor to export template.
3. In the Export dialog box, enter the file name and click Save.
4. Open the project that you want the template to import to. Open the report dialog box by selecting Tools > Generate HTML/PDF/Word Report
from the main menu.
5.
Click on the button.
6. In the Import dialog box, select the report template file and click Open.
NOTE: By default, element paragraph added to project root enables the looping of root level elements. If you want to change to access elements
in all levels, change the option Root Level above the element list. Notice that changing the value of Root Level is not about changing
available element selection, but also the end result, whether to access only root level elements or not.
3. If you generate report with a template like this, you will obtain a list of element names, provided that there exists element(s) of the chosen
type(s). If you need to print specific element properties other than just name, click on the Add Property Column button in the toolbar of element
paragraph, then select the property(ies) to show. For more details about the use of property, read the chapter Property.
2. Click on the Add Custom Content button from the toolbar of loop.
NOTE: Make sure you are clicking on the button from the toolbar of element loop. If you are clicking on the button at editor toolbar, you will
create a loop at template root.
3. On the right hand side of the template editor, enter the custom content. You can format your content through the buttons in the content pane.
For details, read the section below about editing custom content.
1 Editor pane The editor where you can enter and edit custom content.
14 Clear formats Clear formats of whole editor to convert the content to plain text.
2. Click on the Add Property Value button from the toolbar of loop.
3. On the right hand side of the template editor, select the property to access.
2. Click on the Add Property Value Below or Add Property Value Above button.
3. On the right hand side of the template editor, select the property to access.
2. Click on the Add Page Break button from the toolbar of loop.
3. Reposition the page break by pressing Move Up or Move Down from the toolbar of page break.
2. In the Project Publisher dialog box, specify the output directory where you want to save the published content.
3. You can optionally configure the publisher by adjust the options or options. For details, refer to the sections below.
4. Click OK button to start publishing.
1 Output directory The folder where you want to publish the content to.
2 Preserve image When checked, published content will show images in exact width and height.
size
3 Copy reference files You can add file references to model elements. When this option is checked, referenced files will be copied to the output
directory so that you can access any referenced file when browsing the published content in other machine easily.
4 Launch viewer When checked, the system will launch the web browser and open the published Web contents.
5 Advanced options Click to configure advanced publisher options. For details about the options, read the next section.
6 OK Click to publish.
Option Description
Generate model element list in diagram page Check to generate a list of model element in a diagram page.
Generate only documentation in model element Check to generate only documentation in model element page, and exclude other contents.
page
Generate only when documentation is defined Generate element page only when that element has documentation. When this option is off,
the shape will have no linkage from image in diagram page due to the absent of element
page.
Show documentation when hover over a shape Check to show element's documentation when moving the mouse pointer over a shape in an
image of diagram.
Generate diagram type Check to generate the diagram type in addition to diagram name.
Drill down effect for general models Choose the action when pressing on model elements on a diagram.
Drill down effect for business sub-process Choose the action when pressing on sub-processes on a diagram.
Drill down effect for process (Process Map) Choose the action when pressing on processes on a process map diagram.
Drill down effect for events (BPMN) Choose the action when pressing on (BPMN) events on a diagram.
Drill down effect for diagram overview Choose the action when pressing on diagram overviews on a diagram.
Publisher engine Choose the engine for publishing. You are advised to use the new engine.
Sort elements in type groups by Choose the way of sorting elements show in summary or drop down menu in diagram page
Filtered content Choose the content for not to show in published content
Published project
1 Navigator
pane
2 Menu pane It shows the sub-menus of the Navigator pane. The contents shown in this pane varies with the link you clicked in the Navigator
Pane. For more details about the possible contents please refer to the Navigator Pane section.
3 Content It shows the details of the item (diagram, model or package/class) you clicked in the Menu Pane or Content Pane.
pane
Navigator pane
There are four tabs within the navigator pane - Diagram Navigator, Model Explorer, Class Navigator and Logical View. They are responsible for
eading the project from different angle.
Diagram Navigator
Diagram Navigator shows the categories of diagrams in the project. You can click on a category to view its diagrams in the Menu Pane, or click Show
All Diagrams to view all diagrams.
Diagram navigator
Model Navigator
Class Navigator
Shows the Package models in the project. You can click on a package to view its child packages/classes in the Menu Pane, or click Show All Models
to view all packages/classes.
Class navigator
Logical view
Echos the logical view defined in project. You can click on a diagram to open it.
Logical view
To view the details of an item (diagram, model or package/class), click on its link in the Menu Pane and its details will be shown in the Content Pane.
Menu navigator
Diagram Content
The diagram type, name, description, together with a full size image of the diagram are shown in the Content Pane. The image is mapped to different
clickable regions for each shape, so you can click on a shape in the image to view its details.
Jump to
Besides, there will be two shortcut buttons above the selected shape.
The Back to top button brings you to the top of the page.
Back to top
The Open specification button brings you to the details page of the shape.
Open specification
Model elements
Parent hierarchy
The parent hierarchy is shown as a list of models on top of the page. You can click on a parent in the hierarchy to view its details.
Parent hierarchy
Relationships
The summary of the relationships of the model is shown in the Relationships Summary section. Click on a relationship and it will take you to the
Relationships Detail section.
Relationships summary
Relationships detail
Report writer
Diagram navigator
The Diagram Navigator displays all diagrams within the project in a form of a project tree and organizes them by their diagram type. Through the use
of a folding tree structure you can browse the names of these diagrams by either expanding or collapsing the folders and perform sorting by diagram
type and name.
Diagram navigator
Button Description
To sort diagrams within the project tree by alphabetical order of their names.
Model tree
The Model Pane displays models within the project in a form of a project tree. Notice that not all the model elements are displayed, and only the
elements that are available for generating report content are shown.
Model tree
Button Description
To display the models within the project without sorting. Ordering of models will be based on their order of creation.
To sort models within the project tree by alphabetical order of their names.
Template pane
Each template represents the corresponding report content of a particular model or diagram. By dragging a template into the Writer Pane, the report
content will be printed on the report. There are three types of template: Text, Image and Table. Each of them has its own appearance in the report
content.
Button Description
The generated element block is mainly composed of text. It is mainly used in the documentation template of elements.
The generated element block is mainly composed of images. It is used in the diagram template for UML Diagrams.
The generated element block is mainly composed of tables. Most of the content-related templates use this type of template.
Writer pane
Writer Pane embeds a word processor to provide a report editing environment.
Writer pane
Button Description
To update the content within the current report from the VP-UML models.
To display bookmarks that outlines the boundary for each generated element.
To insert a hyperlink.
Details of toolbar
Template pane
3. Drag the desired template from the Template Pane and drop it onto the report.
4. When the cursor drags over the Writer Pane, a tiny straight line will appear in the report indicating the position of the expected position of the
generated element. Once you've dropped the template onto the report, corresponding content will be generated element to the dropped position.
6. When the cursor drags over the Writer Pane, a tiny straight line will appear in the report indicating the position of the expected position of the
generated element. Once you've dropped the template onto the report, corresponding content will be generated element to the dropped position.
Showing bookmarks
Stylist
To edit the style, right-click on the highlighted style and choose Modify... from the popup menu. This displays the dialog box for the selected style. You
can now adjust it with your own preference. When everything is ready, please click OK to commit the settings and exit the dialog.
Edit style
The changes will take effect immediately and you will notice the style is applied to those generated elements using the same style.
Style change
Select a desired report for getting the style configuration and click Copy Style. The style configuration in the current report is replaced by the style
configuration of the selected report. All the predefined styles will be overwritten.
0 Heading 1
(VP)
1 Heading 2
(VP)
2 Heading 3
(VP)
3-9 None
To update the Table of Contents, right-click on the caption Table of Contents and select Update Index/Table from popup menu.
Report writer
Edit project
Updated report
NOTE: Please do not click on the Writer Pane while the update process is undergoing, as it may affect the accuracy of the content. It can also
damage the generated element, so that updating cannot be performed anymore unless the damaged block is removed manually.
NOTE: The update process will replace ALL the contents within each generated element without notification. Therefore please insert the content
carefully and ensure that it is not located inside the scope of any generated elements.
Importing a report
You can import a document back into Report Writer for data updating. To import a report:
1. Click the Import Report... button on the toolbar or select Report > Import Report... from main menu. This displays the Open dialog box.
2. Select a file and click Open to import the selected document into Report Writer.
3. If the document has previously been exported from Report Writer, a dialog will appear and ask for overwriting the existing one or not.
If you click Yes, the existing report will be replaced by the imported one. If you click No, the imported report will be stored into Report.
To edit a template
NOTE: You can save your work from time to time by pressing Save.
NOTE: If you have chosen Refresh Report when OK, the report will refresh itself to apply the changes you have made.
To duplicate a template
File A template is an XML file which defines the structure of report content. By default, it will be stored in the resources folder of
installation folder.
NameThe name of template, which will appear in the template list in template pane.
NOTE: If you have chosen Refresh Report when OK, the report will refresh itself to apply the changes you have made.
Function Hotkey
Copy Ctrl-
C
Paste Ctrl-
V
Delete Delete
Cut Ctrl-
X
Template schema
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema
targetNamespace="http://www.visual-paradigm.com/2008/ReportWriter1.1"
xmlns:rw="http://www.visual-paradigm.com/2008/ReportWriter1.1"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:element name="Template">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="rw:TemplateInformationHeader"/>
Export XML
2. In the Export to XML dialog box, specify the output destination, which is a folder for containing the exported XML files and optionally the image
files of diagrams.
3. Click Export.
1 Output destination The location where you want to save the file.
2 Export project By checking Export project, all models in the project will be exported.
3 Export sub-diagrams when export By selecting Export sub-diagrams when export parent, the sub-diagram(s) will also be exported
parent when the parent diagram(s) is exported.
For example, package MyWorks contains diagrams A and B. If you select to export diagram A, its
parent "MyWork" will get exported, too. With the option Export sub-diagrams when export parent
on, B will get exported too since B is a sub-diagram of package MyWorks. By turning off the option, B
will be ignored when export.
5 Preview window By checking the selected diagram and Show preview, it will be shown in preview window.
6 Preview mode You can choose either Stretch or Real size to preview your diagram.
Stretch: The ratio of your diagram will be fit in the size of preview window.
Real size: The ratio of your diagram will be shown on the preview window as its real size.
-out Folder for storing the exported XML and images C:\Demo\Output
Upon finishing, you can visit the output destination specified to obtain the XML files.
Import XML
NOTE: All changes made in project will be overwritten by data in XML. For example, if class Foo is renamed to Bar. By importing an XML
exported before renaming class, Bar will be renamed to Foo.
This displays the usage of the export command. Below is a description of parameters:
Parameter Description Example
Upon finishing, the project file will be updated with the data presented in the XML file.
Export VP project
3. Check in the diagram tree the diagrams to export. If you want to export the whole project, check the top most root node.
4. Click Export button. Upon finishing, you can visit the output destination specified to obtain the .vpp project file.
3 Preview window By checking the selected diagram and Show preview, it will be shown in preview window.
4 Preview mode You can choose either Stretch or Real size to preview your diagram.
Stretch: The ratio of your diagram will be fit in the size of preview window.
Real size: The ratio of your diagram will be shown on the preview window as its real size.
7 Help More information about how to export VP Project can be obtained by clicking this button.
Import VP Project
2. Select the file path of the .vpp file to import in file chooser.
3. Click Open.
NOTE: All changes made in project will be overwritten by imported project. For example, if class Foo is renamed to Bar. By importing a project
exported before renaming class, Bar will be renamed to Foo.
Export Excel
2 Launch Editor Check to open the exported Excel file after exported.
4 Export Tagged Tagged values can be added to model elements to specify domain specific properties. You can add tagged values in the
Values specification dialog box of model element. Check Export Tagged Values if you want to export tagged values of model
elements.
5 Export Comments You can add your own comments to model elements in their specification dialog box. Check Export Comments if you
want to export the comments to the Excel file.
6 Export PM PM properties is the short form of project management properties. You can set project management properties, such as
Properties version, phrase, author, in the specification dialog box of a model element. Check Export PM Properties if you want to
export PM properties of model elements.
7 Export Test Plans Test plan refers to the test plans that can be specified for Test Case elements in requirement diagram. Check Export Test
Plans to export the information of test plan to a separate sheet in Excel file.
8 Model Elements Select this tab and check the model elements you want to export to Excel.
9 Diagrams All diagrams in the opening project are listed here. Select the diagrams to export to Excel.
10 Model Types When you have updated the diagram selection in Diagrams list, the Model Types list will be updated to list the types of
diagram elements that appear in the chosen diagrams. By default, all diagram element types are checked, meaning that
diagram elements in those types will be exported to Excel. You can uncheck type(s) to ignore certain type(s) of diagram
elements when exporting.
Import Excel
2. In the file chooser, select the Excel file to import and click Open to confirm.
Caution
When you start to modify the Excel, pay attention to the following points to avoid having problems when importing the file back to project:
• Do NOT modify the gray cells
• Do NOT just delete a row for deleting a model element. Instead, change the value No to Yes under the Delete? column.
• Do NOT modify the System Data sheet
Export XMI
1 File path The file path for the XMI file to export.
2 XMI There are three versions of XMI to suit different interoperability needs, including 1.0, 1.2 and 2.1. If the latest version 2.1 is selected,
version the following options are then available for selection:
• Export <<Interface>> to Interface - Determine whether to export stereotype "interface" as stereotype, or a segment of
interface element.
• Export Interface Realization - Determine whether to keep exporting realization between interface and concrete class as
realization, or export it as interface realization.
-type [optional] Version of XMI. Unless specified, the lastly generated version will be selected. Here are the possible options: 2.1
• 1.0
• 1.2
• 2.1
• 2.1UML2
Upon finishing, you can visit the output destination specified to obtain the XMI.
Import XMI
NOTE: All changes made in project will be overwritten by data in XMI. For example, if class Foo is renamed to Bar. By importing an XMI
exported before renaming class, Bar will be renamed to Foo.
2 Import Comment as Note (for XMI 2.1 only) Determines whether to import comment as documentation, or as note of model.
3 Auto Layout after imported Determines whether to run a layout on diagram after import. Note that running layout may takes
time for a massive amount of diagram data.
4 Suppress Super Stereotype Determines whether to ignore super stereotype when importing.
5 Matching The importing of XMI is a procedure to merge the data in XMI into the opening project. The
matching option is to determine how to match between data in XMI and the opening project during
export, and to perform changes accordingly.
Upon finishing, the project file will be updated with the data presented in the XMI file.
A Visio drawing
2. To import a Visio drawing into VP-UML, select File > Import > Visio... in the main menu of VP-UML.
NOTE: Only valid XML Drawing (*.vdx) can be imported. If your Visio drawing does not have a .vdx as extension, open it in Visio and save it as
a .vdx file.
4. Click OK to start importing. This popup another Import Visio dialog box. As the model structure is different among Visio and Visual Paradigm,
this dialog enables users to resolve inconsistency between Visio and VP-UML.
The left hand side of the dialog box represents the structure of Visio drawing, while the right hand side represents the expected outcome in VP-
UML through importing. Users can perform the following actions in this dialog box.
Action Description and steps
Not to import a shape Click on the button beside the shape node and select Not Import in the popup menu.
Rename a shape when Click on the button beside the shape node and select Rename in the popup menu. Then, enter the
importing new name of shape and press the Enter key to confirm renaming/.
Reset the shape to another type Click on the button beside the shape node and select an appropriate shape type to reset to.
5. Click OK when the import is configured. The drawings can then be accessible in the Diagram Navigator. You can then double click on the
diagram node to open the diagram.
2 Import Color and By selecting this option, colors and fonts of the shapes to be imported will remain unchanged. Otherwise, Visual
Font Paradigm's default settings will be applied.
3 Auto Fit Size By selecting this option, shapes' size will be optimized to their minimum possible size. Otherwise, the original size of the
imported shapes will remain unchanged.
4 OK Click to import.
A Rose drawing
2. To import a Rose model into VP-UML, select File > Import > Rose Project... in the main menu of VP-UML.
3 OK Click to import.
Model element can be accessed in the Model Explorer. User can form diagrams with them by dragging and dropping them onto diagrams. You
can then double click on the diagram node to open the diagram.
A Rational drawing
2. To import a Rational model into VP-UML, select File > Import > Rational Model... in the main menu of VP-UML.
3. In the Import Rational Software Architect UML Model dialog box, specify the file path of the .emx file and click OK.
A Rational drawing
2. To import the drawing into VP-UML, select File > Import > Rational DNX... in the main menu of VP-UML.
3. In the Import Rational Diagram DNX dialog box, specify the file path of the .dnx file and click OK.
2. Select XML Files (*.xml) in Save as type and enter the file name in the Save As dialog box.
3. Click Save. This popup the Save as XML File dialog box.
5. Click OK to confirm. This saves an XML file that can be used for importing into VP-UML.
6. To import an ERwin Data Modeler project into VP-UML, select File > Import > ERwin Project(XML)... in the main menu of VP-UML.
8. Click OK to start importing. When import is completed, the Open Imported Entity Relationship Diagram(s) dialog box will appear.
9. Select the diagram(s) to open and click Open to open them. The drawings will then be opened.
3. Specify the file path of the Telelogic Rhapsody Project in the pop-up Import Rhapsody dialog box.
4. Click OK button when the import is configured. The drawings can then be accessible in the Diagram Navigator. You can then double click on
the diagram node to open the diagram.
2. To import a Telelogic System Architect project into VP-UML, select File > Import > Telelogic System Architect ... in the main menu of VP-
UML.
1 File path The path of Telelogic System Architect .xml file to be imported.
2 Import Color and By selecting this option, colors and fonts of the shapes to be imported will remain unchanged. Otherwise,
Font Visual Paradigm's default settings will be applied.
3 Auto Fit Size By selecting this option, shapes' size will be optimized to their possible minimum size. Otherwise, the original
size of the imported shapes will remain unchanged.
4. Click OK to start importing. When import is completed, the message pane will popup, with a notification appear in it. The drawings can then be
accessible in the Diagram Navigator. You can then double click on the diagram node to open the diagram.
To import a NetBeans UML project into VP-UML, select File > Import > NetBeans UML Project... in the main menu of VP-UML.
3. Click OK to start importing. When import is completed, the message pane will pop up with a notification.
The drawings can then be accessible in the Diagram Navigator.
You can then double click on the diagram node to open the diagram.
NOTE: Due to different ways in presenting diagrams in VP-UML and NetBeans, the imported shapes may contain unnecessary spaces in them.
To fit a shape's size, move the mouse cover over it and press on the resource icon at the bottom right of shape. To fit size for all
shapes on a diagram, right click on the diagram background and select Diagram Content > Auto Fit Shapes Size in the popup menu.
2. In the Save dialog box, set the image quality. The higher the quality, the clearer the image, the larger the image size.
NOTE: There are two options for exporting as PNG files - with and without background. With background will export diagram's background color.
Without diagram will ignore the background color by exporting transparent background.
NOTE: You can export VP-UML diagram to native PDF format. Since the exported PDF is of a small size, it can save a lot of space. Also,
because the diagram in PDF is a vector, it is scalable.
There are two different options when you export. For PDF(diagram per page), all the diagrams selected will be exported in the same PDF
file. Each diagram will occupy one page. For PDF(diagram per file), each diagram selected will be exported in one new PDF file.
Export diagrams
1. Select File > Export > Diagrams as Image... from main menu.
1 Output destination The Output destination is the directory where all the exported images are saved to. You can enter the path in
the text field directly, or you can click on the ... button to browse for the directory.
2 Export type To select the image format of the exported image click on the pull-down box beside the Export type field and
select the format you want to use.
There are two options for exporting as PNG files - with and without background. With background will export
diagram's background color. Without diagram will ignore the background color by exporting transparent
background.
You can export VP-UML diagram to native PDF format. Since the exported PDF is of a small size, it can save a
lot of space. Also, because the diagram in PDF is a vector, it is scalable. There are two different options when
you export. For PDF(diagram per page), all the diagrams selected will be exported in the same PDF file. Each
diagram will occupy one page. For PDF(diagram per file), each diagram selected will be exported in one new
PDF file.
3 Quality The quality of image. By applying a higher quality, the images will be more clear, but larger in file size. By
applying a lower quality, the images will look more blur, but smaller in file size.
4 Auto overwrite existing files You can check the Auto overwrite existing files checkbox to allow overwriting of files in the export process.
5 Diagrams The Diagrams pane shows the diagrams in the current project. Check the checkbox beside the diagram you
want to export. The number of selected diagrams is displayed at the bottom of the Diagram pane. The Preview
pane also allows you to preview the exported image of the selected diagram.
7 Preview The Preview pane shows the preview of the exported image of the selected diagram in the Diagrams pane.
8 Preview mode Select the size of the preview image by selecting from the pull-down box beside the Preview mode field.
Selecting Stretch will show the image in scaled size that fits to the preview area, while selecting Real size will
show the image in its actual size.
9 Diagram slicer Click to configure how diagram is sliced into pieces. This is enabled only when the check box for Slice
Diagrams (for slicing all diagrams) is unchecked. For details about slicing diagrams, please refer to the following
section.
11 Text Anti-aliasing Anti-aliasing is a method which handles the staircase pixels of slanted lines and curves to make them look
smoother. You can apply anti-aliasing to the exported images. To apply anti-aliasing to text, check the Text Anti-
aliasing checkbox.
12 Max. Size Maximum size of exported images. If the diagram size is larger than the max. size, it will be resized.
13 Slice Diagrams Enable it to slice all diagrams into pieces to obtain multiple image files for a single diagram. For details, please
refer to the following section.
15 Export image with frame A frame is a border that print around a diagram. By selecting None, frame won't be printed. By selecting
Export with frame, a frame will be added to exported images, making the diagram name show at the top left of
diagram. By selecting Export with border, a black and thin border will be added to exported images.
2 Fixed size A simple strategy which slice exported diagram into pieces that have the same size.
3 Free slicing User can customize how to slice the exported diagram by specifying the position of vertical slices and horizontal slices.
4 Fixed ratio User can customize how to slice the exported diagram by specifying the position of vertical slices and horizontal slices.
13 Zoom fit to Zoom the diagram to make it fit weel on the slicer window.
screen
15 Scale The way of scaling. When configuring slicing for all diagrams, this part will not be displayed.
18 Ruler Shows the size of the diagram. When the slicing strategy Free Slicing is selected, a new row and column can be created by
dragging a new one from the ruler.
19 Slice line Lines that divide the diagram into pieces. The show the vertical and horizontal position that the diagram will be sliced at.
When Free Slicing or Fixed Ratio is selected, the lines can be dragged and moved.
20 Index label Shows the index of the pieces. This index will be printed on the exported fileExporting
as well. multiple diagrams as images P. 959
Slicing strategies
There are three slicing strategies - Fixed Size, Free Slicing and Fixed Ratio. Each gives a distinct way of slicing images.
Fixed size
Fixed Size is a simple strategy which slice exported diagram into pieces that have the same size. User specifies the number of columns and rows to
slice and then the exported diagram will be sliced into specific pieces.
Fixed Size
Free slicing
User can customize how to slice the exported diagram by specifying the position of vertical slices and horizontal slices. It is particularly useful to
prevent a shape from being sliced into pieces.
Free Slicing
Fixed ratio
Fixed Ratio strategy gain the benefit of Fixed Slice and Free Slicing. The width and height of pieces are the same but last row and column. User can
also customize the width and height of sliced pieces. Like Free Slicing, Fixed Ratio is size oriented. User modifies the size of pieces and Diagram
Slicer calculates the number of row and column to slice.
Fixed Ratio
Control by ratio
To control the total size of the exported diagram by specific ratio, select Ratio from the Scale combo box and enter the ratio in the field next to the
combo box. The total size of the exported diagram shows next to that field.
2. Select File > Export > Selection as Image... from main menu.
NOTE: There are two options for exporting as PNG files - with and without background. With background will export diagram's background color.
Without diagram will ignore the background color by exporting transparent background.
NOTE: You can export VP-UML diagram to native PDF format. Since the exported PDF is of a small size, it can save a lot of space. Also,
because the diagram in PDF is a vector, it is scalable.
There are two different options when you export. For PDF(diagram per page), all the diagrams selected will be exported in the same PDF
file. Each diagram will occupy one page. For PDF(diagram per file), each diagram selected will be exported in one new PDF file.
Plugin.xml
A plugin is defined in a XML file (plugin.xml). It includes the information (such as plugin id, provider, required libraries, etc...), custom actions (menu,
toolbar and popup menu) and custom shapes/connector of the plugin.
For working with VP-UML in plugin, there are 4 main components must be known by developers: Model, Diagram, Diagram Element and Action/Action
Controller.
Model element
Model Elements are basic construct of a model. Plugin allows developer to create, retrieve, update and delete model elements through the popup
menu context or through the project (by iterating model elements within a project).
Diagram
Diagram is contains diagram elements on different domain (such as Use Case Diagram, Class Diagram, ERD, etc...).
Plugin allows developer to create, retrieve, update and delete diagrams through the popup menu context or through the project (by iterating diagrams
within a project)
Action/Action controller
Action represents buttons and menus (menu, toolbar and popup menu), which contains the information on outlook (such as label, icon, mnemonic,
etc...) and responses to trigger the function call.
Action is used to represent the button on 3 regions: menu/toolbar, popup menu and diagram toolbar
Action Controller is the control (function call) of actions. Developer needs to implement different Action Controller on different region's actions.
Beginning of plugin.xml
plugin.xml is the base of a plugin, to develop a plugin, should be start from writing the plugin.xml. The basic directory structure is "VP_SUITE_HOME/
plugins/YOUR_PLUGIN_ID/plugin.xml"
For improving the variability of the plugin.xml, a properties file (plugin.properties) can be used for storing the value of the xml. Developer can
assignment the value of the attributes in xml starts with '%', then the value will be read from the properties file. For example
In plugin.xml: <plugin id="sample.plugin name="%plugin.name" .../>
In plugin.properties: plugin.name=sample.plugin
Sample on XML:
< plugin
id= "sample.plugin"
name= "Sample Plugin"
description= "Sample Plugin"
provider= "Visual Paradigm"
class= "sample.plugin.SamplePlugin">
< runtime >
< library path= "lib/sampleplugin.jar" relativePath= "true"/>
</ runtime >
<!-- to be continued -->
</ plugin >
Table shows the description of elements in the plugin.xml.
plugin The root element of plugin.xml, specify the basic information of the plugin (id, name,
provider, etc...)
library (1..*) Specifies the .jar or directory as the classpaths required on the plugin. Such as the classes
of the plugin and some libraries the plugin required.
library (1..*) relativePath (optional, default: true ) Specifies whether the path is relative path.
Description on Code:
VPPlugin (com.vp.plugin.VPPlugin)
This class must be implemented and ref on <plugin class="xxx"... Otherwise, the plugin will not be loaded completely. In fact, the class can do nothing
on it.
The following is the sample code:
package sample.plugin;
public class SamplePlugin implements com.vp.plugin.VPPlugin {
// make sure there is a constructor without any parameters
public void loaded(com.vp.plugin.VPPluginInfo info) {
// called when the plugin is loaded
// developer can get the current plugin's id and the
// current plugin directory (default: %VP_SUITE%/plugins)of VP-UML from the VPPluginInfo.
}
public void unloaded() {
// called when the plugin is unloaded (when the VP-UML will be exited)
}
}
actionSets It is a collection of ActionSet. There 2 kinds of ActionSet: actionSet and contextSensitiveActionSet. actionSet is a set of
actions which will be shown on menu/toolbar or diagram toolbar. contextSensitiveActionSet is set of actions which will be
shown on popup menu.
There are differences on xml definition and code implementation of the 3 kinds of Actions (menu/toolbar, popup menu, diagram toolbar).
Below is the menupaths required for implementing the menus shown in the above images.
2 Tools/Report Tools/Report Under the Tools menu, after the Report menu
3 Tools/Report/# Tools/Report/# Under the Tools menu, and under the Report menu, place on the
front
4 Tools/Report/Generate HTML Tools/Report/Generate HTML Under the Tools menu, and under the Report menu, after the
Report Report Generate HTML Report menu item
Sample on XML:
< actionSet id="sample.plugin.actions.ActionSet1">
< toolbar
id= "sample.plugin.actions.Toolbar1"
orientation= "north"
index= "last"/>
< menu
id= "sample.plugin.actions.Menu1"
label= "Sample Menu 1"
mnemonic= "M"
menuPath= "Tools/Report"/>
< action
id= "sample.plugin.actions.Action1"
actionType= "generalAction"
label= "Sample Action 1"
tooltip= "Sample Action 1"
icon= "icons/red.png"
style= "normal"
menuPath= "Tools/Report"
toolbarPath= "sample.plugin.actions.Toolbar1/#">
< actionController class= "sample.plugin.actions.ActionController"/>
</ action>
actionSets It is a collection of
ActionSet. There 2
kinds of ActionSet:
actionSet and
contextSensitiveActionSet.
actionSet is a set of
actions which will be
shown on menu/toolbar
or diagram toolbar.
contextSensitiveActionSet
is set of actions which
will be shown on popup
menu.
toolbar (0..*) orientation [north | east |south | west] Specifies which side will
be the toolbar placed on.
action (0..*) actionType [generalAction | shapeAction | connectorAction] (optional, default: generalAction) There are 3 types:
generalAction,
shapeAction and
connectorAction. As the
action on menu/toolbar,
generalAction should be
assigned.
Description on Code:
contextTypes all [true | false] (optional, default: false) Specify whether all the types of the models, diagram elements
and diagrams will be considered by this actionSet.
exclude Specify the model, diagram element or diagram type will not
be considered by this ActionSet. (This will be ignored if the
contextType's attribute 'all' is assigned 'false'.
actionController Specifies the Action Controller for the action (the parent node
in the xml)
actionController class The class name of the Action Controller. For the
action on popup menu, it is required to implement
com.vp.plugin.action.VPContextActionController.
Description on Code:
VPContextActionController (com.vp.plugin.action.VPContextActionController)
This class is used to perform the function call when the action is clicked. One Action Controller class refers to multi Actions is allowed.
Sample:
package sample.plugin.actions;
import java.awt.event.ActionEvent;
public class ContextActionController implements com.vp.plugin.action.VPContextActionController {
// make sure there is an constructor without any parameters
public void performAction(
com.vp.plugin.action.VPAction action,
com.vp.plugin.action.VPContext context,
ActionEvent e
){
// called when the button is clicked
}
public void updated(
com.vp.plugin.action.VPAction action,
com.vp.plugin.action.VPContext context
){
// when the popup menu is selected, this will be called,
// developer can set the properties of the action before it is shown (e.g. enable/disable the menu item)
}
}
VPContext ( com.vp.plugin.action.VPContext)
Context will be passed into the Action Controller when the popup menu is shown or action is trigger. It is what the user selected on the diagram, can be
model, diagram element or/and diagram.
A diagram may contain many diagram elements, when user right-click on the diagram element or the diagram, a popup menu will be shown. So, the
context may be diagram element or diagram. However, the diagram element must be contained by diagram, then if popup menu shown on a diagram
element, the context must contain both diagram element and diagram. And the diagram element always represents for a model, so that is possible the
context contains model, diagram element and diagram as same time. However, sometime, the popup menu is shown for a model only (e.g. select on
an attribute of a class, because there is no diagram element for the attribute, the class's diagram element will be contained in the context).
Action It is a collection
of menu, action,
separator on
the popup
menu of the
plugin. The child
elements should
be ordered if
they have the
relationship on
the position
(e.g. developer
prefers Action1
is placed into
Menu1, then
please define
the Menu1 on
the xml first
Action actionType [generalAction | shapeAction | connectorAction] (optional, default: generalAction) There are
3 types:
generalAction,
shapeAction
and
connectorAction.
As the action for
custom shape,
"shapeAction"
should be
assigned.
For custom
connector,
"connectorAction"
should be
assigned.
shapeCreatorInfo If the
actionType is
"shapeAction",
shapeCreatorInfo
is required. It is
used to specify
the details of the
custom shape.
Creating model
Developer can use the model element factory ( com.vp.plugin.model.IModelElementFactory) to create the model. Or based on a parent model (
com.vp.plugin.model.IModelElementParent) to create a child model.
IModelElementFactory can be access by IModelElementFactory.instance(). It provides the functions to create all the models.
IModelElementParent is subclass of IModelElement. It provides the function to create the child into it. If the parent class is more specified, it may
support a more details function to create the child. For example, IClass is subclass of IModelElementParent, it provides createOperation() to create
an operation into it.
Sample on Code:
/*
* create model by IModelElementFactory
* result of the 2 methods: "class model is created and added into the project"
*
// assume in a code segment
IClass classModel1 = IModelElementFactory.instance().createClass();
IClass classModel2 = (IClass) IModelElementFactory.instance().create(IModelElementFactory. MODEL_TYPE_CLASS);
/*
* create model by IModelElementParent
* result of the first 2 methods, "operation model is created and added into the class model"
* result of the last method, "actor model is created and added into project", because actor cannot be the child of class model
*/
// assume in a code segment
IOperation operationModel1 = classModel1.createOperation();
IOperation operationModel2 = (IOperation) classModel1.create(IModelElementFactory. MODEL_TYPE_OPREATION);
IActor actorModel1 = (IActor) classModel1.create(IModelElementFactory. MODEL_TYPE_ACTOR);
Retrieving model
Developer can use the project ( com.vp.plugin.model.IProject) or the context ( com.vp.plugin.action.VPContext) from ActionController to retrieve
the models.
IProject is the project of VP-UML. The project contains all models, diagram and diagram elements. It provides function ( modelElementIterator()) for
the developer to iterate the models.
VPContext is the context of a popup menu. Developer can access the context by popup menu's action controller (
com.vp.plugin.action.VPContextActionController). Context may contain a model element if the popup menu is shown on a diagram element or
model.
Sample on Code:
/*
* retrieve model by IProject
*/
// assume in a code segment
IProject project = ApplicationManager.instance().getProjectManager().getProject();
Iterator iter = project.modelElementIterator();
while (iter.hasNext()) {
IModelEmenet modelElement = (IModelElement) iter.next();
// model element retrieved
}
/*
*retrieve model by VPContext
*/
// assume on a sub-class of com.vp.plugin.action.VPContextActionController
Sample on Code:
// assume in a code segment
ViewManager viewManager = ApplicationManager.instance().getViewManager();
viewManager.showMessage( "Thank you for reading VP-UML Plugin Support User's Guide. >=)", "sample.plugin");
Showing simple message dialog
In Swing, we may use the javax.swing.JOptionPane to show a message dialog (e.g. JOptionPane.showMessageDialog(...)). ViewrManager
provides the functions which simulate the JOptionPane. ViewManger provides a set of showXXXXDialog(...) functions for showing the dialog. The
signature of the functions are same with the JOptionPane. Developer need not feel strange on calling the showXXXXDialog(...) functions.
After all, restart VP-UML will see the plugin available. If not, make sure the code was written correctly and can be compiled, and you have setup the
above folder structure correctly.
Executing ExportDiagramImage
-diagram A list of diagram required to export images. User can enter "*" for representing all diagrams, to supply the names of diagram_1
diagrams, or to supply a text file which includes the names of all diagrams diagram_2
-type [optional] Type of diagrams. Here are the possible types: png
• png
• png_with_background
• jpg
• svg
• pdf
Exporting XMI
To export XMI from a project through command line:
1. Browse the scripts folder under the VP Suite installation directory.
Executing ExportXMI
-type [optional] Version of XMI. Unless specified, the lastly generated version will be selected. Here are the possible options: 2.1
• 1.0
• 1.2
• 2.1
• 2.1UML2
Importing XMI
To import XMI to a project through command line:
2. Copy the script file ImportXMI and paste to the bin folder of VP Suite installation directory.
Executing ImportXMI
Exporting XML
To export XML and images from a project through command line:
1. Browse the scripts folder under the VP Suite installation directory.
Executing ExportXML
-out Folder for storing the exported XML and images C:\Demo\Output
Importing XML
To import XML to a project through command line:
2. Copy the script file ImportXML and paste to the bin folder of VP Suite installation directory.
Executing ImportXML
Executing GenerateORM
-out Folder for storing the generated files including the source code, required libraries and mapping XML C:
\Demo
\Output
Executing GenerateReport
-type Type of report to generate. Here are the possible options: pdf
• html
• pdf
• word
-all [optional] By default, only the selected diagrams (saved in vpp) will be covered when generating report. By including -all, all -
diagrams will be covered. all
Executing InstantGenerator
-template [optiona] The path of template folder. Unless specified, the default folder will be selected. C:
\MyTemplat
-lang [optional] Specify the language to generate. Unless specified, the lastly selected language (saved in project file) will be C
generated. Here are the possible options: +
• Java +
• C#
• .NET
•
• ODL
• ActionScript
• IDL
• C++
• Delphi
•
•
• Python
• Objective-C
• Ada95
• Ruby
NOTE: Code generation through command line generates only classes selected to generate when running VP-UML. In other words, you must at
least generate once in VP-UML in order to make command line generation work.
Executing InstantReverse
-lang Specify the language of the source code to reverse. Here are the possible options: Java
• Java
• "C++ Source"
• ".NET dll or exe files"
• "CORBA IDL Source"
• Ada 9x Source"
• XML
• "XML Schema"
• Hibernate
• "PHP 5.0 Source"
• "Python Source"
• Objective-C
pathtype Useful only for Java, pathtype defines the type of the path supplied for -path. Here are the possible options: file
• file
• folder
• zip
sourcetype Useful only for Java, sourcetype defines the type of source to reverse. Here are the possible options: source
• source
• class
Executing JavaCodeSync
-generate | -reverse Action to perform. Include -generate to indicate the update of code from model. Include -reverse to indicate the -
update of model from code. generate
Executing ProjectPublisher
Executing UpdateTeamworkProject
2. Copy the script file build.xml and paste to the bin folder of VP Suite installation directory.
4. Modify task(s) specific parts by changing the values of parameters. For details about the parameters, refer to previous sections.
To Perform Printing
Print Print the diagram(s). The Print dialog box will be opened.
Quick Print Print the diagram(s) without previewing them. The Quick Print dialog box will be
opened.
Page Setup Set up the page properties, such as paper size and orientation.
Use Gradient Color Select the use gradient color in printout. Since printing gradient color will use up
lots of memory, it is recommended to turn this option off for better performance.
Paper Base Layout/ Diagram Base If the Fit to Pages option is chosen, and there are multiple pages in the printout,
/ Layout choosing Paper Base Layout will cause the distribution of pages to be paper-
oriented (the diagram size is ignored in arranging the preview); while choosing
Diagram Base Layout will cause the distribution of pages to be diagram-
oriented. Note that this option affects the preview only; the order of the printout
remains unchanged.
Paper Place Style Change the order of the printout. A large diagram is divided into many pages,
/ choosing From left to right will arrange the printout order from the pages on the
left to the pages on the right, while choosing From top to bottom will arrange
the print order from the pages on the top to the pages on the bottom.
Fit to Ratio Set the diagram size to fit to the specified ratio.
Fit to Pages Set the diagram to be printed on the specified number of pages.
Overlapping Set the percentage of the margins to overlap among adjacent pages.
Show/ Hide Clip Marks on Page Select/ deselect to show/hide the clip marks on the printout.
Edit Header/ Footer Edit the header and the footer of the printout.
Multiple Page Mode Switch to the Multiple Page Mode to set the multiple page options.
Close Print Preview Close the print preview pane and return to the design area.
Details of toolbar
Diagram preview
2.
Click the Print button on the Print preview toolbar. The Print dialog box will be shown.
3. Select a specific printer, the page range and the number of copies to be printed. You may click the Properties... button to configure the printer-
specific properties as well.
4. Click OK to start printing.
1.
Click the Page Setup button on the toolbar. The Page Setup dialog box will appear.
2. You can click the Size drop-down menu to select the paper size for printing.
3. You can check either Portrait or Landscape udner Orientation.
4. You can enter the value into the Left, Right, Top and Bottom text fields to adjust the size of the corresponding margin.
5. Click OK to confirm the settings.
Adjusting margins
1. Click the Adjust Margin button on the toolbar. The margin setting page will be shown in the preview area.
2. You can edit the margins size by entering the sizes into the text fields. Alternatively, click the spinner buttons to increase/ decrease the margin sizes.
3. Click the Finish Adjust Margin button when you finish configuring the margin settings. The margin sizes will then be updated.
Zooming pages
Diagrams can be zoomed in or zoomed out according to the user's preference.
1. Click the Zoom drop-down menu to select the desired zoom ratio.
To select a layout of the preview, click the Paper Base Layout button or Diagram Base Layout button on the toolbar. A pop-up menu where
you can choose the layout will appear.
Fit to ratio
Fit to Ratio is used to resize the diagrams in the printout to a specific ratio.
Click the Fit to drop-down menu and select Ratio.
You can enter the ratio into the text field. After editing the ratio, the diagrams in the printout will be resized at once.
Fit to ratio
Fit to pages
Fit to Pages is used to split the diagram to a desired number of pages when printing.
1. Click the Fit to drop-down menu and select pages.
3. Click the row-column combination to select it (note that you can click and drag on the page selector to extend the selection). The diagram will be
split into multiple pages by the rows and columns that you have selected.
Fit to page
1. Input the overlapping percentage and press Enter in Overlapping text field.
2. The printing area near the boundaries of the pages will be duplicated through the input value of overlapping percentage.
Clip marks
To show clip marks on the printout, click the Show Clip Marks on Page button . The boundaries of the pages will be surrounded by clip marks. To
hide the clip marks, click the Hide Clip Marks on Page button again.
To edit the header/ footer of the printout, click the Edit Header/Footer button on the toolbar. You will then switch to the edit header/footer pane.
You can edit the header and the footer in the Header panel and the Footer panel respectively. Each of the panel consists of the Left Section, Center
Section and the Right Section, which represents the position that the content will be located in the header/footer.
Select Font Select the font format. Note that you have to click the section you want its font to be formatted before you start
setting the font format.
Insert Page Number Insert the page number. Note that you have to click the section you want page number to be inserted into before
you click it.
Insert Number of Insert the total number of pages. Note that you have to click the section you want the number of pages to be
Pages inserted into before you click it.
Insert Date Insert the date that the printing starts. Note that you have to click the section you want the date to be inserted into
before you click it.
Insert Time Insert the time that the printing starts. Note that you have to click the section you want the time to be inserted into
before you click it.
Insert File Name Insert the file name of the VP-UML project. Note that you have to click the section you want the file name to be
inserted into before you click it.
Insert Project Name Insert the name of the VP-UML project. Note that you have to click the section you want the project name to be
inserted into before you click it.
Insert Diagram Name Insert the diagram name. Note that you have to click the section you want the diagram name to be inserted into
before you click it.
Insert Parent Package Insert the parent package. Note that you have to click the section you want the parent package to be inserted into
before you click it.
Insert Parent Hierarchy Insert the parent hierarchy. Note that you have to click the section you want the parent hierarchy to be inserted into
before you click it.
After you have finished editing the header/footer, click the Close Edit Header/Footer button to switch to the print preview mode. A sample page
with the header and footer is shown in the figure below:
Click the icon behind Page Style to change the printout order. Considering a large diagram is divided into many pages, choosing From left to right
will arrange the printout order from the pages on the left to the pages on the right, while choosing From top to bottom will arrange the print order from
the pages on the top to the pages on the bottom.
After you have finished configuring the multiple page settings, click the Close Multiple Page Mode button to close it.
1 Print Range Click on either of the below options to specify the print range.
All - Print all the diagrams within the current project
Active - Print only the active diagram
Diagrams - Check from the diagram tree to select the diagram(s) for printing
2 Scaling Select No scaling to print with diagrams' original size. Numbers of pages used for each diagram are subject to the scale of
diagrams. Select Fit to pages to print with specified number of pages per diagram with respect to the specified number of
rows and columns.
4 Page Setup... Page Setup allows you to specify the page size, the orientation as well as the margins of the pages.
Administration
Administration is the process of setting up projects and users (i.e. team members), and deciding the access rights of members against projects.
Administration is a must in order to start working.
Checkout project
Checkout project is a process done by team members, for getting a project from repository to start working with. Team members should login into the
Teamwork Server in VP-UML, then checkout the projects to work with, provided that they have the permission to do so, as granted by administrator.
Commit
Commit is the process of uploading changes done in working copy to server. As team members make changes in a project, they can share their works
by committing those changes to the server. VP-UML will try to merge changes from working copy to server copy. When merging, there may be conflict
when any changes a team member made cause an unresolvable contradiction with changes made by others. Team member is required to decide
whether to keep his/her change (i.e. overwrite) or to take the co-worker’s change (i.e. revert). All conflicts must be resolved in order to proceed
with committing.
Conflict
Conflict is a situation that happens when committing or updating. It occurs during the merging between working and server copy of project, when
a contradiction is detected between them. For example, a team member has renamed a shape from A to B and has committed the change. Then,
another team member has renamed the same shape from A to C and attempt to commit. Due to difference in the name of use case, a conflict is
occurred. Whenever a conflict occurred, users have to resolve it or else to abort before commit/update operation.
A conflict is occurred
Branching
Branching is the process of creating a branch from trunk (i.e. main development flow), for isolating changes that are not supposed to be available on
trunk, either at the moment or permanently. By working in a branch, team members can carry out half-broken or risky changes without worrying the risk
of damaging the work in trunk. Once the works done in branch is examined, and confirmed alright, team member can make changes available in trunk
through merging. Merging can also be done from trunk to branch to ensure that the branch is always up-to-date.
Tagging
Tagging is the process of producing a snapshot (i.e. tag) of a project in time. People often create tags for archiving releases of works. Therefore, tags
are often named as release-1.0 where 1.0 is the number of version. Since a tag is a snapshot, team members can never commit under a tag.
Revision history
Every time a team member performs a commit with success, a new revision is created as a snapshot of project. More and more revisions will be
created through repeated committing. A list of revisions that shows the changes of project is called the revision history. In VP-UML, you can review the
works done in specific revision(s) by exporting them in project files. You can identify the differences between revisions by comparing them.
A list of revisions
2. When the Login to the Teamwork Server dialog box pops out, enter your server host, user name and password respectively. Finally, click OK
to login to the teamwork server.
3. In the Manage Project dialog box, select your project and click > button to manage it. Click OK to proceed.
2 Toolbar Login: Log into the server. After you choose it, you will be able to execute all actions.
Logout: Log out the server. After you choose it, you will not be able to execute any actions.
Manage Project: Select a project that you get involved in.
Import Project to Repository: Import a new project to the server on the list.
Update: Update the latest copy of project from the server to your computer.
Commit: Commit your current modified project to the server.
Checkout: Click it to checkout the project selected in Projects list. It will be disabled when the selected project has already been
checked out.
Open: Click it to open the checkout project on your computer.
Revert...: Click it to undo un-committed changes made on the local project copy. If no changes have been made, the project will go
back to the original state.
Check for Update: Click it to check whether the project is up-to-date or not.
Tag...: Create a new tag for your current project. It allows you to produce a static release version of project.
Branch...: Create a new branch for your current project. It becomes a duplication of project to perform isolated changes.
Merge...: Combine the selected branch(es) with the trunk (main project). When some changes are made in branch, it will be made
in trunk as well.
Switch...: Switch from a branch/ tag to another branch/ tag or from the trunk (main project) to a branch/ tag and vice versa.
Delete Branch...: Select a branch to delete, for preventing accidental modifications in branch.
3 Show all By checking it, the list of all eligible users who have logged into the server in this workspace will be displayed. On the contrary, by
user unchecking it, only the current user will be displayed.
4 Repository It refers to the list of available project(s). Select All from the drop-down menu means all projects managed by all eligible users who have logged into Teamwork Server in this
workspace will be listed. On the other hand, the project(s) managed by a specific user can be selected from the drop-down menu. If you uncheck Show all user and do not
select the current user in Repository, no project will be listed.
7 File path The path of the selected project file. It is shown only when project is checked out from the server.
8 Checkout It displays the date and time of your first checkout for the project.
time
9 Revision It displays the revision of your local project copy. Note that the revision here does not always mean the latest revision on the
server.
10 Status It displays the status of selected project, such as "Not Checked Out" will be shown when the project has not been checked out yet.
11 Comment It shows the textual description of selected project written by administrator when creating project.
12 Update Update the latest project from the server to your computer.
15 Open Click it to open the checkout project on your computer. If the project has not checked out yet, it will perform a checkout prior to
Project opening project.
18 Show drop-down menu Select the number of latest project revision to view from the drop-down menu.
19 Project revisions It lists all the latest project revisions. The number of revisions is in accordance with the show drop-down menu.
21 Export Export selected revisions...: Select a directory for exporting the selected revision of project.
Export all revisions from repository...: Select a directory for exporting all revisions of project from repository.
23 Compare... After you have selected two revisions, click it to compare the differences between them.
24 Commit Comment A textual description of commit given by you or your teammates before committing.
25 Modified model elements It displays the modified model elements of the selected revision of project.
26 Modified diagrams It displays the modified diagrams of the selected revision of project.
27 Modified diagram It displays the modified diagram elements of the selected revision of project.
elements
Select a project
When the Teamwork Client dialog box pops out, select the project under Projects, and click Checkout. After the selected project has been checked
out, click Open Project.
After that, the project has been downloaded from the server to your computer and you can start working on it.
1 toolbar Select previous conflict: Select the previous conflict you made in current copy.
Select next conflict: Select the next conflict you made in current copy when a conflict is found during
committing.
Overwrite all conflicts: Keep all modification you made in current copy when a conflict is found during
committing.
Revert all conflicts: Accept all modification other team members made previously and discard all your
modification when a conflict is found during committing.
Reset all conflicts: Cancel the decision you have just made for dealing with all conflicts when a conflict is
found during committing.
Overwrite selected conflicts: Keep the selected modification you made in current copy when a conflict is
found during committing.
Revert selected conflicts: Accept the selected modification other team members made in current copy
when a conflict is found during committing.
Reset selected conflicts: Cancel the decision you have just made for dealing with the select conflict(s)
when a conflict is found during committing.
Select previous change: Select the previous modification you have made in the sequence of list
displaying in Display window.
Select next change: Select the next modification you have made in the sequence of list displaying in
Display window.
2 Filter Select a specific scope for previewing the to-be-committed project, including: All, Update from Server,
Commit, Conflict, Created Elements, Modified Element and Deleted Elements.
3 Element Filter Select a specific scope for previewing the to-be-committed model elements, including: All, TaggedValue,
TaggedValueContainer and UseCase.
4 Display window It displays a specific scope for previewing the to-be-committed project/ model elements in accordance
with the selection of Filter/ Element Filter.
9 Latest server revision It shows the number of latest revision in the server.
10 Edit the commit comment You can give a comment for your current commit by typing here.
11 Choose a previously entered You can search and select a comment that you entered previously in this drop-down menu.
comment
13 Cancel Click Cancel to cancel committing and close the dialog box.
16 Server preview window It displays the original revision in server for previewing.
17 Local modified preview window It displays the modified and to-be-committed revision for previewing.
Choosing Overwrite means keeping your modified copy while choosing Revert refers to accept others' copy.
NOTE: Conflicts occur only when the same property of same shape you and other team members have made.
You can preview the choice you made by clicking Preview button. The left window shows the image before update while the right window shows the
image after update. Click OK when you want to confirm the modification(s).
NOTE: Conflicts occur only when the same property of same shape you and other team members have made.
When the Create Branch dialog box pops out, enter a name in Branch Name for your new branch and select an option from the drop-down menu.
Finally, click OK to confirm.
When the Merge dialog box pops out, select a branch you want to merge from. A specified revision of project can be merged by checking From
revision and selecting ... button from From revision and To revision respectively. Click OK to confirm selecting.
In Create Tag dialog box, enter the name for a new tag in Tag Name. Click OK to proceed.
3. In Select Directory dialog box, select an existing folder or make a new folder for storing the selected revision(s). Click OK button to proceed.
Select a directory
Choosing Export all revision from repository... in Teamwork Client dialog box
3. In Select Directory dialog box, select an existing folder or make a new folder for storing all revisions. Click OK button to proceed.
Administration
Administration is the process of setting up Subversion server and users (i.e. team members). Administration is a must in order to start working.
Import project
Import project is a process done by either administrator or team members, for creating a project in repository to start working with. Team members
should login into the Subversion in VP-UML, then import a new, an existing or current project into the server.
Checkout project
Checkout project is a process done by team members, for getting a project from repository to start working with. Team members should login into
Subversion in VP-UML, then checkout the projects to work with, provided that they have the permission to do so, as granted by administrator.
Checkout a project
Commit
Commit is the process of uploading changes done in working copy to server. As team members make changes in a project, they can share their works
by committing those changes to the server. VP-UML will try to merge changes from working copy to server copy. When merging, there may be conflict
when any changes a team member made cause an unresolvable contradiction with changes made by others. Team member is required to decide
whether to keep his/her change (i.e. overwrite) or to take the co-worker’s change (i.e. revert). All conflicts must be resolved in order to proceed
with committing.
Update
Update is the process of refreshing the working copy by merging changes that others had made and committed to server before. Similar to commit,
update is a process of merging differences instead of overwriting. If your changes overlap the changes others had made, you will be asked to resolve
conflict. All conflicts must be resolved in order to proceed with updating.
A conflict is occurred
Branching
Branching is the process of creating a branch from trunk (i.e. main development flow), for isolating changes that are not supposed to be available on
trunk, either at the moment or permanently. By working in a branch, team members can carry out half-broken or risky changes without worrying the risk
of damaging the work in trunk. Once the works done in branch is examined, and confirmed alright, team member can make changes available in trunk
through merging. Merging can also be done from trunk to branch to ensure that the branch is always up-to-date.
Tagging
Tagging is the process of producing a snapshot (i.e. tag) of a project in time. People often create tags for archiving releases of works. Therefore, tags
are often named as release-1.0 where 1.0 is the number of version. Since a tag is a snapshot, team members can never commit under a tag.
Revision history
Every time a team member performs a commit with success, a new revision is created as a snapshot of project. More and more revisions will be
created through repeated committing. A list of revisions that shows the changes of project is called the revision history. In VP-UML, you can review the
works done in specific revision(s) by exporting them in project files. You can identify the differences between revisions by comparing them.
A list of revisions
Revert revision
2. When the Login to the Teamwork Server dialog box pops out, select Subversion from the drop-down menu of Server. Enter user name,
password and repository respectively. Click OK button to proceed.
3. In the Manage Project dialog box, select your repository and click OK button to proceed.
2 Toolbar Login: Log into the server. After you choose it, you will be able to execute all actions.
Logout: Log out the server. After you choose it, you will not be able to execute any actions.
Manage Project: Select a project that you get involved in.
Import Project to Repository: Import a new project to the server on the list.
Update: Update the latest copy of project from the server to your computer.
Commit: Commit your current modified project to the server.
Checkout: Click it to checkout the project selected in Projects list. It will be disabled when the selected project has already been
checked out.
Open: Click it to open the checkout project on your computer.
Revert...: Click it to undo un-committed changes made on the local project copy. If no changes have been made, the project will go
back to the original state.
Check for Update: Click it to check whether the project is up-to-date or not.
Tag...: Create a new tag for your current project. It allows you to produce a static release version of project.
Branch...: Create a new branch for your current project. It becomes a duplication of project to perform isolated changes.
Merge...: Combine the selected branch(es) with the trunk (main project). When some changes are made in branch, it will be made
in trunk as well.
Switch...: Switch from a branch/ tag to another branch/ tag or from the trunk (main project) to a branch/ tag and vice versa.
Delete Branch...: Select a branch to delete, for preventing accidental modifications in branch.
3 Repository It refers to the list of available project(s). Select All from the drop-down menu means all projects managed by all eligible users who have logged into SVN in this workspace
will be listed.
6 File path The path of the selected project file. It is shown only when project is checked out from the server.
7 Checkout It displays the date and time of your first checkout for the project.
time
8 Revision It displays the revision of your local project copy. Note that the revision here does not always mean the latest revision on the
server.
9 Status It displays the status of selected project, such as "Not Checked Out" will be shown when the project has not been checked out yet.
11 Comment It shows the textual description of selected project written by administrator when creating project.
12 Update Update the latest project from the server to your computer.
15 Open Click it to open the checkout project on your computer. If the project has not checked out yet, it will perform a checkout prior to
Project opening project.
18 Show drop-down menu Select the number of latest project revision to view from the drop-down menu.
19 Project revisions It lists all the latest project revisions. The number of revisions is in accordance with the show drop-down menu.
21 Export Export selected revisions...: Select a directory for exporting the selected revision of project.
Export all revisions from repository...: Select a directory for exporting all revisions of project from repository.
23 Compare... After you have selected two revisions, click it to compare the differences between them.
24 Commit Comment A textual description of commit given by you or your teammates before committing.
25 Modified model elements It displays the modified model elements of the selected revision of project.
26 Modified diagrams It displays the modified diagrams of the selected revision of project.
27 Modified diagram It displays the modified diagram elements of the selected revision of project.
elements
When the Manage Project dialog box pops out, click OK button when no other team member has been checkout any project before. You may select a
specific project when other team members have been checkout out projects before.
When the Teamwork Client dialog box pops out, click Import Project to Repository button.
NOTE: If you have an active project, the option of Currently opened project will be available.
After that, the project has been downloaded from the server to your computer and you can start working on it.
1 toolbar Select previous conflict: Select the previous conflict you made in current copy.
Select next conflict: Select the next conflict you made in current copy when a conflict is found during
committing.
Overwrite all conflicts: Keep all modification you made in current copy when a conflict is found during
committing.
Revert all conflicts: Accept all modification other team members made previously and discard all your
modification when a conflict is found during committing.
Reset all conflicts: Cancel the decision you have just made for dealing with all conflicts when a conflict is
found during committing.
Overwrite selected conflicts: Keep the selected modification you made in current copy when a conflict is
found during committing.
Revert selected conflicts: Accept the selected modification other team members made in current copy
when a conflict is found during committing.
Reset selected conflicts: Cancel the decision you have just made for dealing with the select conflict(s)
when a conflict is found during committing.
Select previous change: Select the previous modification you have made in the sequence of list
displaying in Display window.
Select next change: Select the next modification you have made in the sequence of list displaying in
Display window.
2 Filter Select a specific scope for previewing the to-be-committed project, including: All, Update from Server,
Commit, Conflict, Created Elements, Modified Element and Deleted Elements.
3 Element Filter Select a specific scope for previewing the to-be-committed model elements.
4 Display window It displays a specific scope for previewing the to-be-committed project/ model elements in accordance
with the selection of Filter/ Element Filter.
9 Latest server revision It shows the number of latest revision in the server.
10 Edit the commit comment You can give a comment for your current commit by typing here.
11 Choose a previously entered You can search and select a comment that you entered previously in this drop-down menu.
comment
13 Cancel Click Cancel to cancel committing and close the dialog box.
16 Server preview window It displays the original revision in server for previewing.
17 Local modified preview window It displays the modified and to-be-committed revision for previewing.
Choosing Overwrite means keeping your modified copy while choosing Revert refers to accept others' copy.
NOTE: Conflicts occur only when the same property of same shape you and other team members have made.
You can preview the choice you made by clicking Preview button. The left window shows the image before update while the right window shows the
image after update. Click OK when you want to confirm the modification(s).
NOTE: Conflicts occur only when the same property of same shape you and other team members have made.
The three options in the drop-down menu are Start working in branch, Checkout branch and Stay in trunk. Selecting Start working in branch
means you create, checkout and open a new branch and then start working on it. Selecting Checkout branch means you create and checkout a new
branch, but just keep it in repository for working on it later on. Selecting Stay in trunk mean you create a new branch, but do not checkout it out and do
not show it in repository either.
After you have finished creating a branch and have committed it, you can merge it back into the trunk.
When the Merge dialog box pops out, select a branch you want to merge from by clicking the ... button. A specified revision of project can be merged
from/ to by checking Revision and clicking Show Log ... button. Click OK to confirm selecting.
Tagging P. 1082
In Create Tag dialog box, enter the name for a new tag in Tag Name. Select an option for Create copy in repository from. Check HEAD revision in
the repository if you want to create a tag from the latest revision of trunk while check Specific revision in the repository if you want to create a tag
from a specific revision. Click OK button to proceed.
Tagging P. 1083
Revert local modification
Since VP teamwork collaboration allows the feature of revert, you can undo all modifications you made in the local project copy when the changes
haven't been committed yet.
After you made some changes on your current project, you can undo them through the main menu or teamwork client dialog box.
To undo all non-committed changes through the main menu:
After entering VP-UML, select Tools > Teamwork > Revert from the main menu.
3. In Select Directory dialog box, select an existing folder or make a new folder for storing the selected revision(s). Click OK button to proceed.
Select a directory
Choosing Export all revision from repository... in Teamwork Client dialog box
3. In Select Directory dialog box, select an existing folder or make a new folder for storing all revisions. Click OK button to proceed.
Login CVS
Server host The server host, which can be host name or IP address
Remember Check to memorize the password so that you don't need to enter again
password
Use proxy Check if proxy is needed for connecting to server. When checked, you will need to enter proxy host.
4. Click on the > button in the middle of the dialog box to add them into project selection.
5. Click OK to proceed. This end up showing the Teamwork Client dialog box.
Region Description
To manage projects, which enables you to add or remove projects from the list of managed projects.
To create a project in server by importing one into it. You may create a blank new project, or import an existing project file to start
with.
To open the project selected in Projects list. If the project is not checked out yet, it will be checked out automatically.
Repository To update the Projects list by showing only projects in certain repository.
Project Details Details of selected project, including the name, revision and status.
Project details
Field Description
Comment The comment of project entered by the administrator when creating project.
Revisions
Region Description
Show: To list certain amount of revisions, such as all, last 10, last 20, etc.
[Revert] By reverting a selected revision, this means to undone changes made in that revision.
CVS path The filepath of cvs.exe. By default, the one in installation folder will be picked up
Connection type The type of connection with CVS server, which can be pserver, ext, ssh
Port The port of connecting to CVS server. To specify one, check User port and enter the port number
Remember Check to memorize the password so that you don't need to enter again
password
Field Description
Create folder for project Create a folder in repository for storing the project. The folder will be of same name as the project.
Project file Create new project - Start with a blank, new project
Import existing project - Start by using an existing project file
6. Choose Create new project or Import existing project from Project file. Create new project will import a blank project into teamwork server,
Import existing project will import an existing VP-UML Project file (*.vpp) into teamwork server as first revision.
NOTE: Please make sure the user login to Teamwork Client has Create Project permission
Select repository
Input comment
3. In Manage Project dialog, expand the repository node and select the project to checkout, click > button to add project. Click OK button to close
the dialog.
Manage projects
Open project
Project opened
Modified project
2. Show Teamwork Toolbar by right click on the Toolbar, select Teamwork if not selected already.
Commit project
5. On the bottom of dialog, click the Preview tab to visually preview the changes in diagram. The selected shape is highlighed in purple.
6. After review the changes, click the Comment tab and input the comment for commit. Click OK button to start commit.
Modified project
Conflict Revision The revision that cause conflict with the committing/updating action.
[Revert] Click on revert the conflict selected in tree. Resolving conflicts P. 1107
4. Select the conflict element, click Overwrite selected conflicts button on the toolbar to overwrite other user's change.
You can also click Overwrite all conflicts or Revert all conflicts to overwrite or revert all conflicts at once.
5. After resolve conflict, the preview will be enabled to visualize the final result.
6. You can change your mind by click Reset selected conflicts or Reset all conflicts button. Then overwrite or revert the conflict again.
Reset conflicts
7. After all conflicts was resolved, you can now input comment and click OK button to commit.
2. Similar to commit, you can review the change and preview the diagram in Update dialog.
Update dialog
3. If there are conflicts, resolve it similar to commit, but the changes will apply to local project instead of commit to server immediately.
Updated project
Checking status
1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Select Project > Check Update from menu.
4. You can see the status showing Has update or Up-to-date, it also indicate local project status (local project not modified) or (local project
modified).
Project status
Modify project
Reverted project
Open project
Revision tab
Select revision
Revert button
NOTE: You may make multiple selection by selecting one revision, pressing the Control key, and selecting the rest. Note that a non-consecutive
revision selection is not revertable.
8. A new revision with the reverted changes was created in server, and opened in VP-UML.
Reverted project
Open button
Compare button
Compare differences
Export buttons
Select directory
8. You'll found the selected revisions was exported to the select directory.
Exported revisions
Stay in head
Select branch
Branch project
Merge dialog
6. Finally, review the changes in Commit dialog. Input comment and click OK to commit.
7. The branch project now contains the changes from HEAD.
HEAD project
3. Select Project > Merge... from menu, or click Merge... button from toolbar.
Merge dialog
5. The Merge Project dialog show a list of changes similar to Commit and Update dialog.
6. Finally, review the changes in Commit dialog. Input comment and click OK to commit.
7. The HEAD project now contains the changes from branch.
Delete branch
2. Expand the repository and folder node, select the branch to delete. Click OK button to continue.
Login Perforce
Server host The server host, which can be host name or IP address
Remember Check to memorize the password so that you don't need to enter again
password
Use proxy Check if proxy is needed for connecting to server. When checked, you will need to enter proxy host.
4. Click on the > button in the middle of the dialog box to add them into project selection.
5. Click OK to proceed. This end up showing the Teamwork Client dialog box.
Region Description
To manage projects, which enables you to add or remove projects from the list of managed projects.
To create a project in server by importing one into it. You may create a blank new project, or import an existing project file to start
with.
To open the project selected in Projects list. If the project is not checked out yet, it will be checked out automatically.
Repository To update the Projects list by showing only projects in certain repository.
Project Details Details of selected project, including the name, revision and status.
Project details
Field Description
Comment The comment of project entered by the administrator when creating project.
Revisions
Region Description
Show: To list certain amount of revisions, such as all, last 10, last 20, etc.
[Revert] By reverting a selected revision, this means to undone changes made in that revision.
Perforce path The filepath of p4.exe. You are required to supply a valid path in order to connect to Perforce server
Remember Check to memorize the password so that you don't need to enter again
password
Field Description
Create folder for project Create a folder in repository for storing the project. The folder will be of same name as the project.
Project file Create new project - Start with a blank, new project
Import existing project - Start by using an existing project file
7. Choose Create new project or Import existing project from Project file. Create new project will import a blank project into teamwork server,
Import existing project will import an existing VP-UML Project file (*.vpp) into teamwork server as first revision.
Select repository
Input comment
3. In Manage Project dialog, expand the repository node and select the project to checkout, click > button to add project. Click OK button to close
the dialog.
Manage projects
Open project
Project opened
Modified project
2. Show Teamwork Toolbar by right click on the Toolbar, select Teamwork if not selected already.
Commit project
5. On the bottom of dialog, click the Preview tab to visually preview the changes in diagram. The selected shape is highlighed in purple.
6. After review the changes, click the Comment tab and input the comment for commit. Click OK button to start commit.
Modified project
Conflict Revision The revision that cause conflict with the committing/updating action.
[Revert] Click on revert the conflict selected in tree. Resolving conflicts P. 1141
4. Select the conflict element, click Overwrite selected conflicts button on the toolbar to overwrite other user's change.
You can also click Overwrite all conflicts or Revert all conflicts to overwrite or revert all conflicts at once.
5. After resolve conflict, the preview will be enabled to visualize the final result.
6. You can change your mind by click Reset selected conflicts or Reset all conflicts button. Then overwrite or revert the conflict again.
Reset conflicts
7. After all conflicts was resolved, you can now input comment and click OK button to commit.
2. Similar to commit, you can review the change and preview the diagram in Update dialog.
Update dialog
3. If there are conflicts, resolve it similar to commit, but the changes will apply to local project instead of commit to server immediately.
Updated project
Checking status
1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Select Project > Check Update from menu.
4. You can see the status showing Has update or Up-to-date, it also indicate local project status (local project not modified) or (local project
modified).
Project status
Modify project
Reverted project
Open project
Revision tab
Select revision
Revert button
NOTE: You may make multiple selection by selecting one revision, pressing the Control key, and selecting the rest. Note that a non-consecutive
revision selection is not revertable.
8. A new revision with the reverted changes was created in server, and opened in VP-UML.
Reverted project
Open button
Compare button
Compare differences
Export buttons
Select directory
8. You'll found the selected revisions was exported to the select directory.
Exported revisions
Stay in trunk
Select branch
Branch project
Merge dialog
5. The Merge Project dialog show a list of changes similar to Commit and Update dialog.
6. Finally, review the changes in Commit dialog. Input comment and click OK to commit.
Trunk project
3. Select Project > Merge... from menu, or click Merge... button from toolbar.
4. Select the branch path(e.g //depot/branches/john_changes/FireSafetyDepartment.vpp) as From in the Merge dialog, and press OK.
Merge dialog
5. The Merge Project dialog show a list of changes similar to Commit and Update dialog.
6. Finally, review the changes in Commit dialog. Input comment and click OK to commit.
Delete branch
1. Select Project > Delete Branch... from menu
Locking diagram
1. To lock a diagram which you don't want it to be modified by others, right click on the diagram's background and select Diagram Content >
Lock ... from the pop-up menu.
Perform lock
2. Enter your password in the pop-up Lock dialog box and then click OK button. For your safety, always keep your password secret.
Enter password
NOTE: Lock by password: Check this option when you want to lock the diagram with password. On the other hand, uncheck it to lock the
diagram without password.
Save password: Check this option when you want to save your password in the project under your user account. Thereafter, you don't
have to enter password when you want to unlock the diagram. Otherwise, you need to enter password to unlock the diagram after you
uncheck it.
Show password: Check this option when you want to reveal the password. The password will be hidden by asteriks when you keep it
unchecked.
If you try to modify any model elements of the locked diagram, an Authorization Required dialog box will prompt out. Click Remove Lock button if
you want to unlock the diagram permanently while click Unlock button if you want to unlock it temporarily.
NOTE: If you uncheck Save password when you lock the diagram, you will be asked to enter password to unlock the diagram.
Moreover, you can also unlock the diagram permanently in Configure Lock dialog box. Right click on the diagram's background and select Diagram
Content > Configure Lock... from the pop-up menu. Choose Remove lock and enter password.
Removing lock
You can remove the lock or change the password after you lock the diagram.
Configure lock
NOTE: Configure Lock... option is available on the pop-up menu only after you have locked the diagram.
2. In Configure Lock dialog box, choose Change password if you want to change the current password and set a new password; otherwise,
choose Remove lock if you want to remove the lock permanently. Click OK button to confirm.
Change password
Project
Auto save interval (mins) Time needed to wait until the next auto saving.
Delete no referenced model element Action that happen when all views of a model element are being deleted:
• Ask - (default) Prompt if you want to delete the model element as well.
• Delete without ask - Delete the model element as well.
• Don't delete - Do not delete the model element.
Open exported image file Action that happen after exporting images
• Ask - (default) Prompt if you want to open the exported image file.
• Yes - Open image file (when export single image) or image folder (when export
multiple images) directly.
• No - Do not take any action.
Backup level The number of files that will be saved as backup. When reached the limit, the next backup will
overwrite the earliest one.
Confirm delete diagram (default true) Prompt if you really want to close diagram.
Confirm delete shape (default true) Prompt if you really want to delete a shape on diagram.
Never delete model elements with referenced views (default false) If a model element has multiple views, delet any of them will never cause the
model element to be deleted, even if you are deleting a master view.
Open last project on startup (default true) If checked, it will open the last opened project immediately when starting VP-
UML. If unchecked, it will open new project.
Export as image with frame • None - (default) Do not surround the diagram with neither frame nor border.
• Export with frame - Add a frame around image to show a border with the name of
diagram appear at top left of diagram.
• Export with border - Add a thin border around image.
Linked Project
Duplicate Model from Linked Project Duplicating a model element from linked project will cause a local copy to
be created.
• Prompt - (default) Prompt if you really want to duplicate.
• Yes - Confirm duplication. A local copy of selected shape(s) will be
created.
• No - Discard duplication.
Show warning when failed to add child to model from linked project You cannot place a shape inside a linked shape, such as a linked
package. If you try to do this you will be warned by default. This option
determines whether the warning will appear or not.
Caption Here
Appearance
Theme (for Office 2003 L&F only) The tone of the application screen.
User Language Language being applied on the user interface. This affects the text in menus, tooltips, dialog content, report
content, etc.
Date Sample The sample of date is shown after you select the format of date.
Time Sample The sample of time is shown after you select the format of time.
Connection
Option Description
Name
Login The user name of the proxy server (if the proxy server required the user to login).
name
Password The password of the proxy server (if the proxy server required the user to login).
Printing
Use gradient color when print diagrams Control whether to use gradient or solid color for shapes and diagrams when printing.
Edition
Enable non-supported (default true) When checked, executing features that are not available in the running edition will be prompted, asking
feature whether you want to advance to higher edition in order to use the feature. When unchecked, those non supported
features will be disabled.
Teamwork
Show Export/Import Teamwork (default false) Determines whether the export/import Teamwork project menus will appear in the Projects
project menu of Teamwork Client dialog box
Update
Option Description
Name
Auto Auto Update lets VP-UML to check for available updates with respect to the running build/version, and notify you to perform update
update whenever possible.
Appearance
Snap to grid (default true) When checked, shapes will be docked to the closest grid line when being created/moved.
Otherwise, shapes can be moved freely as if the grid does not exist.
Global Pallet Option - Show name (default true) Determines whether the name of items will be shown in the pallet.
Global Pallet Option - Expand group (default false) Determines whether the group will be expanded to display all items.
Model Element Name Alignment • Top Left - Shape name will appear at top left of shape
• Top Middle - Shape name will appear at top middle of shape
• Top Right - Shape name will appear at top right of shape
• Middle Left - Shape name will appear at middle left of shape
• Middle - (default) Shape name will appear at middle middle of shape
• Middle Right - Shape name will appear at middle right of shape
• Bottom Left - Shape name will appear at bottom left of shape
• Bottom Middle - Shape name will appear at bottom middle of shape
• Bottom Right - Shape name will appear at bottom right of shape
Show Hidden Layer Indicator • Yes - When move the mouse over a shape, the hidden layer indicator is shown
• No - The hidden layer indicator isn't shown even when move the mouse over a shape
• Prompt -Ask if users want to show hidden layer indicator when move the mouse over a shape
Enable minimum size (default true) Determines whether shapes are restricted to a built-in minimum size.
Fractional Metrics (default true) When checked, fit size of shape will be performed correctly. When disabled, the shape may look
better but size may not fit.
Environment
Alignment Guide - Show diagram alignment guide (default true) Show alignment guide which appear when moving a shape on a diagram.
Alignment Guide • Show edges - (default) Show guides at edges of the closest shape
• Show center - Show a guide that lies on the center of the closest shape
Shape Selection Detection • Inside selection area - (default) When selecting a range of shape, only shapes that
are completely inside the selection range are included in selection
• Overlapped with selection area - When selecting a range of shape, shapes that are
partly or completely covered by the selection range are included in selection
Copy as XML with RTF style • Yes - When copy Use Case, the rich text format of Use Case Details will also be
copied (size of copied content will increase considerably)
• No - When copy Use Case, Use Case Details will be copied as plain text
• Prompt - Ask if user want to copy rich text for Use Case Details when copying XML
Delay of show Quick Preview in Diagram Tree (second) • Never show - Never show Quick Preview when moving mouse cursor over diagram
node in Diagram Navigator
• 1.0 - 3.5 - The number of seconds that a Quick Preview will disappear after moving
the mouse cursor out of a diagram
Show Copy to Clipboard as OLE (default false) Determines whether the Copy to Clipboard as OLE menu is available or not
Default Copy Action • Within VP-UML - (default) When triggering the hotkey for Copy (Ctrl-C, by default),
it will perform copying within VP-UML
• Copy to Clipboard as Image (JPG) - When triggering the hotkey for Copy (Ctrl-C,
by default), it will perform copying as JPG image
• Copy to Clipboard as Image (EMF) - When triggering the hotkey for Copy (Ctrl-C,
by default), it will perform copying as EMF image
Copy as image with frame • Unspecified - (default) Prompt for adding a frame or a border when copying shapes
as image
• None - Do not add border nor frame to image when copy shapes as image
• Copy with frame - Add a frame around image to show a border with the name of
diagram appear at top left of diagram
• Copy with border - Add a thin border around image
Show shape content when dragging (default true) Show the shape content such as shape name when dragging shape.
Default HTML Documentation Font The default font face, size, color, bold and italic status for HTML content in documentation
pane.
Stereotype support HTML tagged value Enables you to define tagged value in HTML format for stereotype.
Prompt when Apply Design Pattern (default true) Prompt for applying design pattern even when there are remaining undo or
redo due to the undo and redo records will be cleared after applying design pattern.
Number of stereotypes shown in popup menu You can assign stereotypes to a shape through its popup menu. This option determines
the number of stereotypes to display in that popup menu.
Model generation
Generate Sequence Diagram from Use Case Description Overwrite Existing Diagram • Yes - Automatically overwrite Sequence Diagram
generated from Use Case Details when generate
again
• Prompt - (default) Prompt for overwriting Sequence
Diagram generated from Use Case Details when
generate again
Generate Diagram from Scenario Overwrite Existing Diagram • Yes - Automatically overwrite diagram generated from
Scenario when generate again
• Prompt (default) Prompt for overwriting diagram
generated from Scenario when generate again
Overwrite Flow of Events when Synchronize from Sequence Diagram • Ask - (default) Prompt for overwriting Flow of
Events in Use Case Details when Synchronize from
Sequence Diagram
• Yes - Overwrite Flow of Events in Use Case Details
automatically when Synchronize from Sequence
Diagram
Default generate diagram type from scenario • Sequence Diagram - (default) Take Sequence
Diagram to be the type of diagram that will be
generated by Scenario
• Interaction Overview Diagram - Take Interaction
Overview Diagram to be the type of diagram that will
be generated by Scenario
Shape
Font Default font settings for shape content, inlcuding font, size, color, bold
and italic.
Initial Shape Size When Set to Display Image • Fit shape to image - Resize the image placeholder to fit the
selected image
• Fit image to shape - (default) Resize the image to fit into the
image placeholder
Add Covered Shapes as Children After Resize • Yes - Automatic contain the covered shapes after resizing a
container to cover shapes
• No - Do not contain covered shapes after resizing a container
to cover shapes
• Prompt - (default) Ask if you want to contain covered shapes
after resizing a container to cover shapes
No View Model as Master View When you try to create a shape from existing model element, like to
drag and drop model element from Model Explorer to diagram, and if
the new shape is the only view of the model element, you can control
whether to set the shape to be master view or not.
• Yes - Set the created shape to be master view
• No - Do not set the created shape to be master view
• Prompt - (default) Ask if you want to set the created shape to
be master view
Show New Member in Other View When you try to create a new member, like a column of an entity, on
a shape, and if there is another view of the model element, you can
set whether to show the member on other view as well.
• Yes - Show the member on other view(s)
• No - Do not show the member on other view(s)
• Prompt - (default) Ask if you want to show the member on
other view(s)
Auto fit size (diagram-based) (default false) Determines whether shapes in diagrams will fit in size
automatically.
Create new line key • <Ctrl> + <Enter> - Press Ctrl-Enter to create a new line when
inline editing
• <Alt> + <Enter> - (default) Press Alt-Enter to create a new line
when inline editing
• <Enter> - Press Enter to create a new line when inline editing
Show unlimited level in preview shape (May slower the diagram display) (default false) Determines whether a diagram overview will show
contents for all nested diagrams.
Show rich text content in preview shape (default false) Determines whether diagram overview will show rich
text content.
Name completion (Classes, Entities and Requirements) (default true) When creating a class/ requirement/ an entity, you can
select an existing class/requirement/entity from a list so that a view of
the selected class/requirement/entity can be created. You can enable
or disable the popup of such list.
Resize shape when add member (default true) For shapes that have member, like class and entitiy,
when you add a member, it will or will not resize the owner against
the length of member, base on this option.
Connector
Connection Point Style • Round the shape - (default) Set the connector end to attach the round the
shape
• Follow center - Set the connector end to point to the center of attached
shapes
Caption orientation • Horizontal only - Enforce connector caption to appear horizontally regardless
of connector angle
• Horizontal or Vertical only - Enforce connector caption to appear either
horizontally or vertically, depending on the connector angle
• Follow Connector Angle - Enforce connector caption to appear an the same
horizontal level as the connector
• Follow Connector Angle and Keep Text Upright - Enforce connector caption
to appear an the same horizontal level as the connector, but keep the text
upright
Default pin from connection point (default false) Automatically pin connector's from end when connector is being
created.
Default pin to connection point (default false) Automatically pin connector's to end when connector is being created.
Show relationship connectors for dropped models (default true) Show connectors when dragging and dropping inter-related model
elements/views from tree to diagram.
Auto relocate connector when overlapped with other shapes (default false) Auto relocate connector when connector is being overlapped by
another shape.
Scroll connector delay (second) • No delay - Immediately scroll to the other side of connector
• 1 - 9 - Time provided for scrolling to the other side of connector
Paint connector through label (default true) Captions' background will become transparent so that connectors can
show completely without having part of it covered by opaque caption.
Highlight selected connector (default true) Increase the thickness of selected connector(s).
Resource centric
Show group resources (default true) Show group resources that appear when selecting multiple shapes.
Show extra resources (default false) Show also uncommon resource icons.
Show generic resources only (default false) Show generic resource but hide other resource icons.
Show resources delay (second) 0 - 2 - Time needed to wait from having mouse cursor hover on shape till the resource icons
appear.
Auto hide resource delay (second) Time needed to wait the resource icons to disappear when mouse cursor is moved out of a
shape.
Always show reference and sub-diagram (default true) Always show the reference and subdiagram resource icon at the bottom of shape
resource no matter whether the shape has reference and sub-diagram added.
Class
Auto-synchronize role name (default true) Rename role when the owner class is
being renamed.
Auto-generate role name (default false) Auto generate role names for a
relationship when the relationship is between
created.
Support multiple-line class name (default true) Allow to enter class name in multiple
lines by pressing the new line key defined in
Diagramming > Shape.
Update constructor after class renamed • Auto rename - Automatic update constructor
name when the class name is being updated
• Do not rename - Do not update constructor
name when the class name is being updated
• Prompt - (default)
Show fully qualified class and package name in tooltip (default true) Enable to show fully qualified class
and package name in tooltip like Package::Class/
Package.Class (depending on the setting of Show
parent style). Disable to show only the hovering
class or package name and type like Class : Class.
Show row grid line within compartment of Classes in Class Diagram (diagram type-based) (default false) Show a horizontal line between each
attribute or operation in class.
Show attribute option • Show all - (default) Show all attributes in Classes
• Show public only - Show all public attributes in Classes
• Hide all - Hide all attributes in Classes
Show type option • Fully-qualified - Show attribute type, operation return type and parameter type as full qualified class
name
• Name only - (default) Show attribute type, operation return type and parameter type as class name
• Relative - Show attribute type, operation return type and parameter type as relative class name
Show operation option • Show all - (default) Show all operations in Classes
• Show public only - Show all public operations in Classes
• Hide all - Hide all operations in Classes
Visibility style • Icon - Show icons for representing class members' visibilities
• UML - (default) Show icons for representing class members' visibilities such as + for public, minus for
private
• None - Do not display visibilities
Show attribute initial value (default true) Show initial value of attribute after its name.
Show attribute multiplicity (default false) Show multiplicity of attribute after its name.
Show attribute getter/setter (default false) Show getter and setter symbol for attribute, in front of attribute name.
Show class member stereotype (default true) Show the stereotypes set to attributes and operations.
Wrap class member (default false) Automatic wrap class member against the class's width.
Show owner of class/package (default false) Show the owner of class or package in class shape.
Display as Robustness Analysis icon (default true) Display class as robustness analysis icon for classes stereotyped as boundary/control/entity.
Display as stereotype icon (default false) Display stereotyped class as stereotype icon.
Show operation parameter name (default true) Show operation parameter name. When disabled, only parameter type, if defined, would be
shown.
Show empty compartments (default false) Show compartments even when no members are defined.
Default attribute type Define attribute type that will be applied to newly created attributes.
Auto set attribute type by name (default true) Automatically set attribute type and default value when the name user entered for an attribute
matches with one of those listed in the table followed.
Association
Show association stereotype (default true) Show the stereotypes assigned to an association.
Show from role name (default true) Show the role name of the from end of association.
Show to role name (default true) Show the role name of the to end of association.
Show from role visibility (default true) Show the role visibility of the from end of association.
Show to role visibility (default true) Show the role visibility of the to end of association.
Show from multiplicity (default true) Show the role multiplicity me of the from end of association.
Show to multiplicity (default true) Show the role multiplicity of the to end of association.
Show multiplicity constraints (default false) Show multiplicity constraint such as {unique} for roles.
Show direction (default false) Show a triangle mark on association for indicating
direction.
Show association role stereotypes (default true) Show stereotypes assigned to role.
Default Association End Navigable • Unspecified - A new association will set Navigable as Unspecified
for both ends
• True - (default) A new association will set Navigable as True for
both ends
• False - A new association will set Navigable as False for both
ends
Default Association End Visibility • Unspecified - (default) A new association will set Visibility as
Unspecified for both ends
• private - A new association will set Visibility as private for both
ends
• protected - A new association will set Visibility as protected for
both ends
• package - A new association will set Visibility as package for both
ends
• public - A new association will set Visibility as public for both ends
• protected internal (.NET only) - A new association will set Visibility
as protected internal for both ends when programming language is
set to be .NET
• internal (.NET only) - A new association will set Visibility as
internal for both ends when programming language is set to
be .NET
Suppress implied "1" multiplicity for attribute and association end (default false) Suppress implied "1" multiplicity for attribute and
association end.
Generalization
Create generalization direction • from General to Specific - (default) When creating a generalization, the arrow head will appear at the
mouse release side
• from Specific to General - When creaNessageting a generalization, the arrow head will appear at the firstly
selected shape
Generalization set notation • One Shape per Generalization - One generalization set shape per each Generalization relationship
• Common Generalization Arrowhead - (default) Combine Generalization relationships' arrow head for the
same set
• Dashed Line
Foreign key connector end points to associated column (default false) Attach foreign key
connector end points to the column
associated.
Show row grid line within compartment of Entities/Views in ERD (diagram type-based) (default true) Show grid lines
between row within Entities and
Database Views in ERD.
Show row grid line within compartment of Entities/Views/Classes in ORM Diagram (diagram type-based) (default true) Show grid lines
between row within Entities,
Database Views and Classes in
ORM.
Warning on create ORM-Persistable Class in default package (default true) Warn when creating
ORM Persistable class at root.
Show schema name in ERD: ${name}.${tableName} (default true) Show schema name, if
defined, for entities.
Default column type Define column type that will be applied to newly created columns.
Auto set column type by (default true) Automatically set column type and default value when the name user entered for a column matches
name with one of those listed in the table followed.
Interaction
Show sequence diagram text editor You can edit sequence diagram through
the text editor pane that appears at the
bottom of diagram. This option controls
the visibility of editor.
Auto fit message completion size (default true) Fit message completion
box's size everytime you activate it.
If disabdeterminsled, size adjusted
manually won't be remembered.
Mark target lifeline stopped when attached by destroy message The effect when attaching a Destroy
Message to a Lifeline, whether the
Lifeline will be marked stopped or not
• Yes - Lifeline will mark as stopped
• No - Lifeline will not mark as
stopped
• Prompt - (default) Ask if you want
to mark the Lifeline as stopped
Show messages operation signature in Sequence Diagram and Communication Diagram (diagram- (default false) Show Sequence
based) Messages' operation signatures in
Sequence Diagram and Communication
Diagram.
Show stereotype of message in Sequence Diagram and Communication Diagram (diagram-based) (default true) Show Sequence Messages'
stereotypes in Sequence Diagram and
Communication Diagram.
Display as Robustness Analysis icon in Sequence Diagram (default true) Display Lifeline as
robustness analysis icon for Lifelines
stereotyped as boundary/control/entity.
Show Use Case Extension Points (default true) Show Use Case Extension Points within Use Case shapes.
Rename Extension Point to Follow Extend Use • Yes - Rename Extension Points to follow extend use case automatically when the
Case name of extend use case is changed.
• No - Even when the name of extend use case is changed, the name of Extension
Points will not change to follow extend use case.
• Prompt (default) - Ask if rename Extension Points to follow extend use case when
the name of extend use case is changed.
Actor ID Generator Format - Prefix Prefix of ID that will be automatically generated when creating actor.
Actor ID Generator Format - Num of digits The number of digits of ID that will be automatically generated when creating actor.
Actor ID Generator Format - Suffix Suffix of ID that will be automatically generated when creating actor.
Use Case ID Generator Format - Prefix Prefix of ID that will be automatically generated when creating use case.
Use Case ID Generator Format - Num of digits The number of digits of ID that will be automatically generated when creating use case.
Use Case ID Generator Format - Suffix Suffix of ID that will be automatically generated when creating use case.
Auto create Use Case Description from default template (default false) When opening Use Case Description for a Use Case, a Use Case
Description will be created automatically using the chosen template. You can select
a template from the drop down menu under the checkbox, or select Other in the drop
down menu and import the template from file.
Template name • Main - (default) Main template will be used as Use Case Description default
template
• Alternative - Alternative template will be used as Use Case Description default
template
• Basic - Basic template will be used as Use Case Description default template
• Full - Full template will be used as Use Case Description default template
• Scenario - Scenario template will be used as Use Case Description default
template
• Other - Select Other to enable the drop down menu on the right, which is made
for selecting a template file to be used for default template
Clear Opposite Side Content in Flow of Event For every row of a flow of events table, either the Actor or the System side should be
filled, but not both. This option is for controlling the effect when you try to enter content
for both Actor and System cell.
• Yes - Automatically clear the other side's cell content
• No - Keep the other side's content
• Prompt - (default) Ask for whether to clear or keep the other side's content
Show Caption (State Machine Diagram) • Shallow History - (default false) Show caption for Shallow History
• Deep History - (default false) Show caption for Deep History
• Initial Pseudo State - (default false) Show caption for Initial Pseudo State
• Junction - (default false) Show caption for Junction
• Final State - (default false) Show caption for Final State
• Terminate - (default false) Show caption for Terminate
• Fork - (default false) Show caption for Fork
• Join - (default false) Show caption for Join
Auto create Initial State on State Diagram (default true) Automatic create an initial state when creating a State Machine Diagram.
Show Caption (Activity Diagram) • Initial Node - (default false) Show caption for Initial Node
• Expansion Node - (default false) Show caption for Expansion Node
• Activity Final Node - (default false) Show caption for Activity Final Node
• Flow Final Node - (default false) Show caption for Flow Final Node
• Decision Node - (default false) Show caption for Decision Node
• Merge Node - (default false) Show caption for Merge NodeArtifactat
• Fork Node - (default false) Show caption for Fork Node
• Join Node - (default false) Show caption for Join Node
Show Partition Header (Activity Diagram) • Auto - (default) Show horizontal and/or vertical Partition headers if there is Partitions in that
orientation
• Always Show - Always show Partition headers regardless of the orientation of Partitions, even
if there is no Partition
• Always Hide - Always hide Partition headers
Use state name tab (default false) Name tab is a a tiny rectangle that appear on top of a state and at the left hand side,
displaying the name of a state. Use state name tab is to enable such tab.
Show transition trigger Triggers can be added to a Transition relationship. This option determines the visibility of Triggers.
• Show - (default) Show Triggers information on a Transition connector
• Hide - Do not show Triggers information on a Transition connector
Decision/Merge Node connection point style Determines how connector connects to decision/merge node.
• Default (default)
• Connect to vertex
Component diagram
Show Component • Keyword - Show only the keyword <<component>> at the top of Component
Option
• Icon - Show only an icon representing a Component at the top right of Component
• Keyword and Icon - (default) Show both keyword and icon for a Component
• None - Do not show keyword and icon for a Component
Show Artifact • Keyword - Show only the keyword <<artifact>> at the top of Artifact
Option
• Icon - Show only an icon representing an Artifact at the top right of Artifact
• Keyword and Icon - (default) Show both keyword and icon for a Artifact
• None - Do not show keyword and icon for a Artifact
Business process
Invalid Connection Handling • Ignore all - Ignore all invalid actions related to connecting shapes
• Cancel move - Cancel invalid actions related to connecting shapes
• Prompt - (default) Prompt for an action when an invalid actions related to
connecting shapes is discovered
Show Lane Handle • Auto - (default) Show horizontal/vertical Lane header only when horizontal/
vertical Lane exist
• Always Show - Always show both horizontal and vertical Lane headers even
when Lane does not exist
• Always Hide - Always hide Lane headers
Connection Point Style • Round the shape - Set the connection point style to Round the shape
• Follow center - (default) Set the connection point style to Follow center
Connect Gateway with Flow Object in Different Pool • Prompt - (default) Prompt if user want to change the Message to Message
Flow, Sequence Flow or cancel the action
• Connect with Message Flow - Change or keep the relationship as Message
Flow
• Connect with Sequence Flow - Change or keep the relationship as Sequence
Flow
ID Generator Format - Prefix Prefix of ID that will be automatically generated when creating BPMN shapes.
ID Generator Format - Num of digits The number of digits of ID that will be automatically generated when creating BPMN
shapes.
ID Generator Format - Suffix Suffix of ID that will be automatically generated when creating BPMN shapes.
ID Generator Format - Show ID option • Not Show - (default true) Do not display ID
• Show Below Caption - Display ID as part of the caption, under the name
• Show as Label - Display ID as a label attaching to shape
Show Activities type icon (diagram-based) (default true) Show icons that represent the type of Task and Sub-Process.
Show convert Sub-Process/Task warning (default true) Show warning when trying to convert between Sub-Process and Task.
Auto stretch pools (default true) Stretch Pools automatically to the reach diagram bound.
Draw text annotation open rectangle folow connector end (default true) Make the open rectangle of text annotation follow the position of end of
the attached connector.
Requirement diagram
ID Generator Format - Prefix Prefix of Requirement ID that will be automatically generated when creating Requirement.
ID Generator Format - Num of digits The number of digits of Requirement ID that will be automatically generated when creating Requirement.
ID Generator Format - Suffix Suffix of Requirement ID that will be automatically generated when creating Requirement.
Show Attributes • Show All Attributes - (default) Show all Requirement attributes
• Show Non-empty Attributes - Show only Requirement attributes that have values defined
• Hide All Attributes - Hide all Requirement attributes
Support HTML Attribute (default false) Allow to fill in attributes with rich text format.
DFD
Add Data Stores and External Entities to Decomposed DFD • Yes - When decompose a DFD, Data Stores and External Entities on the
current diagram will be copied to the decompose diagram
• No - When decompose a DFD, Data Stores and External Entities on the current
diagram will not be copied to the decompose diagram
• Prompt - (default) When decompose a DFD, prompt if user want the Data
Stores and External Entities on the current diagram to be copied to the
decompose diagram
Communication Diagram
Textual Analysis
Highlight Option • Case insensitive - (default) Words which are the same as the entered word, even in
different cases, are highlighted.
• Case sensitive - Words which are the same as the entered word or/and with same case
are highlighted.
Generate Requirement Text from Candidate • Extracted text - (default) When create requirement from a candidate requirement, its text
Option property will be filled by the candidate's extracted text.
• Class description - When create requirement from a candidate requirement, its text
property will be filled by the candidate's class description.
Highlight Color • Highlight color (inactive selection) - The color of inactive candidate item in problem
statement.
• Highlight color (active selection) - The color of selected candidate item in problem
statement.
Options
View Options
Diagram Navigator Sort Type • Sort by name - (default) Sort tree nodes in Diagram Navigator by their names
• Sort by type - Sort tree nodes in Diagram Navigator by their types
Model Explorer Sort Type • No sort - Do not sort tree nodes in Model Explorer
• Sort by name - (default) Sort tree nodes in Model Explorer by their names
• Sort by type - Sort tree nodes in Model Explorer by their types
Show data types (default false) Show Data Types node in trees.
Show Activation in Diagram Navigator (default true) Show activations in Diagram Navigator.
Show project path in Diagram Navigator (default false) Show project path in Diagram Navigator.
Sort elements in tree with case sensitive (default false) Make sorting of tree nodes case sensitive (consider the case).
Show carriage return character (default true) Show carriage return character for line breaks of shape names that are in multiple lines.
Options
.NET • Not specified - (default) Do not specify whether Instant Reverse of .NET
is enabled or not.
• Enabled - Enable Instant Reverse for .NET
• Disabled - Disable Instant Reverse for .NET
C++ • Not specified - (default) Do not specify whether Instant Reverse of C++
is enabled or not.
• Enabled - Enable Instant Reverse for C++
• Disabled - Disable Instant Reverse for C++
Text File Encoding • System default - (default) The default system encoding will be selected
as encoding for source files that will be reversed
• Other - Specify an encoding for the source files that will be reversed
Show Instant Reverse Form Diagram dialog after Instant Reverse (default true) Show the Instant Reverse Form Diagram dialog box after
Instant Reverse so that you can form diagram after reversing code into VP-
UML.
Create shape for parent model of dragged class/package (default false) When drag and drop an element from tree to diagram, add also
their parent (e.g. Package) to diagram to contain the dropped shapes.
General
Decimal Precision and Scale - Use default (default true) Automatic determine the
most suitable precision and scale when
synchronize from attribute to column as
decimal.
Decimal Precision and Scale - Precision Specify the precision when synchronize from
attribute to column as decimal.
Decimal Precision and Scale - Scale Specify the scale when synchronize from
attribute to column as decimal.
Entity => Class Name - Class name • Capitalize - (default) The first character of each word become uppercase
• Decapitalize - The first character of each word become lowercase
• Upper case - All characters become uppercase
• Lower case - All characters become lowercase
• Upper camel case - words are joined without underscore ("_") and are capitalized
• Lower camel case - Same as upper camel case except that the first character is lower case
• Reverse camel case - each upper case character are considered as word separator, words are
joined with underscore ("_") and are lower case
• Reverse camel to upper case - each upper case character are considered as word separator,
words are joined with underscore ("_") and are upper case
• Don't change - Keep name unchanged
Column => Attribute Name - Attribute Name • Capitalize - The first character of each word become uppercase
• Decapitalize - (default) The first character of each word become lowercase
• Upper case - All characters become uppercase
• Lower case - All characters become lowercase
• Upper camel case - words are joined without underscore ("_") and are capitalized
• Lower camel case - Same as upper camel case except that the first character is lower case
• Reverse camel case - each upper case character are considered as word separator, words are
joined with underscore ("_") and are lower case
• Reverse camel to upper case - each upper case character are considered as word separator,
words are joined with underscore ("_") and are upper case
• Don't change - Keep name unchanged
Class => Entity Name - Table name • Capitalize - The first character of each word become uppercase
• Decapitalize - The first character of each word become lowercase
• Upper case - All characters become uppercase
• Lower case - All characters become lowercase
• Upper camel case - words are joined without underscore ("_") and are capitalized
• Lower camel case - Same as upper camel case except that the first character is lower case
• Reverse camel case - each upper case character are considered as word separator, words are
joined with underscore ("_") and are lower case
• Reverse camel to upper case - each upper case character are considered as word separator,
words are joined with underscore ("_") and are upper case
• Don't change - (default) Keep name unchanged
Attribute => Column Name - Column name • Capitalize - (default) The first character of each word become uppercase
• Decapitalize - The first character of each word become lowercase
• Upper case - All characters become uppercase
• Lower case - All characters become lowercase
• Upper camel case - words are joined without underscore ("_") and are capitalized
• Lower camel case - Same as upper camel case except that the first character is lower case
• Reverse camel case - each upper case character are considered as word separator, words are
joined with underscore ("_") and are lower case
• Reverse camel to upper case - each upper case character are considered as word separator,
words are joined with underscore ("_") and are upper case
• Don't change - Keep name unchanged
Attribute => Column Name - Suffix Append characters/words after name. ORM options P. 1209
State code engine options
Options
Synchronized transition methods (default true) Generate synchronized keyword for transition methods.
Generate try catch block (default true) Generate try catch block for method calls that may produce exception.
Generate debug messages (default false) Generate debug message to help tracing problems that happen when running
generated code.
Auto create transition methods (default true) Auto generate operation to owner class by transition.
Re-generate transition methods (default false) Overwrite the transition methods if already exists in source code.
Generate sample code (default true) Generate sample code to help you understand how to work with generated code.
Browse output directory after generate code (default false) Open the directory of generated state code.
Options
Remember Import Decision VP-UML detects changes made in exported document, and will suggest you to import changes back to VP-UML.
This option determines whether the import will be on or off.
• Yes - Enable the import option.
• No - Disable the import option.
• Not Specified - (default) You will be asked if you want to import the changes from document to VP-UML
whenever changes are detected.
Insert page break (default true) Insert a page break for each element.
Generate blank model (default false) Export an empty form for user to create new model.
element
Options
Show user path (default false) Select to show user paths in references, instead of displaying resolved absolute paths. A user path is
displayed with its name enclosed by ${ }.
Prompt to specify user path (default false) When adding a reference comprises a path that is not defined as a user path, you will be prompted to
add path as user path.
Code
Default attribute type (default int) Type that will be assigned to Attribute upon code generation
when type is unspecified.
Default operation return type (default void) Return Type that will be assigned to operation upon code
generation when return type is unspecified.
Default parameter type (default int) Type that will be assigned to Parameter upon code generation
when type is unspecified.
Auto realize interface (default false) Generate operations defined in interface in sub-classes.
Remove method body after changed to abstract method (default true) When an operation is set from non-abstract to abstract,
updating code will remove the related method's body.
Use "is" prefix for getters that return boolean (default true) Generate getter's name as isXXXX() for getters that return a
boolean value.
Add import statement instead of using fully qualified type name (default true) Add import statement for referencing classes in another
package/namespace instead of using fully qualified name inline.
Import fully qualified type name for referenced type (default false) Use fully qualified type name in import statements instead of
using wildcard character * to represent importing all classes in package.
Generate annotation in code convention (default true) Generate annotation in code convention.
Text File Encoding • System default - (default) The default system encoding will be selected
as encoding for source files
• Other -Specify an encoding for source files
Class declaration • Same line - (default) Brace for class declaration appear at the same line as the declaration
• Next line - Brace for class declaration appear at the line after the declaration
Constructor declaration • Same line - (default) Brace for constructor appear at the same line as the declaration
• Next line - Brace for constructor appear at the line after the declaration
Method declaration • Same line - (default) Brace for method appear at the same line as the declaration
• Next line - Brace for method appear at the line after the declaration
Enum declaration • Same line - (default) Brace for enumeration appear at the same line as the declaration
• Next line - Brace for enumeration tor appear at the line after the declaration
Annotation type declaration • Same line - (default) Brace for annotation type appear at the same line as the declaration
• Next line - Brace for annotation type appear at the line after the declaration
Before package declaration Number of blank lines to appear before Package declaration.
After package declaration Number of blank lines to appear after Package declaration.
Before import declaration Number of blank lines to appear before import statements.
After import declaration Number of blank lines to appear after import statements.
Before first declaration Number of blank lines to appear before the first declaration within Class declarations.
Before different kind declaration Number of blank lines to appear before a different kind of declaration.
Before field declaration Number of blank lines to appear before field declaration.
Before method declaration Number of blank lines to appear before method declaration.
Before inner type declaration Number of blank lines to appear before inner type declaration.
Number of lines to empty body Number of blank lines to appear in empty method body.
Template
Option Description
Name
Code
Default attribute type (default int) Type that will be assigned to Attribute upon code generation when type is unspecified.
Default operation return type (default void) Return Type that will be assigned to operation upon code generation when return type is unspecified.
Default parameter type (default int) Type that will be assigned to Parameter upon code generation when type is unspecified.
Text File Encoding • System default - (default) The default system encoding will be selected as encoding for source files
• Other - Specify an encoding for source files
Class declaration • Same line - (default) Brace for class declaration appear at the same line as the declaration
• Next line - Brace for class declaration appear at the line after the declaration
Constructor declaration • Same line - (default) Brace for constructor appear at the same line as the declaration
• Next line - Brace for constructor appear at the line after the declaration
Method declaration • Same line - (default) Brace for method appear at the same line as the declaration
• Next line - Brace for method appear at the line after the declaration
Enum declaration • Same line - (default) Brace for enumeration appear at the same line as the declaration
• Next line - Brace for enumeration tor appear at the line after the declaration
Annotation type declaration • Same line - (default) Brace for annotation type appear at the same line as the declaration
• Next line - Brace for annotation type appear at the line after the declaration
Before first declaration Number of blank lines to appear before the first declaration within Class declarations.
Before different kind declaration Number of blank lines to appear before a different kind of declaration.
Before field declaration Number of blank lines to appear before field declaration.
Before method declaration Number of blank lines to appear before method declaration.
Template
Option Description
Name
Options
Ignore words in UPPERCASE (default true) Do not classify the use of upper case in a word as a spelling mistake(unless the spelling is wrong).
Ignore words with numbers (default true) Do not classify the inclusion of number in word as a spelling mistake (unless the spelling is wrong).
Ignore Internet and file address (default true) Do not classify Internet and file address as a spelling mistake.
• By executing the launcher VP Suite Update in the launcher folder of VP Suite installation directory. Users in all operating system can
start VP-UML in this way.
NOTE: If there is a connection problem when downloading the update files from the specified server under Automatic Connection, VP Suite
Update will connect to another server randomly instead of the specified connection to continue the update automatically.
NOTE: By using the Update Synchronizer to keep the files in the update repository up-to-date, network client can specify the or file path of the
update repository using the Manual Connection.
NOTE: Patch is special build for specific users. You should choose the Update to Latest Patch option only when you are recommended by
Visual Paradigm Support Team.
4. Review the files to be updated. You may select or deselect files to be updated by checking and unchecking individual file listing in the page,
under the Update column. Usually, you can keep the selection unchanged. But if you see the filenames appear in blue or red, you better confirm
the selection carefully. Below is a description of red and blue colored filename:
Color Description
Blue Modified. This refers to files which are modified by the users and will be replaced with the original files
Red Obsolete. This refers to files which are no longer useful in the new version of the product and will be deleted.
If you want to keep the modified and obsolete files, press the Deselect "Obsolete" and Deselect "Modified" buttons so that these files will not
be updated.
5. Click Next to proceed with updating the files.
6. Click Finish to confirm.
Next Check for product updates next time when starting VP-UML.
time
No Check for product updates after a certain period of time (The invertal can be defined in the Options dialog box. Refer to the
section below for details).
3. Select Update now and click OK to proceed. This popup the VP Suite Update.
To shutdown VP-UML
5. Review the files to be updated. You may select or deselect files to be updated by checking and unchecking individual file listing in the page,
under the Update column. Usually, you can keep the selection unchanged. But if you see the filenames appear in blue or red, you better confirm
the selection carefully. Below is a description of red and blue colored filename:
Color Description
Blue Modified. This refers to files which are modified by the users and will be replaced with the original files
Red Obsolete. This refers to files which are no longer useful in the new version of the product and will be deleted.
Weekly Check for product updates every week, when starting VP-UML
Monthly Check for product updates every month, when starting VP-UML
Click OK to confirm updating. From now on, once the interval elapsed, and if there are available updates, you will see the Automatic Update
dialog box, letting you to update to the latest build.
Combined
fragment
Interaction use
Frame
Actor
Continuation
State Transition Transition Transition Transition Transition Transition Transition Transition Transiti
Submachine state Transition Transition Transition Transition Transition Transition Transition Transition Transiti
Initial pseudo Transition Transition Transition Transition Transition Transition Transition Transition Transiti
state
Shallow history Transition Transition Transition Transition Transition Transition Transition Transiti
Deep history Transition Transition Transition Transition Transition Transition Transition Transiti
Join Transition Transition Transition Transition Transition Transition Transition Transition Transiti
Entry point Transition Transition Transition Transition Transition Transition Transition Transition Transiti
Exit point Transition Transition Transition Transition Transition Transition Transition Transition Transiti
Terminate
Final state
Activity Control Object Flow Control Flow Control Flow Control Flow Control Control
Control
Object
Flow Flow Flow
Flow
Activity parameter node Object Object Flow Object Flow Object Flow Object Flow Object Flow Object
Object
Flow Flow
Flow
Action Control Object Flow Control Flow, Control Flow Control Flow Control Control
Control
Object
Excepti
Flow Exception Flow Flow
Flow
Flow,
handler
handler Excepti
handler
Accept event action Control Object Flow Control Flow Control Flow Control Flow Control Control
Control
Object
Excepti
Flow Flow Flow
Flow
Flow,
handler
Excepti
handler
Send signal action Control Object Flow Control Flow Control Flow Control Flow Control Control
Control
Object
Excepti
Flow Flow Flow
Flow
Flow,
handler
Excepti
handler
Decision node Control Object Flow Control Flow Control Flow Control Flow Control Control
Control
Object
Flow Flow Flow
Flow
Merge node Control Object Flow Control Flow Control Flow Control Flow Control Control
Control
Object
Flow Flow Flow
Flow
Fork node Control Object Flow Control Flow Control Flow Control Flow Control Control
Control
Object
Flow Flow Flow
Flow
Join node Control Object Flow Control Flow Control Flow Control Flow Control Control
Control
Object
Flow Flow Flow
Flow
Initial node Control Object Flow Control Flow Control Flow Control Flow Control Control
Control
Object
Flow Flow Flow
Flow
Input pin
Value pin
Object node Object Object Flow Object Flow Object Flow Object Flow Object Flow Object
Object
Flow Flow
Flow
Central buffer node Object Object Flow Object Flow Object Flow Object Flow Object Flow Object
Object
Flow Flow
Flow
Data store node Object Object Flow Object Flow Object Flow Object Flow Object Flow Object
Object
Flow Flow
Flow
Expansion node Object Object Flow Object Flow Object Flow Object Flow Object Flow Object
Object
Flow Flow
Flow
Swimlane
Structured Activity node Control Control Flow Control Flow Control Flow Control Control
Control
Excepti
Flow Flow Flow
Flow
handler
Conditional node Control Control Flow Control Flow Control Flow Control Control
Control
Excepti
Flow Flow Flow
Flow
handler
Loop node Control Control Flow Control Flow Control Flow Control Control
Control
Excepti
Flow Flow Flow
Flow
handler
Value pin Object Central Data store Interruptible activity region Expansion
Conditional
Expansion
Structured
Sequence
Swimlane
Loop
node buffer node node region Activity
node
node
Input pin
Value pin
Swimlane
Subsystem
Dependency, Dependency,
Import, Import,
Access, Access,
Realization, Generalization,
Merge Realization,
Merge
Interaction Control Control flow Control flow Control Control Control flow Control flow
flow flow flow
Interaction Control Control flow Control flow Control Control Control flow Control flow
use flow flow flow
Decision Control Control flow Control flow Control Control Control flow Control flow
node flow flow flow
Merge node Control Control flow Control flow Control Control Control flow Control flow
flow flow flow
Fork node Control Control flow Control flow Control Control Control flow Control flow
flow flow flow
Join node Control Control flow Control flow Control Control Control flow Control flow
flow flow flow
Initial node Control Control flow Control flow Control Control Control flow Control flow
flow flow flow
Activity final
Requirement
Composition,
Derive,
Trace
Model Satisfy,
Refine
Testcase Verify,
Sequence
Stored procedures
Stored procedure
resultset
Triggers
Task Sequence flow, Sequence flow, Message flow Sequence flow, Sequence Associa
Sequen
Message flow Message flow Message flow flow, flow,
To-
Messag
Directio
flow
Associa
Data
Associa
Sub-process Sequence flow, Sequence flow, Message flow Sequence flow, Sequence Associa
Sequen
Message flow Message flow Message flow flow, flow,
To-
Messag
Directio
flow
Associa
Data
Associa
Start event Sequence flow, Sequence flow, Sequence flow, Sequence Associa
Sequen
flow, flow,
To-
Directio
Associa
Intermediate event Sequence flow, Sequence flow, Sequence flow, Sequence Associa
Sequen
flow, flow,
To-
Directio
Associa
End event Message flow Message flow Message flow Message flow Messag
Associa
flow
To-
Directio
Associa
Choreography task Sequence flow, Sequence flow, Sequence flow, Sequence Sequen
Associa
flow, flow,
To-
Directio
Associa
Choreography sub- Sequence flow, Sequence flow, Sequence flow, Sequence Sequen
Associa
process flow, flow,
To-
Directio
Associa
Call activity Sequence flow, Sequence flow, Message flow Sequence flow, Sequence Associa
Sequen
Message flow Message flow Message flow flow, flow,
To-
Messag
Directio
flow
Associa
Data
Associa
Pool/lane Associa
To-
Directio
Associa
Text Association
annotation
Organization Line
unit
Business object Read access Read access Read access Read access Read
access
Contract Read
access
Representation
Meaning
Value Association
Application Assignment
collaboration
Application
function
Application
interaction
Application Used by
interface
Data object
Node
System software
Infrastructure
interface
Infrastructure
service
Artifact
Business Line
actor
Business Association
role
Business Association
collaboration
Business Read
process access,
Write
access,
Business Read
function access,
Write access
Business Read
interaction access,
Write access
Business Read
event access,
Write access
Junction
Business Aggregation,
interface Specialization
Contract Aggregation,
Specialization
Application
collaboration
Application
component
Application
service
Application
interaction
Application
interface
Node
Device
System
software
Infrastructure
interface
Infrastructure
service
Artifact
Business
actor
Business Require
role
Business
collaboration
Business Assignment
process
Business
function
Business
event
Junction
Business Used by
interface
Business
object
Product
Contract
Representation
Meaning
Value
Node
Device
System
software
Infrastructure
interface
Infrastructure
service
Business
actor
Business
role
Business
collaboration
Business
process
Business
function
Business
interaction
Business
event
Junction
Business
service
Business
interface
Business
object
Product
Contract
Meaning
Value
Application
collaboration
Application
component
Application
service
Application
function
Application
interaction
Application
interface
Data
object
NodeBranch,
Link,
From
link,
To link