Model Guardian Framework Editions Download Page

Model Guardian, v6.03 Evaluation Edition is available for download here

The evaluation edition is a fully functioning edition that will work for 45 days. If you purchase a license, you will be able to continue working with profile(s) that you created with th evaluation edition.

v6.03.02

This fixes the trial license for the evaluation edition. It also fixes SQL queries used within MG processing in which the element's name had a single quote in it, e.g. Player's Request.

v6.03

This is a maintenance release.

v6.02 New Features

Nesting Relationships Management

This version adds a new feature that allows you to control the nesting of elements. Sometimes you want to rely on the way you nest elements within the browser with elements nested under another element in a parent/child relationship. Unfortunately, if you happen to place one of the child elements on top of a different element on a diagram the element becomes a child of the element on the diagram and moves under it in the browser. The new Nested Relationship Management menu option under the Modeling Tasks menu item, allows you to automatically add a nesting connector between all of the parent/child pairs in a given package. While doing so, it also fixes any existing nesting relationships that were reversed, i.e. from the parent to the child. A second option allows you to delete the nesting connectors. Now you can always find who the real parent is but looking at an element's nesting link. Soon to come will be the ability to automatically renest any elements that were mistakenly moved out of the hierarchy.

v6.02 Fixes

Install All Users now the default

When installing v6.00 the default was installing just for yourself. If done this way, previous versions are removed. However, in some environments where a different user account from the normal user of the computer, like an administrator or automated process, Model Guardian would not be available to the normal user. The installationn default is once again for all users. If you had previously installed MG for just yourself and choose to install the new version for all users, you may have to run the installation a second time, choosing to repair it.

v6.01

Version 6.01 fixed a couple of problems experienced when using Model Guardian with no profiles were available. We took the opportunity to enhance the file management of the profiles. It is now easier to select, create, import, and delete profiles.

v6.00.06 Maintenance Release

Only Diagram Types for a given role were made available when setting the Diagram Type of a diagram. This makes sense. However, it presents problems when opening diagrams with types not on the User Role's list. v6.00.06 shows all of the Diagram Types. We will try to find a work around for the problem.

v6.00 Major Feature Upgrade

It's been a little while in coming, but this release is filled with several new features. Key among these are:

  • Deployment of your profile to all of your modelers has been automated, insuring they are always using the most update to date version
  • Improved, two-way synchronization between profiles and models
  • Model Guardian's reach has been extended to include managing the use of external profiles, like Sparx's BPMN 2.0 profile, as if they had been built in Model Guardian

To learn more about this new release, download the new features document.

v5.03 Maintenance Release

This version is a maintenance release fixes a program error that occurred when closing Model Guardian when no profile was loaded. It also fixes some minor inconsistencies in the tabs of the editor’s user interface when the element on the tab is null, i.e. no element has been added to the profile yet. All instances of v5.02 should be replaced by v5.03.

v5.02 Maintenance Release

Version 5.02 is a maintenance upgrade for the optional Service Provisioning add-in for Model Guardian.

Note that you do not need to upgrade if you are not using the Service Provisioning add-in and have already downloaded v5.01. The upgrade takes care of some errors that occurred when creating a new service hierarchy. Download the Service Provisioning with Model Guardian (PDF) to learn about this powerful feature for managing a service-based approach to architectural requirements and road mapping.

If you have not downloaded v5.01 yet, then download v5.02 since that is the most recent version with all of the fixes and added features of v5.01.

v5.01 New Features

Users and User Roles

With Version 5.01 you can add Users to your profile and assign them User Roles. When creating a user on the new User Tab, you enter the user’s full name and their Window’s login name. You can then assign one or more roles to the user. When Model Guardian starts up, it gets the user’s Windows login name, looks for a match in the selected profile and, if one is found, assigns the user role. If the user has been given multiple roles, MG will prompt the user to select which role to use for the current modeling session. If MG does not find the user, it asks the user what role she wants to assume, just as in v5.00.

There two user configurable fields available on the Users tab. You can use these to distinguish between users who have the same name. You can set the name of these fields on the MG Configuration form. If you provide no names for the fields, they do not appear on the Users tab. However, if you assign them names, e.g. “Department” and “Date of Hire” they will appear, letting you enter “tie-breaking” information.

