Visual UML version 4.11 Update Release Notes
Version 4.11 Release (Build #546 –
NOTE: Model files (*.Uml) created
by Visual UML version 4.0 (or later) are NOT backwards compatible with Visual
UML version 3.2 (versions 3.2 thru 3.26) or earlier. Therefore, Model files
(*.Uml) created by Visual UML version 4.0 (or later) can NOT be opened by
Visual UML version 3.2 (versions 3.20 thru 3.26) or earlier. Also, if you saved
your version 3.x models in XML file format you will need to save them in .Uml
file format in order to be able to open them using version 4.0 (or later).
After you have upgraded your version 3.x models to version 4.0 (or later)
format you can save them in XML file format (.Umlx file extension).
Also, Model files (*.Uml) created by Visual UML version 4.11 are NOT
backwards compatible with Visual UML version 4.0, 4.01 or 4.1. Therefore, Model
files (*.Uml) created by Visual UML version 4.11 can NOT be opened by Visual
UML version 4.0, 4.01 or 4.1.
Updated Files: Visual UML4.Exe, VUML.Chm, VUML2HTML4.Dll, Rose2VUML4.Dll,
VUML40LayoutDiagram.Dll, RevEngrCPP.Dll, VSPrint8.Ocx, VSPDF8.Ocx
New Files: XML Files\vuml411.dtd (replaces vuml40.dtd), XML
Files\empty411.xml (replaces empty40.xml)
1. Can now change the relative order of classes when generating database
schema tables from classes on class diagrams.
2. Tagged Values, Constraints or Responsibilities names that are displayed
inside Classes on Class diagrams are no longer drawn using italic font if the
preceding Attribute or Operation was Abstract.
3. Nested Class names that are displayed inside Classes on Class diagrams
are now drawn using an italic font if Abstract.
4. Fixed a problem that could result in a run-time #52 when generating XML
Schema (XSD) code from Classes located in the root of the Model (I.e. Classes Not in a Package) when the ‘Force
All Classes Into Single File’ option is set to on (checked).
5. Fixed a problem that could result in a run-time error when attempting to
Rename a Nested Class in a container Class if that Nested Class was the only
one in the container Class.
6. Model Elements, Relationships and Diagrams can now “realize” Model-level
Requirements and/or Test Cases. These are Requirements and/or Test Cases that
are defined at the Model level (root) and are globally available in the Model
for realization by any number of objects, relationships, etc. of any type.
Thus, one or more objects, relationships, etc. can realize a particular
Requirement or Test Case.
7. When the Requirements Editor dialog box is accessed for any object,
relationship, diagram, etc. it now has two tabs: one for owned Requirements and
another for Realized Requirements. Owned Requirements have scope only within a
particular object, relationship, diagram, etc. Realized Requirements are
derived from the Model root and are available for realization by any object,
relationship, diagram, etc. within the model. Model-level Requirements are
realized by an object, relationship, diagram, etc. by setting the checkbox
adjacent to it to on (checked).
8. When the Test Cases Editor dialog box is accessed for any object,
relationship, diagram, etc. it now has two tabs: one for owned Test Cases and
another for Realized Test Cases. Owned Test Cases have scope only within a
particular object, relationship, diagram, etc. Realized Test Cases are derived
from the Model root and are available for realization by any object,
relationship, diagram, etc. within the model. Model-level Test Cases are
realized by an object, relationship, diagram, etc. by setting the checkbox adjacent
to it to on (checked).
9. Added options to the Reports sub-menu option Tools menu for
Printing/Exporting Reports of Model-level Requirements and/or Test Cases.
10. Can now choose to include Realized Requirements and/or Test Cases in
Object Definitions and Use Case Definitions reports.
11. Can now choose to include Model-level Requirements and/or Test Cases in
Object Definitions reports.
12. Can now choose to include Model-level Requirements and/or Test Cases in
Model Items reports.
13. Can now choose to include Realized Requirements and/or Test Cases when
Publishing the Model, Packages or Diagrams to HTML.
14. Nested Classes are now included in Classes when Publishing the Model,
Packages, Classes or Class Diagrams to HTML.
15. When generating C++ code for classes that have an association
relationship with another Class, a #include filename reference of the file
containing the other class is only inserted into the header (.H) file of the
generated class for composition associations. For aggregation associations, a
class declaration of the other class is instead inserted into the header (.H)
file of the generated class and a #include filename reference of the file
containing the other class is inserted into the implementation (.CPP) file.
Inclusion of the associated class’ #include filename and/or the associated
class declaration can be enabled/disabled using a new option in the Code
Generation Options dialog box.
16. Added a new option named ‘Place Nested Classes Before Attributes and
Operations’ to the Code Generation Options dialog box that controls whether
Nested Classes are placed before Attributes and Operations when generating C++,
C#, Java or VB.NET code. The default is to place Nested Classes after Attributes and Operations.
17. Fixed problem whereby Bring-to-Front and Send-to-Back would not work
properly for Activities on an Activity diagram.
18. The ‘Class File Preamble’ and ‘Class File Comment Block’ fields are no
longer enabled on the C++, C#, Java, VB.NET Languages tab in the Class
Properties Editor dialog box for Nested Classes as they pertain only to
container Classes, not nested Classes.
19. Added a ‘Class Postamble’ field to the C++, C#, Java, VB.NET Languages
tab in the Class Properties Editor dialog box. The contents of the field are
appended to the Class (incl. Nested Classes) declaration during code
generation.
20. Updated on-line Help.
Version 4.1 Release (Build #543 –
NOTE: Model files (*.Uml) created
by Visual UML version 4.0 (or later) are NOT backwards compatible with Visual
UML version 3.2 (versions 3.2 thru 3.26) or earlier. Therefore, Model files
(*.Uml) created by Visual UML version 4.0 (or later) can NOT be opened by
Visual UML version 3.2 (versions 3.20 thru 3.26) or earlier. Also, if you saved
your version 3.x models in XML file format you will need to save them in .Uml
file format in order to be able to open them using version 4.0 (or later).
After you have upgraded your version 3.x models to version 4.0 (or later)
format you can save them in XML file format (.Umlx file extension).
Also, Model files (*.Uml) created by Visual UML version 4.1 are NOT
backwards compatible with Visual UML version 4.0 or 4.01. Therefore, Model
files (*.Uml) created by Visual UML version 4.1 can NOT be opened by Visual UML
version 4.0 or 4.01.
Updated Files: Visual UML4.Exe, VUML.Chm, VUML-CPP.Chm, VUML2HTML4.Dll,
Rose2VUML4.Dll, VUML40LayoutDiagram.Dll, RevEngrCPP.Dll, XML Files\vuml40.dtd
New Files: VSPrint8.Ocx, VSPDF8.Ocx, PGStandardLib20.dll, PGPreprocessorLib.dll,
SQLServer2000Pubs.Uml, SQLServer2000Pubs.Sql, Northwind_SQLServer2000.Uml, SQLServer2000Northwind.Sql,
XMLModelFileFormat.Zip
1. The Class Diagram Layout Interface (DLI) is now included.
2. Removed the “Warning” messages that appeared when choosing to Import a
Model in VUML or XML file format.
3. Fixed the appearance of the “resize handles” icon located at the bottom
right corner of many resizable dialog boxes so that they display better under
Windows XP display themes.
4. Fixed the appearance of the up/down buttons icon in several dialog boxes
so that they display better under Windows XP display themes.
5. Fixed the appearance of assorted buttons icons in several dialog boxes so
that they display better under Windows XP display themes.
6. Fixed the resize behavior of several dialog boxes so that they display
better under Windows XP.
7. Fixed the appearance of assorted fields in several dialog boxes so that
they display better under Windows XP display themes.
8. The State Invariant Expression dialog box (for State Invariants on
Lifelines on Objects on Sequence diagrams) is now resizable.
9. The C++ Explicit option is now copied when copying a Class Operation,
either individually or when a Class is copied.
10. Added a ‘Class File Preamble’ field to the ‘C++/C#/Java/VB.NET’ Languages
tab in the Class Properties Editor dialog box.
11. Added an ‘Add Namespace Reference’ button next to the (new) ‘Class File
Preamble’ field on the ‘C++/C#/Java/VB.NET’ Languages tab in the Class
Properties Editor dialog box.
12. Added a ‘Class File Comment Block’ field to the ‘C++/C#/Java/VB.NET’
Languages tab in the Class Properties Editor dialog box.
13. Added an ‘Add Namespace Reference’ button to the Preamble tab/field in
the Package Properties Editor dialog box.
14. Can now display Classes and their Members (Attributes, Operations, Nested
Classes, Parameters, etc.) on Class diagrams using a notation that is
essentially the same as the code that would be generated for the Class. This
applies to Classes whose target language is C++, C#, Java or VB.NET. The code
notation is displayed by setting the new ‘Display Classes Using Language
Notation’ options on the (renamed) ‘Classes & Interfaces’ tab in the
Diagram Properties dialog box.
15. Added new menus, menu options, toolbar and toolbar buttons to enable more
convenient adding of class types (classes, interfaces, enums, structs,
delegates, modules, etc.) to the model and class diagrams. These new menus,
menu options, toolbar and toolbar buttons are made available according to the
model’s target language. These class type menu options and toolbar buttons are
also available to enable more convenient adding of nested class types. When a
class diagram is active, the selected class is added to it. When a package or
class is active in the model explorer, the selected class is added to it.
16. Added new menus, menu options, toolbar and toolbar buttons to enable more
convenient adding of class members (fields/variables, constants, properties,
methods, constructors, destructors, events, delegates, indexers, operators,
attributes, etc.) to classes in the model and on class diagrams. These new
menus, menu options, toolbar and toolbar buttons are made available according
to the class type and the target language assigned to the class.
17. The new menu options and toolbar buttons for adding properties to classes
results in the automatic creation of the private member variable and the
corresponding get and/or set accessors and is similar to the approach
previously used to create properties when generating code for class attributes
with stereotype = “Property”. This property creation applies to C#, VB.NET, VB6
and Java properties.
18. The (new) Code Class Toolbar can be shown and hidden using a (new) option
in the View Toolbars menu.
19. Can now add more than one anonymous Enum to a Class. These are Nested
Classes with Stereotype = “Enum” and Name = “<anonymous>”.
20. Can now add more than one anonymous Parameter to a Class Operation. These
are Parameters with Name = “<anonymous>”.
21. Can now add more than one anonymous Parameter to a Template Class. These
are Parameters with Name = “<anonymous>”.
22. The Pass By Pointer option is now properly transferred from Pass By
column in Operation Parameters grid to Parameter Editor dialog box when using
Edit button.
23. Port Names (on Class and Component diagrams) are now prefixed with the
appropriate visibility prefix (+, -, # or ~).
24. Fixed problem that could cause loss of linkage of foreign key (FK)
relationships attributes between parent (referenced) and child (referencing)
classes if the parent (referenced) class (or any of its attributes) were
edited. Note: This loss of FK attributes linkage would typically only occur if
the FK was to non-PK fields in the parent (referenced) class that was edited.
It would typically NOT occur if the FK was to PK fields in the parent
(referenced) class that was edited.
25. No longer get a run-time error and/or inability to edit an object’s
description if did not choose to install the spell checker when installing
Visual UML.
26. No longer get a run-time error and/or inability to edit a Use Case’s
detailed definition/specification if did not choose to install the spell
checker when installing Visual UML.
27. Fixed some problems with the placement and routing of connections (such
as Transitions) between an object (such as a State) and another object inside
it (such as another State) so that the connections stay in place more
predictably as the container object is modified, moved, etc. and when the
diagram is redrawn such as when scrolling, zooming, being edited, etc. Also, a
more predictably routed connection (such as a Transition) is initially created
when adding between a container object (such as a State) and a contained object
(such as another State).
28. Modified the way that dates are entered in the grids for Test Cases,
Project Issues, Project Tasks, etc. Now, a button in the cell is clicked to
invoke a dialog box in which the date is selected.
Publish To HTML:
29. Changed the presentation of information for Tagged Values, Constraints,
Responsibilities, Requirements, Scenarios and Test Cases to use a more tabular
format with rows for each property. Also fixes word-wrapping problems for long
descriptions of Tagged Values, Constraints, Responsibilities, Requirements,
Scenarios and Test Cases.
30. Changed the presentation of information for Model Glossary Entries,
Project Issues and Project Tasks to use a more tabular format with rows for
each property. Also fixes word-wrapping problems for long descriptions of Model
Glossary Entries, Project Issues and Project Tasks.
31. Activity Object Nodes can now be included in HTML Reports for Activities
& Actions.
32. Fixed problem Publishing Class diagrams to HTML if the Class diagram
contained a Class with one or more Ports.
33. Fixed problem Publishing Component and Deployment diagrams to HTML if the
Component or Deployment diagram contained a Component with one or more Ports.
34. Tagged Values, Constraints, Scenarios, Requirements and Test Cases can now
be included in HTML Reports for Activity Flows, State Transitions,
Associations, Dependencies and Generalizations.
Reporting:
35. When printing/exporting Descriptions reports, object categories (Actors,
Classes, Components, Nodes, Packages, Use Cases, etc.) are no longer included
if they do not contain objects with descriptions.