Extension d’Enterprise Architect

Oui.

Oui. You can search for "Profile Helpers" in the Enterprise Architect User Guide. The online documentation for this topic is currently unavailable.

Oui you can - there is no need to remodel everything. You will, however, need to make some manual updates to reflect the name change:

• If you have included model patterns in a toolbox profile, these will include the MDG Technology name. So you'll need to update the corresponding toolbox page entries. Simply edit them using the Profile Helper dialog.
• If you change the name of a profile (not the MDG Tech name), you must update the toolbox pages that include stereotypes from that profile - again you may use the Profile Helper dialog to do this. The fully qualified name will appear incorrect until you change it.

Note: The MDG Technology name (ID) is only defined when generating your MDG Technology file and is stored with the MTS file. This is distinct from the name you assign to the top-level package when creating an MDG Technology model using the Profile Helper Model Pattern, which can be any arbitrary name.

Any Shape Scripts that have been defined for stereotypes in the MDG Technology will not be rendered.
Instead, the standard UML presentation for the metaclass will be used.
As soon as the MDG Technology file is referred to, however, the custom Shapes will be drawn as defined by the Shape Script.
To refer to an MDG Technology use the main menu: Settings > MDG Technologies > Advanced > Add Path/URL

Oui it is possible to render an alternate image by defining a Shape Script and using the image() command. You specify the image to be drawn by passing a reference to the imdageId, defined in Enterprise Architect's Image Manager. See the Drawing Methods help topic for further information.

This could form the basis of a future webinar topic.

Currently this option cannot be set as part of a diagram profile, so it is not available in the Profile Helper dialog either. This option will be considered for a future release however.

No, currently this is not possible. You would need to deploy the Learning Center files to Enterprise Architect's installation directory - for example a subfolder of the following location:

C:\Program Files (x86)\Sparx Systems\EA\Books

Note: These files would then not be removed when updating Enterprise Architect to a new version.

Currently, versioning of model scripts is not supported inside Enterprise Architect. They need to be saved to a file first to be version controlled.

Oui. If you create a Model Script based on VBScript you can use the MsgBox command that is built into VBscript.
For example: MsgBox "Hello World"

Alternatively, you can use the Session object to achieve something similar. The Model Script used in the webinar demonstration has such an example at line 64:

Session.Prompt "This script does not support items of this type.", promptOK

There have been some minor enhancements since version 9.3.

The most comprehensive documentation is the User Guide itself. See the "Automation and Scripting" topic, in particular the "Enterprise Architect Object Model" subtopic. You can also access this documentation online.

There are code samples included in the documentation. There are also some complete examples available on our automation interface resources web page. Third-party contributed samples are also available on the Sparx Systems Enterprise Architect Community website.

Enterprise Architect's Model Scripts can be defined using one of the following popular scripting languages: VBScript, JScript and JavaScript. There are numerous third-party resources available for learning these languages. Information specifically relating to Enterprise Architect's Model Scripts is available from the User Guide under the topic: Automation and Scripting > Scripting.

One future possibility would be based on defining and evaluating OCL constraints. While Enterprise Architect supports OCL definitions and validation of OCL syntax, it does not yet evaluate and enforce OCL constraints. So the only feasible approach currently is to use some programming logic to validate models.

Oui. Staff at Sparx Systems make use of this capability and have successfully debugged Model Scripts containing 2,500+ lines of code, operating on large-scale information models.