Turning data into business advantage

 Home  Services  Downloads / Links  Résumé  Company Profile  Contact  Search
   Data Modelling      
   Data Architecture From UML to XML    
   Data Analysis MXV loose coupling    
   Database Design & Implementation MXV demo / case study    
   XML Schema & Vocabulary Design MXV trial download    
   XML Value Validation MXV Tool Suite V3.2    
   Model Change Management MXV Tool Suite V2.3    
   AllFusion ERwin & PowerDesigner Tool Suites Methodology documents    
   Hands-on consulting MXV NDR 2.1    
    Latest MXV news    
    MXV history    
    Copyrights and IPs    

 

 

What's new in MXV Productivity Tools version 2.3 

On this page

Topic

1. MXV Productivity Tool Enhancements v2.3 (February 2 2010)

   1.1 MXV Power Designer Property Sheet tab enhancements

   1.2 MXV Object Type prompts
   1.3 MXV Definitions: Copy button
   1.4 Reset Check Model Options
   1.5 Fixed a PowerDesigner Repository Check-in issue
2. Updated MXV documentation
   2.1 A documented MXV Example
   2.2 Free MXV Demo Video
   2.3 Free MXV Example with a 30 day MXV trial license

1. MXV Productivity Tool Enhancements v2.3 (February 2 2010)

Feb 2 2010: Data Management Solutions is pleased to announce the release of MXV Productivity Tools 2.3.

 

MXV has been successfully implemented since 2007 at the New Zealand Ministry of Education under the name of ESL (Education Sector Language).


1.1 MXV Power Designer Property Sheet tab enhancements

BEFORE v2.3:

 

Previously, when editing a MXV model object in PowerDesigner 12.5, one had to navigate across various tabs on that object's property sheet, because a customised tab such as 'MXV NDR' could only display custom properties of that object. Standard PowerDesigner fields could be edited only on the standard PowerDesigner tab. For example,'Name' could be edited on the General tab only.

 

For example, for a View in the CommonAggregateComponentType Library, the user had to know

  • which tabs are relevant/irrelevant for data entry

  • which fields on a tab are relevant/irrelevant for data entry

  • whether fields need to be entered in a certain sequence, so that derived data values are updated and kept correct

 

 

In short, the user had to know and adhere to a number of strict data entry procedures, hopping from one tab to the next, and sometimes back.

 

Since v2.3:

Since February 2010, MXV has been enhanced to take advantage of new PowerDesigner features for custom property sheet tabs.

 

For example:

  • All relevant fields and collections are now clearly visible on a single tab, called MXV NDR (where 'MXV' is customisable)

  • The fields represent also the data entry sequence, from top to bottom.

 

 

This enhancement simplifies data entry, because the model administrator does not need to remember the many object types and their relevant fields and data entry sequences.

 

The eliminated tab hopping saves and errors.

Note: There is presently a software bug in PowerDesigner v15.1:

Symptom 1: A property field is not editable when you expect it to be.

Workaround 1: Locate the particular property field on the standard PowerDesigner (PD) property tab, edit it there, and return to the MXV NDR tab.

 

Symptom 2: A collection matrix does not allow you to add rows, or ends up in empty pop-up windows for selecting an object.

Workaround 2: Locate the particular collection on the standard PD property tab, edit it there, and return to the MXV NDR tab.

Sybase has been informed of this bug and has raised a change request to resolve the issue.

 


1.2 MXV Object Type prompts

BEFORE v2.3:

 

Previously, all Property sheets of a model object type would look identical, even if that object type had multiple sub-types, often with differing data entry needs and sequences.

 

For example, for a complexType in the CommonAggregateComponent Library, the model administrator had to know the required fields and data entry sequence for a View-complexType, which in turn differed from a non-View-complexType.

 

Since v2.3:

 

Since February 2010, MXV has been enhanced to prompt the user at object creation time for the sub-types to create.

 

For example:

When creating a MXV complexType in the CommonAggregateComponent Library, the user defines whether this complexType is going to be a View or a non-View.

 

 

This enhancement allows, after pressing 'Close', displaying the correct MXV NDR property sheet tab, with as many as possible fields pre-populated.

Data entry is simpler, faster and less error-prone.

 

Similar dialogs have been added when creating

  • a View in a Document Schema model to distinguish between Root-Views and non-Root-Views

  • an element nested within a View to distinguish between leaf-elements (BBIE) and branch-elements (ASBIE)


1.3 MXV Definitions: Copy button

BEFORE v2.3:

 

Previously, the administrator had to cascade definitions from the UML model to the XML model by copying and pasting blocks of text.

 

Since v2.3:

 

Where possible, the MXV object property sheet has been enhanced with a 'Copy Definition' button.

 

For example:

 

 

This Copy button saves time and errors by eliminating repeated, onerous sequences of highlight, copy, paste steps.


1.4 Reset Check Model Options

BEFORE v2.3:

 

Occasionally, the model administrator may want to (temporarily) override certain Check Model Settings by deactivating selected model checks.

 

These modified settings are then stored with the affected model.

 

Returning to the original default model check settings has been a tedious and time-consuming exercise.

 

Since v2.3:

 

Each MXV NDR Tool Menu now contains a button for 'Reset Model Check Options':

 

 

This enhancement allows quickly resetting the model check options to the required default, ensuring that the Check Model output is complete and un-filtered.


1.5 Fixed a PowerDesigner Repository Check-in issue

BEFORE v2.3:

 

When running certain MXV Productivity Tools under PowerDesigner 15.1, a issue not known under PowerDesigner 12.5 started to appear:

Model A is copied and saved under a new name as a new model B (i.e. explicitly severing all links of the original model).

 

Under PowerDesigner 12.5, Model B did correctly, upon its first check-in (consolidation) into the repository, create a NEW repository model.

Under PowerDesigner 15.1, Model B does incorrectly, upon its first check-in (consolidation) into the repository,  attempt to UPDATE repository model A.

 

This PowerDesigner software bug affects the MXV tools which create

  • a new UML model version

  • a new XML model version

  • a new document schema model

 

Since v2.3:

 

The affected MXV tools have been modified to work around the described PowerDesigner issue, and now function correctly and identical to previous PowerDesigner 12.5 behaviour when checking in models.

Sybase has been informed of this bug and is investigating the issue.


2. Updated MXV documentation

The following documentation has been updated in light of v2.3:


2.1 A documented MXV Example

The document A practical example: Model-driven Semantic Interoperability using Open Standards and MXV design and Productivity Tools (version 1.5, 1.2 MB pdf) has been updated and reflects the latest 2.3 enhancements.


2.2 Free MXV Demo Video

The free Model-driven XML Vocabulary Design Demo video (90 MB, 60 minutes viewing time, with narration and animations) has been updated and reflects the latest 2.3 enhancements.


2.3 Free MXV Example with a 30 day MXV trial license

The MXV Example download has been updated and reflects the latest 2.3 enhancements. Request your free MXV Example download here.


2.4 MXV Methodology documentation

MXV is defined on a solid foundation, backed with a considerable amount of methodology documentation. Selected documents (SD05 and SD06) have been updated and reflect the latest 2.3 enhancements.


Back to XML Schema & Vocabulary Design

For further information, feel free to contact me.

 


        © Copyright 2011 Data Management Solutions, Wellington, New Zealand                   Last Update: 2011 November 2