UML Type Maintenance

The MG Configuration form now has a Manage UML Types button which brings up a form that lets you add new, update existing, and remove existing UML types.

One reason for adding this is to “future-proof” Model Guardian. If Sparx makes any changes in the UML types, you will be able to adjust accordingly without having to wait for a new version of Model Guardian.

Another reason is that you may not need all of the UML types and would rather have smaller lists of types from which to choose.

Finally, there are some bugs in Enterprise Architect’s API that prevents some of the types from working properly. We are working with Sparx to remedy this. Once fixed, we will send out an update list so that you will be able to add the correct types.

More Consistency within the Viewpoint Rules

Version 5.00 added rules regarding what elements and connector types may appear on the diagrams of a given viewpoint (aka. Diagram Type). The enforcement rules, like Enforce Object Types, add constraints when checking them, while the allow rules, like Allow UML Object Types, remove constraints when checked. This has been changed in v5.01. In all cases, leaving a rule unchecked means that you are granting greater flexibility. Checking it adds constraints. You should check the logic of the rules for each of your Diagram Types after installing v5.01.

Restricted Deletion

You can now prevent users from deleting elements and connectors that are not a creatable tool in at least one of their viewpoints. There are two levels of control for connectors. With level 1, you may delete a connector if either the source or the target element are creatable tools within at least one of your Viewpoints. With level two, you must also have the connector as a creatable tool within a Viewpoint.

You can now prevent users from deleting elements and connectors that are not a creatable tool in at least one of their viewpoints. There are two levels of control for connectors. With level 1, you may delete a connector if either the source or the target element are creatable tools within at least one of your Viewpoints. With level two, you must also have the connector as a creatable tool within a Viewpoint.

Another control over deleting connectors addresses a deficiency in Enterprise Architect’s locking mechanism. You can lock elements but cannot lock connectors. The MG Runtime edition (which is included within the Editor editions) intercepts the OnPreDeleteConnector message from EA and tries to lock the connector’s source element. If it does, it deletes the connector. If it can’t, it will notify you that it was unable to obtain the lock and that the connector was not deleted. Of course, this only applies to users of the MG Runtime. Anyone else will still have carte blanc when deleting connectors.

Program Fixes

Version 5.01 is also a maintenance release that has correct some programming errors in the New Profile process.

 

When Upgrading to v4.xx to v5.xx...

In version 4.xx, you could have any number of Diagram Types using the same Toolbox. This does not really make sense because a Diagram Type with its Toolbox represents a Viewpoint into the model. Change the Toolbox and you really have a different Viewpoint. Consequently, version 5.00, which introduces Viewpoint enforcement, dictates a one to one relationship between Diagram Types and Toolboxes. Each Diagram Type should have its own Toolbox and a Toolbox should belong to only one Diagram Type.

The first time you open a profile with version 5.00, Model Guardian will look for any Toolboxes that are assigned to multiple Diagram Types. If it finds any, it makes copies of the Toolbox and assigns them to the Diagram Types so that, going foward, they each have their own. If it finds a Diagram Type with no Toolbox, it creates one for it.

Please email us at sales@OADSystems.com requesting the login credentials for downloading the files.

 

v5.00 New Features to Better Control the Modeling Environment

This is a major upgrade that includes a number of new features.

Viewpoint Enforcement

Viewpoints have been included in architectural standards since the advent of ISO's Reference Model for Open Distributed Processing (RM-ODP) in the 1990's. They are a staple of the TOGAF architectural framework. Viewpoints are a way of looking at a model for a specific purpose and/or user role. They provide guidance for users and hide parts of the model that are not of concern for the current task or role.

Viewpoints are realized in Enterprise Archtect by Diagram Types. A Diagram Type has an underlying UML type, which indicates the type of task to be done, and a Toolbox, which provides the type of elements and connectors that should be used on the diagram. Model Guardian allows you create user roles and then assign them Viewpoints. However, they were only suggestions. A user could still add elements and connectors not in the Viewpoint's toolbox onto a Viewpoint diagram.

