0% found this document useful (0 votes)
218 views1,274 pages

VP-UML Users Guide

user guide

Uploaded by

Sukant Makhija
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
218 views1,274 pages

VP-UML Users Guide

user guide

Uploaded by

Sukant Makhija
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1274

About Visual Paradigm for UML

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

About Visual Paradigm for UML P. 1


The interoperability support allows you to exchange model data with other tools. The following tools are supported:

Import Export

Telelogic Modeler

Rational Rose

ERwin Data Modeler project

Rational Software Architect

Rational DNX

NetBeans 6.x UML diagrams

Visio drawing

BPEL for Oracle workflow engine

BPEL for JBoss workflow engine

Diagram (JPG, PNG, SVG, EMF, PDF)

Microsoft Excel

EMF based UML2 model

XMI (1.0, 1.2, 2.1)

XML (native)

VP project

Microsoft Word document (for use case model)

List of standard or tools that are covered by interoperability support

Code engineering

About Visual Paradigm for UML P. 2


Instant Reverse and Instant Generator are provided for reversing engineering and forward engineering. In addition, the Java Round-Trip engineering
support lets you keep code and model in-sync. Below are the type of source code that can be reversed or generated through Instant Reverse and
Instant Generator.

Instant Reverse Instant Generator

Java

C++

XML Schema

PHP

Python Source

Objective-C

CORBA IDL Source

.NET dll or .exe files (binary)

CORBA IDL Source

XML (structure)

JDBC

Hibernate

C#

VB.NET

ODL

ActionScript

Delphi

Perl

Ada95

Ruby

List of souce code supported by Instant Reverse and/or Generator

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

About Visual Paradigm for UML P. 3


Editions
Belows are the kinds of features that can be found in each edition of VP-UML. For details, please visit: http://www.visual-paradigm.com/product/vpuml/
editions

Enterprise Professional Standard Modeler Personal Community

UML Modeling

Use Case Diagram

Flow of Events Editor

Requirement Diagram

Glossary Grid

User Interface Mock-up

Entity Relationship Diagram

Generate Hibernate Mapping

Business Process Modeling

Mind Mapping

UML Profile

Design Pattern

Visual Diff

Animacian

Simulacian

Team Collaboration (Teamwork Server)

Team Collaboration (Subversion, Perforce, CVS)

Instant Forward and Reverse Engineering

Java and C++ Round Trip Engineering

Impact Analysis

PDF, HTML Report Generation

Word Report Generation

Report Template Designer

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.

Enterprise Professional Standard Modeler Personal Community Viewer

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

Use case detail editor

Use case flow-of-events listing

Generate sequence diagrams from flow of events lists

Select attribute's getter or setter as call message's action

Business model use case support

The feature is available but unable to make changes.


UML Supports in different editions of VP-UML

Features P. 6
Requirements management
Capture requirements with SysML Requirement Diagram, Use Case Modeling, Textual Analysis, CRC and more!

Enterprise Professional Standard Modeler Personal Community Viewer

Requirement diagram

Textual analysis

CRC Cards

User interface designer

Identify candidate activity and action by textual analysis

Define and customize requirement types

Display full set of requirements in tabular view

Support generating ID for Requirements

The feature is available but unable to make changes.


Requirements management support in different editions of VP-UML

Business process modeling


Visualize, understand and improve your business process with the most comprehensive BPMN tool.

Enterprise Professional Standard Modeler Personal Community Viewer

Business process diagram

Data flow diagram

Event-driven process chain diagram

Process map diagram

Export business process diagrams to BPEL

Identify candidate business process elements using textual analysis

Automatically stretch pools and lanes to fit diagram

Smart routing for connecting objects

Extend business process model with stereotype and tagged value

Set state for data object

Organization chart

Relocate a branch of unit through drag and drop

Nested lanes support

The feature is available but unable to make changes.


Business Process modeling support in different editions of VP-UML

Features P. 7
Animacian
A set of tools to help animating paths in a diagram, or to export animation to flash for further analysis.

Enterprise Professional Standard Modeler Personal Community Viewer

Animate business process using Animacian

Animate sequence diagram using Animacian

Animate activity diagram using Animacian

Travel along execution path with slider

Step forward and backward in an animation

Auto validate execution path

Auto calculate all possible execution paths

Eliminate paths using filter

Dim non-execution path

Support Full and Compact Mode

Protect diagram when animating

Export selected path to flash format

Animate and navigate animation in exported flash

The feature is available but unable to make changes.


Animacian support in different editions of VP-UML

Mind mapping

Enterprise Professional Standard Modeler Personal Community Viewer

Mind map diagram

Create link relationships between nodes

Smart layout for mind mapping nodes and diagram

Mind Mapping support in different editions of VP-UML

Database modeling
Enhance database documentation quality with sophisticated ERD and Object-Relational Mapping diagrams.

Enterprise Professional Standard Modeler Personal Community Viewer

Entity relationship diagram

ORM diagrams

Reverse engineer existing databases to entity relationship diagrams


(ERDs)

Generate and execute database schema (DDLs)

Conceptual, logical and physical ERD support

Reverse engineer stored procedures to ERDs

Features P. 8
Foreign key auto-naming

Define PK naming pattern

Define FK relationship naming pattern

Model primary key in object model by using the <<PK>> stereotype

Download database drivers automatically

Display database architecture in object-relational mapping (ORM) pane

Customizable SQL generation

Generate class diagrams from ERDs

Generate ERDs from class diagrams

Select target diagram when first synchronized between class diagram


and ERD

Jump between ORM class and entity

Generate and reverse engineer database support for Oracle schema

Generate or reverse engineer user-defined database types

Database trigger and stored procedure modeling

Reverse engineer DDL models to ERD models

Database trigger and stored procedure generation and reversal

Unique and Index support for entities

Convert a normal association to ORM association

Support AbstractPersistable class for generating non ORM super class


attributes

Configurable generated SQL statements in upper or lower case

Model and generate DB Sequence (Oracle and DB2 only)

The feature is available but unable to make changes.


Database modeling support in different editions of VP-UML

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.

Enterprise Professional Standard Modeler Personal Community Viewer

Java ORM code generation

.NET ORM code generation

PHP ORM code generation

Lazy collection fetching

Database view support

Custom ID generator support

Map single classes to multiple tables

Custom query support

Automatic array table generation

Criteria class generation

DAO code generation

Factory code generation

POJO code generation

Optional library selection

Hibernate annotation support in ORM persistence

Generate Hibernate version tags for optimistic concurrency control

Formula support for ORM attribute

User defined exception support in error handling

Define default type mapping between database column and class


attribute

Configurable naming pattern for synchronization between Class


Diagram and ERD

Object Relational Mapping support in different editions of VP-UML

Visual modeling
Improve the user-friendlyness of drawing diagrams, thus speed up the time need to spend on diagramming.

Enterprise Professional Standard Modeler Personal Community Viewer

Reference other projects' model elements

Freehand shape support

Justify shape name

Support enable or disable minimum shape size

Features P. 10
Layer support to show/hide set of shape with single click

Support showing line jump in Arc, Square, Skip or normal

Align Connector Caption Base on Connector Orientation

Annotation with callout shapes

Annotation with freehand shapes

Organize model elements and diagrams using Model Explorer

Bookmark support

Handi-Selection tool

Customizable data types for use with multiple programming languages

Overview diagrams

Resource-centric interface

Model sharing

Cut, copy and paste

Copy diagrams as images for use in other applications

Undo and redo options

Mouse gestures

Reverse connector direction

Group creation support

Jump to feature for selecting a particular shape or model

Quick connect feature

Easy navigation to connected elements

Model commenting

Duplicate shapes and models

Selectable/non-selectable toggling for shapes

Diagram locking

Reference to any type of artifact

Advanced file and directory selector

Advanced tree support

Duplicate, move and reconnect connectors

Package headers for all types of diagrams

Features P. 11
Tagged value display toggling for diagram elements

Sub-diagrams and reference indicators

Rectilinear, round rectilinear, oblique, round oblique and curve


connector styles

Space reclamation using Sweeper

Space elimination using Magnet

Create shapes with user-defined initial sizes

Drag-and-drop creation of shapes using trees in diagrams

Auto-fit shape sizes

In-line editing

Spell checking

Visual alignment guides

Numerous grid options

Diagram information display in diagrams

Jump to diagram feature

Drag-and-drop copying, moving and reordering of classes and entity


members

Open view from model element

Diagram renaming boxes

Add folders as favorites

Display Undo/Redo action names

Inverse shape selection

Create new attribute with Enter key

Automatic reroute connector when overlapped with other shapes

Hide shapes or type of shapes on a diagram

Visualize related model element

Enforcing master view between model element and shape

Auto extend activation

Model name completion for class

Pinnable connector end

The feature is available but unable to make changes.


Visual Modeling support in different editions of VP-UML

Features P. 12
Visual diff
A set of tools that help to compare diagrams, and identify their differences.

Enterprise Professional Standard Modeler Personal Community Viewer

Compare and show difference between diagrams visually

Support compare by name, id and transitor options

Compare view, model element or both kinds of properties

Filter result by displaying all, addition, modification or deletion of items

Support of Visual Diff in different editions of VP-UML

Design pattern support


Define a pattern and save it for future use, or share with team members for making the design consistent.

Enterprise Professional Standard Modeler Personal Community Viewer

Design pattern support for class diagrams

Full Gang of Four (GOF) design patterns support

Define pattern with a configurable number of subclasses

Define pattern with a configurable number of attributes and operations

Define pattern with implementation hierarchy

Define pattern with automatically named association end

Automatically rename elements in pattern

Design pattern support for sequence diagrams

Design pattern support for all UML diagram types

Design pattern support for entity relationship diagrams

Design pattern support for business process diagrams

Sharing Design Patterns through team collaboration support

Design Pattern support in different editions of VP-UML

Model element nicknaming


Define nickname for a set of models.

Enterprise Professional Standard Modeler Personal Community Viewer

Assign nicknames to model elements

Model element nicknaming in different editions of VP-UML

Features P. 13
Model transitor
Setup and maintain transition between models through the Model Transitor

Enterprise Professional Standard Modeler Personal Community Viewer

Generate and link model elements

Trace the origin of model elements (model traceability)

Trace the origin of model elements (model traceability)

Navigate between operation and sequence diagram

Transit Entity relationship diagram from Conceptual to Logical to


Physical

Model Transitor support in different editions of VP-UML

Style and formatting


Define and apply style and formatting to shapes.

Enterprise Professional Standard Modeler Personal Community Viewer

Manage and apply styles within project

Customizable shape style and formatting

Image incorporation in diagrams

Stereotyped element appearance

Rich text documentation

Add rich text elements to diagrams

Shape format copier

Enrich model documentation with images

Save/load template for model documentation

Display stereotyped model element as image icon

The feature is available but unable to make changes.


Style and Formatting support in different editions of VP-UML

Features P. 14
Team collaboration with VP teamwork server
Perform modeling collaboratively and concurrently with the VP Teamwork Server.

Enterprise Professional Standard Modeler Personal Community Viewer

Concurrent and collaborative modeling with VP Teamwork Server

Import projects to VP Teamwork Server

View projects from VP Teamwork Server

Commit project changes to VP Teamwork Server

Update local project copy using VP Teamwork Server

Review past revisions using VP Teamwork Server

Compare past revisions using VP Teamwork Server

Undo committed changes by reverting revisions

Detect and resolve conflicts using VP Teamwork Server

Branch and tag projects using VP Teamwork Server

Merge branch changes using VP Teamwork Server

Export multiple revisions from VP Teamwork Server

Run VP Teamwork Server on common Java web servers

Element based revision history

Preview local and server changes before commit or update

The feature is available but unable to make changes.


Support of Teamwork Collaboration with Teamwork Server in different editions of VP-UML

Features P. 15
Team collaboration with CVS repository
Perform modeling collaboratively and concurrently with CVS.

Enterprise Professional Standard Modeler Personal Community Viewer

Concurrent and collaborative modeling with CVS Repository

Import projects to CVS Repository

View projects from CVS Repository

Commit project changes to CVS Repository

Update local project copy using CVS Repository

Review past revisions using CVS Repository

Compare past revisions using CVS Repository

Undo committed changes by reverting revisions

Detect and resolve conflicts using CVS Repository

Branch and tag projects using CVS Repository

Merge branch changes using CVS Repository

Export multiple revisions from CVS Repository

Element based revision history

Preview local and server changes before commit or update

The feature is available but unable to make changes.


Support of Teamwork Collaboration with CVS Repository in different editions of VP-UML

Features P. 16
Team collaboration with Subversion repository
Perform modeling collaboratively and concurrently with Subversion.

Enterprise Professional Standard Modeler Personal Community Viewer

Concurrent and collaborative modeling with Subversion Repository

Import projects to Subversion Repository

View projects from Subversion Repository

Commit project changes to Subversion Repository

Update local project copy using Subversion Repository

Review past revisions using Subversion Repository

Compare past revisions using Subversion Repository

Undo committed changes by reverting revisions

Detect and resolve conflicts using Subversion Repository

Branch and tag projects using Subversion Repository

Merge branch changes using Subversion Repository

Export multiple revisions from Subversion Repository

Element based revision history

Preview local and server changes before commit or update

The feature is available but unable to make changes.


Support of Teamwork Collaboration with Subversion Repository in different editions of VP-UML

Features P. 17
Team collaboration with Perforce
Perform modeling collaboratively and concurrently with the Perforce.

Enterprise Professional Standard Modeler Personal Community Viewer

Concurrent and collaborative modeling with Perforce Repository

Import projects to Perforce Repository

View projects from Perforce Repository

Commit project changes to Perforce Repository

Update local project copy using Perforce Repository

Review past revisions using Perforce Repository

Compare past revisions using Perforce Repository

Undo committed changes by reverting revisions

Detect and resolve conflicts using Perforce Repository

Branch and tag projects using Perforce Repository

Merge branch changes using Perforce Repository

Export multiple revisions from Perforce Repository

Element based revision history

Preview local and server changes before commit or update

The feature is available but unable to make changes.


Support of Teamwork Collaboration with Perforce in different editions of VP-UML

Documentation generation
Share your design with your customers in popular document formats (PDF, HTML and MS Word).

Enterprise Professional Standard Modeler Personal Community Viewer

PDF report generation

MS Word report generation [1]

HTML report generation

Project publisher

Ad Hoc report creation [1]

Intelligent element sorting during report generation

[1] This feature is only available for the Windows platform.


Documentation generation support in different editions of VP-UML

Features P. 18
Printing
Print out diagrams using the Print features.

Enterprise Professional Standard Modeler Personal Community Viewer

Print multiple diagrams

Preview printable pages

Print clip marks

Page margin, size and orientation alteration support

Fit-to-pages option

Fit-to-ratio option

Customizable page header and footer

Project name and diagram name display in header or footer

Print with frame or border support

Toggle gradient color printing

Quick print support

This feature is available but the single watermark will be shown.

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.

Printing support in different editions of VP-UML

IDE integrations
Support full software development life-cycle, from analysis to design, and from design to implementation with your most favorite IDE.

Enterprise Professional Standard Modeler Personal Community Viewer

Activate full UML environment from your favorite IDE

Automatic code and model synchronization

Simple integration of any IDE

Import existing VP-UML project to IDE

Integration with Eclipse

Integration with NetBeans

Integration with IntelliJ IDEA

Multilingual support in IDE integration

IDE integration support in different editions of VP-UML

Features P. 19
Reverse engineering
Reverse engineer UML models from source code.

Enterprise Professional Standard Modeler Personal Community Viewer

Reverse engineer source code or executables to class diagrams using


Instant Reverse feature

Reverse engineer Java source code, classes and .jar files

Reverse engineer C++ source code

Reverse engineer .NET .dll and .exe files

Reverse engineer CORBA IDL source code

Reverse engineer Ada 9x source code

Reverse engineer XML

Reverse engineer XML Schema

Reverse engineer databases with JDBC

Reverse engineer Hibernate mapping files

Reverse engineer PHP 5.0 source code

Reverse engineer Python

On-demand Java reverse engineering

Template parameter support

Reverse Engineering support in different editions of VP-UML

Features P. 20
Code generation
Generate various kind of source code from class models.

Enterprise Professional Standard Modeler Personal Community Viewer

Instantly generate source code from class diagrams

Generate Java source code

Generate C# source code

Generate VB.NET source code

Generate PHP 5.0 source code

Generate Object Definition Language source code

Generate Flash ActionScript 3.0 source code

Generate IDL source code

Generate C++ source code

Generate Delphi source code

Generate Perl source code

Generate XML Schema source code

Generate Python source code

Generate Objective-C source code

Generate Ada source code

Generate Ruby source code

Template parameter support

Template support for generating source code with generic constructs

Customizable source code generation

Code generation support in different editions of VP-UML

State machine diagram code generation


Generate code from a state machine diagram for state machine.

Enterprise Professional Standard Modeler Personal Community Viewer

Generate Java source code from state diagram

Generate C++ source code from state diagram

Generate C# source code from state diagram

Generate VB.NET source code from state diagram

State Machine Diagram code generation support in different editions of VP-UML

Features P. 21
Java round-trip engineering
Update between UML class models and Java source code with the round-trip engineering functionalities.

Enterprise Professional Standard Modeler Personal Community Viewer

Reverse engineer Java source code to class diagram

Update Java source code based on class diagram

Java Round-Trip support in different editions of VP-UML

Shape editor
Create domain specific shapes with Shape Editor to use in diagrams.

Enterprise Professional Standard Modeler Personal Community Viewer

Design arbitrary shapes

Import SVG shapes

Incorporate different shapes into UML diagram

Organize shapes by gallery, category and stencil

Advanced shape design capabilities

Shape Editor support in different editions of VP-UML

Layout facilities
Tidy up diagram content by performing layout with several mouse actions.

Enterprise Professional Standard Modeler Personal Community Viewer

Automatic diagram layouts

Shape alignment and centering

Uniform shape width and height maintenance

Automatic shape distribution

Layout support in different editions of VP-UML

Interoperability
Exchange UML diagrams and models with other tools with industrial standard representation.

Enterprise Professional Standard Modeler Personal Community Viewer

Import Telelogic Modeler project files

Import and export EMF based UML2 model

Command-line operations

Import and export XMI 1.0, 1.2 and 2.1

Import and export XML

Import and export VP project file format

Import and export use case model to MS Word

Import Rational Rose project files

Features P. 22
Import ERwin data modeler project files [2]

Generate BPEL code for Oracle workflow engine

Generate BPEL code for JBoss workflow engine

Export diagrams as JPG, PNG, SVG and EMF image files

Export diagrams as PDFs

Slice exported diagrams into smaller segments

Import Rational Software Architect files

Import Rational DNX

Import NetBeans 6.x UML diagrams

Copy diagram elements as XML

Import Visio drawings into Visual Paradigm

Import and export Microsoft Excel file for use case diagram

Import and export Microsoft Excel file for class diagram

Import and export Microsoft Excel file for sequence diagram

Import and export Microsoft Excel file for communication diagram

Import and export Microsoft Excel file for state machine diagram

Import and export Microsoft Excel file for activity diagram

Import and export Microsoft Excel file for component diagram

Import and export Microsoft Excel file for deployment diagram

Import and export Microsoft Excel file for package diagram

Import and export Microsoft Excel file for object 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 requirement diagram

Import and export Microsoft Excel file for basic 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 orm 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 organization chart

Import and export Microsoft Excel file for mind mapping diagram

[2] This feature requires ERwin project on version 7.0 or above.

This feature is available but the single watermark will be shown.


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.

Interoperability support in different editions of VP-UML

Intuitive user interface


User friendly user interface to let you achieve tasks effortlessly.

Enterprise Professional Standard Modeler Personal Community Viewer

Group diagrams by category

Advanced property pane

Dockable user interface windows

New project generation using predefined templates

Easy-to-use "New Diagram" dialog

Flexible zooming

Palette-style toolbar

Collapsible toolbar

Display tool names for toolbar buttons

Expand grouped toolbar buttons

Display various diagram categories in toolbar

Display stereotyped model types in toolbar

Numerous looks-and-feels

Import user preferences from existing workspaces

Multilingual support

Searchable options

Customizable program shortcuts

The feature is available but unable to make changes.


Support of 'intuitive user interface' in different editions of VP-UML

Features P. 24
Automatic updates
Keep VP-UML up-to-date with the automatic updates features.

Enterprise Professional Standard Modeler Personal Community Viewer

Automatic online updating

Maintain local update server with update synchronizer

Support of 'automatic updates' in different editions of VP-UML

Open architecture
Extend VP-UML's functionalities using plug-in

Enterprise Professional Standard Modeler Personal Community Viewer

Plug-in support (Java)

VP model and XML interaction

Support of 'open architect' in different editions of VP-UML

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.

Importing single-seat license key (For purchased customers)


A Visual Paradigm's Single Seat (developer based) license allows a licensee to install the software on more than one machine, such as desktop and
notebook, which belong to the licensee only. As the license is developer based, the software must be used by the licensee only, without running more
for than one instance concurrently. When you run VP-UML the first time, the License Key Manager pops up to let you import the license key.

License Key Manager

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.

Entering the filepath of license key

Licensing P. 26
If the imported key is valid, information of key will appear in the License Key Manager.

License key is imported

Importing evaluation key (For evaluation users)


You can evaluate VP-UML for 10 days without importing any keys. To do this, click Close to close the key manager and continue running VP-UML.
After 10 days gone, the key manager will popup again when you start VP-UML, requesting for a key. At that moment, you must supply a valid key in
order to continue.
If you want to evaluate for a longer period of time, click Request key to request for an evaluation key that enables you to run VP-UML for 30-days.
Click Import key to import the evaluation key into the key manager and continue.

Working with floating license server


Before you use VP-UML with a floating license key, your machine need to access to the license server via LAN to acquire a license key first. For more
details, you can refer to the Floating License Server Installation Guide about floating license server installation for more details.

Configuring floating license server


Floating license need to be acquired from server, through the License Key Manager. When you start VP-UML the first time, the License Key
Manager will show up automatically. From the License Key Manager, select License Keys > Floating License > Configure... in the menu.

To confirm floating license

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.

Specifying host of license server

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.

Viewing license in license 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.

Exporting floating license key from server


In order to acquire a floating license key, you must have access to the floating license server machine through network. If you need to use VP-UML
offline, which means, at a location that cannot reach the server machine (e.g. when having a meeting outside the office), you can export a floating
license keys to your laptop for running VP-UML with a local license key. Once a key has been exported from server, the number of keys in the server
will decrease by one. The volume will reset once you have imported the licence key back to the server.

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.

To export floating license key

A message appears informing you about the export of license key.


From the moment the key is exported from server, you do not need to connect to the license server anymore until the moment you import the key back
to the server.

Importing floating license key to server


To import an exported floating license key back to license server, start the License Key Manager by selecting Tools > Key Manager... in the main
menu of VP-UML, and select License Keys > Floating License > Import Floating License... in the menu of License Key Manager.

To import floating license key

In the Import Floating License Key dialog box, select the key you need to import and click OK to confirm.

Select the license key to import

This finished importing the key back to server.

Switching from evaluation license key to purchased license key


An evaluation key is required for evaluating VP-UML. But once you have purchased, you will receive a purchased license key from Visual Paradigm.
In order to make the purchased key take effect, you need to remove the evaluation keys, then import the purchased license key. To switching from an
evaluation license key to a purchased license key:
1. Start VP-UML.

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.

To remove all keys in 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.

Various licensing options


Single seat license
Visual Paradigm's single-seat (team-member-based) license allows a licensee to install the software on a computer that belongs, and provides sole
access, to the named user only. Since the license is team-member-based, the software must be used by the licensee only, without running more than
one instance concurrently. The single-seat license only allows installation on a maximum of three computers.

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

Edition 1 Year Maintenance 1 Year Maintenance

(extend current maintenance) (buy maintenance separately)

Enterprise $279.5 $419.5

Professional $139.5 $209.5

Standard $59.5 $89.5

Modeler $19.5 $29.5

Personal $11.5 $17.5

Community not applicable not applicable

Viewer not applicable not applicable


The above software maintenance contract prices are for 1 year only.

Price for single-seat license

Floating license

Software Maintenance P. 31
Prices are provided in US dollar

Edition 1 Year Maintenance 1 Year Maintenance

(extend current maintenance) (buy maintenance separately)

Enterprise $363.5 $545.5

Professional $181.5 $272.5

Standard $77.5 $116.5

Modeler $25.5 $38.5

Personal not applicable not applicable

Community not applicable not applicable

Viewer not applicable not applicable


The above software maintenance contract prices are for 1 year only.

Price for floating license

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.

IDE requirements (for IDE integration)


• Eclipse 3.1 or above
• IntelliJ IDEA 4 or above (8.1 ready)
• NetBeans 4.0 or above (6.8 ready)

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).

Using installer (.exe)


1. Execute the downloaded VP Suite installer file. The setup wizard appear as below.

VP Suite Welcome screen

2. Click Next to proceed to the License agreement page.


3. Read through the License Agreement carefully. Make sure you accept the terms before continuing with the installation. If you accept the
agreement, select I accept the agreement and click Next > to proceed to the Select Destination Directory page.

The License Agreement

Installing Visual Paradigm for UML on Windows 2000/NT/2003/XP/Vista P. 34


4. Specify the directory for installing VP Suite. Click Next > to proceed to the next page.
5. Specify the name of the Start Menu folder that will be used to store the shortcuts. Keep Create shortcuts for all users checked if you want the
shortcut to be available in all the user accounts in the machine. Click Next > to proceed.
6. In the File Association page, keep Visual Paradigm Project (*.vpp) and Visual Paradigm License File (*.zvpl) checked if you want your
system able to open the project file and the license key file. Click Next > to proceed to the product selection page.
7. Select Visual Paradigm for UML. Click Next > to proceed to the product configuration page.

The product selection page

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.

Select product edition

Installing Visual Paradigm for UML on Windows 2000/NT/2003/XP/Vista P. 35


9. 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.

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

Installing Visual Paradigm for UML on Windows 2000/NT/2003/XP/Vista P. 36


11. A combined license key is a key file which allows unlocking multiple products. To import a combined license key, select Combined License Key
and specify the file path of the key.
A single license key is a key file which allows unlocking only one product. To import a single license key, select Single License Key and specify
the file path of the key.
The import of license key is optional at this point, because you can import it when you run VP-UML. Click Next > to proceed with copying files.

The license key selection page

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.

Installing Visual Paradigm for UML on Windows 2000/NT/2003/XP/Vista P. 37


12. 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.

Installation completed screen

Using no install version (.zip)


1. Decompress the downloaded zip file into a directory. This should create a subdirectory named &ldquo;VP Suite 4.0&rdquo; where 4.0 is the
version number.

Extracting No-Install zip file

Installing Visual Paradigm for UML on Windows 2000/NT/2003/XP/Vista P. 38


2. Change directory to &ldquo;VP Suite 4.0\bin&rdquo; and execute VP Suite in it.

Launching VP Suite

3. Select Visual Paradigm for UML. Click Next > to proceed to the product configuration page.

The product selection page

Installing Visual Paradigm for UML on Windows 2000/NT/2003/XP/Vista P. 39


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.

Select product edition

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

Installing Visual Paradigm for UML on Windows 2000/NT/2003/XP/Vista P. 40


6. A combined license key is a key file which allows unlocking multiple products. To import a combined license key, select Combined License Key
and specify the file path of the key.
A single license key is a key file which allows unlocking only one product. To import a single license key, select Single License Key and specify
the file path of the key.
The import of license key is optional at this point, because you can import it when you run VP-UML. Click Next > to proceed with copying files.

The license key selection page

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.

Installation completed screen

Installing Visual Paradigm for UML on Windows 2000/NT/2003/XP/Vista P. 41


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: I don't have administrator right, can I install the software?
Answer: Yes, you can.
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.

Installing Visual Paradigm for UML on Windows 2000/NT/2003/XP/Vista P. 42


Installing Visual Paradigm for UML on Mac OSX
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 (.dmg) and no-install (.zip).

Using installer (.dmg)


1. Execute the downloaded VP Suite installer file:
bash ./%VP-SUITE-INSTALLER-FILENAME% (e.g. bash ./VP_Suite_Linux_7_0.sh)
The setup wizard appear as below.

VP Suite Welcome screen

2. Click Next to proceed to the License agreement page.

Installing Visual Paradigm for UML on Mac OSX P. 43


3. Read through the License Agreement carefully. Make sure you accept the terms before continuing with the installation. If you accept the
agreement, select I accept the agreement and click Next > to proceed to the Select Destination Directory page.

The License Agreement

4. Specify the directory for installing VP Suite. Click Next > to proceed to the next page.

The Select Destination Directory page

Installing Visual Paradigm for UML on Mac OSX P. 44


5. In the File Association page, keep Visual Paradigm Project (*.vpp) and Visual Paradigm License File (*.zvpl) checked if you want your
system able to open the project file and the license key file. Click Next > to proceed to the product selection page.

The Select File Associations page

6. Select Visual Paradigm for UML. Click Next > to proceed to the product configuration page.

The product selection page

Installing Visual Paradigm for UML on Mac OSX P. 45


7. 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.

Select product edition

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.

Pre-configure floating license server connection for floating license user

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

Installing Visual Paradigm for UML on Mac OSX P. 46


10. A combined license key is a key file which allows unlocking multiple products. To import a combined license key, select Combined License Key
and specify the file path of the key.
A single license key is a key file which allows unlocking only one product. To import a single license key, select Single License Key and specify
the file path of the key.
The import of license key is optional at this point, because you can import it when you run VP-UML. Click Next > to proceed with copying files.

The license key selection page

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.

Installing Visual Paradigm for UML on Mac OSX P. 47


11. 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.

Installation completed screen

Using no install version (.tgz)

Installing Visual Paradigm for UML on Mac OSX P. 48


1. Decompress the downloaded zip file into a directory.
tar -zxf %NO-INSTALL-FILE.tar.gz% -C %DESTINATION-FOLDER%
This should create a subdirectory named &ldquo;VP Suite 4.0&rdquo; where 4.0 is the version number.

Extracting No-Install zip file

2. Change directory to &ldquo;VP Suite 4.0/bin&rdquo; and execute VP Suite in it.

Launching VP Suite

Installing Visual Paradigm for UML on Mac OSX P. 49


3. Select Visual Paradigm for UML. Click Next > to proceed to the product configuration page.

The product selection page

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.

Select product edition

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

Installing Visual Paradigm for UML on Mac OSX P. 50


6. A combined license key is a key file which allows unlocking multiple products. To import a combined license key, select Combined License Key
and specify the file path of the key.
A single license key is a key file which allows unlocking only one product. To import a single license key, select Single License Key and specify
the file path of the key.
The import of license key is optional at this point, because you can import it when you run VP-UML. Click Next > to proceed with copying files.

The license key selection page

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.

Installation completed screen

Installing Visual Paradigm for UML on Mac OSX P. 51


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.

Installing Visual Paradigm for UML on Mac OSX P. 52


Installing Visual Paradigm for UML on Linux and Unix
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 (.sh) and no-install (.zip).

Using installer (.sh)


1. Execute the downloaded VP Suite installer file:
bash ./%VP-SUITE-INSTALLER-FILENAME% (e.g. bash ./VP_Suite_Linux_7_0.sh)
The setup wizard appear as below.

VP Suite Welcome screen

2. Click Next to proceed to the License agreement page.

Installing Visual Paradigm for UML on Linux P. 53


3. Read through the License Agreement carefully. Make sure you accept the terms before continuing with the installation. If you accept the
agreement, select I accept the agreement and click Next > to proceed to the Select Destination Directory page.

The License Agreement

4. Specify the directory for installing VP Suite. Click Next > to proceed to the next page.

The Select Destination Directory page

Installing Visual Paradigm for UML on Linux P. 54


5. select a folder for creating symlinks. You may select Don't create symlinks if you do not want to. Click Next to proceed.

The Select Symlinks Directory page

6. Select Visual Paradigm for UML. Click Next > to proceed to the product configuration page.

The product selection page

Installing Visual Paradigm for UML on Linux P. 55


7. 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.

Select product edition

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.

Pre-configure floating license server connection for floating license user

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

Installing Visual Paradigm for UML on Linux P. 56


10. A combined license key is a key file which allows unlocking multiple products. To import a combined license key, select Combined License Key
and specify the file path of the key.
A single license key is a key file which allows unlocking only one product. To import a single license key, select Single License Key and specify
the file path of the key.
The import of license key is optional at this point, because you can import it when you run VP-UML. Click Next > to proceed with copying files.

The license key selection page

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

Installing Visual Paradigm for UML on Linux P. 57


11. 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.

Installation completed screen

Using no install version (.tar.gz)

Installing Visual Paradigm for UML on Linux P. 58


1. Decompress the downloaded zip file into a directory.
tar -zxf %NO-INSTALL-FILE.tar.gz% -C %DESTINATION-FOLDER%
This should create a subdirectory named &ldquo;VP Suite 4.0&rdquo; where 4.0 is the version number.

Extracting No-Install zip file

2. Change directory to &ldquo;VP Suite 4.0/bin&rdquo; and execute VP Suite in it.

Launching VP Suite

Installing Visual Paradigm for UML on Linux P. 59


3. Select Visual Paradigm for UML. Click Next > to proceed to the product configuration page.

The product selection page

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.

Select product edition

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

Installing Visual Paradigm for UML on Linux P. 60


6. A combined license key is a key file which allows unlocking multiple products. To import a combined license key, select Combined License Key
and specify the file path of the key.
A single license key is a key file which allows unlocking only one product. To import a single license key, select Single License Key and specify
the file path of the key.
The import of license key is optional at this point, because you can import it when you run VP-UML. Click Next > to proceed with copying files.

The license key selection page

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.

Installing Visual Paradigm for UML on Linux P. 61


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.

Installation completed screen

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.

Installing Visual Paradigm for UML on Linux P. 62


Switching edition
Product edition can be changed through the Product Edition Manager without the need of re-installation. When you attempt to switch to another edition,
make sure you have the required key in order to run the product in new edition.
1. Launch the Product Edition Manager under the bin folder of VP Suite installation folder.

Launching Product Edition Manager

2. Select the edition to switch to in the edition manager.

Select product edition

3. Click Next to confirm.

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

Uninstalling Visual Paradigm for UML P. 64


Starting Visual Paradigm for UML
Ways of starting Visual Paradigm for UML
VP-UML can be launched through accessing the Start Menu.

Starting Visual Paradigm for UML via Start Menu

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 with launcher

Starting Visual Paradigm for UML P. 65


For Linux users, VP-UML can be started through the shortcuts in desktop, created by the installer.

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

Editing the start up 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

Specify the workspace folder.


If you do not want this dialog box to appear again, check Use this as the default and do not ask again. This will cause VP-UML to open the specified
workspace folder automatically the next time.
If you already have an existing workspace, you can import the settings from there by clicking Import Workspace....

Starting Visual Paradigm for UML P. 66


Click OK to continue.

Starting Visual Paradigm for UML P. 67


Interface overview
VP-UML's user interface comprises a menu bar, a toolbar several panes for model navigation, a message pane and a diagram pane that occupy most
spaces.

User Interface of Visual Paradigm for UML

No. Name Description

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.

5 Diagram pane The diagram will be displayed in diagram pane.

6 Message pane Information, notification or warnings will be shown here.

Description of user interface

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

The File menu

The File menu enables you to:


• Create a project
• Create a diagram
• Open project
• Save project
• Save and manage project template.
• Import project data from the following media: VP-UML Project, Rose Project, XMI, XML, Erwin Project, Telelogic Rhapsody Project, Telelogic
System Architect, Rational Model, Rational DNX, MS Word (Use Case Model documentation exported from VP), Excel (Exported from VP),
Visio, NetBeans
• Export project into the following formats: VP-UML Project, XMI, XML, MS Word (for Use Case Model), Excel
• Export images (JPG, PNG, SVG, EMF, PDF)
• Printing
• Set project properties
• Exit

Edit menu

Menu bar P. 69
The Edit menu

The Edit menu enables you to:


• Undo and Redo
• Cut
• Copy
• Duplicate
• Delete
• Change the end model element of connector
• Repeat an action
• Select everything in diagram
• Find a model element/diagram
• Jump to a diagram or an element
• Add or manage bookmarks
• Grouping
• Shapes alignment and distribution

View menu

Menu bar P. 70
The View menu

The View menu enables you to:


• Show/Hide a pane
• Show and manage grid
• Manage Layers
• Change Resource Centric behavior
• Save, open and manage perspective
• Change VP-UML to show in full screen
• Zoom diagram in and out
• Manage nickname
• Manage style
• Show spell check

Tools menu

Menu bar P. 71
The Tools menu

The Tools menu enables you to:


• Generate report
• Publish project
• Perform use case scheduling
• Open various kind of element grid
• Configure stereotypes
• Configure requirements
• Configure programming language
• Customize use case ranks
• Reverse and Forward engineering with Instant Reverse and Instant Generator
• Perform round-trip engineering
• Reverse DDL
• Perform Object Relational Mapping (ORM)
• Perform State Machine Code Generation
• Launch Animacian
• Launch Simulacian
• Perform IDE integration
• Perform Visio integration
• Launch Shape Editor
• Perform Teamwork operations
• Launch DB-VA SQL
• Compare diagrams with Visual Diff

Menu bar P. 72
• Launch License Key Manager
• Configure application options through the Options dialog box

Window menu

The Window menu

The Window menu enables you to:


• Navigate between diagram
• Rearrange diagram windows
• Switch to another diagram
• Show the Start Page
• Close Diagrams

Help menu

The Help menu

The Help menu enables you to:


• Browse the help contents
• Check the instruction of Mouse Gesture
• Visit Visual Paradigm online support
• Repair project
• Customize the user interface
• Check the environment using the About dialog box

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.

Show or hide Standard toolbar

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.

Drag toolbar with the handle of toolbar

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.

Uncheck the Rearrangable option

Standard toolbar

The Standard toolbar

Icon Name Description

New Project Create a project.

Open Project Open a project.

Save Project Save the changes made in the opening project.

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.

Cut Cut selected diagram elements.

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.

Undo Roll back undesired changes.

Redo Rerun an undone task.

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.

Impact Analysis Select and create Matrix 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).

Project Publisher Publish project to Web pages through Project Publisher.

Open Teamwork Client Open the Teamwork Client dialog box.

Commit Commit changes to server.

Update Update changes from server.

Tag Create a tag.

Toolbar P. 75
Branch Create a branch.

Merge Merge changes between trunk and branches.

Switch Switch between trunk, branches and tags.

Revert Click it to undo all non-committed changes in working project.

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).

Wizards... Open the ORM Wizards.

Toolbar P. 76
Database Configuration... Open the Database Configuration dialog box to configure database connections.

Reverse Database... Reverse engineering from database.

Reverse Java Classes... Reverse engineering from Java Class.

Reverse Hibernate... Reverse engineering from Hibernate mapping file.

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.

Using the dockable user interface


The Dockable User Interface is composed of a number of windows called dockable frames. A dockable frame may be standalone (floating) or docked
into another container (split pane/tab pane).
You can press on the title bar of a dockable frame or press on a tab to drag it to anywhere you like.

A frame can be dragged out and dock to elsewhere

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.

Docking a dockable frame to elsewhere


By dragging out a dockable frame/tab, and move the cursor to certain position, the frame/tab will be repositioned accordingly.
If you drag the dockable frame/tab and release it over another container, the gray outline will change its shape to fit the dockable area of the container.
If you release the frame/tab, it will be docked into the underlying container and also removed from its original container.

A frame docked to the right of application screen

Dockable User Interface P. 78


You also can drag a frame/tab out to make it a floating window.

A frame is floating on the application screen

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.

A frame docked to another frame

Dockable User Interface P. 79


Auto-hiding a dockable frame
A dockable frame can be set to "auto hide", meaning it will automatically disappear when not active. To set a dockable frame to "auto hide", click on the
Toggle auto-hide button on the upper right corner of the frame (the button with a pin as the icon, see figure below)

Diagram Navigator is hidden

Dockable User Interface P. 80


Diagram navigator
Diagram navigator is the location where diagrams are listed. You can create your own diagrams easily as they are listed by categories, such as UML
Diagrams, Requirements Capturing, Database Modeling, Business Process Modeling and Others. With diagram navigator, you can create, open and
delete diagrams.

The diagram navigator

The toolbar
Name Icon Description

New diagram Create a new diagram through the New Diagram dialog box.

Collapse Collapse the selected diagram.

Expand Expand the selected diagram.

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

Move Selected Diagram Move the selected diagram down or up.


This option only works within the same diagram type when there are multiple diagrams.

Refresh Update the content of diagram tree.

The description of icons on diagram navigator

Pop-up menu
Pop-up menu of diagram navigator

Diagram navigator P. 81
The pop-up menu of diagram navigator

Menu Title Description

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

Sorting Select the way to sort diagram elements in diagram navigator.

Group by Category Categorize diagrams base on their types.

Teamwork Perform teamwork activities.

Manage Dependent Project... Add or remove dependent project.

Refresh Refresh diagram navigator content.

Collapse All Collapse all tree nodes.

Expand All Expand all tree nodes.

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.

The description of pop-up menu of diagram navigator

Pop-up menu of project node

The pop-up menu of project node in diagram navigator

Menu Title Description

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.

Nicknames Configure or switch to another nickname.

New Diagram... Create a diagram.

Configure Programming Change to another programming language or configure the type mapping for a language.
Language...

Group by Category Categorize diagrams base on their types.

Sorting Select the way to sort diagram elements in diagram explorer.

Teamwork Perform teamwork activities.

Refresh Refresh diagram navigator.

Collapse All Collapse the project node.

Expand All Expand the project node.

The description of pop-up menu of project node

Pop-up menu of diagram category

The pop-up menu of diagram category in diagram navigator

Menu Title Description

New Diagram... Create a diagram.

Collapse Collapse the selected diagram category node.

Expand Expand the selected diagram category node.

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.

The description of pop-up menu of diagram category

Pop-up menu of diagram type

The pop-up menu of diagram type in diagram navigator

Diagram navigator P. 83
Menu Title Description

New [diagram type] Create a new diagram in the selected type.

New Diagram... Create a new diagram with popup dialog box.

Sort [diagram type] by Sort the diagram nodes of the selected type node in specific way.
name

Collapse Collapse the selected diagram type node.

Expand Expand the selected diagram type node.

The description of pop-up menu of diagram type

Pop-up menu of diagram

The pop-up menu of diagram in diagram navigator

Menu Title Description

Open [diagram name] Specification... Open the specification of the selected diagram.

Open [diagram name] Open the selected diagram if closed or inactive.

Close [diagram name] Close the selected diagram if opened.

Use Case Scheduling... Open Use Case Scheduling dialog box.

Rename... Rename the selected diagram.

Lock Set a password to lock the diagram. On the other hand, you can type the password to unlock the diagram.

Delete Delete the selected 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.

Export VP-UML Project... Export the selected diagram as VP-UML project.

Export XML... Export the selected diagram as XML.

Export Selected as Image... Export the selected diagram as image Excel.

Export as Image... Export diagram(s) as image via the Diagram Exporter.

Export to Excel... Export the selected diagram as image Excel.

Print... Print the selected diagram.

Move Up Move the selected diagram node upwards.

Move Down Move the selected diagram node downwards.

Collapse Collapse the selected diagram node.

Expand Expand the selected diagram node.

Sorting Change the way of sorting diagram elements.

The description of pop-up menu of diagram

Closing and opening the diagram navigator


Diagram navigator is opened by default. To close it, press the X button at the top right corner. On the other hand, it can be opened by selecting View >
Panes > Diagram Navigator from the main menu.

Creating a diagram
Approach 1 &ndash; 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

Approach 2 &ndash; Through the New Diagram dialog box


This approach let you create a diagram and enter the name and documentation simultaneously. To create a diagram:
1. Right click on the diagram type that you want to create.
2. Select New Diagram from the pop-up menu.

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.

New Diagram dialog box

Opening a diagram
Double click in the diagram you want to view in the diagram tab.

Sorting diagram elements


In diagram navigator, diagram elements are listed under diagram nodes. You can sort diagram elements by their names, or by their types (e.g. use
case, package, etc.)
To sort by name, click Sort Diagram Element by Name button. The elements will be listed by name, in alphabetical order.

Click Sort Diagram Element by Name

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.

Filtering model elements


You can choose which model elements you want to be displayed or not on the diagram tree.
1. Right click on the diagram navigator's background and select Filter Model Element. Model Element Filtering Dialog will then be pop-up.

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.

Model Element Filtering dialog box

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)

Showing/hiding carriage return character


If it is the case that the name of the diagram and diagram elements is in multi-line, the character &para; will be revealed.
When Show Carriage Return Character is selected, line break will be shown.

To show carriage return character

When deselected, the character &para; is hidden.


If you want to hide it, uncheck Show Carriage Return Character and the character will automatically be unshown.

Grouping or ungrouping by category


As it is said before, default groups are automatically arranged by category.
If you want to ungroup diagram:
1. Right click on the diagram navigator's background.

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

Connecting to server for team collaboration


VP-UML's team collaboration support enables your team members work together on projects. To connect to server and perform related activities:
1. Right click on the diagram background.
2. Select Teamwork and the action you want to perform (e.g. commit and update, etc) from the pop-up menu.

Perform teamwork

Displaying only diagram nodes but not diagram elements


If you only want the diagram nodes to be shown but not the diagram elements under them, just click on Show Diagram View button.

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 Model Explorer

The toolbar
Name Icon Description

New Model Element Create a new model element.

Collapse Collapse the selected model element.

Expand Expand the selected model element.

No Sorting Arrange model elements without grouping.

Sort By Name Sort model elements by their names in alphabetical order.

Sort By Type Sort model elements by their types.

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.

Refresh Update the content of model explorer.

The description of icons on Model Explorer

Popup menu

Model explorer P. 89
Popup menu of model explorer
The Model Explorer lists all the model elements in the project.

The popup menu of Model Explorer

Menu Title Description

Model Create a Model.

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

Sorting Select the way to sort model elements in Model Explorer.

Teamwork Perform teamwork activities.

Manage Dependent Project... Add or remove dependent project.

Refresh Refresh Model Explorer content.

Collapse All Collapse all tree nodes.

Expand All Expand all tree nodes.

Popup menu of project

Model explorer P. 90
The popup menu of project node in Model Explorer

Menu Title Description

No View Model Elements... It lists the model element(s) that either has not been visualized (no view) or has no master view.

Rename... Rename the project.

Nicknames Configure or switch to another nickname.

Create Profile Create a profile.

Model Create a Model.

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...

Sorting Select the way to sort model elements in Model Explorer.

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).

Teamwork Perform teamwork activities.

Manage Dependent Project... Add or remove dependent project.

Refresh Refresh Model Explorer.

Collapse All Collapse the project node.

Expand All Expand the project node.

Closing and opening the model explorer


Model Explorer is opened by default. To close it, press the X button at the top right corner. On the other hand, it can be opened by selecting View >
Panes > Model Explorer from the main menu.

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.

Select New Model in pop-up menu

Creating a model element


A model element is created when you create a shape on a diagram. If you want to create a model element without visualizing it, you can create it
through the Model Explorer. To create a model element:
1. Right click on the root node.
2. Select Model Element> New Model Element..., or select a pre-defined model element from the pop-up menu.

Select New Model Element from the pop-up menu

Sorting model elements


In model explorer, model elements are listed under root nodes. You can sort model elements by their names, by their types (e.g. use case, package,
etc.) or with no sorting.

Model explorer P. 92
To sort by name, click Sort by Name button. The elements will be listed by name, in alphabetical order.

Sort model elements by name

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.

Reordering model elements


Select the model element(s) you want to reorder. If there are multiple model elements you want to select, just click one while pressing Ctrl button and
make the other selections.
Click Move Selected Model Element Up button to move the selection upwards, or Move Selected Model Element Down button to move the
selection downwards.

NOTE: This option only works within the same model element type when there are multiple model elements.

Filtering model elements


You can choose which model elements you want to be displayed or not on the model explorer.
Right click on the model explorer's background and select Filter Model Element. In Model Element Filtering Dialog, select the types of model
element(s) you want to be displayed by checking the type. Otherwise, uncheck the one you don't want to be displayed.

Model Element Filtering Dialog

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.

Showing/hiding carriage return character


If it is the case that the name of model elements is in multi-line, the character &para; will be revealed.
When Show Carriage Return Character is selected, line break will be shown.

Show Carriage Return Character is selected

When off, the character &para; is hidden.


If you want to hide it, uncheck Show Carriage Return Character and the character will automatically be unshown.

Connecting to server for team collaboration


VP-UML's team collaboration support enables your team members work together on projects. To connect to server and perform related activities:
1. Right click on the model explorer's background.
2. Select Teamwork> Open Teamwork Client... from the pop-up menu.

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 Class Repository

The toolbar
Name Icon Description

New Model To create a new model element.


Element

Collapse To collapse the selected model element.

Expand To expand the selected model element.

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.

Refresh To update the content of Class Repository

The description of icons on Class Repository

Pop-up menu
Pop-up menu of class repository

The pop-up menu of Class Repository

Menu Title Description

Model Create a Model.

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.

Manage Dependent Project... Add or remove dependent project.

Refresh Refresh Class Repository content.

Collapse All Collapse all tree nodes.

Expand All Expand all tree nodes.

Popup menu of project

The pop-up menu of project node in Class Repository

Menu Title Description

No View Model Elements... It lists the model element(s) that either has not been visualized (no view) or has no master view.

Rename... Rename the project.

Nicknames Configure or switch to another nickname.

Model Create a Model.

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...

Teamwork Perform teamwork activities.

Manage Dependent Project... Add or remove dependent project.

Refresh Refresh Class Repository.

Collapse All Collapse the project node.

Expand All Expand the project node.

Closing and opening the Class Repository


Class Repository is opened by default. To close it, press the X button at the top right corner. On the other hand, it can be opened by selecting View >
Panes > Class Repository from the main menu.

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.

Select New Model from the pop-up menu

Creating a model element


A model element is created when you create a shape on a diagram. If you want to create a model element without visualizing it, you can create it
through the Class Repository. To create a model element:
1. Right click on the project root node.
2. Select Model Element> New Model Element..., or select a pre-defined model element from the pop-up menu to create a new model.

Select New Model Element from the pop-up menu

Showing/hiding carriage return character


If it is the case that the name of model elements is in multi-line, the character &para; will be revealed.
When Show Carriage Return Character is selected, line break will be shown.

Show Carriage Return Character is revealed

When off, the character &para; is hidden.


If you want to hide it, uncheck Show Carriage Return Character and the character will automatically be unshown.

Connecting to server for team collaboration


VP-UML's team collaboration support enables your team members work together on projects. To connect to server and perform related activities:

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 Logical View

The toolbar
Name Icon Description

Collapse To collapse the selected diagram.

Expand To expand the selected diagram.

Refresh To update the content of logical view.

Set Logical View Structure as Default To set default structure for logical view in all projects.

The description of icons on Logical view

Pop-up menu
Pop-up menu of logical view

The pop-up menu of Logical View

Menu Title Description

Show Carriage Return Display line breaks of multi-lined diagram name as carriage return character.
Character

Teamwork Perform teamwork activities.

Manage Dependent Project... Add or remove dependent project.

Refresh Refresh Logical View content.

Logical view P. 99
Collapse All Collapse all tree nodes.

Expand All Expand all tree nodes.

Pop-up menu of project

The pop-up menu of project node in Logical View

Menu Title Description

Rename... Rename the project.

Add View Add a view under project.

New Diagram Create a diagram under root view.

Add Existing Diagram... Add an existing diagram under root view.

Import View from XML Import logical view configuration file.

Export View to XML Export logical view as configuration file.

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.

Sort Child by Name Sort the views by name.

Teamwork Perform teamwork activities.

Collapse All Collapse the project node.

Expand All Expand the project node.

Pop-up menu of view

The pop-up menu of view in Logical View

Menu Title Description

Logical view P. 100


Add View Add a child view under the selected view.

New Diagram Create a diagram under the selected view.

Add Existing Diagram... Add an existing diagram under the selected view.

Sort Child by Name Sort the views/diagrams by name.

Collapse Collapse the selected view node.

Expand Expand the selected view node.

Rename... Rename the selected view.

Delete Delete the selected view.

Closing and opening the Logical view


Logical view is opened by default. To close it, press the X button at the top right corner. On the other hand, it can be opened by selecting View >
Panes > Logical View from the main menu.

Creating a new view node


Right-click a root node on Logical View and select Add View from the pop-up menu.

Click Add View from the pop-up menu

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.

Created new view node

Logical view P. 101


Adding diagram to view
After you create a few diagrams, right-click on a view node and select Add Existing Diagram... from the pop-up menu.

Select Add Existing Diagram... from the pop-up menu

In Select Diagrams Dialog, check the diagrams you would like to insert in the view node.

Check diagrams in Select Diagrams Dialog

Click OK button to confirm the selection.

Creating a new diagram


Right click the newly created view node, select New Diagram from the pop-up menu and then select New Diagram... or a pre-defined diagram.

Select New Diagram... from the pop-up menu

A new diagram is, therefore, created under the view node.

Logical view P. 102


Opening a diagram
Double click on the diagram you want to view in the logical view.

Setting Default View Structure


VP-UML provides a feature where you can set the current logical view structure as default, therefore, you may save your time and do not have to re-
create the structure every time you create a new project.
Either click Set Logical View Structure as Default button on the top of logical view or right click a root node to select Set Logical View Structure as
Default.

Click Set Logical View


Structure as Default button

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.

Sorting diagram by name


In logical view, diagram are listed under diagram nodes by default. You can sort child diagrams by their names as well.
To sort by name, right click on view node and select Sort Child by Name from the pop-up menu. The child diagrams will be listed by name, in
alphabetical order.

Click Sort Child by Name

NOTE: The sort function applies to the entire logical view instead of the selected node.

Showing/hiding carriage return character


If it is the case that the name of the diagram is in multi-line, the character &para; will be revealed.

Logical view P. 103


When Show Carriage Return Character is selected, line break will be shown.

To show carriage return character

When off, the character &para; is hidden.


If you want to hide it, uncheck Show Carriage Return Character and the character will automatically be unshown.

Exporting View Structure to XML


VP-UML allows you to export the current Logical View Structure as an XML file and to re-use it again on other projects.
Right click the root node and select Export View to XML from the pop-up menu.

Click Export View to XML from the pop-up menu

Logical view P. 104


Find a location for exporting the project and enter its file name in Save dialog box. At last, click the Save.

Enter the file name in Save dialog box

Importing View Structure from XML


VP-UML also allows you to import the existing xml file in your new project.
Right click on the root node and select Import View to XML from the pop-up menu.
In Open dialog box, browse and select the xml file to be imported. You can choose one out of two following choices provided for importing a logical
view structure:
1. Append to existing structure: the imported structure will be added to the current structure without deleting the old one.
2. Replace existing structure: the new imported structure will replace the current structure. Therefore, the current structure will be removed.

Select export.xml in Open dialog box

Connecting to server for team collaboration


VP-UML's team collaboration support enables your team members work together on projects. To connect to server and perform related activities:
1. Right click on the logical view's background.

Logical view P. 105


2. Select Teamwork and the action you want to perform from the pop-up menu.

Performce teamwork

Logical view P. 106


ORM pane
ORM pane consists of two views, class view and database view. They two serve two distinct purposes. The class view act as a media to convert
domain source code into UML persistable class model, while the database view act as a media to convert database schema into entity models.

An ORM pane (Database view)

An ORM pane (Class view)

The toolbar
Name Icon Description

Database View / Class Switch between views.


View
Class view - act as a media to convert domain source code into UML persistable class model.
Database view - act as a media to convert database schema into entity models.

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.

The description of icons on ORM pane

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.

ORM pane P. 107


In order to list tables, you need to configure the database connection first. Click to open the Database Configuration dialog box. Then, specify the
database connection for the database you want to have its tables list in ORM pane.

Configuring database connection

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.

Entity relationship diagram is formed from entities in ORM pane

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.

ORM pane P. 108


In order to list classes, you need to configure add classpaths first. Click to open the Classpath Configuration dialog box. Then, add the classpaths
of classes you want to list in ORM pane.

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.

Class diagram is formed from classes in ORM pane

ORM pane P. 109


Property pane
Property pane is the location where the properties of a diagram, model element or shape are listed. With Property pane, you can view and edit
properties directly.

The Property pane

The toolbar
Name Icon Description

Categorized To sort all properties by their category.


View

Alphabetical To sort all properties in ascending order base on their names.


View

Collapse To collapse all properties of each subitem.

Expand To expand all properties of each subitem.

The description of icons on Property pane

Closing and opening the Property pane


Property pane is opened by default. To close it, press the X button at the top right corner. On the other hand, it can be opened by selecting View >
Panes > Property from the main menu.

Viewing the properties


Click a shape that you would like to view its properties directly when the shape is shown on diagram pane. There are not only the properties of shapes,
but also the properties of diagrams in Diagram Navigator and the properties of model elements in Model Explorer that can be viewed in property
pane.
Select a diagram on Diagram Navigator to view the properties of diagram or select a model element in Model Explorer to view the properties of
model element.

Property pane P. 110


Viewing the properties in shortcut
When a diagram, model element or shape is selected, its properties are shown on property pane. Meanwhile, you are allowed to view other properties,
which are in the same diagram, in shortcut by selecting the diagram, model element and shape from dropdown menu at the top of the property pane.

Select Customer -
Pool in dropdown menu

Sorting the properties


In Property pane, the properties of a diagram, model element and shape are listed. You can sort the properties by their category, or in ascending order.
To sort by the name of properties, click Alphabetical View button. All properties will be listed in ascending order base on their names.

Click Alphabetical Vie w

To sort by category, click Categorized View button. As a result, all properties will be listed by category.

Property pane P. 111


Diagram overview
Diagram overview is a pane where users can view and zoom in an active diagram directly and shortly.

The Diagram overvi ew

Closing and opening the diagram overview


Diagram overview is opened by default. To close it, press the X button at the top right corner. On the other hand, it can be opened by selecting View >
Panes > Diagram Overview from the main menu.

Viewing an active diagram


An active diagram can be viewed in diagram overview automatically. As the diagram is shown on the diagram pane, it can be viewed in diagram
overview.

An active diagram is shown on Diagram Overview

Having a quick view on a particular part of diagram


There is much truth in saying that viewing a large diagram is such an annoying task, especially a particular part of this large diagram is needed to
focus on. In fact, a particular part of diagram can be navigated by moving the purple rectangle which represents the visible area of diagram in diagram
overview.

Diagram overview P. 112


1. Press on the purple rectangle and drag it to the preferred part of diagram you would like to view.

Drag to the preferred part of diagram

2. As a result, the part of diagram will be subsequently shown on the diagram pane.

The particular part of diagram is viewed on diagram pane

Diagram overview P. 113


Zooming in a particular part of diagram
Drag the diagonal of purple rectangle to zoom in a particular part of diagram. The smaller you drag the purple rectangle, the more the part of diagram
will be magnified.

Drag the diagonal of purple rectangle

On the contrary, the larger you drag the purple rectangle, the more the part of diagram will be dwindled.

Diagram overview P. 114


Documentation pane
Documentation pane enables you to document project data such as model elements, shapes or diagrams either in written or verbal form. For written
content, it can be a plain text or HTML text with formattings like bold, italic, table, etc.

The Documentation pane

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.

Bold Set the highlighted text to bold.

Italic Set the highlighted text to italic.

Underline Underline the highlighted text.

Left Justify Set the alignment of highlighted text to left.

Center Justify Set the alignment of highlighted text to center.

Right Justify Set the alignment of highlighted text to right.

Ordered list Add a numbered list.

Un-ordered list Add a list with bullet points.

Font Select the font family of highlighted text.

Font size Select the size of highlighted text.

Font color Select the color of highlighted text.

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.

Background color Select the background color of highlighted text.

Clear formats Clear formats of whole editor to convert the content to plain text.

Link Add a hyperlink.

Documentation pane P. 115


Image Add an image.

Save as Save the documentation as template.


template...

Manage Preview a saved template.


Template...

Print Print the custom content.

The description of icons on Documentation pane

Closing and opening the Documentation pane


Documentation pane is opened by default. To close it, press the X button at the top right corner. On the other hand, it can be opened by selecting View
> Panes > Documentation from the main menu.

Documenting project data in text


Documentation pane enables users to type in the textual description for project data, for instance, model elements, shapes and diagrams.

Defining a glossary item


A word or a lexis can be defined as a glossary item for explication.
1. Highlight the word or the lexis you would like to be defined and then right click on it. Select Add "..." to Glossary from the pop-up menu to
switch to Glossary Grid.

Select Add "premium plan" to


Glossary from the pop-up menu

2. In Glossary Grid, click Open Specification... button in order to fill more details about the new item.

Click Open Specification... button

Documentation pane P. 116


3. In Term Specification dialog box, click Add button to type the alias(es) for the new item.

Type an alias for 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.

Click Create Term (Insert) button

Checking spelling
When you type an incorrect word carelessly, documentation pane can offer you a help.

Documentation pane P. 117


For correction, right click on the incorrect word with a red curved line and select one out of the suggested words from the pop-up menu.

Select a correct word from the pop-up menu

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.

Documenting a shape by voice


In addition to textual description, documentation pane also enables users to document for project data in verbal form.
Click Record... button for recording voice.

Click Record... button

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.

Click Record in Record Voice dialog box

Name Icon Description

Record Press it to start recording.

Play Press it to play the voice you recorded.

Documentation pane P. 118


Stop Press it to stop recording.

Clear Press it to clear the voice you recorded.

The description of icons on Record Voice dialog box

Documentation pane P. 119


Stencil pane
Stencil pane is a library of custom shapes or images that can be used on diagrams. With Stencil Pane, users can create custom shapes and display
stencils by selecting stencils and drag them on diagram. Furthermore, stencils can be created in Shape Editor.

The Stencil pane

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.

The description of icons on Stencil pane

Closing and opening the Stencil pane


Stencil pane is opened by default. To close it, press the X button at the top right corner. On the other hand, it can be opened by selecting View >
Panes > Stencil from the main menu.

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.

Select Hardwares from the pop-up menu

Stencil pane P. 120


When the subfolder is unfolded, press the preferred stencil and drag it on the diagram pane.

Drag a stencil on the diagram pane

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.

Select Open Shape Editor


from the pop-up menu

In Shape Editor dialog box, click New Shape button.

Click New Shape button

Stencil pane P. 121


Press on the stencil you want to be edited and drag it on the diagram pane.
Insert any shape(s) from the diagram toolbar with your preference and edit the format for the shape(s) in Format tab.

Turn the shadow of stencil into pink

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.

Stencil pane P. 122


Creating project
Visual Paradigm for UML stores information like model elements and diagrams in a project. Therefore, you need to create a project before performing
modeling. To create a project, select menu File > New Project. The New Project dialog box appears. Click on Create Blank Project to create the
project.

Create a new project

Overview of New Project dialog box

An overview of New Project dialog box

No. Name Description

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.

Creating Project P. 123


4 Template A page for you to create a project by selecting a template.

5 Other CASE Tools A page for you to specify either a Rose or XMI file path for creating a new project.
Project

Description of New Project dialog box

Properties
To create a blank project, ensure the Properties page is being selected, and then click the Create Blank Project button.

An overview of Properties page

No. Name Description

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 Project name The name of project.

3 Author The author of project.

4 Company The company of project.

5 Project description The project description. You can make use of the toolbar on top of the description pane to add formatted content.

Description of Properties page

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.

Creating Project P. 124


To create project from template, select the Template page and select a template to use, then click the Create From Template button.

An overview of Template page

No. Name Description

1 Template list A list of template that you have defined before.

2 Template preview By selecting a template from the template list, you can read the structure in the Template preview pane.

3 Template A description of the template.


description

Description of Template page

Other CASE Tools Project


If you have legacy projects created with other CASE tools, you can import them to VP-UML. Select either to import from Rose or from XMI, specify the
file path of source to import and click Create From Other CASE Tools at the bottom of dialog box.

An overview of Other CASE Tools Project page

No. Name Description

Creating Project P. 125


1 Import from Select this option if you want to create a new project by importing a Rational Rose project.
Rose

2 File path The file path of Rational Rose (*.mdl) project.

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

5 File path The file path of XMI (*.xmi) project.

6 Description Description of chosen option.

Description of Other CASE Tools Project page

Creating Project P. 126


Saving project
VP-UML saves all project content to a single file, with file extension .vpp.
To save project, select File > Save Project from the main menu. If you are saving the first time, the Save Project dialog box will appear. You can save
a project to workspace, or any location in the machine. For details, read the sections below.

Saving project to workspace


To save project to workspace, select Save to workspace. Enter the file name and click OK to save.

Save project to workspace

Saving project to specified directory


To save project to a specified directory, select Save to directory, and then specify in the Directory field the directory for saving project. Enter the file
name and click OK to save.

Save project to a specified directory

Saving Project P. 127


Organizing diagrams by model explorer
For small scale project, it would be easy to use Diagram Navigator to manage it. However, for middle to large scale project which has considerable
numbers of diagrams and model elements, it would be better to use Model Explorer to organize the project.
VP-UML loads diagrams and model elements only when they are used. For example, opening a diagram will load all its diagram elements, and opening
the specification dialog box of a model element will cause it (and the model elements it referenced) to be loaded. Besides, selecting a tree node in the
Model Explorer will cause the corresponding element to be loaded as well.
For this reason, we recommend you to group diagrams using Model instead of laying them flat in the project. This can avoid accidentally loading
diagrams and model elements that you never use, and thus can speed up project loading and saving.

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.

Create a model in Model Explorer

Creating diagram in model


To create diagram in model, right-click on the target model, select Diagram from the pop-up menu and then select either create a new diagram or add
existing diagram.

Create a diagram under Model

NOTE: When you create a shape, its model element will be put under the same model as diagram.

Organizing diagrams by model explorer P. 128


Moving diagrams between models
If you are not organizing project structure with model, you may want to do it now. You can move a diagram from root into a model, or transfer a diagram
from one model to another.
To move diagram from one model to another, right-click on the target model in Model Explorer and select Diagram > Add Existing Diagram... from
the popup menu.

Add existing diagram to Model

Select the diagrams you want to move in the Add Sub Diagrams dialog box and click OK button.

Select diagrams to move

The selected diagrams will be moved to the target model.

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.

Organizing diagrams by model explorer P. 129


Project dependency
Project dependency enables you to reference to an another project, and use its model elements in developing our own project. You can organize
our model elements in a more disciplined approach by having one Visual Paradigm project per library project. This also helps to "slim up" projects by
breaking down a project into smaller pieces. Other than this, you can reference to other projects, and create an overview project for them.

Adding dependent projects


To reference to another project:
1. Right-click on the background of any of the following panes and select Manage Dependent Project... from the pop-up menu.
• Diagram Navigator
• Model Explorer
• Class Repository
• Logical View
• ORM

Manage dependent project

2. In the Manage Dependent Projects dialog box, click Add.


3. In the Open dialog box, choose the Visual Paradigm project file (*.vpp) to reference to and click Open.

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.

Using model elements in dependent projects


Once a project dependency has been established, you can develop your model using model elements in dependent project. To do this:
1. In Model Explorer, click on the drop down menu at the top of the pane and select the project that contains the model elements you want to use.

Select a dependent project

NOTE: By selecting the first selection (Current), model elements in the current project will be listed.

Project dependency P. 130


2. In the model element list, select the model element you want to use. Press and drop to diagram. This create views from them.

Form class diagram from model elements in dependent project

NOTE: Alternatively, you can right-click on the model elements and select Create View in Active Diagram from the popup menu.

3. Continue modeling with the referenced elements.

Model with model elements in dependent project

NOTE: Views for dependent project are read-only (i.e. non edit-able).

Mirroring model element


Due to views of dependent model elements are read-only, you cannot add shapes in it. This may be a problem when you want to use dependent
packages in your project, and to add model elements such as classes in it. To overcome this problem, you can create a mirror of container-typed
dependent model element. By mirroring, a dependent element is localized partially by keeping a mirrored copy in your project which echos the element
in dependent project. The mirrored copy can be accessed in Model Explorer that lists model elements in current project, but not editable.
To create a mirror from a container-typed dependent model element (e.g. package, business pools/lanes...), right click on the element in Model
Explorer and select Create Mirror Model Element from popup menu. 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 can also right click on the shape and select Convert to Mirror
from popup menu.

Mirror a dependent package

Project dependency P. 131


Indicating dependent elements on diagram
In order to know which shape(s) on a diagram comes from a dependent project, you can enable to model element indicators. Click on the Show Model
Element Indicators button at the top of diagram toolbar.

To show model element indicators

After that, you can see the indicator, which is a small arrow, appear at the shapes that are referencing a dependent project.

Model element indicator appears

Project dependency P. 132


Maintaining backups
Backup is a copy of project file. The major advantage of backup is to allow you to recover your work, in case you have made some undesired
modification on your project. The backup file is usually put along with the project.
Backup is a default setting. After you save your project, it will be produced subsequently. The name of backup file is basically similar to the name of
project file, but an extra ~ and a number are appended to it.

Backup copy is produced

Setting the backup level


You can set the amount of backup copy for your own reference. Select Tools > Options... from the main menu.

Select Options... from the main menu

Maintaining Backups P. 133


In Options dialog box, click General and select a number from the drop-down menu of Backup level under Project tab. The number of backup level
represents the amount of backup copy that is produced after a project is saved.

Select the amount of backup level in Options dialog box

Maintaining Backups P. 134


Model element and view
A model element is an elementary component of a model. It will be created when you create a shape on a diagram, or when we create one directly
through the Model Explorer. An example of model element is class.

Creat a model element through Model Explorer

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.

Showing a view of a model element


If you want to open a diagram from a model element, right click on the model element in Model Explorer and select Show View... from the popup
menu. Then, select the view to open in the Show View dialog box and click Go to View to open the diagram.

Model element and view P. 135


Master view and auxiliary view
When you create a shape, it creates a model element as well as a view. We call the first view to be created from a model element a master view. For
subsequent views created from the same model element, they are called auxiliary views. A model element can have unlimited number of auxiliary
views. Yet, it can have at most one master view.
A master view differs from auxiliary view in that master view affects the parent assignment of the owned model element, while auxiliary view does not
has such power. For example, if there is a package with a use case in it, and you try to drag the use case out of the package, the use case's parent
will be changed from package to root. However, if the use case is an auxiliary view, moving it to another parent will have the package as its parent,
remaining unchanged.

Converting an auxiliary view to master view


A model element can have multiple views. Yet, it can only have one master view. You can, however, convert an auxiliary view to become a master
view. By doing so, the original master view will become auxiliary, and the assignment of parent element will be updated immediately base on the new
master view when the conversion take place.
To convert an auxiliary view to master view, right click on the auxiliary view and select Selection > Set as Master View from the popup menu.

Converting an auxiliary view to master

Master view and auxiliary view P. 136


Drawing use case diagrams
Use case diagrams can be created in Visual Paradigm for UML. It is recommended to group related diagrams and model elements in a model, this
could improve the performance while saving and loading the project.

Creating a use case diagram


Right click Use Case Diagram on Diagram Navigator and select New Use Case Diagram from the pop-up menu.

Create a use case diagram

Enter name for the newly created use case diagram in the text field of pop-up box on the top left corner.

Enter name for the newly created use case diagram

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

Drawing use case diagrams P. 137


Drawing an actor
To draw an actor, select Actor on the diagram toolbar and then click it on the diagram pane. Finally, name the newly created actor when it is created.

Create an actor

Drawing a use case


Besides creating a use case through diagram toolbar, you can also create it through resource icon.
Move the mouse over a shape and press a resource icon that can create use case. Drag it and then release the mouse button until it reaches to your
preferred place. The source shape and the newly created use case are connected. Finally, name the newly created use case.

Create a use case through resource icon

Line wrapping use case name


If a use case is too wide, for a better outlook, you may resize it by dragging the filled selectors. As a result, the name of use case will be line-wrapped
automatically.

Resize a use case

NOTE: Alternatively, you can press Alt + Enter to force a new line.

Drawing <<Extend>> relationship


To create an extend relationship, move the mouse over a use case and press its resource icon Extend -> Use Case. Drag it to your preferred place
and then release the mouse button. The use case with extension points and a newly created use case are connected. After you name the newly
created use case, a pop-up dialog box will ask whether you want the extension point to follow the name of use case. Click Yes if you want it to do so;
click NO if you want to enter another name for extension point.

Create an extend relationship

Drawing use case diagrams P. 138


Drawing <<Include>> relationship
To create an include relationship, mouse over a use case and press its resource icon Include -> Use Case. Drag it to your preferred place and then
release the mouse button. A new use case together with an include relationship is created. Finally, name the newly created use case.

Include relationship is created

Structuring use cases with package


You can organize use cases with package when there are many of them on the diagram.
Select Package on the diagram toolbar (under Common category).

Create a package

Drag the mouse to create a package surrounding those use cases.

Surround use cases with package

Finally, name the package.

Name the package

Assigning IDs to actors/Use cases


You may assign IDs to actors and use cases. By default, IDs are assigned with the order of object creation, starting from one onwards. However, you
can define the format or even enter an ID manually.

Drawing use case diagrams P. 139


Defining the format of ID
To define the format of ID, select Tools > Options from the main menu to unfold the Options dialog box. Select Diagramming from the list on the left
hand side and select the Use Case Diagram tab on the right hand side. You can adjust the format of IDs under Use Case Diagram tab. The format of
ID consists of prefix, number of digits and suffix.

Use Case Diagram tab

The description of options for ID generator format is shown below.

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.

Options for formatting ID

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

Drawing use case diagrams P. 140


As a result, the use case is displayed with ID.

A use case with ID displayed

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

Drawing business use case


1. Right click on a use case and select Model Element Properties > Business Model from the pop-up menu.

Click Business Model

2. After selected, an extra slash will be shown on the left edge of the use case.

Business model

Drawing use case diagrams P. 141


Documenting use case details
The feature of use case details refers to the basic information, flow of events, requirements and test plan of a use case. Documenting use case details
is essential in recording meaningful and important information for a use case.

Opening use case details


To start editing and viewing use case details, right click on the target use case in use case diagram and select Use Case Details... from the pop-up
menu.

Select Open Use Case Details...

Entering basic information


Basic information refers to all general information of a use case. Rank and justification determine the importance of use case. Select a rank from the
drop-down menu and enter the text in Justification text field.
Primary actors list the actors being involved in a use case. Actors that are connected to a use case are automatically defined as primary actors.
Supporting actor are actors who are beneficial from the system, but without direct interaction. Both primary and supporting actors can be added
manually by pressing the Plus button and select the actors in the pop-up dialog box.

Basic information of use case

Documenting use case details P. 142


Entering flow of events
Flow of events refers to the steps required to go through and fulfill a use case. You may define multiple flows of events under a use case and add
extension to an event as well. For more information about documenting flow of events, read the next chapter Documenting Flow of Events.

Flow of events of use case

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.

Details of use case

Inserting requirement links

Documenting use case details P. 143


1. Click in the text field where you want to insert a requirement link. Click the Insert Requirement... button when it pops out. Note that only fields
where support multiple line are allowed to add requirement links.

Click Insert Requirement... button

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.

Requirements of use case

To add requirement(s) to a use case:


1. Click the Add... button at the bottom right of dialog box.

Documenting use case details P. 144


2. In the Requirements dialog box, look for and select the requirements to add, and click OK to confirm the selection.

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.

Diagrams of use case

Adding a sub-diagram

Documenting use case details P. 145


1. Click the Add button at the bottom of Diagrams page, select a type of diagram from the pop-up menu if you want to add a new diagram as sub-
diagram. On the other hand, select Add Existing Diagrams... if you want to add an existing diagram in your current project.

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.

Writing test plan


While the detailed testing procedure can be documented in flow of events, the testing setup and configurations can be documented in the Test Plan
tab.

Test Plan of use case

Documenting use case details P. 146


Adding references
You may add references to both internal and external artifacts, such as shapes, diagrams, files, folders and URLs for describing the use case in
various views.

References of use case

Opening obsolete use case description


Use Case Description was an obsolete feature removed in Visual Paradigm Suite version 4.1. We recommend users to use the flow of events tool
to document the internal flow of use case rather than making use of use case description. But for the old version users, they can still activate the
Description pane to access the saved data.

Obsolete use case description

Documenting use case details P. 147


You can convert the obsolete use case details to flow of events by clicking on the Convert button at the bottom right corner.

Convert use case description

Documenting use case details P. 148


Documenting flow of events
A flow of events refers to the steps required to go through and then fulfill a use case. Furthermore, multiple flows of events can be defined under a
use case. A few more features are applied in the flow of events, such as model element link presentation options, extension and generating activity
diagram.

Opening flow of events editor


1. In a use case diagram, right click on the target use case and select Open Use Case Details... from the pop-up menu.
2. When the details pane pops out, select the Flow of Events tab.

Flow of Events tab

The flow of events editor


The upper part is the flow of events pane for editing the flow of events step by step while the bottom part is the extension pane for editing extension of
sub item. Furthermore, when Main is chosen from the drop-down menu of (Hide testing procedures), two columns of procedures and expected results
will be shown as testing procedure in the flow of events pane.

The flow of events editor

Button Name Description

Drop-down menu of Flow of Events You may select Manage... from the drop-down menu to create new flow of
events.

Control menu You may select various function in the menu:


Step (Enter): Enter next step.
Extension (Shift+Enter): Enter extension for the selected step.
If: Enter conditional situation for the selected step.
Else if: Insert another situation under If.
Else: Insert it to control If and Else if.
Clear control, Go to previous condition and Go to end.
While:
For each:
Loop until:
Exit:

Documenting flow of events P. 149


Jump:

Add menu Select an existing use case/ actor/ requirement in the current project and insert
it in the selected step for referenced link.

Hyperlink... Add a link in the selected step for reference.

Font Select font effect for the highlighted text: Bold, Italic and Font Color.

Font size Select font size for the highlighted text:


Grow Font: To multiply the font size of flow of events and extension content.
Shrink Font: To reduce the font size of flow of events and extension content.
Default Font: To reset the font size to default.
Moreover, you can adjust the font size for the highlighted text manually by
slider.

Move Up Move a selected step upward.

Move Down Move a selected step downward.

Descrease Indent Decrease the indentation of flow of events by one level.

Increase Indent Increase the indentation of flow of events by one level.

Delete Step Delete the selected step.

Undo Undo a previous action.

Redo Revert a previous action.

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.

Buttons in flow of events editor

Documenting flow of events


1.
Click on the first row to start editing, press Enter or click from the control menu after finish editing the first event and then go to the next
event.

Enter the first event

Documenting flow of events P. 150


2. Repeat the previous steps for creating as much as events you need until all events are documented.

Fill flow of events

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.

Inserting actor/usecase/requirement link


A new feature of actor/ usecase/ requirement link can be attached in a specific event with different presentations.
Select actor/ usecase/ requirement link from the add menu.

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.

An actor link is applied

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.

Select a presentation option

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.

Documenting flow of events P. 151


Adding extension
An extension can be seen as an extension point of use case. It documents the alternative flow that can be extended from the main flow. To add an
extension:
1.
Select a specific event and press for adding extension.
2. You may enter a sub item of an event in the extension pane. Press the Enter key to add a sub item.

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.

Documenting testing procedure


Testing procedure can be documented for each step of the flow. To document testing procedure:
1. Choose Main from the drop-down menu of Testing Procedure to reveal the columns of Procedures and Expected Results respectively.

Select Main

2. Enter the testing procedure for the event that we need to test in Procedures text field.

Enter testing procedures

Documenting flow of events P. 152


3. Enter the result we expected for the testing procedure in Expected Results text field.

Enter expected results

4. Repeat the previous steps until finish documenting the testing procedure.

Creating multiple flow of events


1. To create a new flow of events, select Manage... from the drop-down menu of Flow of Events at the toolbar.

Create multiple flow of events

2. When the Flow of Events dialog box pops out, click the New Flow of Events button to create a new flow of events.

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.

Generating activity diagram from flow of events


To generate activity diagram from flow of events, right click on the background of flow of events editor and select Synchronize to Activity Diagram
from the pop-up menu.

Generate activity diagram from flow of events

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.

Documenting flow of events P. 153


Elaborating use case
A use case can be elaborated by using sequence diagrams and activity diagrams to model its interactions and activity flows respectively.

Elaborating use case by sequence diagrams


A use case can be elaborated by using sequence diagrams as a sub diagram.

Creating a sub diagram


Right click on the target use case and select Sub Diagrams > Sequence Diagram > Create Sequence Diagram from the pop-up menu.

Create a sequence diagram as sub diagram

Drawing sequence diagram


The sequence diagram is created to show how users can interact with the procedure in the use case.

Draw a sequence diagram

Navigating to parent use case


If you want to return to the parent use case, click the parent use case's name on the diagram title bar.

Navigate to parent use case

Elaborating use case by activity diagrams


In addition, a use case can be elaborated by using activity diagrams to fill in the flow of events of a use case and synchronize the events to an activity
diagram.

Synchronizing flow of events to activity diagram


1. Right click on the target use case and select Open Use Case Details... from the pop-up menu.

Open use case details

Elaborating use case P. 154


2. When the details dialog box pops out, select the Flow of Events tab.

Open flow of events editor

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.

Generate activity diagram from flow of events

Navigating to flow of events


If you want to return to the flow of events, right click on a target action in activity diagram and select Related Elements > Open Flow of event from the
popup menu.

Open flow of events from activity diagram

Elaborating use case P. 155


Updating activity diagram from flow of events
If you have made some changes on flow of events, you can synchronize the changes to activity diagram. Right click on the background of flow of
events and select synchronize to the name of activity diagram from the pop-up menu.

Update changes from flow of events to activity diagram

Elaborating use case P. 156


Managing actors with actors grid
Actors Grid is a table with actors listed in it. It lets you to access all actors in a project or diagram, check their related use cases, lookup and create
actors.

Creating the actors grid


Select UML > Actor Grid from the toolbar.

Open Actor Grid

The overview of actors grid

The actors grid

Field Description

Click this button to reveal Name and Model Element. To hide these them, click this button again.

Create a new actor.

To find an actor by providing its name or documentation.

To open the specification of actor selected in grid.

To show the view(s) of actor selected in grid.

To visualize an actor selected in grid.

Add/ remove property column(s) in Term list.

Managing actors with actors grid P. 157


To update the display on the Term list.

To select the scope for showing mdoel elements on Term list.

To filter actors by name. The rubber on the right hand side is for clearing the filter content.

The fields in actors grid

Accessing use case from actor


Click on the name of use case in the Related use cases cell of the actor that we want to access its related use case.

Access use case from actor

Creating actor
1.
Click on above the grid.

Create an actor in 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.

Select an actor to visualize

2.
Click on above the grid.

Click Visualize button

Managing actors with actors grid P. 158


3. If you want to visualize actor in a new diagram, check Create new diagram, select the type of diagram to create and specify the diagram name.

Name a new diagram

If you want to visualize actor in an existing diagram, check Show in existing diagram and select a diagram in the diagram list.

Select an existing use case diagram to visualize the actor

4. Click Create button at the bottom of the dialog box.

Managing actors with actors grid P. 159


Filtering actors
By filtering actors, actors that do not match the required naming convention are filtered. To filter, enter the name of actor, or part of its name at the top
right of grid. You can make use of the asterisk (*) character to represent any character(s).

Filter actor by name

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).

The matched actors are highlighted

Managing actors with actors grid P. 160


Managing use cases with use cases grid
Use Cases Grid is a table with use cases listed in it. It lets you to access all use cases in a project or diagram, check their related actors, lookup and
create use case.

Creating the use case grid


Select UML > Use Case Grid from the toolbar.

Open Use Case Grid

The overview of use cases grid

The use cases grid

Button Name Description

Configure Grid Click this button to reveal Name and Model Element. To hide these them, click this button
again.

Create Use Case Create a new use case.

Find To find a use case by providing its name or documentation.

Open Specification... To open the specification of use case selected in grid.

Open Use Case Detail To open the use case details of use case selected in grid.

Show View... To show the view(s) of use case selected in grid.

Visualize... To visualize a use case selected in grid.

Managing use cases with use cases grid P. 161


Configure columns... Add/ remove property column(s) in Term list.

Refresh To update the display on the Term list.

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.

The fields in use cases grid

Accessing actor from use case


Click on the name of actor in the Primary Actors/Supporting Actors column of the use case that we want to access its related actor.

Access actor from use case

Creating use case


1.
Click on above the grid.

Create a use case

2. Name the use case. You may optionally reset the ID by double-clicking on the ID cell and entering a new one.

Name use case

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.

Browsing use case's details


To browse for the details of a use case, select the use case in grid and click on the button. This opens its use case details.

Visualizing a use case


You can form a diagram with use case, or show it in an existing diagram by visualizing it in use cases grid. To visualize a use case:

Managing use cases with use cases grid P. 162


1. Select the use case to visualize.

Select a use case to visualize

2.
Click on above the grid.

Click Visualize button

Managing use cases with use cases grid P. 163


3. If you want to visualize use case in a new diagram, check Create new diagram, select the type of diagram to create and then specify the
diagram name.

Name a new diagram

If you want to visualize use case in an existing diagram, check Show in existing diagram and select a diagram in the diagram list.

Select an existing use case diagram to visualize the use case

4. Click Create button at the bottom of the dialog box.

Managing use cases with use cases grid P. 164


Filtering use cases
By filtering use cases, use cases that do not match the required naming convention are filtered. To filter, enter the name of use case, or part of its
name at the top right of grid. You can make use of the asterisk (*) character to represent any character(s).

Filter use case by name

Finding use case


To find out use cases that match specific naming or documentation pattern:
1.
Click above the grid.

Find a use case

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

Managing use cases with use cases grid P. 165


Drawing activity diagrams
Activity diagram is a flowchart-based diagram showing flow of control from activity to activity. It shows concurrency, branch, control flow and object
flow. Swimlane, furthermore, is used for partitioning the activity states.

Creating activity diagram


Right click Activity Diagram on Diagram Navigator and select New Activity Diagram from the pop-up menu to create an activity diagram.

Create activity diagram

Creating swimlane
You can click either Horizontal Swimlane or Vertical Swimlane on the diagram toolbar.

Create swimlane

Click on the diagram to create the swimlane.

Swimlane created

Double-click the partition name to rename it.

Rename partition

Drawing activity diagrams P. 166


Inserting partition to swimlane
To insert partition to swimlane, right-click on a partition and select Insert Partition After from the popup menu.

Insert partition to swimlane

A partition is inserted.

Partition inserted

Creating initial node


Click Initial Node on the diagram toolbar.

Create initial node

Click inside the partition to create the initial node there.

Initial node created

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

Drawing activity diagrams P. 167


Similarly you can create a new action using the Control Flow -> Action resource of an action.

Create a new action from an action

A new action is created and is connected to the action with a control flow.

Action created

Continue to complete the activity diagram.

Completed activity diagram

Working with scenario


A scenario is a diagram formed by the internal interaction of a sequence of action, modeled by their sub-diagrams. With scenario, you can produce
a diagram which presents an overview of an execution path in activity diagram, so as to know how user and system communicate with each other in
order to complete the flow.

Producing scenario from activity diagram

Drawing activity diagrams P. 168


1. Right click on the activity diagram that contains the flows that you want to produce a scenario, and select Scenarios > Edit Scenarios... from
the popup menu.

Edit scenarios

2. In the Edit Scenarios dialog box, click Add... button at the bottom left corner.

Add a scenario

Drawing activity diagrams P. 169


3. Select a path for generating scenario. Click OK to confirm.

Select a path for generating 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.

4. Name the scenario. Add description if necessary.

Name and describe scenario

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.

Select diagram for action

Drawing activity diagrams P. 170


6. Click on the arrow beside the Generate button and select the type of diagram of the scenario.

Generate scenario with specific diagram type

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.

Drawing activity diagrams P. 171


Drawing state machine diagrams
State machine diagram shows flow of control from state to state within single object. It usually contains simple states, composite states, composite
states, transitions, events and actions.

Creating state machine diagram


Right click State Machine Diagram on Diagram Navigator and select New State Machine Diagram from the pop-up menu to create a state machine
diagram.

Create state machine diagram

Creating states and transitions


After creating a state machine diagram, an initial pseudo state appears by default. Move the mouse over it and click its resource icon Transition ->
State.

Create state from initial pseudo state

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.

State and transition created

Similarly, you can use the Transition -> Final State resource to create a final state.

Create final state

Drawing state machine diagrams P. 172


Final state does not show caption by default. To show it, right-click on the diagram and select Presentation Options > Show Shape Caption > Final
State.

Show caption of final state

Adding region to state


To model substates of a composite state, you need to add one or more regions to it. To add a region, right-click the state and select Add Horizontal
Region from the popup menu.

Add region to state

Next, you can draw the substates inside the region.

Substates in a composite state

Drawing state machine diagrams P. 173


Modeling properties of transition
To model properties of transition such as effect and guard, right-click the transition and select Open Specification... from the pop-up menu.

Open specification of transition

When the Transition Specification dialog box pops out, you can edit its name, effect and guard. Next, click Edit... button of the Effect property.

Transition Specification dialog box

In Activity Specification (Effect) dialog box, change its name, and then click OK button to apply the change.

Edit effect property of transition

Click OK in the Transition Specification dialog box to close it. The name and effect are shown on the transition caption.

Name and effect shown in caption of transition

Drawing state machine diagrams P. 174


Drawing timing diagrams
Timing diagram shows time, event, space and signal for real-time and distributed system.

Creating timing diagram


Right click Timing Diagram on Diagram Navigator and select New Timing Diagram from the pop-up menu to create a timing diagram.

Create timing diagram

Creating timing frame


To create timing frame, click Timing Frame on the diagram toolbar and then click on the diagram.

Create timing frame

Double click on the top left corner of the frame to rename it.

Rename frame

The name of a timing frame is usually preceded by the sd keyword.

Frame renamed

Adding lifeline to frame


To add lifeline to frame, right-click the frame and select Add Lifeline from the pop-up menu.

Add lifeline

Double-click on the name of the lifeline to rename it.

Drawing timing diagrams P. 175


Adding time unit to frame
To add time unit to frame, right-click the frame and select Add Time Unit from the pop-up menu.

Add time unit

Repeat the step to add as many as time units you need. Double-click on a time unit to rename it.

Rename time unit

Adding state/condition to lifeline


To add state/condition to lifeline, right-click the lifeline and select Add State/Condition from the pop-up menu.

Add state/condition

Double click on the name of the state/condition to rename it.

Dragging time instance


Mouse over the line segment of a time instance, click and drag it.

Drag time instance

Drawing timing diagrams P. 176


Release the mouse button when reached the target state/condition.

Dragged time instance

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.

Move a group of time instances

Release the mouse button when reached the target state/condition. The group of time instances is moved at once.

Moved group of time instances

Adding time messages to frame


To add time messages to frame, right-click the frame and select Edit Frame... from the pop-up menu.

Edit frame

In the Edit Frame dialog box, open the Time Messages tab and click Add... button.

Add time message

Drawing timing diagrams P. 177


When the Add Time Message dialog box pops out, enter name and select the start lifeline, start time, end lifeline and end time for this time message.
Note that as time units may be unnamed, when selecting start/end time you should check the relative position of the time unit in the list.

Select end time of time message

The time message is shown on the frame.

Time message

Drawing timing diagrams P. 178


Switching to compact view mode
To switch to compact view mode, right-click the frame and select View Mode > Compact from the popup menu.

Switch to compact view mode

The frame will be shown in compact mode.

Frame shown in compact mode

Drawing timing diagrams P. 179


Drawing sequence diagrams
A sequence diagram is used primarily to show the interactions between objects that are represented as lifelines in a sequential order.

Creating sequence diagram


Right click Sequence diagram on Diagram Navigator and select New Sequence Diagram from the pop-up menu to create a sequence diagram.

Create sequence diagram

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.

Lifeline and message created

Drawing sequence diagrams P. 180


Auto extending activation
When create message between lifelines/actors, activation will be automatically extended.

Auto extending activation

Using sweeper and magnet to manage sequence diagram


Sweeper helps you to move shapes aside to make room for new shapes or connectors. To use sweeper, click Sweeper on the diagram toolbar (under
the Tools category).

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 towards right

Drawing sequence diagrams P. 181


The picture below shows the message specify visit time is being swept downwards, thus new room is made for new messages.

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.

Drawing sequence diagrams P. 182


The picture below shows when drag the magnet upwards, shapes below dragged position are pulled upwards.

Pull shapes upwards using magnet

Creating combined fragment for messages


To create combined fragment to cover messages, select the messages, right-click on the selection and select Create Combined Fragment, and then
select a combined fragment type (e.g. loop) from the popup menu.

Create combined fragment for messages

Drawing sequence diagrams P. 183


A combined fragment of selected type will be created to cover the messages.

Combined fragment created

Developing sequence diagram with quick editor or keyboard shortcuts


In sequence diagram, an editor appears at the bottom of diagram by default, which enables you to construct sequence diagram with the buttons there.
The shortcut keys assigned to the buttons provide a way to construct diagram through keyboard. Besides constructing diagram, you can also access
diagram elements listing in the editor.

The quick editor

Editing lifelines
There are two panes, Lifelines and Messages. The Lifelines pane enables you to create different kinds of actors and lifelines.

Lifelines pane in quick editor

Button Shortcut Description

Alt-Shift- To create an actor


A

Alt-Shift-L To create a general lifeline

Drawing sequence diagrams P. 184


Alt-Shift- To create an <<entity>> lifeline
E

Alt-Shift- To create a <<control>> lifeline


C

Alt-Shift- To create a <<boundary>> lifeline


B

Alt-Shift- To open the specification of the element chosen in quick editor


O

Ctrl-Del To delete the element chosen in quick editor

Ctrl-L To link with the diagram, which cause the diagram element to be selected when selecting an element in editor, and vice versa

Buttons in Lifelines pane

Editing messages
The Messages pane enables you to connect lifelines with various kinds of messages.

Messages pane in quick editor

Button Shortcut Description

Alt-Shift-M To create a message that connects actors/lifelines in diagram

Alt-Shift-D To create a duration message that connects actors/lifelines in diagram

Alt-Shift-C To create a create message that connects actors/lifelines in diagram

Alt-Shift-S To create a self message on an actor/lifeline in diagram

Alt-Shift-R To create a recursive message on an actor/lifeline in diagram

Alt-Shift-F To create a found message that connects to an actor/lifeline

Alt-Shift-L To create a lost message from an actor/lifeline

Alt-Shift-E To create a reentrant message that connects actors/lifelines in diagram

Ctrl-Shift-Up To swap the chosen message with the one above

Ctrl-Shift- To swap the chosen message with the one below


Down

Ctrl-R To revert the direction of chosen message

Alt-Shift-O To open the specification of the message chosen in quick editor

Ctrl-Del To delete the message chosen in quick editor

Drawing sequence diagrams P. 185


Ctrl-L To link with the diagram, which cause the message to be selected when selecting a message in editor, and vice versa

Buttons in Messages pane

Expanding and collapsing the editor


To hide the editor, click on the down arrow button that appears at the bar on top of the quick editor. To expand, click on the up arrow button.

Collapse the quick editor

Setting different ways of numbering sequence messages


You are able to set the way of numbering sequence messages either on diagram base or frame base.

Diagram-based sequence message


Right click on the diagram's background, select Sequence Number and then either Single Level or Nested Level from the pop-up menu.

Diagram-based pop-up menu

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

Drawing sequence diagrams P. 186


Frame-based sequence message
Right click on the diagram's background, select Sequence Number and then either Frame-based Single Level or Frame-based Nested Level from
the pop-up menu.

Frame-based pop-up menu

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.

Frame-based nested level

Drawing sequence diagrams P. 187


Drawing communication diagrams
Communication diagram is designed for illustrating the dynamic view of the system. It emphasizes the structural organization of the objects' send and
receive messages.

Creating communication diagram


Right click Communication Diagram on Diagram Navigator and select New Communication Diagram from the pop-up menu to create a
communication diagram.

Create communication diagram

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).

Lifeline, link and message created

Creating message on link


To create message on link, click its Create Message resource.

Create message on link

Drawing communication diagrams P. 188


A message will be created on the link.

Message created on link

Editing sequence number of messages


To edit sequence number of messages, for example, to show certain messages are in nested level of interaction, right-click the diagram and select
Reorder Messages ... from the pop-up menu.

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.

Edit sequence number of messages

Drawing communication diagrams P. 189


The sequence number of messages is updated.

Sequence number of messages updated

Drawing communication diagrams P. 190


Drawing interaction overview diagrams
Interaction overview diagram is the variant of activity diagram. Interaction overview diagrams overview control flow. The main element, frame shows
any type of interaction diagram.

Creating interaction overview diagram


Right click Interaction Overview Diagram on Diagram Navigator and select New Interaction Overview Diagram from the pop-up menu to create an
interaction overview diagram.

Create interaction overview diagram

Creating initial node


To create initial node, click Initial Node on the diagram toolbar and then click on the diagram.

Create initial node

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.

Show caption of initial node

Creating decision node


To create a decision node from an initial node, move the mouse over the initial node and press its resource icon Generic Resource.

Generic resource

Drawing interaction overview diagrams P. 191


Drag it to your preferred place and then release the mouse button. Select Control Flow -> Decision Node from the pop-up menu.

Create decision node

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.

Creating interaction use


To create an interaction use, move the mouse over a shape and press its resource icon Control Flow -> Interaction Use.

Create interaction use

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.

Interaction use and control flow created

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.

Make interaction use refers to diagram

When sequence diagram is created, rename the diagram.

Rename
sequence diagram

Drawing interaction overview diagrams P. 192


When you return to the interaction overview diagram, you can see the interaction use caption shows the diagram it refers to.

Interaction use caption updated

Creating fork node


To create a fork node, move the moue over a shape and press its resource icon Control Flow -> Fork Node.

Create fork node

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.

Change orientation of fork node

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.

Drawing interaction overview diagrams P. 193


A new sequence diagram is created and associated with an interaction by default. To open it, right click on the interaction and select Associated
Diagram > (target diagram name).

Open associated diagram of interaction

Draw the sequence diagram.

Sequence diagram

When you return to the interaction overview diagram, you can see the interaction shows the thumbnail of the sequence diagram.

Updated diagram thumbnail in interaction

Creating join node


To create a join node, move the mouse over a shape and press its resource icon Control Flow -> Join Node.

Create join node

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.

Creating activity final node


To create an activity final node, move the mouse over a shape and press its resource icon Control Flow -> Activity Final Node.

Create activity final node

Drawing interaction overview diagrams P. 194


Drag it to your preferred place and then release the mouse button. An activity final node is created and connected to the shape you selected with a
control flow.

Activity final node and control flow created

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

Drawing interaction overview diagrams P. 195


Drawing class diagrams
A class diagram shows the objects that are required and the relationships between them. Since it provides detailed information about the properties
and interfaces of the classes, it can be considered as the main model and regard the other diagrams as supplementary models.

Creating class diagram


Right click Class Diagram on Diagram Navigator and select New Class Diagram from the pop-up menu to create a class diagram.

Create class diagram

Creating class
To create class, click Class on the diagram toolbar and then click on the diagram.

Create class

A class will be created.

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

Drawing class diagrams P. 196


To create aggregation, use the Aggregation -> Class resource instead.

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

Drawing class diagrams P. 197


The direction arrow is shown beside the association.

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

Creating attribute with enter key


After creating an attribute, press the Enter key, another attribute will be created. This method lets you create multiple attributes quickly and easily.

Create attribute with Enter key

Drawing class diagrams P. 198


Creating operation
To create operation, right click the class and select Add > Operation from the pop-up menu.

Create operation

An operation is created.

Operation created

Similar to creating attribute, you can press the Enter key to create multiple operations continuously.

Drag-and-Drop reordering, copying and moving of class members


To reorder a class member, select it and drag within the compartment, you will see a thick black line appears indicating where the class member will be
placed.

Reorder class member

Release the mouse button, the class member will be reordered.

Class member reordered

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.

Copy class member

Release the mouse button, the class member will be copied.

Class member copied

Drawing class diagrams P. 199


To move a class member, select it and drag to the target class, you will see a thick black line appears indicating where the class member will be
placed. Unlike copy, do not press the Ctrl key when drag, the mouse cursor without the plus sign indicates this is a move action.

Move class member

Release the mouse button, the class member will be moved.

Class member moved

Model name completion for class


The model name completion feature enables quick creation of multiple views for the same class model. When create or rename class, the list of
classes is shown.

Model name completion

Type text to filter classes in the list.

List filtered by typed text

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.

Multiple views of the same model

Drawing class diagrams P. 200


Continue to complete the diagram.

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.

Create a generalization set

Drawing class diagrams P. 201


Name the set in the Manage Generalization Sets dialog box, and confirm by pressing OK.

Name the generalization set

The selected generalizations are grouped. Adjust the connector to make the diagram tidy.

Adjust connector

Repeat the steps for other generalizations.

Generalization sets defined

Drawing class diagrams P. 202


Defining delegate method for class
When project's programming language is set to be Visual Basic or C#, it is possible to define delegate method for classes. To define delete method,
right click on the class and select Stereotypes > Delegate from the pop-up menu.

Stereotype class as Delegate

Hiding (and showing) attributes and operations


Per workspace
This applies to new classes that will be created in a project opened in specific workspace. To change the setting:
1. Select Tools > Options from the main menu to open the Options dialog box.
2. Click Diagramming on the list.
3. Open the Class tab.
4. Click Presentation tab.
5. Change the settings for Show attribute option and/or Show operation option.

Show or hide operations

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.

Drawing class diagrams P. 203


3. Select Hide All / Show All / Show Public Only.

Change the operations' presentation options for classes in diagram

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.

Change the operations' presentation options for a class

For specific attribute/operation


Instead of showing or hiding all members or public members, you may show/hide specific class member per class. To do this:
1. Right click on the class to set the option.

Drawing class diagrams P. 204


2. Select Presentation Options > Attributes / Operations > Customized... from the pop-up menu.

Show or hide specific class member

3. Select Customized under the drop down menu of Show.

Select Customized in dialog box

Drawing class diagrams P. 205


4. Select the member(s) to hide and click > to hide them.

Select attributes to hide

5. Click OK button to confirm.

Setting initial (default) value for attribute


Initial value can be set to an attribute, indicating the default value of the attribute when the owning object is instantiated. You can give a text value for
initial value, or select an attribute of another class. To set initial value to an attribute:
1. Open the specification dialog box of attribute by right clicking on the attribute and selecting Open Specification... from the popup menu.

Opening the attribute specification

Drawing class diagrams P. 206


2. In the General page of the specification dialog box, enter the initial value in initial value field if it is a text value, or popup the drop down menu to
select a public and static field of any class to be the value.

Selecting an initial value

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.

Drawing class diagrams P. 207


Drawing object diagrams
Object diagram shows a snapshot of instances of things in class diagram. Similar to class diagram, it shows the static design of system from the real or
prototypical perspective.

Creating object diagram


Right click Object Diagram on Diagram Navigator and select New Object Diagram from the pop-up menu to create an object diagram.

Create object diagram

Creating instance specification


To create instance specification, click Instance Specification on the diagram toolbar and then click on the diagram.

Create instance specification

An instance specification will be created.

Instance specification 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

Drawing object diagrams P. 208


When the Instance Specification Specification dialog box pops out, the Classifiers tab is opened by default. Select the classifier on the left and click
Add Selected button to add it.

Add selected classifiers

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

Drawing object diagrams P. 209


The Instance Specification Specification dialog box appears with the Slots tab selected. Select the features that you want to define slots on the left
and click Define Slot.

Select features to define slots

Select a slot in Defined slots and click Edit Values... button.

Edit values of slot

Drawing object diagrams P. 210


The Slot Specification dialog box pops out, the Values tab is opened by default. Click Add button and select Text from the pop-up menu.

Add text value

Enter the value when prompted. Close the specification dialog boxes to apply the changes, defined slots will be shown in the instance specification.

Defined slots shown

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

Drawing object diagrams P. 211


Continue to complete the diagram.

Completed diagram

Drawing object diagrams P. 212


Drawing package diagrams
Package diagram shows the arrangement and organization of model elements in middle to large scale project. It can show both structure and
dependencies between sub-systems or modules.

Creating package diagram


Right click Package Diagram on Diagram Navigator and select New Package Diagram from the pop-up menu to create a package diagram.

Create package diagram

Creating package
To create package, click Package on the diagram toolbar and then click on the diagram.

Create package

A package will be created.

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.

Drawing package diagrams P. 213


If the stereotype you want to use is not on the list, click Edit Stereotypes... button.

Edit stereotypes

Click Add... button in the Configure Stereotypes dialog box.

Add stereotype

Drawing package diagrams P. 214


Enter name for the new stereotype (e.g. facade). Click OK button in Stereotype Specification dialog box and the Configure Stereotypes dialog box.
You will see the added stereotype appears on the list in Package Specification dialog box. Select it and click Add Selected button. Next, click OK
button to proceed.

Add selected stereotypes

Close the specification dialog box. Stereotypes will be applied to the package.

Stereotypes assigned

Continue to complete the diagram.

Completed diagram

Drawing package diagrams P. 215


Drawing composite structure diagrams
Composite structure diagram visualizes the internal structure of a class or collaboration. It is a kind of component diagram mainly used in modeling a
system at micro point-of-view.

Creating composite structure diagram


Right click Composite Structure Diagram on Diagram Navigator and select New Composite Structure Diagram from the pop-up menu to create a
composite structure diagram.

Create composite structure diagram

Creating class
To create class, click Class on the diagram toolbar and then click on the diagram.

Create class

A class will be created.

Class created

Creating part
To create part, move the mouse over the target class, press its resource icon New Part.

Create part

A part will be created.

Part created

Creating port
To create port, move the mouse over the target class, press its resource icon New Port.

Create port

Drawing composite structure diagrams P. 216


A port will be created.

Port created

Specifying type of port


Right-click the port and select Open Specification... from the pop-up menu. The Port Specification dialog box appears.
Click the combo box of Type and select a class.

Select type

Click OK button to apply the changes. Type will be shown on the caption of the port.

Type shown on 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

Drawing composite structure diagrams P. 217


Continue to complete the diagram.

Completed diagram

Drawing composite structure diagrams P. 218


Drawing component diagrams
Component diagram shows the physical aspect of an object-oriented software system. It illustrates the architectures of the software components and
dependencies between them.

Creating component diagram


Right click Component Diagram on Diagram Navigator and select New Component Diagram from the pop-up menu to create a component
diagram.

Create component diagram

Creating component
To create component, click Component on the diagram toolbar and then click on the diagram.

Create component

A component will be created.

Component created

Assigning stereotypes
Right click on the package and select Stereotypes > Stereotypes... from the pop-up menu.

Assigning stereotypes

Drawing component diagrams P. 219


When the Component Specification dialog box pops out, the Stereotypes tab is opened by default. The list on the left shows the selectable
stereotypes.
If the stereotype you want to use is not on the list, click Edit Stereotypes... button.

Edit stereotypes

Click Add... button in the Configure Stereotypes dialog box.

Add stereotype

Drawing component diagrams P. 220


Name the stereotype (e.g. application) in the Stereotype Specification dialog box and then click OK button to close it. Click OK button in the
Configure Stereotypes dialog box. The added stereotype will then be shown on the list in the Component Specification dialog box. Select it and
click Add Selected button. Finally, click OK button to confirm.

Add selected stereotypes

Close the specification dialog box. Stereotypes will be applied to the package.

Stereotypes assigned

Creating provided interface


To create provided interface for a component, move the mouse over the target component and press its resource icon Realization -> Interface.

Create provided interface

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.

Provided interface created

Creating required interface


To create required interface for a component, move the mouse over the target component and press its resource icon Usage-> Interface.

Create required interface

Drawing component diagrams P. 221


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.

Required interface created

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

Continue to complete the diagram

Completed diagram

Drawing component diagrams P. 222


Drawing deployment diagrams
Deployment diagram shows the physical aspects of an object-oriented system. It also shows the configuration of run time processing nodes and
artifacts.

Creating deployment diagram


Right click Deployment Diagram on Diagram Navigator and select New Deployment Diagram from the pop-up menu to create a deployment
diagram.

Create deployment diagram

Creating node model element


To create node model element, right click on the background of Model Explorer and select Model Element > New Model Element from the pop-up
menu.

Create model element

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

Drawing deployment diagrams P. 223


A node model element will be created.

Node created

Creating instance of node


To create instance of node, click Instance Specification on the diagram toolbar and then click on the diagram.

Create instance specification

An instance specification will be created.

Instance specification 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

Drawing deployment diagrams P. 224


When the Instance Specification Specification dialog box pops out, the Classifiers tab is opened by default. Select the classifier(s) on the left and
click Add Selected button to add them.

Add selected classifiers

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

Creating instance of component


Similar to creating instance of node, you first create a component model element, and then create an instance specification, but this time assigns a
component to the instance specification as classifier. After that the instance specification will be displayed as a component.

Instance of component

Drawing deployment diagrams P. 225


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

Continue to complete the diagram.

Completed diagram

Drawing deployment diagrams P. 226


Modeling and documenting test cases
Produce test case from requirement
1. In a requirement diagram, move the mouse cursor over the requirement that we want to produce Test Case.

Moving mouse cursor over requirement

2. Press on the Verify <- Test Case resource of requirement and drag.

Create test case through the resource centric interface

3. Release the mouse button to create a test case. Name it.

Test case is created

Creating test case and link to requirement


1. In a requirement diagram, click the Test Case button on the diagram toolbar and then click on the diagram.

Create Test Case

2. Press on the Verify -> Requirement resource of test case and drag.

Linking Requirement with Test Case

Modeling and documenting test cases P. 227


3. 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.

Verify relationship created

Documenting test case


1. Right click on a test case and select Open Specification... from the popup.

Open specification of test case

2. In the Test Plans tab, fill in the Steps, Procedures and Expected Results.

Test Plan filled

Modeling and documenting test cases P. 228


Drawing requirement diagrams
Creating requirement diagram
To create requirement diagram, right click Requirement Diagram on Diagram Navigator and select New Requirement Diagram from the pop-up
menu.

Create new requirement diagram

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

Creating requirement diagram P. 229


Move the mouse over empty space of the diagram and then release the mouse button, a Requirement together with a Containment relationship will be
created.

Requirement and Containment created

Inline editing requirement properties


To inline edit the property of a Requirement (e.g. ID), double-click on the property, enter new value and press Enter to confirm.

Inline editing Requirement properties

Edit requirement properties with specification dialog box


You can also open specification dialog box of a Requirement to edit its properties. Click Open Specification resource of the Requirement.

Open specification of Requirement

Creating requirement diagram P. 230


The Requirement Specification dialog box shows. Edit the properties and click OK button to apply the changes.

Requirement Specification

Creating test case and link to requirement


To create a Test Case, click the Test Case button on the diagram toolbar and then click on the diagram.

Create test case

Click Verify -> Requirement resource of Test Case and drag.

Linking Requirement with Test Case

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.

Verify relationship created

Creating requirement diagram P. 231


Defining your own set of requirement types
Users can record and present requirements as boxes visually through requirement modeling. The name of requirements summarizes the requirement
while a set of attributes defines the requirement. The default requirement box allows users to specify general attributes, such as ID, source, kind, verify
method, risk and status. Moreover, you are allowed to customize your own requirement types that contain attributes related to your domain.

Creating new requirement type


Before creating new Requirement type, create a new requirement diagram or open your target requirement diagram where you want to customize your
our own requirement types. Select Tools > Configure Requirements... from the main menu.

Configure Requirements

The Configure Requirements dialog box appears. Click Add to add a new requirement type.

Configure Requirements dialog box

Enter name of the Requirement type in Name field.

Enter name for Requirement type

Customizing requirement types P. 232


Add attributes for the requirement type to make it meaningful. Click Add button below the attribute table and select an attribute.

Add documentation attribute

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.

Customize color for 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.

Customizing requirement types P. 233


Once you finish configuring requirement types, click OK button to return to your target requirement diagram.

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.

The customized requirement type

Customizing requirement types P. 234


Managing requirements with requirements grid
Requirements Grid is a table with requirements listed in it. It enables you to access all requirements in a project or diagram, lookup requirements by
criteria and create requirements.

Creating the requirements grid


Select Requirement > Requirement Grid from the toolbar.

Open Requirement Grid

The overview of requirements grid

The requirements grid

Field Description

Click this button to reveal Name and Model Element. To hide these them, click this button again.

Create a new requirement.

To find a requirement by providing its name or documentation.

Requirements grid P. 235


To open the specification of requirement selected in grid.

To show the view(s) of requirement selected in grid.

To visualize a requirement selected in grid.

To filter requirements by selecting the diagram(s) (or all diagrams) that contain the requirements.

Add/ remove property column(s) in Term list.

To update the display on the Term list.

To filter requirements by name. The rubber on the right hand side is for clearing the filter content.

The fields in requirements grid

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.

Select a requirement to visualize

2.
Click on above the grid.

Create visualize

Requirements grid P. 236


3. If you want to visualize requirement in a new diagram, keep Create new diagram selected, select the type of diagram to create and specifying
the diagram name.

Name a new diagram

If you want to visualize requirement in an existing diagram, select Show in existing diagram and select a diagram in the diagram list.

Select an existing requirement diagram to visualize the requirement

4. Click Create button at the bottom of the dialog box.

Requirements grid P. 237


Filtering requirements
By filtering requirements, requirements that do not match the required naming convention are filtered. To filter, enter the name of requirement, or part
of its name at the top right of grid. You can make use of the asterisk (*) character to represent any character(s).

Filter requirement by name

Finding requirement
To find out requirements that match specific naming or documentation pattern:
1.
Click above the grid.

Find a requirement

2. In the Search Text text box, enter the text to search.

Enter requirement name and check Name

3. Click Find. As a result, the matched requirement(s) will be highlighted in grid.

Finding result

Requirements grid P. 238


Recording requirements
Before you start business process modeling, you usually need to talk to the customers or meet them to know what they need, and to familiarize
yourself with their company's operations as well as their problems. During the meeting you can collect useful information from customer, which include
the conversation log, documents. You can make use of textual analysis, a text-based editor, to help record those textual information. In addition to a
plain text editor, you can identify important terms or objects (e.g. class, use case) from the problem description.

Creating textual analysis


To create textual analysis, right click Textual Analysis on Diagram Navigator and select New Textual Analysis from the pop-up menu.

Create a textual analysis

Entering problem statement


Three ways of entering problem statement are provided in VP-UML.
• Typing on the editor
• Importing an external text file
• Copying and pasting from an external source
To type in the editor, type the problem statement directly on the editor.
To import a text file, click Import Text File on the toolbar.

Import text file

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.

Recording requirements P. 239


To copy and paste from an external source, press Ctrl + C on the selected text and press Ctrl + V for pasting it on the editor.

Completed problem statement

Recording requirements P. 240


Identifying important terms
In textual analysis, you identify important terms by adding them to glossary, and clarify them by defining aliases and entering documentation.
1. Highlight the specific term on the left hand side editor, right click on it and select Add [the highlighted term] to Glossary from the pop-up
menu.

Add "OTV" to Glossary

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.

Right click to open term editor

3. In the Term Editor page, open Definition tab.


4. You can define aliases for the term and enter documentation as definition for the term. To insert an alias, click Add button to type the alias in the
pop-up Input dialog box. To enter the definition of the term, enter under Definition directly.

Define aliases and enter definition

Identifying important terms P. 241


5. As a result, the columns of Aliases and Documentation are filled when you return Glossary Grid page.

Completed glossary grid

NOTE: If the Aliases column is hidden, you can click Configure Columns... button. Open Properties tab and select it under Details folder.

Identifying important terms P. 242


Identifying candidate objects
By studying the problem statement, you can extract words or phrases that are relevant to the system and convert them into model elements, such as
classes, use cases (system goals) and action, etc. Those objects are regarded as candidate objects. You can extract word or phrases from problem
statement to become specific type of candidate objects, and list them next to the editor, at the right hand side.
To create a candidate object, highlight a word/ phrase on the editor, drag it on the right-hand side text field and release the mouse until after it has
reached the right-hand side text field.

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.

Candidate object name is highlighted

The candidate object is set as class type by default.


To change the candidate object type, right click on the candidate object and select the preferred model element type from the pop-up menu.

Change candidate object type

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.

Create a candidate object with preferred type

As a result, a candidate object with your selected type of model element will be shown on the right-hand side.

Identifying candidate objects P. 243


Writing description for candidate objects
The table on the bottom right of the textual analysis editor allows you to view and edit details of candidate objects. You can edit description of a
candidate object by double clicking on the Class Description cell. Moreover, you may resize its cell to create more spaces by dragging on its bottom
line.

Edit in class description cell

Identifying candidate objects P. 244


Forming diagram from candidate objects
You can form a diagram from candidate objects, or show it in an existing diagram by visualizing it. First, you need to create model element from a
candidate object. To create model element for candidate object, right click on a candidate object and select Create Model Element (the specific type of
model element) from the pop-up menu.

Create a model element

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.

Check an option in Visualize Model Element dialog box

As a result, the model element will be shown on the selected diagram.

Forming diagram from candidate objects P. 245


NOTE: If you have already made a model element for the candidate object, the Create Model Element option will be hidden even after you right
click on it.

Forming diagram from candidate objects P. 246


Drawing CRC card diagram
Class-Responsibility Collaborator (CRC) card visualize classes in card-like presentation. Each CRC card contains information like the description of
class, its attributes and responsibility. A CRC card diagram is a holder of these cards.

Creating CRC card diagram


To create a CRC Card diagram, right click on CRC Card Diagram in Diagram Navigator and select New CRC Card Diagram from the pop-up menu.

Create CRC card diagram

Creating CRC card


Click CRC Card on the diagram toolbar and then click on the diagram to create a CRC card. You can create as many as CRC card on a diagram by
repeating this step.

Create CRC card

Editing CRC card properties


All properties in a CRC card must be edited inline. To edit, double click on the desired field, update its value, and click on the diagram background to
confirm editing.

Edit description

Drawing CRC card diagram P. 247


Adding attributes
Right-click on the Attributes heading and select Add > Attribute from the pop-up menu.

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

Drawing CRC card diagram P. 248


Creating user interface diagram
You can design the graphical user interface of your application or system by using user interface diagram. The diagram toolbar of User Interface
provides you with common GUI components like frame, text fields, labels, buttons, etc. You can select appropriate components and drag them to
diagram to construct the GUI. You can also change the appearance of user interface by modifying GUI components' properties.
To create a user interface diagram:
1. Right click on User Interface and select New User Interface from the pop-up menu on Diagram Navigator.

Create a User Interface diagram through Diagram Navigator

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

2. Name your screen design by filling in the diagram name.

Enter the diagram name

3. Press Enter to confirm the diagram name. As a result, the name for User Interface diagram is created.

A User Interface diagram is created

Creating user interface diagram P. 249


Frame
A Frame is a top-level window with a title and a border. The size of the frame includes any area designated for the border. User can add components
on a frame.

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.

Drag diagonally to expand the frame

3. Release the mouse button to confirm the size of frame.


4. Enter the frame title and press Enter to confirm.

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.

Description of frame properties

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.

Select Label from


diagram toolbar

2. Click on a container (e.g. a Frame) or diagram background to create a label.


3. Enter the label caption and press Enter to confirm the caption of label.

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

Caption Caption is the text appear in a label.

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.

Description of label properties

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.

Creating a text field


1. Select the Text Field tool from the diagram toolbar.

Selecting Text Field


from diagram toolbar

2. Press to set the position of the text field. Drag diagonally from the starting point to expand the text field.

Drag diagonally to expand the text field

3. Release the mouse button to confirm the size of text field.


4. Enter the text field text and press Enter to confirm the title of text field.

A text field is created

Text field properties


The appearance of text field can be changed by editing its properties. To configure a text field, right click on the text field and select Open
Specification... from the popup menu. The UI tab is where user can configure a text field.

Property Description

Text Text refers to the text that appears in the text field.

Description of text field properties

Text field P. 252


Scrollbar
A scrollbar is a bar with a knob which appears at the bottom or right of a container, such as a frame. The user positions the knob in the scrollbar
to determine the contents of the viewing area. The program typically adjusts the display so that the end of the scrollbar represents the end of the
displayable contents, or 100% of the contents. The start of the scrollbar is the beginning of the displayable contents, or 0%. The position of the knob
within those bounds then translates to the corresponding percentage of the displayable contents.

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.

Select Horizontal Scrollbar


from diagram toolbar

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

Change orientation with resource-Centric interface


A scrollbar can be oriented horizontally or vertically, which determines the contents of the viewing area when being scrolled. User can change the
orientation of a scrollbar easily through the resource-centric interface. When a scrollbar is put inside a container, changing orientation will automatically
dock to the bottom or the right of container. To change scrollbar orientation:
1. Move the mouse over the scrollbar.
2. Click on the resource icon Switch Orientation.

Click on the resource icon for switching Scrollbar Orientation

3. The orientation of scrollbar will then be switched.

Scrollbar Orientation switched from horizontal to vertical

Automatic sticking scrollbar to frame


In a normal User Interface design, scrollbars, no matter horizontal or vertical, are placed at the bottom or on the right of a container component. VP-
UML follows this practice. When creating a scrollbar in a container component, or when moving a scrollbar into a container component, the scrollbar
will be docked to the border of component automatically.

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

Orientation It indicates if the scroll bar is vertical or horizontal.

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.

Minimum The minimum value of scrollbar.

Maximum The maximum value of scrollbar.

Value Value which controls the location of the scroll bar knob.

Description of scrollbar properties

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.

Creating a combo box


1. Select the Combo Box tool from the diagram toolbar.

Selecting Combo Box


from diagram toolbar

2. Click to set the position of the combo box. Drag diagonally from the starting point to expand the combo box.

Drag diagonally to expand the Combo box

3. Release the mouse button to confirm the size of combo box.

Combo box is created

Editing combo box values


1. Right click on the combo box and select Open Specification... from the popup menu.
2. In the UI tab of the UIComboBox Specification dialog box, click Add.
3. Enter the value for of item in Input dialog box and click OK to confirm.
4. Repeat step 2 and 3 to create all the combo box items.

Combo box items are created

5. Click OK to confirm editing.

Combo box P. 255


Combo box properties
The appearance of combo box can be changed by editing its properties. To configure a combo box, right click on the combo box and select Open
Specification... from the popup menu. The UI tab is where user can configure a combo box.

Property Description

Items The items that can be selected by users.

Selected The default selected item.


item

Description of combo box properties

Combo box P. 256


List
List is a component that list out all available selection in rows, and allow the selection of values in it.

Creating a list
1. Select the List tool from the diagram toolbar.

Selecting List from


diagram toolbar

2. Press to set the position of the list. Drag diagonally from the starting point to expand the list.

Drag diagonally to expand the List

3. Release the mouse button to confirm the size of list.

List is created

Editing list values


1. Right click on the list and select Open Specification... from the popup menu.
2. In the UI tab of the List specification dialog box, click Add.
3. Enter the value for of item in Input dialog box and click OK to confirm.

List P. 257
4. Repeat step 2 and 3 to create all the list items.

List items are created

5. Click OK to confirm editing.

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

Values The items that can be selected by user.

Selected value The default selected item in the list.

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.

Description of list properties

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.

Select Table from


diagram toolbar

2. Press to set the position of the table. Drag diagonally from the starting point to expand the table.

Drag diagonally to expand the Table

3. Release the mouse button to confirm the size of table.

Table is created

Editing table contents


Basic setup
To insert columns and rows into a table:
1. Right click on the table and select Open Specification... from the popup menu.

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.

Insert a column into table

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.

Insert a row into table

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.

Table with data

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.

To remove a column in table

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.

To remove a row in table

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.

Moving a row in table upwards

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

Row The height of rows in table.


height

Determines when a horizontal scrollbar will appear in a table.

Determines when a vertical scrollbar will appear in a table.

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.

Determines the color of grid in table.

Determines the visibility of horizontal lines in table.

Determines the visibility of vertical lines in table.

Description of table properties

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.

Selecting Tree from


diagram toolbar

2. Press to set the position of the tree. Drag diagonally from the starting point to expand the tree.

Drag diagonally to expand the Tree

3. Release the mouse button to confirm the size of tree.

Tree is created

Editing tree contents


Basic setup
To insert columns and rows into a tree:
1. Right click on the tree and select Open Specification... from the popup menu.

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.

Insert a node into tree

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.

Insert a 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.

To remove a node in tree

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.

Moving a node in tree upwards

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

Root visible Determines whether the root of tree will appear.

Show root handles Determines whether the expand/collapse button for root will appear.

Row height The height of nodes in tree.

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.

Description of tree properties

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.

Selecting Web Label


from 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.

UIWebLabel Specification's UI tab

Property Description

Text Text is the text appear in a label.

For Specifies which form element a label is bound to.

Description of web label properties

Web Label P. 269


Web Button Input
A web button is a component on a web form which triggers certain action when being clicked. The button "Validate" that appear on a registration form is
an example of web button.

Creating a web button


1. Select the Web Button Input tool from the diagram toolbar.

Selecting Web Button


Input from diagram toolbar

2. Click on a container (e.g. a web panel) or diagram background to create a button.


3. Enter the button caption and press Enter to confirm the caption of button. This creates the button.

A button is created

Web button input properties


The appearance of web button can be changed by editing its properties. To configure a button, right click on the button and select Open
Specification... from the popup menu. The UI tab is where user can configure a button.

UIWebButtonInput Specification's UI tab

Property Description

ID ID is the ID of web button.

Value Value is the text appear on a web button input.

Description of web button properties

Web Button Input P. 270


Web Text Input
Web Text Input is a component that allows the editing of a single line of text. Editable text fields in a registration form are typical examples of text
inputs.

Creating a web text input


1. Select the Web Text Input tool from the diagram toolbar.

Selecting Web Text Input


from diagram toolbar

2. Press to set the position of the text input. Drag diagonally from the starting point to expand the text input.

Drag diagonally to expand the text input

3. Release the mouse button to confirm the size of text input.


4. Enter the text input text and press Enter to confirm the title of text input.

A text input is created

Text input properties


The appearance of text input can be changed by editing its properties. To configure a text input, right click on the text input and select Open
Specification... from the popup menu. The UI tab is where user can configure a text input.

UIWeb TextInput Specification's UI tab

Property Description

ID ID refers to the ID of text input on a form.

Value Value refers to the text that appears in the text input.

Description of web text input properties

Web Text Input P. 271


Web Combo Box
Web Combo box is a component that combines a button and a drop-down list. User can select a value from the drop-down list to make a decision.

Creating a web combo box


1. Select the Web Combo Box tool from the diagram toolbar.

Selecting Web Combo


Box from diagram toolbar

2. Press to set the position of the combo box. Drag diagonally from the starting point to expand the combo box.

Drag diagonally to expand the Combo box

3. Release the mouse button to confirm the size of combo box.

Combo box is created

Editing combo box values


1. Right click on the combo box and select Open Specification... from the popup menu.
2. In the UI tab of the UIWebComboBox Specification dialog box, click Add.
3. Enter the value for of item and click OK to confirm.
4. Repeat step 2 and 3 to create all the combo box items.

Combo box items are created

5. Click OK to confirm editing.

Web Combo Box P. 272


Combo box properties
The appearance of web combo box can be changed by editing its properties. To configure a combo box, right click on the combo box and select Open
Specification... from the popup menu. The UI tab is where user can configure a combo box.

UIWebComboBox Specification's UI tab

Property Description

ID ID of the combo box in web form.

Options The items that can be selected by users. You can optionally mark the default item's Selected to be
true.

Description of web combo box properties

Web Combo Box P. 273


Web List
Web list is a component that lists out all available selection in rows, and allows the selection of values in it.

Creating a list
1. Select the Web List tool from the diagram toolbar.

Selecting Web List


from diagram toolbar

2. Press to set the position of the list. Drag diagonally from the starting point to expand the list.

Drag diagonally to expand the List

3. Release the mouse button to confirm the size of list.

List is created

Editing list values


1. Right click on the list and select Open Specification... from the popup menu.
2. In the UI tab of the UIWebList Specification dialog box, click Add.
3. Enter the value for of item in Input dialog boxand click OK to confirm.
4. Repeat step 2 and 3 to create all the list items.

Web List P. 274


5. Click OK to confirm editing.

List with values

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.

UIWebList Specification's UI tab

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.

Description of web list properties

Web List P. 275


Web Password Input
Web Password Input is a component that allows the entering of password. Text entered will be shown as dots, which act as a mask of password.

Creating a web password input


1. Select the Web Password Input tool from the diagram toolbar.

Selecting Web Password


Input from diagram toolbar

2. Press to set the position of the password input. Drag diagonally from the starting point to expand the password input.

Drag diagonally 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.

A password input is created

Password input properties


The appearance of password input can be changed by editing its properties. To configure a password input, right click on the password input and
select Open Specification... from the popup menu. The UI tab is where user can configure a password input.

UIWebPasswordInput Specification's UI tab

Property Description

ID ID refers to the ID of password input on a web form.

Web Password Input P. 276


Value Value refers to the underlying password of the password input.

Description of web password properties

Web Password Input P. 277


Web File Input
Web File Input is a component that involve a text field which represent file field, and a Browse button for locating the file to select.

Creating a web file input


1. Select the Web File Input tool from the diagram toolbar.

Selecting Web File Input


from diagram toolbar

2. Press to set the position of the file input. Drag diagonally from the starting point to expand the file input.

Drag diagonally to expand the file input

3. Release the mouse button to confirm the size of file input and press Enter to confirm creation.

A file input is created

Web File Input P. 278


File input properties
The appearance if web file input can be changed by editing its properties. To configure a file input, right click on the file input and select Open
Specification... from the popup menu. The UI tab is where user can configure a file input.

UIWebFileInput Specification's UI tab

Property Description

ID ID refers to the ID of file input on a web form.

Description of web file input properties

Web File Input P. 279


Annotating the UI design with callout shape
Annotation is extra information, such as comments, notes, explanation, or other type of external mark that describes a model. It is an effective way to
edit and review work in a work group environment. Designers often need to be able to jot down information which should not be part of the model itself.
In this situation, annotation helps. For instance, annotation can be added to a User Interface design to specify validation checking.
To annotate a User Interface design:
1. Select Callout from the diagram toolbar. Note that the Callout is under the Common category.

Select Callout from


diagram toolbar

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.

Enter the content of 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.

Using Callout shape to annotate a text field

Annotating the UI design with callout shape P. 280


6. Repeat the above steps to annotate the whole design with Callout shapes.

User Interface diagram with annotations

Annotating the UI design with callout shape P. 281


Identify glossary term
You identify specific terms by adding them to glossary, and clarify them by defining aliases and entering documentation in any textual documents.
1. Highlight the specific term on Documentation editor, right click on it and select Add "[the highlighted term]" to Glossary from the pop-up
menu.

Add "online register" to glossary

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.

Right click to open term editor

3. In the Term Editor page, open Definition tab.


4. You can define aliases for the term and enter documentation as description for the term. To insert an alias, click Add button and type the alias in
the pop-up Input dialog box. To enter definition, enter under Definition directly.

Define aliases and enter definition

5. As a result, the columns of Aliases and Documentation are filled when you return Glossary Grid page.

Completed glossary grid

Identify term from flow of events


Highlight the specific term on flow of events editor, right click on it and select Add "the highlighted term" to Glossary from the pop-up menu.

Add "online register" to Glossary

Identify glossary term P. 282


Identify term from textual analysis
Highlight the specific term on textual analysis, right click on it and select Add "the highlighted term" to Glossary from the pop-up menu.

Add "archived" to Glossary

Identify glossary term P. 283


Glossary grid
Glossary grid is a table where you can identify specific glossary term. In addition, you can define aliases and enter documentation for the glossary
term. With Visual Paradigm for UML (VP-UML), you can categorize the terms by defining and assigning label(s) to them.

Creating glossary grid


To open a grid diagram, select Requirement > Glossary Grid from the toolbar.

Open Glossary Grid

Overview of glossary grid

Glossary grid

No. Name Description

1 Name You can enter the name of grid in here.

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.

Glossary grid P. 284


4 Create Term (Insert) Click this button to create a new term.

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.

9 Import to Excel To import the selected term to an existing 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.

13 Configure columns... Add/ remove property column(s) in Term list.

14 Fresh To update the display on the Term list.

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.

17 Clear filter To clear all words you typed in Filter Term.

18 Term list All created term will be listed in here.

The overview of glossary grid

Organizing terms with labels


With VP-UML, you can categorize the terms by defining and assigning label(s) to them.

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.

Click Manage Label

Glossary grid P. 285


2. In the pop-up Manage Label dialog box, click Add... button to create a label.

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.

Enter name and select a color

4. Click OK button in the Manage Label dialog box.

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.

Click the small plus button

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..

Glossary grid P. 286


2. In the pop-up Add Label dialog box, check a label and then click OK button.

Check a label

NOTE: You can apply multiple labels to a term. Check the applicable labels in the Add Label dialog box.

3. As a result, a specific label is assigned to the corresponding term.

Membership is assigned to general

Filtering terms with specific label


1. If you want to list terms of specific label, click the combo box of Project and select With Label....

Select With Label...

Glossary grid P. 287


2. In the Scope dialog box, check the specific label you want to be listed and then click OK button.

Check Membership

3. As a result, terms with specific label are listed in the grid.

Terms with Membership label are listed

Exporting glossary to Excel


You can export the glossary, along with its terms into an Excel file, and import it back to share with your teammates.
1. In the Glossary Grid, click Export to Excel button.

Click Export to Excel button

2. In the Export Excel dialog box, enter the output directory. Click Export button.

Enter the output directory

Glossary grid P. 288


3. To import the Excel back to your project for a mass modification or review, select File > Import > Excel... from the main menu.

Import the Excel

Glossary grid P. 289


Creating ArchiMate diagram
ArchiMate is a modeling technique for describing enterprise architectures. It divides architecture into three layers - business layer, application layer
and technology layer. The business layer offers products and services to external customers. The application layer supports business layer and the
technology layer offers infrastructural services for application layer.

A part of a sample ArchiMate diagram

Creating ArchiMate diagram


To create an ArchiMate diagram, right click on ArchiMate Diagram in Diagram Navigator and select New ArchiMate Diagram from the popup menu.

To create an ArchiMate diagram through Diagram Navigator

Notations - Business Layer


Name Representation

Business actor

Business role

Creating ArchiMate diagram in VP-UML P. 290


Business
collaboration

Business process

Business function

Business interaction

Business event

Junction

Business service

Business interface

Business object

Product

Contract

Representation

Meaning

Value

A list of supported notations in ArchiMate diagram, for business layer

Notations - Application Layer


Name Representation

Application collaboration

Application component

Application service

Application function

Application interaction

Creating ArchiMate diagram in VP-UML P. 291


Application interface

Data object

A list of supported notations in ArchiMate diagram, for application layer

Notations - Technology Layer


Name Representation

Node

Device

System software

Infrastructure interface

Infrastructure service

Artifact

Communication path

Network

A list of supported notations in ArchiMate diagram, for technology layer

Changing the appearance of some notations


Some of the ArchiMate notations support different ways of presentation. Take node in technology layer as example, to change to another presentation,
right click on the node and select Presentation Options > Display Option, Show as Box/Symbol from the popup menu.

To change the presentation of a node

Node shown as box or symbol

Creating ArchiMate diagram in VP-UML P. 292


Creating ArchiMate diagram in VP-UML P. 293
Creating grid diagram
VP-UML introduces model element grids to provide a convenient way to model and overview the requirements, use cases and actor within your project.
You can also create a grid to list whatever model element type you like, and customize the properties of model element being shown inside the grid.
To create a grid diagram:
1. Select Diagrams > Grid Diagram from the toolbar.

Click Grid Diagram

2. When the Grid Diagram is opened, enter name for the grid.

Enter grid's name

Creating grid diagram P. 294


3. Select a model element type from the combo box of Model Element.

Select use case

The model element of selected type will then be shown on the grid.

The model element of selected type is shown

Creating grid diagram P. 295


Creating element in grid
Besides creating elements by drawing them on diagram, you can also create them in grid. Creating elements in grid gives you an overview on all
elements of same type.
1. Click on the Create [element] button, where element refers to the type of model element you have chosen in the Model Element's combo box.

Click Create Use Case button

2. Enter name for the newly created model element and then press Enter to confirm.

Enter name

Creating element in grid P. 296


Adding/removing property columns
In grid, rows represent model elements while the columns show their properties. Name and documentation columns are shown by default, in addition,
you can optionally add or remove columns to display the data you are interested in.

Adding extra property column


1. Click Configure Columns... button.

Click Configure Columns... button

2. In the Configure Columns dialog box, select your preferred property under Properties tab and then click OK button.

Select Model Type

As a result, the selected property column is inserted in the grid.

Model Type column is added

Removing property column


1. Click Configure Columns... button.

Adding/removing property columns P. 297


2. In the Configure Columns dialog box, select your undesired property under Selected Columns and then click OK button.

Remove Model Type column

As a result, the deselected property column will be removed from the grid.

Adding/removing property columns P. 298


Setting the scope of grid content
In grid, you can customize the scope of grid content after you have created various types of model elements. After that, your desired model elements
within a particular scope will be shown on the grid.
To set the scope of grid content:
1. Select your desired scope from the combo box of Project.

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.

Grid content is updated

Setting the scope of grid content P. 299


Filter and find
VP-UML introduces model element grids to provide a convenience way to model and overview the requirements, use cases and actor within your
project. Except creating a grid with your preferred model element type, you can also search your target model element in shortcut through filter and
find.

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.

Model elements match the word/ phrase you typed

Finding
1. Click Find button.

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

3. Click Find button behind Search Text.

Click Find button

Model element(s) matching the word/ phrase you typed will be highlighted in the grid subsequently.

The matched model elements are highlighted

Filter and find P. 300


Drawing entity relationship diagram
ERD, short for entity relationship diagram, is a kind of diagram for presenting the properties as well as the relationships between data or participants.
Database designer use of ERD to model physical structure of a relationship database, while business analyst uses ERD to model the data that is
logically required or produced by processes.

Creating entity relationship diagram


Right click on Entity Relationship Diagram from Diagram Navigator and select New Entity Relationship Diagram from the pop-up menu.

Create entity relationship diagram

Enter the name for the diagram. At the same time, a Data Model selection box appears on the top right corner of the diagram.

Select data model

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

Click on diagram and specify the entity name.

Rename an entity

Entity Relationship Diagram(ERD) P. 301


Right click on the entity and select New Column from the pop-up menu, or press Alt+Shift+C.

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.

Set as primary key

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

Entity Relationship Diagram(ERD) P. 302


Drawing many-to-many relationship
Click or drag Many-to-Many relationship resource icon of an entity.

Create many-to-many relationship

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.

Created join table with one-to-many relationships

Defining default schema


A default schema can be set on diagram, to make entities to be created on the diagram share the same schema. To define a default schema on
diagram:
Right click on the diagram background and select Open Specification... from the pop-up menu.

Select Open Specification... from the pop-up menu

Entity Relationship Diagram(ERD) P. 303


Specify the default schema in the Entity Relationship Diagram Specification dialog box. Click OK to confirm the change.

Specify default schema

Now, when you create an entity on the diagram, the entity will be under the default schema.

An entity with myschema as its 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.

Entity Relationship Diagram(ERD) P. 304


Drawing sequence
Creating sequence
Click Sequence from diagram toolbar and drag it on the diagram pane.

Create sequence

Type the name for sequence when it is created.

Rename sequence

Right click on the sequence and select Open Specification... from the pop-up menu. In Sequence Specification dialog box, specify sequence
attributes.

Specify sequence attributes

NOTE: Generate sequence is only supported in DB2 and Oracle.

Select sequence for entity


After creating an entity and a primary key column, right click on the primary key column and select Open Specification... from the pop-up menu.

Drawing sequence P. 305


In Column Specification dialog, select sequence for ID Generator, and select the sequence name for Key.

Select sequence for entity

When using Object-Relational Mapping feature, the primary key value will be inserted automatically from the sequence.

Drawing sequence P. 306


Drawing stored procedures
Creating stored procedures shape
Click Stored Procedures from diagram toolbar and drag it on the diagram pane.

Create stored procedure shape

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.

Create stored procedure

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.

Specify create statement in Procedure Specification dialog box

Moving or duplicating a procedure to another procedure container

Drawing stored procedures P. 307


1. Select the procedure to move or duplicate.

Select procedures to move or duplicate

2. Drag over the target procedure container.

Drag procedure towards the target procedures container

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.

Procedures are moved

Creating stored procedure resultSet


Click Stored Procedure ResultSet from diagram toolbar and drag it on the diagram pane.

Create stored procedure resultset

After specify the name for the newly created resultset, press Enter.

Rename stored procedure resultset

The way of creating resultset column is the same as creating entity column.

Drawing stored procedures P. 308


Right click on the procedure that created above, select Open Specification... from the pop-up menu. In Procedure Specification dialog box, specify
stored procedure return resultset.

Specify stored procedure return resultset

Drawing stored procedures P. 309


Drawing triggers
Create a triggers shape
Click Triggers from diagram toolbar and drag it on the diagram pane.

Create triggers shape

After specify the name for the newly created triggers, press Enter.

Rename a triggers shape

Create a new trigger


Right click the triggers and select New Trigger from the pop-up menu, or press Alt+Shift+T.

Create a new trigger

In Triggers Specification dialog box, specify the create statement.

Specify the create statement in Trigger Specification dialog box

Move or duplicate triggers to another trigger container


1. Select the trigger to move or duplicate.

Selecting triggers to move or duplicate

Drawing triggers P. 310


2. Drag over the target trigger container.

Dragging trigger towards the target triggers container

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.

Triggers are moved

Drawing triggers P. 311


Controlling primary key values using ID generator
ID generator defines how a unique value will be produced for a primary key column. You can assign an ID generator to a primary key column for which
strategy will be used when generating an ID in runtime.
1. Right click the primary key column that you want to select an ID generator for and select Open Specification... from the pop-up menu.

Select Open Specification... from the pop-up menu

Controlling primary key values using ID generator P. 312


2. In Column Specification dialog box, select the ID Generator and then click OK to confirm.

Select an ID generator in Column Specification dialog box

ID Generator Description

assigned lets the application to assign an identifier to the object before is called.

guid uses a database-generated GUID string on MS SQL Server and MySQL.

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

The description of available ID Generator

Controlling primary key values using ID generator P. 313


Customizing ID generator
Besides the built-in strategies for generating ID, user can implement how ID will be generated by customizing an ID generator.
1. In Class Diagram, create the ID generator class, and stereotype it as ORM ID Generator.

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.

Click Open Specification... from the pop-up menu

3. In the Column Specification dialog box, select the class in the ID Generator.

Select an ID generator in Column Specification dialog box

4. Click OK to confirm.

Customizing ID generator P. 314


5. After generated ORM code, look for the ID generator class and implement the generate method by return an Integer or Long.
/**
* Licensee: VP Development
* License Type: Purchased
*/
import java.io.Serializable;
import org.hibernate.engine.SessionImplementor;
import org.hibernate.id.IdentifierGenerator;
public class ProductIDGenerator implements IdentifierGenerator {
public Serializable generate(SessionImplementor session, Object object) {
//TODO: Implement Method
throw new UnsupportedOperationException();
}
}
//ORM Hash:fae9faed19486e5f2b85c9d2d0d52cd9

Customizing ID generator P. 315


Drawing View
Drawing view
Click View from diagram toolbar and drag it on the diagram.

Creating view

Click on diagram and specify the view name.

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

Enter the column name and press Enter to confirm.

Column created

Drawing View P. 316


Generate class diagram from ERD
1. Open an existing ERD or create a new ERD.

ERD

2. Right click on the diagram's background and select Synchronize to Class Diagram from the pop-up menu.

Synchronize to class diagram

Generate class diagram from ERD P. 317


3. In the Synchronize from Entity Relationship Diagram to Class Diagram dialog box, select the target diagram and click OK button.

Select diagram for synchronize

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.

Synchronize to Class Diagram dialog box

Generate class diagram from ERD P. 318


5. A class diagram with generated classes and associations is created.

Generated class diagram

Generate class diagram from ERD P. 319


Synchronize from class diagram to ERD
1. Select ORM-Persistable Class from the diagram palette.

Create ORM-Persistable class

2. Click on the diagram to name it as Supplier, create attributes and association as follow.

Create Supplier class

3. Add name attribute to Product_Type class.

Create attribute

4. Right click on diagram, select Synchronize to Entity Relationship Diagram from the popup menu.

Synchronize to Entity Relationship Diagram

Synchronize from Class Diagram to ERD P. 320


5. A Synchronize to Entity Relationship Diagram dialog appears. Select Auto Generate in Select Primary Key table and rename the entity/
column if necessary. Click OK button to continue.

Synchronize to Entity Relationship Diagram dialog box

6. New entities and column are created on the ERD.

Synchronized ERD

Synchronize from Class Diagram to ERD P. 321


Configure key naming pattern
1. Select Tools > Options... from the main menu.

Open Options dialog box

2. Select Diagramming from the list on the left and open ERD & ORM tab.

Open ERD & ORM tab

Configure key naming pattern P. 322


3. Change Primary Key Pattern and Foreign Key Pattern.

Change primary key and foreign key pattern

4. Create a new ORM-Persistable class on class diagram and synchronize to ERD.


5. In the Synchronize to Entity Relationship Diagram dialog box, the primary key column name is newly generated.

Default primary key column name

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.

Default foreign key column name

Configure key naming pattern P. 323


Drawing business process diagrams
Business Process Modeling Notation (BPMN) is a graphical representation for designing and modeling business processes visually. It is a standard for
business process modeling, and provides a graphical notation for specifying business processes in a business process diagram (BPD).

Creating business process diagram


To create a business process diagram, right click on Business Process Diagram in Diagram Navigator and select New Business Process Diagram
from the pop-up menu.

Create business process diagram

Creating pool
To create pool, click Horizontal Pool on the diagram toolbar and then click on the diagram.

Create pool

Adding lane to pool


To add lane to pool, right-click the pool and select Add Lane from the pop-up menu.

Create lane

Creating start event


To create start event, click Start Event on the diagram toolbar and then click on the diagram.

Create start event

Creating task
To create task from a start event, click on the Sequence Flow -> Task resource beside it and drag.

Create task

Drawing business process diagrams P. 324


Move the mouse to where you want to place the shape to and then release the mouse button. A task is created and connected to the start event with a
sequence flow.

Task and sequence flow created

Creating message flow


To create message flow, click Message Flow on the diagram toolbar.

Create message flow

Drag from the source shape, move the mouse over the target shape and then release the mouse button to create the message flow.

Connect shapes with message flow

Automatic connection rule checking


VP-UML provides automatic connection rule checking to make sure your business process diagram is in compliance with the BPMN specification.

Drawing business process diagrams P. 325


For example, if you move a task from one pool to another, and if this task is connected with another shape with sequence flow, the Invalid Connection
Detected dialog box shows to advice you to change sequence flow to message flow.

Invalid connection detected

Click OK button to accept the correction. The sequence flow is changed to message flow automatically.

Sequence flow changed to message flow

Creating gateway
To create gateway from a task, click on the Sequence/Message Flow -> Gateway resource beside it and drag.

Create gateway

Drawing business process diagrams P. 326


Move the mouse to where you want to place the shape to and then release the mouse button. A gateway is created and connected to the task with a
sequence flow.

Gateway and sequence flow created

Creating intermediate event


To create intermediate event from a task, click on the Sequence/Message Flow -> Intermediate Event resource beside it and drag.

Create intermediate event

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.

Intermediate event and sequence flow created

Creating text annotation


To create text annotation from a task, click on the Association -> Text Annotation resource beside it and drag.

Create text annotation

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.

Text annotation and association created

Splitting sequence flow with shape


You can use the split sequence flow utility to split a sequence flow by task, sub-process, intermediate event or gateway.
Before this, you may want to move some shapes aside to make room for the new shape. Select Sweeper on the diagram toolbar.

Sweeper

Drawing business process diagrams P. 327


Click on the diagram and drag to sweep shapes aside, release the mouse button when enough room is made.

Sweep shapes aside to make more room

Click the Split with Shape resource beside the sequence flow.

Split with Shape resource

Select the shape type to split the sequence flow.

Select shape type to split sequence flow

The sequence flow is split by the selected type of shape.

Sequence flow split by the selected type of shape

Forming sub-Process diagram


To create sub-process for shapes, select the shapes in diagram, right click on the selection and select Form Sub-Process Diagram from the pop-up
menu.

Form sub-process diagram

A new diagram is created with the selected shapes.

Form sub-process diagram

Drawing business process diagrams P. 328


When you return to the original diagram, you will see the selected shapes are transformed to a sub-process.

Shapes transformed to sub-process

Continue to complete the diagram.

Completed diagram

Assigning IDs to model elements


It is possible to assign IDs to objects in business process diagram. By default, IDs are assigned by following the order of object creation, starting from
number 1. However, you can define the format, or to enter an ID manually.

Defining the format of ID


To define the format of ID, open the Options dialog box by selecting Tools > Options from the main menu. Select Diagramming from the list on the
left hand side, and open the Business Process tab. From there you can adjust the format, and control whether or not to display the ID on diagram,
and the position of ID.

Define format of ID

Drawing business process diagrams P. 329


Below is a description of options.

Option Description

Prefix Text to add before the number

Num of digits The number of digits of the number. For example, when digit is 3, ID "1" will become "001"

Suffix Text to append to the number

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

Options for formatting ID

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

Drawing business process diagrams P. 330


In the Configure Show ID Options dialog box, click on the drop down menu Show ID Options and select if you want to show IDs, and if yes, where to
show - below caption or as a label.

To configure the whether or not to show ID

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.

To make ID of task show as label, position at the left of shape

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

Drawing business process diagrams P. 331


Setting task/sub-process/gateway/event type
To change the type of task/sub-process/gateway/event, right click on the shape and select Type, and then the target type from the pop-up menu.

Select task type

Drawing business process diagrams P. 332


Setting loop type for task and sub-process
To set the loop type for task/sub-process, right click on the shape and select Open Specification... from the pop-up menu. In the specification dialog
box, update the Loop Type selection and click OK button to confirm editing.

Edit the loop type

Drawing business process diagrams P. 333


Drawing data flow diagrams
Data flow diagram is a well known approach to visualize the data processing in business analysis field. A data flow diagram is strong in illustrating the
relationship of processes, data stores and external entities in business information system.

Creating data flow diagram


To create a data flow diagram right click on Data Flow Diagram in Diagram Navigator and select New Data Flow Diagram from the pop-up menu.

Create data flow diagram

Creating external entity


To create external entity, click External Entity on the diagram toolbar and then click on the diagram.

Create external entity

An external entity is created.

External entity created

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.

Process and data flow created

To edit properties of the process, right click on it and select Open Specification from the pop-up menu.

Drawing data flow diagrams P. 334


Edit properties such as ID and Location in the Process Specification dialog box, click OK button to apply the changes.

Process specification dialog box

The process is updated.

Process updated

Creating data store


To create data store from process, click the Data Flow -> Data Store resource beside it and drag.

Create data store

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.

Data store and data flow created

Continue to complete the diagram.

Completed diagram

Drawing data flow diagrams P. 335


Drawing event-driven process chain diagrams
EPC diagram, short for event-driven process chain diagram, is a flowchart based diagram that can be used for resource planning and identifying
possible improvements of a business process.

Creating event-driven process chain diagram


To create an EPC diagram, right click on EPC Diagram in Diagram Navigator and select New EPC Diagram from the pop-up menu.

Create EPC diagram

Creating event
To create event, click Event on the diagram toolbar and then click on the diagram.

Create event

An event will be created.

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.

Function and control flow created

Drawing event-driven process chain diagrams P. 336


Creating operator
To create operator (e.g. XOR operator) from event, click the Control Flow -> XOR Operator resource beside it and drag .

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.

Operator and control flow created

Creating process path


To create process path from event, click the Control Flow -> Process Path resource beside it and drag .

Create process path

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.

Process path and control flow created

Creating information resource


To create information resource, click Information Resource on the diagram toolbar and then click on the diagram.

Create information resource

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.

Create information flow

Mouse over a function and then release the mouse button, an information flow will be created.

Information flow created

Drawing event-driven process chain diagrams P. 337


Continue to complete the diagram.

Completed diagram

Drawing event-driven process chain diagrams P. 338


Drawing process map diagram
Process map diagram gives an overview that shows the processes needed to approach a business goal. It is rather in an upper level of analyzing and
understanding a business process.

Creating process map diagram


To create a process map diagram, right click on Process Map Diagram in Diagram Navigator and select New Process Map Diagram from the pop-
up menu.

Create process map diagram

Creating receive
To create receive, click Receive on the diagram toolbar and then click on the diagram.

Create receive

A receive will be created.

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

Drawing process map diagram P. 339


Creating send
To create send from process, click the Process Link -> Send resource beside it and drag .

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

Continue to complete the diagram.

Completed diagram

Drawing process map diagram P. 340


Drawing organization charts
An organization chart is a diagram that visualizes the formal structure of an organization as well as the relationships and relative ranks of its positions.
It is usually drawn and read from the top to the bottom. The default unit will pop out when a new organization chart is created.
In VP-UML, organization chart is not only a diagram, but also a reference used for other parts of your model. For example, you may use an
organization chart to depict the company hierarchy involved in a business process model. Its prime function is to help a business analyst to visualize
efficiently the company structure as well as the division of works when performing business analysis.
The completed organization chart is shown as follows:

Completed organization chart

Creating an organization chart


Right Click Organization Chart in Diagram Navigator and select New Organization Chart from the popup menu.

Create new organization chart

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:

Drawing organization charts P. 341


1. Move the mouse pointer a unit and click its resource icon New Coworker, either on its left or right hand side.

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

2. Release the mouse to confirm the position.

Completed relocating a branch

NOTE: If you are not satisfied the relocation, press Esc to cancel the movement.

Drawing organization charts P. 342


JPDL generation in VP-UML
1. Model the process in a business process diagram.

A business process diagram

2. Right click on the diagram's background and select jPDL Diagram in the popup menu.

Set diagram to be a jPDL diagram

JPDL generation P. 343


3. Right click on the diagram's background and select Utilities > Generate jPDL... 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.

The jBPM console

JPDL generation P. 344


What is simulacian?
The objective of performing business process modeling is to facilitate the communication with stakeholders, to perform cost and benefit analysis and
to perform process improvement, etc. Simulacian is a set of value-added tools designed to aid business process modeling. With simulacian, you
can simulate the execution of business process for studying the resource consumption (e.g. human resources, devices, etc.) throughout a process,
identifying bottlenecks, quantifying the differences between improvement options which helps study and execute process improvements.

Simulating a business process with Simulacian

Key concepts

What is simulacian? P. 345


Resources
Resources refer to any kind and form of input essential for the execution of a process. Each resource has three properties - name, type and amount.
There are two types of resources - available resources and required resources. Available resources refer to the resources that can be used by
business process, but may not be fully used. For example, a post office has 10 counters as resources, but only 3 are in used at peak hours. Required
resources is a flow object wide option. You can set the resource and the amount of resource required by completing a flow object. For example, task
Answering Enquiry requires 1 counter as resource.

Required and available resources

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.

Executing and pending jobs

What is simulacian? P. 346


Performance analysis through charts
During simulation of business process, you can identify the bottleneck(s) by observing the occurrence of pending jobs (i.e. the inverted triangle). This
works well in a relatively small process. However, if your business process diagram is large you may not be able to study the simulacian outcome just
by observation because the simulcian can be lengthy and involve several bottlenecks. Furthermore, you may want to know the exact figure of resource
consumption for conducting a more accurate resource re-allocation plan. In those cases, you can produce simulacian charts that reports the completion
of inputs, resource usage and queue time of flow objects against time.

Different kinds of chart

What is simulacian? P. 347


Simulacian control panel
In order to simulate a business process you need to define simulation details like available and required resources, duration of tasks/sub-processes,
instances of pools/lanes and inputs. All these information can be defined in simulacian control pane, which is a pane that display at the bottom of
diagram, important for adjusting any settings related to simulacian. The panel will be updated base on your selection in active diagram. Besides setting
simulacian details, start/pause of simulation can also be done in the panel.

Opening simulacian control panel


To open the simulacian control panel, right click on the business process diagram that you want to simulate and select Show Simulacian Control
Panel from the popup menu.

Opening simulacian control panel

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.

Overview of simulacian control panel


Common

An overview of simulacian control panel

No. Name Description

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.

2 Stop Stop a simulating business process.

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.

Simulacian control panel P. 348


5 Simulacian Click to display a new window that display the completion, resource usage and queue time charts base on the settings of
charts resource, duration and input. You can treat it as a chart form of simulation outcome.

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.

Description of simulacian control panel

When selected pool/lane

An overview of simulacian control panel while selected pool/lane

No. Name Description

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

Description of simulacian control panel while selected pool/lane

When selected flow objects

Simulacian control panel P. 349


An overview of simulacian control panel while selected flow object

No. Name Description

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

Description of simulacian control panel while selected flow objects

When selected diagram background / showing inputs

An overview of simulacian control panel while selected diagram background or showing inputs

No. Name Description

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.

Simulacian control panel P. 350


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

Description of simulacian control panel while selected diagram background or showing inputs

When simulating

An overview of simulacian control panel while simulating

No. Name Description

1 Pause To temporarily pause a simulation.

2 Stop To stop simulating the business process.

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.

Description of simulacian control panel while simulating

Simulacian control panel P. 351


Simulating business process
In order to simulate a business process, you must provide performance-related information to the business process diagram, such as resource
consumption and duration of flow objects, so that simulacian can analyze the information and conduct a simulation. Below are what you have to do to
start simulation.
1. Right click on the background of the business process diagram that you want simulate and select Diagram Type > Simulacian from the popup
menu.

Set diagram's type to Simulacian

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?.

To add available resources

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.

To add required resources

Simulating business process P. 352


4. For each of the flow objects, select it in diagram, and set in Simulacian Control Panel its duration, which is the time it takes to get completed. If
you want to know more about duration, please refer to the chapter What is simulacian?.

To set the duration of 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.

To set instance of pools or lanes

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

Simulating business process P. 353


8. Click Start in Simulacian Control Panel to start simulation.

Start simulation

Now, you can watch the simulation in diagram, to see the executions of inputs and identify bottlenecks.

Simulation is running

Simulating business process P. 354


Simulacian charts
Sometimes, just by watching the simulacian outcome is not enough in finding out the bottleneck, especially when the diagram is large, and have many,
many bottlenecks. In such cases, you can produce charts for simulacian outcome, which helps quantify resource consumption and queuing time for
each flow object.
To read the charts, click Simulacian Charts in simulacian control panel.

To open simulacian charts window

Completion chart
The completion chart primarily shows the status of inputs completion against time.

An overview of completion chart

No. Name Description

1 Resource usage Click to show resource usage chart.

2 Queue time Click to show queue time chart.

3 Time scale Control the length of chart by selecting a time scale.

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.

Simulacian charts P. 355


9 Chart body The chart body.

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.

Description of completion chart

Resource usage chart


The resource usage chart shows the percentage of resource consumption throughout simulation. If a resource has its peak reaching 100%, it means
that the allocation of that resource is in optimum state. If the peak is below 100%, it means that some of the resources are not used throughout the
simulation, which usually signifies that they are wasted, and you should consider to adjust the amount of available resource to optimize the resource
consumption.

An overview of resource usage chart

No. Name Description

1 Complete Click to show completion chart.

2 Queue time Click to show queue time chart.

3 Show by Select what to present in the chart.


Resource - Cause the chart to presents the resource consumption of each available resource.
Resource Type - Cause the chart to presents the resource consumption of resource types.

4 Time scale Control the length of chart by selecting a time scale.

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.

Simulacian charts P. 356


9 Chart body The chart body.

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.

Description of resource usage chart

Queue time chart


The queue time chart shows the time the flow objects spent on waiting, which corresponds to the time an inverted triangle appear during simulacian.
You may study whether the queue time of certain flow object is reasonable or not, and think of the improvement.

An overview of queue time chart

No. Name Description

1 Completion Click to show completion chart.

2 Resource Click to show resource usage chart.


usage

3 Time scale Control the length of chart by selecting a time scale.

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.

7 Chart body The chart body.

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.

Description of queue time chart

Simulacian charts P. 357


Drawing mind mapping diagram
Mind mapping is a tool to help you in brainstorming and organizing ideas, concepts, words, tasks through a visual note-taking way. It sometimes helps
to capture requirements and business process, too. Modelers can create and link model element (such as task, use case, classes) with mind mapping
node. The traceability can be kept between initial idea (mind mapping node) and detail design elements (e.g. class).

Creating mind mapping diagram


To create a mind mapping diagram:
1. Right click on the node Mind Mapping Diagram in Diagram Navigator and select New Mind Mapping Diagram in popup menu.

Create a mind mapping 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.

Naming central idea node

Creating branch with resource centric interface


Mind mapping is formed by nodes that represent ideas or concepts. They are connected with each other, showing the flow of thinking. To create a new
branch of nodes from an existing node:
1. Move the mouse pointer over a node. Press on the resource icon Branch -> Node.

To create a node

2. Drag it out. Release the mouse button to create the node.

A node is created

3. Name the node and press Enter to confirm. Create the other nodes by repeat the same steps.

A mind mapping diagram is created

Drawing mind mapping diagram P. 358


Formatting nodes
You can set colors to nodes to represent different kinds of idea and concepts. You can also set icon(s) to a node to represent the nature of a node,
such as a telephone icon for concepts related to contacting some body.

Changing the line, fill or font style of node


1. Select the node(s) that you want to format. Multiple node selection can be made by a range selection or by pressing the Ctrl key and select the
nodes subsequently.
2. Move the mouse pointer to a node within the selection. Click on the Format resource icon.

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.

Choosing a color for node

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.

Nodes with brown border

Fill
Fill settings control the background color of node(s). You can apply solid and gradient colors, as well as to control the transparency.

Nodes with gray background

Font
Font settings control the font style, size, type and color of text appear on a node.

Nodes with Times new roman text

Formatting nodes P. 359


Changing icon of node
1. Select the node(s) that you want to set icon. Multiple node selection can be made by a range selection or by pressing the Ctrl key and select the
nodes subsequently.
2. Move the mouse pointer to a node within the selection. Click on the Format resource icon, then select Icons... from the popup menu.

To edit icons for a node

3.

A node with icons

Formatting nodes P. 360


Linking nodes
Other than the traditional branch connector that represents a generation of idea, you can link related ideas and concepts by using a link connector.
There is no exact definition about how two nodes can said to be related. It is up to the designer whether to link the nodes or not. As long as you want to
represent that two nodes and related, and the relationship is meaningful, you can add a link between them.
To link nodes:
1. Move the mouse cursor over the source node. Press on any of the resources: Link, To Link, From Link. To and From links are directed
relationship, which shows an arrow to indicate the flow from source to target node.

To link to antoher node

2. Drag to the target node and release the mouse button.

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.

3. Optionally enter the name of link. Press Enter to confirm editing.

Link is created between nodes

Linking nodes P. 361


Reference to resources
You can add references to node, to reference to both internal and external resources such as a shape, a diagram, a file, a URL, etc. For example, to
make a node Prepare Agenda link to a document of agenda template. This makes a mind map more informative by providing additional information
from a mind map which might be casually developed.
To add a reference:
1. Right click on the node you want to add reference and select Open Specification... from the popup menu.

Opening node specification

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.

Going to add a reference

Type of reference Description

File An external file.

Folder An external folder.

URL A URL. For example, http://www.visual-paradigm.com

Diagram A diagram in the opening project, such as a requirement diagram.

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.

Description of different kinds of reference

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.

Opening a referenced file

Reference to resources P. 362


Relocating a branch
In case a branch of nodes is mis-positioned, you can reposition it to under another node through drag and drop. Here are the steps:
1. Press on the pointer end of the first node of a branch that you want to reposition.

Pressing on the pointer end of a node

2. Drag to node that you want to move the branch to.

Dragging over the target node

3. Release the mouse button.

Mouse button released

Relocating a branch P. 363


Layout diagram
In a mind mapping diagram, ideas are stretching out across, which leads difficulties in tracing nodes with different ideas due to the unorganized nodes.
It will be time consuming to rearrange the idea nodes manually. This also affects our brainstorming procedure by caring the tidiness of diagram. By
performing a layout, you can keep brainstorming and drawing the diagram without caring about the tidiness of the diagram. You can perform a layout
once the diagram is drew. Any nasty diagrams can be well organized in a breeze.

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.

To layout nodes on a diagram

Result of diagram based layout - all nodes are layout-ed

Layout nodes and diagram P. 364


Using resource-centric interface
Mouse gesture enables you to layout shapes on a diagram through the movement of mouse. To perform a layout with mouse gesture, right press on
the diagram background, sketch a "L" like gesture path and release the mouse button to execute layout.

Layout diagram with mouse gesture

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.

To perform a node based layout

Layout nodes and diagram P. 365


Result of node based layout - only Schedule node is layout-ed

Layout nodes and diagram P. 366


What is animacian?
Animacian is a tool that helps you make possible paths in an active diagram by presenting the paths in animation form. This can make your design
more attractive by animating it. Besides, you can control the flow of animation yourself to help demonstrating your work to client with your annotation. It
also calculates all possible paths of the interaction, making the design more accurate.

Animating paths in diagram


Animation can be played directly on diagram. When the animation begins, a tiny black dot will be attached to the begining of the path selected to
animate. During the animation, the black dot will traverse through the path, shapes that lie on the path will be painted in purple one by one, when being
approached by the black dot, until the black dot reached the end of the path.

An animating path

Automatic paths identification


Interconnected shapes form a path. It is possible to have multiple paths on a diagram. Animacian helps finding out all possible paths in a diagram.
When opening the Animacian dialog box, valid paths on the opening diagram will be identified and listed for selection. You can then select a path to
animate. Unclosed paths or paths that does not obey the notation are classified as invalid, thus won't be available for playing animation.

Filter business paths base on conditions


The Animacian dialog box is where you can configure animation and select path to animate. You can apply filter on path identification, which clears
undesired path that does not match certain condition. To configure filter:

What is animacian? P. 367


1. Click Filter... button in the Business Process Diagram Animacian dialog box.

Click the Filter... button

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.

What is animacian? P. 368


3. Click OK to confirm. The identified paths will be reduced accordingly.

Paths are reduced as a result of applying filter

Walking through a path step-by-Step


Instead of letting the animation to run itself, you can control it yourself. The horizontal bar that appear at the bottom of VP-UML when animating lets

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.

Walk though a path step by step

Showing documentation of current step when playing animation


When walking through a path, the documentation of the visiting shape, if written, will appear instantly at the bottom right corner of VP-UML.

What is animacian? P. 369


To turn this function on or off, open the Animacian dialog box, then check or uncheck Show documentation when playing.

Uncheck Show documentation when playing

What is animacian? P. 370


Animating business process diagram
By animating a business process diagram with Animacian, you can see the flow of tasks within a process, from the beginning until the end. This does
not only help to understand a process, but also trace the bottleneck and look for improvements.

Launching an animation
1. Select Tools > Animacian... from the main menu.

Launch Animacian through the main menu

2. In Business Process Diagram Animacian dialog box, select a path and then click Play.

Clicking Play in Business Process Diagram Animacian dialog box

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.

Animating business process diagram P. 371


Overview of Animacian
The Business Process Diagram Animacian dialog box will pop out after clicking Animacian.... This dialog box is where you can select an execution
path to play an animation.

Business Process Diagram Animacian dialog box

No. Name Description

1 Backward Move one shape backward in the flow.

2 Play Play or continue to play the animation with Animacian minimized.

3 Stop Terminate the animation.

4 Forward Advance to the next shape in the flow.

5 Slider It is used for controlling the flow of animation.

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.

14 Minimize Click to minimize this dialog box.

15 Options pane The Options pane helps you to configure animation.

Animating business process diagram P. 372


Show invalid paths: It lists not only the valid and selected path, but also the invalid and non-playable paths in the
Paths list.
Dim other path: It dims the components that are not a part of the selected path.
Show start node when switch path: Jump to the first node of the selected path, or keep staying at the current viewing
field.
Minimize when play: It minimizes this dialog box when playing an animation.
Lock diagram when playing: It locks the diagram when playing the animation to prevent accidental editing.
Show documentation when playing: It shows documentation of shape at the bottom right of diagram when playing
the animation.
Play voice when playing: Voice can be recorded as documentation of model element. Check this if you want to play
recorded voice when running animation.

16 Advanced Options... It provides the color and speed options for animation.

17 OK Click this button to confirm the settings and close Animacian.

18 Cancel Click this button to close Animacian without saving the editing.

Description of Business Process Diagram Animacian dialog box

Advanced options

Advanced Options dialog box

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.

Visited fill color The background color of visited shapes.

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.

Visited line color The line color of visited shapes.

Visited font color The font color of visited shapes.

Visited line width The thickness of visited shape's border.

Ball color The color of ball that goes through a path during animation for indicating the progress of flow.

Speed The pace of animation.

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.

The description of Advanced Options dialog box

Animating business process diagram P. 373


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.
1. To rename a path, move the mouse pointer on a path in the list and double click on it.
2. Enter the name of path.
3. Press Enter to confirm editing.

Naming the paths

Creating a manual path


In Business Process Diagram Animacian dialog box, all paths are listed in Paths list by default. However, you can manage the flow of animation
with your own choice. To create a manual path:
1. Select Manual in Paths.

Selecting Manual in Paths

2. Press Add Path to insert a new path.


3. Select the shapes that are shown on the Components list to direct the flow of animation.
4. Click OK to confirm editing.

Animating business process diagram P. 374


Handling decision
You should choose an outgoing flow when there is a gateway in the flow. Different decisions will lead to different forks and make a different outcome
for the flow of animation. Make either decision to view the outcome.

Making a decision for the flow of path

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

BackwardMove one shape backward in the flow.

Pause Temporary stop playing the movie. Press Play


to continue to play.

Play Play or continue to play the animation.

Forward Advance to the next shape in the flow.

Stop Terminate the animation.

MaximizeMaximize Animacian.

Description of Animacian bar

3. When the animation starts, a black ball will appear at beginning of path and traverse through the path until the end.

Animating business process diagram P. 375


4. When the black ball reaches a shape, the shape will turn into purple.

Reviewing the animation

Animating business process diagram P. 376


Animating sequence diagram
By animating a sequence diagram with Animacian, you can see interaction between lifelines and the flow of message calls in active.

Launching an animation
1. Select Tools > Animacian... from the main menu.

Launch Animacian through the main menu

2. In Sequence Diagram Animacian dialog box, select a path and then click Play.

Clicking Play in Sequence Diagram Animacian dialog box

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.

Animating sequence diagram P. 377


Overview of Animacian
The Sequence Diagram Animacian dialog box will pop out after clicking Animacian.... This dialog box is where you can select an execution path to
play an animation.

Sequence Diagram Animacian dialog box

No. Name Description

1 Backward Move one shape backward in the flow.

2 Play Play or continue to play the animation with Animacian minimized.

3 Stop Terminate the animation.

4 Forward Advance to the next shape in the flow.

5 Slider It is used for controlling the flow of animation.

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.

13 Minimize Click to minimize this dialog box.

14 Options pane The Options pane helps you to configure animation.


Show invalid paths: It lists not only the valid and selected path, but also the invalid and non-playable paths in the
Paths list.
Dim other path: It dims the components that are not a part of the selected path.
Show start node when switch path: Jump to the first node of the selected path, or keep staying at the current viewing
field.

Animating sequence diagram P. 378


Minimize when play: It minimizes this dialog box when playing an animation.
Lock diagram when playing: It locks the diagram when playing the animation to prevent accidental editing.
Show documentation when playing: It shows documentation of shape at the bottom right of diagram when playing
the animation.
Play voice when playing: Voice can be recorded as documentation of model element. Check this if you want to play
recorded voice when running animation.

15 Advanced Options... It provides the color and speed options for animation.

16 OK Click this button to confirm the settings and close Animacian.

17 Cancel Click this button to close Animacian without saving the editing.

Description of Sequence Diagram Animacian dialog box

Advanced options

Advanced Options dialog box

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.

Visited fill color The background color of visited shapes.

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.

Visited line color The line color of visited shapes.

Visited font color The font color of visited shapes.

Visited line width The thickness of visited shape's border.

Ball color The color of ball that goes through a path during animation for indicating the progress of flow.

Speed The pace of animation.

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.

The description of Advanced Options dialog box

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.

Animating sequence diagram P. 379


1. To rename a path, move the mouse pointer on a path in the list and double click on it.
2. Enter the name of path.
3. Press Enter to confirm editing.

Naming the path

Creating a manual path


In Sequence Diagram Animacian dialog box, all paths are listed in Paths list by default. However, you can manage the flow of animation with your
own choice. To create a manual path:
1. Select Manual in Paths.

Selecting Manual in Paths

2. Press Add Path to insert a new path.


3. Select the shapes that are shown on the Components list to direct the flow of animation.
4. Click OK to confirm editing.

Animating sequence diagram P. 380


Handling decision
You should choose an operand when there is more than one option in the interaction. Different decisions will lead to different forks and make a different
outcome for the flow of animation. Make either decision to view the outcome.

Making a decision for the flow of path

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

BackwardMove one shape backward in the flow.

Pause Temporary stop playing the movie. Press Play


to continue to play.

Play Play or continue to play the animation.

Forward Advance to the next shape in the flow.

Stop Terminate the animation.

MaximizeMaximize Animacian.

Description of Animacian bar

3. When the animation starts, a black ball will appear at beginning of path and traverse through the path until the end.

Animating sequence diagram P. 381


4. When the black ball reaches a shape, the shape will turn into purple.

Reviewing the animation

Animating sequence diagram P. 382


Animating activity diagram
By animating an activity diagram with Animacian, you can see the flow of actions in active.
1. Select Tools > Animacian... from the main menu.

Launch Animacian through the main menu

2. In Activity Diagram Animacian dialog box, select a path and then click Play.

Clicking Play in Activity Diagram Animacian dialog box

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.

Animating activity diagram P. 383


Overview of Animacian
The Activity Diagram Animacian dialog box will pop out after clicking Animacian.... This dialog box is where you can select an execution path to play
an animation.

Activity Diagram Animacian dialog box

No. Name Description

1 Backward Move one shape backward in the flow.

2 Play Play or continue to play the animation with Animacian minimized.

3 Stop Terminate the animation.

4 Forward Advance to the next shape in the flow.

5 Slider It is used for controlling the flow of animation.

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.

13 Minimize Click to minimize this dialog box.

14 Options pane The Options pane helps you to configure animation.


Show invalid paths: It lists not only the valid and selected path, but also the invalid and non-playable paths in the
Paths list.
Dim other path: It dims the components that are not a part of the selected path.
Show start node when switch path: Jump to the first node of the selected path, or keep staying at the current viewing
field.

Animating activity diagram P. 384


Minimize when play: It minimizes this dialog box when playing an animation.
Lock diagram when playing: It locks the diagram when playing the animation to prevent accidental editing.
Show documentation when playing: It shows documentation of shape at the bottom right of diagram when playing
the animation.
Play voice when playing: Voice can be recorded as documentation of model element. Check this if you want to play
recorded voice when running animation.

15 Advanced Options... It provides the color and speed options for animation.

16 OK Click this button to confirm the settings and close Animacian.

17 Cancel Click this button to close Animacian without saving the editing.

Description of Activity Diagram Animacian dialog box

Advanced options

Advanced Options dialog box

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.

Visited fill color The background color of visited shapes.

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.

Visited line color The line color of visited shapes.

Visited font color The font color of visited shapes.

Visited line width The thickness of visited shape's border.

Ball color The color of ball that goes through a path during animation for indicating the progress of flow.

Speed The pace of animation.

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.

The description of Advanced Options dialog box

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.

Animating activity diagram P. 385


1. To rename a path, move the mouse pointer on a path in the list and double click on it.
2. Enter the name of path.
3. Press Enter to confirm editing.

Naming the paths

Creating a manual path


In Activity Diagram Animacian dialog box, all paths are listed in Paths list by default. However, you can manage the flow of animation with your own
choice. To create a manual path:
1. Select Manual in Paths.

Selecting Manual in Paths

2. Press Add Path to insert a new path.


3. Select the shapes that are shown on the Components list to direct the flow of animation.
4. Click OK to confirm editing.

Animating activity diagram P. 386


Handling decision
You should choose an outgoing flow when there is more than one option in the flow. Different decisions will lead to different forks and make a different
outcome for the flow of animation. Make either decision to view the outcome.

Making a decision for the flow of path

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

BackwardMove one shape backward in the flow.

Pause Temporary stop playing the movie. Press Play


to continue to play.

Play Play or continue to play the animation.

Forward Advance to the next shape in the flow.

Stop Terminate the animation.

MaximizeMaximize Animacian.

Description of Animacian bar

3. When the animation starts, a black ball will appear at beginning of path and traverse through the path until the end.

Animating activity diagram P. 387


4. When the black ball reaches a shape, the shape will turn into purple.

Reviewing the animation

Animating activity diagram P. 388


Export animation to adobe flash
Exporting flash movie from animacian
1. To launch Animacian, select Tools > Animacian from the main menu.

Open Animacian through the main menu

NOTE: Animacian can also be started by 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.

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.

Select paths to animate

Export animation to Adobe Flash P. 389


3. Click the Export to Flash... button.

Click the Export to Flash... button

This shows the Export to Flash dialog box.

The Export to Flash dialog box

Here is a description of the Export to Flash dialog box.


Region Description

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

Dimension The width and height of viewing region of Flash.

Available Available paths that can be selected to export to Flash movie for animation.

Selected Selected paths to export to Flash movie for animation.

Description of the Export to Flash dialog box

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.

Select the Flash movie dimension

6. Click Export button.

Click the Export button

Export animation to Adobe Flash P. 390


7. Open the HTML file in the web browser to play the movie.

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.

Navigation in exported movie


You can control the flow of movie by clicking on the buttons at the bottom of the movie or by pressing shortcut keys. Here is a list of buttons.

Button Description

Backward. Move one shape backward in the flow.

Pause. Temporary stop playing the movie. Can play again by pressing the
button.

Play. Play or continue to play the movie content.

Forward. Advance to the next shape in the flow.

Stop. Terminate the movie.

Buttons in exporting Flash movie

You can also click on the slider to move the animation to a desired position.

Navigate in the Flash movie by dragging slider

Export animation to Adobe Flash P. 391


Depending another project
Depending another project enables you to reference to another project, and use its model elements in developing your own project. You can organize
your model elements in a more disciplined approach by having one project per library project. This also helps you to "slim up" projects through breaking
down a project into smaller pieces. Moreover, you can reference to other projects, and create an overview project for them.
To reference to another project:
1. Right click on the background of any of the following panes and select Manage Dependent Project... from the pop-up menu.
• Diagram Navigator
• Model Explorer
• Logical View

Right click on Diagram Navigator and


select Manage dependent project...

2. In the Manage Dependent Projects dialog box, click Add button.

Click Add button

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.

Depending Another Project P. 392


Referencing other projects' model elements
Once a dependent project has been established, you can develop your model using model elements in dependent project. To do this:
1. In Model Explorer, click on the drop-down menu at the top of the pane and select the project that contains the model elements you want to use.

Select a dependent project

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).

Drag model elements from dependent project

NOTE: Alternatively, you can right click on the model elements and select Create View in Active Diagram from the pop-up menu.

Indicating dependent elements on diagram


In order to know which shape(s) on a diagram comes from a dependent project, you can enable to model element indicators. Click on the Show Model
Element Indicators button at the top of diagram toolbar.

To show model element indicators

After that, you can see the indicator, which is a small arrow, appear at the shapes that are referencing a dependent project.

Model element indicator appears

Referencing other projects' model elements P. 393


Mirroring model element
Due to views of dependent model elements are read-only, you cannot add shapes in it. This may be a problem when you want to use dependent
packages in your project, and to add model elements such as classes in it. To overcome this problem, you can create a mirror of container-typed
dependent model element. By mirroring, a dependent element is localized partially by keeping a mirrored copy in your project which echoes the
element in dependent project. The mirrored copy can be accessed in Model Explorer that lists model elements in current project, but not editable.
To create a mirror from a container-typed dependent model element (e.g. package, pools/lanes), right click on the element in Model Explorer and
select Create Mirror Model Element from pop-up menu.

Mirror a dependent class

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.

Mirroring model element P. 394


Viewing dependent diagrams
Sometimes, you may want to take a look at the design created in dependent project to make yourself familiar with it. Instead of the traditional way of
opening a project, you can read diagrams of dependent diagrams by scrolling down to the bottom of diagram navigator, expanding the dependent
project node and double clicking on a diagram node to open it. Note that the diagram is read-only.

Reading diagram in dependent project

Viewing dependent diagrams P. 395


Duplicating element from linked project
When we have added a dependent project, we say we are referencing that project. By reference, it&rsquo;s like a linkage that points to the actual data
stored in dependent project. Those elements borrowed from dependent project are not editable by current project.
Sometimes, you need the elements created in another project, not to appear as form of references, but to make it become your own data. You will
need to duplicate element from linked project. To duplicate a model element:
1. Open the Model Explorer.
2. Right click on the element you want to duplicate ands elect Duplicate to Current Project from the popup menu.

Duplicate a model element

The duplicated element can be found in Model Explorer, under current project.

Duplicated element appear in model explorer

Duplicating element from linked project P. 396


What is nickname?
We all have a name, and we may have multiple names such as nicknames or names in other languages. This is the same for your VP-UML project
content. While we have applied certain language in naming and documenting model elements, we may have the need to model with another language
to satisfy the readers of model. The nickname feature is designed to let you define multiple language sets for a model. Further to the definition of
nickname, you also can make use of the translate function to translate your work into another language.
One model element can have one Original name and multiple nicknames, and the same for documentation. With nickname, you can define and
view different names without affecting the original name of model elements. You can disable the effect of nickname anytime by switching to Original
nickname. Features that related to code generation will always use Original name, i.e. changing Class's name in other nicknames will not affect the
generated code.

The following image shows the diagram in original name:

Original name

After you define a nickname and rename model element, the diagram will be switched to the selected nickname.

Select a nickname

What is nickname? P. 397


Multi-national team
If you are working in a team and your members using different languages, you can define model elements name and documentation in multiple
languages. Each member can choose their own language for modeling or view diagrams. The following example demonstrates the Business Process
Diagram in English and French:

Original version of a business process

You can create a French nickname and rename the model elements:

Chinese version of a business process

Now you can switch between English (Original) and Traditional Chinese anytime, or even creating more nicknames.

What is nickname? P. 398


Increase readability of entity relationship diagram
The name of Entity will be used to generate SQL, but Database Management System (DBMS) has many constraints on the name of Entity, Column,
etc, and each DBMS are different. These constraints include the length of the name, reserved keywords, special characters, etc. They restricted the
database designer to create an Entity Relationship Diagram (ERD) with meaningful names. With nickname, you can freely change any names to
create a high readability ERD without affecting the generated SQL. The following diagram display ERD in nickname but generate SQL in original name:

Generate SQL with original name

What is nickname? P. 399


Configure nickname
You can add a nickname through the nickname drop down menu that appears in toolbar, or through the appropriate menu under the View menu in
menu bar. By adding a nickname, you can start editing the names and documentations of model elements under the new nickname.

Overview of Configure Nickname dialog box

An overview of Configure Nickname dialog box

No. Name Description

1 Original user The language (e.g. English) of the Original nickname The selection only affects the outcome of translation.
language

2 Nickname list List all the nicknames.

3 Add Click to add a nickname with a name.

4 Add user language Click to add a nickname with selected language.

5 Rename Click to rename a chosen nickname.

6 Remove Click to delete a chosen nickname.

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.

Description of Overview dialog box

Adding nickname

Configure nickname P. 400


1. Click on the drop down menu of Modeling Tools on the toolbar and select Nicknames > Configure Nicknames....

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.

Two nicknames are added

Renaming nickname

Configure nickname P. 401


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 rename. Click Rename.

NOTE: You are not allowed to rename the original nickname.

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

NOTE: You are not allowed to remove the original nickname.

Configure nickname P. 402


Specifying user language for the nickname
There must be an original nickname in every project, namely Original, representing the most standard version of language of project. You can specify
the language for the original nickname, such as German. The language you have set affects the outcome of translation.

Select original user language

To add a nickname in specific language, click on the Add User Language... button and select a language.

Add a user language

Configure nickname P. 403


Using nickname
Once you have defined a nickname, you can start updating your model by entering the new names and documentations of model elements.

Start updating elements' nickname


1. From the application toolbar, select the nickname you need to work with.

Select a nickname to work with

2. Start renaming model elements and updating their documentation. The changes you make will only be applied to the selected nickname.

Update the name and documentation of elements under a nickname

Switching between nicknames


The names and documentations of model elements are language specific. This means that, the change you make applies only to a specific nickname.
Once you have switched to another nickname, the names and documentations of model elements will be updated to show the definition under the new
nickname.
To switch between nicknames, select the nickname to switch to from the drop down menu of nickname in application toolbar.

Switch nickname

Using nickname P. 404


Translation
Further to the definition of nickname, you also can make use of the translate function to translate your work into another language. This is particularly
useful when you want to add a new nickname for another different language, without entering all names and documentations from the beginning.
To perform a translation:
1. Right click on the shape you want to perform translation and select Translate... from the pop-up menu.

Perform translation on a shape

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.

A translated business task

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.

The overview of Visual Diff dialog box

Various comparison strategies


A comparison strategy determines how two diagrams will be compared. Each strategy is used for its own specific purpose. You can select the
appropriate strategy that suits your case most. The following is the description of strategies:

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.

Description of comparison strategies

Comparing view only, model element only, or both


Comparison is divided into view, model element and both of them. The selected option from the drop-down menu of Compare determines the display
for comparison. By selecting View, the differences in view settings, such as the coordination of shapes, will be considered as changes. By selecting
Model Element, the differences in model element level, such as their names, will be considered as changes. By selecting All, the differences in both
view settings and model element level are displayed.

What is visual diff? P. 407


The following screenshot displays both view and model element differences:

Compare All

The result of selecting View is shown as follows:

Compare View

What is visual diff? P. 408


The result of selecting Model Element is shown as follows:

Compare Model Element

What is visual diff? P. 409


Comparing from the left to the right and vice versa
Comparisons are made between two diagrams, which are put on the left and the right hand side in the Visual Diff dialog box respectively. By default,
comparison is based on left hand side, which means, if a shape does not exist on the left hand side but on the right hand side, the shape will be
considered as newly added in the result pane. The base can be swapped from the right to the left, and vice versa. By doing so, the absence of shape
on the left hand side will result in a report of deleted shape.

Comparing diagrams with right hand side as base

What is visual diff? P. 410


The result of left hand side as base is shown below. The deleted model element is regarded as an addition (it indicates as New).

Comparing diagrams with left hand side as base

Exporting a report of differences


A report of the current comparing diagrams can be saved in your computer as PDF. Click Export PDF... button on the bottom left corner of the dialog
box. Select a directory for storing in Export PDF dialog box and then click Save button.

Click Export PDF... button

What is visual diff? P. 411


Comparing as-is and to-be business process diagram
In this page, two Business Process Diagrams are compared: one for modeling the As-is Process and another for modeling the To-be Process. The
features of Visual Diff are applied in order to find the differences between them.

Comparing as-is and to-be business process diagram P. 412


1. In As-Is Process diagram, select Tools > Visual Diff... from the main menu.

Launch Visual Diff through the main menu

NOTE: Alternatively, you may start Visual Diff as follows:


• Right click on diagram background and select Utilities > Visual Diff... from the pop-up menu.
• Click the drop-down menu of Modeling Tools and select Visual Diff... on the toolbar.

The overview of Visual Diff dialog box:

Comparing as-is and to-be business process diagram P. 413


2. In Visual Diff dialog box, the left hand side window shows the currently opened diagram by default. You may remain it unchanged; otherwise
uncheck Use Working Project on the left hand side if you want to select a diagram in other projects to compare with. Click ... button in Project
to select the directory of other projects. Similarly, check/ uncheck Use Working Project on the right hand side window.

Check Use Working Project

3. Select the To-be Process diagram to compare with from the drop-down menu of Diagram.

Select a diagram for comparison

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.

Two diagrams are selected

4. Select an option in Strategy.

Select a strategy

Comparing as-is and to-be business process diagram P. 414


5. Select an option in Compare.

Select a compare

6. Choose an option in Base.

Choose a base

7. Select an option in Filter.

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.

Select a node on the result pane

Comparing as-is and to-be business process diagram P. 415


Comparing logical and physical ERD
Entity relationship diagram (ERD) represents a detailed picture of the entities needed for a business. In forward engineering, ERD will be transformed
into a relational database eventually. There are at least two types of ERD &ndash; Logical and Physical. They are used in different stages of
development, and are inter-related.
Logical ERD models information gathered from business requirements. Entities and relationships modeled in such ERD are defined around the
business's need. The need of satisfying the database design is not considered yet.
Physical ERD represents the actual design of database. It deals with conversion from logical design into a schema level design that will be transformed
into relational database. When modeling a physical ERD, Logical ERD is treated as base, refinement occurs by defining primary keys, foreign keys and
constraints. Sometimes, relationships need to be resolved by introducing additional tables, like a Linked table for a many to many relationship.
Since physical ERD and logical ERD represent the business requirement and database schema respectively, comparing physical and logical ERD
helps to find out the differences between them in order to confirm the database is exactly following the initial business requirements regardless of the
changes.
Two ERDs are compared: one for modeling the Logical Model and another one for modeling the Physical Model. With the features of Visual Diff, the
differences between Logical and Physical ERD can be found easily.

Comparing logical and physical ERD P. 416


1. In Logical ERD diagram, select Tools > Visual Diff... from the main menu.

Launch Visual Diff through the main menu

NOTE: Alternatively, you can start Visual Diff as follows:


• Right click on diagram background and select Utilities > Visual Diff... from the pop-up menu.
• Click the drop-down menu of Modeling Tools and select Visual Diff... on the toolbar.

The overview of Visual Diff dialog box:

Comparing logical and physical ERD P. 417


2. In Visual Diff dialog box, the left hand side window shows the currently opened diagram by default. You may remain it unchanged; otherwise
uncheck Use Working Project on the left hand side if you want to select a diagram in other projects to compare with. Click ... button in Project
to select the directory of other projects. Similarly, check/ uncheck Use Working Project on the right hand side window.

Select Use Working Project

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.

Two diagrams are selected

4. Select an option in Strategy.

Select a strategy

Comparing logical and physical ERD P. 418


5. Select an option in Compare.

Select a compare

6. Choose an option in Base.

Select a base

7. Select an option in Filter.

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.

Select a node in the result pane

Comparing logical and physical ERD P. 419


Defining design pattern
In VP-UML, design pattern is a part of diagram that can be used in many different diagrams, thus form a pattern. Design pattern typically shows the
shapes and more importantly, the relationships between the shapes. You can define and reuse design pattern in your project, across projects, or share
with your team members. You can define and apply design patterns on any kinds of diagram.
In order to apply a pattern, you need to define it first, and save it as a pattern file ready for being used. To define a pattern, draw the pattern on
diagram. After that, you can save the pattern, which is the diagram content as a pattern file.

Defining design pattern


1. In the diagram where the pattern was drew, select the shapes to be involved in pattern.
2. Right click on any selected shapes, select Define Design Pattern... from the popup menu.

Defining design pattern

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.

Naming design pattern

Defining design pattern P. 420


Applying design pattern
You can apply a previously defined design pattern into your diagram, and modify it to make it fit into your design. To apply a design pattern:
1. Open an existing diagram where you want to apply a design pattern or create a new diagram.
2. Right click on diagram, select Utilities > Apply Design Pattern... from the pop-up menu.

Apply 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

Applying design pattern P. 421


4. For searching a specify shape on the defined pattern, select the shape from the drop-down menu of Diagram Element to filter the list.

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.

Applying design pattern P. 422


Synchronize design pattern with teamwork server
Teamwork server can synchronize design patterns defined and saved to workspace, you can then share the design patterns with your team members.
This feature is available to Visual Paradigm Teamwork Server, Subversion, CVS and Perforce.

Synchronize local design pattern to server


1. Click Team Collaboration > Open Teamwork Client on toolbar, or select Tools > Teamwork > Open Teamwork Client... from the main
menu.
2. Login to the teamwork server.
3. In the Teamwork Client dialog box, select Repository > Synchronize Design Pattern to Server from the menu.

Synchronize Design Pattern to Server

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

Synchronize design pattern from server


1. Start VP-UML with another user and use a different workspace.
2. Create a diagram.
3. Right click on the diagram's background, select Utilities > Apply Design Pattern... from the pop-up menu.
4. After you open the Teamwork Client dialog box, select Repository > Synchronize Design Pattern to Server.

Synchronize Design Pattern to Server

Synchronize design pattern with teamwork server P. 423


5. When the Pattern Synchronization dialog box pops out, it displays that your pattern is available for update from teamwork server. Click OK
button and the pattern will be updated from teamwork server to workspace.

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.

Apply design pattern again

Synchronize design pattern with teamwork server P. 424


Model transitor for shape
You can use different diagrams for modeling different phrases of development, such as a diagram for modeling the current system, and another
diagram for modeling to system to be implemented. In order to trace the evolution of model elements across diagrams, you can make use of model
transitor. Model transitor enables you to establish transit relationship between shapes. With the transition relationship, you can trace between shapes
across diagrams.

Adding a transition between shapes


1. Right click on the shape you want to add a transition. It can be the source or target shape within the transition to add.

Right clicking on a class

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.

Select shapes to transit to

Model transitor for shape P. 425


Navigating transited shape
Once a transition is added between two shapes, you can navigate between them. There are two methods to navigate to a transited shape. The first
way is to go through the transitor popup menu of a shape. Right click on a shape and select Related Elements > Transit From/To from the popup
menu, then the shape to navigate to.

Navigate to a transited shape through the popup menu

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.

Navigate to a transited shape through the resource centric interface

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.

De-select shapes to withdraw from transition

Model transitor for shape P. 426


Model transitor for diagram (diagram transitor)
You can use different diagrams for modeling different phrases of development, such as a diagram for modeling the current system, and another
diagram for modeling to system to be implemented. Sometimes, diagrams across phrases are similar, but little variation. Model transitor enables you
to duplicate a diagram with transition added in between. You can then continue modeling in the new diagram by using the original diagram's content as
base.

Transiting to a new diagram


1. Right click on the background of diagram that you want to transit from. Select Utilities > Transit to New Diagram... from the pop-up menu.

To transit to a new diagram

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.

Selecting a model for storing the new diagram

3. You can then start editing the new diagram.

Editing transited diagram

Model transitor for diagram P. 427


Navigating transited shape
By adding a transition between diagrams, transitions are automatically added between shapes in the two diagrams. With the transition between
shapes, you can navigate between them. There are two methods to navigate to a transited shape. The first way is to go through the transitor popup
menu of a shape. Right click on a shape and select Related Elements > Transit From/To from the popup menu, then the shape to navigate to.

Navigate to a transited shape through the pop-up menu

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.

Navigate to a transited shape through the resource centric interface

Model transitor for diagram P. 428


Applying stereotype to model element
A stereotype defines how a model element may be extended, and enables the use of platform or domain specific terminology or notation in place of, or
in addition to, the ones used for the extended metaclass. In VP-UML, you can apply one or more stereotypes to model elements, and decide whether
or not to visualize the stereotype or tagged values in views. To apply stereotype to model element:
1. Right click on the model element, or the view of the model element that you want to apply stereotype to. Select Stereotypes from pop-up menu.

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.

Stereotype Enum is selected

NOTE: You can also double click on a stereotype to apply it.

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.

Stereotype Enum is applied to a class

Apply Stereotype to Model Element P. 429


Robustness analysis icon
Robustness analysis helps to find out the relationships between actor, boundary, control and entity objects.

Robustness analysis icons

To draw a robustness analysis diagram with robust analysis symbols:


1. Create a class in diagram.
2. Depending on the type of robustness analysis symbol you want to create, apply either boundary, control and entity stereotype to the class.

To apply entity stereotype to User class

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.

Presenting a shape as stereotype icon


You can specify icon for a stereotype (Read the next chapter for details). When a stereotype is applied to a model element, you can let the stereotype
icon show above the name of model element, which is the default presentation, or to make the model element show as the icon. To present a shape as
stereotype icon, right click on the shape and select Presentation Options > Stereotype Icon from the popup menu.

Different presentations of a model element with a stereotype that has icon defined

Showing or hiding stereotype


By default, applied stereotypes are shown within a shape. Yet, it is up to you whether to show or hide them. Furthermore, you can choose not to
display the stereotypes, but to display only their tagged values.
To update the visibility of stereotypes, right click on the background of diagram where the shapes exist. Select/De-select Presentation Options >
Show Stereotypes from the popup menu.

A use case with stereotype names shown and hidden

Apply Stereotype to Model Element P. 430


Configure stereotypes
You can configure stereotypes, not just to create and name stereotypes for specific model element types, but also to format stereotypes like to set their
colors, line formatting and font, and to define their tagged values. By configuring stereotypes, domain specific stereotype set can be built.
To configure stereotypes:
1. Select Tools > Configure Stereotypes... from the main menu.

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.

Select class to edit its stereotypes

4. You may now perform any of the following action:


• If you want to edit an existing stereotype, select the stereotype and click Edit....
• If you want to add a stereotype, click Add....
• If you want to remove a stereotype, select the stereotype and click Remove.

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.

An overview of Configure Stereotypes dialog box

Configure stereotypes P. 431


An overview of Configure Stereotypes dialog box

No. Name Description

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.

3 Stereotypes A list of stereotypes of the selected model element type.

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 .

5 Duplicate Click to duplicate the stereotype selected in Stereotype pane.

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.

7 Export Click to export stereotype configuration to an XML file.

8 Add Click this to add a stereotype for the selected type of model element.

9 Edit Click to edit the selected stereotype.

10 Remove Click to delete the selected stereotype.

11 OK Click to apply the configuration and close the dialog.

12 Cancel Click to discard the changes (if any) and close the dialog box.

13 Help Click to open the Help contents.

Description of Configure Stereotypes dialog box

Configure stereotypes P. 432


Editing stereotype
By adding or editing a stereotype, you can specify its icon and adjust its fill, line and font style in the General page within the Stereotype
Specification.

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.

Defining tagged values for stereotypes


A stereotype may have properties, which may be referred to as tag definitions. When a stereotype is applied to a model element, the values of the
properties may be referred to as tagged values.
You can define tagged values for stereotypes. By doing so, when you apply the stereotype with tagged values defined to a model element, you can fill
in the values for the model element.
1. Select Tools > Configure Stereotypes... from the main menu.
2. In the Configure Stereotypes dialog box, select the stereotype that you want to define tagged value and click Edit. If you want to add a new
stereotype, select the base model type and click Add...
3. In the Stereotype Specification dialog box, open the Tagged Value Definitions tab.
4. Click Add. Select the type of tagged value to define. The type of tagged value limits the type of content user can enter for a tag.

Adding a tag

Tag type Description

Text The most common and general type of tagged value that consists of words.

Multi-line Text The value of tag is a text in multiple lines.

Model element The value of tag is a model element in project.

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.

Integer The value of tag must be a real number.

Floating point The value of tag must be a number that consists of one or more digits.
number

Type of tags

Configure stereotypes P. 433


5. Double click the name cell and enter the name of tag. Repeat step 4 and 5 to add all tagged values for this stereotype.

Tags defined for an API stereotype

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.

Configure stereotypes P. 434


Shortcut of creating stereotyped model element
One of the ways of creating a shape is by selecting the element type in diagram toolbar, and clicking on diagram to create a shape of that type. If then
you want to apply a stereotype to that model element, you will open the specification dialog box and make a stereotype selection. These steps can be
simplified by adding a shortcut in diagram toolbar, for creating a type of model element with specific stereotype pre-set. To do so:
1. In any diagram, click on the double down arrow button at the top of diagram toolbar, then select Configure Buttons... from the popup menu.

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.

Configure buttons in diagram toolbar

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.

Create a stereotyped shape

Shortcut of creating stereotyped model element P. 435


Creating a profile
A UML profile provides a generic extension mechanism for customizing UML model elements for different purposes. Profiles are defined using
stereotypes and tagged values definition for specific types of model elements. You can tailor UML meta model for different domains and platforms by
creating and developing a profile.
1. In Model Explorer, right click on the project root node and select Create Profile from the pop-up menu.

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.

Naming the profile

3. Repeat step 1 and 2 to create all the profiles.

All profiles are created

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.

Creating a profile P. 436


Drawing a profile diagram
A profile diagram enables you to create domain and platform specific stereotypes and define the relationships between them. You can create
stereotypes by drawing stereotype shapes, and relate them with composition or generalization through the resource-centric interface. You can also
define and visualize tagged values of stereotypes.

Creating a profile diagram


To create a profile diagram:
1. Right click on a profile in Model Explorer and select Sub Diagrams > New Profile Diagram from the pop-up menu.

Create a profile diagram

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.

Naming a profile diagram

Drawing a stereotype
To draw a stereotype in profile diagram:
1. Select Stereotype in diagram toolbar.

Selecting Stereotype
in diagram toolbar

2. Click on the diagram to create a stereotype.

Drawing a profile diagram P. 437


3. In the Select Base Type of Stereotype dialog box, select the base type of stereotype from the model type tree. A base type is the type of
model element that the stereotype will extend.

Selecting a base type

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.

Defining tagged values for stereotypes


A stereotype may have properties, which may be referred to as tag definitions. When a stereotype is applied to a model element, the values of the
properties may be referred to as tagged values.
You can define tagged values for a stereotypes. By doing so, when you apply the stereotype with tagged values defined to a model element, you can
fill in the values for the model element.
1. Right click on a stereotype shape and select Open Specification... from the popup menu.
2. In the Stereotype Specification dialog box, open the Tagged Value Definitions tab.

Drawing a profile diagram P. 438


3. Click Add. Select the type of tagged value to define. The type of tagged value limits the type of content user can enter for a tag.

To add a tag

Tag type Description

Text The most common and general type of tagged value that consists of words.

Multi-line Text The value of tag is a text in multiple lines.

Model element The value of tag is a model element in project.

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.

Integer The value of tag must be a real number.

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.

Tags defined for an Vehicle 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.

Stereotypes with tagged values defined

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.

Drawing a profile diagram P. 439


Composition
A composition relationship shows a "part of" relationship between stereotypes. The composite stereotype has responsibility for the existence and
storage of the composed stereotype.

Composition between stereotypes

To create a composed stereotype:


1. Move the mosue pointer over a stereotype. Press on the resource icon Composition > Stereotype from the popup menu.

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

To create a specific stereotype from a general stereotype:


1. Move the mosue pointer over a stereotype. Press on the resource icon Generalization > Stereotype from the popup menu.

To create 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.

Drawing a profile diagram P. 440


Creating diagrams
You can create diagrams to help visualize what you did, what you are doing and what you need to do on your target system or application. There are
different types of diagrams to fulfill different needs, categorized as UML diagrams, requirements capturing, database modeling, business process
modeling and others. Here are the three possible ways of creating a diagram:
• Through toolbar
• Through the File menu
• Through the pop-up menu on Diagram Navigator
To create a diagram through toolbar:
Select the icon of a specified diagram under diagram category on the toolbar.

Select UML icon on the toolbar

To create a diagram through File menu:

Creating Diagrams P. 441


1. Select File > New Diagram > New Diagram... from the main menu.

Select New Diagram... from the main menu

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.

New Diagram dialog box

To create diagrams through the pop-up menu on Diagram Navigator:

Creating Diagrams P. 442


Right click on a specified diagram type node on Diagram Navigator and select the specified new diagram type from the pop-up menu.

Select New Class Diagram from the


pop-up menu on Diagram Navigator

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.

Click an actor on the diagram pane

For defining a specific shape size, drag a specific boundary with the mouse after clicking a diagram element from the diagram toolbar.

Drag a specific boundary with the mouse

Creating Diagrams P. 443


Alternatively, a diagram element can be created by dragging the diagram element and then dropping it on the diagram pane.

Drag and drop to create a shape

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.

Create a shape through the pop-up menu of diagram

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.

An invalid connection is created

If the connection is valid, a blue rectangle surrounding the destination shape can be seen.

A valid connection is created

Moreover, connectors can be created through resource icons:

Creating Diagrams P. 444


Move the mouse over the source shape, press one of its resource icons and drag it to the destination shape.

Press a resource icon to connect shapes

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

Creating turning point on connector


A turning point is a point on a connector where a bending take place. To create a turning point on an existing connector, press on the connector and
drag to bend the connector.

Create turning point on existing connector

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.

Create turning points when creating shape by dragging a resource

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.

Create turning points when creating shape by clicking a resource

Creating Diagrams P. 445


Resource-centric interface
Visual Paradigm is the first vendor to introduce the resource centric diagramming interface. The resource centric interface greatly improves the
efficiency of modeling. You don't have to traverse between the toolbar and the diagram to create diagram elements, make connections and modify the
diagrams. The resource centric interface can make sure the modeler is able to create a diagram with correct syntax more quickly.
There are tree types of resource icons:
• Connection Resource
• Manipulation Resource
• Branching Resource

Connection resource
It is designed for creating elements and making connections.

Create association with connecting a new or existing use case

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.

Fit size through manipulation resource

Branching resource
Branching Resource helps you to create decision structure in diagram.

Create decision structure through branching resource

Drawing freehand shapes


Freehand shape is a kind of general graphic shapes. Pen shapes, pencil shapes, and some regular shapes like circle, rectangle and arrow are
available. Freehand shape can be used for annotating diagram. For example, you can use freehand shapes to emphasize some shapes.

Creating Diagrams P. 446


A specific shape can be highlighted with a pencil shape.

Pencil

An outstanding text can be shown with word art.

Word Art

A freehand shape style can be formatted in order to address your information.

Styled freehand shapes

Changing package header


You can specify the parent package of any diagram through Package Header.

Creating Diagrams P. 447


Package header when diagram created
When a diagram is created, the package header will be unfolded as it allows you to specify the parent package of the diagram. Specify the package by
entering the fully qualifier name of the package.

Specify parent package in package header

After entering the name of parent package, you will find that the diagram name is the same as the name of parent package.

Diagram name will be same as fully qualify 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.

Double click on the parent package

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.

Creating Diagrams P. 448


A package header can be either shown or hidden through the pop-up menu of diagram. Right click on the diagram background and select
Presentation Options > Show Package Headerfrom the pop-up menu.

Show/hide package header

Justifying shape name


In Visual Paradigm, a shape name is aligned center horizontally, and top or middle vertically, depending on the characteristic of shapes. However, the
shape name can be realigned. Even if a language, such as Modern Hebrew, that is written from the right to the left can be displayed on a shape clearly.

Adjusting shape name's position

Creating Diagrams P. 449


1. Right click on the diagram background, select Presentation Options > Model Element Name Alignment and then select a specific alignment
option from the pop-up menu.

Select an alignment option from the pop-up menu

2. As a result, all shapes' name in the whole diagram will turn into the alignment option you set previously.

All shapes' names turn into middle right

Apart from the whole diagram setting, a specific shape can also be set:

Creating Diagrams P. 450


1. Right click on a shape, select Presentation Options > Model Element Name Alignment and then select a specific alignment option from the
pop-up menu.

Select an alignment option from the pop-up menu

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.

Check an alignment option in the Options dialog box

Creating Diagrams P. 451


Exceptions
Although most shape' name can be justified, some are exceptional. Two main kinds of shapes that their name cannot be justified are introduced as
follows:
On one hand, shapes neither with floating name label (freely movable) nor with a label outside the shape can be justified. Actor, Initial Pseudo Node
and BP Start Events are examples of this kind of shape.

Floating name label

On the other hand, the names of container shapes are not available for positioning. Since their &ldquo;bodies&rdquo; 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

Enabling and disabling minimum shape size


Since all shapes have their own default minimum size, users are not allowed to resize them to smaller than the minimum size. The default setting
helps to ensure those compact shapes are clear enough to be seen on a diagram under normal circumstance. The minimum size of a shape can be
determined by pressing its fit size button.

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.

Uncheck Enable minimum size

3. After that, you can resize a shape to the size as small as you want.

Creating Diagrams P. 452


4. Furthermore, select other shapes and select an option from the drop-down menu of resource icon Same Width.

Select an option from the drop-down menu of resource icons

5. As a result, other shapes will turn into the same size as the shape you have done previously.

All shapes are turned into the same small size

Undo and redo


During the process of editing a diagram, you may make some careless mistakes, such as accidentally deleting a shape. You can use the Undo
function to cancel the previous action. On the contrary, you may re-perform the action through the Redo function. Note that the undo/redo feature in
VP-UML is diagram based.

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.

Creating Diagrams P. 453


• Press Ctrl-Y.

Showing name for undo and redo action


It's hard for us to remember all actions we have done previously. By VP-UML, we can recall the actions we have done before.
You can find an action name of undo/ redo by clicking Edit from the main menu.

Menu shows Undo/Redo name

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.

Toolbar button's tooltip shows undo action

Creating Diagrams P. 454


Resource centric interface
Visual Paradigm is the first vendor to introduce the resource centric diagramming interface. The resource centric interface greatly improves the
efficiency of modeling. It can make sure the modeler is able to create a diagram with correct syntax more quickly. The utmost importance thing is
that you don't have to go back and forth between the toolbar and the diagrams for creating diagram elements, making connections and modifying the
diagrams.

Resource centric interface on action

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.

Creating shapes through resource centric interface


Instead of clicking shapes one by one from the diagram toolbar, you can create another shape from an existing shape on the diagram.
1. Move the mouse on a shape and select a resource icon out of resource centric interface.

Create a use case with resource centric interface

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.

Release the mouse to create use case

Connecting shapes through resource centric interface


For relating two shapes together, you have to link a shape to another. With resource centric interface, you can not only link them up, but also select an
appropriate relationship for them.
1. Select two shapes from the diagram toolbar and drag them on the diagram individually. Move the mouse on one shape and select a resource
icon out of resource centric interface.

Create Use Case with Association

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

Resource Centric Interface P. 455


Using quick connect
With quick connect, you are able to search the preferred shape and connect to it on the diagram accurately and quickly.
1. After creating some shapes on diagram, move the mouse on a shape and click a resource icon out of resource centric interface. The Quick
Connect dialog box will be shown subsequently.

Quick Connect dialog box

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.

Use Case is spotlighted

4. Confirm the selection, press Enter. The two shapes will be linked automatically.

An actor is linked with a use case

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.

Managing transition of shapes


Model transitor enables you to trace between model elements across different phrases of development. Once a transition is created between two
shapes, you can navigate between them through the resource centric interface.

Resource Centric Interface P. 456


Move the mouse on a shape and select Model Transitor> Transit To and then select the shape's name you would like to transit to/from from the pop-
up menu. As a result, the vision will be diverted to the selected shape after transition is selected. Thereafter, you can transit to/ from between these two
shapes.

Transit from one shape to another

NOTE: Transition does apply not only on two shapes on the same diagram, but also two shapes in different diagrams.

Adding and opening reference


For providing extra information to shapes, you can insert both internal and external resources, such as a shape, a diagram, a file, a URL through the
resource centric interface. After editing references, they can be opened throughout the resource centric interface.
1. Move the mouse on a shape that you would like to insert references for, press resource icon Resources at the bottom left corner and select a
reference option from the pop-up menu.

Select Add File...


from the pop-up menu

Resource Centric Interface P. 457


2. Insert the corresponding resource in References tab of your shape's specification dialog box.

Insert a file in Class Specification dialog box

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.

The newly created reference

Splitting connection by shape


Resource centric supports some connectors (e.g. Control Flow in Activity Diagram) with splitting the connector by adding another shape.
1. Move the mouse on the connector between two shapes and select a split resource icon out of resource centric interface.

Select a split resource icon

2. As a result, an extra shape is inserted between two existing shapes.

Control Flow is split by Decision Node

NOTE: There is an orange asterisk on the split resource icon.

Resource Centric Interface P. 458


Creating structure
Resource centric interface supports some models (e.g. Action in Activity Diagram) with creating a structure of models. Instead of creating shapes one
by one, branch resource icon helps speed up the shape creation process; you thereby can create several shapes simultaneously.
1. Move the mouse on a shape and select a branch resource icon out of resource centric interface.

Select Create Branch with Decision


Node on resource centric interface

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.

Create Decision Node and Actions

NOTE: There is an orange asterisk on the branch resource icon.

Group selection resource


When a great amount of shapes are displayed on the diagram disorderly, resource centric interface can support alignment and grouping after selecting
several shapes.
1. Select several shapes on diagram.
2. Move the mouse on the last selected shapes and group selection resources will be shown instantly.

Group Selection Resources are shown

3. Press the reversed triangle of Align Top and select an alignment option from the drop-down menu.

Select Align Top from the drop-down menu

Resource Centric Interface P. 459


Tagged values
In VP-UML, tagged values are properties defined by user and can be added to a model element. VP-UML supports either defined tagged values
in stereotype or tagged values without stereotype. In UML 1.1, stereotypes and tagged values were used as string-based extensions that could be
attached to UML model elements. In UML 2.x, stereotypes and tagged values will be defined in Profile that can provide more structure and precision to
the definition.

Adding user-defined tags


1. Right click on the selected shape and select Open Specification... from the pop-up menu.

Right click to select Open Specification...

2. In Specification dialog box, select Tagged Values tab and click Add button to select an option of value type.

Add an option of value type

Different types of tagged values


Text
Text supports string-based value.
In Specification dialog box, select Tagged Values tab, click Add button and select Text from the pop-up menu. Enter the text in the text field directly.

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.

Add multi-line text

Tagged Values P. 460


2. When Edit Value dialog box pops out, enter the multi-line text. Click OK button to finish editing.

The Edit Value dialog box

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.

Add model element

2. When the Select Model dialog box pops out, check Model and select a model element. Click OK button to confirm.

Select a model element

Integer
Integer supports values with numbers only.

Tagged Values P. 461


In Specification dialog box, select Tagged Values tab, click Add button and select Integer from the pop-up menu. Enter a number in Value.

Add integer

Floating Point Number


Floating Point Number supports values with decimal places.
In Specification dialog box, select Tagged Values tab, click Add button and Floating Point Number from the pop-up menu. Enter a number with
decimal places in Value.

Add floating point number

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.

Add HTML text

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.

Format the HTML text content

Click OK button to finish editing.

Tagged Values P. 462


Editing tagged values
You can enter the user-defined tagged value's name, select its type and enter its value.

Edit name, type and value on user-defined tagged value

The value of stereotype can be edited, however, its name and its type cannot be edited as they are defined in stereotype.

Visualizing tagged values on diagram


Right click on the diagram background and select Presentation Options > Show Tagged Values from the pop-up menu.

Show tagged values

If it is defined, the tagged values will be seen within the shape(s) on the diagram.

Tagged values are shown

Tagged Values P. 463


Spell checking
You will never find it hard to avoid making mistakes in your diagram after using spell checking. It can help you to correct both typing mistakes and
spelling mistakes, however, it is slightly different from other spelling and grammar checking tools you have used before. It doesn't check your whole
diagram automatically, but underlines wrong words with a curve line.

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.

Adding a new word to dictionary


Sometimes, the dictionary cannot recognize the word you type and it doesn't always mean you type an incorrect word . It may be a rare word or a new
word that you create, for example, your company's name. You can simply right click on the wrong word and select Add to dictionary to add a new
word to dictionary. You type this word again next time, it won't be marked as a wrong word.

Adding a new word to dictionary

Changing the language of dictionary


The dictionary usually defaults as American English for spell checking. If you want to change the language of dictionary, you just need to:
1. Click Tools > Options > Spell Checking.
2. For example, you can change from American to British.

Changing the language of dictionary

NOTE: There are a few more languages in dictionary that can be used, such as French and German.

Spell Checking P. 464


More options of spell checking
There are a few more options of spell checking, for example Ignore words with numbers and Ignore Internet and file address. Check the item you
want to be included in spell checking while uncheck the item you don't want to be included.

Checking other options of spell checking

Spell Checking P. 465


Using project management properties
Project management properties are a set pre-defined properties, made for recording additional management-level information for all kinds of project
data (e.g. diagrams, model elements, diagram elements). Here are all the project management properties you can find:

Property name Description

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.

Priority The importance of editing element.

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 .

A list of project management properties

Further to recording project management properties, you can print those properties in report, too.

Editing project management properties


Like all the other specification level properties, project management properties can be edited through the specification dialog box of all diagrams, model
and diagram elements. Select the desired diagram/model element/diagram element. Right click and select Open Specification... from the popup
menu. Under the tab Project Management you can find the properties of the chosen element.

Editing project management properties

Using project management properties P. 466


Project management properties in report generation
Like most other properties, project management properties will be presented in PDF, HTML and Word report, too. Furthermore, you can filter the
elements to present in report by project management properties when editing template.

Editing project management filter in editing report template

Using project management properties P. 467


Configuring project management properties
For each project management property, there are several default values available for selection. For example, values "1.0" and "2.0" can be selected for
property Version. You can edit an existing value, or add additional values to a property by editing the look-ups.
To configure a property:
1. Select Tools > Project Management Look-ups... from the main menu.

To edit project management property look-ups

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

Configuring project management properties loop-up P. 468


RTF documentation
With rich text format (RTF), you can format the text in documentation editor, such as making it bold, italic, or adding tables within the text. In addition to
formatting, RTF supports users to add linkage to another model element, save documentation as template and furthermore reuse the template.

Viewing and editing the documentation of model element


To view or edit the documentation of model element, right click on the model element and select Open Specification... from the pop-up menu.

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.

The overview of documentation editor

RTF documentation P. 469


The toolbar on documentation editor

No. Name Description

1 HTML HTML - Read and edit the real content.


HTML Source - Read and edit the HTML source of content.
Plain Text - Read and edit plain text of content without formatting.

2 Bold Set the highlighted text to bold.

3 Italic Set the highlighted text to italic.

4 Underline Underline the highlighted text.

5 Alignments Set the alignment of highlighted text to the left, the center or the right.

6 Ordered list Add a numbered list.

7 Un-ordered list Add a list with bullet points.

8 Font Select the font family of highlighted text.

9 Font size Select the size of highlighted text.

10 Font color Select the color of highlighted text.

11 Table Add a table.

12 Background Select the background color of highlighted text.


color

13 Clear formats Clear formats of the whole editor to convert the content to plain text.

14 Link Add a hyperlink.

15 Image Add an image.

16 Add Model Insert an existing model element or create a new one.


Element

17 Template Save as Template...: Save the current documentation content as a template.


Manage Template...: Delete the saved template.

18 Print Print the documentation content.

19 Editor pane Enter and start editing the documentation content.

The description of documentation editor

Editing documentation
Saving a template

RTF documentation P. 470


1. The documentation you typed can be saved as template in the documentation editor. Choose Save as template... from the drop-down menu of
Template.

Choose Save as template...

2. In the Input dialog box, enter the template name and click OK button to confirm.

Enter template name

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

2. As a result, the selected template will be shown on the documentation editor.

Adding model element


1. Click Add Model Element button on the editor's toolbar after decided a place for inserting a model element.

Click Add Model


Element button

RTF documentation P. 471


2. In Select Model dialog box, select an existing model element on the list. If you want to modify the selected model element, you can click Open
Specification... button. On the other hand, you can create a new model element by clicking New... button after select a model element on the
list.

Click Open Specification... button

3. Finally, click OK button to confirm.


4. Consequently, the name of inserted model element will be shown on the documentation pane with underline. If you want to preview the inserted
model element, you can right click on its name and select Show View... from the pop-up menu. After the Show View dialog box pops out, you
can preview it in the Preview window. If you want to view the actual model element on the diagram, you can click Go to View button.

Click Show View... from the pop-up menu

Printing documentation
1. After clicking the Print button, the Page Setup dialog box will pop out.

Click Print button

RTF documentation P. 472


2. In Page Setup dialog box, select size and source for paper, check an option under Orientation and enter the inches for the paper margins.

The Page Setup dialog box

3. Click OK button to confirm printing.

RTF documentation P. 473


Voice documentation
In addition to textual description for your model elements, you can record voice documentation, or embbed audio files.

Viewing and editing the documentation of model element


To read or edit the documentation of model element, right click on a model element and select Open Specification... from the pop-up menu to unfold
Specification dialog box.

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.

Click Record... button

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.

Voice documentation P. 474


5. Enter the name for recorded voice clip in the text field of Name.

Name voice clip

6. Click OK button to confirm recording.

Linking voice to documentation


1. Right click on a model element and select Open Specification... from the pop-up menu.
2. In Specification dialog box, choose Manage... button on the bottom left corner of dialog box.

Click Manage... button

3. In the Manage Voice dialog box, click the Add button, and choose either Embedded or Link to File.

Click Add button

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.

Voice documentation P. 475


5. The voice clip can be renamed in the text field of Name.

Rename a voice clip

6. Click OK button to confirm.

Voice documentation P. 476


Applying fill, line and font styles on diagram elements
You can change the diagram element's style in the Formats dialog box. To open the Formats dialog box, right click on the shape and select Styles
and Formatting > Formats... from the pop-up menu.

Select Formats... from the pop-up menu

Formats dialog box

You can change the following settings from the Formats dialog box:
• Changing shapes foreground style
• Changing shapes font style
• Changing shapes background style

Applying fill, line and font styles on diagram elements P. 477


Changing shapes foreground style
In the Format dialog, you can change the foreground style in the Font section. Just 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). If you want to specify a custom color, you can switch to the Custom pane.

Font section

After change the font color, the preview will update automatically.

Changing shapes font style


In the Font section, you can also change the font name, style and size.

Change font style

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.

Applying fill, line and font styles on diagram elements P. 478


Changing shapes background style
You can click on the Background tab to custom the background style.

Change background style

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

Applying fill, line and font styles on diagram elements P. 479


Upon selecting Gradient from the Fill style field you will see the detail pane for formatting a gradient fill color.

Check gradient fill style

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.

Change shape background style result

Applying fill, line and font styles on diagram elements P. 480


Changing connector line style
To change the connector line style through Property pane, select the target connector on the diagram, click the ... button in Foreground row of the
Property pane.

Change connector line style on property pane

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.

Changing connector background style


Upon selecting the Background tab, it allows you to specify the background fill style of the line. Click OK button to apply the settings.

Change connector style result

Applying fill, line and font styles on diagram elements P. 481


Managing and applying styles
VP-UML allows you to define you own style and apply to other shapes by simple steps.

Adding style
To open the style dialog box, Select View > Styles... from the main menu.

Click Styles... from the main menu

In the Style dialog box, click Add... to create and edit a new style.

Style dialog box

Managing and applying styles P. 482


In the Edit Style dialog, you can change the name, foreground line style, font style, background style and arrow style. Click OK button after you finish
editing the setting.

Edit Style dialog box

As a result, the style is created.

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.

Managing and applying styles P. 483


As a result, the shape is changed into the newly created style.

Apply style to selected shape

Managing and applying styles P. 484


Setting line style
Connectors are the lines that connect two shapes. When more shapes are created and more connectors appear, you may find that it is difficult to
handle the straight spaghetti-like connectors. To overcome this problem, VP-UML provides five connector styles to help you handle the connectors,
namely Rectilinear, Oblique, Curve, Round Oblique and Round Rectilinear.

Setting connector line style


To change the line style, right click on the target connector and select Style and Formatting > Connector Style and one of five line style options from
the pop-up menu.

Change line style

As a result, the connector is changed into the selected line style.

Change line style

Line style options

Name Sample

Rectilinear

Setting line style P. 485


Oblique

Curve

Round Oblique

Round
Rectilinear

Setting diagram base line style


Beside the five styles mentioned above, there also have Follow Diagram feature, you don't need to set the connector one by one if you want to
change all connectors in the diagrams which defined as Follow Diagram.
To change the style of all lines on diagram, right click on the diagram background, select Connectors and one of five line style options from the pop-up
menu.

Change diagram line style

Setting line style P. 486


As a result, all lines on the diagram are changed into the selected line style.

All lines are changed into curve

Setting line style P. 487


Setting line jumps options
As more diagram elements on your diagram, more miscellaneous connectors are overlapped with each other. It is impossible to explicate on those
intersections which connector you indicate. The advantage of Line Jumps is making one of the two connectors different to another to indicate that
which connector links with which diagram element clearly. Visual Paradigm for UML (VP-UML) provides four line jumps options to help you to
distinguish connectors. Furthermore, the enhanced feature of line jumps in VP-UML 8.0 enables you to set different size of line jumps.

Setting connector line jumps options


To change the jumps option of a connector, right click on the connector, select Style and Formatting > Connector Style and then select an option
under Line Jumps.

Set Arc

Arc sample

NOTE: The line jumps options are available only when two connectors are overlapped.

Line jump options

Name Sample

Off

Setting line jumps options P. 488


Arc

Gap

Square

The description of 4 line jump options

Setting diagram base line jumps options


In addition to the 4 options mentioned above, Follow Diagram is another choice for altering the connectors. The main feature of Follow Diagram is, all
connectors in the diagrams can be changed simultaneously instead of setting one by one.
Right click on the diagram's background, select Connectors and select an option under Line Jumps from the pop-up menu.

Select Gap from the pop-up menu

Setting line jump for new project


1. Select Tools > Options from the main menu to open the Options dialog box.
2. In the Options dialog box, click the Diagramming page, open the Connector tab and select the Line Jumps style, or select Off to disable it.
At last, click OK to confirm the changes.

Setting different line jump size


You can enlarge the line jump size to make the selected line jump (or all line jumps) on the connector(s) more obvious. Furthermore, the size of line
jump can be customized in either the current diagram or the future diagram. If you only want to set to the connectors of current diagram, right click
on the diagram's background, select Connectors and then a size option from the pop-up menu. Otherwise, if you want to set to the connectors of
future diagram, set it through Options dialog box. Three size are availabe for chooising. Normal is the standard size by default while extra large is the
maximum size.

Setting line jumps options P. 489


Setting line jump size for current diagram
1. Right click on the diagram's background, select Connectors and then a size option from the pop-up menu.

Set Large

2. The line jump(s) on the current diagram will turn into the size you selected.

Arc in large size

Setting line jump size for future diagram


1. Select Tools > Options from the main menu to open the Options dialog box.
2. In the Options dialog box, click Diagramming page and open Connector tab.
3. Under the Line Jumps section, check an line jump option and then select a line jump size option from Line jump size's drop-down menu.

select Large from the drop-down menu

Setting line jumps options P. 490


Setting connector caption orientation
Visual Paradigm supports a number of ways of aligning connector caption, which apply on different modeling preferences. By default, the caption
of a connector is aligned horizontal only, but you also can customize it to Follow Diagram, Horizontal Only, Horizontal or Vertical Only, Follow
Connector Angle, and Follow Connector Angle and Keep Text Up Right. You can either customize it one by one or change all connectors in the
diagram which defined Follow Diagram.

Setting connector caption orientation

Sample class diagram 1

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.

change caption orientation to Follow Connector Angle

Setting connector caption orientation P. 491


Follow Connector Angle sample

Caption orientation options

Name Sample Description

Horizontal Only The caption of connector is aligned horizontally.

Horizontal or Vertical Only The caption of connector is aligned either


horizontally or vertically, according to the connector.

Follow Connector Angle The caption of connector is aligned the diagonal


angles of both shapes.

Follow Connector Angle and Keep Text Up Right The caption of connector is aligned the diagonal
angles of both shapes, but keeps top right.

The description of 4 caption orientation options

Setting connector caption orientation P. 492


Setting diagram base connector caption direction
In addition to the 4 options mentioned above, Follow Diagram is another choice for altering the connector. The main feature of Follow Diagram is, all
connectors in the diagrams can be changed simultaneously instead of setting one by one.

Sample class diagram 2

Right Click on the diagram background, select Connectors and select one out of four options under Caption Orientation from the popup menu.

Change caption orientation by diagram popup menu

Setting connector caption orientation P. 493


Workspace wide
Workspace wide setting affects the new connectors being created in projects created or will be created under the current workspace, including the
opening project. To set, select Tools > Options from the main menu.

Clicking Options... in popup menu

Setting connector caption orientation P. 494


In the Options dialog box, open the Diagramming page, switch to the Connector tab and select the desired way of aligning caption under the
Caption Orientation drop down menu. At last, click OK to confirm the changes.

Selecting Horizontal only in Options dialog box

Setting connector caption orientation P. 495


Format copier
Format is defined as the properties for a shape in terms of fill, line and font. Shapes are formatted for two major reasons: making your project more
attractive and giving emphasis on the meaning of shapes. However, it would be troublesome and time-consuming to repeat the same action when you
need other shapes to have exactly the same format as the previous one you have already done. Format copier can deal with this problem for you. It's
so handy that you can clone the formatting properties from one shape to another or even more.

Copying format to another shape


If you want another shape to have exactly the same formatting properties as the previous one you have done, you can simply:
1. Click on the shape that you want its format to be cloned.
2. Click on the Format Copier button in toolbar.

Click Copier

3. Click the shape you want to format.

Clone the format property from one shape to another

NOTE: You can copy formatting to another type(s) of shape.

Copying format to multiple shapes


If you want the format properties of your previous shape to be cloned to more than one shape, you should:
1. Click on the shape that you want its format to be cloned.
2. Double click the Format Copier button on toolbar.

Double click Copier

Format copier P. 496


3. Click the shape you want to format.

Clone the format property from one to multiple shapes

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.

Format copier P. 497


Automatic diagram layout
VP-UML provides a layout facility for arranging diagram elements in diagrams. Diagram elements do not overlap and the relationship links do not cross
over each another. Different layout styles and configurable options are provided, which allows extremely flexible and sophisticated layouts to be applied
to diagrams.

Automatic layout diagram


There are a few different kinds of layouts: Auto Layout, Orthogonal Layout, Hierarchic Layout, Directed Tree Layout, Balloon Tree Layout,
Compact Tree Layout, Horizontal-Vertical Tree Layout, BBC Compact Circular Layout, BBC Isolated Circular Layout, Single Cycle Circular
Layout, Organic Layout and Smart Organic Layout.

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.

Select Auto Layout

Class diagram (Hierarchy base / factory class diagram)

Automatic Diagram Layout P. 498


Hierarchy base (Factory class diagram)

Class diagram (Navigation base / mediator class diagram)

Automatic Diagram Layout P. 499


Navigation base (Mediator class diagram)

Activity diagram

Automatic Diagram Layout P. 500


Auto Layout of activity diagram

State machine diagram

Automatic Diagram Layout P. 501


Auto layout of state machine diagram

Communication diagram

Auto layout of communication diagram

Other diagrams

Automatic Diagram Layout P. 502


Auto layout of other diagrams

Automatic Diagram Layout P. 503


Orthogonal layout
Shapes are arranged based on the topology-shape-metrics approach in orthogonal layout. It is the best way for users to arrange shapes and
connectors in Class Diagrams. As it is default layout in VP-UML, every time you drag the models from the Model Tree to a diagram, the orthogonal
layout will be applied to arrange the newly created shapes in the Class Diagram.

Automatic Diagram Layout P. 504


Layout Grid Size: the virtual grid size for layout. Each shape will be placed in accordance with its center point lays on a virtual grid point.

Orthogonal Layout setting

Automatic Diagram Layout P. 505


Hierarchic layout
Hierarchic Layout arranges shapes in a flow. It is the best way for users to arrange shapes that have hierarchical relationships, such as generalization
relationships and realization relationships.

Hierarchic Layout

Automatic Diagram Layout P. 506


Min. Layer Distance: the minimal horizontal distance between the shapes.
Min. Shape Distance: the minimal vertical distance between the shapes.
Min. Connector Distance: the minimal vertical distance of the connector segments.
Orientation: the layout direction for arranging nodes and connectors -top to bottom, left to right, bottom to top, and right to left.
Shape Placement: affects the horizontal spacing between shapes, and the number of bends of the connectors -pendulum, linear segments, polyline,
tree and simplex.

Hierarchical Layout setting

Automatic Diagram Layout P. 507


Directed tree layout
Directed Tree Layout, which is one of the tree layouts in VP-UML, arranges shapes in a tree structure. It is the best way for users to arrange shapes
except those which have hierarchical relationships, such as generalization relationships and realization relationships.

Directed Tree Layout

Automatic Diagram Layout P. 508


Min. Layer Distance: the minimal horizontal distance between the shapes.
Min. Shape Distance: the minimal vertical distance between the shapes.
Orientation: the layout direction for arranging nodes and connectors &ndash; top to bottom, left to right, bottom to top, and right to left.
Connector End Point Style: how the connector end points will be placed &ndash; shape centered, border centered, border distributed.
Orthogonal Connector: whether the connectors will be arranged in orthogonal.

Directed Tree Layout setting

Automatic Diagram Layout P. 509


Balloon tree layout
Balloon Tree Layout, which is one of the tree layouts in VP-UML, arranges shapes in a tree structure in a radial fashion. It is the best way for users to
arrange large trees.

Automatic Diagram Layout P. 510


Min. Connector Length: the minimal distance between the connectors and shapes.
Preferred Child Wedge: the angle at which the child node will be placed around its parent node.
Preferred Root Wedge: the angle at which a node will be placed around the root node.
Root Node Policy: determines which node is chosen as the tree root node for layout &ndash; directed root, center root, and weighted center root.

Balloon Tree Layout setting

Automatic Diagram Layout P. 511


Compact tree layout
Compact Tree Layout, which is one of the tree layouts in VP-UML, arranges shapes in a tree structure. The aspect ratio (relation of tree width to tree
height) of the resultant tree can be set.

Automatic Diagram Layout P. 512


Horizontal Spacing: the horizontal spacing between the shapes.
Vertical Spacing: the vertical spacing between the shapes.
Min. Connector Length: the vertical distance of the connector segments.
Aspect Ratio: the relation of the tree width to the tree height.

Compact Tree Layout setting

Horizontal-Vertical tree layout


Horizontal-Vertical Tree Layout, which is one of the tree layouts in VP-UML, arranges shapes in a tree structure horizontally and vertically.

Horizontal-Vertical Tree Layout

Automatic Diagram Layout P. 513


Horizontal Spacing: the horizontal spacing between the shapes.
Vertical Spacing: the vertical spacing between the shapes.

Horizontal-Vertical Tree Layout setting

Automatic Diagram Layout P. 514


BBC compact circular layout
BBC Compact Circular Layout, which is one of the circular layouts in VP-UML, arranges shapes in a radial tree structure. The detected group is laid out
on the separate circles. It is the best way for user to arrange shapes that belong to more than one group with a ring structure.

BBC Compact Circular Layout

Automatic Diagram Layout P. 515


Maximal Deviation Angle: the maximal angle of deviation.
Preferred Child Wedge: the angle at which the child node will be placed around its parent node.
Minimal Edge Length: the minimal distance between the shapes.
Compactness Factor: the parameter that affects the length of connector. The smaller the compactness factor, the length of connectors will be shorter
and the layout will be more compact.
Allow Overlaps: whether the shape can be overlapped.

BBC Compact Circular Layout setting

Automatic Diagram Layout P. 516


BBC isolated circular layout
BBC Isolated Circular Layout, which is one of the circular layouts in VP-UML, arranges shapes into many isolated ring structures. It is the best way for
users to arrange shapes that belong to one group with ring structure.

BBC Isolated Circular Layout

Automatic Diagram Layout P. 517


Maximal Deviation Angle: the maximal angle of deviation.
Preferred Child Wedge: the angle at which the child node will be placed around its parent node.
Minimal Edge Length: the minimal distance between the shapes.
Compactness Factor: the parameter that affects the length of connector. The smaller the compactness factor, the length of connectors will be shorter
and the layout will be more compact.
Allow Overlaps: whether the shape can be overlapped.

BBC Isolated Circular Layout setting

Automatic Diagram Layout P. 518


Single cycle circular layout
Single Cycle Layout, which is one of the circular layouts in VP-UML, arranges shapes in circular structure in single circle.

Single Cycle Circular Layout

Automatic Diagram Layout P. 519


Choose radius automatically: determine the radius of circular structure automatically or manually.
Minimal Node Distance: the minimal distance between the nodes.
Fixed radius: the radius of circular structure.

Single Cycle Circular Layout setting

Automatic Diagram Layout P. 520


Organic layout
Organic Layout, which is one of the organic layouts in VP-UML, arranges shapes in a star or ring structure. It is the best way for users to arrange the
shapes that have highly connectivity relationship.

Organic Layout

Automatic Diagram Layout P. 521


Activate Deterministic Mode: whether the layouter is in deterministic mode.
Activate Tree Beautifier: whether or not to activate the subtree beautifier.
Attraction: the degree of the attraction between shapes.
Final Temperature: the factor that affects the distance between shapes.
Gravity Factor: the factor that affects the distance between shapes and the center.
Initial Placement: the initial value of placement.
Initial Temperature: the initial value of temperature.
Iteration Factor: the degree of iteration.
Maximum Duration: the maximum degree of duration.
Obey Node Size: the size of obey shapes.
Preferred Edge Length: the preferred length between the nodes.
Repulsion: the factor that affects the distance between shapes which belong to the same ring or star structure.

Organic Layout setting

Automatic Diagram Layout P. 522


Smart organic layout
Smart Organic Layout, which is one of the organic layouts in VP-UML, is a variant of the Organic Layout. It can set the ratio of the quality: producing
time of layout and controls the compactness of layout.

Smart Organic Layout


Automatic Diagram Layout P. 523
Compactness: the factor that sets less/more compact layout.
Deterministic: whether the layouter is in deterministic mode.
Minimal Node Distance: the minimal distance between nodes.
Node Overlaps Allowed: whether the node can be overlapped.
Node Size Aware: whether the node size can be aware.
Preferred Minimal Node Distance: the preferred minimal distance between the nodes.
Quality Time Ratio: the ratio of the quality of layout to the producing time of layout.

Organic Layout setting

Automatic Diagram Layout P. 524


Automatic layout selected shapes
To layout all the shapes in the diagram, right-click on the diagram and select Layout from the pop-up menu.

Perform layout with all shapes of diagram

Automatic Diagram Layout P. 525


To layout the selected shapes, right-click on the selection and select Layout from the pop-up menu (make sure there are more than one diagram
elements selected).

Perform layout with selected shapes

Automatic route connectors


There are 2 kinds of layouts which do not change the location of shapes, only change the connectors: Organic Edge Route Layout and Orthogonal
Edge Route Layout

Automatic Diagram Layout P. 526


Organic edge route layout
Organic Edge Route Layout, which is one of the edge route layouts in VP-UML, arranges the connectors without affecting the location of shapes. It can
ensure that the shapes will not overlap and keep a specific minimal distance.

Organic Edge Route Layout

Automatic Diagram Layout P. 527


Minimal Distance: the minimal distance of the connectors.
Route All: whether all the connectors will be routed.
Use Existing Beans: whether using existing bends.

Organic Edge Route Layout setting

Automatic Diagram Layout P. 528


Orthogonal edge route layout
Route Connectors can arrange the connectors using vertical and horizontal line segments only. It is the best way for users to arrange the connectors
that have complicated route.

Orthogonal Edge Route Layout

Automatic Diagram Layout P. 529


Center to space ratio: the ratio of center to the distance between center and nodes.
Coupled distances: the distance between coupled nodes.
Crossing cost: the cost of crossing connectors.
Custom border capacity: the capacity of the border.
Local crossing minimization: whether the local crossing of connectors will be minimized.
Minimum distance: the minimum distance of connectors.
Minimum distance to node: the minimum distance between the shapes.
Rerouting: whether the connector that has many crossings will be rerouted.
Routing style: the style of routing.

Orthogonal Edge Route Layout setting

Automatic Diagram Layout P. 530


Fit shape size
In some cases, shapes are found oversized. For better presentation, you may need to resize them smaller. Fit size can help you to adjust shapes into
the smallest size based on their content, such as the name of shape. The size of shapes can be fixed either manually or automatically.

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.

Fit selected shapes size


To adjust a shape size, move the mouse on a shape and fit size resource centric interface will be shown. Click Fit Sizeresource icon at the bottom of
the shape.

Click Fit 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.

Fit size for several shapes 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.

Shapes are fitted size

Fit Shape Size P. 531


Check/uncheck automatic fit shape size mode
You can check/ uncheck the Auto Fit Shapes Size on diagram to make all the shapes on the diagram to be fitted size automatically. To do so, right
click on the diagram's background, select Diagram Content > Auto Fit Shapes Size from the pop-up menu.

Check Auto Fit Shapes Size from the pop-up menu

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.

Class shape is resized automatically after new attribute added

You can also check Auto Fit Size for future usage.
1. Select Tools > Options... from the main menu to unfold Options dialog box.

Fit Shape Size P. 532


2. In the Options dialog box, press the Diagramming category, select the Shape tab and check Auto fit size (diagram-based).

Check Auto fit size (diagram-based) in the Options dialog box

Fit Shape Size P. 533


Diagram element selection
When a number of diagram elements need selecting simultaneously, diagram element selection supports this purpose. You can either click directly with
hot keys or select a range of selection with the mouse. A specific type of diagram element(s) on a diagram can be selected as well.

Selecting multiple shapes


Multiple shapes can be selected by either selecting a range of shapes with the mouse on diagram or clicking shapes with pressing hot keys.

Selecting a range of shapes with the mouse


1. For selecting multiple shapes, drag them from corner to corner diagonally with the mouse. They will then be surrounded by a rectangle
individually.

Select multiple shapes with the mouse

2. After releasing the mouse, those shapes will be selected.

Shapes are selected

Diagram Element Selection P. 534


Clicking with pressing ctrl/Shift key
Click a shape in advance and then click other shapes with pressing Ctrl or Shift key. As a result, those shapes will be selected.

Click shapes with pressing Ctrl or Shift key

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.

Diagram Element Selection P. 535


1. Right click on the diagram's background where is in the vicinity of those shapes you are going to select, select Handi-Selection and then select
a scope for selecting shapes (i.e. above/ below/ left/ right) from the pop-up menu.

Select all shapes on the right from the pop-up menu

2. As a result, all the shapes of the particular scope will be selected.

All shapes on the right are selected

Diagram Element Selection P. 536


Selecting same type of shapes
When you want to select a few shapes of same types on the diagram, right click on a shape and select Selection > Select All of Same Type from the
pop-up menu. As a result, other shapes of same type as the shape you selected previously will be selected.

All shapes of same type are selected

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

Diagram Element Selection P. 537


Copy and paste
You can create a view of a model element by copying a view and pasting as view, while pasting as model creates a new model from the copied one.

Copying within VP-UML


1. Right click on the selected shape(s), select Copy > Copy within VP-UML from the pop-up menu.

Copy selected shapes with VP-UML EE

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.

Paste the selected shape

Copying to clipboard as image (JPG)


1. Right click on the selected shape(s) and select Copy > Copy to Clipboard as Image (JPG) from the pop-up menu.

Copy and paste P. 538


2. When the Copy as Image Option dialog box pops out, select an option from the drop-down menu of Copy type. Click Copy button to proceed.

Select an option from the drop-down menu of Copy type

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 to clipboard as image (EMF)


1. Right click on the selected shape(s) and select Copy > Copy to Clipboard as Image (EMF) from the pop-up menu.
2. When the Copy as Image Option dialog box pops out, select an option from the drop-down menu of Copy type. Click Copy button to proceed.
3. EMF is a kind of scalable image which can be pasted on a document for further documentation. After you switch to the destination document,
right click on a 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.

Select the xml file path

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.

Copy and paste P. 539


2. When the Copy to Diagram dialog box pops out, check Create new diagram if you want to paste to a new diagram or check Select an
existing diagram if you want to paste to an existing diagram.

Check Create new diagram

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.

Duplicate a selected shape

Copy and paste P. 540


2. As a result, the selected shape(s) will be duplicated.

The shape is duplicated

Copy and paste P. 541


Alignment guide
Alignment is the adjustment of an object in relation with other objects. Therefore, the diagram alignment means adjusting a shape's position with
another's (or others') in a straight line or in parallel lines. When you drag shapes, alignment guide will appear to let you position the dragging content in
accordance with existing shape(s).

Showing edges alignment guide


When you drag a shape upward or downward, two horizontal lines will reveal on the both edge of the shape as an offer of assistance for adjusting the
shape's position.

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 to the right

Showing center alignment guide


When you drag a shape upward or downward, a horizontal line will reveal in the center of the shape as an offer of assistance for adjusting the shape's
position.

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.

Drag to the right

Changing alignment guide options


If you want the alignment guide to help you to position when you drag shapes, check Show diagram alignment guide; on the contrary, uncheck it if
you don't need a help. Two Choices are provided in alignment guide: Show edges and Show center. Choose Show edges if you want two horizontal
lines to reveal on the both edge of the moving shape while choose Show center if you want a horizontal line to reveal in the center of the shape.
1. Select Tool > Options... from the main menu to unfold Options dialog box.

Alignment guide P. 542


2. In shortcut, typing Alignment guide on top-left text field for searching. It will be shown that the option of alignment guide is on Diagramming
category, Environment tab shortly. As you see, the option will be highlighted for your convenience.

Change alignment guide options

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.

Alignment guide P. 543


Reverse connector direction
The flow between shapes is represented by connectors, for example, a sequence message between two lifelines of Student and StudentController
which represents the call from Student to StudentController. If the flow is created mistakenly, or the flows need reverting due to an updated data, the
flows can be fixed by reverting connectors.

Reverse connector direction


1. Right click on the connector between two shapes and select Reverse Connector from the pop-up menu.

Select Reverse Connector from the pop-up menu

2. As a result, the flow of connector is reversed.

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.

Reverse connector direction P. 544


Visualize model elements on diagram
Model elements are fundamental parts of a project. While a model element can be shown on more than one diagram, a diagram can also show a
model element more than once. They, which can be found in Model Explorer or Class Repository, contain metadata and can be shown in diagram
for visualizing the data. For example, a stick figure for an actor model element.
To visualize a model element or several model elements:
1. Select a model element (or as many as model elements you preferred) from Model Explorer.

Select several model elements from Model Explorer

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.

Drag the model elements on diagram

Visualize model elements on diagram P. 545


Visualize related model elements
Sometimes, several model elements that related to the current model element(s) are hidden for various reasons. These related model elements, in
fact, can be revealed through the feature of visualize related model element. With this feature, the relationship between model elements can be viewed
thoroughly.
1. Right click on a model element and select Related Elements > Visualize Related Model Element... from the pop-up menu.

Select Visualize Related Model Element...

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.

Visualize Related Model Element dialog box

Visualize related model elements P. 546


3. As a result, the related models with connectors are shown on the diagram.

Related model elements are visualized

Visualize related model elements P. 547


Adding comments
VP-UML supports comments on model elements. Since comments are usually used to record the progress and status of model elements, they are
regarded as a textual annotation for model elements.

Adding comment to model element


1. For adding comment in a particular shape, right click on the shape and select Open Specification... from the pop-up menu.

Open specification

2. In Specification dialog box, select Comments tab and click Add... button to create a comment.

Add comment

Adding comments P. 548


3. In Comment Specification dialog box, enter summary, author and date time respectively. Select OK button to confirm editing.

Enter information in Comment Specification dialog box

4. As a result, the comment you entered previously is shown on Specification dialog box.

Comment is shown

Managing comment of model element


1. To modify comment in a particular shape, right click on the shape and select Open Specification... from the pop-up menu.

Adding comments P. 549


2. In Specification dialog box, click Comments tab, select a specified summary comment and click Open Specification... button to proceed.

Open specification

3. In Comment Specification dialog box, modify information and select OK to confirm changing.

Modify information

Adding comments P. 550


Pinning connector ends
Connectors can be either pinned temporarily or pinned permanently. Connector ends help you to point out a specific position of shapes with pin.

Adjusting connector ends temporarily


1. Connectors can be joined at same point of a shape on the diagram. To do so, drag one end of a connector to the shape.

Drag one end of a connector to a shape

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.

Connector is temporarily pinned

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

Pinning connector ends


1. Move the mouse over a connector and press its resource icon Pin.

Press resource icon Pin

Pinning connector ends P. 551


2. Drag one end of connector to point out a specific position. Note that no dialog box of temporary pin will be shown this time.

Drag one end of connector to point out a specific position

3. Moving either from shape or to shape will not unpin the connector.

Connector is still pinned

Pinning connector ends P. 552


Align and distribute diagram elements
VP-UML supports two types of positioning features: alignment and distribution which allow the positioning of selected shapes in accordance with the
alignment/ distribution option through the toolbar or grouping resource icons. Alignment refers to the edges and the centers of selected shapes are
aligned to each other while distribution refers to selected shapes are distributed in same direction based on their centers or edges.

Aligning diagram elements


Select a few model elements with the mouse on the diagram pane before executing alignment.

Selected shapes

through main menu


1. Select Edit > Align Shapes and then an alignment option from the main menu.

Select Edit > Align Shapes > Right from the main menu

Align and distribute diagram elements P. 553


2. As a result, the alignment of all selected shapes is based on the last selected shape. Note that the last selected shape refers to the shape with
no-filled selector.

Shapes are aligned

3. For turning the non-selected shape into the last selected shape, click a shape with pressing Ctrl key.

Change the last selected shape

through grouping resource icons


1. When move the mouse over one of the selected shapes, grouping resource icons will be shown.
2. Select an alignment option from the drop-down menu of Align Top on the grouping resource icons.

Select Align Left on resources

Align and distribute diagram elements P. 554


3. As a result, all selected shapes are aligned in accordance with the last selected shape.

Shapes are aligned

Setting model elements same width and height


Besides aligning the shapes, shapes can also be resized through the toolbar or grouping resource icons or Align Shapes Dialog.

through main menu


Select Edit > Align Shapes and an alignment option from the main menu.

Resize through main menu

Align and distribute diagram elements P. 555


As a result, the shapes are resized.

Shapes are resized

through grouping resources


Select an option from the drop-down menu of Same Width on grouping resource icons after select a few shapes on the diagram pane.

Resize through grouping resources

through align shapes dialog


After select a few shapes on the diagram pane, select either Align Shapes > Align Shapes on toolbar or Edit > Align Shapes > Align Shapes...
from the main menu to unfold Align Shapes Dialog. You can select an option by clicking the option button on the Align Shapes Dialog directly.

Align Shapes Dialog

Distributing diagram elements


In addition, model elements can be distributed in various directions through the toolbar or grouping resource icons.

Align and distribute diagram elements P. 556


through toolbar
Select a distribution option from the drop-down menu of Distribute Shape on the toolbar after select a few shapes on the diagram pane.

Select Distribute Shapes > Vertically from the main menu

through grouping resource icons


Select a distribution option from the drop-down menu of Distribute Horizontally on grouping resource icons after select a few shapes on the diagram
pane.

Distribute shapes on grouping resource icons

Align and distribute diagram elements P. 557


Adjusting caption's position and angle in BPD
In BPD, for shapes like event and gateway, their names are put outside and below the shape, which may overlap with outgoing sequence or message
flow, making the name hard to read. To solve this problem, you can choose to place the caption elsewhere. Furthermore, you can rotate the caption to
make it easier to read in print out.
To set the position and angle of start, intermediate or end event, or gateway:
1. Right click on the shape and select Presentation Options > Caption Placement... from the popup menu.

To change caption placement

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.

To choose a placement option

3. Click OK to confirm.

Caption position updated

Adjusting caption's position and angle in BPD P. 558


Sweeper and Magnet
Modifying your diagrams from time to time is no longer a drag-- let's take our utilities: sweeper and magnet which can help you to modify your diagrams
easily. With these two features, you can move diagram elements easily without worrying too much about the layout. Sweeper can help you to increase
more space between the diagram elements while magnet can help you diminish the space.

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.

Moving down the diagram element horizontally

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:

Sweeper and magnet P. 559


1. Click Magnet button from the diagram toolbar.

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.

Moving up the diagram element horizontally

Sweeper and magnet P. 560


Mouse gestures
A variety of shapes and model elements can be created by sketching a path directly on the diagram pane with dragging the right mouse button to
form a gesture. For your convenience and quick creation, mouse gestures allow you to execute common commands and create UML models within all
diagrams.

Drawing shapes
1. To start using a mouse gesture, press the right mouse button and drag it until finish drawing a shape.

Drawing clockwise rectangle

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 Class member


You can learn how to create attribute and operation within the class in the following sub-sections.

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

Mouse gestures P. 561


2. If draw the line until outside the class, a public operation will be created.

Public operation is created

Connecting shapes
1. Draw a line from one shape to another.

Drawing from a shape to another

2. After the mouse is released, a connector is created between two shapes.

Association created

Creating a new shape


1. A new shape can also be created. To do so, draw a line from an existing shape to your preferred place.

Drawing to empty area

Mouse gestures P. 562


2. After the mouse is released, a pop-up menu will be shown. You can select your preferred type of connector and shape from the pop-up menu.

Create generalization with class

3. The two shapes with connector are created.

Class with generalization created

List of supported mouse gestures


General

Icon Description

Layout diagram

Open diagram specification

Connect new shape

Connect existing shape

Close Diagram

Mouse gestures P. 563


Thumbnail view

The description of general mouse gestures

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.)

The description of mouse gestures for activity diagram

Activity diagram (UML 1.x)

Icon Description

Action State

Sub-Activity

Swimlane

Horizontal Synchronization Bar

Vertical Synchronization Bar

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 activity diagram

Business process diagram

Icon Description

Mouse gestures P. 564


Sub-Process

Pool/Task

Horizontal
Lane

Vertical Lane

The description of mouse gestures for business process diagram

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.)

The description of mouse gestures for class diagram

Communication diagram

Icon Description

Sync. To Sequence
Diagram

Lifeline

Actor

Package

Mouse gestures P. 565


The description of mouse gestures for communication diagram

Component diagram

Icon Description

Component

Instance Specification

Package

The description of mouse gestures for component diagram

Composite structure diagram

Icon Description

Class

Interface

Collaboration

Collaboration Use

The description of mouse gestures for composite structure diagram

Data flow diagram

Icon Description

Process

External Entity

Data Store

The description of mouse gestures for data flow diagram

Deployment diagram

Icon Description

Node

Mouse gestures P. 566


Component

Instance Specification

Package

The description of mouse gesture for deployment diagram

EJB diagram

Icon Description

Entity Bean

Message-Driven
Bean

Session Bean

Package

The description of mouse gestures for EJB diagram

Entity relationship diagram

Icon Description

Sync. to Class Diagram

Entity

Add column

The description of mouse gestures for ERD

Interaction overview diagram

Icon Description

Interaction

Decision Node

Mouse gestures P. 567


Initial Node/Final 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.)

The description of mouse gestures for interaction overview diagram

Mind mapping diagram

Icon Description

Node

The description of mouse gesture for mind mapping diagram

Object diagram

Icon Description

Instance Specification

Class

Package

The description of mouse gestures for object diagram

ORM diagram

Icon Description

Sync. Classes -> Entities

Sync. Entities -> Classes

Class

Entity

Package

The description of mouse gestures for ORM diagram

Overview diagram

Icon Description

Diagram
Overview

Mouse gestures P. 568


The description of mouse gesture for overview diagram

Package diagram

Icon Description

Package

The description of mouse gesture for package diagram

Sequence diagram

Icon Description

Sync. to Communication
Diagram

Lifeline

Actor

Alt

Loop

The description of mouse gestures for sequence diagram

State machine diagram

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.)

The description of mouse gestures for state machine diagram

State machine diagram (UML 1.x)

Icon Description

State

Concurrent State

Mouse gestures P. 569


Submachine State

Horizontal Synchronization Bar

Vertical Synchronization Bar

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

The description of mouse gesture for timing diagram

Use case diagram

Icon Description

Use Case

Actor

Package

The description of mouse gestures for use case diagram

Mouse gestures P. 570


Jumping to shape
For searching a shape/shapes faster, the application of the jump to shape/shape facility is introduced. You can select either jump to a model element in
an active diagram, or jump to any model elements in the current project, or even jump to a diagram in current project.

Jumping to a diagram/model element in project


If there is an active diagram opened, you can jump to the model element in the active diagram.
1. You can select Edit > Jump to Element in Active Diagram... from the main menu or press Ctrl+J to unfold Jump to dialog box.

Select Jump to Element in Active


Diagram from the main menu

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.

Jump to dialog box is shown

Jumping to shape P. 571


4. Enter a word in the text field, a list of model element's name that starts with the word you typed will be shown .

A list of possible shapes is shown

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 shape P. 572


6. Press Enter to confirm jump to the model element. Finally, the Jump to dialog box will then be hidden and the model element will be selected
on diagram.

Shape is selected after confirm jump to

Jumping to shape P. 573


Filtering with wild card character
For quick search, you can type a word with * in the text field. The asterisk can substitute a character or a word when you don't remember the exact
spelling. As a result, all names of shape that similar to the word you typed will be shown.

Entering name with *

Jumping to diagram

Jumping to shape P. 574


1. To do so, select Edit > Jump to Diagram... from the main menu or press Ctrl+Shift+D to show Jump to dialog box.

Select Jump to Diagram... from the main menu

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.

Jump to dialog 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.

Select the diagram on list

Easy navigation to connected elements


If you have an oversized diagram that the from/to model elements of connector can't be shown on the screen, it is hard for you to know the from/to
model elements. VP-UML supports Scroll to function to scroll to from/to model element of a connector. If you want to know which model element is the
from model element that is connected with a model element .
To achieve this:

Jumping to shape P. 575


1. Right click on the connector and select Scroll to and then select Source with parentheses from the pop-up menu. (The word in parentheses is
the name of the from model element.)

Scroll to from model element

2. The from model element is subsequently selected on diagram.

From model element is selected

Jumping to shape P. 576


Grouping diagram elements
After you have aligned shapes to a group of shapes, in some cases, you want to move a number of shapes simultaneously, or make them share the
same formatting properties, like background color and line formatting. Grouping can help you for this purpose exactly. By grouping shapes, shapes
within the group will move together when moving any shape inside the group. If you edit formatting of one shape, all shapes will also be shared.

Grouping diagram elements


1. Select the shapes you want them to be grouped together.

Select several shapes

2. Click resource icon Group to group the selected shapes.

Group through resource icon Group

3. When you move a shape, other shapes within the same group will also be moved.

All shapes in group are moved together

Grouping diagram elements P. 577


Ungrouping diagram elements
To ungroup the shapes, click resource icon Ungroup.

Click Ungroup

Grouping diagram elements P. 578


Show/hide diagram elements
On a compact diagram, to hide or show some of the shapes is necessary. You can choose to hide away diagram elements on a diagram temporarily.
For example, hiding away annotation shapes which record internal communications before printing out a diagram for customers' review. In VP-UML,
hiding of diagram elements can be done per shape, per shape type or by stereotype.

Hiding selected diagram element(s)


Right click on the selected shape(s) and select Selection > Hide from the pop-up menu.

Select Hide from the pop-up menu

Show/hide diagram elements P. 579


Apart from the selected shapes, its related shape(s) (e.g. children and relationship) will also be hidden.

The selected shape and its related shapes are hidden

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.

Show/hide diagram elements P. 580


Hiding diagram elements by shape type
All the shapes with same type from the diagram can also be hidden. Right click on the diagram's background and select Diagram Content > Show/
Hide > Hide by Shape Type, and then select the shape you want to be hidden from the pop-up menu. As a result, all shapes with the same type you
selected will be hidden.

Hide all shapes by shape type

Show/hide diagram elements P. 581


Hiding diagram elements by stereotype
The stereotype of all diagram elements from the diagram can be hidden. Right click on the diagram's background and select Diagram Content >
Show/Hide > Hide by Stereotype, and then select one stereotype out of the list from the pop-up menu. As a result, all shapes with same stereotype
you selected will be hidden.

Hide all shapes by stereotype

Show/hide diagram elements P. 582


Showing all hidden diagram elements
All hidden shapes from the diagram can be shown again. Right click on the diagram's background and select Diagram Content > Show/Hide > Show
all Diagram Elements. As a result, the hidden shapes will be shown on the diagram.

Managing show/Hide of specific diagram element(s)


A better management of showing and hiding the shapes can be done in Show Hide Diagram Elements dialog box.
1. Right click on the diagram's background, select Diagram Content > Show/Hide > Show/Hide Diagram Elements... from the pop-up menu.

Select Show/Hide Diagram Elements... from the pop-up menu

Show/hide diagram elements P. 583


2. When Show Hide Diagram Elements dialog box is unfolded, you may select the shape(s) you would like to be hidden or to be shown. Click the
diagram element you would like to move to Hide list and press Hide Selected button; on the other hand, click the diagram element you would
like to remove it back to Show list and press Show Selected button. For moving all diagram elements to Hide list, press Hide All button; press
Show All button, vice verse. Finally, click OK to confirm.

Select a diagram element to be moved to Hide list

NOTE: If a shape is selected from Show list, the related shape(s) of the selected shape will be also removed to Hide list

Show/hide diagram elements P. 584


Layer
If you have ever experienced how hard it is to deal with a number of shapes, try the application of multi-layers. VP-UML supports multi-layers to help
you manage different shapes efficiently. The functions of layer assist you in assigning different shapes into different layers, hiding unnecessary shapes,
locking shapes and selecting shapes in shortcut.

Creating a layer
1. Right click on the diagram background and select Layers... from the pop-up menu.

Select Layers... from the pop-up menu

2. In Diagram Layers dialog box, click Create new layer button to create a new layer.

Create a new layer in Diagram Layers dialog box

Layer P. 585
3. Finally, define the name for the newly created layer.

New layer will be an active layer

Sending shapes to a layer


The existing shapes are kept in default layer. However, both existing shapes and the newly created shapes on diagram can be sent to a new layer.
Create a new layer just like the steps of previous section. Right click on a shape and select Layers, and then select the new layer you have created.

Send the shape to a new 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.

Shapes on the layers are invisible on diagram

Locking shapes on a layer


In Diagram Layers dialog box, check Locked to make all shapes in that layer immovable and unable for editing while uncheck Locked to make them
movable and editable.

Shapes on the selected layer are locked

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.

Shapes of the layer are selected on diagram

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.

Changing the shape to non-selectable


1. Right click on the selected shapes, uncheck Selection > Selectable from the pop-up menu.

Selected shape to be non-selectable

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.

Changing the shape to selectable again


To make the shape selectable again, right click on the non-selectable shape and select Selectable from the pop-up menu.

Select Selectable

Making shape non-selectable P. 589


Setting all shapes to selectable or non-selectable
To makes all shapes on the diagram to be selectable or non-selectable, right click on the diagram background, select Diagram Content and then
select either Make All Shapes Selectable or Make All Shapes Non-Selectable from the pop-up menu.

Select Make All Shapes Selectable

Making shape non-selectable P. 590


Locking diagram
For reviewing the diagram, the application of lock diagram is the straight way. Diagram can be locked to be read-only. After it is locked, any shapes on
the diagram cannot be modified, inserted or deleted.

Locking the diagram


To lock the diagram, right click on the diagram background and select Diagram Content > Lock Diagram from the pop-up menu.

Lock the diagram

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

Locking diagram P. 591


Unlocking the diagram
To unlock the diagram, you should click Unlock button on the Diagram Locked dialog box.

Click Unlock in the Diagram Locked dialog box

Alternatively, you can right click on the diagram background and select Diagram Content > Lock Diagram from the pop-up menu.

Unlock the diagram from the pop-up menu

Locking diagram P. 592


Showing model element in multiple diagrams (Context base modeling)
You can show a model element in multiple diagrams to fit into different contexts. To show model elements on different diagrams, you may drag and
drop the model element(s) from the tree to the diagram, or copy and paste it as view.

Reusing model elements


In Model Explorer, a model element or several model elements from the source diagram can be dragged from the tree and drop it/ them on the
destination diagram.

Drag a model element from the tree

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.

Copy a model element

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.

Class PrivateCar is pasted as a new view

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.

Showing model element in multiple diagrams (Context base modeling) P. 593


As a result, their relationship is shown on the diagram.

Relationship is visualized

Opening other views


You can find out the source diagram of a model element by right clicking on it and select Related Elements > Show Other Views... from the pop-up
menu.

Click Show Other Views...

Showing model element in multiple diagrams (Context base modeling) P. 594


All diagrams, which contain the same model elements you selected, are listed and shown in the Show View dialog box. You can check a diagram
under Views and preview it under Preview; furthermore, click Go to View button to jump to and view the actual diagram.

Show View dialog box

Enforcing master view between model element and shape


If a model element is shown on different diagrams, you can define a shape to be the master view of the model element. Right click on the selected
shape, select Selection > Set as Master View from the pop-up menu.

Set as Master View

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.

Showing model element in multiple diagrams (Context base modeling) P. 595


Using overview diagram
When various diagrams with different contexts are modeled in your system, an overview diagram can be created to illustrate their relationships related
each other. With the overview diagram, you can have an overview of your system, after all, you can study their relationships. Since the overview
diagram is consist of thumbnail of diagrams that you have created previously, the overview of each diagram if find to be related to another diagram can
be linked up with connectors.

Creating an overview diagram


To create an overview diagram, select File > New Diagram > Others > Overview Diagram from main menu.

Create a new overview diagram

As a result, an empty overview diagram is created. Create overviews of diagrams and relate them to illustrate their relationship with each other.

The overview diagram

Using overview diagram P. 596


Creating an overview of new diagram
You can create a diagram from overview diagram. To create a new diagram from overview diagram, select your preferred diagram type from the
diagram toolbar and drag it on the diagram pane.

Create a use case diagram overview

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.

The newly created diagram is shown on overview diagram

Creating an overview of existing diagram


Besides creating an overview diagram of new diagram, you can also create an overview of existing diagram.
1. Create a diagram overview from the toolbar of overview diagram.

Create a diagram overview

2. Right click on the diagram overview and select Associate to Diagram... from the pop-up menu.

Using overview diagram P. 597


3. Select a diagram that you want to be shown on diagram overview and select OK button.

Select an existing diagram

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.

The selected diagram is shown

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.

Press Visualize Related Diagrams

Using overview diagram P. 598


As a result, the sub-diagram will be shown and both diagram overviews are connected.

Two diagram overviews are connected

Selecting a connector for diagram overviews


In order to present a relationship between two diagrams, different connectors should be used. Diagram containment is used when a diagram contained
is a part of the containing diagram overview while directional generic connector is used to model the sequence of diagrams, from advance to another.
Select a connector from the diagram toolbar and drag it from the source diagram overview to the destination diagram overview.

Select Diagram Containment

Using overview diagram P. 599


UML note
In VP-UML, UML notes can be created and attached to a shape via an anchor connector. The premier advantage of using UML notes is annotating a
specific model element on the diagram with normal text or HTML text, or to define OCL.

Creating a UML note with resource centric


1. Move the mouse over a shape and select a note resource icon.

Mouse the mouse over a shape

2. Drag it to a desired place on the diagram pane.

Drag the resource icon

3. Release the mouse. The shape is connected with the newly created note.

Note created

Editing UML note content


1. Double click the note to start editing its content. Note that the toolbar above the note can be used to format its content.

Start editing

2. Drag the bottom right corner of note to resize it.

Resizing

3. Click on the diagram background to confirm editing the note.

UML note P. 600


Callout shape
Callout shape is a label that is used for explanation on your model elements. Inserting callout shape aims to draw others' attention and give them
additional remarks. Basically, its function is similar to a photo caption or a comment. However, it does more than merely either a photo caption or a
comment. In fact, it looks more likely to a dialog box that you can place it next to your model elements.

Adjusting the direction of callout shape pointer


1. A remark can be inserted by selecting Callout from the diagram toolbar and dragging it to the model elements directly on the diagram pane.
2. The direction of callout shape pointer can be adjusted by simply dragging the pointer's end.

Adjust the pointer

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.

Adjust the pointer to a specific class member out of a class

NOTE: You can not only adjust the pointer's direction, but also its length.

Repositioning the shape


The position of callout shape can be moved by dragging the + icon that is located on the top right corner of the callout. This icon is used to reposition
the shape in a straight and simple way.

Reposition the shape

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.

Editing callout shape content


The content of callout shape can be edited by double clicking on the callout shape.

Callout shape P. 601


Emphasizing the content of callout shape
Formatting buttons can be used to insert formatting for the text in order emphasize your key points while you are editing the content, such as changing
font color. This helps to enhance the visual effect of the text as well.

Format the text

Callout shape P. 602


Freehand shapes
Freehand shapes are multi-functional features in VP-UML. With freehand shapes, you can not only draw various kinds of shapes, but also insert an
annotation. If you want to stress an important message with visual effect, you may use word art rather than using a note or a callout because you can
reshape the text in word art, however, not in a note or a callout. Moreover, the shapes in freehand are flexible that you can twist them freely, but you
can only resize a note or a callout.

Freehand toolbar interface

Summary of freehand shapes


Shape Type Sample

Pencil

Pen

Calligraphic Tool

Connector

Line

Label Line

Path Rectangle

Rectangle

Freehand shapes P. 603


Round Rectangle

Round Rectangle 2

Diamond

Parallelogram

Trapezoid

Isosceles
Trapezoid

Path Ellipse

Ellipse

Arc

Chord

Pie

Regular Polygon

Freehand shapes P. 604


Isosceles Triangle

Hexagon

Arrow

Two Head Arrow

Spiral

Text

Word Art

Summary of freehand shape

NOTE: Freehand can be switched on by clicking on diagram toolbar and select Category > Freehand from the pop-up menu.

Drawing free style path with pencil


1. Press on the empty space on diagram pane and drag to form the outline.

Drawing with pencil

2. Release the mouse and new freehand shape will then be created.

Activating the fine editing selector


Fine editing selector shows a second later after the freehand shape is being selected. To show it immediately, press keyboard ' N' key.
Press on a yellow selector for selecting and the selected selector will turn into orange. More fine editing selectors will appear for curve adjustment.

Selected fine editing selector

Freehand shapes P. 605


Drawing curve with pen
1. Click on empty space on diagram pane and drag it to create the first stroke.

Straight line 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

Drawing calligraphic path with calligraphic tool


1. Press on the diagram and drag to form the outline of shape. Release the mouse to create the shape.

Freehand shape created

2. By combining several other calligraphic shapes, you can create a complete diagram.

Calligraphy example

Draw straight and curve line with connector

Freehand shapes P. 606


1. Press on a source shape and drag it to the destination shape.

Connecting shapes

2. Release the mouse and a new connector will be created between them.

A line is created

Bend a straight connector into a curve


1. Press on a straight connector.

Clicking on straight line

2. Bend it to your preferred direction and it will become a curve connector.

A curve connector

Split a straight connector


1. Press the Ctrl key.
2. Click on the specified location to split. A new point at where you have clicked will turn into orange.

Splitting line

Freehand shapes P. 607


3. Drag on that point to split the line.

Moving mid point

Drawing straight and curved line


1. Press on the diagram pane and drag to form the outline.
2. Release the mouse button and a straight line will be created.

Line created

Bend a straight line into a curve


1. Select a straight line for a second to wait for the fine editing selectors popping out.

Showing fine editing selector

2. Press on the straight line. Drag it to bend into your preferred direction.

Dragging line as curve

Split straight line


1. Press the Ctrl key.
2. Click on the specified location to split. A new point at where you have clicked will turn into orange.

Splitting line

Freehand shapes P. 608


3. Drag on that point to split the line.

Moving mid point

Drawing labelled line


1. Press on the diagram and starting dragging to form its outline.
2. Release the mouse button to create the labelled line.

Freehand shape created

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.

Freehand shape created

Drawing path rectangle


Click on the diagram to create a path rectangle.

Freehand shape created

Freehand shapes P. 609


What's the difference between rectangle and path rectangle?
Path rectangle is formed by path, which enables you to freely reshape it, while rectangle always keeps shape as a rectangle.

Drawing rounded rectangle


Click on the diagram to create a rounded rectangle.

Freehand shape created

Drawing rounded rectangle 2


Click on the diagram to create a rounded rectangle 2.

Freehand shape created

What's the difference between rounded rectangle and rounded rectangle 2?


Rounded rectangle uses a single control point to control the deepness of corner, which ensures that the four corners remain consistent while rounded
rectangle 2 uses two points to control the deepness of corner, which can produce irregular corners.

Drawing diamond
Click on the diagram to create a diamond shape.

Freehand shape created

Drawing parallelogram
Click on the diagram to create a parallelogram shape.

Freehand shape created

Drawing trapezoid
1. Click on the diagram to create a trapezoid shape.

Freehand shapes P. 610


2. You can adjust the slope by dragging the fine editing selectors in yellow.

Other trapezoid outline

Drawing isosceles trapezoid


1. Click on the diagram to create an isosceles trapezoid shape.
2. You can reshape the Isosceles Trapezoid by dragging the fine editing selectors in yellow.

Other isosceles trapezoid outline

Drawing ellipse
Click on the diagram to create an ellipse shape.

Freehand shape created

Drawing path ellipse


Click on the diagram to create a path ellipse shape.

Freehand shape created

What's the difference between ellipse and path ellipse?


Path ellipse is formed by path, which enables you to freely reshape it while ellipse always keeps shape as an oval.

Drawing arc
1. Click on the diagram to create an arc shape.

Freehand shapes P. 611


2. You can extend the line by dragging on the fine editing selectors in yellow.

Other arc outline

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.

Other Chord outline

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.

Other pie outline

Drawing hexagon
Click on the diagram to create a hexagon shape.

Freehand shape created

Drawing regular polygon


1. Click on the diagram to create a regular polygon shape.

Freehand shapes P. 612


2. You can modify the outline of shape by dragging the fine editor selectors in yellow.

Other regular polygon outline

Drawing isosceles triangle


Click on the diagram to create an isosceles triangle shape.

Freehand shape created

Drawing single head arrow


1. Click on the diagram to create an arrow shape.
2. You can reshape it by dragging the fine editing selectors in yellow.

Other Arrow Outline

Drawing two head arrow


1. Click on the diagram to create a two head arrow shape.
2. You can reshape it by dragging the fine editing selectors in yellow.

Other two head arrow outline

Drawing spiral
1. Click on the diagram to create a spiral shape.

Freehand shapes P. 613


2. You can reshape it by dragging the fine editing selectors in yellow.

Other Spiral outline

Inserting text
1. Click on the diagram to create a text shape, and input the text. You can press Enter to insert line break.

Input the text in text shape

2. You can click Ctrl while pressing Enter to confirm editing.

Inserting word art


1. Click on the diagram to create a word art shape, and input the text. You can press Enter to insert line break.
2. You can click Ctrl while pressing Enter to confirm editor.

Freehand shape created

3. You can reshape it by dragging the fine editing selectors in yellow.

Editing word art

Freehand shapes P. 614


Reference to external resources
Additional references can be attached to a shape through resource icon References, such as inserting a file, a folder and a URL. After that, you can
open and view the inserted references through resource icon References.

Adding external resources


Adding a file reference
1. Move the mouse over a shape to add reference, click the resource icon References and select Add File... from the pop-up menu.

Click Add File...

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.

Enter file reference path

3. Click OK button to confirm the creation for file.

Adding a folder reference


1. Move the mouse over a shape to add reference, click the resource icon References and select Add Folder... from the pop-up menu.

Click Add Folder...

Reference to external resources P. 615


2. When the specification dialog box pops out, click the ... button in Path to select a folder path.

Click the ... button

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.

Adding a URL reference


1. Move the mouse over a shape to add reference, click the resource icon References and select Add URL... from the pop-up menu.

Click Add URL...

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.

Enter URL path

3. Click OK button to confirm the creation for URL.

Opening external resources


Move the mouse over a shape to open reference, click the resource icon References and select an external resource from the pop-up menu.

Reference to external resources P. 616


If you select a URL reference to open, it will be opened by default web browser. If you select a file reference to open, it will be opened by your system
with the program used to open this kind of file. If you select a folder reference to open, it will be opened by your system automatically.

Open a URL reference

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.

Enter the description

4. Finally, click Enter button to confirm editing.

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.

Select a reference to remove

3. Finally, click OK button to confirm the reference removal.

Reference to external resources P. 617


Reference to diagrams and shapes
Additional references can be attached to a shape through resource icon References, for example, inserting a diagram and a shape. After that, you can
open and view the inserted references through resource icon References.

Reference to diagrams
1. Move the mouse over a shape, press its resource icon References and select Edit References... from the pop-up menu.

Click Edit References...

2. When the specification dialog box pops up, click Add Diagram... button.

Click Add Diagram...

3. In Select Diagram dialog box, check an existing diagram or create a new diagram by clicking the icon under Diagrams.

Check an existing diagram

Reference to diagrams and shapes P. 618


4. You may enter the description for the diagram in the specification dialog box. Finally, click OK button to confirm the reference creation.

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.

Click Add Shape...

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.

Open a shape reference

Reference to diagrams and shapes P. 619


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.

Enter the description

4. Finally, click Enter button to confirm editing.

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.

Select a reference to remove

3. Finally, click OK button to confirm the reference removal.

Reference to diagrams and shapes P. 620


Elaborating model element with sub diagram
Each notation has its own meaning and semantic. For example, you use a use case to present users' goals (system functions) but not how to achieve
the goals. In order to model other aspects like the dynamic behavior of use case, you can elaborate a model element with a proper type of sub-diagram
and contribute the details on the model element.

Creating a new sub diagram


Move the mouse over a shape, press its resource icon Sub Diagrams when it reveals and select Add and then a preferred type of diagrams from the
pop-up menu.

Add a sub diagram

NOTE: Inserting a sub diagram on a model element, all child model elements of the sub diagram will also be attached.

Adding an existing diagram as sub diagram


Right click on a selected shape, select Sub Diagrams > Add Existing Diagrams... from the pop-up menu.

Add an existing diagram as sub diagram

Elaborating model element with sub diagram P. 621


When the Add Sub Diagrams dialog box pops out, select a sub diagram and then click OK button.

Add Sub Diagrams dialog box

Removing sub diagram


1. Move the mouse over a shape, press its resource icon Sub Diagrams and select Edit Sub Diagrams... from the pop-up menu.

Click Edit Sub Diagrams...

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.

Elaborating model element with sub diagram P. 622


Showing sub diagrams and reference indicators
The indicator of sub-diagrams and references helps you identify which shapes in diagram have sub-diagrams and/ or attached with references. The
indictor can be shown through the button on diagram toolbar.
1. Click Always Show Reference, Sub Diagram, Model Transitor and Documentation Resource button on diagram toolbar.

Click Always Show Reference, Sub Diagram, Model


Transitor and Documentation Resource button

2. As a result, references resource icon and sub-diagrams resource icon are shown.

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.

Showing sub diagrams and reference indicators P. 623


Creating shape in shape editor
Although UML and BPMN are well-established notations, sometimes they still not rich enough to express domain specific idea. Shape Editor is a
diagramming tool for you to design your own notation (stencil). Notations created can be incorporated into diagrams in VP-UML. To use shape Editor:

Creating Shape in Shape Editor P. 624


1. To launch Shape Editor, select Tools > Shape Editor... from the main menu.

Open Shape Editor through the main menu

Shape Editor is opened.

Shape Editor

Creating Shape in Shape Editor P. 625


2. A shape need to be created under a stencil, while a stencil is put under a category, under a gallery. To create a gallery, right-click on the Stencil
pane and select Add Gallery in the popup menu.

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.

Creating Shape in Shape Editor P. 626


6. To create a stencil, right click on a category and select Add Stencil in the pop-up menu.

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

Creating Shape in Shape Editor P. 627


9. Draw the shape in the drawing pane.

Draw a shape in drawing pane

10. Save the drawing by selecting File > Save from the main menu.

Save the drawing

Shapes created in Shape Editor can be used in VP-UML. For details, please refer to the next section.

Creating Shape in Shape Editor P. 628


Creating shapes from stencil pane
The Stencil pane is where user-created stencil shapes are stored. User can create a stencil shape on diagram by first displaying a stencil, dragging
and dropping a shape from Stencil pane to diagram. Below are the steps in detail.
1. Open the Stencil pane. It is by default resided at the panes at the bottom left of VP-UML. If it does not appear, select View > Panes > Stencil
from the main menu.
2.
Click on the (Add Stencil) button in the top of Stencil pane. This pops up a list of gallery. Select the stencil to add. The stencil is then added
to the Stencil pane.

Add a stencil

NOTE: You can add multiple stencil by repeating this step.

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.

Dragging shape out of Stencil pane

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.

Select Generic Connector


from the diagram toolbar

5. Press on the source shape, hold the mouse button, move the mouse cursor to the target shape and release the mouse button.

Connecting an Actor with a stencil shape

Creating Shapes from Stencil Pane P. 629


Hiding user interface components
You may want to hide away some diagram types, menu items or toolbar items to avoid your team creating wrong types of model. This can be done by
user interface (UI) customization.
1. Select Help > Customize UI... from the main menu.

Open the customize UI dialog box

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.

Select the menus to hide

3. Click OK button to confirm. By restarting the application, the selected user interface componenets will be hidden.

User interface components are hidden

Hiding user interface components P. 630


Adjusting user interface font
VP-UML runs with a screen design that is friendly enough for most users, but you can customize it to make it suit your preference. One of the possible
customization is to adjust the font settings for text appears on user interface, like the button caption for tools in toolbar, diagram editor tab's title, menus'
captions, etc. The settings will be stored in workspace. Hence, you can keep the settings every time you run VP-UML.
To adjust font settings:
1. Select Tools > Options from the main menu.
2. Select General from the list on the left hand side.
3. Open the Appearance page.
4. Check Change application font in the Font section. Adjust the font type and size.

Adjusting font settings

5. Click OK.

Adjusting user interface font P. 631


6. Restart the application to let the settings take effect.

Updated user interface

Adjusting user interface font P. 632


Instant reverse Java sources and classes
Instant reverse is a process to produce UML class model from a given input of source code. With instant reverse, you can reverse a snap shot of your
code-base to UML classes and form class diagram in further. By bringing code content into visual UML model, this helps programmers or software
engineers to review an implementation, identify potential bugs or deficiency and look for possible improvements. Apart from this, developers may
reverse a code library as UML classes, and construct model with them, like to reverse a generic collection framework and develop your own framework
by extending the generic one. In this chapter, we will go through the instant reverse of Java.

Reverse engineering UML classes from source files


1. Select Tools > Instant Reverse > Java. .. from the main menu.

Perform instant reverse

Reverse engineering of Java sources and classes P. 633


2. In the Instant Reverse dialog box, add the file or folder path of source by clicking on the appropriate Add button at the right hand side of the
dialog box. There are four kinds of supported sources: Jar file, class folder, a zip of source or a folder of source files.

The Instant Reverse dialog

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.

Overview of Instant Reverse

Reverse engineering of Java sources and classes P. 634


Overview of instant reverse dialog box

No. Name Description

1 Language The programming language for reversing.

2 Source paths A list of source paths to be reversed.

3 Add Jars Add a path of Jar file for reversing.

4 Add class folder Add a path of Java class folder for reversing.

5 Add zips Add a path of a zipped source 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.

13 OK Click to start reversing.

14 Cancel Click to cancel reversing and exit.

15 Help Click to read Help contents for instant reverse.

Description of instant reverse dialog box

On-demand reverse engineering


Consider if you have a zip file that contains million of Java source file, like the file src.zip of Java Development Kit (JDK), and now you want to make
the class java.util.Collection appear as UML class so that you can extend it when developing your own collection framework. Now, if you try to reverse
the zip file it will take you a long time to complete the reverse due to the amount of classes (and relationships) is just too many. With on-demand
reverse engineering, you will reverse the sources as indexes, and obtain an index tree in class repository. No actual UML classes will be reversed until
you trigger the reverse manually. This reduces the processing time significantly.

Reverse engineering of Java sources and classes P. 635


To perform on-demand reverse engineering, make sure the option Reverse source on demand is checked in the Instant Reverse dialog box.

The option Reverse source on demand


that appear in reverse dialog box

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.

Reversing a java source file from index tree

NOTE: On-demand reverse engineering is only available for Java

Forming class diagram from reversed classes


By the end of an instant reverse operation, you will be asked whether or not to form a class diagram with reversed UML classes. By selecting classes
and configuring the way to present them, and confirm, a diagram will then be form.

The Instant Reverse Form Diagram dialog box

Reverse engineering of Java sources and classes P. 636


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.

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.

Below is a description of this dialog, base on the tabs.

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.

Form Diagram Options

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.

Description of form diagram options

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.

Type options Fully-qualified - Show fully-qualified name of types.


Name only - Show name of types.
Relative - Show name of types relative to this class.

Description of presentation options

Reverse engineering of Java sources and classes P. 637


Reverse engineer package diagram from source files
By reverse engineering package diagram from source files, UML packages and the relationships in between will be produced.
1. Select Tools > Instant Reverse > Java ... from the main menu.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The instant reverse dialog

3. Check Reverse Package Diagram at the bottom of dialog box.


4. You can place reversed packages to specific model. 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.

5. Click OK to start reversing.

Reverse engineering of Java sources and classes P. 638


Instant reverse C++ header files
Instant reverse is a process to produce UML class model from a given input of source code. With instant reverse, you can reverse a snap shot of your
code-base to UML classes and form class diagram in further. By bringing code content into visual UML model, this helps programmers or software
engineers to review an implementation, identify potential bugs or deficiency and look for possible improvements. Apart from this, developers may
reverse a code library as UML classes, and construct model with them, like to reverse a generic collection framework and develop your own framework
by extending the generic one. In this chapter, we will go through the instant reverse of C++ header files.

Reverse engineering UML classes from source files


1. Select Tools > Instant Reverse > C++ Source ... from the main menu.

Perform instant reverse

Reverse engineering of C++ header files P. 639


2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files. You can add multiple paths by clicking
the + button.

The Instant Reverse dialog

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. Click OK to start reversing.


5. Upon finishing, you will see the Instant Reverse Form Diagram dialog box appear. If you want to form a class diagram with the reversed
classes, select the classes to form diagram, configure the options and click OK to proceed. Read the next section for detail. If you do not want to
form diagram now, click Cancel to exit.

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.

Overview of Instant Reverse

Reverse engineering of C++ header files P. 640


The instant reverse dialog box

No. Name Description

1 Language The language of source to reverse.

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.

5 Encoding The encoding of source file.

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.

9 OK Click to start reversing.

10 Cancel Click to close instant reverse.

11 Help Click to read the Help contents.

Overview of instant reverse dialog box

Reverse engineering of C++ header files P. 641


Forming class diagram from reversed classes
By the end of an instant reverse operation, you will be asked whether or not to form a class diagram with reversed UML classes. By selecting classes
and configuring the way to present them, and confirm, a diagram will then be form.

The Instant Reverse Form Diagram dialog box

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.

Below is a description of this dialog, base on the tabs.

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.

Form Diagram Options

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.

Reverse engineering of C++ header files P. 642


Description of form diagram options

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.

Type options Fully-qualified - Show fully-qualified name of types.


Name only - Show name of types.
Relative - Show name of types relative to this class.

Description of presentation options

Reverse engineer package diagram from source files


By reverse engineering package diagram from source files, UML packages and the relationships in between will be produced.
1. Select Tools > Instant Reverse > C++ header files... from the main menu.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The instant reverse dialog

3. Check Reverse Package Diagram.


4. You can place reversed packages to specific model. 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.

5. Click OK to start reversing.

Reverse engineering of C++ header files P. 643


Instant reverse .NET dll and exe files
Instant reverse is a process to produce UML class model from a given input of source code. With instant reverse, you can reverse a snap shot of your
code-base to UML classes and form class diagram in further. By bringing code content into visual UML model, this helps programmers or software
engineers to review an implementation, identify potential bugs or deficiency and look for possible improvements. Apart from this, developers may
reverse a code library as UML classes, and construct model with them, like to reverse a generic collection framework and develop your own framework
by extending the generic one. In this chapter, we will go through the instant reverse of .NET dll and exe files.

Reverse engineering UML classes from source files


1. Select Tools > Instant Reverse > .NET dll or exe files... from the main menu.

Perform instant reverse

2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The Instant Reverse dialog

Reverse engineering of .NET dll and exec files P. 644


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. Click OK to start reversing.


5. Upon finishing, you will see the Instant Reverse Form Diagram dialog box appear. If you want to form a class diagram with the reversed
classes, select the classes to form diagram, configure the options and click OK to proceed. Read the next section for detail. If you do not want to
form diagram now, click Cancel to exit.

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.

Overview of Instant Reverse

The instant reverse dialog box

No. Name Description

1 Language The language of source to reverse.

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.

6 OK Click to start reversing.

7 Cancel Click to close instant reverse.

8 Help Click to read the Help contents.

Overview of instant reverse dialog box

Reverse engineering of .NET dll and exec files P. 645


Forming class diagram from reversed classes
By the end of an instant reverse operation, you will be asked whether or not to form a class diagram with reversed UML classes. By selecting classes
and configuring the way to present them, and confirm, a diagram will then be form.

The Instant Reverse Form Diagram dialog box

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.

Below is a description of this dialog, base on the tabs.

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.

Form Diagram Options

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.

Reverse engineering of .NET dll and exec files P. 646


Description of form diagram options

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.

Type options Fully-qualified - Show fully-qualified name of types.


Name only - Show name of types.
Relative - Show name of types relative to this class.

Description of presentation options

Reverse engineer package diagram from source files


By reverse engineering package diagram from source files, UML packages and the relationships in between will be produced.
1. Select Tools > Instant Reverse > .NET dll or exe files... from the main menu.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The instant reverse dialog

3. Check Reverse Package Diagram.


4. You can place reversed packages to specific model. 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.

5. Click OK to start reversing.

Reverse engineering of .NET dll and exec files P. 647


Instant reverse CORBA IDL Source files
Instant reverse is a process to produce UML class model from a given input of source code. With instant reverse, you can reverse a snap shot of your
code-base to UML classes and form class diagram in further. By bringing code content into visual UML model, this helps programmers or software
engineers to review an implementation, identify potential bugs or deficiency and look for possible improvements. Apart from this, developers may
reverse a code library as UML classes, and construct model with them, like to reverse a generic collection framework and develop your own framework
by extending the generic one. In this chapter, we will go through the instant reverse of CORBA IDL Source files.

Reverse engineering UML classes from source files


1. Select Tools > Instant Reverse > CORBA IDL Source files... from the main menu.

Perform instant reverse

2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The Instant Reverse dialog

Reverse engineering of CORBA IDL source file P. 648


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. Click OK to start reversing.


5. Upon finishing, you will see the Instant Reverse Form Diagram dialog box appear. If you want to form a class diagram with the reversed
classes, select the classes to form diagram, configure the options and click OK to proceed. Read the next section for detail. If you do not want to
form diagram now, click Cancel to exit.

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.

Overview of Instant Reverse

The instant reverse dialog box

No. Name Description

1 Language The language of source to reverse.

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.

6 OK Click to start reversing.

7 Cancel Click to close instant reverse.

8 Help Click to read the Help contents.

Overview of instant reverse dialog box

Reverse engineering of CORBA IDL source file P. 649


Forming class diagram from reversed classes
By the end of an instant reverse operation, you will be asked whether or not to form a class diagram with reversed UML classes. By selecting classes
and configuring the way to present them, and confirm, a diagram will then be form.

The Instant Reverse Form Diagram dialog box

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.

Below is a description of this dialog, base on the tabs.

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.

Form Diagram Options

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.

Reverse engineering of CORBA IDL source file P. 650


Description of form diagram options

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.

Type options Fully-qualified - Show fully-qualified name of types.


Name only - Show name of types.
Relative - Show name of types relative to this class.

Description of presentation options

Reverse engineer package diagram from source files


By reverse engineering package diagram from source files, UML packages and the relationships in between will be produced.
1. Select Tools > Instant Reverse > .NET dll or exe files... from the main menu.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The instant reverse dialog

3. Check Reverse Package Diagram.


4. You can place reversed packages to specific model. 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.

5. Click OK to start reversing.

Reverse engineering of CORBA IDL source file P. 651


Instant reverse Ada 9X Source files
Instant reverse is a process to produce UML class model from a given input of source code. With instant reverse, you can reverse a snap shot of your
code-base to UML classes and form class diagram in further. By bringing code content into visual UML model, this helps programmers or software
engineers to review an implementation, identify potential bugs or deficiency and look for possible improvements. Apart from this, developers may
reverse a code library as UML classes, and construct model with them, like to reverse a generic collection framework and develop your own framework
by extendinDeterming the generic one. In this chapter, we will go through the instant reverse of Ada 9x Source files.

Reverse engineering UML classes from source files


1. Select Tools > Instant Reverse > Ada 9x Source files... from the main menu.

Perform instant reverse

2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The Instant Reverse dialog

Reverse engineering of Ada 9x source files P. 652


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. Click OK to start reversing.


5. Upon finishing, you will see the Instant Reverse Form Diagram dialog box appear. If you want to form a class diagram with the reversed
classes, select the classes to form diagram, configure the options and click OK to proceed. Read the next section for detail. If you do not want to
form diagram now, click Cancel to exit.

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.

Overview of Instant Reverse

The instant reverse dialog box

No. Name Description

1 Language The language of source to reverse.

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.

6 OK Click to start reversing.

7 Cancel Click to close instant reverse.

8 Help Click to read the Help contents.

Overview of instant reverse dialog box

Reverse engineering of Ada 9x source files P. 653


Forming class diagram from reversed classes
By the end of an instant reverse operation, you will be asked whether or not to form a class diagram with reversed UML classes. By selecting classes
and configuring the way to present them, and confirm, a diagram will then be form.

The Instant Reverse Form Diagram dialog box

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.

Below is a description of this dialog, base on the tabs.

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.

Form Diagram Options

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.

Reverse engineering of Ada 9x source files P. 654


Description of form diagram options

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.

Type options Fully-qualified - Show fully-qualified name of types.


Name only - Show name of types.
Relative - Show name of types relative to this class.

Description of presentation options

Reverse engineer package diagram from source files


By reverse engineering package diagram from source files, UML packages and the relationships in between will be produced.
1. Select Tools > Instant Reverse > .NET dll or exe files... from the main menu.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The instant reverse dialog

3. Check Reverse Package Diagram.


4. You can place reversed packages to specific model. 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.

5. Click OK to start reversing.

Reverse engineering of Ada 9x source files P. 655


Instant reverse XML
Instant reverse is a process to produce UML class model from a given input of source code. With instant reverse, you can reverse a snap shot of your
code-base to UML classes and form class diagram in further. By bringing code content into visual UML model, this helps programmers or software
engineers to review an implementation, identify potential bugs or deficiency and look for possible improvements. Apart from this, developers may
reverse a code library as UML classes, and construct model with them, like to reverse a generic collection framework and develop your own framework
by extending the generic one. In this chapter, we will go through the instant reverse of XML files.

Reverse engineering UML classes from source files


1. Select Tools > Instant Reverse > XML... from the main menu.

Perform instant reverse

2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The Instant Reverse dialog

Reverse engineering of XML P. 656


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. Click OK to start reversing.


5. Upon finishing, you will see the Instant Reverse Form Diagram dialog box appear. If you want to form a class diagram with the reversed
classes, select the classes to form diagram, configure the options and click OK to proceed. Read the next section for detail. If you do not want to
form diagram now, click Cancel to exit.

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.

Overview of Instant Reverse

The instant reverse dialog box

No. Name Description

1 Language The language of source to reverse.

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.

5 OK Click to start reversing.

6 Cancel Click to close instant reverse.

7 Help Click to read the Help contents.

Overview of instant reverse dialog box

Reverse engineering of XML P. 657


Forming class diagram from reversed classes
By the end of an instant reverse operation, you will be asked whether or not to form a class diagram with reversed UML classes. By selecting classes
and configuring the way to present them, and confirm, a diagram will then be form.

The Instant Reverse Form Diagram dialog box

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.

Below is a description of this dialog, base on the tabs.

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.

Form Diagram Options

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.

Reverse engineering of XML P. 658


Description of form diagram options

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.

Type options Fully-qualified - Show fully-qualified name of types.


Name only - Show name of types.
Relative - Show name of types relative to this class.

Description of presentation options

Reverse engineering of XML P. 659


Instant reverse XML Schema
Instant reverse is a process to produce UML class model from a given input of source code. With instant reverse, you can reverse a snap shot of your
code-base to UML classes and form class diagram in further. By bringing code content into visual UML model, this helps programmers or software
engineers to review an implementation, identify potential bugs or deficiency and look for possible improvements. Apart from this, developers may
reverse a code library as UML classes, and construct model with them, like to reverse a generic collection framework and develop your own framework
by extending the generic one. In this chapter, we will go through the instant reverse of XML Schema.

Reverse engineering UML classes from source files


1. Select Tools > Instant Reverse > XML Schema... from the main menu.

Perform instant reverse

2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The Instant Reverse dialog

Reverse engineering of XML schema P. 660


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. Click OK to start reversing.


5. Upon finishing, you will see the Instant Reverse Form Diagram dialog box appear. If you want to form a class diagram with the reversed
classes, select the classes to form diagram, configure the options and click OK to proceed. Read the next section for detail. If you do not want to
form diagram now, click Cancel to exit.

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.

Overview of Instant Reverse

The instant reverse dialog box

No. Name Description

1 Language The language of source to reverse.

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.

7 OK Click to start reversing.

8 Cancel Click to close instant reverse.

9 Help Click to read the Help contents.

Overview of instant reverse dialog box

Reverse engineering of XML schema P. 661


Forming class diagram from reversed classes
By the end of an instant reverse operation, you will be asked whether or not to form a class diagram with reversed UML classes. By selecting classes
and configuring the way to present them, and confirm, a diagram will then be form.

The Instant Reverse Form Diagram dialog box

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.

Below is a description of this dialog, base on the tabs.

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.

Form Diagram Options

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.

Reverse engineering of XML schema P. 662


Description of form diagram options

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.

Type options Fully-qualified - Show fully-qualified name of types.


Name only - Show name of types.
Relative - Show name of types relative to this class.

Description of presentation options

Reverse engineer package diagram from source files


By reverse engineering package diagram from source files, UML packages and the relationships in between will be produced.
1. Select Tools > Instant Reverse > .NET dll or exe files... from the main menu.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The instant reverse dialog

3. Check Reverse Package Diagram.


4. You can place reversed packages to specific model. 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.

5. Click OK to start reversing.

Reverse engineering of XML schema P. 663


Instant reverse database through JDBC
Instant reverse is a process to produce UML class model from a given input of source code. With instant reverse, you can reverse a snap shot of your
code-base to UML classes and form class diagram in further. By bringing code content into visual UML model, this helps programmers or software
engineers to review an imDeterminplementation, identify potential bugs or deficiency and look for possible improvements. Apart from this, developers
may reverse a code library as UML classes, and construct model with them, like to reverse a generic collection framework and develop your own
framework by extending the generic one. In this chapter, we will go through the instant reverse of database through JDBC.

Reverse engineering UML classes from database


1. Select Tools > Instant Reverse > JDBC... from the main menu.

Perform instant reverse

Reverse engineering of Database through JDBC P. 664


2. In the Instant Reverse dialog box, specify the JDBC settings.

The Instant Reverse dialog

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. Click OK to start reversing.


5. Upon finishing, you will see the Instant Reverse Form Diagram dialog box appear. If you want to form a class diagram with the reversed
classes, select the classes to form diagram, configure the options and click OK to proceed. Read the next section for detail. If you do not want to
form diagram now, click Cancel to exit.

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.

Overview of Instant Reverse

The instant reverse dialog box

No. Name Description

1 Language The language of source to reverse.

Reverse engineering of Database through JDBC P. 665


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 JDBC settings The JDBC settings required to connect to database to reverse.

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.

5 OK Click to start reversing.

6 Cancel Click to close instant reverse.

7 Help Click to read the Help contents.

Overview of instant reverse dialog box

Forming class diagram from reversed classes


By the end of an instant reverse operation, you will be asked whether or not to form a class diagram with reversed UML classes. By selecting classes
and configuring the way to present them, and confirm, a diagram will then be form.

The Instant Reverse Form Diagram dialog box

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.

Below is a description of this dialog, base on the tabs.

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.

Form Diagram Options

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.

Reverse engineering of Database through JDBC P. 666


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.

Description of form diagram options

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.

Type options Fully-qualified - Show fully-qualified name of types.


Name only - Show name of types.
Relative - Show name of types relative to this class.

Description of presentation options

Reverse engineering of Database through JDBC P. 667


Instant reverse hibernate mapping files
Instant reverse is a process to produce UML class model from a given input of source code. With instant reverse, you can reverse a snap shot of your
code-base to UML classes and form class diagram in further. By bringing code content into visual UML model, this helps programmers or software
engineers to review an implementation, identify potential bugs or deficiency and look for possible improvements. Apart from this, developers may
reverse a code library as UML classes, and construct model with them, like to reverse a generic collection framework and develop your own framework
by extending the generic one. In this chapter, we will go through the instant reverse of Hibernate mapping files.

Reverse engineering UML classes from source files


1. Select Tools > Instant Reverse > Hibernate... from the main menu.

Perform instant reverse

2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The Instant Reverse dialog

Hibernate mapping file P. 668


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. Click OK to start reversing.


5. Upon finishing, you will see the Instant Reverse Form Diagram dialog box appear. If you want to form a class diagram with the reversed
classes, select the classes to form diagram, configure the options and click OK to proceed. Read the next section for detail. If you do not want to
form diagram now, click Cancel to exit.

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.

Overview of Instant Reverse

The instant reverse dialog box

No. Name Description

1 Language The language of source to reverse.

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.

6 OK Click to start reversing.

7 Cancel Click to close instant reverse.

8 Help Click to read the Help contents.

Overview of instant reverse dialog box

Hibernate mapping file P. 669


Forming class diagram from reversed classes
By the end of an instant reverse operation, you will be asked whether or not to form a class diagram with reversed UML classes. By selecting classes
and configuring the way to present them, and confirm, a diagram will then be form.

The Instant Reverse Form Diagram dialog box

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.

Below is a description of this dialog, base on the tabs.

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.

Form Diagram Options

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.

Hibernate mapping file P. 670


Description of form diagram options

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.

Type options Fully-qualified - Show fully-qualified name of types.


Name only - Show name of types.
Relative - Show name of types relative to this class.

Description of presentation options

Reverse engineer package diagram from source files


By reverse engineering package diagram from source files, UML packages and the relationships in between will be produced.
1. Select Tools > Instant Reverse > Hibernate... from the main menu.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The instant reverse dialog

3. Check Reverse Package Diagram.


4. You can place reversed packages to specific model. 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.

5. Click OK to start reversing.

Hibernate mapping file P. 671


Instant reverse PHP 5.0 Source files
Instant reverse is a process to produce UML class model from a given input of source code. With instant reverse, you can reverse a snap shot of your
code-base to UML classes and form class diagram in further. By bringing code content into visual UML model, this helps programmers or software
engineers to review an implementation, identify potential bugs or deficiency and look for possible improvements. Apart from this, developers may
reverse a code library as UML classes, and construct model with them, like to reverse a generic collection framework and develop your own framework
by extending the Determingeneric one. In this chapter, we will go through the instant reverse of PHP 5.0 Source files.

Reverse engineering UML classes from source files


1. Select Tools > Instant Reverse > PHP 5.0 Source files... from the main menu.

Perform instant reverse

2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The Instant Reverse dialog

Reverse engineering of PHP 5.0 source files P. 672


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. Click OK to start reversing.


5. Upon finishing, you will see the Instant Reverse Form Diagram dialog box appear. If you want to form a class diagram with the reversed
classes, select the classes to form diagram, configure the options and click OK to proceed. Read the next section for detail. If you do not want to
form diagram now, click Cancel to exit.

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.

Overview of Instant Reverse

The instant reverse dialog box

No. Name Description

1 Language The language of source to reverse.

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.

5 Treat directory as package Convert folders to UML packages

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.

8 OK Click to start reversing.

9 Cancel Click to close instant reverse.

10 Help Click to read the Help contents.

Overview of instant reverse dialog box

Reverse engineering of PHP 5.0 source files P. 673


Forming class diagram from reversed classes
By the end of an instant reverse operation, you will be asked whether or not to form a class diagram with reversed UML classes. By selecting classes
and configuring the way to present them, and confirm, a diagram will then be form.

The Instant Reverse Form Diagram dialog box

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.

Below is a description of this dialog, base on the tabs.

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.

Form Diagram Options

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.

Reverse engineering of PHP 5.0 source files P. 674


Description of form diagram options

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.

Type options Fully-qualified - Show fully-qualified name of types.


Name only - Show name of types.
Relative - Show name of types relative to this class.

Description of presentation options

Reverse engineer package diagram from source files


By reverse engineering package diagram from source files, UML packages and the relationships in between will be produced.
1. Select Tools > Instant Reverse > .NET dll or exe files... from the main menu.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The instant reverse dialog

3. Check Reverse Package Diagram.


4. You can place reversed packages to specific model. 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.

5. Click OK to start reversing.

Reverse engineering of PHP 5.0 source files P. 675


Instant reverse Python
Instant reverse is a process to produce UML class model from a given input of source code. With instant reverse, you can reverse a snap shot of your
code-base to UML classes and form class diagram in further. By bringing code content into visual UML model, this helps programmers or software
engineers to review an implementation, identify potential bugs or deficiency and look for possible improvements. Apart from this, developers may
reverse a code library as UML classes, and construct model with them, like to reverse a generic collection framework and develop your own framework
by extending the generic one. In this chapter, we will go through the instant reverse of Python.

Reverse engineering UML classes from source files


1. Select Tools > Instant Reverse > Python... from the main menu.

Perform instant reverse

2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The Instant Reverse dialog

Reverse engineering of Python P. 676


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. Click OK to start reversing.


5. Upon finishing, you will see the Instant Reverse Form Diagram dialog box appear. If you want to form a class diagram with the reversed
classes, select the classes to form diagram, configure the options and click OK to proceed. Read the next section for detail. If you do not want to
form diagram now, click Cancel to exit.

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.

Overview of Instant Reverse

The instant reverse dialog box

No. Name Description

1 Language The language of source to reverse.

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.

6 OK Click to start reversing.

7 Cancel Click to close instant reverse.

8 Help Click to read the Help contents.

Overview of instant reverse dialog box

Reverse engineering of Python P. 677


Forming class diagram from reversed classes
By the end of an instant reverse operation, you will be asked whether or not to form a class diagram with reversed UML classes. By selecting classes
and configuring the way to present them, and confirm, a diagram will then be form.

The Instant Reverse Form Diagram dialog box

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.

Below is a description of this dialog, base on the tabs.

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.

Form Diagram Options

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.

NOTE: The containment relationships between classes are shown as connectors.

Description of form diagram options

Presentation Options

Reverse engineering of Python P. 678


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.

Type options Fully-qualified - Show fully-qualified name of types.


Name only - Show name of types.
Relative - Show name of types relative to this class.

Description of presentation options

Reverse engineer package diagram from source files


By reverse engineering package diagram from source files, UML packages and the relationships in between will be produced.
1. Select Tools > Instant Reverse > .NET dll or exe files... from the main menu.
2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The instant reverse dialog

3. Check Reverse Package Diagram.


4. You can place reversed packages to specific model. 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.

5. Click OK to start reversing.

Reverse engineering of Python P. 679


Instant reverse Objective-C
Instant reverse is a process to produce UML class model from a given input of source code. With instant reverse, you can reverse a snap shot of your
code-base to UML classes and form class diagram in further. By bringing code content into visual UML model, this helps programmers or software
engineers to review an implementation, identify potential bugs or deficiency and look for possible improvements. Apart from this, developers may
reverse a code library as UML classes, and construct model with them, like to reverse a generic collection framework and develop your own framework
by extending the generic one. In this chapter, we will go through the instant reverse of Objective-C.

Reverse engineering UML classes from source files


1. Select Tools > Instant Reverse > Objective-C... from the main menu.

Perform instant reverse

2. In the Instant Reverse dialog box, specify the path of the source file, or the folder that contain those files.

The Instant Reverse dialog

Reverse engineering of Objective-C P. 680


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. Click OK to start reversing.


5. Upon finishing, you will see the Instant Reverse Form Diagram dialog box appear. If you want to form a class diagram with the reversed
classes, select the classes to form diagram, configure the options and click OK to proceed. Read the next section for detail. If you do not want to
form diagram now, click Cancel to exit.

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.

Overview of Instant Reverse

The instant reverse dialog box

No. Name Description

1 Language The language of source to reverse.

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.

5 OK Click to start reversing.

6 Cancel Click to close instant reverse.

7 Help Click to read the Help contents.

Overview of instant reverse dialog box

Reverse engineering of Objective-C P. 681


Forming class diagram from reversed classes
By the end of an instant reverse operation, you will be asked whether or not to form a class diagram with reversed UML classes. By selecting classes
and configuring the way to present them, and confirm, a diagram will then be form.

The Instant Reverse Form Diagram dialog box

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.

Below is a description of this dialog, base on the tabs.

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.

Form Diagram Options

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.

Reverse engineering of Objective-C P. 682


Description of form diagram options

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.

Type options Fully-qualified - Show fully-qualified name of types.


Name only - Show name of types.
Relative - Show name of types relative to this class.

Description of presentation options

Reverse engineering of Objective-C P. 683


Instant reverse Java sources to sequence diagram
Instant reverse is a process to produce UML class model from a given input of source code. With instant reverse, you can reverse a snap shot of
your code-base to UML classes and form class diagram in further. Instant reverse can read the code body of operation in Java class (source file),
analyze the method invocations and form the result on a sequence diagram. This lets you study the runtime behavior of your application by mean of a
sequence diagram, which makes it easier to locate potential bottleneck and carry out changes.

Reverse engineering sequence diagram from source files


1. Select Tools > Instant Reverse > Java to Sequence Diagram. .. from the main menu.
2. In the Instant Reverse dialog box, add the zip file of source or folder path of source by clicking on the appropriate Add button at the right hand
side of the dialog box. Make sure the source folders include all the source files of all classes necessary for analyzing the traces of calls.

The Instant Reverse dialog

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.

Select an operating to analyze its code body and form diagram

Java to sequence diagram P. 684


5. Click Next.
6. In the Choose Diagram page, select the diagram to visualize the result. You can either form a new sequence diagram by selecting Create
new sequence diagram and entering the diagram name, or select Select an existing sequence diagram and choose an existing sequence
diagram to visualize the result.

Select a diagram to visualize the result

7. Click Finish. When the process is completed, you can obtain the result in sequence diagram.

Sequence diagram formed

Java to sequence diagram P. 685


Instant Generator for Java
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of Java. To
generate code by instant generator:
1. Select Tools > Instant Generator > Java... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for Java P. 686


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for Java P. 687


Description of instant generator dialog box

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.

Advanced Options dialog box

Instant Generator for Java P. 688


Below is a description of available options.

Option Description

Encoding The encoding of source file.

Follow Convention Whether to apply camel case Java naming convention.

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

Allow From Linked Project Check to generate also classes in referenced project.

Indentation Character(s) being used for indentation. Default is Tab .

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.

Local variable prefix The characters to be appended to local variables.

Association implementation The type of collection to be used for association.

JDK Version Generate code in a specific standard of JDK.

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.

Generics (Template) Whether to generate template or not.

A description of advanced options

Instant Generator for Java P. 689


Instant Generator C# source code
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of C# source
code. To generate code by instant generator:
1. Select Tools > Instant Generator > C# ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant generate for C# source code P. 690


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant generate for C# source code P. 691


Description of instant generator dialog box

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.

Advanced Options dialog box

Below is a description of available options.

Option Description

Encoding The encoding of source file.

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.

Association implementation The type of collection to be used for association.

Create folder for namespace Create a directory in system for namespace

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

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

A description of advanced options

Instant generate for C# source code P. 692


Instant Generator for VB.NET source code
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of VB.NET. To
generate code by instant generator:
1. Select Tools > Instant Generator > VB.NET ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant generate for VB.NET source code P. 693


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant generate for VB.NET source code P. 694


Description of instant generator dialog box

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.

Advanced Options dialog box

Below is a description of available options.

Option Description

Encoding The encoding of source file.

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.

Association implementation The type of collection to be used for association.

Create folder for namespace Create a directory in system for namespace

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

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

A description of advanced options

Instant generate for VB.NET source code P. 695


Instant Generator for PHP source code
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of PHP. To
generate code by instant generator:
1. Select Tools > Instant Generator > PHP ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for PHP source code P. 696


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for PHP source code P. 697


Description of instant generator dialog box

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.

Advanced Options dialog box

Instant Generator for PHP source code P. 698


Below is a description of available options.

Option Description

Encoding The encoding of source file.

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

Allow From Linked Project Check to generate also classes in referenced project.

Indentation Character(s) used for indentation, default is Tab.

Generate unnamed attribute Whether to generate nameless attributes.

Unnamed attribute The naming pattern of nameless attributes.

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.

Local variable prefix The characters to be appended to local variables.

Directory Follow package - generate source in directory same as package's structure


Flat level - generate source in same directory ( only one directory )

A description of advanced options

Instant Generator for PHP source code P. 699


Instant Generator for ODL source code
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of ODL. To
generate code by instant generator:
1. Select Tools > Instant Generator > ODL ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for ODL source code P. 700


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for ODL source code P. 701


Description of instant generator dialog box

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.

Advanced Options dialog box

Below is a description of available options.

Option Description

Encoding The encoding of source file.

Allow From Linked Check to generate also classes in referenced project.


Project

A description of advanced options

Instant Generator for ODL source code P. 702


Instant Generator for ActionScript source code
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of ActionScript.
To generate code by instant generator:
1. Select Tools > Instant Generator > ActionScript ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for ActionScript source code P. 703


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for ActionScript source code P. 704


Description of instant generator dialog box

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.

Advanced Options dialog box

Instant Generator for ActionScript source code P. 705


Below is a description of available options.

Option Description

Encoding The encoding of source file.

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

Allow From Linked Project Check to generate also classes in referenced project.

Indentation Character(s) being used for indentation. Default is Tab .

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.

Local variable prefix The characters to be appended to local variables.

ActionScript Version Generate code in a specific standard of action script.

A description of advanced options

Instant Generator for ActionScript source code P. 706


Instant Generator for IDL source code
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of IDL. To
generate code by instant generator:
1. Select Tools > Instant Generator > IDL ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for IDL source code P. 707


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for IDL source code P. 708


Description of instant generator dialog box

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.

Advanced Options dialog box

Instant Generator for IDL source code P. 709


Below is a description of available options.

Option Description

Encoding The encoding of source file.

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

Allow From Linked Project Check to generate also classes in referenced project.

Indentation Character(s) being used for indentation. Default is Tab .

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.

A description of advanced options

Instant Generator for IDL source code P. 710


Instant Generator for C++ source code
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of C++. To
generate code by instant generator:
1. Select Tools > Instant Generator > C++ ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for C++ source code P. 711


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for C++ source code P. 712


Description of instant generator dialog box

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.

Advanced Options dialog box

Below is a description of available options.

Option Description

Encoding The encoding of source file.

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

Allow From Linked Project Check to generate also classes in referenced project.

Indentation Character(s) being used for indentation. Default is Tab .

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.

Instant Generator for C++ source code P. 713


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.

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.

Local variable prefix The characters to be appended to local variables.

Association implementation The type of collection to be used for association.

Standard ANSI C++ - Most general standard of C++


Visual C++ - Microsoft enhanced ANSI C++ and develop another standard

Using Template Whether to generate template or not.

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.

Folder Structure Follow Package Generate folders according to package structure.

Group By Visibility Group class members by their visibility.

A description of advanced options

Instant Generator for C++ source code P. 714


Instant Generator for Delphi source code
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of Delphi. To
generate code by instant generator:
1. Select Tools > Instant Generator > Delphi ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for Delphi source code P. 715


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for Delphi source code P. 716


Description of instant generator dialog box

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.

Advanced Options dialog box

Instant Generator for Delphi source code P. 717


Below is a description of available options.

Option Description

Encoding The encoding of source file.

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

Allow From Linked Project Check to generate also classes in referenced project.

Indentation Character(s) being used for indentation. Default is Tab .

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.

Local variable prefix The characters to be appended to local variables.

A description of advanced options

Instant Generator for Delphi source code P. 718


Instant Generator for Perl source code
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of Perl. To
generate code by instant generator:
1. Select Tools > Instant Generator > Perl ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for Perl source code P. 719


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for Perl source code P. 720


Description of instant generator dialog box

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.

Advanced Options dialog box

Instant Generator for Perl source code P. 721


Below is a description of available options.

Option Description

Encoding The encoding of source file.

Installation path The Perl installation path

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

Allow From Linked Project Check to generate also classes in referenced project.

Indentation Character(s) being used for indentation. Default is Tab .

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.

Local variable prefix The characters to be appended to local variables.

A description of advanced options

Instant Generator for Perl source code P. 722


Instant Generator for XML Schema file
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of XML
Schema. To generate code by instant generator:
1. Select Tools > Instant Generator > XML Schema ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for XML schema file P. 723


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for XML schema file P. 724


Description of instant generator dialog box

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.

Advanced Options dialog box

Below is a description of available options.

Option Description

Encoding The encoding of source file.

Allow From Linked Project Check to generate also classes in referenced project.

Indentation Character(s) being used for indentation. Default is Tab .

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.

Namespace Define a namespace for generated code.

A description of advanced options

Instant Generator for XML schema file P. 725


Instant Generator for Python source code
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of Python. To
generate code by instant generator:
1. Select Tools > Instant Generator > Python ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for Python source code P. 726


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for Python source code P. 727


Description of instant generator dialog box

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.

Advanced Options dialog box

Instant Generator for Python source code P. 728


Below is a description of available options.

Option Description

Encoding The encoding of source file.

Installation path The installation path of Python.

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

Allow From Linked Project Check to generate also classes in referenced project.

Indentation Character(s) being used for indentation. Default is Tab .

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.

Constructor Select the constructor to use

Python Version Generate code in a specific standard of Python.

A description of advanced options

Instant Generator for Python source code P. 729


Instant Generator for Objective-C source code
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of Objective-C.
To generate code by instant generator:
1. Select Tools > Instant Generator > Objective-C ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for Objective-C source code P. 730


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for Objective-C source code P. 731


Description of instant generator dialog box

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.

Advanced Options dialog box

Instant Generator for Objective-C source code P. 732


Below is a description of available options.

Option Description

Encoding The encoding of source file.

Explicit Type in Declaration hen checked, will generate attribute/parameter type with specified type or just id.

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

Allow From Linked Project Check to generate also classes in referenced project.

Indentation Character(s) being used for indentation. Default is Tab .

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.

Local variable prefix The characters to be appended to local variables.

Association implementation The type of collection to be used for association.

A description of advanced options

Instant Generator for Objective-C source code P. 733


Instant Generator for Objective-C 2.0 source code
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of Objective-C
2.0. To generate code by instant generator:
1. Select Tools > Instant Generator > Objective-C 2.0 ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for Objective-C 2.0 source code P. 734


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for Objective-C 2.0 source code P. 735


Description of instant generator dialog box

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.

Advanced Options dialog box

Below is a description of available options.

Option Description

Encoding The encoding of source file.

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

Allow From Linked Project Check to generate also classes in referenced project.

Indentation Character(s) being used for indentation. Default is Tab .

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.

Local variable prefix The characters to be appended to local variables.

A description of advanced options

Instant Generator for Objective-C 2.0 source code P. 736


Instant Generator for Ada95
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of Ada95. To
generate code by instant generator:
1. Select Tools > Instant Generator > Ada95 ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for Ada95 P. 737


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for Ada95 P. 738


Description of instant generator dialog box

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.

Advanced Options dialog box

Below is a description of available options.

Option Description

Encoding The encoding of source file.

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

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.

A description of advanced options

Instant Generator for Ada95 P. 739


Instant Generator for Ruby
Instant generator is the process of producing source code from class model. Designers or software architects can build a high level domain
class model, then pass to programmer to perform more lower-level system or application modeling, and eventually generate source code from
implementation model. This chain makes building software faster and cheaper. In this chapter, we will go through the instant generation of Ruby. To
generate code by instant generator:
1. Select Tools > Instant Generator > Ruby ... from the main menu.

Open instant generator

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.

Select 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.

Overview of Instant Generator

Instant Generator for Ruby P. 740


Overview of instant generator dialog box

No. Name Description

1 Language The programming language to generate.

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.

11 Generate Click to start generation.

12 Close Click to close the instant generator.

Instant Generator for Ruby P. 741


Description of instant generator dialog box

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.

Advanced Options dialog box

Below is a description of available options.

Option Description

Encoding The encoding of source file.

Attribute prefix The text to append to attribute name as prefix.

Parameter prefix The text to append to parameter name as prefix.

Allow From Linked Project Check to generate also classes in referenced project.

Indentation Character(s) being used for indentation. Default is Tab .

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.

A description of advanced options

Instant Generator for Ruby P. 742


Customizing code generation
Instant generator allows you to generate programming source code from class models. Basically, the content of the generated code follows the
common coding convention of the programming language. There are also advanced options for you to configure some of the specific settings in
forming the code, like the use of prefix for attributes and parameters.
Although the built-in way of generating source code can satisfy most of the general needs, you may want to define something more specific. For
example, you may need to print a copyright statement at the beginning of the code file, which is not a kind of customization being supported by Instant
generator.
Fortunately, the way of how source code will be generated is handled by Apache Velocity engine, a templating engine, and the templates being used
are fully opened for customization. In the following sections, we will explain how to customize a template to make the generated code follow your
requirement.

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.

Setting up development environment


The template files are put under the resources/instantgenerator folder of VP Suite installation directory. It is absolutely alright to edit those files
directly. However, it is recommended to setup your own development environment, copy the template files to there to perform further editing. There are
two reasons for separating the development environment from VP Suite:
• Avoid the unexpected template removal by un-installing the VP Suite.
• Avoid accidental file replacement by running product updates.
To setup your development environment:
1. Create a folder as working directory.
2. Explore %VP-Suite-Installation-Directory%/resources/instantgenerator.
3. You will see a number of sub-folders that have the programming language as their names. Each of them contains the templates files for a
specific programming language. Copy the folder(s) of the language(s) you need to customize and paste at the working directory.

Copy folder

Customizing code generation P. 743


Customizing template
By having the text editor and the development environment ready, it&rsquo;s time to get your hand dirty with editing the template. As mentioned before,
Instant generator adopted the Apache Velocity engine in generating source code. For those who are interested in knowing how to write templates,
please read Velocity&rsquo;s Users&rsquo; guide at:
http://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html .
The following example demonstrates how to edit the PHP code generation template to reposition the brace of operation blocks to a new line.

Customization of operation in PHP class

1. Open the template you need to edit in text editor.

Open PhpOperation.vm in text editor

At the beginning, you may find the template a bit complex. But once you start working on it for a while, you&rsquo;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.

Customizing code generation P. 744


2. Look for the area that you need to edit.

Search for the open branch

3. Make change.

Insert line breaks

Customizing code generation P. 745


4. Add a variable $indentation to indicate the need of printing indentation before the open brace.

Add variable

5. Save the file.

Generate code with the customized template


To generate code with customized template:
1. In VP-UML, select Tools > Instant Generator, then the programming language that have the template customized.
2. Specify the Template directory where the customized templates are stored.

Specifying template directory

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.

List of API calls


The following table lists the available API calls for retrieving data from models.

Class API Return Value

Annotation commentArray() Comment[]

commentAt(int) Comment

commentCount() int

commentIterator() Iterator

Customizing code generation P. 746


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

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

AnnotationProperty 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

getValue() String

hasStereotype(String) boolean

hasStereotypeIgnoreCase(String) boolean

hasTaggedValue(String) boolean

hasTaggedValueIgnoreCase(String)boolean

isFromLinkedProject() boolean

stereotypeArray() Stereotype[]

Customizing code generation P. 747


stereotypeAt(int) Stereotype

stereotypeCount() int

stereotypeIterator() Iterator

taggedValueArray() TaggedValue[]

taggedValueAt(int) TaggedValue

taggedValueCount() int

taggedValueIterator() Iterator

Association associationClassArray() AssociationClass[]

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

Customizing code generation P. 748


taggedValueArray() TaggedValue[]

taggedValueAt(int) TaggedValue

taggedValueCount() int

taggedValueIterator() Iterator

toAssociationClassArray() Object[]

toAssociationClassAt(int) AssociationClass

toAssociationClassCount() int

toAssociationClassIterator() Iterator

AssociationClass commentArray() Comment[]

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

AssociationEnd commentArray() Comment[]

commentAt(int) Comment

commentCount() int

commentIterator() Iterator

getAggregationKind() String

getDocumentation() String

Customizing code generation P. 749


getMultiplicity() 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

Attribute annotationArray() Object[]

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

Customizing code generation P. 750


getMultiplicity() 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

Customizing code generation P. 751


isVolatile() 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

AttributeType commentArray() Comment[]

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

Class annotationArray() Object[]

Customizing code generation P. 752


annotationAt(int) Annotation

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

Customizing code generation P. 753


getStereotype(String) Stereotype

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[]

Customizing code generation P. 754


stereotypeAt(int) 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

Comment commentCount() int

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[]

Customizing code generation P. 755


stereotypeAt(int) Stereotype

stereotypeIterator() Iterator

taggedValueCount() int

taggedValueArray() TaggedValue[]

taggedValueAt(int) TaggedValue

taggedValueIterator() Iterator

DataType 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

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

ElementType commentArray() Comment[]

commentAt(int) Comment

commentCount() int

commentIterator() Iterator

getBlock() String

getDocumentation() String

getForm() String

Customizing code generation P. 756


getName() 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

Generalization commentArray() Comment[]

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

Customizing code generation P. 757


stereotypeCount() int

stereotypeIterator() Iterator

taggedValueArray() TaggedValue[]

taggedValueAt(int) TaggedValue

taggedValueCount() int

taggedValueIterator() Iterator

ImplModel commentArray() Comment[]

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

Object 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

Customizing code generation P. 758


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

Operation annotationArray() Object[]

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

Customizing code generation P. 759


getVisibility() String

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

Customizing code generation P. 760


raisedExceptionArray() Object[]

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

Package classArray() Class[]

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

Customizing code generation P. 761


stereotypeCount() int

stereotypeIterator() Iterator

taggedValueArray() TaggedValue[]

taggedValueAt(int) TaggedValue

taggedValueCount() int

taggedValueIterator() Iterator

templateParameterArray() Object[]

templateParameterAt(int) TemplateParameter

templateParameterCount() int

templateParameterIterator() Iterator

Parameter annotationArray() Object[]

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

Customizing code generation P. 762


stereotypeArray() Stereotype[]

stereotypeAt(int) Stereotype

stereotypeCount() int

stereotypeIterator() Iterator

taggedValueArray() TaggedValue[]

taggedValueAt(int) TaggedValue

taggedValueCount() int

taggedValueIterator() Iterator

Realization commentArray() Comment[]

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

Stereotype commentArray() Comment[]

commentAt(int) Comment

commentCount() int

commentIterator() Iterator

getDocumentation() String

getName() String

Customizing code generation P. 763


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

TaggedValue 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

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

Customizing code generation P. 764


taggedValueCount() int

taggedValueIterator() Iterator

TemplateParameter commentArray() Comment[]

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

Customizing code generation P. 765


commentIterator() Iterator

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

TemplateTypeBindInfo commentArray() Comment[]

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

Customizing code generation P. 766


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

Text 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

stereotypeArray() Stereotype[]

stereotypeAt(int) Stereotype

stereotypeCount() int

stereotypeIterator() Iterator

taggedValueArray() TaggedValue[]

taggedValueAt(int) TaggedValue

taggedValueCount() int

taggedValueIterator() Iterator

TextType commentArray() Comment[]

commentAt(int) Comment

commentCount() int

commentIterator() Iterator

getDocumentation() String

getName() String

Customizing code generation P. 767


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

A list of API calls

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=====
${...}

Customizing code generation P. 768


Generate/Update Java code
Round-trip engineering is the ability to generate model from source code and generate source code from model, and keep them synchronized. You can
make use of round-trip engineering to keep your implementation model and source code up-to-date, so as to produce up-to-date documentation on
your model.

Generating/Updating code from whole project


You can generate Java code from all classes in current project. To generate code from project:
1. Select Tools > Java Round-trip > Generate Code... from the main menu.

Generate code for a project

Generate or Update Java code from UML classes P. 769


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>.

The mappings between models and source paths are defined

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: Documentation in model elements is generated as comment in code.

Generating/Updating code from opening class diagram


You can generate Java code from an opening class diagram that contains the class(es) you want to generate code. To generate code from class
diagram:
1. Right click on the class diagram background and select Utilities > Java Round-trip > Generate Code from the popup menu.

Generate or Update Java code from UML classes P. 770


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>.

The mappings between models and source paths are defined

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.

NOTE: Documentation in model elements is generated as comment in code.

Generating/Updating code from chosen classes


You can generate Java code from specific class or classes. To generate code from class/classes:

Generate or Update Java code from UML classes P. 771


1. Select the class(es) and right click on them, then select Java Round-trip > Generate Code from the popup menu.

To generate code for classes

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>.

The mappings between models and source paths are defined

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).

Generate or Update Java code from UML classes P. 772


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: Documentation in model elements is generated as comment in code.

An overview of Generate Code dialog box

An overview of Generate Code dialog box

No. Name Description

1 Language The programming language of the source code to generate.

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.

3 Remove model-to-source-path mapping Click to remove chosen model-to-source-path mapping.

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.

9 OK Click to start generation.

10 Cancel Click to close the Generate Code dialog without generating code.

A description of Generate Code dialog box

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

Generate or Update Java code from UML classes P. 773


Code configuration

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

Java Collection • Array - Generate one-to-many relationship as array


• Collection - (default) Generate one-to-many relationship as collection

Use generic collections (default true) Allow to use generic collection

Generate annotation on • Property method - Generate annotation on property method

Generate or Update Java code from UML classes P. 774


• Field - Generate annotation on field

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

A description of code configuration

Brace and Indentation

Brace and indentation configuration

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

Generate or Update Java code from UML classes P. 775


• Next line - Brace for annotation type appear at the line after the declaration

Indentation policy • Tabs - (default) Use a tab of space as indentation


• Spaces - Use spaces as indentation. The number of spaces can be defined below

Indentation size The number of spaces to indent

A description of brace and indentation configuration

New Lines

New lines configuration

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

Generate or Update Java code from UML classes P. 776


A description of new lines configuration

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.

A description of template configuration

Generate or Update Java code from UML classes P. 777


To ignore classes in generation
You can make certain UML class not to generate code against code generation by ignoring them. To ignore class(es), click Ignore Classes... in
Generate Code dialog box. In the second Generate Code dialog box that popped up, select the class(es) to ignore and click > to move them to the
ignore list. Click OK to confirm.

The class IgnoreMe is ignored

Generate or Update Java code from UML classes P. 778


Generate/Update UML classes from Java code
Round-trip engineering is the ability to generate model from source code and generate source code from model, and keep them synchronized. You can
make use of round-trip engineering to keep your implementation model and source code up-to-date, so as to produce up-to-date documentation on
your model.

Generate/Update UML classes from code


You can produce UML classes from source code, or to update from code all the reversed UML classes in project. To do this:
1. Select Tools > Java Round-trip > Reverse Code... from the main menu.

Reverse code to UML classes

Generate or update UML classes from Java code P. 779


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>.

The mappings between source paths and model are defined

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.

Generate or update UML classes from Java code P. 780


Updating UML classes on a class diagram from code
Once you have performed round-trip engineering for once, you can update UML class(es) on a diagram from source code for reflecting the changes
made in code. To update, right click on the background of the class diagram for update and select Utilities > Java Round-trip > Reverse Code from
the popup menu.

To update UML classes in a diagram from code

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.

Generate or update UML classes from Java code P. 781


Updating specific UML classes from code
Once you have performed round-trip engineering for once, you can update specific UML class(es) from source code for reflecting the changes made
on that particular class(es) To update, select in class diagram the UML class(es) you want to update. Right click on them and select Java Round-trip >
Reverse Code from the popup menu.

To update specific UML class from code

An overview of Reverse Code dialog box

An overview of Reverse Code dialog box

No. Name Description

1 Language The programming language of the source code to reverse.

Generate or update UML classes from Java code P. 782


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.

3 Remove source-path-to-model mapping Click to remove chosen source-path-to-model mapping.

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.

8 OK Click to start reversal.

9 Cancel Click to close the Reverse Code dialog without reversing code.

A description of Reverse Code dialog box

On-demand reverse engineering


Consider if you have a project that contains million of Java source file, and now you want to re-develop just a few classes in it. If you try to reverse the
whole project it will take you a long time to complete the reverse due to the amount of classes (and relationships) are just too many. With on-demand
reverse engineering, you will reverse the sources as indexes, and obtain an index tree in class repository. No actual UML classes will be reversed until
you trigger the reverse manually. This reduces the processing time significantly.
To perform on-demand reverse engineering, make sure the option Reverse source on demand is checked in the Reverse Code dialog box.

The option Reverse source on demand


that appear in reverse dialog box

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.

Reverse a java source file from index tree

Generate or update UML classes from Java code P. 783


Generate/Update C++ code
Round-trip engineering is the ability to generate model from source code and generate source code from model, and keep them synchronized. You can
make use of round-trip engineering to keep your implementation model and source code up-to-date, so as to produce up-to-date documentation on
your model.

Generating/Updating code from whole project


You can generate C++ code from all classes in current project. To generate code from project:
1. Select Tools > C++ Round-trip > Generate Code... from the main menu.

To generate code for a project

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>.

The mappings between models and source paths are defined

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.

Generate or Update C++ code from UML classes P. 784


NOTE: Documentation in model elements is generated as comment in code

Generating/Updating code from opening class diagram


You can generate C++ code from an opening class diagram that contains the class(es) you want to generate code. To generate code from class
diagram:
1. Right click on the class diagram background and select Utilities > C++ Round-trip > Generate Code from the popup menu.
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>.

The mappings between models and source paths are defined

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.

NOTE: Documentation in model elements is generated as comment in code

Generating/Updating code from chosen classes


You can generate C++ code from specific class or classes. To generate code from class/classes:

Generate or Update C++ code from UML classes P. 785


1. Select the class(es) and right click on them, then select C++ Round-trip > Generate Code from the popup menu.

To generate code for classes

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>.

The mappings between models and source paths are defined

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.

Generate or Update C++ code from UML classes P. 786


4. Click OK to proceed with generation.

NOTE: Documentation in model elements is generated as comment in code

An overview of Generate Code dialog box

An overview of Generate Code dialog box

No. Name Description

1 Language The programming language of the source code to generate.

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.

3 Remove model-to-source-path mapping Click to remove chosen model-to-source-path mapping.

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.

9 OK Click to start generation.

10 Cancel Click to close the Generate Code dialog without generating code.

A description of Generate Code dialog box

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

Generate or Update C++ code from UML classes P. 787


Code configuration

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

A description of code configuration

Brace and Indentation

Generate or Update C++ code from UML classes P. 788


Brace and indentation configuration

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

Indentation policy • Tabs - (default) Use a tab of space as indentation


• Spaces - Use spaces as indentation. The number of spaces can be defined below

Indentation size The number of spaces to indent

A description of brace and indentation configuration

New Lines

Generate or Update C++ code from UML classes P. 789


New lines configuration

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

A description of new lines configuration

Template

Generate or Update C++ code from UML classes P. 790


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.

A description of template configuration

Generate or Update C++ code from UML classes P. 791


To ignore classes in generation
You can make certain UML class not to generate code against code generation by ignoring them. To ignore class(es), click Ignore Classes... in
Generate Code dialog box. In the second Generate Code dialog box that popped up, select the class(es) to ignore and click > to move them to the
ignore list. Click OK to confirm.

The class IgnoreMe is ignored

Generate or Update C++ code from UML classes P. 792


Generate/Update UML classes from C++ code
Round-trip engineering is the ability to generate model from source code and generate source code from model, and keep them synchronized. You can
make use of round-trip engineering to keep your implementation model and source code up-to-date, so as to produce up-to-date documentation on
your model.

Generate/Update UML classes from code


You can produce UML classes from source code, or to update from code all the reversed UML classes in project. To do this:
1. Select Tools > C++ Round-trip > Reverse Code... from the main menu.

To reverse code to UML classes

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>.

The mappings between source paths and model are defined

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.

Generate or update UML classes from C++ code P. 793


Updating UML classes on a class diagram from code
Once you have performed round-trip engineering for once, you can update UML class(es) on a diagram from source code for reflecting the changes
made in code. To update, right click on the background of the class diagram for update and select Utilities > C++ Round-trip > Reverse Code from
the pop-up menu.

To update UML classes in a diagram from code

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.

Generate or update UML classes from C++ code P. 794


Updating specific UML classes from code
Once you have performed round-trip engineering for once, you can update specific UML class(es) from source code for reflecting the changes made
on that particular class(es) To update, select in class diagram the UML class(es) you want to update. Right click on them and select C++ Round-trip >
Reverse Code from the pop-up menu.

To update specific UML class from code

An overview of Reverse Code dialog box

An overview of Reverse Code dialog box

No. Name Description

1 Language The programming language of the source code to reverse.

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.

Generate or update UML classes from C++ code P. 795


3 Remove source-path-to-model mapping Click to remove chosen source-path-to-model mapping.

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.

8 OK Click to start reversal.

9 Cancel Click to close the Reverse Code dialog without reversing code.

A description of Reverse Code dialog box

On-demand reverse engineering


Consider if you have a project that contains million of C++ source file, and now you want to re-develop just a few classes in it. If you try to reverse the
whole project it will take you a long time to complete the reverse due to the amount of classes (and relationships) are just too many. With on-demand
reverse engineering, you will reverse the sources as indexes, and obtain an index tree in class repository. No actual UML classes will be reversed until
you trigger the reverse manually. This reduces the processing time significantly.
To perform on-demand reverse engineering, make sure the option Reverse source on demand is checked in the Reverse Code dialog box.

The option Reverse source on demand


that appear in reverse dialog box

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.

Reversing a C++ source file from index tree

Generate or update UML classes from C++ code P. 796


Database configuration
Opening database configuration dialog
Select Tools > Object-Relational Mapping (ORM) > Database Configuration... from the main menu.

Database configuration

Database Configuration P. 797


Selecting database
In the Database Configuration dialog box, check the target database.

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.

Set as default database

Downloading JDBC driver


If the JDBC driver is free and available to public, VP-UML can help you to download it automatically. Click the Download or Update button under
Database Setting section.

Download JDBC driver

Database Configuration P. 798


Configure proxy if required, click OK button to continue download.

Download JDBC proxy setting

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.

Downloaded JDBC driver

Testing connection
After configure the database setting, click the Test Connection button to confirm the setting is valid.

Test connection

If it's successful, a dialog will show connect successful.

Database Configuration P. 799


Generating SQL for selected entities
Generating SQL
Select multiple entities on the diagram, right click on one of them and select Generate SQL... from the pop-up menu.

Generate SQL

Generating SQL for selected entities P. 800


The Generate SQL dialog box shows the DDL and DML for the selected entities.

Generate SQL dialog box

DDL and DML


DDL stand for Data Definition Language, include create, drop and alter statements. DML stand for Data Manipulating Lanauge, include select, insert,
update, delete statements.
The generated DDL statements can directly execute to database without any modification. Generate alter statement require connection to database,
query the object from database and compare with the ERD. The alter statements are not generated by default, you can click the Generate button to
generate on demand.

Generate alter statements

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.

Generating SQL for selected entities P. 801


After change the database, the SQL will re-generate for the selected database.

SQL updated

Generate SQL options


There are several option on the top of the Generate SQL dialog box.

Generate SQL options

• 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

Generating SQL for selected entities P. 802


• Formatted SQL - formatted sql generate high readability SQL statements. If you check it, the SQL will become:

Formatted SQL

Using toolbar
There is a toolbar above each group of statements.

Generate SQL toolbar

• Save to file - Save the generated SQL to file.


• Copy - Copy the generated SQL to clipboard.
• Revert - The textbox of SQL is editable, you can modify before execute. The Revert button allows you to undo the user modification.
• Execute - Execute the statements in the textbox to database.

Generating SQL for selected entities P. 803


Generating SQL for project
Select Tools > Object-Relational Mapping (ORM) > Generate Database... from the main menu.

Generate database

Generating SQL for project P. 804


The Database Code Generation dialog box provides several options to generate DDL and export to database.

Database Code Generation dialog box

• 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.

• Export to database - execute the generated statements directly to database.


• Generate DDL - save the generated statements to a file.
• Generate Comment - generate comment of tables/columns to database/DDL (only available to My SQL, DB2, Oracle, Postgre SQL)
• Upper Case SQL - generate upper case for keyword (e.g. select, from, update, insert...etc).
• Formatted SQL - generate pretty format, high readability SQL.
• Quote SQL Identifier - if database object name is reserved word, it must be quoted; otherwise, it cannot be used as the object name:
• Auto - auto detect and quote the name only if it is reserved word.
• Yes - always quote the name.
• No - never quote the name.

• Table Charset (Only available for MySQL) - the charset used for database connection.

Generating SQL for project P. 805


• Connection:

Connection

• JDBC - a standard way to connect database in Java.


• Datasource - the database connection is managed by application server.

Generating SQL for project P. 806


Generating alter statements
Generate alter statements helps you to update the database with the changes on ERD. With the generate DDL option, you can preview a list of alter
statements before actually applies to the database.
1. Select Tools > Object-Relational Mapping (ORM) > Generate Database... from the main menu to open Database Code Generation dialog
box.
2. As a result, the Database Code Generation dialog box is opened.

Database Code Generation dialog box is opened

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

Generating alter statements P. 807


5. Click OK button to generate. Assume some tables and columns were created in database already. The following is the example of generated
statements:

Alter statements

Generating alter statements P. 808


Export and import database configuration between projects
Export and import database configuration allows you to reuse the same database configuration across projects, without the needs to re-define the
configuration in each project.
1. Select Tools > Object-Relational Mapping (ORM) > Database Conguration... from the main menu to open Database Configuration dialog
box.
2. In the Database Configuration dialog box, select database(s) and define their settings.

Database Configuration dialog box

3. Click the Export... button and specify the filen ame to save the setting.

Click Export button

4. Create a new project.


5. Open Database Configuration dialog again, the setting is blank now.
6. Click the Import... button and select the previously saved file.
7. The setting was imported to current project.

Export and import database configuration between projects P. 809


Entering and generating default data
VP-UML let you design your database with entity relationship diagram (ERD), and finally generate the design to database as database schema. On top
of the schema that will be generated, you can also specify default data to add to database upon database generation.

Entering default data


Default data has to be entered in the table record editor. To enable the editor, right click on the background of diagram and selecting Show Table
Record Editor from the popup menu.

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

Entering and generating default data P. 810


Selecting foreign key value
To select a foreign key value, click on the cell to popup the drop down menu, and select the value from the menu.

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

Entering and generating default data P. 811


Validating records
Record validation helps verify the correctness of entered data. To validate, click on the Validate records button.

Caption Here

If anything wrong is detected, the Message pane will popup and a message will appear in it.

Caption Here

Generating default data


To generate sample data to database:
1. Select Tools > Object-Relational Mapping (ORM) > Generate Database... from the main menu.
2. Check Export to database and Generate sample data. If you are creating the database the first time, select Create Database for the drop
down menu of Generate Database. If you just want to generate data to a previously created database, select Update Database.

Caption Here

3. Click OK to continue.

Entering and generating default data P. 812


Reversing database
1. Create a new project.
2. Select Tools > Object-Relational Mapping (ORM) > Reverse Database... from the main menu.

Reverse database

3. In the Database to Data Model dialog box, select Reverse Table and click Next > button to continue.

Check Reverse Table

Reversing database P. 813


4. Fill in the database setting and click Next > button.

Database setting

5. Select the Selected Schema and check the schema containing your tables, and then click Next > button.

Select schema

Reversing database P. 814


6. Select the tables you want to reverse and click the Finish button to start reverse.

Select tables

7. After reverse, a new Entity Relationship Diagram is created automatically with a Reversed Entities dialog box.

Reversed entities

Reversing database P. 815


8. Select the tables and drag on the diagram.

Drag and drop tables to diagram

9. The tables were created on the diagram, click Close button to finish reversing database.

Reversed ERD

Reversing database P. 816


Reversing DDL
1. Create a new project.
2. Select Tools > Reverse DDL... from the main menu.

Reverse DDL

3. Fill in the filename of DDL and select database in Reverse DDL dialog box. Click OK button to continue.

Reverse DDL dialog box

Reversing DDL P. 817


4. An Entity Relationship Diagram is created with the reversed entities.

Reversed ERD

Reversing DDL P. 818


Generating code and database
1. Select Tools > Object-Relational Mapping (ORM) > Generate Code... from the main menu.

Generate code

Generating code and database P. 819


2. Fill in the Output Path and select code generation options.

Database code generation

• 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.

3. Click OK button to start code generation.

Generating code and database P. 820


Lazy collection setting
Setting lazy collection for association
1. Open specification dialog box of association.
2. Switch to ORM Association Detail tab, select Lazy or Extra for From lazy initialization or To lazy initialization, depending on which side
multiplicity is *. Lazy collection is fetched when the application invokes an operation upon that collection. Extra lazy supports individual elements
of the collection are accessed from the database as needed, rather than fetch the whole collection. If the value is Unspecified, it will follow the
default lazy collection setting described below.

Lazy collection setting

Setting default lazy collection when generating ORM


1. Open Database Code Generation dialog box.
2. Specify a value for Default Lazy Collection Initialization.

Default lazy collection setting

Lazy collection setting P. 821


Persistent API
The persistent API setting supports various styles for generated code. It can be configurated in Database Code Generation dialog box.

Persistent API setting

Static methods
Static methods generate all persistent methods in the persistent class, client can access the methods in the same persistent object.

Static methods

Persistent API P. 822


Factory class
Factory class generate save/delete/refresh methods in persistent class, other persistent methods that return persistent object are generated in factory
class.

Factory class

DAO
DAO generate all persistent methods in DAO class, a DAO class is generate for each persistent class.

DAO

Persistent API P. 823


DAO (with interface)
DAO (with Interface) generate all persistent methods signature in DAO interface. A DAO interface is generate for each persistent class, and a
corresponding DAO implementation class is generated with default persistent implement.

DAO (with Interface)

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.

Persistent API P. 824


Using generated code
The following sections demonstrate how to use the generate ORM code with factory method persistent API.

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:

Using generated code P. 825


Customizing getter and setter body
In generated ORM code, getters and setters will be generated for attributes added to every ORM Persistable class. Sometimes, you may want to
customize the method body of those getters and setters, like to apply security checking or to print a statement upon the updating of data. In these
cases, you can customize the getter and setter of attribute to add the code you want.

A part of the generated code, showing the getters and setters generated from attributes of an ORM Persistable class

To customize getter/setter of attribute:


1. Right click on the attribute that you want to customize its getter or setting and select Open Specification... from the popup menu.

Opening the specification of attribute

Customizing getter and setter body P. 826


2. Open the ORM Attribute Detail tab and enter the code body in Getter/Setter code sections.

Customizing the setter of attribute

When you generate code, you will see the entered code appended to the generated getter or setter.

Customized setter

Customizing getter and setter body P. 827


Modeling guidelines
A state machine involves a number of states as well as the transition of states. You can generate source code for a state machine by first creating a
controller class, then create sub-state machine diagram from the controller class, model the state machine. In this chapter, you will see how to model a
state machine readily for code generation. For the steps of code generation, read the next chapter.
Step 1 - Modeling controller class
A controller class is a class that is used for controlling and managing the activities within a use case. It also manage the states within the use case or
the system.

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.

To create a sub state machine diagram from controller class

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.

Open specification of transition

Modeling guidelines P. 828


2. At the bottom of the specification page, select the operation from the Operation drop down menu.

Select operation for transition

Repeat the steps to assign operations to all transitions.


Step 4 - Specifying method body for the entry/exit of state
You can specify the invokcation of method call when entering and exiting a state by updating the Entry and Exit properties of state. To do this:
1. Right click on the state and select Open Specification... from the popup menu.
2. Click on Edit... next to the Entry field.
3. In the specification, fill in the Body field by entering the methods to invoke. Click OK to confirm.

Specifying method for Entry

4. Repeat the steps on Exit.


Step 5 - Specifying method body for operation
Part of the method body of operations being assigned to transitions can be defined by editing the Effect property of a transition. To do this:
1. Right click on the transition where operation was assigned.
2. In the General page, click on Edit... next to the Effect field.
3. Fill in the Body. Click OK to confirm.
4. Click OK to confirm and go back to diagram.

Modeling guidelines P. 829


Generating state machine code
Once the controller class and state machine are modeled, you can generate state machine code for the controller and state machine. With the
generated state machine, you can run instant generator to produce other classes, like the model and view classes, and incooperate with the state
machine code.
To generate state machine code:
1. Select Tools > State Machine Code > Generate Code... from the main menu.

Generate state machine code

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.

An overview of Generate State Machine Code dialog box

Generating state machine code P. 830


An overview of Generate State Machine Code dialog box

No. Name Description

1 Class The controller class for generating state machine.

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

3 Language The programming language of code to generate.

4 Output Path The output path of state machine code.

5 Options Options for code generation. Below is a description:


Synchronized transition methods - By checking, it causes the generated code to:
• Java: add the synchronized keyword to the transition method declarations.
• VB.net: encapsulate the transition method's body in a SyncLock Me, End SyncLock block.
• C#: encapsulate the transition method's body in a lock(this) {...} block.
Generate try/catch - Uncheck to not generate try/catch code. You are recommended to keep this checked. Uncheck only in C++
applications where exceptions are not used.
Generate debug message - Adds debug output messages to the generated code.
Re-generate transition methods - Check to overwrite the transition methods in code, including the implementation.
Browse output directory after generate - Open the output path.
Auto create transition operations - If a transition is named, but does not have Operation assigned. By checking this option
operation will be created to the parent class, named as the transition name.
Generate sample - Generate sample files to guide you how to work with the generated file.
Generate diagram image - Generate PNG image for chosen state machine diagram.

6 OK Click to start code generation.

7 Cancel Click to close the Generate State Machine Code dialog box.

A description of Generate State Machine Code dialog box

Generating state machine code P. 831


Introduction of Impact Analysis
What is impact analysis?
Impact analysis is the technique to find out the potential influences that may happen when updating a design blueprint. For example, when we want to
update the use case model, we may also want to update the sequence diagrams which model how to achieve the user goals. There are two ways of
performing impact analysis in Visual Paradigm, analysis diagram and matrix.

How does impact analysis improves your work?


Impact analysis helps avoid unexpected consequences resulted by updating your design blueprint. Contrary to this, it lets you find out everything you
need to update along when a change is to be made.

Introduction of impact analysis P. 832


Analyzing a model element
We analyze a model element when we want to identify its related elements so as to foresee the potential impact that may cause on the model resulted
by modifying the model element. The term "related" here represents any kinds of connection that can have between two elements, such as a general
to-and-from relationship, a parent-child relationship, transitor, or even a sub-diagram relationship with a diagram.

To analyze a model element


By analyzing a model element, you can know its relationships with other elements. To analyze:
1. Right click on the diagram element we want to analyze, and select Related Elements > Analysis... from the pop-up menu.

Analyze a diagram element

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.

Analyzing a model element P. 833


2. The result of analysis will be presented in analysis diagram. In the Analysis dialog box, either select Create new diagram to present the result
in a new analysis diagram, or select to present in an existing analysis diagram. The check boxes at the Analyse section governs the type(s) of
relationship to be analyzed. Click OK when ready.

Create a diagram, or select an existing analysis diagram to present the result

Type Description

Transitor The transited element of the chosen element, or the element where the chosen element was transited from

Reference The shape or diagram references of the chosen element

Parent- The parent (e.g. package) or the child of the chosen element
Child

Sub- The sub-diagram(s) of the chosen element


diagram

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

Kinds of relationships that can analyze

Analyzing a model element P. 834


Reading analysis diagram
The result of analysis is shown in an analysis diagram.

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.

Analyzing a model element P. 835


Updating analyzed result
Once a model is refined, the previous analysis result may no longer reflecting the latest changes. Therefore, you need to update the analysis result in
order to perform impact analysis for the chosen element, on the latest model.
1. Move the mouse pointer over the node that you want to update its relationships with others.

To analyze a diagram element

NOTE: Besides the central node, you may update/show the relationships of other Model nodes on diagram, too.

2. Click on the Analyze resource icon.

To click on Analyse

3. Select a type of relationship to analyze.

To analyze all kinds of relationships

Updating analyzed result P. 836


Grouping of nodes
To make it easier to identify the relationships of a chosen element, you can group all relationships of a particular kind into a single node, eliminating the
connectors being shown on diagram. To group, right click on the background of analysis diagram, and select Presentation Options > Group By, and
then the type of node from the popup menu.

Select a kind of relationship to group by

Nodes of same type are grouped.

Diagrams are grouped

To ungroup, simply deselect the node type by walking through the same popup menu path.

Grouping of nodes P. 837


Opening view from node
When reading an analysis diagram, you may find the existence of related model element, or related diagrams, such as sub-diagram, of the chosen
model element. You can open the view of such related elements through the resource icons appear on top of nodes.

Opening a diagram of diagram node


1. Move the mouse pointer over a Diagram node.
2. Click on the Open Diagram resource icon.

To open diagram of Diagram node

This opens the diagram.

Opening a view of model node


1. Move the mouse pointer over a Model node.
2. Click on the Open View resource icon.

To open view of a Model node

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.

The Show View dialog box

Opening view from node P. 838


Creating a matrix
A matrix is a table, which shows the existence of relationships among model elements of particular types. By reading a matrix, you can tell easily
whether two model elements are related or not, and what kind of relationship they have.
1. Right click on Matrix Diagram, under the category Others in Diagram Navigator, and select New Matrix Diagram from the pop-up menu.

Create a new matrix diagram

Creating a Matrix P. 839


2. Configure the matrix.

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

on Available Models and click button to insert it/them in here.

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.

Fields for matrix configuration

3. Click OK button to form the matrix.

Creating a Matrix P. 840


Reading a matrix
Knowing how to read a matrix helps you understand your model better, and to perform further modifications more comfortably. In this chapter, we will
see how to read a matrix, and how to refine the matrix content with the help of functionalities like hiding columns and rows, and filter.
A matrix is a table, with rows and columns, both representing sets of model elements of specific types. A cell in table is an intersection of a row and
a column, which reflects the relationship of the row and column. If the cell is filled either by a tick, or by a kind of relationship (when a matrix was set
to match things by Relationship), this means that the model elements of the row and column are related. The type of relationship can be checked by
referring to the drop down menu at the top left of matrix.

Overview of a matrix diagram

No. Name Description

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.

6 Configure Click this button to configure the content to display in matrix.

7 By It shows how matrix will match against rows and columns.

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.

Description of matrix diagram

Reading a matrix P. 841


Exporting Excel
You can export Excel file from matrix, and analyze relationships between model elements in worksheet in Excel. To export Excel:
1. Click Export to Excel above the matrix, near the Configure button.

To Click Export to Excel

2. In the Export Excel dialog box, specify the output destination and click Save.

Reading a matrix P. 842


Generating report
Report generation is the process of producing a report for sharing your design work and model specification with teammates and clients. You can
generate reports in different formats such as HTML, PDF or MS Word for reading or publishing in different environments. They differ in file format, but
have the same layout. In this chapter, we will go through the core steps in report generation.
To generate a report:
1. Select Tools > Report from the main menu. Then select Generate HTML Report..., Generate PDF Report... or Generate Word Report...
depending on the type of report you want to generate.

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.

3. Select the grid(s) and/or diagram(s) to be included in report.

Select diagram to include in report

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.

Overview of report generation dialog box

Generating report P. 843


Overview of report generation dialog box

The bottom part of report generaition dialog box for MS Word report

No. Name Description

1 Content The main page of report generation that lets you select the diagram(s) to generate report.

2 Options Configurable options for detailed report configuration.

3 Page Setup The setup of layout of report.

4 Header/Footer The content of header and footer.

5 Document info To define document info.

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.

7 Use external template Click to link to an external template file.

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.

11 Output path The output path of report to be generated.

12 Launch viewer Check to open the report automatically after generation.

13 Available diagram list The list of diagrams in opening project.

14 Selected diagram list The list of diagrams selected to generate report.

15 Preview Preview of diagram being selected in the list of selected diagram

Generating report P. 844


16 Reset Reset changes made in this dialog box

17 Reset to default Reset changes made in this dialog box to default settings.

18 Set as default Set the settings in this dialog box to default.

19 Generate Click to generate report.

20 Cancel Click to close the report dialog box.

21 Apply Click to apply the changes made in report, causing reopening of this dialog box to restore the applied settings.

22 Help Click to read the help contents.

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).

Description of report generation dialog box

Generating MS Word report with template (MS Word report only)


At the bottom of the MS Word report generation dialog box, there is an option Word template path, with a text box next to it for filling in the path of
template file. A Word template file provides the start up contents and defines the style of report. During report generation, the generator will make a
copy of the template file, treat the copied file as base, append the generated content to the copied file, and save the file to the destination path. By
using a word template, you can define your own headers/footers, cover page, start up content, styles for your generated report.

A generated report with style defined in template applied

Generating report P. 845


Sorting diagrams in report
By default, diagrams show in report follows the order defined in diagram tree in the Generate PDF dialog box. We may, however, sort the diagrams to
make them appear in desired sequence. To sort diagram(s), select the diagram(s) to be ordered on the list at the center of dialog box, and click or
to sort.

Reorder diagram

Sorting shapes in report


Custom sorting
1. Select the diagram to sort and click to expand it.
2. Select the shape(s) to sort.
3. Click or to sort.

Sort shapes

Automatic sorting
1. Select the diagram to sort and click to expand it.

Generating report P. 846


2. Select from the drop down menu Sort element a way to sort.

Select the way to sort shape

Way of sorting Description

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 .

Different ways of sorting

Generating report P. 847


Configuring report
Report generation can be configured to make the output more close to your expectation. Common configuration options include whether to generate
table of contents/figure or not, whether to generate shape/diagram type as icon or text, and whether to generate a particular type of detail such as
children. Besides configuration options, you can also adjust the page setup, design the cover page and define header/footer. In this chapter, we will go
through all the options one by one.

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.

Configuring report P. 848


Generate reference (file/URL) link Select to generate links for referenced files/URLs defined in models.

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.

Details Select a kinds of content to generate it.


Children - Everything a shape is containing. When selected, you can further select
Model-based or Diagram-based for controlling the scope of children. Model-
based consider all children the model of view contained. Diagram-based only
consider the view in generating diagram. Let say if you have a package containing
several classes. By selecting Model-based, all classes will be considered. By
selecting Diagram-based, only the classes that are contained by the package in the
generating diagram will be considered.
Members - Attributes and operations are example of members.
Properties - Name, documentation, abstract, leaf are example of properties.
Relationships - Association, dependency are example of relationships
References - File, diagram, folder, URL, shape are possible kinds of reference
References documentation - Determine whether to generate the referenced shape/
diagram's documentation in reference table
Sub-diagrams - Sub-diagrams of a shape
Comments - Comments of shape
Tagged values - Tagged values of shape
ORM Class Details - ORM class details specialized for ORM Persistable class
Use Case Details - Use case details of use case

Anti-aliasing Determine the quality of report content.


Graphics - To enable/disable the graphic anti-aliasing of the diagram images.
Text - To enable/disable the text anti-aliasing of the diagram images.

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.

A description of general options

Configuring report P. 849


Page Setup
Page setup controls the layout of report. You can adjust a report size, page orientation and margin.

Page setup

Option Description

Page size To select the paper size of the generated report.

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.

A description of options of page setup

Configuring report P. 850


Cover Page (Front Page for HTML report generation)
Cover page is the first page of report. You can add your company logo there, and enter the report title, organization namd and author name. Notice that
in HTML report generation, the tab Cover Page is named as Front Page.

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.

Title The title text

Organization name The organization name text

Author name The author name text

A description of options of cover page

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.

Configuring report P. 851


Instead of typing in the content of header/footer, there are a set of variables for you to apply with. The following table provides you with description with
each of the variable.

Header/Footer

Variable Name Description

Selection font Font settings of selected content

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.

A description of variables that can be used in header and footer

Configuring report P. 852


Document Info
For HTML report, document info refers to the meta information of HTML document. For PDF and MS Word report, document info refers to the possible
document properties that can be defined.

Document info

Option Description

Title The title of report.

Author The author of the report. This option is only available to PDF report.

Subject The subject of the report.

Keywords The keywords of the 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.

A description of document info

Configuring report P. 853


Customizing report
Instead of generating a report in a way that VP-UML defined for you, you can develop report templates to customize the report content, to make output
match your needs. With report customization, you can select model elements and properties to generate to report. You also can add custom text
content. To customize report:
1. Select Tools > Report from the main menu. Then select Generate HTML Report..., Generate PDF Report... or Generate Word Report...
depending on the type of report you want to generate.

Open report generator

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

5. Click Save to save your work.


6. Click Close.

An overview of tools in template editor


Tool Name Description

Save Save the opening template.

Save as Save the opening template as a new one.

Exoprt To export the opening template to a report template file (.vpr). You can import the file to other machines for
reusing it.

Customizing report P. 854


Add diagram loop To add a component to template editor, indicating the need of looping specific type(s) of diagram.

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.

Options Configure report options.

Description of differnet tools in template editor

Ignoring specific diagrams/shapes


A report template is independent of any project file. But if you try to apply a template on a project, you can ignore generating specific diagrams or
shapes in that project. To ignore specific diagrams/shapes:
1. Open the template in template editor.
2.
Preview the report by pressing or from the toolbar.
3. In the report structure tree, select the diagrams or shapes that you want to ignore in generated report.
4. Right click on your selection and de-select Generate from the popup menu.

To not generate model elements

More about Preview


When you try to preview a template, it tries to apply the template on the opening project to form the report structure and to render the preview. Due to
the connection between template and project, there are several actions that you can perform with the preview.
Ignoring specific diagrams/shapes

Customizing report P. 855


In the report structure tree, right click on the diagram(s) or shape(s) that you want to ignore when generating report and de-select Generate from the
popup menu.
Reordering diagrams/shapes
In the report structure tree, right click on the diagram(s) or shape(s) that you want to re-order and select Move Up or Move Down to reposition them.

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

Customizing report P. 856


Export/import report template
You can apply a report template on another project by exporting it as a report template file, and importing it to the target project. To export and import
template:
1. Open the report template in template editor.

To open a template in template editor

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.

Export/import report template P. 857


Diagram loop
A diagram loop is a component in a report template, indicating the need of looping (i.e. walking through) specific type(s) of diagram. For example, to
loop all use case diagrams and class diagrams in a project. Diagram loop means nothing more than just to loop diagram. The content to print for each
diagram being looped is to be determined by the children components of loop.

Looping diagrams in project


To loop specific type(s) of diagrams in project, create diagram loop at template root. To create diagram loop at template root:
1.
In the template editor, click on the on toolbar.
2.
On the right hand side of the template editor, select the type of diagram(s) to loop and click to confirm the selection.

Select to loop use case diagram

Including use case scheduling,ranks, stereotypes and various grid in report


Use case scheduling, use case ranks, stereotypes and various grid fall into the category of diagram. If you want to print them to report, follow the steps
as described in the previous section, and to select the appropriate content to include at the final step.

Choosing to include information of use case ranks in template

Looping sub-diagrams of specific element


Instead of looping diagrams in a project, you can also place diagram loop under an element loop to loop for sub-diagrams of specific type(s) of model
element. To create diagram loop under an element loop:
1. Select the element loop that you want to loop for its sub-diagrams.

Selecting an element loop

Diagram loop P. 858


2. Click on the Add Diagram Loop button from the toolbar of element loop.

Adding a diagram 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, select the type of sub-diagram(s) to loop and click to confirm the selection.

Switching from diagram loop to diagram summary table/paragraph


A diagram summary indicates the need of looping specific type(s) of diagram for constructing a tabular diagram summary, while a diagram paragraph
indicates the need of looping specific type(s) of diagram for constructing paragraphs of properties.
You can convert a diagram loop to diagram summary table or paragraph by right clicking on a diagram loop and selecting Change to Summary Table/
Paragraph from popup menu.

To convert a diagram loop to diagram summary table/paragraph

Diagram loop P. 859


Diagram summary
A diagram summary is a component in a report template, indicating the need of looping (i.e. walking through) specific type(s) of diagram, and
presenting their properties in tabular form. For example, to loop all use case diagrams in a project and form a table consisting of diagram names and
documentation. By default, a table of diagram names will be printed. You are expected to add property column(s) under a diagram summary to indicate
the diagram properties to print in the table.

Showing a property table for diagrams in project


To loop specific type(s) of diagrams in project for listing their properties in a table, create diagram summary at template root. To create diagram
summary at template root:
1.
In the template editor, click on the on toolbar.
2.
On the right hand side of the template editor, select the type of diagram(s) to loop and click to confirm the selection.

Select to loop use case diagram

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.

To add a property column in diagram summary

Switching from diagram summary to diagram loop/paragraph


A diagram loop indicates the need of looping specific type(s) of diagram, while a diagram paragraph indicates the need of looping specific type(s) of
diagram for constructing paragraphs of properties.
You can convert a diagram summary to diagram loop or paragraph by right clicking on a diagram summary and selecting Change to Diagram Loop/
Paragraph from pop-up menu.

To convert a diagram summary to diagram loop/paragraph

Diagram summary P. 860


Diagram paragraph
A diagram paragraph is a component in a report template, indicating the need of looping (i.e. walking through) specific type(s) of diagram, and
presenting their properties in paragraph form. For example, to loop all use case diagrams in a project and print out their documentation and last
modified data in a paragraph, one paragraph per diagram. You are expected to add property value(s) under a diagram paragraph to indicate the
diagram properties to print out.

Showing a property paragraph for diagrams in project


To loop specific type(s) of diagrams in project for listing their properties in paragraph form, create diagram paragraph at template root. To create
diagram paragraph at template root:
1.
In the template editor, click on the on toolbar.
2.
On the right hand side of the template editor, select the type of diagram(s) to loop and click to confirm the selection.

Select to loop use case diagram

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.

To add a property value in diagram paragraph

Switching from diagram paragraph to diagram summary table/loop


A diagram summary indicates the need of looping specific type(s) of diagram for constructing a tabular diagram summary, while a diagram loop
indicates the need of looping specific type(s) of diagram.
You can convert a diagram paragraph to diagram summary table or loop by right clicking on a diagram paragraph and selecting Change to Summary
Table/Diagram Loop from popup menu.

To convert a diagram paragraph to diagram summary table/loop

Diagram paragraph P. 861


Element loop
An element loop is a component in a report template, indicating the need of looping (i.e. walking through) specific type(s) of diagram/model elements.
For example, to loop all use case and class in a project. Element loop means nothing more than just to loop diagram/model element. The content to
print for each diagram/model element being looped is to be determined by the children components of loop.

Looping model elements in project


To loop specific type(s) of model elements in project, create element loop at template root. To create element loop at template root:
1. In the template editor, click on any of the buttons in the toolbar depending on your need.
Button Name Description

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.

Description of available type of element loop

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.

Select to loop actor

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.

Looping diagram elements in a diagram


Instead of looping model elements in a project, you can also place element loop under a diagram loop to loop for diagram elements in specific type(s)
of diagram. To create element loop under a diagram loop:
1. Select the element loop that you want to loop for its sub-diagrams.

Selecting a diagram loop

Element loop P. 862


2. Click on the Add Element Loop button from the toolbar of element loop.

Adding an element loop

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.

Switching from element loop to element summary table/paragraph


An element summary indicates the need of looping (i.e. walking through) specific type(s) of diagram/model element, and presenting their properties
in tabular form, while an element paragraph indicates the need of looping specific type(s) of diagram/model element for constructing paragraphs of
properties.
You can convert an element loop to element summary table or paragraph by right clicking on a element loop and selecting Change to Summary
Table/Paragraph from popup menu.

To convert an element loop to element summary table/paragraph

Element loop P. 863


Element summary
An element summary is a component in a report template, indicating the need of looping (i.e. walking through) specific type(s) of diagram/model
element, and presenting their properties in tabular form. For example, to loop all use cases in a project and form a table consisting of use case IDs
and documentation. By default, a table of element names will be printed. You are expected to add property column(s) under an element summary to
indicate the element properties to print in the table.

Showing a property table for elements in project


To loop specific type(s) of model elements in project for listing their properties in a table, create element summary at template root. To create element
summary at template root:
1.
In the template editor, click on the on toolbar.
2.
On the right hand side of the template editor, select the type of model element(s) to loop and click to confirm the selection.

Select to loop use case

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.

To add a property column in element summary

Switching from element summary to element loop/paragraph


An element loop indicates the need of looping specific type(s) of model/diagram element, while an element paragraph indicates the need of looping
specific type(s) of diagram/model element for constructing paragraphs of properties.
You can convert an element summary to element loop/paragraph by right clicking on an element summary and selecting Change to Element Loop/
Paragraph from popup menu.

To convert a element summary to element loop/paragraph

Element summary P. 864


Export/import report template
You can apply a report template on another project by exporting it as a report template file, and importing it to the target project. To export and import
template:
1. Open the report template in template editor.

To open a template in template editor

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.

Export/import report template P. 865


Element paragraph
An element paragraph is a component in a report template, indicating the need of looping (i.e. walking through) specific type(s) of diagram/model
element, and presenting their properties in paragraph form. For example, to loop all use cases in a project and form paragraphs consisting of use case
IDs and documentation. By default, a list of element names will be printed. You are expected to add property value(s) under an element paragraph to
indicate the element properties to print out.

Showing a property paragraph for elements in project


To loop specific type(s) of model elements in project for listing their properties in paragraph form, create element paragraph at template root. To create
element paragraph at template root:
1.
In the template editor, click on the on toolbar.
2.
On the right hand side of the template editor, select the type of model element(s) to loop and click to confirm the selection.

Select to loop use case

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.

To add a property value in element paragraph

Switching from element paragraph to element summary table/loop


An element summary indicates the need of looping specific type(s) of diagram/model element for constructing a tabular element summary, while an
element loop indicates the need of looping specific type(s) of diagram/model element.
You can convert an element paragraph to element summary table or loop by right clicking on a element paragraph and selecting Change to Summary
Table/Element Loop from popup menu.

To convert a element paragraph to element summary table/loop

Element paragraph P. 866


Custom content
Custom content is a component in a report template, which acts as a placeholder of user written text. For example, to add a section of acknowledgment
at the beginning of report with custom text. You can write custom content in rich text, and you can add custom content to template root or under a
diagram/element loop.

Adding custom content at template root


To add custom content at template root:
1.
In the template editor, click on on toolbar.
2. 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.

Entering custom content

Adding custom content into a loop


To add custom content into a diagram/element loop:
1. Select the loop that you want to add custom content under it.

Selecting an element loop

2. Click on the Add Custom Content button from the toolbar of loop.

Adding custom content

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.

Editing custom content


You can write plain text in custom content as well as to add formatted text, images and tables through the help of the tools in the editor.

Custom content editor

No. Name Description

1 Editor pane The editor where you can enter and edit custom content.

2 HTML HTML - Read and edit the real content.


HTML Source - Read and edit the HTML source of content.

3 Bold Set the highlighted text to bold.

4 Italic Set the highlighted text to italic.

5 Underline Underline the highlighted text

6 Alignments Set the alignment of highlighted text to right, center or left.

Custom content P. 867


7 Ordered list Add a numbered list.

8 Un-ordered list Add a list with bullet points.

9 Font Select the font family of highlighted text.

10 Font size Select the size of highlighted text.

11 Font color Select the color of highlighted text.

12 Table Add a table.

13 Background Select the background color of highlighted text.


color

14 Clear formats Clear formats of whole editor to convert the content to plain text.

15 Link Add a hyperlink.

16 Image Add an image.

17 Print Print the custom content.

A description of custom content editor

Custom content P. 868


Diagram image
Diagram image is a component in a report template, which represents a placeholder of the image of a diagram under a diagram loop. You must place a
diagram image under diagram loop. To add a diagram image:
1. Select the diagram loop that you want the images of diagrams to be printed.

Selecting a diagram loop

2. Click on the Diagram Image button from the toolbar of loop.

Adding a diagram image

Diagram Image P. 869


Property value
Property value is an element component in a report template, which represents the access of certain property of a diagram, model element or diagram
element. For example, to print out the ID (property) of a use case. You can add property value into a diagram loop, a diagram summary, an element
loop, an element summary. Property value added to a summary component will become a property column in summary table.

Adding property value into a loop or summary


To add property value into a loop or summary:
1. Select the loop or summary that you want to add property value under it.

Selecting a diagram loop

2. Click on the Add Property Value button from the toolbar of loop.

Adding property value

3. On the right hand side of the template editor, select the property to access.

Selecting a property to access

Adding a property below another property


To add property below another property:
1. Select an existing property value.

Selecting a property value

2. Click on the Add Property Value Below or Add Property Value Above button.

To add a property value below an existing one

3. On the right hand side of the template editor, select the property to access.

Property value P. 870


Page break
Page Break is where the report should start the contents which follows in a new page. It can be placed within a loop, either a diagram or element loop.
To create a Page Break:
1. Select the loop that you want to insert a page break.

Selecting the loop for adding a page break

2. Click on the Add Page Break button from the toolbar of loop.

Adding a page break

3. Reposition the page break by pressing Move Up or Move Down from the toolbar of page break.

Repositioning a page break

Page break P. 871


Publish project using project publisher
The Project Publisher is a tool that exports the project, including detailed information in diagrams and models, into interactive and well-organized web
pages. The generated web pages can be read in any web browser with no additional plug-in required, so collaborative partners may see the published
product even if they do not have Visual Paradigm products installed.
To launch Project Publisher:
1. Select Tools > Project Publisher... from main menu.

To launch project publisher

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.

An overview of project publisher

Overview of project publisher

No. Name Description

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.

7 Cancel Click to close the dialog box without publishing.

Description of project publisher

Publish project using project publisher P. 872


Advanced options
On the Project Publisher dialog box you can configure some of the common options. You can also configure the advanced options for more detailed
settings by clicking the Advanced Options... button.

Project publisher advanced options

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.

Generate page header Check to generate pre-defined header.

Generate page footer Check to generate pre-defined footer.

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.

Publish project using project publisher P. 873


Default diagram Choose the diagram that first appear when opening the published content. If unspecified, a
default page with project information will be presented.

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

Description of project publisher advanced options

Publish project using project publisher P. 874


Using the published content
Go to the output directory of the published project and open the file 'index.html' with a web browser. The web page is organized in frames, namely the
Navigator Pane, Menu Pane and Content Pane.

Published project

No. Name Description

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

Description of the interface of published Web content

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

Using the published contents P. 875


Model Explorer
Shows the package models in the project. You can click on a package to view its child models in the Menu Pane, or click Show All Models to view all
model elements.

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

Using the published contents P. 876


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.

Shape link to descriptions

Using the published contents P. 877


Using jump to
The Jump to drop down menu in the diagram content page lists all shapes in the diagram. You can select a shape to jump to. The content page will
scroll to the selected shape and the shape will be highlighted by a red border.

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

Using the published contents P. 878


Model elements
The Model Elements section of the diagram content page shows the name, type and documentation of the models of all shapes in the diagram. You
can click on the link of a model to view its details.

Model elements

Model element content


The type, name and general model properties of a model are shown in the content page.

Model element content

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

Using the published contents P. 879


Relationships detail

Relationships detail

Other model details


Certain types of model have their own properties, for example, attributes and operations of class, or columns of ERD table. They are also included in
the content page as custom sections. For instance, the Operations Overview and the Operations Detail sections show the overview and details of the
operations of a class respectively.

Other model detail

Using the published contents P. 880


Installing report writer
The Report Writer is a sophisticated tool for report creation. Users can output the existing project as reports by documenting their project within VP-
UML. VP-UML offers seamless integration of UML modeling tool with word processors to provide a unified documenting environment. By dragging the
models from VP-UML to Report Writer, data is extracted from models and content is created in Report Writer.
Retaining the conformance between documentation and design is a tedious task. Report Writer maintains the consistency between them. If you create
a new model, the content will be appended to the existing one. If you remove a model, the generated element will be removed. If you re-edit the
models, the content will be refreshed.
Users can also apply their own style for the generated element, to the Report Writer more flexible.

Launching report writer


To launch Report Writer:
1. Select Tools > Report > Report Writer... from main menu.

Launch report writer

Installing report engine


If it is the first time you have started the Report Writer, the Report Engine Installation dialog box will be displayed asking for the installation of report
engine.

Report Engine Installation dialog box

To install Report Engine, perform one of the following actions:


• Select the option Download from Internet and click OK. This downloads the report engine from the Internet and automatically proceeds with
report engine installation once the download has been completed.
• Select the option Select in local file system. Locate the report engine and then click OK to start the installation. The report engine can be
obtained by clicking Download with browser.
Report writer will be available when installation is done.

Installing report writer P. 881


Creating report
Upon launching Report Writer for the first time, the Templates dialog box will be displayed and ask for the information of the new report. Enter the
report information and select a desired report theme for the report, preview of the selected theme is shown on the preview pane. Click OK to start
report writer when everything is ready.

Templates dialog box

Creating report P. 882


Introduction to report writer user interface
When Report Writer is launched you are taken to the Report Writer environment where you can create and edit your reports. Three distinct panes are
presented on the screen: the Project Explorer, Template Pane and the Writer Pane.

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

Introduction to report writer user interface P. 883


Details of each button in Diagram Navigator are show as below:

Button Description

To collapse all the nodes within the project tree.

To expand all the nodes within the project tree.

To show only diagrams but not models in the tree.

To sort diagrams within the project tree by alphabetical order of their names.

To sort diagrams within the project tree by their diagram type.

To sort diagrams within the project tree by their diagram type.

Details of diagram navigator

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

Details of each button in Model Tree are shown as below:

Button Description

To collapse all the nodes within the project tree.

To expand all the nodes within the project tree.

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.

To sort models within the project tree by their model type.

To refresh the project tree within the Model Pane.

Details of model tree

Introduction to report writer user interface P. 884


Template pane
The Template Pane displays all the templates available for the model or diagram selected in Project Explorer.

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.

Details of template pane

Writer pane
Writer Pane embeds a word processor to provide a report editing environment.

Writer pane

Introduction to report writer user interface P. 885


Toolbar
Toolbar is the horizontal bars placed below the menu bar. They store all the frequently used commands that appear as a row of buttons.

Button Description

To create a new report.

To save modified reports.

To import an external document (either an .sxw or a .doc file) as a report.

To export the current report as an .sxw or .doc file.

To export all the reports within the current project.

To update the content within the current report from the VP-UML models.

To print the current report by supplying the printer name.

To undo the last action you performed.

To redo the last action you performed.

To select a report from the current project for editing.

To remove the existing report(s).

To display the stylist dialog box for modifying the style.

To copy the style settings defined in another report.

To display bookmarks that outlines the boundary for each generated element.

To insert a hyperlink.

To insert index or table

To include documentation of model when generating content.

To close Report Writer and go back to VP-UML.

Details of toolbar

Introduction to report writer user interface P. 886


Constructing report
Creating a generated element
The term "Generated element" here means a block of report content generated by Report Writer and consists of details of a particular diagram or
model element.
To create a generated element block:
1. Click to select the desired model element from either the Diagram Navigator or Model Navigator for content generation.
2. The supported templates for the selected model element are shown on the Template Pane. Each template represents a way in presenting
the selected model element on the report. For example, Children template of a System represents a list of children placed inside a particular
System.

Template pane

3. Drag the desired template from the Template Pane and drop it onto the report.

Drag template from template pane

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.

Drop template to report

Constructing report P. 887


5. Same as diagram, model element's template also able to drag to report.

Drag template from template pane

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.

Drop template to report

Showing the bookmarks


Creating a new generated element within the boundary of an existing one is dangerous because the content may be messed up during a report update
process. To avoid this, you can display bookmarks to indicate the start and end position of each generated element, and to prevent dropping a new one
within the scope of the existing generated element.
To show/hide bookmarks, either check/uncheck Tool > Show Bookmarks from main menu to show/hide bookmarks.

Showing bookmarks

Applying style to report


A style in Report Writer is a collection of formatting attributes that describe the nature of paragraphs. The generated element highly adopts the
predefined styles in Report Writer therefore users can customize the related styles to bring consistency to the whole document. There are two ways for
applying style to report.

Constructing report P. 888


Style configuration
The Stylist dialog box allows you to configure the pre-defined styles. To display the Stylist dialog box, select Tool > Show Stylist from main menu.
The Stylist dialog box appear.

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

Constructing report P. 889


Loading style from other report
The Copy Style dialog box allows you to copy the style from existing report. To display the Copy Style dialog box, select Tool > Copy Style from main
menu. The Copy Style dialog box appear.

Copy style dialog

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.

Updating table of contents


There is a predefined Table of Contents in each of the report template. Here is the pre-built Table of Contents structure:

Level Paragraph Style

0 Heading 1
(VP)

1 Heading 2
(VP)

2 Heading 3
(VP)

3-9 None

Details of predefined table of contents

To update the Table of Contents, right-click on the caption Table of Contents and select Update Index/Table from popup menu.

Constructing report P. 890


Updating report content
In reality, software design keeps evolving from time to time. Originally, users needed to modify the related documents manually to ensure that it is
fully conformed to the latest design. Report Writer binds closely with the VP-UML project, and hence generated elements can then be updated without
affecting the user-defined content.

Report writer

Updating report content P. 891


Edit project's content which used by report.

Edit project

Updating report content P. 892


To update a report, choose the desired report for updating from the drop-down menu and click the Update from Model button from the toolbar or
select Report > Update from Model from main menu.

Update from model element

Updating report content P. 893


Update process will start automatically. Data will be extracted from project and replace with the content within the existing generated element.

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.

Updating report content P. 894


Export and import report
You can export report as file and edit it outside VP-UML. Supported format includes Microsoft Word and OpenOffice.org Text Document.

Exporting current report


1. Click on the Export Report... button on the toolbar or select Report > Export Report... from main menu. This display the Save dialog box.
2. In the Save dialog box, enter the file name and select the format for exporting.
3. Click Save to export the report.

Exporting all report(s)


1. Click the Export All Reports... button on the toolbar or select Report > Export All Reports... from main menu. This display the Save dialog
box.
2. In the Save dialog box, enter the directory for storing the reports in the File name field and select the Document Type.
3. When everything is ready, click Save to export the report(s).

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.

Confirm overwrite existing report

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.

Export and import report P. 895


Customizing report writer template
In report writer, the templates for model elements and diagrams, such as the basic information template, are formed by XML, and can be customized.
By customizing a template, you can make report writer print additional customized text, to make it query other properties you wanted, or to remove part
of the unneeded content, like a row in a table.

Customizing an existing template


1. Right click on a template and select Edit... from the popup menu.

To edit a template

2. Edit the template in the Edit Template dialog box.

The template editor

NOTE: You can save your work from time to time by pressing Save.

3. Click OK to confirm editing.

NOTE: If you have chosen Refresh Report when OK, the report will refresh itself to apply the changes you have made.

Creating a template from existing template

Customizing Report Writer Template P. 896


1. Right click on a template and select Duplicate... from the popup menu.

To duplicate a template

2. Fill in the Duplicate Template dialog box and click OK.

The duplicate template dialog box

Below is a description of the dialog box.


Field Description

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.

ID The uniqie ID for template.

NameThe name of template, which will appear in the template list in template pane.

Details of duplicate template dialog box

3. Click OK to confirm editing.

NOTE: If you have chosen Refresh Report when OK, the report will refresh itself to apply the changes you have made.

The template editor


The template editor is where you edit a template. The template is in XML format. Within the editor, you may make use of hotkey to perform operations
like copy, paste and delete. Below is a description of common hotkeys.

Function Hotkey

Copy Ctrl-
C

Paste Ctrl-
V

Delete Delete

Cut Ctrl-
X

Hotkeys for template editor

Customizing Report Writer Template P. 897


As most of the templates are in tabular forms. We recommend users who want to add new rows to highlight and copy a trunk of row content...

Select existing content to copy and start editing

and edit the custom text and properties to query.

Template content with respect to report content

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"/>

Customizing Report Writer Template P. 898


<xsd:choice>
<xsd:element ref="rw:ElementBaseInitiationBlock"/>
<xsd:element ref="rw:DiagramBaseInitiationBlock"/>
<xsd:element ref="rw:DiagramElementBaseInitiationBlock"/>
<xsd:element ref="rw:ProjectBaseInitiationBlock"/>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="TemplateInformationHeader">
<xsd:complexType>
<xsd:attribute name="id" type="xsd:string" use="optional"/>
<xsd:attribute name="name" type="xsd:string" use="required"/>
<xsd:attribute name="description" type="xsd:string" use="optional"/>
<xsd:attribute name="default" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="type" use="optional" default="text">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="text"/>
<xsd:enumeration value="image"/>
<xsd:enumeration value="table"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="ElementBaseInitiationBlock">
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="DiagramBaseInitiationBlock">
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="DiagramElementBaseInitiationBlock">
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ProjectBaseInitiationBlock">
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<!-- CONTENTS -->
<!-- Breaks, Text -->
<xsd:element name="ParagraphBreak"/>
<xsd:element name="PageBreak"/>
<xsd:element name="StaticText">
<xsd:complexType>
<xsd:attribute name="content" type="xsd:string" use="optional"/>
<xsd:attribute name="isBold" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="isItalic" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="fontFamily" type="xsd:string" use="optional" default="Times New Roman"/>
<xsd:attribute name="alignment" use="optional" default="left">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="left"/>
<xsd:enumeration value="center"/>
<xsd:enumeration value="right"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="fontSize" type="xsd:integer" use="optional" default="12"/>
<xsd:attribute name="style" type="xsd:string" use="optional"/>

Customizing Report Writer Template P. 899


<xsd:attribute name="numberingLevel" type="xsd:short" use="optional"/>
<xsd:attribute name="foreColor" type="rw:color" use="optional"/>
<xsd:attribute name="indentation" type="xsd:double" use="optional"/>
</xsd:complexType>
</xsd:element>
<!-- Table -->
<xsd:element name="TableBlock">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="rw:TableRow" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="tableWidth" type="xsd:integer" use="optional" default="10000">
<xsd:annotation>
<xsd:documentation>Document is in A4 size (21000*27000)</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="colWidths" type="rw:integers" use="optional">
<xsd:annotation>
<xsd:documentation>
@colWidths is relative to @tableWidth.
For example, tableWidth="15000" colWidths="10, 20, 70", finally the columns widths will be:
1500 (15000*10/(10+20+70))
3000 (15000*20/(10+20+70))
10500 (15000*70/(10+20+70))
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="alignment" use="optional" default="center">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="left"/>
<xsd:enumeration value="center"/>
<xsd:enumeration value="right"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="rowBackgroundColors" type="rw:colors" use="optional"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="TableRow">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="rw:TableCell" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="height" type="xsd:integer" use="optional"/>
<xsd:attribute name="backgroundColor" type="rw:color" use="optional"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="TableCell">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="rw:TableCell" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="topBorderEnable" type="xsd:boolean" use="optional" default="true"/>
<xsd:attribute name="bottomBorderEnable" type="xsd:boolean" use="optional" default="true"/>
<xsd:attribute name="leftBorderEnable" type="xsd:boolean" use="optional" default="true"/>
<xsd:attribute name="rightBorderEnable" type="xsd:boolean" use="optional" default="true"/>
<xsd:attribute name="color" type="rw:color" use="optional"/>
<xsd:attribute name="splitted" type="xsd:boolean" use="optional" default="false"/>
</xsd:complexType>
</xsd:element>
<!--
Iteration, retrieve a list of values
(IterationBlock, ForEach, ForEachSimpleRelationship, ForEachRelationshipEnd, ForEachSubDiagram, ForEachOwnerDiagram, ForEachDiagram)
-->
<xsd:element name="IterationBlock">
<xsd:annotation>
<xsd:documentation>
Retrieve children from Project/Model/Diagram/DiagramElement.
Project and Model will be retrieved children Model.
Diagram and DiagramElement will be retrieved children DiagramElement.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="elementType" type="xsd:string" use="optional">

Customizing Report Writer Template P. 900


<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @modelType (Model's modelType or DiagramElement's shapeType)</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="modelType" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Filter children by modelType.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="elementTypes" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @modelTypes (Model's modelTypes or DiagramElement's shapeTypes)</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="modelTypes" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>Filter children by modelTypes. If @modelType is defined, @modelTypes will be ignored.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="name" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Filter children by name.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="filterHidden" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>
Filter hidden children DiagramElement.
For retrieve from Diagram/DiagramElement only.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="includeConnector" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @includeConnectors</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="includeConnectors" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>
Retrieve Shape+Connector from Diagram. Otherwise, only the Shape will retrived.
For retrieve from Diagram only.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="byBounds" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>
Retrieve DiagramElement by Bounds.
sometimes, the parent shape "contains" another shape. But another shape is not child of the shape.
e.g. BPGroup won't be parent of the shapes.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="byBoundsInAllLevel" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="allLevel" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>
Retrieve all models of the project. Otherwise, only the "root level models (models have no parent model)" will be retrieved.
For retrieve from Project only.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="ignoreParagraphBreakForLastModel" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="breakString" type="xsd:string" use="optional"/>
<xsd:attribute name="sortBy" type="xsd:NMTOKEN" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @sortBys</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortBys" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
Sort by following options:
name | modelType | property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortProperty" type="xsd:string" use="optional">

Customizing Report Writer Template P. 901


<xsd:annotation>
<xsd:documentation>
If sort by property, @sortProperty is required to specified sort by which property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortValues" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @sortValues can be specified for sort by values of the property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="defaultPropertyValue" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @defaultPropertyValue can be specified for the default value of the model has no this property value
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSort" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @descendingSort</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSorts" type="rw:booleans" use="optional">
<xsd:annotation>
<xsd:documentation>
Sorting in descending order?
numbers of descendingSorts should be same as sortBys
e.g. @sortBy="name, modelType" @descendingSorts="true, false"
then, sort by name will be descending, sort by modelType will be ascending
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="identifier" type="xsd:string" use="optional"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="ForEach">
<xsd:annotation>
<xsd:documentation>Retrieve Model values from Model's property.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="property" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Retrieve from which proprety.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="ignoreParagraphBreakForLastModel" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="breakString" type="xsd:string" use="optional"/>
<xsd:attribute name="sortBy" type="xsd:NMTOKEN" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @sortBys</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortBys" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
Sort by following options:
name | modelType | property
if sort by property, @sortProperty is required to specified sort by which property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortProperty" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @sortProperty is required to specified sort by which property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortValues" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @sortValues can be specified for sort by values of the property

Customizing Report Writer Template P. 902


</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="defaultPropertyValue" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @defaultPropertyValue can be specified for the default value of the model has no this property value
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSort" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @descendingSort</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSorts" type="rw:booleans" use="optional">
<xsd:annotation>
<xsd:documentation>
Sorting in descending order?
numbers of descendingSorts should be same as sortBys
e.g. @sortBy="name, modelType" @descendingSorts="true, false"
then, sort by name will be descending, sort by modelType will be ascending
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="ForEachSimpleRelationship">
<xsd:annotation>
<xsd:documentation>Retrieve SimpleRelationship from Model, or Connector from DiagramElement</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="type" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @modelType (Model's modelType or DiagramElement's shapeType)</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="modelType" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Filter relationships by modelType.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="modelTypes" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>Filter relationships by modelTypes. If @modelType is defined, @modelTypes will be ignored.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="direction" use="optional">
<xsd:annotation>
<xsd:documentation>Filter relationship by direction.</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="all"/>
<xsd:enumeration value="from"/>
<xsd:enumeration value="to"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="ignoreParagraphBreakForLastModel" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="breakString" type="xsd:string" use="optional"/>
<xsd:attribute name="sortBy" type="xsd:NMTOKEN" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @sortBys</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortBys" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
Sort by following options:
name | modelType | property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortProperty" type="xsd:string" use="optional">

Customizing Report Writer Template P. 903


<xsd:annotation>
<xsd:documentation>
If sort by property, @sortProperty is required to specified sort by which property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortValues" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @sortValues can be specified for sort by values of the property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="defaultPropertyValue" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @defaultPropertyValue can be specified for the default value of the model has no this property value
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSort" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @descendingSort</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSorts" type="rw:booleans" use="optional">
<xsd:annotation>
<xsd:documentation>
Sorting in descending order?
numbers of descendingSorts should be same as sortBys
e.g. @sortBy="name, modelType" @descendingSorts="true, false"
then, sort by name will be descending, sort by modelType will be ascending
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="ForEachRelationshipEnd">
<xsd:annotation>
<xsd:documentation>Retrieve SimpleRelationship from Model, or Connector from DiagramElement</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="type" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @modelType (Model's modelType or DiagramElement's shapeType)</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="modelType" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Filter relationships by modelType.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="modelTypes" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>Filter relationships by modelTypes. If @modelType is defined, @modelTypes will be ignored.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="endPointer" use="optional">
<xsd:annotation>
<xsd:documentation>
Filter relationship by direction.
both = all, self = from, other = to
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="all"/>
<xsd:enumeration value="from"/>
<xsd:enumeration value="to"/>
<xsd:enumeration value="both"/>
<xsd:enumeration value="self"/>
<xsd:enumeration value="other"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>

Customizing Report Writer Template P. 904


<xsd:attribute name="ignoreParagraphBreakForLastModel" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="breakString" type="xsd:string" use="optional"/>
<xsd:attribute name="sortBy" type="xsd:NMTOKEN" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @sortBys</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortBys" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
Sort by following options:
name | modelType | property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortProperty" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @sortProperty is required to specified sort by which property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortValues" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @sortValues can be specified for sort by values of the property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="defaultPropertyValue" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @defaultPropertyValue can be specified for the default value of the model has no this property value
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSort" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @descendingSort</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSorts" type="rw:booleans" use="optional">
<xsd:annotation>
<xsd:documentation>
Sorting in descending order?
numbers of descendingSorts should be same as sortBys
e.g. @sortBy="name, modelType" @descendingSorts="true, false"
then, sort by name will be descending, sort by modelType will be ascending
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="ForEachSubDiagram">
<xsd:annotation>
<xsd:documentation>Retrieve sub diagrams from Model</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="diagramType" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Filter diagram by diagramType.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="ignoreParagraphBreakForLastModel" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="sortBy" type="xsd:NMTOKEN" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @sortBys</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortBys" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
Sort by following options:
name | modelType | property
</xsd:documentation>

Customizing Report Writer Template P. 905


</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortProperty" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @sortProperty is required to specified sort by which property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortValues" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @sortValues can be specified for sort by values of the property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="defaultPropertyValue" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @defaultPropertyValue can be specified for the default value of the model has no this property value
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSort" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @descendingSort</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSorts" type="rw:booleans" use="optional">
<xsd:annotation>
<xsd:documentation>
Sorting in descending order?
numbers of descendingSorts should be same as sortBys
e.g. @sortBy="name, modelType" @descendingSorts="true, false"
then, sort by name will be descending, sort by modelType will be ascending
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="ForEachOwnerDiagram">
<xsd:annotation>
<xsd:documentation>Retrieve owner diagrams which the Model is shown on</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="diagramType" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Filter diagram by diagramType.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="ignoreParagraphBreakForLastModel" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="sortBy" type="xsd:NMTOKEN" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @sortBys</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortBys" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
Sort by following options:
name | modelType | property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortProperty" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @sortProperty is required to specified sort by which property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortValues" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @sortValues can be specified for sort by values of the property

Customizing Report Writer Template P. 906


</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="defaultPropertyValue" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @defaultPropertyValue can be specified for the default value of the model has no this property value
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSort" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @descendingSort</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSorts" type="rw:booleans" use="optional">
<xsd:annotation>
<xsd:documentation>
Sorting in descending order?
numbers of descendingSorts should be same as sortBys
e.g. @sortBy="name, modelType" @descendingSorts="true, false"
then, sort by name will be descending, sort by modelType will be ascending
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="ForEachDiagram">
<xsd:annotation>
<xsd:documentation>Retrieve diagrams from Project</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="diagramType" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Filter diagram by diagramType.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="ignoreParagraphBreakForLastModel" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="sortBy" type="xsd:NMTOKEN" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @sortBys</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortBys" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
Sort by following options:
name | modelType | property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortProperty" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @sortProperty is required to specified sort by which property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="sortValues" type="rw:strings" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @sortValues can be specified for sort by values of the property
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="defaultPropertyValue" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
If sort by property, @defaultPropertyValue can be specified for the default value of the model has no this property value
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSort" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @descendingSort</xsd:documentation>

Customizing Report Writer Template P. 907


</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="descendingSorts" type="rw:booleans" use="optional">
<xsd:annotation>
<xsd:documentation>
Sorting in descending order?
numbers of descendingSorts should be same as sortBys
e.g. @sortBy="name, modelType" @descendingSorts="true, false"
then, sort by name will be descending, sort by modelType will be ascending
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<!--
Conditional, if condition not match, children template node won't be executed
(DefaultConditionChecker, ValueConditionChecker, HasChildElementChecker, HasMetaModelPropertyChecker, HasParentModelChecker,
HasRelationshipChecker, ReportOptionChecker, HasDiagramChecker)
-->
<xsd:element name="DefaultConditionChecker">
<xsd:annotation>
<xsd:documentation>Check property value equals to its default value.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="equalFlag" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @flag</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="flag" type="xsd:boolean" use="optional" default="false"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="ValueConditionChecker">
<xsd:annotation>
<xsd:documentation>Check property value.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="propertyType" use="optional" default="string">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="string"/>
<xsd:enumeration value="int"/>
<xsd:enumeration value="boolean"/>
<xsd:enumeration value="model"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="operator" use="required">
<xsd:annotation>
<xsd:documentation>
"equal" is deprecated, replaced by "equals"
"not equal" is deprecated, replaced by "not equals"
"equals", "not equals" for string/int/boolean/model property
"less than", "equals or less than", "greater than", "equals or greater than" for string/int property
"like", "not like" for string property
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="equals"/>
<xsd:enumeration value="not equals"/>
<xsd:enumeration value="less than"/>
<xsd:enumeration value="equals or less than"/>
<xsd:enumeration value="greater than"/>
<xsd:enumeration value="equals or greater than"/>
<xsd:enumeration value="like"/>
<xsd:enumeration value="not like"/>
<xsd:enumeration value="equal"/>
<xsd:enumeration value="not equal"/>
</xsd:restriction>
</xsd:simpleType>

Customizing Report Writer Template P. 908


</xsd:attribute>
<xsd:attribute name="expectedValue" type="xsd:string" use="optional"/>
<xsd:attribute name="caseSensitive" type="xsd:boolean" use="optional" default="true">
<xsd:annotation>
<xsd:documentation>Case sensitive/insensitive for string property</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="HasChildElementChecker">
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="flag" type="xsd:boolean" use="optional" default="true"/>
<xsd:attribute name="type" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @modelType</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="modelType" type="xsd:string" use="optional"/>
<xsd:attribute name="elementTypes" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @modelTypes</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="modelTypes" type="xsd:string" use="optional"/>
<xsd:attribute name="includeConnector" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @includeConnectors</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="includeConnectors" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>
Retrieve Shape+Connector from Diagram. Otherwise, only the Shape will retrived.
For retrieve from Diagram only.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="allLevel" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>
Retrieve all models of the project. Otherwise, only the "root level models (models have no parent model)" will be retrieved.
For retrieve from Project only.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="HasMetaModelPropertyChecker">
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="flag" type="xsd:boolean" use="optional" default="true"/>
<xsd:attribute name="property" type="xsd:string" use="required"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="HasParentModelChecker">
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="flag" type="xsd:boolean" use="optional" default="true"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="HasRelationshipChecker">
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="flag" type="xsd:boolean" use="optional" default="true"/>
<xsd:attribute name="type" type="xsd:string" use="optional">
<xsd:annotation>

Customizing Report Writer Template P. 909


<xsd:documentation>Deprecated, replaced by @modelType</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="modelType" type="xsd:string" use="optional"/>
<xsd:attribute name="modelTypes" type="xsd:string" use="optional"/>
<xsd:attribute name="direction" use="optional" default="all">
<xsd:annotation>
<xsd:documentation>
self_begins, self_ends are deprecated
self_begins = from
self_ends = to
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="all"/>
<xsd:enumeration value="from"/>
<xsd:enumeration value="to"/>
<xsd:enumeration value="self_begins"/>
<xsd:enumeration value="self_ends"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="ReportOptionChecker">
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="equalFlag" type="xsd:boolean" use="optional" default="false">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @flag</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="flag" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="option" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
Check the option. Now, only one option is supported. Which is:
basicInformationShowsDocumentation
user can switch the option on Report Writer main menu: Tool &gt; Options &gt;
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element name="HasDiagramChecker">
<xsd:complexType>
<xsd:sequence>
<!-- any element after the comment "CONTENTS"-->
<xsd:any minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="flag" type="xsd:boolean" use="optional" default="true"/>
<xsd:attribute name="type" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @diagramType</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="diagramType" type="xsd:string" use="optional"/>
</xsd:complexType>
</xsd:element>
<!--
Property, getting property value from model
(StringPropertyText, IntPropertyText, BooleanPropertyText, MetaModelElement, FromEnd, ToEnd, RelationshipEndEndRelationship,
RelationshipEndOppositeEnd, ParentModel, DiagramProperty)
-->
<xsd:element name="StringPropertyText">
<xsd:complexType>
<xsd:attribute name="propertyText" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @property</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="isHTML" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="forcePlainText" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="defaultValue" type="xsd:string" use="optional"/>
<xsd:attribute name="property" type="xsd:string" use="optional"/>

Customizing Report Writer Template P. 910


<xsd:attribute name="isBold" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="isItalic" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="fontFamily" type="xsd:string" use="optional" default="Times New Roman"/>
<xsd:attribute name="alignment" use="optional" default="left">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="left"/>
<xsd:enumeration value="center"/>
<xsd:enumeration value="right"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="fontSize" type="xsd:integer" use="optional" default="12"/>
<xsd:attribute name="style" type="xsd:string" use="optional"/>
<xsd:attribute name="numberingLevel" type="xsd:short" use="optional"/>
<xsd:attribute name="foreColor" type="rw:color" use="optional"/>
<xsd:attribute name="indentation" type="xsd:double" use="optional"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="IntPropertyText">
<xsd:complexType>
<xsd:attribute name="propertyText" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @property</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="isHTML" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="property" type="xsd:string" use="optional"/>
<xsd:attribute name="isBold" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="isItalic" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="fontFamily" type="xsd:string" use="optional" default="Times New Roman"/>
<xsd:attribute name="alignment" use="optional" default="left">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="left"/>
<xsd:enumeration value="center"/>
<xsd:enumeration value="right"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="fontSize" type="xsd:integer" use="optional" default="12"/>
<xsd:attribute name="style" type="xsd:string" use="optional"/>
<xsd:attribute name="numberingLevel" type="xsd:short" use="optional"/>
<xsd:attribute name="foreColor" type="rw:color" use="optional"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="BooleanPropertyText">
<xsd:complexType>
<xsd:attribute name="propertyText" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @property</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="property" type="xsd:string" use="optional"/>
<xsd:attribute name="isBold" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="isItalic" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="fontFamily" type="xsd:string" use="optional" default="Times New Roman"/>
<xsd:attribute name="alignment" use="optional" default="left">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="left"/>
<xsd:enumeration value="center"/>
<xsd:enumeration value="right"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="fontSize" type="xsd:integer" use="optional" default="12"/>
<xsd:attribute name="style" type="xsd:string" use="optional"/>
<xsd:attribute name="numberingLevel" type="xsd:short" use="optional"/>
<xsd:attribute name="foreColor" type="rw:color" use="optional"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="MetaModelElement">
<xsd:annotation>
<xsd:documentation>Retrieve Model from property.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:attribute name="mode" type="xsd:boolean" use="optional" default="true"/>
<xsd:attribute name="modelProperty" type="xsd:string" use="optional">

Customizing Report Writer Template P. 911


<xsd:annotation>
<xsd:documentation>Deprecated, replaced by @property</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="identifier" type="xsd:string" use="optional"/>
</xsd:complexType>
</xsd:element>
<xsd:element name="FromEnd">
<xsd:annotation>
<xsd:documentation>Retrieve From RelationshipEnd from EndRelationship, or From model from SimpleRelationship.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ToEnd">
<xsd:annotation>
<xsd:documentation>Retrieve To RelationshipEnd from EndRelationship, or To model from SimpleRelationship.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="RelationshipEndEndRelationship">
<xsd:annotation>
<xsd:documentation>Retrieve EndRelationship from RelationshipEnd.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="RelationshipEndOppositeEnd">
<xsd:annotation>
<xsd:documentation>Retrieve opposite end from RelationshipEnd.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ParentModel">
<xsd:annotation>
<xsd:documentation>Retrieve parent model from Model.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DiagramProperty">
<xsd:annotation>
<xsd:documentation>Retrieve diagram from property. e.g. BPSubProcess.diagramId refer its bpd.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:attribute name="property" type="xsd:string" use="required"/>
</xsd:complexType>
</xsd:element>
<!--
Others
(ElementImage, FlowOfEventsTemplate)
-->
<xsd:element name="ElementImage">
<xsd:annotation>
<xsd:documentation>Showing image of Diagram/DiagramElement, or icon for model type.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:attribute name="imageType" use="optional" default="icon">
<xsd:annotation>
<xsd:documentation>
"diagram" means show image for Diagram/DiagramElement
"icon" means show icon for the model type
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="diagram"/>
<xsd:enumeration value="icon"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="alignment" use="optional" default="left">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="left"/>
<xsd:enumeration value="center"/>
<xsd:enumeration value="right"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="style" type="xsd:string" use="optional"/>
<xsd:attribute name="width" type="xsd:integer" use="optional"/>
<xsd:attribute name="height" type="xsd:integer" use="optional"/>
<xsd:attribute name="maxWidth" type="xsd:integer" use="optional"/>
<xsd:attribute name="maxHeight" type="xsd:integer" use="optional"/>
</xsd:complexType>
</xsd:element>

Customizing Report Writer Template P. 912


<xsd:element name="FlowOfEventsTemplate">
<xsd:annotation>
<xsd:documentation>Showing Flow Of Events for a Use Case.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:attribute name="showProcedure" use="optional" default="follow model">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="follow model"/>
<xsd:enumeration value="true"/>
<xsd:enumeration value="false"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="tableWidth" type="xsd:integer" use="optional" default="15500"/>
<xsd:attribute name="showRowBorder" type="xsd:boolean" use="optional" default="false"/>
<xsd:attribute name="showColumnBorder" type="xsd:boolean" use="optional" default="true"/>
<xsd:attribute name="showName" type="xsd:boolean" use="optional" default="true">
<xsd:annotation>
<xsd:documentation>Show the name of Flow of event?</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="columnWidths" type="rw:integers" use="optional"/>
<xsd:attribute name="name" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>Filter Flow of events by name.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:simpleType name="strings">
<xsd:annotation>
<xsd:documentation>Strings separated by ", ". e.g. "Class, UseCase, Actor" means "Class", "UseCase", "Actor"</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
<xsd:simpleType name="integers">
<xsd:annotation>
<xsd:documentation>Integers separated by ", ". e.g. "10, 20, 70"</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
<xsd:simpleType name="booleans">
<xsd:annotation>
<xsd:documentation>Booleans separated by ", ". e.g. "true, false, false"</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
<xsd:simpleType name="color">
<xsd:annotation>
<xsd:documentation>
Color can be represented in following 2 forms:
1. "R, G, B" in decimal, e.g. "230, 230, 230" (it is a light gray color)
2. #FFFFFF (RGB in hexadecimal), e.g. #FF0000 (it is a red color)
Prefer using #FFFFFF. Because "R, G, B" is not suitable for colors.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
<xsd:simpleType name="colors">
<xsd:annotation>
<xsd:documentation>
Colors separated by ", ". e.g. "#FF0000, #00FF00, #0000FF".
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:schema>

Customizing Report Writer Template P. 913


Exporting XML
Interoperability is the ability to exchange information between two systems and to use the information that has been exchanged. VP-UML supports
interoperability with XML file. You can export project data to an XML, manipulate it externally, and feed the changes back to VP-UML. In this chapter,
you will see how to export XML file of whole project or specific diagram in project.

Exporting whole project to XML


1. Select File > Export > XML... from the main menu.

Export XML

2. Specify the output destination.


3. Check Export project to export everything in the project to XML, or keep it unchecked, and check the diagram(s) to export only their content.
4. Click Export. Upon finishing, you can visit the output destination specified to obtain the XML.

Exporting active diagram to XML

Exporting XML P. 914


1. Right click on diagram and select Export > Export XML... from the popup menu.

Export XML from diagram popup

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.

Overview of exporting XML

Exporting XML P. 915


Overview of Export XML dialog box

No. Name Description

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.

4 Diagram list All diagrams in your project will be shown in here.

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.

7 Export Click Export to proceed with exporting to XML.

8 Cancel Click Cancel to discard exporting to XML.

Description of Export XML dialog box

Exporting diagrams to XML with command line interface


1. Start the command console.
2. In the console, change directory to the scripts folder and execute ExportXML with parameters required.

Parameters for ExportXML

This displays the usage of the command. Below is a description of parameters:


Parameter Description Example

-project Project path C:\Demo\Demo.vpp

-out Folder for storing the exported XML and images C:\Demo\Output

- One or more diagrams to be exported "Diagram A" "Diagram


diagram B"

- Do not export image files for diagrams N/A


noimage

Parameters for ExportXML

Upon finishing, you can visit the output destination specified to obtain the XML files.

Exporting XML P. 916


Importing XML
You can import changes made externally in XML back to VP-UML, to update the project data. In this chapter, you will see how to import an XML
exported before. Notice that XML import is made in response to XML export in VP-UML. Only XML exported from VP-UML can be imported.

Importing XML to current project


1. Select File > Import > XML... from the main menu.

Import XML

2. Specify the file path of the XML to import.


3. Click OK.

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.

Importing XML to project with command line interface


1. Start the command console.

Importing XML P. 917


2. In the console, change directory to the scripts folder and execute ImportXML with the parameters required.

Parameters for ImportXML

This displays the usage of the export command. Below is a description of parameters:
Parameter Description Example

-project Project path C:\Demo\Demo.vpp

-file The filepath of the XML file to import C:\Demo\input


\sample.xml

Parameters for ImportXML

Upon finishing, the project file will be updated with the data presented in the XML file.

Importing XML P. 918


Exporting VP project
Interoperability is the ability to exchange information between two systems and to use the information that has been exchanged. VP-UML supports
interoperability with native .vpp project file. You can export some of the diagrams to a project file, send to your team member for editing, and feed the
changes back to VP-UML. In this chapter, you will see how to export project file for diagrams in project. To export VP project:
1. Select File > Export > VP-UML Project... from the main menu.

Export VP project

2. Specify the output destination.

Inputting output destination

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.

Overview of exporting VP project

Exporting VP project P. 919


Overview of Export Project dialog box

No. Name Description

1 Output The location where you want to save the file.


destination

2 Diagrams All diagrams in your project will be shown in here.

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.

5 Export Click Export to proceed with exporting to VP project.

6 Cancel Click Cancel to discard exporting to VP project.

7 Help More information about how to export VP Project can be obtained by clicking this button.

Description of Export Project dialog box

Exporting VP project P. 920


Importing VP project
You can import a VP project to VP-UML for importing changes made in an exported project, or to import model in another project. In this chapter, you
will see how to import a VP project. To import a project:
1. Select File > Import > VP-UML Project... from the main menu.

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.

Importing VP project P. 921


Exporting diagrams to Microsoft Excel format
Interoperability is the ability to exchange information between two systems and to use the information that has been exchanged. VP-UML supports
interoperability with Microsoft Excel file. You can export project data to an excel file, make changes in exported Excel's worksheets, or further
processing like to query data with formula, and eventually feed the changes back to VP-UML. In this chapter, you will see how to export an Excel file
from a project. To export Excel:
1. Select File > Export > Excel... from the main menu.

Export Excel

This opens the Export Excel dialog box.


2. Specify the output path of Excel file.
3. Select the diagrams to export to Excel.
4. On the Model Types list at the right hand side, you can optionally select the type(s) of model elements to be exported.

Exporting to Microsoft Excel P. 922


5. Click Export. Upon finishing, you can visit the output destination specified to obtain the Excel file.

The exported Excel file

An overview of Export Excel dialog box

Exporting to Microsoft Excel P. 923


Overview of the Export Excel dialog box

No. Field Description

1 Output Path The file path of the Excel file.

2 Launch Editor Check to open the exported Excel file after exported.

3 Export Style Determine how data will be presented in Excel.


Diagram Per Sheet - Selected diagrams will be exported to separate sheets.
All in One Sheet - Selected diagrams will be exported to a single sheet.
Model Type Per Sheet - Selected model elements will be exported to separate sheets, grouped by type.
Raw - Only one sheet will be generated with all elements listed in it. All the properties of selected elements will be listed as
columns, which each row represents a model element.

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.

11 Export Click Export to proceed with exporting Excel.

12 Cancel Click Cancel to diacard exporting to Excel.

Exporting to Microsoft Excel P. 924


Overview of the Export Excel dialog box

Exporting to Microsoft Excel P. 925


Importing Microsoft Excel file
You can import changes made externally in Excel file back to VP-UML, to update the project data. In this chapter, you will see how to import an Excel
exported before. Notice that Excel import is made in response to Excel export in VP-UML. Only Excel exported from VP-UML can be imported.

Importing an Excel file


1. Select File > Import > Excel... from the main menu.

Import Excel

2. In the file chooser, select the Excel file to import and click Open to confirm.

Importing Microsoft Excel file P. 926


3. In the Import dialog box, you can preview the changes you have made in the previous Excel file. If you want to keep a record of changes, click
on Save Details... at the bottom of dialog box to export the changes to an Excel file.

Import dialog box

4. Click OK button to proceed.

Importing Microsoft Excel file P. 927


Excel modification guidelines
When you are going to modify Excel file exported from VP-UML, make sure the changes you make are all valid. Making invalid changes will cause the
file cannot be imported back to VP-UML. In this chapter, we will go through some of the points that you need to pay attention to when editing.

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

Renaming a model element


Double click on a cell and enter a new name.

Renaming class in Excel

Excel modification guidelines P. 928


Deleting a model element
To delete a model element, change No to Yes under the Delete? column. Do NOT delete the row.

Deleting attribute in Excel

Excel modification guidelines P. 929


Adding a model element
Suppose you want to add an attribute, select the last attribute row and insert a row in Excel, right under the last one. Then, start editing it. The gray
cells can leave blank.

Adding attribute in Excel

Excel modification guidelines P. 930


Exporting XMI
Interoperability is the ability to exchange information between two systems and to use the information that has been exchanged. VP-UML supports
interoperability with XMI file, a standard made for data exchange. You can export project data to an XMI, edit it externally with other softwares that
accepts XMI. In this chapter, you will see how to export XMI file.

Exporting project to XMI


1. Select File > Export > XMI... from the main menu.

Export XMI

This displays the Export XMI dialog box.


2. Specify the file path of the XMI file.
3. Configure the exporting such as setting the XMI version and changing the encoding of XMI.

Exporting XMI P. 931


4. Click OK button to start exporting. Upon finishing, you can visit the output destination specified to obtain the XMI.

Review exported XMI

An overview of Export XMI dialog box

An overview of the Export XMI dialog box

No. Name Description

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:

Exporting XMI P. 932


• Export for UML 2 - By checking this option, the exported XMI will conform to the tool UML2's standard. The following options
will appear in further.
• Export Data Type to - Determine whether to export data type to UML or Ecore primitive type
• Export Java Annotation to EAnnotation - Determine whether to export Java annotation to EAnnotation

• 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.

3 Encoding Select the encoding of XMI file.

Description of Export XMI dialog box

Exporting diagrams to XMI with command line interface


1. Start the command console.
2. In the console, change directory to the scripts folder and execute ExportXMI with the parameters required.

Export XMI using command line interface

Below is a description of parameters:


Parameter Description Example

-project Project path C:


\Demo
\Demo.vpp

-out The filepath of XMI file C:


\Demo
\Output
\sample.xmi

-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

-encoding [optional] Encoding of XMI file UTF-8

Parameters for ExportXMI

Upon finishing, you can visit the output destination specified to obtain the XMI.

Exporting XMI P. 933


Importing XMI
You can migrate your works done in another software to VP-UML through XMI, provided that the software supports XMI. In this chapter, you will see
how to import an XMI file.

Importing XMI to current project


1. Select File > Import > XMI... from the main menu.

Import XMI

This displays the Import XMI dialog box.


2. Specify the file path of the XMI to import, and configure the import if necessary.
3. Click OK.

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.

An overview of Import XMI dialog box

Importing XMI P. 934


An overview of Import XMI dialog box

No. Name Description

1 File path The file path of the XMI file to import.

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.

Description of Import XMI dialog box

Importing XMI to project with command line interface


1. Start the command console.
2. In the console, change directory to the scripts folder and execute ImportXMI with the parameters required.

Import XMI using command line interface

Below is a description of parameters:


Parameter Description Example

-project Project path C:\Demo\Demo.vpp

-file The filepath of the XMI file to import C:\Demo\input


\sample.xmi

Parameters for ImportXMI

Upon finishing, the project file will be updated with the data presented in the XMI file.

Importing XMI P. 935


Importing Visio drawing into VP-UML
You may have drew diagrams in Visio. You can now import your previous work through the import feature.
1. Save your Visio drawing as a .vdx file.

A Visio drawing

2. To import a Visio drawing into VP-UML, select File > Import > Visio... in the main menu of VP-UML.

Import Visio drawing

Importing Visio Drawing into VP-UML P. 936


3. Specify the file path of the Visio drawing.

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 Import Visio dialog box

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.

Description of available import options on individual shape

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.

An overview of Import Visio dialog box

An overview of Import Visio dialog box

No. Name Description

Importing Visio Drawing into VP-UML P. 937


1 File path The path of Visio .vdx 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, 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.

5 Cancel Click to cancel importing.

Description of Import Visio dialog box

Importing Visio Drawing into VP-UML P. 938


Importing Rational Rose model into VP-UML
Rational Rose is one of the most widely used UML CASE Tool in the 90's. Visual Paradigm supports the importing of Rational Rose model. With this,
users can import legacy design made in Rose into VP-UML, with all the model data as well as formatting retained.
1. Save your work in Rose.

A Rose drawing

2. To import a Rose model into VP-UML, select File > Import > Rose Project... in the main menu of VP-UML.

The import Rose Project menu

Importing Rational Rose Model into VP-UML P. 939


3. Specify the file path of the Rose model.

Specifying Rose model path

No. Name Description

1 File path The path of Rose .mdl file to be imported.

2 Import You can choose the mode to be imported.


mode Model only: By selecting this option, only the model elements (e.g. Actor, Use Case, Class, etc.) will be imported. NO
diagrams will be imported.
Model and diagram: By selecting this option, both model elements and diagrams will be imported.

3 OK Click to import.

4 Cancel Click to cancel importing.

5 Help Click to obtain more information from the help system.

Description of import rose properties

4. Click OK to start importing.


5. When import is completed, click Close to close the progress dialog box. If Model and diagram was set for Import mode, the drawings can then
be accessible in the Diagram Navigator.

Diagram Navigator listing the imported diagram(s)

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.

Model Explorer listing the imported model element(s)

Importing Rational Rose Model into VP-UML P. 940


Importing Rational Software Architect EMX into VP-UML
Rational Software Architect (RSA) is a modeling and development environment, which leverages UML for architectural design for C++ and Java 2
Enterprise Edition (Java2EE) applications and web services. Import of the RSA file, i.e. the .emx file, is supported in VP-UML so that users can simply
migrate the work from RSA to VP, also perform further modeling on the imported models in the VP tool.
1. Save your work in Rational.

A Rational drawing

2. To import a Rational model into VP-UML, select File > Import > Rational Model... in the main menu of VP-UML.

The import Rational model menu

3. In the Import Rational Software Architect UML Model dialog box, specify the file path of the .emx file and click OK.

Importing Rational Software Architect EMX into VP-UML P. 941


4. The drawings can then be accessible in the Diagram Navigator. You can then double click on the diagram node to open the diagram.

Diagram Navigator listing the imported diagram(s)

Importing Rational Software Architect EMX into VP-UML P. 942


Importing Rational Software Architect DNX into VP-UML
VP-UML supports importing drawing drew in Rational Software Architect with a .dnx extension. By importing a drawing, all diagrams, shapes and
model information will be imported.
1. Save the drawing in Rational Software Architect.

A Rational drawing

2. To import the drawing into VP-UML, select File > Import > Rational DNX... in the main menu of VP-UML.

The import Rational DNX menu

3. In the Import Rational Diagram DNX dialog box, specify the file path of the .dnx file and click OK.

Importing Rational Software Architect DNX into VP-UML P. 943


4. After importing is completed, you can then double click on the diagram node to open the diagram.

Diagram Navigator listing the imported diagram(s)

Importing Rational Software Architect DNX into VP-UML P. 944


Importing ERwin data modeler project into VP-UML
AllFusion ERwin Data Modeler is a popular tool for data modeling. You can import ERwin diagrams and entity models into VP-UML with all properties
preserved.
1. Here is a ERwin Data Modeler Project. In order to let VP-UML import it, you need to save it as an XML file. Select File > Save As... from the
menu.

To save an ERwin Data Modeler project as XML

2. Select XML Files (*.xml) in Save as type and enter the file name in the Save As dialog box.

Save the ERwin Data Modeler project as XML

3. Click Save. This popup the Save as XML File dialog box.

Importing ERwin Data Modeler project file into VP-UML P. 945


4. Keep using the default settings Standard XML Format and Only save minimum amount of information.

Exporting the XML in standard XML format

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.

The import ERwin Data Modeler Project menu

Importing ERwin Data Modeler project file into VP-UML P. 946


7. Specify the file path of the XML file.

Specifying ERwin Data Modeler project file path

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.

Importing ERwin Data Modeler project file into VP-UML P. 947


Importing Telelogic Rhapsody project into VP-UML
1. Save your Telelogic Rhapsody Project.

A drawing in Telelogic Modeler

Importing Telelogic Rhapsody project into VP-UML P. 948


2. To import a Telelogic Phapsody project into VP-UML, select File > Import > Telelogic Rhapsody Project ... in the main menu of VP-UML.

The import Telelogic Rhapsody Project menu

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.

Diagram Navigator listing the imported diagram(s)

Importing Telelogic Rhapsody project into VP-UML P. 949


Importing Telelogic System Architect into VP-UML
1. Save your Telelogic System Architect drawing:

A Telelogic System Architect drawing

2. To import a Telelogic System Architect project into VP-UML, select File > Import > Telelogic System Architect ... in the main menu of VP-
UML.

The import Telelogic System Architect menu

Importing Telelogic System Architect into VP-UML P. 950


3. Specify the file path of the Telelogic System Architect project.

Specifying Telelogic System Architect path

No. Name Description

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 OK Click OK to proceed with importing Telelogic System Architect.

5 Cancel Click Cancel to discard importing XML.

Description of Import Telelogic System Architect dialog box

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.

Diagram Navigator listing the imported diagram(s)

Importing Telelogic System Architect into VP-UML P. 951


Importing NetBeans 6.x UML diagrams into VP-UML

Importing NetBeans 6.x UML diagrams into VP-UML P. 952


1. Here is a NetBeans UML Diagram:

A Class Diagram drew in NetBeans

To import a NetBeans UML project into VP-UML, select File > Import > NetBeans UML Project... in the main menu of VP-UML.

The import NetBeans UML Project menu

Importing NetBeans 6.x UML diagrams into VP-UML P. 953


2. Specify the file path of the NetBeans project.

Specify NetBeans UML Project path

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.

Diagram Navigator listing the imported diagram(s)

You can then double click on the diagram node to open the diagram.

A class diagram imported from NetBeans UML Project

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.

Importing NetBeans 6.x UML diagrams into VP-UML P. 954


Exporting active diagram as image
You can export the opening diagram to image file. To export the active diagram as an image file:
1. Select File > Export > Active Diagram as Image... from main menu.

Export active diagram as image

2. In the Save dialog box, set the image quality. The higher the quality, the clearer the image, the larger the image size.

Set image quality

3. Select the image format at the bottom of dialog box.

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.

4. Specify the filename.


5. Click Save to export.

Exporting active diagram as image P. 955


Exporting multiple diagrams as images
You can export diagrams in your project to image files. You can specify not only the quality and format (e.g. JPG, PNG, SVG, EMF, PDF) of images,
but also to slice diagram into pieces, for easier insertion into documents.

Export diagrams
1. Select File > Export > Diagrams as Image... from main menu.

Export diagrams as images

2. In the Diagram Exporter dialog box, select the diagram(s) to export.


3. Specify the output desctination for storing the image files.
4. Click Export to export the diagrams.

An overview of Diagram Exporter

Exporting multiple diagrams as images P. 956


An overview of Diagram Exporter dialog box

No. Name Description

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.

6 Show preview Check or uncheck to enable or disable the preview.

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.

Exporting multiple diagrams as images P. 957


10 Graphics 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 graphics, check the
Graphics Anti-aliasing checkbox .

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.

14 Slice all diagrams Click to configure slice settings on all diagrams.

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.

16 Export Click to proceed with exporting.

17 Cancel Click to close the exporter without exporting diagrams.

18 Help Click to show the help contents.

Description of Diagram Exporter dialog box

Slice a diagram into pieces with diagram slicer


You can slice diagrams into pieces (number of files), as well as restrict the size of the exported diagrams.

The slice diagram dialog box


The way how diagram is sliced can be set per diagram, or to all diagrams. To slice a diagram, click on the slice button right under the diagram preview
in the Diagram Exporter dialog box. To slice all diagrams, enable Slice Diagrams and click on Slice All Diagrams button. Both ways open the
Diagram Slicer for configuring how diagram(s) is to be sliced.

Exporting multiple diagrams as images P. 958


An overview of Diagram Slicer dialog box

Below is the description of different parts of the dialog box.

No. Name Description

1 No slicing Do not slice diagram.

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.

5 Add row Slice the diagram into specific number of rows.

6 Add column Slice the diagram into specific number of columns.

7 Remove row Reduce the number of rows to slice.

8 Remove column Reduce the number of columns to slice.

9 Rows The number of rows for slicing a diagram.

10 Columns The number of columns for slicing a diagram.

11 Zoom in Magnify the diagram content.

12 Zoom out Demagnify the diagram content.

13 Zoom fit to Zoom the diagram to make it fit weel on the slicer window.
screen

14 Show label Click to show/hide index label.

15 Scale The way of scaling. When configuring slicing for all diagrams, this part will not be displayed.

16 Width The total width of diagram.

17 Height The total height of diagram.

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

Controlling size of exported image


Diagram Slicer not only slice diagram into pieces but also controls the total size of the exported diagrams. There are scale controls on the right of
the toolbar from the Diagram Slicer dialog. By default, the type of scale is Original. And it shows the size of diagram. The following are some of the
possible ways of controlling diagram size.

Exporting multiple diagrams as images P. 960


Control by size
To control the total size of the exported diagram by specific width and height, select Size from the Scale combo box, and then enter the width and
height of the diagram. The ruler shows the size of the diagram.

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.

Exporting multiple diagrams as images P. 961


Exporting portion of diagram as image
You can export some shapes in a diagram as an image file by selecting the shapes you want to export then perform export. To export selected shapes
to image:
1. On a diagram, select the shapes to be exported.

Selecting shapes to export as image

2. Select File > Export > Selection as Image... from main menu.

Export selected shapes as image

Exporting portion of diagram as image P. 962


3. In the Save dialog box, set the image quality. The higher the quality, the clearer the image, the larger the image size.

Set image quality

4. Select the image format at the bottom of dialog box.

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.

5. Specify the filename of the image file.


6. Click Save to export.

Exporting portion of diagram as image P. 963


Introduction to plugin support
Plugin Support provides an interface for developers to integrate with VP-UML. Developers can develop their plugins for what they want. In this section,
we will introduce the structure of a plugin.

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).

Model Elements under Model Explorer

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)

An opening Use Case Diagram

Introduction to plugin support P. 964


Diagram element
A model element does not contain information of appearance (such as x, y, width, height, etc...). It is the diagram element, which appear on the
user interface, that owns the appearance data. Diagram Element represents a view of a model element. A model element can be shown on different
diagrams (such as a class can be shown on 2 different class diagrams).
There are 2 kinds of diagram element: Shape and Connector. Shape represents the non-relationships diagram element (such as Class). Connector
represents the relationships (such as Generalization). Plugin allows developer to create, retrieve, update and delete diagram elements through the
popup menu context or through the project (to iterate all the diagrams and then the diagram elements appear on a diagram).

Shapes and connectors are both diagram elements

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.

Menu with user-defined menus

Toolbar with user-defined buttons

Popup menu with user-defined menus

Introduction to plugin support P. 965


Diagram toolbar with user-defined buttons

Introduction to plugin support P. 966


Implementing plugin
Configuring development environment
Plugin Support API is placed on %VP_SUITE%/lib/openapi.jar. In order to working with VP-UML, developer must import the jar into the development
classpaths.

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.

Element Attribute Description

plugin The root element of plugin.xml, specify the basic information of the plugin (id, name,
provider, etc...)

plugin class The class of the plugin, required to implements com.vp.plugin.VPPlugin.

runtime The element specified the runtime environment of the plugin.

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..*) Path The path of the .jar or directory.

library (1..*) relativePath (optional, default: true ) Specifies whether the path is relative path.

plugin.xml element description

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)
}
}

Implementing custom action


There are 2 main components for an Action: Action and Action Controller. Action represents the outlook, Action Controller responses to work as
function call. In order to create custom action, developer needs to define the Action on xml, and implement the Action Controller on code.
Sample on XML:
<plugin>
< actionSets>
<!-- to be continued -->
</ actionSets>
<!-- to be continued -->
</plugin>

Implementing plugin P. 967


Table shows the description of elements in the above XML.

Element Attribute Description

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.

XML sample for custom action

There are differences on xml definition and code implementation of the 3 kinds of Actions (menu/toolbar, popup menu, diagram toolbar).

Custom action on menu/Toolbar


Developer can define the menu, menu item, toolbar, toolbar button and etc... on the plugin.xml. In order to trigger the menu item and toolbar button's
function call, Action Controller is required to be implemented and added into the Action. The Action Controller class on menu/toolbar actions is
com.vp.plugin.action.VPActionController.
There are 2 important attributes used on menu, action and separator: menuPath and toolbarPath .
menuPath is the path specified where is the item placed on menu, toolbarPath is the path specified where is the item placed on toolbar. The path is
formed by a set of 'name'. The 'name' is similar with the caption of the menu items (caption in English, ignores the "..." and remind the 'space'). '/' is
used as delimiter of the path. '#' is used to represent the front of the menu. Here is 4 examples will be given:

Custom Action on MenuBar

Below is the menupaths required for implementing the menus shown in the above images.

Menu "label" in XML "menupath" in XML Remarks

1 Tools Tools After the Tools menu

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

Different menupaths settings

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>

Implementing plugin P. 968


< separator
id= "sample.plugin.actions.Separator1"
menuPath= "Tools/sample.plugin.actions.Action1"
toolbarPath= "sample.plugin.actions.Toolbar1/sample.plugin.action.Action1"/>
</ actionSet>

Implementing plugin P. 969


Table shows the description of elements in the above XML.

Element Attribute Description

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..*) Specifies a toolbar,


contains the location
information of the toolbar.

toolbar (0..*) orientation [north | east |south | west] Specifies which side will
be the toolbar placed on.

toolbar (0..*) index [(number) | last |new] Based on the orientation,


where will be the
toolbar placed. e.g. the
orientation is "north" and
there is 2 rows toolbars
already. If the index is
"0", then the toolbar will
be placed on the first
row's last position. If the
index is "last", the toolbar
will be placed on the
last row, last position. If
the index is "new", the
toolbar will be placed on
the third row (new row).

menu (0..*) Specifies a menu or pull


down button on menu bar
or toolbar. It contains the
outlook information of the
menu.

action (0..*) Specifies a menu item or


button on menu bar or
toolbar. It contains the
outlook information of the
menu item.

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.

actionController Specifies the Action


Controller for the action
(the parent node in the
xml).

actionController The class name of the


Action Controller. For the
action on menu/toolbar, it
is required to implement
com.vp.plugin.action.VPActionCo

separator Specified a separator on


(0..*) menu bar or toolbar.

XML sample for menus and toolbars

Description on Code:

Implementing plugin P. 970


VPActionController (com.vp.plugin.action.VPActionController)
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;
public class ActionController implements com.vp.plugin.action.VPActionController {
// make sure there is an constructor without any parameters
public void performAction(com.vp.plugin.action.VPAction action) {
// called when the button is clicked, the parameter action represents the Action which be clicked.
// developer also can set the properties of the action
}
public void updated(com.vp.plugin.action.VPAction action) {
// *for the actions located on menu bar only
// when the parent 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)
}
}
Custom action on popup menu (context sensitive)
Developer can define the menu, menu item and separator on the popup menu shown on the diagram. The popup menu on diagram is context sensitive
which based on what diagram element or diagram is selected. In order to make the menu item trigger the function call, Action Controller is required to
be implemented. For popup menu, com.vp.plugin.action.VPContextActionController is the interface required developer to implement.
Same as Action on Menu/Toolbar, menuPath is used to specify the location of the action (menu/menu item on popup menu).
Sample on XML:
< contextSensitiveActionSet id= "sample.plugin.actions.ActionSet2">
< contextTypes all= "false">
< include type="Class"/>
<!-- ignored when contextTypes.all = true -->
< exclude type="Package"/>
<!-- ignored when contextTypes.all = false -->
</ contextTypes>
<action
id= "sample.plugin.actions.ContextAction1"
label= "Sample Action [1]"
icon= "icons/blue.png"
style= "toggle"
menuPath= "OpenSpecification">
< actionController class= "sample.plugin.actions.ContextActionController"/>
</action>
</contextSensitiveActionSet>

Implementing plugin P. 971


Table shows the description of elements in the above XML.

Element Attribute Description

contextSensitvieActionSet It is a collection of menu, action, separator on the popup menu


(0..*) 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

contextTypes It is a collection of the model of diagram element of diagram


types which the contextSensitiveActionSet is considering.

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.

Include Specify the model, diagram element or diagram type will


be considered by this ActionSet. (This will be ignored if the
contextType's attribute 'all' is assigned 'true'.

Include type It is type of the element. Such as "Class", "Actor",


"ClassDiagram", "Attribute", etc...

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'.

type It is type of the element. Such as "Class", "Actor",


"ClassDiagram", "Attribute", etc...

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.

XML sample for popup menu

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).

Custom diagram element (shape and connector)


Developer can define the shape of connect on the specified diagram. But it is not allowed to develop a custom model. ActionSet and Action are used
on definition of custom diagram element.
Sample on XML:

Implementing plugin P. 972


<actionSet id= "sample.plugin.actions.ShapeActionSet">
<action
id= "sample.plugin.actions.ShapeAction1"
actionType= "shapeAction"
label= "Sample Action {1}"
tooltip= "Sample Action {1}"
icon= "icons/yellow.png"
editorToolbarPath= "com.vp.diagram.ClassDiagram/Class">
< shapeCreatorInfo
shapeType= "sample.plugin.shape.Shape1"
defaultWidth= "30"
defaultHeight= "30"
controllerClass= "sample.plugin.actions.ShapeController1"
multilineCaption= "false"
captionStyle= "north"
resizable= "true"/>
</action>
<action
id= "sample.plugin.actions.ConnectorAction1"
actionType= "connectorAction"
label= "Sample Action {2}"
tooltip= "Sample Action {2}"
icon= "icons/green.png"
editorToolbarPath= "com.vp.diagram.ClassDiagram/sample.plugin.actions.ShapeAction1">
<connectorCreatorInfo
shapeType= "sample.plugin.connector.Connector1"
fromArrowHeadStyle= "Arrow1"
toArrowHeadStyle= "Arrow2"
fromArrowHeadSize= "verySmall"
toArrowHeadSize= "large"
dashes= "7,10"
lineWeight= "3"
connectorStyle= "rectilinear">
< connectionRules>
< connectionRule
fromShapeType= "sample.plugin.shape.Shape1"
toShapeType= "sample.plugin.shape.Shape1"
bidirection= "true"/>
< connectionRule
fromShapeType= "Class"
toShapeType= "sample.plugin.shape.Shape1"
bidirection= "true"/>
<connectionRule
fromShapeType= "Package"
toShapeType= "sample.plugin.shape.Shape1"
bidirection= "true"/>
</connectionRules>
</connectorCreatorInfo>
</action>
</actionSet>

Implementing plugin P. 973


Table shows the description of elements in the above XML.

Element Attribute Description

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.

Action editorToolbarPath Specify which


diagram toolbar
contains
this action.
e.g. to add a
shapeAction on
class diagram
after the button
for creating
a new class,
"com.vp.diagram.ClassDia
Class" should
be assigned.
"com.vp.diagram.ClassDia
is the id of
the class
diagram. "/" is
the delimiter.
"Class" is the
button id.

shapeCreatorInfo If the
actionType is
"shapeAction",
shapeCreatorInfo
is required. It is
used to specify
the details of the
custom shape.

shapeCreatorInfo shapeType The shape


type assigned
by developer,
unique value is
required.

shapeCreatorInfo captionStyle [center | north | none] (optional) Specify where


the caption of
the shape is
displayed.

shapeCreatorInfo controllerClass The class name


which the class
is responsible to
Implementing draw
pluginthe shape
P. 974
on the diagram,
Description on Code:
VPShapeController ( com.vp.plugin.diagram.VPShapeController)
It response to handle the outlook of the shape on the diagram.
Sample:
package sample.plugin.actions;
// import the necessaries
public class ShapeController implement com.vp.plugin.diagram.VPShapeController {
public void drawShape(
Graphics2D g, Paint lineColor, Paint fillColor, Stoke stroke,
Com.vp.plugin.diagram.VPShapeInfo shapeInfo
){
// draw the shape by the graphics
// shapeInfo contains the information of the shape, e.g. the bounds of the shape.
}
public boolean contains( int x, int y, com.vp.plugin.diagram.VPShapeInfo shapeInfo) {
// check whether the x, y is inside the shape,
// it is used to checking what is selected by the user
}
}

Working with models


Plugin Support provides interface for the developer to create, retrieve update and delete the models in VP-UML. The base class of the model is
com.vp.plugin.model.IModelElement. All models are contained in the project ( com.vp.plugin.model.IProject). Each model has a model type, to
access all the model type, please refers to the class com.vp.plugin.model.IModelElementFactory, it is the class to create the models.

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

Implementing plugin P. 975


public void update(VPAction action, VPContext context) {
IModelElement modelElement = context.getModelElement();
// model element retrieved, but please take care,
// context.getModelElement() may return null if the popup menu is shown for the diagram
// or the selected diagram element doesn't refer to a model element.
}
/*
* retrieve relationship model from a class model
* there are 2 kinds of relationships: IRelationship and IEndRelationship
*/
// assume in a code segment
IClass classModel = ...; // retrieved the class model from somewhere
// retrieve a generalization (IRelationship)
Iterator genIter = classModel.fromRelationshipIterator();
while (genIter.hasNext()) {
IRelationship relationship = (IRelationship) genIter.next();
// found out the another side's model of the relationship
IModelElement otherModel = relationship.getTo();
}
// retrieve am association (IEndRelationship)
Iterator assoIter = classModel.fromRelationshipEndIterator();
while (assoIter.hasNext()) {
IRelationshipEnd relationshipEnd = (IRelationshipEnd) assoIter.next();
IModelElement otherModel = relationshipEnd.getEndRelationship().getToEnd().getModelElement();
}
Updating model
Developer can call a set of get/set methods on a model. Different model type has different properties. For setting and getting the model's property, cast
the IModelElement into it sub-class is necessary. For example, developer get the IModelElement from the popup menu's context. Developer check
whether the model is a IClass, then developer cast the IModelElement into IClass, and call the function IClass.setVisibility(xxx).
Sample on Code:
/*
* update a class model
*/
// assume in a code segment
IModelElement model = ...; // model is retrieved from somewhere
If (IModelElementFactory. MODEL_TYPE_CLASS.equals(model.getModelType()) ) {
IClass classModel = (IClassModel) model;
// set the class to be 'private'
classModel.setVisibility(IClass. VISIBILITY_PRIVATE);
// set super class
IClass superClassModel = ...; // another class model is retrieved, it will be set to be the previous model's super class
IGeneralization generalizationModel = IModelElementFactory.instance().createGeneralization();
generalizationModel.setFrom(superClassModel);
generalizationModel.setTo(classModel);
// get all "setName" operation from the class and set to be "protected final"
Iterator operationIter = classModel.operationIterator();
while (operationIter.hasNext()) {
IOperation operation = (IOperation) operationIter.next();
if ( "setName".equals(operation.getName()) ) {
operation.getJavaDetail( true).setJavaFinal( true);
operation.setVisibility(IOperation. VISIBILITY_PROTECTED);
}
}
}
Deleting model
Developer can delete the model by simple way, just call the IModelElement.delete().

Working with diagrams/Diagram elements


Plugin Support provides interface for the developer to create, retrieve update and delete the diagrams or diagram elements in VP-UML. The base class
of the diagram is co m.vp.plugin.diagram.IDiagramUIModel. The base class of the diagram element is com.vp.plugin.diagram.DiagramElement.
All diagrams are contained in the project ( com.vp.plugin.model.IProject). And the diagram elements can be found in the diagrams. The diagram
elements can contains by the diagrams.

Creating diagrams/Diagram elements


Developer can create the diagram or diagram element by com.vp.plugin.DiagramManager. DiagramManager can be access by
ApplicationManager.instance().getDiagramManager().
Sample on Code:
// assume in a code segment
DiagramManager diagramManager = ApplicationManager.instance().getDiagramManager();
/*
* create diagram
*/
IDiagramUIModel diagram = diagramManager.createDiagram(DiagramManager. DIAGRAM_TYPE_CLASS_DIAGRAM);
/*
* create diagram element with exists models

Implementing plugin P. 976


*/
IModelElement classModel1 = ...; // retrieved a class model from somewhere
IModelElement packageModel1 = classModel1.getParent(); // assume the class model is contained by a package
IDiagramElement packageDiagramElement1 = diagramManager.createDiagramElement(diagram, packageModel1);
IDiagramElement classDiagramElement1 = diagramManager.createDiagramElement(diagram, classModel1);
// class's diagram element should be a shape, not a connector
packageDiagramElement1.addChild((IShapeUIModel) classDiagramElement1);
/*
* create diagram element without models (the model will be created automatically)
*/
IDiagramElement newClassDiagramElement =
diagramManager.createDiagramElement(diagram, IClassDiagramUIModel. SHAPETYPE_CLASS);
IModelElement newClassModel = newClassDiagramElement.getModelElement();
/*
* open the created diagram
*/
diagramManager.openDiagram(diagram);
Retrieving diagrams/Diagram elements
Developer can use the project ( com.vp.plugin.model.IProject) to retrieve the diagrams. Use a diagram ( com.vp.plugin.diagram.IDiagramUIModel)
to retrieve the contained diagram elements. Or use the context ( com.vp.plugin.action.VPContext) from ActionController to retrieve the diagram and/
or diagram element.
IProject is the project of VP-UML. The project contains all models, diagram and diagram elements. It provides function ( diagramIterator()) for the
developer to iterate the diagrams.
IDiagramUIModel is a diagram, which may contain many diagram elements.
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 diagram and/or diagram elements.
Sample on Code:
/*
* retrieve diagram from IProject
*/
// assume in a code segment
IProject project = ApplicationManager.instance().getProjectManager().getProject();
Iterator diagramIter = project.diagramIterator();
while (diagramIter.hasNext()) {
IDiagramUIModel diagram = (IDiagramUIModel) diagramIter.next();
/*
* retrieve diagram element from IDiagramUIModel
*/
Iterator diagramElementIter = diagram.diagramElementIterator();
while (diagramElementIter.hasNext()) {
IDiagramElement diagramElement = (IDiagramElement) diagramElementIter.next();
}
}
/*
* retrieve diagram and diagram element from VPContext
*/
// assume on a sub-class of com.vp.plugin.action.VPContextActionController
public void update(VPAction action, VPContext context) {
IDiagramUIModel diagram = context.getDiagram();
IDiagramElement diagramElement = context.getDiagramElement();
// diagramElement may be null, if the popup menu shown for the diagram
}
/*
* retrieve connected connector from a shape
* because a connector can connected with both Shape and Connector, please check the
* both getToShape() and getToConnector() or getFromShape() and getFromConnector()
*/
// assume in a code segment
IShapeUIModel shape = ...; // retrieved the shape from somewhere
IConnectUIModel[] connectors = shape.toFromConnectorArray();
int count = connectors == null ? 0 : connectors. length;
for ( int i = 0; i < count; i++) {
IDiagramElement toDiagramElement = connectors[i].getToShape();
if (toDiagramElement == null) {
toDiagramElement = connectors[i].getToConnector();
}
}
Updateing diagrams/Diagram elements
IDiagramUIModel provides the functions to set the diagram outlook (size, background, etc...).
IDiagramElement is the super class of IShapeUIModel and IConnectorUIModel. Because there is difference between shape and connector, the
IShapeUIModel and IConnectorUIModel provide different set of functions to update them.
Sample Code:
/*
* update a shape's size and set a connector's connector style

Implementing plugin P. 977


*/
// assume in a code segment
IShapeUIModel shape = ...; // retrieved the shape from somewhere
shape.setBounds(20, 20, 400, 400);
IConnector connector = ...; // retrieved the connector from somewhere
connector.setConnectorStyle(IConnector. CS_CURVE);
Deleting diagrams/Diagram elements
Developer can delete the diagram and diagram element by simple way, just call the IDiagramUIModel.delete() and IDiagramElement.delete().

Showing dialog on VP-UML


Since VP-UML may be integrated with different platforms which may not support Swing (e.g. Eclipse, Visual Studio). That may make to hang on the
process if using the Swing dialog technology (e.g. JOptionPane and JDialog). So, there is necessary to use a special method to show the dialog with
Swing technology.
com.vp.plugin.ViewManager is an interface provides function for developer to show the dialog as same as show dialog by JOptionPane. Besides
that, Viewmanager supports developer to show message on VP-UML's message pane and show custom dialog by implementing an interface (
com.vp.plugin.view.IDialogHandler).
Same as JOptionPane, to show a dialog, it is better to have a component as the invoker/parent component. To get the component in VP-UML, just call
ViewManager.getRootFrame().

Showing message on message pane


ViewManager provides function showMessage(msg:String, msgTabId:String) to show the message on Message Pane. The parameter msg is the
content of the message, msgTabId is the id to identify the tab on Message Pane, which can be defined by developer.

Message in Message Pane

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.

Showing custom dialog


In Swing, we may implement the javax.swing.JDialog and add our component on the dialog's content pane. But in plugin, developer is required to
implement an interface com.vp.plugin.view.IDialogHandler to work for the dialog.
IDialogHandler specify the behaviors of a dialog. There are 4 functions need to be implemented.
getComponent() : java.awt.Component
It is called once before the dialog is shown. Developer should return the content of the dialog (similar to the content pane).
prepare(dialog : com.vp.plugin.view.IDialog) : void
It is called after the getComponent(). A dialog is created on VP-UML internally (it still not shown out). Developer can set the outlook of the dialog on
prepare(), such as title, bounds and modal, etc... For your convenience, the dialog will be shown on the screen center as default. If developer don't
want change the location, there is no necessary to call the setLocation() function.
shown()
It is called when the dialog is shown. Developer may need to do something when the dialog is shown, such as checking something before user to input
data on the dialog.
canClosed()
It is called when the dialog is closed by the user clicking on the close button of the frame. Developer may not allow the user to close the dialog (e.g.
failed on validation check), then please return 'false' on canClosed().
Sample on Code:
package sample.plugin.dialog;
// assume imported necessary classes
public class CustomDialogHandler implements IDialogHandler {
private IDialog _dialog;
private Component _component;
private JTextField _inputField1, _inputField2, _answerField;
public Component getComponent() {
this._inputField1 = new JTextField(10);
this._inputField2 = new JTextField(10);
this._answerField = new JTextField(10);
JLabel addLabel = new JLabel( " + "); JLabel equalLabel = new JLabel( " = ");
JButton okButton = new JButton( "Apply");
okButton.addActionListener( new ActionListener() {

Implementing plugin P. 978


public void actionPerformed(ActionEvent e) { ok();}
} );
JPanel pane = new JPanel();
pane.add( this._inputField1); pane.add(addLabel); pane.add( this._inputField2);
pane.add(equalLabel); pane.add( this._answerField); pane.add(okButton);
this._component = pane;
return pane;
}
public void prepare(IDialog dialog) {
this._dialog = dialog;
dialog.setModal(true);
dialog.setTitle( "Maths Test");
dialog.setResizable( false ); dialog.pack();
this._inputField1.setText(String.valueOf(( int)(Math.random()*10000)));
this._inputField2.setText(String.valueOf(( int)(Math.random()*10000)));
}
public void shown() {
ApplicationManager.instance().getViewManager().showMessageDialog(
this._component, "Maths Test is started, you have an half hour to finish this test.",
"Maths Test", JOptionPane. INFORMATION_MESSAGE
);
}
public boolean canClosed() {
if ( this.checkAnswer()) { return true; }
else {
ApplicationManager.instance().getViewManager().showMessageDialog(
this._component, "Incorrect",
"Maths Test", JOptionPane. ERROR_MESSAGE
);
return false;
}
}
private void ok() {
if ( this.checkAnswer() ) { this._dialog.close(); }
else {
ApplicationManager.instance().getViewManager().showMessageDialog(
this._component, "Incorrect",
"Maths Test", JOptionPane. ERROR_MESSAGE
);
}
}
private boolean checkAnswer() {
try {
int a = Integer.parse Int( this._inputField1.getText());
int b = Integer.parse Int( this._inputField2.getText());
int c = Integer.parse Int( this._answerField.getText());
return (a+b == c);
}
catch (Exception ex) { return false; }
}
}

Implementing plugin P. 979


Deploying plugin
After prepared all the required files for a plugin (plugin.xml, plugin.properties, classes/libraries and other resources), developer can plug the plugin into
VP-UML.
First, create a folder named plugins (notice the ' s') in the VP-Suite directory. Put the plugin files into "%VP-SUITE%\plugins\%PLUGIN_ID%\".
%PLUGIN_ID% is a directory named as the plugin id (use the id as the directory name to avoid duplicated directories defined in plugins)
The following structure should be obtained:
%VP_SUITE%
bin
lib
...
plugins
sample.plugin (%PLUGIN_ID %)
plugin.xml
plugin.properties
classes
sample (package)
... (other packages or classes or resources)
lib
sampleplugin.jar
... (others .jar)
icons (others resources)
red.png
...(other resources)
Below is an example of VP Suite installation folder with plugin created in the plugins folder.

Plugin folder structure

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.

Deploying plugin P. 980


Exporting diagram image
To export images from a project through command line:
1. Browse the scripts folder under the VP Suite installation directory.

The scripts folder inside VP Suite installation directory

Exporting diagram image P. 981


2. Copy the script file ExportDiagramImage and paste to the bin folder of VP Suite installation directory.

Copy and paste ExportDiagramImage from scripts folder to bin folder

3. Start the command prompt.


4. Navigate to the bin folder of VP Suite installation directory.

Navigate to the bin folder of VP Suite in command prompt

Exporting diagram image P. 982


5. Execute the script by supplying the required parameters. For example:
ExportDiagramImage -project C:\Demo\Demo.vpp -out C:\Demo\Output -diagram "*" -type jpg

Executing ExportDiagramImage

Below is a description of parameters:


Parameter Description Example

-project Project path C:


\Demo
\Demo.vpp

-out Folder for storing the exported images C:


\Demo
\Output

-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

Parameters for ExportDiagramImage

Exporting diagram image P. 983


Exporting and import XMI
VP-UML supports interoperability with XMI file, a standard made for data exchange. You can export project data to an XMI, edit it externally with other
softwares that accepts XMI. In this chapter, you will see how to export and import XMI through the command line interface.

Exporting XMI
To export XMI from a project through command line:
1. Browse the scripts folder under the VP Suite installation directory.

The scripts folder inside VP Suite installation directory

Exporting and importing XMI P. 984


2. Copy the script file ExportXMI and paste to the bin folder of VP Suite installation directory.

Copy and paste ExportXMI from scripts folder to bin folder

3. Start the command prompt.


4. Navigate to the bin folder of VP Suite installation directory.

Navigate to the bin folder of VP Suite in command prompt

Exporting and importing XMI P. 985


5. Execute the script by supplying the required parameters. For example:
ExportXMI -project C:\Demo\Demo.vpp -out C:\Demo\Output\Sample.xmi -type 2.1

Executing ExportXMI

Below is a description of parameters:


Parameter Description Example

-project Project path C:


\Demo
\Demo.vpp

-out The filepath of XMI file C:


\Demo
\Output
\sample.xmi

-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

-encoding [optional] Encoding of XMI file

Parameters for ExportXMI

Importing XMI
To import XMI to a project through command line:

Exporting and importing XMI P. 986


1. Browse the scripts folder under the VP Suite installation directory.

The scripts folder inside VP Suite installation directory

2. Copy the script file ImportXMI and paste to the bin folder of VP Suite installation directory.

Copy and paste ImportXMI from scripts folder to bin folder

Exporting and importing XMI P. 987


3. Start the command prompt.
4. Navigate to the bin folder of VP Suite installation directory.

Navigate to the bin folder of VP Suite in command prompt

5. Execute the script by supplying the required parameters. For example:


ImportXMI -project C:\Demo\Demo.vpp -file C:\Demo\input\sample.xmi

Executing ImportXMI

Below is a description of parameters:


Parameter Description Example

-project Project path C:\Demo\Demo.vpp

-file The filepath of the XMI file to import C:\Demo\input


\sample.xmi

Parameters for ImportXMI

Exporting and importing XMI P. 988


Exporting and import XML
You can export project data to an XML, manipulate it externally, and feed the changes back to VP-UML. In this chapter, you will see how to export and
import XML file through the command line interface.

Exporting XML
To export XML and images from a project through command line:
1. Browse the scripts folder under the VP Suite installation directory.

The scripts folder inside VP Suite installation directory

Exporting and importing XML P. 989


2. Copy the script file ExportXML and paste to the bin folder of VP Suite installation directory.

Copy and paste ExportXML from scripts folder to bin folder

3. Start the command prompt.


4. Navigate to the bin folder of VP Suite installation directory.

Navigate to the bin folder of VP Suite in command prompt

Exporting and importing XML P. 990


5. Execute the script by supplying the required parameters. For example:
ExportXML -project C:\Demo\Demo.vpp -out C:\Demo\Output

Executing ExportXML

Below is a description of parameters:


Parameter Description Example

-project Project path C:\Demo\Demo.vpp

-out Folder for storing the exported XML and images C:\Demo\Output

- One or more diagrams to be exported "Diagram A" "Diagram


diagram B"

- Do not export image files for diagrams N/A


noimage

- Whether to embed referenced projects' content inline true


refmodel

Parameters for ExportXML

Importing XML
To import XML to a project through command line:

Exporting and importing XML P. 991


1. Browse the scripts folder under the VP Suite installation directory.

The scripts folder inside VP Suite installation directory

2. Copy the script file ImportXML and paste to the bin folder of VP Suite installation directory.

Copy and paste ImportXML from scripts folder to bin folder

Exporting and importing XML P. 992


3. Start the command prompt.
4. Navigate to the bin folder of VP Suite installation directory.

Navigate to the bin folder of VP Suite in command prompt

5. Execute the script by supplying the required parameters. For example:


ImportXML -project C:\Demo\Demo.vpp -file C:\Demo\input\project.xml

Executing ImportXML

Below is a description of parameters:


Parameter Description Example

-project Project path C:\Demo\Demo.vpp

-file The filepath of the XML file to import C:\Demo\input


\sample.xml

Parameters for ImportXML

Exporting and importing XML P. 993


Generating ORM code and/or database
Generation of ORM code and database can be done through the command line interface. To do this:
1. Browse the scripts folder under the VP Suite installation directory.

The scripts folder inside VP Suite installation directory

Generating ORM code and/or database P. 994


2. Copy the script file GenerateORM and paste to the bin folder of VP Suite installation directory.

Copy and paste GenerateORM from scripts folder to bin folder

3. Start the command prompt.


4. Navigate to the bin folder of VP Suite installation directory.

Navigate to the bin folder of VP Suite in command prompt

Generating ORM code and/or database P. 995


5. Execute the script by supplying the required parameters. For example:
GenerateORM -project C:\Demo\Demo.vpp -out C:\Demo\Output -code -ddl

Executing GenerateORM

Below is a description of parameters:


Parameter Description Example

-project Project path C:


\Demo
\Demo.vpp

-out Folder for storing the generated files including the source code, required libraries and mapping XML C:
\Demo
\Output

-code [optional] Include to generate code. -


code

-ddl [optional] Include to export DDL -


ddl

-exportdb [optional] Include to export database -


exportdb

Parameters for GenerateORM

Generating ORM code and/or database P. 996


Generating report through command line
To generate HTML/PDF/Word report from a project through command line:
1. Browse the scripts folder under the VP Suite installation directory.

The scripts folder inside VP Suite installation directory

Generating report through command line P. 997


2. Copy the script file GenerateReport and paste to the bin folder of VP Suite installation directory.

Copy and paste GenerateReport from scripts folder to bin folder

3. Start the command prompt.


4. Navigate to the bin folder of VP Suite installation directory.

Navigate to the bin folder of VP Suite in command prompt

Generating report through command line P. 998


5. Execute the script by supplying the required parameters. For example:
GenerateReport -project C:\Demo\Demo.vpp -out C:\Demo\Output\MyReport.pdf -type pdf -all

Executing GenerateReport

Below is a description of parameters:


Parameter Description Example

-project Project path C:


\Demo
\Demo.vpp

-out The file or folder path of generated report file(s) C:


\Demo
\Output
\MyReport.p

-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

Parameters for GenerateReport

Generating report through command line P. 999


Instant generator
To generate code from a project through command line:
1. Browse the scripts folder under the VP Suite installation directory.

The scripts folder inside VP Suite installation directory

Instant generator P. 1000


2. Copy the script file InstantGenerator and paste to the bin folder of VP Suite installation directory.

Copy and paste InstantGenerator from scripts folder to bin folder

3. Start the command prompt.


4. Navigate to the bin folder of VP Suite installation directory.

Navigate to the bin folder of VP Suite in command prompt

Instant generator P. 1001


5. Execute the script by supplying the required parameters. For example:
InstantGenerator -project C:\Demo\Demo.vpp -out C:\Demo\Output

Executing InstantGenerator

Below is a description of parameters:


Parameter Description Example

-project Project path C:


\Demo
\Demo.vpp

-out The folder path of generated source files C:


\Demo
\Output

-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

Parameters for InstantGenerator

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.

Instant generator P. 1002


Instant reverse
To reverse source code to a project through command line:
1. Browse the scripts folder under the VP Suite installation directory.

The scripts folder inside VP Suite installation directory

Instant reverse P. 1003


2. Copy the script file InstantReverse and paste to the bin folder of VP Suite installation directory.

Copy and paste InstantReverse from scripts folder to bin folder

3. Start the command prompt.


4. Navigate to the bin folder of VP Suite installation directory.

Navigate to the bin folder of VP Suite in command prompt

Instant reverse P. 1004


5. Execute the script by supplying the required parameters. For example:
InstantReverse -project C:\Demo\Demo.vpp -path C:\Demo\MyProject\src -lang Java -pathtype folder -sourcetype source

Executing InstantReverse

Below is a description of parameters:


Parameter Description Example

-project Project path C:


\Demo
\Demo.vpp

-path The file or folder path of the source files to be reversed C:


\Demo
\Output
\src

-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

-overwrite | -update Overwrite or update model from code -


overwrite

Parameters for InstantReverse

Instant reverse P. 1005


Java code synchronization
To perform synchronization between model and Java code through command line:
1. Browse the scripts folder under the VP Suite installation directory.

The scripts folder inside VP Suite installation directory

Java code synchronization P. 1006


2. Copy the script file JavaCodeSync and paste to the bin folder of VP Suite installation directory.

Copy and paste JavaCodeSync from scripts folder to bin folder

3. Start the command prompt.


4. Navigate to the bin folder of VP Suite installation directory.

Navigate to the bin folder of VP Suite in command prompt

Java code synchronization P. 1007


5. Execute the script by supplying the required parameters. For example:
JavaCodeSync -project C:\Demo\Demo.vpp -src C:\Demo\MyProject\src -generate

Executing JavaCodeSync

Below is a description of parameters:


Parameter Description Example

-project Project path C:


\Demo
\Demo.vpp

-src The folder path of the source file C:


\Demo
\Output
\src

-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

Parameters for JavaCodeSync

Java code synchronization P. 1008


Project publisher
To publish project through command line:
1. Browse the scripts folder under the VP Suite installation directory.

The scripts folder inside VP Suite installation directory

Project publisher P. 1009


2. Copy the script file ProjectPublisher and paste to the bin folder of VP Suite installation directory.

Copy and paste ProjectPublisher from scripts folder to bin folder

3. Start the command prompt.


4. Navigate to the bin folder of VP Suite installation directory.

Navigate to the bin folder of VP Suite in command prompt

Project publisher P. 1010


5. Execute the script by supplying the required parameters. For example:
ProjectPublisher -project C:\Demo\Demo.vpp -out C:\Demo\Output

Executing ProjectPublisher

Below is a description of parameters:


Parameter Description Example

-project Project path C:\Demo


\Demo.vpp

-out The folder path of the files to be published C:\Demo


\Output

Parameters for ProjectPublisher

Project publisher P. 1011


Updating teamwork project from server
To update Teamwork project from server through command line:
1. Browse the scripts folder under the VP Suite installation directory.

The scripts folder inside VP Suite installation directory

Updating teamwork project from server P. 1012


2. Copy the script file ProjectPublisher and paste to the bin folder of VP Suite installation directory.

Copy and paste UpdateTeamworkProject from scripts folder to bin folder

3. Start the command prompt.


4. Navigate to the bin folder of VP Suite installation directory.

Navigate to the bin folder of VP Suite in command prompt

Updating teamwork project from server P. 1013


5. Execute the script by supplying the required parameters. For example:
UpdateTeamworkProject -project "C:\vpworkspace\teamwork_client\projects\MarketManagementSystem\MarketManagementSystem.vpp" -
workspace "C:\vpworkspace"

Executing UpdateTeamworkProject

Below is a description of parameters:


Parameter Description Example

-project Project path C:\Demo


\Demo.vpp

- The path of workspace of the supplied project C:


workspace \vpworkspace

Parameters for UpdateTeamworkProject

Updating teamwork project from server P. 1014


Executing operations with Apache Ant in VP-UML
Apache Ant is a software tool for automating software build processes. It is written in the Java language and is primarily intended for use with Java. If
you are not familiar with Ant, you can find more information about it at Ant's webpage . To execute commands with Ant:
1. Browse the scripts folder under the VP Suite installation directory.

The scripts folder inside VP Suite installation directory

2. Copy the script file build.xml and paste to the bin folder of VP Suite installation directory.

Copy and paste build.xml from scripts folder to bin folder

Executing operations with Apache Ant P. 1015


3. Open the build file in any text editor. Modify the properties vpsuiteInstallationPath, vpproduct, vpworkspace and headless to suit your
environment.

To modify basic properties in build.xml

4. Modify task(s) specific parts by changing the values of parameters. For details about the parameters, refer to previous sections.

Modify task(s) specific properties in build.xml

5. Save the changes and exit.


6. Start the command prompt and navigate to the bin folder of VP Suite installation directory.

Executing operations with Apache Ant P. 1016


7. Enter ant build.xml, and then the task name to execute specific task.

Execute an ant script

Executing operations with Apache Ant P. 1017


Printing diagrams
The Print window dialog box allows you to preview the printout and provides a set of options for changing the printout style. To unfold the Print window
dialog box, select File > Print... from main menu.

To Perform Printing

An overview of Print window

Print preview dialog box

Printing diagrams P. 1018


The toolbar of the print preview pane allows you to configure the print settings. The buttons and their description are shown in the table below:

Button Name Description

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.

Adjust Margin Adjust the margins of the pages.

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.

Zoom Select the percentage to reduce/enlarge the print preview of diagrams.

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.

Border Determine whether to add frame or boder around diagram in printout.

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.

Help Call the VP-UML help file.

Close Print Preview Close the print preview pane and return to the design area.

Details of toolbar

Printing a diagram with preview


You can use the Print command to select the printer. Set the range of pages and number of copies to be printed.

Printing diagrams P. 1019


1. Select the desired diagram(s) for printing. The selected diagram(s) will be shown in the preview area.

Diagram preview

2.
Click the Print button on the Print preview toolbar. The Print dialog box will be shown.

The Print dialog box

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.

Printing diagrams P. 1020


Page setup
Page Setup allows you to specify the page size, orientation, as well as the margins of the pages.

The Page setup dialog box

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.

Printing diagrams P. 1021


Adjusting margins
The Margins pane allows user to specify the margins of the pages, header and footer.

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.

Set zoom ratio

Printing diagrams P. 1022


2. The preview area will show the diagrams in the zoom ratio that you have selected.

Preview in Preview dialog box

Selecting the preview layout


There are two layouts that you can choose for the print preview, the Paper Base Layout and the Diagram Base Layout.
If the Fit to Pages option is chosen and there are multiple pages in the printout, 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.

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.

Printing diagrams P. 1023


The preview after applying the Paper Base Layout:

Preview in paper base layout

The preview after applying the Diagram Base Layout:

Preview in diagram base layout

Setting paper place style


You can select the paper place style to change the order of the printout. To select the paper place style, click the Paper Place Style button on the
toolbar. A pop-up menu where you can choose a paper place style will appear.
Considering a large diagram is divided into many pages, choose 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.

Printing diagrams P. 1024


The order of the printout after choosing From left to right:

Printout order is left to right

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.

Printing diagrams P. 1025


2.
Click the Multiple Page Mode button on the toolbar. The page selector will appear.

Select multiple 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

Setting the diagram overlap percentage


Overlapping is used when users want the diagrams to be overlapped at the boundaries between pages. This is particularly useful when you have a
large diagram that span multiple pages and you want to stick the pages of the printout together; the overlapping area can then be used as a hint when
sticking the pages.

Multiple page without overlap

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.

Multiple page with overlap

Printing diagrams P. 1026


Printing with frame/Border option
You can print your diagram with a frame or border. There are three options available:
• With frame
• With border
• No border
Select With frame/ With border/ No border option from the drop-down menu.

Select an option from drop-down menu

Output of printing with frame:

Printing with frame

Output of printing with border:

Printing with border

Printing diagrams P. 1027


Output of printing with no border:

Printing with no border

Showing/Hiding clip marks on page


Clip marks act as an indication of the boundary of a page.

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.

Printing diagrams P. 1028


Editing header/footer of the pages

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.

Editing header/footer of pages

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.

Printing diagrams P. 1029


There is a toolbar between the Header panel and the Footer panel, which facilitates the editing of header/footer. The description of the buttons in the
toolbar can be found in the following table:

Button Name Description

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.

The description of editing of header/ footer toolbar

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:

Page with header and footer

The multiple page mode


The Multiple Page Mode allows users to configure how the diagrams should be distributed in multiple pages. To switch to the Multiple Page Mode, click

the Multiple Page Mode button on the toolbar.

Printing diagrams P. 1030


Click the icon behind Multiple Pages will pop the page selector out, where you can select the row-column combination for the printout. Alternatively,
you can type in the Row and Column text field directly.

Select multiple pages

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.

Distributes diagram in multiple page

After you have finished configuring the multiple page settings, click the Close Multiple Page Mode button to close it.

Printing diagrams P. 1031


Printing a Diagram with Quick Print
The Quick Print feature allows you to print diagrams without previewing them, hence speeding up the print job. To quick print, perform one of the
following actions:
• Select File > Quick Print... from main menu

Select File > Print... from main menu. This displays the Print Preview dialog box. Click on the toolbar of the Print Preview dialog box.
In both cases, the Quick Print dialog box will show.

Quick print dialog

No. Name Description

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.

3 Border option Select border option of printout.

4 Page Setup... Page Setup allows you to specify the page size, the orientation as well as the margins of the pages.

5 Page numbers Select to print diagrams with page number on it.

6 Use gradient Select to use gradient color in printout.


color

Details of quick print dialog

Quick print P. 1032


Introduction to team collaboration
Team collaboration is the practice of working in a team instead of by one person. Team members can work individually on their own specific parts of
a project, and eventually combine works together to form a complete project. As a result of collaborations between members by employing the unique
skills of each, works can be done more effectively and in higher quality.
VP-UML's team collaboration support provides access to a central repository for managing, sharing and versioning projects. You can let team
members get project from repository, start working on their own parts, let them commit (i.e. upload) their work to server, and update others' works.
Visual Paradigm Teamwork Server, SVN, CVS and Perforce are the supported standards of versioning systems. In this part, we will go through team
collaboration using Teamwork Server. This chapter outlines some of the key concepts in team collaboration in VP-UML.

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.

To add a project with users assigned

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.

A team member is checking out 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&rsquo;s change (i.e. revert). All conflicts must be resolved in order to proceed
with committing.

Going to commit local changes

Introduction to team collaboration P. 1033


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.

Update to obtain changes made by other team members

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

Introduction to team collaboration P. 1034


Revert changes
Revert is the process of undoing changes. In VP-UML's team collaboration support, there are two kinds of revert actions that you can perform. The
first one is to revert locally modified changes to make the working copy back to the original state. Another revert action is for undoing changes made in
revisions. Team members can undo changes made in revisions by reverting them.

To revert two revisions

Introduction to team collaboration P. 1035


The Teamwork Client with VP Teamwork Server
Teamwork Client is where you can manage, checkout and open projects. It involves all teamwork activities that you can perform with.
To launch teamwork client:
1. After entering VP-UML, select Tools > Teamwork > Open Teamwork Client... from the main menu.

Launch teamwork client from the main menu

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.

The Login to the Teamwork Server dialog box

3. In the Manage Project dialog box, select your project and click > button to manage it. Click OK to proceed.

Overview of Teamwork Client dialog box

The Teamwork Client with VP Teamwork Server P. 1036


The Teamwork Client dialog box

No. Name Description

1 Main menu Session: It is a period of active connection to Teamwork Server.


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.
Project: It provides an access to main functions, such as commit and update.
Manage Project: Select a project that you get involved in.
Import Project to Repository: Import a new project to the server.
Commit...: Commit your current modified project to the server.
Update: Update the latest copy of project from the server to your computer.
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.
Check 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 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.
Reset Password: Reset your account's password.
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.
Repair > Force Commit Local Copy: Normally, a commit action is to merge your current changes to server. By checking it, your
current modified project will replace the project copy in server. Do NOT check this option unless you are asked to do so by Visual
Paradigm's support team.
Repair > Force GC: Normally, all redundant files produced by teamwork commit action will be removed after commit. This will be
done periodically. By checking it, it will be done in every commit.

The Teamwork Client with VP Teamwork Server P. 1037


Repository: Synchronize Design Pattern to Server: Synchronize the template files stored in workspace with those stored in
repository. When a conflict occurs, you will be asked which design template files to keep.

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.

5 Projects It lists the project(s) you selected to manage.

6 Project The name of selected project.


name

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.

13 Commit Commit your current modified project to the server.

14 Checkout Click it to checkout the selected project.

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.

16 Close Click to close the Teamwork Client.

17 Help Click it to get assistance from help system.

The description of the Teamwork Client dialog box

The Teamwork Client with VP Teamwork Server P. 1038


The Revisions tab of the Teamwork server dialog box

No. Name Description

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.

20 Revert Click it to undo changes committed by the selected revisions.

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.

22 Open Click it to open the selected revision of project.

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

The description of Revisions tab

The Teamwork Client with VP Teamwork Server P. 1039


Checkout project with VP Teamwork Server
Checkout project is a process that you download a managed project from repository to your computer and start working with. Team members should
log into the Teamwork Server in VP-UML, then checkout their completed projects. Open project is to open the downloaded project in VP-UML.
After entering VP-UML, select Tools > Teamwork > Open Teamwork Client... from the main menu.

Click Open Teamwork Client... from the main menu

Checkout project with VP Teamwork Server P. 1040


When the Manage Project dialog box pops out, select the project you are going to take part in and click > button. Click OK button to proceed.

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.

The Teamwork Client dialog box

After that, the project has been downloaded from the server to your computer and you can start working on it.

Checkout project with VP Teamwork Server P. 1041


Commit with VP Teamwork Server
Commit refers to the process of uploading local modifications to the server. As team members make changes in a project, they can share their works
by committing those changes to the server. VP-UML can help to merge changes from working copy to server copy. During merging, a conflict may be
caused when there is a contradiction between team members. Decision have to be made whether to keep the current modified copy (i.e. overwrite) or
to accept others' copy (i.e. revert). All conflicts have to be solved before proceeding to commit.
To operate commit:
After entering VP-UML, select Tools > Teamwork > Commit... from the main menu to commit your modified copy to the server.

Launch commit from the main menu

Commit with VP Teamwork Server P. 1042


The Commit dialog box displays the changes to be committed to the server. Click OK to proceed.

The Commit dialog box

Overview of Commit dialog box

Commit with VP Teamwork Server P. 1043


The Commit dialog box

No. Name Description

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.

Commit with VP Teamwork Server P. 1044


5 Property view window It lists property name, current value, original value and last modified of the selected model element.

6 Project name It shows the name of current project.

7 Checkout revision It shows the number of current checkout revision.

8 Checkout time It shows the time for latest checkout.

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

12 OK Click OK to proceed committing.

13 Cancel Click Cancel to cancel committing and close the dialog box.

14 Help Click Help to get assistance from help system.

The description of Commit dialog box

The Preview tab of the Commit dialog box

No. Name Description

15 Preview Click it for previewing the selected model element(s).

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.

The description of Preview tab in the Commit dialog box

Commit with VP Teamwork Server P. 1045


Resolving conflict
When your modified copy conflicts with the copy others made previously during committing, you can resolve the conflict by clicking either Overwrite or
Revert in the Update dialog box.

Resolve conflict in the Update dialog box

Choosing Overwrite means keeping your modified copy while choosing Revert refers to accept others' copy.

Commit with VP Teamwork Server P. 1046


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).

Preview before committing

NOTE: Conflicts occur only when the same property of same shape you and other team members have made.

Commit with VP Teamwork Server P. 1047


Update
Update is the process of refreshing your current copy by merging changes that others have made and committed previously to server. Similar to
commit, update is a process of merging differences instead of overwriting. When your changes overlap the changes others have made, you will be
asked to resolve conflict. All conflicts have to be resolved before proceeding with updating.
To operate update:
After entering VP-UML, select Tools > Teamwork > Update from the main menu to update from the server.

Select Update from the main menu

Update with VP Teamwork Server P. 1048


If other team members have made changes and have committed previously to the server, your current project will cause conflicts during updating. You
can resolve the conflict by clicking either Overwrite or Revert in the Update dialog box. Choosing Overwrite means keeping your current copy while
choosing Revert refers to accept others' copy.

Resolve the conflicts

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.

Update with VP Teamwork Server P. 1049


Branching with VP Teamwork Server
In teamwork collaboration, the term trunk refers to your main stream of development. If you create a new project, you will spend the majority of your
time making changes and committing them to the trunk of your repository.
Branch is defined as a copy of work derived from a certain point in the trunk. It sets up an extra space for users to work on and make modifications
without disturbing the trunk. As soon as the modifications in branch are done, it can be merged back into the trunk.
To create a branch:
Select Tools > Teamwork > Branch... from the main menu.

Select Branch... from the main menu

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.

Create Branch dialog box

Branching with VP Teamwork Server P. 1050


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.
Select Tools > Teamwork > Merge... from the main menu.

Select Merge... from the main menu

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.

Merge dialog box

Branching with VP Teamwork Server P. 1051


Tagging with VP Teamwork Server
Tag refers to a named version of your work at a point of time on the trunk. The best application of a tag is to create it for every major release or
milestone. Note that you cannot merge a tag to the trunk nor commit it to the server.
To create a tag:
After entering VP-UML, select Tools > Teamwork > Tag... from the main menu.

Select Tag... from the main menu

In Create Tag dialog box, enter the name for a new tag in Tag Name. Click OK to proceed.

Create Tag dialog box

Tagging with VP Teamwork Server P. 1052


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.

Click Revert from the main menu

To undo all non-committed changes through teamwork client dialog box:


After entering VP-UML, select Tools > Teamwork > Open Teamwork Client... from the main menu in order to unfold teamwork client dialog box.

Revert local modification P. 1053


In Teamwork Client dialog box, either select Project > Revert... from the dialog box's main menu.

Click Revert... in teamwork client dialog box

Or click Revert... button from the dialog box's toolbar directly.

Click Revert... button

As a result, the non-committed changes are discarded.

Revert local modification P. 1054


Roll back past revisions changes
VP teamwork collaboration maintains the histories of changes on your project. With VP Teamwork Server, you can revert all modifications you did in a
specific revision. Furthermore, you can preview the differences between the server and local modified system visually.
After entering VP-UML, select Tools > Teamwork > Open Teamwork Client... from the main menu.

Click Open Teamwork Client... from the main menu

Roll back past revisions changes P. 1055


In the Teamwork Client dialog box, all your project's revisions will be shown in Project revisions under Revisions tab. Select the amount of project's
revisions you want to be listed from the drop-down menu of Show. If all actions you did in a specific revision or a few revisions you want to undo, select
the revision(s) with Ctrl key and click Revert button under Project revisions.

Teamwork Client dialog box

Roll back past revisions changes P. 1056


When the Commit dialog box pops out, you have to resolve all conflicts before proceed reverting. Click either Overwrite button or Revert button.
Choosing Overwrite means keeping the latest copy while choosing Revert refers to accept the selected revision. You can preview the differences
between the server (the latest revision in server) and the local modified (the selected revision) under Preview tab. After fixing all conflicts, click OK to
proceed reverting.

Resolving conflicts in Commit dialog box

Roll back past revisions changes P. 1057


Export revision with VP Teamwork Server
VP teamwork collaboration maintains the histories of changes on your project. With VP teamwork server, you can export the selected revision or all
revisions to your computer for reviewing the project content in past revisions.

Export the selected revision


1. After entering VP-UML, select Tools > Teamwork > Open Teamwork Client... from the main menu.

Select Open Teamwork Client... from the main menu

Export revision P. 1058


2. In the Teamwork Client dialog box, unfold Revisions tab. Select the revisions(s) you want to export under Project revisions, click Export
button and choose Export selected revisions... from the pop-up menu.

Choosing Export selected revisions... in Teamwork Client dialog box

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

Export all revisions from repository


1. After entering VP-UML, select Tools > Teamwork > Open Teamwork Client... from the main menu.

Export revision P. 1059


2. In the Teamwork Client dialog box, unfold Revisions tab. Click Export button and choose Export all revisions from repository... from the
pop-up menu. Note that choosing Export all revisions from repository... means exporting all revisions of the selected project.

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.

Export revision P. 1060


Introduction to team collaboration
Team collaboration is the practice of working in a team instead of by one person. Team members can work individually on their own specific parts of
a project, and eventually combine works together to form a complete project. As a result of collaborations between members by employing the unique
skills of each, works can be done more effectively and in higher quality.
VP-UML's team collaboration support provides access to a central repository for managing, sharing and versioning projects. You can let team members
get project from repository, start working on their own parts, let them commit (i.e. upload) their work to server, and update others' works. Visual
Paradigm Subversion, SVN, CVS and Perforce are the supported standards of versioning systems. In this part, we will go through team collaboration
using Subversion. This chapter outlines some of the key concepts in team collaboration in VP-UML.

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.

A team member is importing a project

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&rsquo;s change (i.e. revert). All conflicts must be resolved in order to proceed
with committing.

Commit local changes

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.

Update changes made by other team members

Introduction to team collaboration with Subversion P. 1061


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

Introduction to team collaboration with Subversion P. 1062


Revert changes
Revert is the process of undoing changes. In VP-UML's team collaboration support, there are two kinds of revert actions that you can perform. The
first one is to revert locally modified changes to make the working copy back to the original state. Another revert action is for undoing changes made in
revisions. Team members can undo changes made in revisions by reverting them.

Revert revision

Introduction to team collaboration with Subversion P. 1063


The Teamwork Client
Teamwork Client is where you can manage, checkout and open projects. It involves all teamwork activities that you can perform with.
To launch teamwork client:
1. After entering VP-UML, select Tools > Teamwork > Open Teamwork Client... from the main menu.

Launch teamwork client from the main menu

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.

The Login to the Teamwork Server dialog box

3. In the Manage Project dialog box, select your repository and click OK button to proceed.

Overview of Teamwork Client dialog box

The Teamwork Client with Subversion P. 1064


The Teamwork Client dialog box

No. Name Description

1 Main menu Session: It is a period of active connection to SVN.


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.
Project: It provides an access to main functions, such as commit and update.
Manage Project: Select a project that you get involved in.
Import Project to Repository: Import a new project to the server.
Commit...: Commit your current modified project to the server.
Update: Update the latest copy of project from the server to your computer.
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.
Check 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 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.
Reset Password: Reset your account's password.
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.
Repair > Force Commit Local Copy: Normally, a commit action is to merge your current changes to server. By checking it, your
current modified project will replace the project copy in server. Do NOT check this option unless you are asked to do so by Visual
Paradigm's support team.
Repair > Force GC: Normally, all redundant files produced by teamwork commit action will be removed after commit. This will be
done periodically. By checking it, it will be done in every commit.

The Teamwork Client with Subversion P. 1065


Repository: Synchronize Design Pattern to Server: Synchronize the template files stored in workspace with those stored in
repository. When a conflict occurs, you will be asked which design template files to keep.
Synchronize Design Pattern Option...: Set the path for storing design pattern files, relative to repository root.

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.

4 Project It lists the project(s) you selected to manage.

5 Project The name of selected project.


name

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.

10 URL It displays the URL of your current project.

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.

13 Commit Commit your current modified project to the server.

14 Checkout Click it to checkout the selected project.

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.

16 Close Click to close the Teamwork Client.

17 Help Click it to get assistance from help system.

The description of the Teamwork Client dialog box

The Teamwork Client with Subversion P. 1066


The Revisions tab of the Teamwork server dialog box

No. Name Description

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.

20 Revert Click it to undo changes committed by the selected revisions.

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.

22 Open Click it to open the selected revision of project.

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

The description of Revisions tab

The Teamwork Client with Subversion P. 1067


Checkout project
Checkout project is a process that you download a managed project from repository to your computer and start working with. Team members should
log into the Subversion in VP-UML, then checkout their completed projects. Open project is to open the downloaded project in VP-UML.
After entering VP-UML, select Tools > Teamwork > Open Teamwork Client... from the main menu.

Click Open Teamwork Client... from the main menu

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.

Click Import Project


to Repository button

Checkout project P. 1068


In Import Project dialog box, check an option in Project file. Check Create new project if you want to checkout a new project while check Import
existing project if you want to checkout the existing project in your computer.

Import Project dialog box

NOTE: If you have an active project, the option of Currently opened project will be available.

Checkout project P. 1069


After the project has been checked out, click Open Project button.

The Teamwork Client dialog box

After that, the project has been downloaded from the server to your computer and you can start working on it.

Checkout project P. 1070


Commit
Commit refers to the process of uploading local modifications to the server. As team members make changes in a project, they can share their works
by committing those changes to the server. VP-UML can help to merge changes from working copy to server copy. During merging, a conflict may be
caused when there is a contradiction between team members. Decision have to be made whether to keep the current modified copy (i.e. overwrite) or
to accept others' copy (i.e. revert). All conflicts have to be solved before proceeding to commit.
To operate commit:
After entering VP-UML, select Tools > Teamwork > Commit... from the main menu to commit your modified copy to the server.

Launch commit from the main menu

Commit with Subversion P. 1071


The Commit dialog box displays the changes to be committed to the server. Click OK to proceed.

The Commit dialog box

Overview of Commit dialog box

Commit with Subversion P. 1072


The Commit dialog box

No. Name Description

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.

Commit with Subversion P. 1073


5 Property view window It lists property name, current value, original value and last modified of the selected model element.

6 Project name It shows the name of current project.

7 Checkout revision It shows the number of current checkout revision.

8 Checkout time It shows the time for latest checkout.

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

12 OK Click OK to proceed committing.

13 Cancel Click Cancel to cancel committing and close the dialog box.

14 Help Click Help to get assistance from help system.

The description of Commit dialog box

The Preview tab of the Commit dialog box

No. Name Description

15 Preview Click it for previewing the selected model element(s).

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.

The description of Preview tab in the Commit dialog box

Commit with Subversion P. 1074


Resolving conflict
When your modified copy conflicts with the copy others made previously during committing, you can resolve the conflict by clicking either Overwrite or
Revert in the Update dialog box.

Resolve conflict in the Commit dialog box

Choosing Overwrite means keeping your modified copy while choosing Revert refers to accept others' copy.

Commit with Subversion P. 1075


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).

Preview before committing

NOTE: Conflicts occur only when the same property of same shape you and other team members have made.

Commit with Subversion P. 1076


Update with Subversion
Update is the process of refreshing your current copy by merging changes that others have made and committed previously to server. Similar to
commit, update is a process of merging differences instead of overwriting. When your changes overlap the changes others have made, you will be
asked to resolve conflict. All conflicts have to be resolved before proceeding with updating.
To operate update:
After entering VP-UML, select Tools > Teamwork > Update from the main menu to update from the server.

Select Update from the main menu

Update with Subversion P. 1077


If other team members have made changes and have committed previously to the server, your current project will cause conflicts during updating. You
can resolve the conflict by clicking either Overwrite or Revert in the Update dialog box. Choosing Overwrite means keeping your current copy while
choosing Revert refers to accept others' copy.

Resolve the conflicts

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.

Update with Subversion P. 1078


Branching
In teamwork collaboration, the term trunk refers to your main stream of development. If you create a new project, you will spend the majority of your
time making changes and committing them to the trunk of your repository.
Branch is defined as a copy of work derived from a certain point in the trunk. It sets up an extra space for users to work on and make modifications
without disturbing the trunk. As soon as the modifications in branch are done, it can be merged back into the trunk.
To create a branch:
Select Tools > Teamwork > Branch... from the main menu.

Select Branch... from the main menu

Branching with Subversion P. 1079


When the Create Branch dialog box pops out, enter a name in Branch Name for your new branch and decide whether to work on the created branch
now or later by selecting the appropriate option from the drop-down menu. You can create branch from a specific revision of trunk by selecting Specific
revision in the repository and entering the revision number. On the other hand, select HEAD revision in the repository if you want to create a
branch from the latest revision in trunk. Finally, click OK button to confirm.

Create Branch dialog box

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.

Branching with Subversion P. 1080


Select Tools > Teamwork > Merge... from the main menu.

Select Merge... from the main menu

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.

Merge dialog box

Branching with Subversion P. 1081


Tagging
Tag refers to a named version of your work at a point of time in the trunk. The best application of a tag is to create it for every major release or
milestone. Note that you can neither merge a tag to the trunk nor commit it to the server.
To create a tag:
After entering VP-UML, select Tools > Teamwork > Tag... from the main menu.

Select Tag... from the main menu

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.

Create Tag dialog box

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.

Click Revert from the main menu

To undo all non-committed changes through teamwork client dialog box:


After entering VP-UML, select Tools > Teamwork > Open Teamwork Client... from the main menu in order to unfold teamwork client dialog box.

Revert Local Modification P. 1084


In Teamwork Client dialog box, either select Project > Revert... from the dialog box's main menu.

Click Revert... in teamwork client dialog box

Or click Revert... button from the dialog box's toolbar directly.

Click Revert... button

As a result, the non-committed changes are discarded.

Revert Local Modification P. 1085


Roll back past revisions changes
Subversion maintains the histories of changes on your project. With SVN, you can revert all modifications you did in a specific revision. Furthermore,
you can preview the differences between the server and local modified system visually.
After entering VP-UML, select Tools > Teamwork > Open Teamwork Client... from the main menu.

Click Open Teamwork Client... from the main menu

Roll back Past Revisions Changes P. 1086


In the Teamwork Client dialog box, all your project's revisions will be shown in Project revisions under Revisions tab. Select the amount of project's
revisions you want to be listed from the drop-down menu of Show. If more than one revision you want to undo, select the revisions with Ctrl key and
click Revert button under Project revisions.

Select a revision to revert

Roll back Past Revisions Changes P. 1087


When the Commit dialog box pops out, you have to resolve all conflicts before proceed reverting. Click either Overwrite button or Revert button.
Choosing Overwrite means keeping the latest copy while choosing Revert refers to accept the selected revision. You can preview the differences
between the server (the latest revision in server) and the local modified (the selected revision) under Preview tab. After fixing all conflicts, click OK to
proceed reverting.

Resolve conflicts in Commit dialog box

Roll back Past Revisions Changes P. 1088


Export revision with Subversion
VP teamwork collaboration maintains the histories of changes on your project. With SVN, you can export the selected revision or all revisions to your
computer for reviewing the project content in past revisions.

Export the selected revision


1. After entering VP-UML, select Tools > Teamwork > Open Teamwork Client... from the main menu.

Select Open Teamwork Client... from the main menu

Export revision P. 1089


2. In the Teamwork Client dialog box, unfold Revisions tab. Select the revisions(s) you want to export under Project revisions, click Export
button and choose Export selected revisions... from the pop-up menu.

Choosing Export selected revisions... in Teamwork Client dialog box

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

Export all revisions from repository


1. After entering VP-UML, select Tools > Teamwork > Open Teamwork Client... from the main menu.

Export revision P. 1090


2. In the Teamwork Client dialog box, unfold Revisions tab. Click Export button and choose Export all revisions from repository... from the
pop-up menu. Note that choosing Export all revisions from repository... means exporting all revisions of the selected project.

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.

Export revision P. 1091


Working with teamwork client dialog box with CVS
To perform teamwork operations such as to commit or update project, you can click the buttons in application menus or toolbars. Besides, you can
perform via the Teamwork Client dialog box. Teamwork Client dialog box enables you to perform teamwork operations, manage teamwork projects, as
well to review and checkout revisions of particular project.

Opening the teamwork client


1. Open the Teamwork Client by either of the ways below:
• Select Tools > Teamwork > Open Teamwork Client... from the main menu.

Open teamwork client through menu

• Click on the button Open Teamwork Client in toolbar.

Open teamwork client through toolbar

Working with teamwork client dialog box with CVS P. 1092


2. In the login dialog box, fill in the server and user information to login to server.

Login CVS

Below is a description of fields in the Login dialog box:


Field Description

Server The type of server, which should be CVS

Server host The server host, which can be host name or IP address

Port number The port of connecting to server

User name The user name for connecting to server

Password The password for given user

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.

Description of Login dialog box

Working with teamwork client dialog box with CVS P. 1093


3. If this is the first time you connect to the CVS server, you will be asked to select the projects to manage. By managing a project, you can check it
out, open and edit it. In the Manage Project dialog box, select the projects to manage.

Select projects to manage

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.

The Teamwork Client dialog box

Working with teamwork client dialog box with CVS P. 1094


The interface
General

The Teamwork Client dialog box

Region Description

To logout from CVS server.

To login to CVS server.

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 update changes from server.

To commit changes to server.

To checkout a project from server.

To open the project selected in Projects list. If the project is not checked out yet, it will be checked out automatically.

To remove changes made in a revision.

To check for changes

To create a tag for a trunk/branch.

To create a branch for a trunk/branch.

To merge changes from trunk/branch.

To switch to another trunk/branch/tag.

Working with teamwork client dialog box with CVS P. 1095


To remove a branch. Note that removed branch will not delete the, but just make it not accessible.

Show all user To show the projects manageable by all users.

Repository To update the Projects list by showing only projects in certain repository.

Projects The list of manageable project.

Project Details Details of selected project, including the name, revision and status.

Revisions Revisions of selected project.

Description of the Teamwork Client dialog box

Project details

The Project Details tab in Teamwork Client dialog box

Field Description

Project Name of the selected project.


name

File path The file path of the project in your system.

Checkout The time when you checkout the project.


time

Revision The revision of your local copy.

Status The status of local project.

Comment The comment of project entered by the administrator when creating project.

Description of Project Details tab in Teamwork Client dialog box

Revisions

Working with teamwork client dialog box with CVS P. 1096


The Revisions tab in Teamwork Client dialog box

Region Description

Show: To list certain amount of revisions, such as all, last 10, last 20, etc.

Revision list To display the revisions of chosen project.

[Revert] By reverting a selected revision, this means to undone changes made in that revision.

[Export] To export selected revision(s) as project files.

[Open] To open selected revision.

[Compare] To compare the differences between revisions.

Description of Revisions tab in Teamwork Client dialog box

Working with teamwork client dialog box with CVS P. 1097


Importing projects to CVS server
1. Start VP-UML.
2. Select Tools > Teamwork > Open Teamwork Client... from the main menu, or Open Teamwork Client icon from toolbar to open teamwork
client.

Open Teamwork Client from main menu

Importing projects to CVS server P. 1098


3. Select CVS Server, fill in the server and user information to login cvs server.

Login cvs server

Below is a description of fields in the Login dialog box:


Field Description

Server The type of server, which should be CVS

User name The user name for connecting to server

Password The password for given user

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

Host The host name of server

Repository path The path of CVS repository

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

Description of Login dialog box

4. Select Project > Import Project to Repository from the menu.

Import project from menu

Or click the Import Project to Repository button on toolbar.

Import project from toolbar

Importing projects to CVS server P. 1099


5. In the Import Project dialog, fill in the Project name.

Fill project name in Import Project dialog

Field Description

Project name The name of teamwork project

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

Repository A tree which shows the structure of repository

URL The URL of the project in repository

Comment The comment of project

Description of Import Project dialog box

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.

Specify project file

NOTE: Please make sure the user login to Teamwork Client has Create Project permission

7. Select the repository for import the project.

Select repository

Importing projects to CVS server P. 1100


8. Fill in the comment.

Input comment

9. Click OK button to import project.

Importing projects to CVS server P. 1101


Checkout project from CVS server
Checkout and open CVS server projects
1. Open Teamwork Client dialog.
2. Select Project > Manage Project from the menu.

Manage project from main menu

Or click Manage Project icon on the toolbar.

Manage project from toolbar

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

4. Select the project in project list.

Select project from the list

5. Click Open Project button to checkout and open the project.

Open project

Checkout project from CVS server P. 1102


6. The project opened in VP-UML.

Project opened

Checkout project from CVS server P. 1103


Committing local modification to CVS server
1. Modify the project.

Modified project

2. Show Teamwork Toolbar by right click on the Toolbar, select Teamwork if not selected already.

Show teamwork toolbar

3. Click the Commit button on Teamwork Toolbar.

Commit project

Committing local modification to CVS server P. 1104


4. In Commit dialog, you can review the changes for commit. On the left of dialog, you can see a list of changes shapes and model elements, click
on it to view the detail changes on the right.

Review commit changes

5. On the bottom of dialog, click the Preview tab to visually preview the changes in diagram. The selected shape is highlighed in purple.

Preview commit changes

6. After review the changes, click the Comment tab and input the comment for commit. Click OK button to start commit.

Input commit comment

Committing local modification to CVS server P. 1105


Resolving conflicts with CVS Server
1. Modify the project.

Modified project

2. Click Commit button on the Teamwork Toolbar.

Resolving conflicts P. 1106


3. In Commit dialog, you may found some shapes or model elements show with red icon. This indicate there is conflict when commit, it is caused
by someone modified the same content and commit after you checkout. You can review the current value, original value (the value when you
checkout), and conflict value (the value changed by other users). And dialog preview is disabled until you resolve the conflict.

Commit with conflicts

Below is a description of buttons or fields in dialog box.


Button/Field Description

Move to the previous conflict in element tree.

Move to the next conflict in element tree.

Overwrite all conflicts.

Revert all conflicts.

Reset all conflicts.

Overwrite the selected conflict in tree.

Revert the selected conflict in tree.

Reset the selected conflict in tree.

Select the previous change in tree.

Select the next change in tree.

Current Name The value of name of the committing/updating copy.

Original Name The value of name of the original copy.

Conflict Name The value of name of the server copy.

Last Modified The user who modified last time.

Conflict Revision The revision that cause conflict with the committing/updating action.

[Overwrite] Click on overwrite the conflict selected in tree.

[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.

Overwrite selected conflicts

Or click Revert selected conflicts to revert your own changes.

Revert selected conflicts

You can also click Overwrite all conflicts or Revert all conflicts to overwrite or revert all conflicts at once.

Overwrite/Revert all conflicts

5. After resolve conflict, the preview will be enabled to visualize the final result.

Preview resolved conflict

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.

Resolving conflicts P. 1108


Updating latest revision from CVS server
Updating modification from CVS server
1. Click Update button on Teamwork Toolbar.

Update from toolbar

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.

Updating latest revision from CVS server P. 1109


4. Click OK button to update. VP-UML will open the updated project.

Updated project

Checking status
1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Select Project > Check Update from menu.

Update project from menu

Or click Check Update button from toolbar.

Update project from toolbar

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

Updating latest revision from CVS server P. 1110


Rolling Back Undesired Changes by Reverting Changes
Roll back local and uncommitted modifications
1. Modify the project.

Modify project

2. Open Teamwork Client dialog.


3. Select the teamwork project in the list.
4. Select Project > Revert... from menu

Revert from menu

Or click Revert... button from toolbar.

Revert from toolbar

Rolling back undesired changes by reverting changes P. 1111


5. Click Yes button from the confirmation dialog.
6. The reverted project opened in VP-UML.

Reverted project

Roll back modifications of a past revision


If there were undesired changes made in past revision(s), such as wrong deletion of elements, you can undo the changes by reverting the revision(s)
involved. Here are the steps:
1. Open project.

Open project

2. Open Teamwork Client dialog.


3. Select the teamwork project in the list.

Rolling back undesired changes by reverting changes P. 1112


4. Click the Revisions tab on the right of the project list.

Revision tab

5. Select the revision(s) to have its changes rolled back.

Select revision

6. Click Revert button.

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.

Rolling back undesired changes by reverting changes P. 1113


7. The Commit dialog show a list of shapes and model elements reverted for review the changes and preview diagram, input the comment and
click OK button to commit the revert.

Commit dialog with reverted changes

8. A new revision with the reverted changes was created in server, and opened in VP-UML.

Reverted project

Rolling back undesired changes by reverting changes P. 1114


Browsing change histories (old revisions) with CVS
Checkout old revisions
1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Click the Revisions tab.
4. Select the revision to open.
5. Click Open button.

Open button

6. Selected revision opened in VP-UML.

Open selected revision

Showing differences between revisions visually


1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Click the Revisions tab.
4. Select a revision for compare.
5. Select another revision by Ctrl+Click.

Select two revisions

6. Click the Compare... button.

Compare button

Browsing change histories (old revisions) with CVS P. 1115


7. Similar to Commit and Update dialog, the Compare Projects dialog show a list of differences between the selected revisions. You can also
view the differences visually in diagram on the preview tab.

Compare differences

Export multiple revisions to local


1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Click the Revisions tab.
4. Select multiple revisions for export, by Ctrl+Click or Shift+Click.

Select multiple revisions

5. Click the Export button.

Export buttons

6. Select Export selected revisions... from the popup.

Export selected revisions

Browsing change histories (old revisions) with CVS P. 1116


7. Select the directory to save the exported project revisions.

Select directory

8. You'll found the selected revisions was exported to the select directory.

Exported revisions

Browsing change histories (old revisions) with CVS P. 1117


Isolating last long modifications with branches with CVS
Creating branch
1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Select Project > Branch... from menu

Branch from menu

Or click Branch... button from toolbar.

Branch from toolbar

4. Fill in the Branch Name in Create Branch dialog.

Create Branch dialog

5. Select Stay in head in the list.

Stay in head

Switch local copy between branches

Isolating last long modifications with Branches with CVS P. 1118


1. Select Project > Switch... from menu

Switch from menu

Or click Switch... button from toolbar.

Switch from toolbar

2. Select the branch to switch.

Select branch

3. The branch is opened in VP-UML.

Merging from HEAD to branch

Isolating last long modifications with Branches with CVS P. 1119


1. Open, modify and commit HEAD project.

Modified HEAD project

2. Open branch project.

Branch project

Isolating last long modifications with Branches with CVS P. 1120


3. Select Project > Merge... from menu.

Merge from menu

Or click Merge... button from toolbar.

Merge from toolbar

4. Select from HEAD in the Merge dialog.

Merge dialog

Isolating last long modifications with Branches with CVS P. 1121


5. The Merge Project dialog show a list of changes similar to Commit and Update dialog.

Merge project 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.

Branch project merged from HEAD

Isolating last long modifications with Branches with CVS P. 1122


Merging from branch to HEAD
1. Open, modify and commit branch project.

Modified branch project

2. Open HEAD project.

HEAD project

3. Select Project > Merge... from menu, or click Merge... button from toolbar.

Isolating last long modifications with Branches with CVS P. 1123


4. Select a branch name in From combo box.

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.

HEAD project merged from branch

Delete branch

Isolating last long modifications with Branches with CVS P. 1124


1. Select Project > Delete Branch... from menu

Delete Branch from menu

Or click Delete Branch ... button from toolbar.

Delete Branch from toolbar

2. Expand the repository and folder node, select the branch to delete. Click OK button to continue.

Delete branch dialog

3. Click Yes button on confirmation dialog.

Isolating last long modifications with Branches with CVS P. 1125


Marking release or milestone with tags with CVS
Tags and branches are almost the same, with the only difference - tags are read only. Creating read only tags ensure you are able open the release
version project later.
1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Select Project > Tag... from menu

Tag from menu

Or click Branch... button from toolbar.

Tag from toolbar

4. Fill in the Tag Name in Create Tag dialog.

Create Tag dialog

5. Click OK button, the tag will be created.

Marking release or milestone with tags with CVS P. 1126


Working with teamwork client dialog box with Perforce
To perform teamwork operations such as to commit or update project, you can click the buttons in application menus or toolbars. Besides, you can
perform via the Teamwork Client dialog box. Teamwork Client dialog box enables you to perform teamwork operations, manage teamwork projects, as
well to review and checkout revisions of particular project.

Opening the teamwork client


1. Open the Teamwork Client by either of the ways below:
• Select Tools > Teamwork > Open Teamwork Client... from the main menu.

Open teamwork client through menu

• Click on the button Open Teamwork Client in toolbar.

Open teamwork client through toolbar

Working with teamwork client dialog box with Perforce P. 1127


2. In the login dialog box, fill in the server and user information to login to server.

Login Perforce

Below is a description of fields in the Login dialog box:


Field Description

Server The type of server, which should be Perforce

Server host The server host, which can be host name or IP address

Port number The port of connecting to server

User name The user name for connecting to server

Password The password for given user

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.

Description of Login dialog box

Working with teamwork client dialog box with Perforce P. 1128


3. If this is the first time you connect to the Perforce server, you will be asked to select the projects to manage. By managing a project, you can
check it out, open and edit it. In the Manage Project dialog box, select the projects to manage.

Select projects to manage

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.

The Teamwork Client dialog box

Working with teamwork client dialog box with Perforce P. 1129


The interface
General

The Teamwork Client dialog box

Region Description

To logout from Perforce server.

To login to Perforce server.

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 update changes from server.

To commit changes to server.

To checkout a project from server.

To open the project selected in Projects list. If the project is not checked out yet, it will be checked out automatically.

To remove changes made in a revision.

To check for changes

To create a tag for a trunk/branch.

To create a branch for a trunk/branch.

To merge changes from trunk/branch.

To switch to another trunk/branch/tag.

Working with teamwork client dialog box with Perforce P. 1130


To remove a branch. Note that removed branch will not delete the, but just make it not accessible.

Show all user To show the projects manageable by all users.

Repository To update the Projects list by showing only projects in certain repository.

Projects The list of manageable project.

Project Details Details of selected project, including the name, revision and status.

Revisions Revisions of selected project.

Description of the Teamwork Client dialog box

Project details

The Project Details tab in Teamwork Client dialog box

Field Description

Project Name of the selected project.


name

File path The file path of the project in your system.

Checkout The time when you checkout the project.


time

Revision The revision of your local copy.

Status The status of local project.

Comment The comment of project entered by the administrator when creating project.

Description of Project Details tab in Teamwork Client dialog box

Revisions

Working with teamwork client dialog box with Perforce P. 1131


The Revisions tab in Teamwork Client dialog box

Region Description

Show: To list certain amount of revisions, such as all, last 10, last 20, etc.

Revision list To display the revisions of chosen project.

[Revert] By reverting a selected revision, this means to undone changes made in that revision.

[Export] To export selected revision(s) as project files.

[Open] To open selected revision.

[Compare] To compare the differences between revisions.

Description of Revisions tab in Teamwork Client dialog box

Working with teamwork client dialog box with Perforce P. 1132


Importing projects to perforce
1. Start VP-UML.
2. Select Tools > Teamwork > Open Teamwork Client... from the main menu, or Open Teamwork Client icon from toolbar to open teamwork
client.

Open Teamwork Client from main menu

3. Select Perforce in Server field.

Perforce teamwork server

Importing projects to Perforce P. 1133


4. Fill in the server and user information to login teamwork server.

Login teamwork server

Below is a description of fields in the Login dialog box:


Field Description

Server The type of server, which should be Perforce

User name The user name for connecting to server

Password The password for given user

Perforce path The filepath of p4.exe. You are required to supply a valid path in order to connect to Perforce server

Host The host of Perforce server

Port The port number of connecting to server

Remember Check to memorize the password so that you don't need to enter again
password

Description of Login dialog box

5. Select Project > Import Project to Repository from the menu.

Import project from menu

Or click the Import Project to Repository button on toolbar.

Import project from toolbar

Importing projects to Perforce P. 1134


6. In the Import Project dialog, fill in the Project name.

Fill project name in Import Project dialog

Field Description

Project name The name of teamwork project

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

Repository A tree which shows the structure of repository

URL The URL of the project in repository

Comment The comment of project

Description of Import Project dialog box

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.

Specify project file

8. Select the depot node for import the project.

Select repository

9. Fill in the comment.

Input comment

10. Click OK button to import project.

Importing projects to Perforce P. 1135


Checkout project from perforce
Checkout and open perforce projects
1. Open Teamwork Client dialog.
2. Select Project > Manage Project from the menu.

Manage project from main menu

Or click Manage Project icon on the toolbar.

Manage project from toolbar

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

4. Select the project in project list.

Select project from the list

5. Click Open Project button to checkout and open the project.

Open project

Checkout project from Perforce P. 1136


6. The project opened in VP-UML.

Project opened

Checkout project from Perforce P. 1137


Committing local modification to perforce
1. Modify the project.

Modified project

2. Show Teamwork Toolbar by right click on the Toolbar, select Teamwork if not selected already.

Show teamwork toolbar

3. Click the Commit button on Teamwork Toolbar.

Commit project

Committing local modification to Perforce P. 1138


4. In Commit dialog, you can review the changes for commit. On the left of dialog, you can see a list of changes shapes and model elements, click
on it to view the detail changes on the right.

Review commit changes

5. On the bottom of dialog, click the Preview tab to visually preview the changes in diagram. The selected shape is highlighed in purple.

Preview commit changes

6. After review the changes, click the Comment tab and input the comment for commit. Click OK button to start commit.

Input commit comment

Committing local modification to Perforce P. 1139


Resolving conflicts with Perforce
1. Modify the project.

Modified project

2. Click Commit button on the Teamwork Toolbar.

Resolving conflicts P. 1140


3. In Commit dialog, you may found some shapes or model elements show with red icon. This indicate there is conflict when commit, it is caused
by someone modified the same content and commit after you checkout. You can review the current value, original value (the value when you
checkout), and conflict value (the value changed by other users). And dialog preview is disabled until you resolve the conflict.

Commit with conflicts

Below is a description of buttons or fields in dialog box.


Button/Field Description

Move to the previous conflict in element tree.

Move to the next conflict in element tree.

Overwrite all conflicts.

Revert all conflicts.

Reset all conflicts.

Overwrite the selected conflict in tree.

Revert the selected conflict in tree.

Reset the selected conflict in tree.

Select the previous change in tree.

Select the next change in tree.

Current Name The value of name of the committing/updating copy.

Original Name The value of name of the original copy.

Conflict Name The value of name of the server copy.

Last Modified The user who modified last time.

Conflict Revision The revision that cause conflict with the committing/updating action.

[Overwrite] Click on overwrite the conflict selected in tree.

[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.

Overwrite selected conflicts

Or click Revert selected conflicts to revert your own changes.

Revert selected conflicts

You can also click Overwrite all conflicts or Revert all conflicts to overwrite or revert all conflicts at once.

Overwrite/Revert all conflicts

5. After resolve conflict, the preview will be enabled to visualize the final result.

Preview resolved conflict

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.

Resolving conflicts P. 1142


Updating latest revision from perforce
Updating modification from perforce
1. Click Update button on Teamwork Toolbar.

Update from toolbar

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.

Updating latest revision from Perforce P. 1143


4. Click OK button to update. VP-UML will open the updated project.

Updated project

Checking status
1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Select Project > Check Update from menu.

Update project from menu

Or click Check Update button from toolbar.

Update project from toolbar

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

Updating latest revision from Perforce P. 1144


Rolling Back Undesired Changes by Reverting Changes
Roll back local and uncommitted modifications
1. Modify the project.

Modify project

2. Open Teamwork Client dialog.


3. Select the teamwork project in the list.
4. Select Project > Revert... from menu

Revert from menu

Or click Revert... button from toolbar.

Revert from toolbar

Rolling back undesired changes by reverting changes P. 1145


5. Click Yes button from the confirmation dialog.
6. The reverted project opened in VP-UML.

Reverted project

Roll back modifications of a past revision


If there were undesired changes made in past revision(s), such as wrong deletion of elements, you can undo the changes by reverting the revision(s)
involved. Here are the steps:
1. Open project.

Open project

2. Open Teamwork Client dialog.


3. Select the teamwork project in the list.

Rolling back undesired changes by reverting changes P. 1146


4. Click the Revisions tab on the right of the project list.

Revision tab

5. Select the revision(s) to have its changes rolled back.

Select revision

6. Click Revert button.

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.

Rolling back undesired changes by reverting changes P. 1147


7. The Commit dialog show a list of shapes and model elements reverted for review the changes and preview diagram, input the comment and
click OK button to commit the revert.

Commit dialog with reverted changes

8. A new revision with the reverted changes was created in server, and opened in VP-UML.

Reverted project

Rolling back undesired changes by reverting changes P. 1148


Browsing change histories (old revisions) with Perforce
Checkout old revisions
1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Click the Revisions tab.
4. Select the revision to open.
5. Click Open button.

Open button

6. Selected revision opened in VP-UML.

Open selected revision

Showing differences between revisions visually


1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Click the Revisions tab.
4. Select a revision for compare.
5. Select another revision by Ctrl+Click.

Figure 4-55 Select two revisions

6. Click the Compare... button.

Compare button

Browsing change histories (old revisions) with Perforce P. 1149


7. Similar to Commit and Update dialog, the Compare Projects dialog show a list of differences between the selected revisions. You can also
view the differences visually in diagram on the preview tab.

Compare differences

Export multiple revisions to local


1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Click the Revisions tab.
4. Select multiple revisions for export, by Ctrl+Click or Shift+Click.

Select multiple revisions

5. Click the Export button.

Export buttons

6. Select Export selected revisions... from the popup.

Export selected revisions

Browsing change histories (old revisions) with Perforce P. 1150


7. Select the directory to save the exported project revisions.

Select directory

8. You'll found the selected revisions was exported to the select directory.

Exported revisions

Browsing change histories (old revisions) with Perforce P. 1151


Isolating last long modifications with branches
Creating branch
1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Select Project > Branch... from menu

Branch from menu

Or click Branch... button from toolbar.

Branch from toolbar

4. Fill in the Branch Name in Create Branch dialog.

Create Branch dialog

Isolating last long modifications with branches P. 1152


5. Select Stay in trunk in the list.

Stay in trunk

Switch local copy between branches


1. Select Project > Switch... from menu

Switch from menu

Or click Switch... button from toolbar.

Switch from toolbar

2. Click ... to browser the path.

Select branch

Isolating last long modifications with branches P. 1153


3. Select the branch to switch, and click OK.

Select branch path

4. The branch is opened in VP-UML.

Merging from trunk to branch


1. Open, modify and commit trunk project.

Modified trunk project

Isolating last long modifications with branches P. 1154


2. Open branch project.

Branch project

3. Select Project > Merge... from menu.

Merge from menu

Or click Merge... button from toolbar.

Merge from toolbar

Isolating last long modifications with branches P. 1155


4. Select the trunk path( depot/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.

Merge project dialog

6. Finally, review the changes in Commit dialog. Input comment and click OK to commit.

Isolating last long modifications with branches P. 1156


7. The branch project now contains the changes from trunk.

Branch project merged from trunk

Merging from branch to trunk


1. Open, modify and commit branch project.

Modified branch project

Isolating last long modifications with branches P. 1157


2. Open trunk project.

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.

Isolating last long modifications with branches P. 1158


7. The trunk project now contains the changes from branch.

Trunk project merged from branch

Delete branch
1. Select Project > Delete Branch... from menu

Delete Branch from menu

Or click Delete Branch ... button from toolbar.

Delete Branch from toolbar

Isolating last long modifications with branches P. 1159


2. Expand the repository and folder node, select the branch to delete. Click OK button to continue.

Delete branch dialog

3. Click Yes button on confirmation dialog.

Isolating last long modifications with branches P. 1160


Marking release or milestone with tags
Tags and branches are almost the same, with the only difference - tags are read only. Creating read only tags ensure you are able open the release
version project later.
1. Open Teamwork Client dialog.
2. Select the teamwork project in the list.
3. Select Project > Tag... from menu.

Tag from menu

Or click Branch... button from toolbar.

Tag from toolbar

Marking release or milestone with tags P. 1161


4. Fill in the Tag Name in Create Tag dialog.

Create Tag dialog

5. Click OK button, the tag will be created.

Marking release or milestone with tags P. 1162


Diagram protection
When you are working on a project with your team members, you probably don't want your work be modified by others by mistake. To protect your
work, you can lock your current diagram with password, so as to make it uneditable by others.

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

Your diagram is then locked.

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.

Diagram protection P. 1163


Trying to edit a locked diagram
If your team members want to modify any model elements of the locked diagram, they need to provide the password set by you in the pop-up
Authorization Required dialog box in order to proceed modification.

Require to enter password to proceed editing

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.

Unlock the diagram

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.

Diagram protection P. 1164


1. Right click on the diagram's background and select Diagram Content > Configure Lock... from the pop-up menu.

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

Diagram protection P. 1165


General options

The overview of General Options

Project

Project Options in General

General Options P. 1166


Option Name Description

Auto save project Save the opening project as backup periodically.

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.

Project Options details

Linked Project

Linked Project Options in General

Option Name Description

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

General Options P. 1167


Appearence Options in General

Option Name Description

Look and feel It controls the appearance of application screen.

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 Format Format of date values that appears in the application.

Date Sample The sample of date is shown after you select the format of date.

Time Format Format of time values that appears in the application.

Time Sample The sample of time is shown after you select the format of time.

Measurement Unit • inch - (default) Set the measurement unit to be inch


• cm - Set the measurement unit to be centimeters

Appearence Options details

Connection

Connection Options in General

Option Description

Name

E-mail Enter the Email field to specify your email address.

General Options P. 1168


Use (default false) To check/uncheck in order to use a proxy server for connecting to the
proxy Internet.

Host The host of the proxy server.

Port The port of the proxy server.

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).

Connection Options details

Printing

Printing Options in General

Option Name Description

Use gradient color when print diagrams Control whether to use gradient or solid color for shapes and diagrams when printing.

Printing Options details

Edition

Edition Options in General

Option Name Description

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.

Printing Options details

Teamwork

Teamwork Options in General

Option Name Description

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

Teamwork Options details

Update

Update Options in General

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.

General Options P. 1169


• Never - Do not inform product update
• On every start - Check for updates everytime when starting VP-UML
• Daily - Check for updates daily
• Weekly - (default) Check for updates weekly
• Monthly - Check for updates monthly

Update Options details

General Options P. 1170


Diagramming options

The overview of Diagramming Options

Appearance

Diagramming options P. 1171


Appearance Options in Diagramming

Diagramming options P. 1172


Option Name Description

Show grid (default false) Show grid lines on diagram

Color Color of grid lines.

Width Determines the horizontal spaces between grid lines.

Height Determines the vertical spaces between grid lines.

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.

Graphics anti-aliasing (default true) Smoothen the graphics.

Text anti-aliasing (default true) Smoothen the text.

Documentation Type Default type of documentation


• HTML - (default) HTML text that consists of formatting such as bold, italic, underline, table
• Plain text - Text without formatting

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

Diagram background Background color of diagrams.

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.

Appearance Options details

Environment

Diagramming options P. 1173


Environment Options in Diagramming

Diagramming options P. 1174


Option Name Description

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.

Environment Options details

Model generation

Diagramming options P. 1175


Model Generation Options in Diagramming

Option Name Description

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

Model Generation Options details

Shape

Diagramming options P. 1176


Shape Options in Diagramming

Diagramming options P. 1177


Option Name Description

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)

Shape line format The default line format for shapes.

Shape fill format The default fill format for shapes.

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.

Shape Options details

Connector

Diagramming options P. 1178


Connector Options in Diagramming

Diagramming options P. 1179


Option Name Description

Font Default font settings for connector caption.

Connector Style • Rectilinear - Set the default connector style to be rectilinear


• Round Rectilinear - Set the default connector style to be round rectilinear
• Oblique - (default) Set the default connector style to be oblique
• Round Oblique - Set the default connector style to be round oblique
• Curve - Set the default connector style to be curve

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

Line Jumps • Off - (default) Disable line jump


• Arc - Show connectors' intersections as an arcs
• Gap - Show connectors' intersections as a gaps
• Square - Show connectors' intersections as a squares

Line jump size • Normal


• Large
• Extra large

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

Foreground Foreground color of connector.

Background Background color of connector.

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).

Connector Options details

Resource centric

Diagramming options P. 1180


Resource Centric Options in Diagramming

Option Name Description

Show resources (default true) Show resource icons around shapes.

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.

Resource Centric Options details

Class

Diagramming options P. 1181


Class Options in Diagramming

Diagramming options P. 1182


Option Name Description

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 attribute (default true) Allow to enter attribute name in


multiple lines by pressing the new line key defined
in Diagramming > Shape.

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)

Synchronize documentation of Interface to sub-class • Always synchronize


• Do not synchronize
• Prompt

Show parent style • UML - (default) Show tooltip of child class in


UML style like Package::Class
• Java/C# - Show tooltip of child class in Java/
C# style like Package.Class

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.

Default parameter direction • in - When creating a parameter in operation,


the direction will be in
• out - When creating a parameter in
operation, the direction will be out
• inout - (default) When creating a parameter
in operation, the direction will be inout
• return - When creating a parameter in
operation, the direction will be return

Default Visibility - Class • Unspecified - A new class will take


Unspecified as visibility
• private - A new class will take private as
visibility
• protected - A new class will take protected
as visibility
• package - A new class will take package as
visibility
• public - (default) A new class will take public
as visibility
• protected internal (.NET only) - A new class
will take protected internal as visibility when
programming language is set to be .NET
• internal (.NET only) - A new class will take
internal as visibility when programming
language is set to be .NET

Default Visibility - Attribute • Unspecified - A new attribute will take


Unspecified as visibility
• private - (default) A new attribute will take
private as visibility
• protected - A new attribute will take
protected asDiagramming
visibility options P. 1183
Presentation of Class Options in Diagramming

Diagramming options P. 1184


Option Name Description

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 operation signature (default true) Show operation signature.

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.

Show template parameter (default true) Show template parameter of class.

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.

Presentation of Class Options details

Diagramming options P. 1185


Auto Attribute Type of Class Options in Diagramming

Option Name Description

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.

Auto Attribute Type of Class Options details

Association

Diagramming options P. 1186


Association Options in Diagramming

Diagramming options P. 1187


Option Name Description

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.

Association Options details

Generalization

Generalization Options in Diagramming

Diagramming options P. 1188


Option Name Description

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

Generalization Options details

ERD & ORM

ERD & ORM Options in Diagramming

Diagramming options P. 1189


Option Name Description

Show column type (default true) Show data type of


column.

Foreign key connector end points to associated column (default false) Attach foreign key
connector end points to the column
associated.

Align column properties (default true) Align the column


properties so that columns in entity
will appear tidier.

Show extra column properties (default true) Show extra column


properties such as Nullable.

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.

Show table record editor

Column Constraints Presentation • Symbol


• Text
• Icon

Foreign key arrow head size • Very Small


• Small
• Medium (default)
• Large
• Extra Large
• Jumbo
• Colossal

Primary Key Pattern Pattern of primary keys that will


be applied when synchronizing
Class Diagram to Entity Relationship
Diagram, which may create primary
key.

Foreign Key Pattern

ERD & ORM Options details

Diagramming options P. 1190


Auto Column Type of ERD & ORM Options in Diagramming

Option Name Description

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.

Auto Column Type of ERD & ORM Options details

Interaction

Diagramming options P. 1191


Interaction Options in Diagramming

Diagramming options P. 1192


Option Name Description

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.

Show message completion documentation (default true) When selecting an


Operation in the message completion
box, the documentation of operation will
appear next to the completion box.

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 sequence number in Communication Diagram (default true) Show numbering on


Sequence Message in Communication
Diagram.

Show sequence number in Sequence Diagram (default true) Show numbering on


Sequence Message in Sequence
Diagram.

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.

Show activations in Sequence Diagram (diagram-based) (default true) Show Activations in


Sequence Diagram. If unchecked,
sequence message will be attached to
Lifeline instead of Activations.

Display as Robustness Analysis icon in Sequence Diagram (default true) Display Lifeline as
robustness analysis icon for Lifelines
stereotyped as boundary/control/entity.

Show associated diagram name of Interaction (default false)

Interaction Options details

Use Case Diagram

Diagramming options P. 1193


Use Case Diagram Options in Diagramming

Option Name Description

Show Use Case Extension Points (default true) Show Use Case Extension Points within Use Case shapes.

Show Use Case ID (default false) Show the ID of use cases.

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.

Use Case Diagram Options details

Use Case Details

Use Case Details Options in Diagramming

Diagramming options P. 1194


Option Name Description

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

Use Case Details Options details

Activity and state

Activity and State Options in Diagramming

Diagramming options P. 1195


Option Name Description

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.

Default location (in pixel) Position of Initial State create by default.

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

Activity and State Options details

Component diagram

Component Diagram Options in Diagramming

Option Name Description

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

Component Diagram Options details

Diagramming options P. 1196


Deployment diagram

Component Diagram Options in Diagramming

Option Name Description

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

Component Diagram Options details

Business process

Business Process Options in Diagramming

Diagramming options P. 1197


Option Name Description

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

Connector Style • Rectilinear - Set the connector style to Rectilinear


• Round Rectilinear - (default) Set the connector style to Round Rectilinear
• Oblique - Set the connector style to Oblique
• Round Oblique - Set the connector style to Round Oblique
• Curve - Set the connector style to Curve

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.

Default Type of Sub-Process The default type of newly created sub-process.


• Unspecified (default)
• Embedded
• Reusable
• Reference
• Event

Business Process Options details

Requirement diagram

Diagramming options P. 1198


Requirement Diagram Options in Diagramming

Option Name Description

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

Wrap member (default false) Wrap the Requirement members' content.

Support HTML Attribute (default false) Allow to fill in attributes with rich text format.

Requirement Diagram Options details

DFD

DFD Options in Diagramming

Option Name Description

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

DFD Options details

Communication Diagram

Communication Diagram Options in Diagramming

Option Name Description

Diagramming options P. 1199


Use one message for one On a link between lifeline, you can choose whether to group message arrows that follow the same direction into
direction a single arrow, or show as separate message arrows.

Communication Diagram Options details

Textual Analysis

Textual Analysis Options in Diagramming

Option Name Description

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.

Textual Analysis options details

Diagramming options P. 1200


View options

View Options in Option List

Options

View Options

View options P. 1201


Option Name Description

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 relationships (default false) Show relationships in trees.

Show sub diagrams (default true) Show subdiagrams 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.

View Options details

View options P. 1202


Instant reverse optons

Instant Reverse Options in Option List

Options

Instant reverse options P. 1203


Instant Reverse Options

Option Name Description

.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.

Calculate Generalization and Realization (default false)

Reverse Operation's Implementation (default false)

Instant Reverse Options details

Instant reverse options P. 1204


ORM options

ORM Options in Option List

General

ORM options P. 1205


General Options in ORM

ORM options P. 1206


Option Name Description

Quote SQL Identifier • Yes - Add quotes to SQL identifier


to prevent potential violation when
executing SQL
• No - Do not add quotes to SQL
identifier
• Auto - (default) Quote only reserved
words

Synchronize Name • Yes - Auto update model element


name when synchronize class
diagram and ERD
• No - Do not update model element
name when synchronize class
diagram and ERD
• Prompt - (default) Prompt to
update model element name when
synchronize class diagram and ERD

Mapping File Column Order • ERD - (default) Generate columns in


mapping file in same order as ERD
• Index - Generate index columns first
in mapping file

Wrapping Servlet Request • On - Automatic lock


persistable object when get by
HttpSession.getAttribute()
• Off - (default) Do not lock object
automatically

Getter/Setter Visibility • Public - (default) Generate public


getter/setter
• Follow attribute -Getter/setter visibility
follow attribute's visibility

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.

ID Generator • assigned - lets the application to


assign an identifier to the object
before is called.
• guid - uses a database-generated
GUID string on MS SQL Server and
MySQL.
• 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
ORMa named
optionsdatabase
P. 1207
sequence.
Synchronization

Synchronization Options in ORM

ORM options P. 1208


Option Name Description

Entity => Class Name - Prefix Append characters/words in front of name

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

Entity => Class Name - Suffix Append characters/words after name.

Column => Attribute Name - Prefix Append characters/words in front of name.

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

Column => Attribute Name - Suffix Append characters/words after name.

Class => Entity Name - Prefix Append characters/words in front of name.

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

Class => Entity Name - Suffix Append characters/words after name.

Attribute => Column Name - Prefix Append characters/words in front of name.

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

State Code Engine Options in Option List

Options

State Code Engine Options

State code engine options P. 1210


Option Name Description

Language you can select the following language:


• Java - (default) Generate code in Java
• C# - Generate code in C#
• VB .NET - Generate code in VB.NET
• C++ - Generate code in C++

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.

State Code Engine Options details

State code engine options P. 1211


Office exchange options

Office Exchange Options in Option List

Options

Office Exchange Options

Office exchange options P. 1212


Option Name Description

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.

Launch viewer (default true) Open the document after export.

Generate table of contents (default true) Generate Table of Contents in document.

Generate blank model (default false) Export an empty form for user to create new model.
element

Office Exchange Options details

Office exchange options P. 1213


User path options
A user path is a variable that refers to a base path in user&rsquo;s computer. You can add a reference to local file using user path so that the reference
refers to a file relative to a user path, instead of an absolute path. This means you can move references files to a different location, or even to a
different computer, and can still open them as long as the user path value is up-to-date.

User Path Options in Option List

Options

User path options P. 1214


User Path Options

Option Name Description

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.

User Path Options details

User path options P. 1215


Data type options
UML is theoretically a modeling language independent to particular programming language(s). Yet, it is possible to transform between UML models to
a software applications or systems. While the pre-defined data-type set works well in the UML world, there is enormous need to ensure the design can
be applied to programming source code. Problems comes from the fact that programming languages, by nature, are unlikely to share the same set of
data-types suggested by UML. A typical example is about the use of boolean. &lsquo;boolean&rsquo;, &lsquo;bool&rsquo; and &lsquo;Boolean&rsquo;
are adopted by UML and Java, C# and VB.NET respectively. But they are all referring to the same thing &ndash; boolean.
Visual Paradigm lets you choose a programming language that your UML project should be based on. When modeling, you can easily select a data-
type that is allowed for the chosen language, without typing it. Besides, new languages and data types can be added, which increase the flexibility of
working under different domains.

Data Type Options in Option List

Configure programming language


1. In Diagram Navigator / Model Pane / Class Repository, right click on the project root node and select Configure Programming Language...
from the pop-up menu.
2. In the Programming Language dialog box, select the language to switch to. The way how data-type will be mapped from the current language
to the chosen language is listed in the table following the data-type definition of that language.

Customizing programming language and data types


By default, there are six types of predefined (programming) languages. Each of them consists of a set of supported data types. Besides working with
those default languages and types, you can add your own languages and add data types. To do so:
1. Press on the plus sign to add a language.
2. Enter its name, and press OK button to confirm.
3. Press Add... button to add a data-type to the chosen language.
4. Enter its name, and press OK to confirm. From now on, once you have set your own language as the language for your project, you can pickup
the associated data-types as attribute type, operation return type and parameter type.

Data type options P. 1216


Data Type Options

Data type options P. 1217


File type options
Model Reference lets you add reference(s) to external file or URL into diagram element. You can open the referenced file or to get more information of
the model in later stage. In the Options dialog box, you can configure to use specific application or command to open different types of file and specify
your favorite web browser to open a URL. The system default handling method will be used if you have not configure the application or command to
handle a particular file type.

File Type Options in Option List

Configure application/Command for file types


To configure application/command for file types:
1. Press on the upper Add... button. This shows a dialog box where you can add file extension.
2. Specify the Extension. Any file reference with this extension will be opened by the particular application or command. Note that for a valid
extension a dot is required to put in front of the name of that extension, such as .doc.
3. Specify the Application/Command. The application or command for opening a file reference with file extension same as that defined in the
Extension field.
A command can be entered directly to the text field, and can include application arguments, while an application an be chosen from a file
chooser by pressing ... next to the text field.
4. Specify the Name of this application or command. This is an optional field for identifying this file extension.
5. Click OK to close the dialog box.

File type options P. 1218


File Type Options

File type options P. 1219


Code synchronization options

Code Synchronization Options in Option List

Code

Code synchronization options P. 1220


Code Options in Code Synchronization

Code synchronization options P. 1221


Option Name 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.

Generate Pre and Post Condition

Reverse ubterface getter/ setter as association

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.

Java Collection • Array - Generate one-to-many relationship as array


• Collection - (default) Generate one-to-many relationship as collection

Use generic collections (default true) Allow to use generic collection.

Generate annotation on • Property method - Generate annotation on property method


• Field - Generate annotation on field

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

Code Options details

Brace and indentation

Code synchronization options P. 1222


Brace and Indentation Options in Code Synchronization

Option Name 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
• Next line - Brace for annotation type appear at the line after the declaration

Indentation policy • Tabs - (default) Use a tab of space as indentation


• Spaces - Use spaces as indentation. The number of spaces can be defined below

Indentation size The number of spaces to indent.

Brace and Indentation Options details

Code synchronization options P. 1223


New Lines Options in Code Synchronization

Option Name 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.

New Lines Options details

Template

Code synchronization options P. 1224


Template Options in Code Synchronization

Option Description

Name

Template Options details

Code synchronization options P. 1225


C++ Code Synchronization

C++ Code Synchronization in Option List

Code

Code Options in C++ Code Synchronization

C++ Code Synchronization P. 1226


Option Name 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

Code Options details

Brace and indentation

Brace and Indentation Options in Code Synchronization

C++ Code Synchronization P. 1227


Option Name 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
• Next line - Brace for annotation type appear at the line after the declaration

Indentation policy • Tabs - (default) Use a tab of space as indentation


• Spaces - Use spaces as indentation. The number of spaces can be defined below

Indentation size The number of spaces to indent.

Brace and Indentation Options details

New Lines Options in Code Synchronization

C++ Code Synchronization P. 1228


Option Name 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.

New Lines Options details

Template

Template Options in Code Synchronization

Option Description

Name

Template Options details

C++ Code Synchronization P. 1229


Spell checking options
The Spell Checking feature supports spell checking in all inline editing, as well as in Textual Analysis. We support in-place editing of misspelled words,
simply by right-clicking your mouse instead of using the complex spell-check box. Spell-check provides intelligent suggestions for words, and you can
add your own words into your personal dictionary.

Spell Checking Options in Option List

Options

Spell Checking Options

Option Name Description

Enable spell checking (default true) Enable spell checking.

Dictionary The choose of dictionary affects the judgment of correctness of words.


• American - (default) Perform spell checking using an American dictionary.
• British - Perform spell checking using an British dictionary.
• Canadian - Perform spell checking using an Canadian dictionary.

Spell checking options P. 1230


Check spelling as you type (default true) Check spelling when typing.

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.

Spell Checking Options details

Spell checking options P. 1231


Keys options

Keys Options in Option List

Customizable program shortcuts


Commands can be invoked by pressing certain keys in the keyboard, as shortcuts. For example, holding down the Ctrl modifier key with the 'S' key
invokes the save command. Now, key bindings, which is the assignment of keys to commands, can be customized. This permits you to use the familiar
keystroke for invoking commands in VP-UML.
To assign/re-assign a key:
1. Double-click on the binding cell of the desired action.
2. Click on the Binding field at the bottom of dialog box.
3. Press the key for invoking the command selected. The binding field will be updated accordingly.
4. Press OK button to confirm the updates. You will be prompted to restart the application in order to make the changes take effect. By restarting,
you can invoke commands using the key defined.

Keys options P. 1232


Keys Options

Keys options P. 1233


Updating VP-UML with VP Suite Update
Visual Paradigm releases hotfixes from time to time. It is recommended to run the update program once a week to make sure the installation is up-to-
date. With an up-to-date program, latest bug fixes and minor enhancements can be obtained.
1. Launch VP Suite Update by any of the ways below:
• Through the Start Menu.

Starting VP Suite Update via Start Menu

• 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.

Starting VP Suite Update with launcher

This starts the VP Suite Update.

Updating VP-UML with VP Suite update P. 1234


2. From the update program, select a server from the drop-down menu for checking and downloading update files. The list of servers can be
refreshed by using the Refresh Server List button.

Selecting a location to check and download updates

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.

Updating VP-UML with VP Suite update P. 1235


3. Click Next button to continue. After checking is completed, the updated files are listed in the Pack Updates page.

The Pack Updates page for selecting files to be updated

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.

Description of blue and red colored filename in Pack Updates page

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.

Updating VP-UML with VP Suite update P. 1236


Automatic update notification
When you run VP-UML, checking of possible updates is done in background. If there are available updates, you will be notified through the message
pane. Then, you can perform an update to advance to the latest build.

Updating when running VP-UML


1. When running VP-UML, a message " Update is available now. Please click here for more information" may pop-up in the Message pane.
This message indicates that there is a build newer than the one that you are running, and you are recommended to perform an update to
advance to the latest build.

Notification of available updates

Automatic update notification P. 1237


2. Click on the message. This popup the Automatic Update dialog box.

Automatic update options

Here are the available options in the dialog box.


Option Description

Update Run the product update now.


now

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).

Never Do not check for product updates anymore.

Available options for automatic update

3. Select Update now and click OK to proceed. This popup the VP Suite Update.

To shutdown VP-UML

Automatic update notification P. 1238


4. In order to update, you need to close all the running VP application. Click Yes first, and then click OK in the dialog shown below to let VP Suite
Update close the applications for you.

Asked to close Visual Paradigm products

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.

Description of blue and red colored filename in Pack Updates page

6. Click Next to proceed with updating the files.


7. When update is complete, click Finish to confirm.

Setting the interval of checking updates


By default, update is checked weekly when starting VP-UML. You can change the interval of checking updates through the Options dialog box. To
change:

Automatic update notification P. 1239


1. Open the Options dialog box by selecting Tools > Options... from the main menu.

Opening the Options dialog box

Automatic update notification P. 1240


2. In the Options dialog box, select General from the list at the left hand side, then open the Update tab.

Update page in Options dialog box

Automatic update notification P. 1241


3. Select the interval of performing auto update from the Auto update drop down menu.

Selecting update interval

Here are the available options:


Option Description

Never Do not check for product updates anymore

On every Check for product updates everytime when starting VP-UML


start

Daily Check for product updates everyday, when starting VP-UML

Weekly Check for product updates every week, when starting VP-UML

Monthly Check for product updates every month, when starting VP-UML

Available update interval

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.

Prompting for update when starting VP-UML

Automatic update notification P. 1242


Use case diagram connection rules
Actor System Collaboration Use case

Actor Association, Dependency, Dependency, Association,


Dependency, Realization Realization Dependency,
Realization, Realization
Generalization

System Dependency, Dependency, Dependency, Dependency,


Realization Realization Realization Realization

CollaborationDependency, Dependency, Dependency, Association,


Realization Realization, Dependency,
Generalization Realization

Use case Dependency, Dependency, Association, Association,


Realization Realization Dependency, Dependency,
Realization Include,
Extend,
Realization,
Generalization

Connection rules in use case diagram

Use case diagram connection rules P. 1243


Class Diagram Connection Rules
Class NARY Collaboration Model

Class Generalization, Realization, Realization, Realization


Realization, Association, Dependency, Dependency,
Usage, Aggregation, Binding Binding
Association, Composition, Dependency, Dependency,
Aggregation, Dependency, Permission, Permission,
Composition, Access, Access, Access,
Dependency, Import, Import, Import,
Binding Merge, Merge, Merge,
Dependency, Instantiation, Instantiation, Instantiation,
Permission, Substitution Substitution, Substitution,
Access, Abstraction, Abstraction,
Import, Derive, Derive,
Merge, Refine, Refine,
Instantiation, Trace Trace
Substitution,
Abstraction,
Derive,
Refine,
Trace

NARY Realization, Realization, Realization, Realization,


Association, Dependency, Dependency, Dependency,
Aggregation, Access, Access, Access,
Composition, Import, Import, Import,
Dependency, Merge, Merge, Merge,
Access, Instantiation, Instantiation, Instantiation,
Import, Substitution Substitution, Substitution,
Merge,
Instantiation,
Substitution

CollaborationRealization, Realization, Generalization, Realization,


Dependency, Dependency, Realization, Dependency,
Binding Access, Usage, Binding
Dependency, Import, Dependency, Dependency,
Permission, Merge, Binding Access,
Access, Instantiation, Dependency, Import,
Import, Substitution Permission, Merge,
Merge, Access, Instantiation,
Instantiation, Import, Substitution,
Substitution, Merge, Abstraction,
Abstraction, Instantiation, Derive,
Derive, Substitution Refine,
Refine, Trace
Trace

Model Realization, Realization, Realization, Generalization,


Dependency, Dependency, Dependency, Realization,
Binding Access, Binding Usage,
Dependency, Import, Dependency, Dependency,
Permission, Merge, Access, Binding
Access, Instantiation, Import, Dependency,
Import, Substitution Merge, Access,
Merge, Instantiation, Import,
Instantiation, Substitution, Merge,
Substitution, Abstraction, Instantiation,
Abstraction, Derive, Substitution,
Derive, Refine, Abstraction,
Refine, Trace Derive,
Trace Refine,
Trace

Connection rules in class diagram

Class diagram connection rules P. 1244


Sequence diagram connection rules
Lifeline Combined Interaction Frame Actor ConcurrentContinuation Gate
fragment use

Lifeline Message MessageMessage Message

Combined
fragment

Interaction use

Frame

Actor

Concurrent Message Message Message

Continuation

Gate Message Message

Connection rules in sequence diagram

Sequence diagram connection rules P. 1245


Communication diagram connection rules
Lifeline Actor

Lifeline Line, Link,


DependencyDependency

Actor Link, Link,


DependencyGeneralization,
Dependency

Connection rules in communication diagram

Communication diagram connection rules P. 1246


State machine diagram connection rules
State Submachine Initial Shallow Deep Choice Junction Fork JoinTerminate
Entry
Final
Exit
state pspeudo state history history point
state

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

Choice Transition Transition Transition Transition Transition Transition Transition Transiti

Junction Transition Transition Transition Transition Transition Transition Transition Transiti

Fork 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

Connection rules in state machine diagram

State machine diagram connection rules P. 1247


Activity diagram connection rules
Activity Activity Action Accept Send signal Decision Merge
Activity
Output
Initial
Input
Flow
Fork
Join
parameter node event action action node node
node
final
pin
node

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

Activity final node

Flow final node

Input pin

Output pin Object Flow Object Flow Object


Object
Flow
Flow

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

Interruptible activity region

Expansion region Excepti


handler

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

Activity diagram connection rules P. 1248


Sequence node Control Control Flow Control Flow Control Flow Control Control
Control
Excepti
Flow Flow Flow
Flow
handler

Connection rules in activity diagram A

Value pin Object Central Data store Interruptible activity region Expansion
Conditional
Expansion
Structured
Sequence
Swimlane
Loop
node buffer node node region Activity
node
node

Activity Object Object Flow Object Flow Object


Control
Flow Flow

Activity parameter node Object Object Flow Object Flow Object


Flow Flow

Action Object Object Flow Object Flow Object


Control
Flow Flow

Accept event action Object Object Flow Object Flow Object


Control
Flow Flow

Send signal action Object Object Flow Object Flow Object


Control
Flow Flow

Decision node Object Object Flow Object Flow Object


Control
Flow Flow

Merge node Object Object Flow Object Flow Object


Control
Flow Flow

Fork node Object Object Flow Object Flow Object


Control
Flow Flow

Join node Object Object Flow Object Flow Object


Control
Flow Flow

Initial node Object Object Flow Object Flow Object


Control
Flow Flow

Activity final node Object Object Flow Object Flow Object


Flow Flow

Flow final node Object Object Flow Object Flow Object


Flow Flow

Input pin

Output pin Object


Flow

Value pin

Object node Object Object Flow Object Flow Object


Flow Flow

Central buffer node Object Object Flow Object Flow Object


Flow Flow

Data store node Object Object Flow Object Flow Object


Flow Flow

Interruptible activity region

Expansion region Exception


handler

Expansion node Object Object Flow Object Flow Object


Flow Flow

Swimlane

Structured Activity node Exception Control


handler Flow

Conditional node Exception Control


handler Flow

Loop node Exception Control


handler Flow

Activity diagram connection rules P. 1249


Sequence node Exception Control
handler Flow

Connection rules in activity diagram B

Activity diagram connection rules P. 1250


Component diagram connection rules
Component Interface Port Instance
specification

Component Dependency, Dependency, Dependency, Dependency,


Generalization, Association, Generalization, Realization
Realization, Aggregation, Realization,
Association, Composition, Association,
Aggregation, Usage Aggregation,
Composition, Composition,
Usage Usage

Interface Dependency, Dependency, Dependency, Dependency,


Realization, Generalization, Generalization, Generalization,
Association, Realization, Realization, Realization,
Aggregation, Association, Association, Association,
Composition, Aggregation, Aggregation, Aggregation,
Usage Composition, Composition Composition
Usage

Port Dependency, Dependency, Dependency, Dependency,


Realization, Association, Realization, Realization
Association, Aggregation, Association,
Aggregation, Composition, Aggregation,
Composition, Usage Composition
Usage

Instance Dependency, Dependency, Dependency Dependency,


specification Realization Generalization, Generalization,
Realization, Realization,
Association, Link
Aggregation,
Composition

Connection rules in component diagram

Component diagram connection rules P. 1251


Deployment diagram connection rules
Node Artifact Deployment Component Interface Port Instance
specification specification

Node Association, Association, Association, Association, Association, Dependency, Dependency,


Aggregation, Aggregation, Aggregation, Aggregation, Aggregation, Manifestation, Manifestation,
Composition, Composition, Composition, Composition, Composition, Realization Realization
Dependency, Dependency, Dependency, Dependency, Dependency,
Manifestation, Manifestation, Manifestation, Manifestation, Manifestation
Generalization, Deployment, Deployment, Generalization,
Realization, Generalization, Generalization, Realization,
Usage Realization, Realization, Usage
Usage Usage

Artifact Association, Association, Association, Association, Dependency, Dependency, Dependency,


Aggregation, Aggregation, Aggregation, Aggregation, Manifestation Manifestation, Manifestation,
Composition, Composition, Composition, Composition, Realization Realization
Dependency, Dependency, Dependency, Dependency,
Manifestation, Manifestation, Manifestation, Manifestation,
Generalization, Generalization, Generalization, Generalization,
Realization, Realization, Realization, Realization,
Usage Usage Usage Usage

Deployment Association, Association, Association, Association, Dependency, Dependency, Dependency,


specification Aggregation, Aggregation, Aggregation, Aggregation, Manifestation Manifestation, Manifestation,
Composition, Composition, Composition, Composition, Realization Realization
Dependency, Dependency, Dependency, Dependency,
Manifestation, Manifestation, Manifestation, Manifestation,
Generalization, Generalization, Generalization, Generalization,
Realization, Realization, Realization, Realization,
Usage Usage Usage Usage

Component Association, Association, Association, Association, Association, Association, Dependency,


Aggregation, Aggregation, Aggregation, Aggregation, Aggregation, Aggregation, Manifestation,
Composition, Composition, Composition, Composition, Composition, Composition, Realization
Dependency, Dependency, Dependency, Dependency, Dependency, Dependency,
Manifestation, Manifestation, Manifestation, Manifestation, Manifestation, Manifestation,
Generalization, Generalization, Generalization, Generalization, Usage Generalization,
Realization, Realization, Realization, Realization, Realization
Usage Usage Usage Usage

Interface Association, Dependency, Dependency, Association, Association, Association, Association,


Aggregation, Manifestation, Manifestation, Aggregation, Aggregation, Aggregation, Aggregation,
Composition, Realization Realization Composition, Composition, Composition, Composition,
Dependency, Dependency, Dependency, Dependency, Dependency,
Manifestation, Manifestation, Manifestation, Manifestation, Manifestation,
Realization Realization, Generalization, Generalization, Generalization
Usage Realization, Realization Realization
Usage

Port Dependency, Dependency, Dependency, Association, Association, Association, Dependency,


Manifestation, Manifestation, Manifestation, Aggregation, Aggregation, Aggregation, Manifestation,
Generalization, Generalization, Generalization, Composition, Composition, Composition, Generalization
Realization Realization Realization Dependency, Dependency, Dependency, Realization
Manifestation, Manifestation, Generalization,
Generalization, Usage Realization
Realization,
Usage

Instance specification Dependency, Dependency, Dependency, Dependency, Association, Dependency, Link,


Manifestation, Manifestation, Manifestation, Manifestation, Aggregation, Manifestation, Dependency,
Realization Realization Realization Realization Composition, Realization Manifestation,
Dependency, Deployment,
Manifestation, Generalization
Generalization Realization

Connection rules in deployment diagram

Deployment diagram connection rules P. 1252


Package diagram connection rules
Package Subsystem

Package Dependency, Dependency,


Import, Import,
Access, Access,
Generalization, Realization,
Realization, Merge
Merge

Subsystem
Dependency, Dependency,
Import, Import,
Access, Access,
Realization, Generalization,
Merge Realization,
Merge

Connection rules in package diagram

Package diagram connection rules P. 1253


Object diagram connection rules
Instance Class
specification

Instance Link, Association,


specification Dependency, Aggregation,
Generalization, Composition,
Realization Dependency,
Generalization,
Realization

Class Association, Association,


Aggregation, Aggregation,
Composition, Composition,
Dependency, Dependency,
Generalization, Generalization,
Realization Realization

Connection rules in object diagram

Object diagram connection rules P. 1254


Composite structure diagram connection rules
Class Part Property Interface Port Collaboration Collaboration
Use

Class Dependency, Dependency, Dependency, Association, Association, Association, Association,


Represents, Represents, Represents, Aggregation, Aggregation, Aggregation, Aggregation,
Occurrence, Occurrence, Occurrence, Composition, Composition, Composition, Composition,
Generalization, Realization Realization Dependency, Dependency, Dependency, Dependency,
Realization Represents, Represents, Represents, Represents,
Occurrence, Occurrence, Occurrence, Occurrence,
Generalization Generalization, Realization Realization
Realization

Part Dependency, Connector, Connector, Dependency, Connector, Dependency, Dependency,


Represents, Dependency, Dependency, Represents, Dependency, Represents, Represents,
Occurrence, Represents, Represents, Occurrence Represents, Occurrence Occurrence,
Occurrence Occurrence Occurrence

Property Dependency, Connector, Connector, Dependency, Connector, Dependency, Dependency,


Represents, Dependency, Dependency, Represents, Dependency, Represents, Represents,
Occurrence Represents, Represents, Occurrence Represents, Occurrence Occurrence
Occurrence Occurrence Occurrence

Interface Association, Dependency, Dependency, Association, Association, Association, Association,


Aggregation, Represents, Represents, Aggregation, Aggregation, Aggregation, Aggregation,
Composition, Occurrence, Occurrence, Composition, Composition, Composition, Composition,
Dependency, Realization Realization Dependency, Dependency, Dependency, Dependency,
Represents, Represents, Represents, Represents, Represents,
Occurrence, Occurrence, Occurrence, Occurrence, Occurrence,
Generalization, Generalization, Generalization, Realization Realization
Realization Realization Realization

Port Association, Connector, Connector, Association, Connector, Dependency, Dependency,


Aggregation, Dependency, Dependency, Aggregation, Association, Represents, Represents,
Composition, Represents, Represents, Composition, Aggregation, Occurrence, Occurrence,
Dependency, Occurrence, Occurrence, Dependency, Composition, Realization Realization
Represents, Realization Realization Represents, Dependency,
Occurrence, Occurrence Represents,
Realization Occurrence,
Realization

Collaboration Association, Dependency Dependency Association, Association, Dependency Association,


Aggregation, Represents, Represents, Aggregation, Aggregation, Represents, Aggregation,
Composition, Occurrence, Occurrence, Composition, Composition, Occurrence, Composition,
Dependency Realization Realization Dependency Dependency Realization Dependency
Represents, Represents, Represents, Represents,
Occurrence, Occurrence Occurrence, Occurrence,
Realization Realization Realization

Collaboration Association, Dependency Dependency Association, Dependency Association, Dependency


Use Aggregation, Represents, Represents, Aggregation, Represents, Aggregation, Represents,
Composition, Occurrence, Occurrence, Composition, Occurrence, Composition, Occurrence,
Dependency Realization Realization Dependency Realization Dependency Realization
Represents, Represents, Represents,
Occurrence, Occurrence Occurrence,
Realization Realization

Connection rules in composite structure diagram

Composite structure diagram connection rules P. 1255


Interaction overview diagram connection rules
Interaction Interaction Decision Merge Fork node Join node Initial Activity final
use node node node

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

Connection rules in interaction overview diagram

Interaction overview diagram connection rules P. 1256


Requirement diagram connection rules
RequirementModelTestcase

Requirement
Composition,
Derive,
Trace

Model Satisfy,
Refine

Testcase Verify,

Connection rules in requirement diagram

Requirement diagram connection rules P. 1257


Basic diagram connection rules
Process Decision Business Document
actor

Process ConnectorConnectorConnector Connector

Decision ConnectorConnectorConnector Connector

Business ConnectorConnectorConnector Connector


actor

Document ConnectorConnectorConnector Connector

Connection rules in basic diagram

Basic diagram P. 1258


Entity relationship diagram connection rules
Entity View Sequence Stored Stored procedure Triggers
procedures resultset

Entity One-to-one relationship, One-to-one relationship,


One-to-many relationship, One-to-many relationship,
Many-to-many relationship Many-to-many relationship

View One-to-one relationship, One-to-one relationship,


One-to-many relationship, One-to-many relationship,
Many-to-many relationship Many-to-many relationship

Sequence

Stored procedures

Stored procedure
resultset

Triggers

Connection rules in entity relationship diagram

Entity relationship diagram connection rules P. 1259


ORM diagram connection rules
Class Entity View

Class Association, Class-entity mapping Class-entity mapping


Aggregation,
Composition

Entity Class-entity One-to-one relationship, One-to-one relationship,


mapping One-to-many relationship, One-to-many relationship,
Many-to-many relationship Many-to-many relationship

View Class-entity One-to-one relationship, One-to-one relationship,


mapping One-to-many relationship, One-to-many relationship,
Many-to-many relationship Many-to-many relationship

Connection rules in orm diagram

ORM diagram connection rules P. 1260


Business process diagram connection rules
Task Sub-process Start event Intermediate event End
Choreography
Gateway
Pool/
Data
Text
Call
event
annotation
activity
Object
Sub-
Lane
task
process

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

Gateway Sequence flow, Sequence flow, Sequence flow, Sequence Associa


Sequen
Message flow Message flow Message flow flow, flow,
To-
Messag
Directio
flow
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

Text annotation Association, Association, Association, Association, Association,Associa


To-Direction Association To-Direction Association To-Direction Association To-Direction Association To- To-
Direction Directio
AssociationAssocia

Data object Association, Association, Association, Association, Association,Data


Associa
To-Direction Association To-Direction Association To-Direction Association To-Direction Association To- To-
Associa
Direction Directio
AssociationAssocia

Pool/lane Associa
To-
Directio
Associa

Connection rules in business process diagram

Business process diagram connection rules P. 1261


Conversation diagram connection rules
Participant Text
annotation

Participant Conversation link, Association


Sub-conversation link,
Call conversation link

Text Association
annotation

Connection rules in conversation diagram diagram

Conversation diagram connection rules P. 1262


Data flow diagram connection rules
Process External entity Data store

Process Data Flow, Data Flow, Data Flow,


Bidirectional data flow Bidirectional data flow Bidirectional data flow

External Data Flow,


entity Bidirectional data flow

Data store Data Flow,


Bidirectional data flow

Connection rules in data flow diagram

Data flow diagram P. 1263


EPC diagram connection rules
Event Function And Or XOR Organization Process Information
operator operator operator unit path resource

Event Control flow Control flow Control Control Control


flow flow flow

Function Control Control flow Control flow Control Control Information


flow flow flow flow

And operator Control Control flow Control flow Control Control


flow flow flow

Or operator Control Control flow Control flow Control Control


flow flow flow

XOR operator Control Control flow Control flow Control Control


flow flow flow

Organization unit Organization unit assignment

Process path Control


flow

Information Information flow


resource

Connection rules in EPC diagram

EPC diagram P. 1264


Process map diagram connection rules
Process Send Receive

ProcessProcess Process Process


link link link

Send Process Process Process


link link link

ReceiveProcess Process Process


link link link

Connection rules in process map diagram

Process map diagram P. 1265


Organization chart connection rules
Organization
unit

Organization Line
unit

Connection rules in organization chart

Organization chart connection rules P. 1266


Archimate diagram connection rules
Business Business Business Business Business Business Business Junction
Business
actor role collaboration process function interaction event service

Business Aggregation, Assignment Realization


actor Composition,
Specialization

Business Assignment Aggregation, Assignment Assignment Assignment


role Composition,
Specialization

Business Aggregation Aggregation, Assignment


collaboration Composition,
Specialization

Business process Assignment Triggering, Triggering Triggering Triggering Triggering Realization


Aggregation,
Composition,
Specialization

Business function Assignment Triggering, Triggering, Triggering Triggering Triggering Realization


Composition Aggregation,
Composition,
Specialization

Business Assignment Assignment Triggering Triggering Triggering, Triggering Triggering Realization


interaction Aggregation,
Composition,
Specialization

Business Triggering Triggering Triggering Aggregation,


event Composition,
Specialization

Junction Triggering Triggering Triggering Triggering

Business service Used by Used by Used by Aggregation


Composition
Specializatio

Business interface Association Association Assignment

Business object Read access Read access Read access Read access Read
access

Product Used by Aggregation

Contract Read
access

Representation

Meaning

Value Association

Application Assignment
collaboration

Application Assignment Assignment Assignment


component

Application Used by Used by Used by Used


service by

Application
function

Application
interaction

Application Used by
interface

Data object

Node

Archimate diagram connection rules P. 1267


Device

System software

Infrastructure
interface

Infrastructure
service

Artifact

Connection rules in archimate diagram A

Business Business Product Contract Representation Meaning Value


interface object

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 Assignment Read Read Association


service access, access,
Write access Write access

Business Aggregation,
interface Specialization

Business Association, Association


object Aggregation,
Specialization

Product Aggregation, Aggregation Association


Specialization

Contract Aggregation,
Specialization

Representation Realization, Aggregation, Association


Association Specialization

Meaning Association Aggregation,


Specialization

Value Association Aggregation,


Specialization

Application
collaboration

Application
component

Application
service

Archimate diagram connection rules P. 1268


Application
function

Application
interaction

Application
interface

Data object Realization

Node

Device

System
software

Infrastructure
interface

Infrastructure
service

Artifact

Connection rules in archimate diagram B

Application Application Application Application Application Application Data object


collaboration component service function interaction interface

Business
actor

Business Require
role

Business
collaboration

Business Assignment
process

Business
function

Business Assignment Assignment


interaction

Business
event

Junction

Business Used by Used by


service

Business Used by
interface

Business
object

Product

Contract

Representation

Meaning

Value

Application Aggregation, Association, Assignment Provide,


collaboration Composition, Aggregation Require
Specialization

Application Association, Aggregation, Realization Assignment, Association,


component Composition Composition, Composition Provide,

Archimate diagram connection rules P. 1269


Specialization Require,
Composition

Application Aggregation, Assignment Read


service Composition, access,
Specialization Write access

Application Assignment Realization Aggregation, Read


function Composition, access,
Specialization Write access

Application Assignment Realization Aggregation, Read


interaction Composition, access,
Specialization Write access

Application Association Assignment Aggregation,


interface Composition,
Specialization

Data Read Read Read Association,


object access, access, access, Aggregation,
Write access Write access Write access Composition,
Specialization

Node

Device

System
software

Infrastructure
interface

Infrastructure
service

Artifact Realization Realization

Connection rules in archimate diagram C

Node Device System Infrastructure Infrastructure Artifact


software interface service

Business
actor

Business
role

Business
collaboration

Business
process

Business
function

Business
interaction

Business
event

Junction

Business
service

Business
interface

Business
object

Product

Contract

Archimate diagram connection rules P. 1270


Representation

Meaning

Value

Application
collaboration

Application
component

Application
service

Application
function

Application
interaction

Application
interface

Data
object

Node Communication Composition Composition Provide, Realization Assignment


path, Require
Aggregation,
Composition,
Specialization

Device Network Aggregation, Assignment Provide, Realization Assignment


Composition, Require
Specialization

System Assignment Aggregation, Provide, Realization Assignment


software Composition, Require
Specialization

Infrastructure Aggregation, Assignment


interface Composition,
Specialization

Infrastructure Assignment Aggregation, Read access,


service Composition, Write access
Specialization

Artifact Assignment Assignment Assignment Read access, Aggregation,


Write access Composition,
Specialization

Connection rules in archimate diagram D

Archimate diagram connection rules P. 1271


EJB diagram connection rules
Entity bean Message-driven bean Session bean

Entity bean One-to-one association, One-to-one association, One-to-one association,


One-to-one bi-directional association, One-to-one bi-directional association, One-to-one bi-directional
One-tomany association, One-tomany association, association,
One-to-many bi-directional association, One-to-many bi-directional association, One-tomany association,
Many-to-many association, Many-to-many association, One-to-many bi-directional
Many-to-many bi-directional association Many-to-many bi-directional association association,
Many-to-many association,
Many-to-many bi-directional
association

Message-driven One-to-one association, One-to-one association, One-to-one association,


bean One-to-one bi-directional association, One-to-one bi-directional association, One-to-one bi-directional
One-tomany association, One-tomany association, association,
One-to-many bi-directional association, One-to-many bi-directional association, One-tomany association,
Many-to-many association, Many-to-many association, One-to-many bi-directional
Many-to-many bi-directional association Many-to-many bi-directional association association,
Many-to-many association,
Many-to-many bi-directional
association

Session bean One-to-one association, One-to-one association, One-to-one association,


One-to-one bi-directional association, One-to-one bi-directional association, One-to-one bi-directional
One-tomany association, One-tomany association, association,
One-to-many bi-directional association, One-to-many bi-directional association, One-tomany association,
Many-to-many association, Many-to-many association, One-to-many bi-directional
Many-to-many bi-directional association Many-to-many bi-directional association association,
Many-to-many association,
Many-to-many bi-directional
association

Connection rules in EJB diagram

EJB diagram P. 1272


Overview diagram connection rules
Diagram overview

Diagram Diagram containment,


overview Directional generic connector

Connection rules in overview diagram

Overview diagram connection rules P. 1273


Mind mapping diagram connection rules
Node

NodeBranch,
Link,
From
link,
To link

Connection rules in mind mapping diagram

Mind mapping diagram P. 1274

You might also like