DB Visual ARCHITECT 4.4 Release Notes
Release Date: October 20, 2008
Reuse Previous Works with Design Patterns
Visual Paradigm introduced the Design Patterns support in this new release to enhance the reusability of your works which has been done in the previous projects. In many development scenarios, we often need to reuse, refine, elaborate and transcribe an portion of diagram, known as a design pattern, during the development process, or in between development phases. With this Design Pattern Repository, you now on longer to need re-model the frequently used design patterns again and again.
Progressively Develop Conceptual, Logical and Physical ERD
There are three types of ERDs: the conceptual, the logical, and the physical, which support modeling of data in three levels of abstraction from conceptual data model to implementation of a specific database. Starting from this new release, Visual Paradigm allows these three levels data modeling for facilitating the creation of database model independent on the particular database system. You may create conceptual model and logical model that are independent on any DBMS. Then, you may generate physical model for each DBMS you will use for your applications.
Starting Up Enterprise-Scale Project in a Few Seconds not Minutes
Although Visual Paradigm has been the leader in the modeling tool market, and is know to be the best in product performance. We are still making every effort for striving for excellent in product performance, especially its startup and loading speed to fulfill the nowadays demanding business. A huge VP project with several thousand of shapes, would require to be started up in about couple minutes of time in the past; but for this new version, with the same hardware configuration, it is talking about a matter of a few seconds, resulting from our unique system architecture and fast loading technology.
Display Stereotyped Model Elements As Image Icon
Stereotypes is extensibility mechanisms in UML which allows designers to extend the vocabulary of UML in order to create new model elements, derived from existing ones, but that have specific properties that are suitable for a particular problem domain or otherwise specialized usage.
For example, when modeling a network you might use a image icon (a symbol) for representing routers and hubs. By using stereotyped nodes you can make these things appear as primitive building blocks and make the specification much more comprehensible.
Import Visio Diagrams into Visual Paradigm
Visio is a widely used diagramming tool in the market, which was also a favorite for many of our users. However after they adopted Visual Paradigm and experience its unbeatable editing capability, most of them requested for converting the legacy diagrams created by Visio to Visual Paradigm project.
In this new release, import Visio to Visual Paradigm in no longer a dream. Just a matter of a few clicks, your legacy diagram will be imported to Visual Paradigm and all the color and style which you created in Visio can be retained. Or alternatively, you can switch to the Visual Paradigm's default style of your choice.
Targeted Placement of Classes in Synchronization of Class and ER Diagram
In a very simple system, there may only be one class diagram which normally includes all the classes created in the class repository. However, in large scale enterprise projects, we used to have hundreds of classes if not over a thousand. Each of the developers would only use a selected set of classes for the subsystem(s) he/she is responsible, representing by one or more class diagrams. Thus, one particular class diagram does not include all classes in the class repository. In other words, a particular class diagram is a static view of the subsystem which includes only a selected set of classes it is required. Likewise, a complex system may have more than one ERDs, and each of these ERDs is interlinked with only a selected of classes in the class repository.
With this new feature, now developers can specify which targeted ERD for the newly created class models to be synchronized in the first time, significantly enhanced the flexibility of the coding engineering process for database applications.
Show or Hide Diagram Elements on Demand
Enterprise applications development often require to deal with complex diagrams which could sometime grow too large for manipulations. For example, We would like to highlight only a group of classes in a class diagram for presentation or printing temporarily. In this new release, the Show and Hide Diagram Element feature allows you to show only those elements on the diagram plane which you are interested for performing some operations more conveniently in a temporary state and later you can make them visible again for the normal operations.
Improve Traceability using Element Based revision history
Element based revision history is introduced to enhance the traceability as the diagram evolved from one version to other. A list of changes will be automatically recorded, making it easier to advice users of the information on how it has changed from version to version. The ability to track changes promotes accountability and makes it easier to find the right person to solve problems in the materials maintained.
- Move callout shape won't snap by container if only its pointer is touching the container
- Supported show/hide role name visibility
- Supported triggering different layout algorithms in Open API
- Added option for suppressing association role names' stereotype
- Fine tuned comments in generated ORM samples for indicating the attributes that cannot be null when saving
- Fixed update failed to work if the URL ends with a slash
- Fixed generate inconsistent content of attribute documentation in HTML, PDF & Word reports
- Fixed index column asking sync name
- Fixed wrongly generated property prefix in ORM code for composite key
- Fixed unable to copy things across project
- Fixed unable to open specification of connector in diagram navigator
- Fixed generated decimal type as bigdecimal
- Fixed bad rendering when wrapped class members and enter attribute name in multiple lines
- Fixed missing join column in the one to one association
- Fixed font size for documentation in generated Word report not follow that defined in the project
- Fixed C++ IR not work on Linux without error message
- Fixed inherited abstract operations are not generated in ORM code
- Fixed reverse DDL fail to reverse SQL Server sample DB
- Fixed cannot see any imported project to Perforce repository in project list caused by security settings
- Fixed bad rendering of diagram info in publisher output
- Fixed export erd to excel missing scale of numeric type
- Fixed unable to rename diagram by pressing F2 on diagram
- Fixed cannot reverse interface for Objective-C
- Fixed ORM option "Compile to dll" is not working