v5.00 takes this to the next level. It allows you to control what element and connector types can appear on a Viewpoint's diagrams. It also allows you to control what element and connector types can be created on a Viewpoint's diagram.

  • If a user tries to drag an existing non-Viewpoint element onto a Viewpoint diagram, it will be blocked.
  • If the user tries to create a non-Viewpoint element or connector on a Viewpoint diagram, it will be blocked.
  • If the user tries to create a non-Viewpoint connector on a Viewpoint's diagram, it will be blocked.

You can set each Viewpoint to ignore the constraints, allow overriding the constraints, or strictly enforcing the constraints.

Extended Profile Viewer

The left side of the Profile Editor's window has a hierarchical view into the Metamodel. In version 5, there is now a Profile Viewer with three different views into the profile, the Metamodel, the Viewpoint Types, and the Viewpoint Hierarchy. There are three corresponding radio buttons at the top of the Viewer that you use to select the view.

Improved Profile Deployment

Deploying your Model Guardian profiles is now easier than ever. You can copy them to any folder on each user's computer or on a shared drive. You do not need the Model Guardian folder structure as with previous versions. You then set the deployment folder's location within each user's Model Guardian Configuration panel. As an alternative, you can create a configuration file with the deployment folder set and copy it to the Model Guardian folder structure on each user's computer.

Profile Support Notice

You can now provide a web addresss and an email address for support of your profile. They will appear on the Help | About Model Guardian window.

Notice Direction

The new Viewpoint violation notices have some options on the Model Guardian Configuration page and on the popup message box. You can use the configuration page to indicate whether informative messages should be presented in a popup message box or in the System Output tab in Enterprise Architect. Using the former provides a more visible style of feedback, while the latter provides a less intrusive style.

When the new stype message box does popup, you have the option to not show that notice again during the current modeling session. If you popup asks for a user response, you have the option to alwasy use that response for the current modeling session.

 

Model Guardian, v4.06

v4.06 New Forms Manager Implemented

Color maps now include Connectors. You already could set the colors to be displayed for each element's background depending on the assigned tagged value. You can now set the color of the connectors according to their tagged value.

One of the key convenience features of Model Guardian is the floating forms. They let you keep certain MG windows on top of Enterprise Architect. This lets you switch back and forth between MG and EA without losing the context of your thoughts . However, there are occasions when a dialog would open under one of the floating forms and you would not be able to see or respond to it. We have designed a forms manager that coordinates all of the MG windows to prevent this from happening. Please note that, since they are in separate DLLs, the coordination does not occur between Model Guardian and the MG Utilities when they are both open. If it seems like the system has locked up, go to your Windows task bar and look for an extra window listed on the Enterprise Architect button. You can close the dialog from there and then move the floating forms or de-select 'Keep on Top' and then reopen the dialog.

Another enhancement is that a sample Service Hierarchy is now installed in the EA2 framework's WIP folder. It is used with the Service Provisioning feature and the sample model.

v4.05 Maintenance Release

Fixes the bug in which the source and object types for relationships were not being saved. Fixes a bug that caused the Model Guardian editor to drop behind Enterprise Architect after being selected from the EA menu.

v4.04 Maintenance Release

Addresses a reported bug when running the "Help | About Model Guardian" window.

v4.03 Maintenance Release

Fixes a bug due to the changing nature of tagged values in Enterprise Architect

v4.02 Maintenance Release

Fixes a bug in the Relationships tab.

v4.01 Maintenance Release

v4.01 fixes two bugs.

  • v4.00 did not use the relationship inheritance feature with the Quicklinker when dragging the Quicklink to empty space. v4.01 now shows all of the child elements of the end-point elements defined in the relationship.
  • v.400 did not properly handle the Connector Type feature in which you select the direction of the connector's arrow. This works as expected in v4.01.

Known Bugs and Work Arounds

There are times when the Model Guardian profile editor window stops accepting keyboard input. There are two ways to get around this.

  • Click on Enterprise Architect to give it the focus. Save the current diagram, if appropriate, and then reload it. Go back to Model Guardian. It should now accept keyboard input.
  • If the first action does not fix the problem, save your work in Enterprise Architect, close it and then restart it.

v4.00 New Edition Release

v4.00 provides some bug fixes, a new edition and reduced pricing. The Custom Framework Editor (CFE) is now known as the MG Profile Generator. It includes all of the features of the CFE edition. You may download and install if for free if you are on a current service contract. If you are using the CFE but are no longer on a service contract, you may purchase the latest version for a reduced price. Contact us for details.

v4.00 now offers the EA Profile Generator edition. This edition includes all of the CFE profile editing features that can be used by directly by Enterprise Architect without the MG Runtime edition. You can generate native Enteprise Architect MDG XML files and distribute them for free to any user of Enterprise Architect. You may also purchase a combined edition that will generate both the EA XML profiles as well as the MG extended profiles for the Runtime editions. This lets you distribute your profile to everyone and give the MG extended profile to those who need to leverage the extra modeling power provided by the MG Runtime edition.

v3.07 Maintenance Release

v3.06 had a bug that caused the following error message to appear during startup: "Unable to initialize Model Guardian. Cannot access a disposed object. Object name: 'SelectFrameworkForm'." v3.07 has fixed this.

A new error has been introduced with Enterprise Architect v11 which does not occur with previous versions of EA.. When opening the Framework Editor from the Enterprise Architect Extensions menu, the Framework Editor opens and then immediately disappears behind Enterprise Architect. You can bring it to the front by clicking on EA in the Windows taskbar or by tabbing through the open windows. Checking the "Keep on Top" box on the Framework Editor will eliminate this annoyance.

New Feature in Version and Bug Fix in 3.06

Version 3.06 adds the ability to set the font color for color maps as well as the background color. It also fixes the problem of the "List Diagrams by Role and Type" menu item in the Framework Editor not working.

New Feature in Version 3.05

Version 3.05 adds a color map feature. When you create a Tag Definition that has an enumerated list of values, you can choose to assign colors to each value. You can then apply the color map to diagrams that have elements with the tagged value assigned to them. This allows you to create heat maps according to elements' status. We refer to these as color maps rather than heat maps because you can create as many color mapped Tag Definitions as you want for whatever purpose. There is a menu option to apply color maps to a diagram and one to turn off the color map, returning the elements to their default colors. You can learn more about this by clicking the "Help" button on the Tag Definitions tab of the Framework Editor in Model Guardian.

New Features in Version 3.04

Version 3.04 introduces user roles and their viewpoints. Each user role has a different set of concerns that should be presented by the appropriate viewpoints into the model. A viewpoint is represented in Enterprise Architect as a diagram type and its associated toolbox. Model Guardian now allows you to set up user roles and the diagram types for each role. When a user starts Enterprise Architect with a Model Guardian framework that has defined user roles, the user is asked to select the role he/she wants to assume for the modeling session. Then, when selecting a diagram type or picking a toolbox, only those germane to the user's role are shown. This greatly reduces the confusing clutter of options open to a user and helps them to focus on their tasks.

In addition to the user roles, v3.04 also adds the ability to search for diagrams of the diagram types defined for a given user role. This yields a hierarchical list of user roles. Under each user role are the diagram types for that role. Under each diagram type is a list of the diagrams in the model of that type.

New Features in Version 3.03

Date validation has been added to the (EA)2 service provisioning features. Each date's format is validated and, depending on your configuration setting (Ignore, Warn, Enforce), invalid formatted dates will be accepted, warned against, or required to be fixed. The date logic of Lifecycle dates (Planned Begin Date, Planned End Date, Actual Begin Date, Actual End Date) is validated to ensure you do not enter, for example, a Planned End Date that occurs before the Actual Begin Date. Again, this the validation level can be set to ignore, warn, or enforce.

New Features in Version 3.02

Deployment Maps have been added to easily highlight inconsistencies in your deployment (roadmap) plans. They apply to diagrams that have Configuration Items and Lifecycle Connectors. A Configuration Item is an element that the four lifecycle date tagged values (Planned Begin Date, Planned End Date, Actual Begin Date, Actual End Date). A Lifecycle Connector is a connector with the four dates.
When applying a Deployment Map style to a diagram, you provide a date range during which you want each of the Configuration Items and Lifecycle Connectors to be active. If the diagram has a Roadmap Phase element on it, the date range will automatically be picked up from the Roadmap Phase. Each Configuration Item is given an appropriate color depending on whether it is active during the time period, is deployed after the period begins, or is retired before the period ends. Each Lifecycle Connector is given an appropriate color depending on whether the Connector's dates align with the dates of the target element, i.e. the service provider.

New Features in Version 3.00

New Licensing

We have updated the software licensing with version 3.00. Therefore, you will need a new serial number and activation code when running v3.00. Please contact us at support@OADSystems.com if you have not already received your new codes.

Notes:

  • All editions are delivered in the same installation package. The active version depends on the license you have purchased. You may select which edition to run during the evaluation period. Model Guardian will run in evaluation mode for 45 days, after which you will need to purchase a license for continued use. See the Ordering page for details.
  • The SQL views are not available in the Model Guardian Framework editions during evaluation mode.
  • The Model Guardian Framework editions include the (EA)2 Enterprise Architecture Modeling Framework.

Model Compliance

This version includes the new move into model compliance. You can establish rules and check the model for compliance to the rules. The initial set of rules include...

  • Connector cardinalities - The compliance dialog will check all model connectors with a framework type to verify that the connectors have the cardinality ranges defined in the framework. You can click through to the offending connectors in EA to make the necessary changes.
  • Element and connector tag cardinalities - You can indicate how many of a given tag an element or connector may have. You can also indicate whether the tag must have a non-blank value. The compliance dialog will check all model element and connector tags for violations. You can click through to the offending elements or connectors in EA to make the necessary changes.
  • Non-framework tagged values - The compliance dialog will list all model element or connector tags that are defined in the framework and those that are not defined in the framework. You can click through to the offending elements or connectors in EA to make the necessary changes.

We are developing additional rules that will be included in versin 3.01 shortly. Let us know what rules you would like to have included by sending us an email at support@OADSystems.com.

Fixed Bugs

Version 3.03

When creating Relationships on Metatypes that had more than one level of child Metatypes, the extended Metatypes did not receive the Quicklink definition.

Version 3.02

It allows Connector Type cardinalities to remain blank rather than defaulting to "0..*". It also provides all tags for compliancing checking rather than just those for the concrete metattypes.

Version 3.01

Fixed problems when first creating a new framework.

Version 3.00

Fixed a problem that prevented the EA2 framework's WIP folder from being created during installation.

Known Issues

Installation Problem Preventing the (EA)2 Framework from Loading - Resolved in version 3.00

Creating Instances in Enterprise Architect Version 10

In versions of Enterprise Architect 9 and earlier, you could create a framework classifier one UML type and give its instances a different UML type. For example, in the (EA)2 framework, a Server Model was given a type of Class and Server, a Server Model's instance, was given a type of Node. Version 10 does not support the disparity between the types.

If you have created frameworks with disparate types and have used them in models, you simply need to make the UML type for the classifier and the instance the same and then synchronize your models.

Changing a Diagram Type

If you change the name of a Diagram Type, that change does not get reflected for diagrams in existing models when updating the models. Converting models from the (EA)2 format has the same problem. Sparx has decided not to address this problem. You will have to manually change the diagram type for each diagram. This can be done by following the steps below. Note that this problem only relates to existing diagrams.

  1. Open the diagram in EA.
  2. Clicked 'Diagram | Advanced | Changed Type...' menu options.
  3. Click on 'EA2 Diagram Types' on the left and then select the desired diagram type on the right.

If you are running on SQL Server, you can use the following update statement in the SQL Server Management Studio to update the diagram types from your previous (EA)2 models:

update t_diagram
set StyleEx =
SUBSTRING(CAST(StyleEx as nvarchar(MAX)), 0, CharIndex('MDGDgm=EA2 Diagram Types::EA2 ', CAST(StyleEx as nvarchar(MAX))) + 26) + SUBSTRING(CAST(StyleEx as nvarchar(MAX)),CharIndex('MDGDgm=EA2 Diagram Types::EA2 ', CAST(StyleEx as nvarchar(MAX)))+30,Len(CAST(StyleEx as nvarchar(MAX))) - CharIndex('MDGDgm=EA2 Diagram Types::EA2 ', CAST(StyleEx as nvarchar(MAX)))+1)
where CharIndex('MDGDgm=EA2 Diagram Types::EA2 ', CAST(StyleEx as nvarchar(MAX))) > 0

AS ALWAYS, YOU SHOULD BACKUP YOUR DATABASE BEFORE APPLYING THESE CHANGES.