Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Modesto Vega

Pages: 1 2 3 [4] 5 6 ... 11
I don't think any of your "conclusions" is correct ???

Geert - generally you are very helfulp except when you choose to use telegraph code or speak Sparkinglish. Which you have been doing in this thread for a while. It will be good if you used more words.

So far I have not managed to produce an MDG containing any profiles used on any of the packages in the project.

It will be a good starting point of if you could provide a step-by-step guide on how to generate an MDG that contains the profiles used in the packages contained within a root node. And please don't tell me again to follow the online help because I have and is rubish.

Just to summarise the contents of this thread so far:

1) Generating an MDG techology file from an existing model will not include the existing profiles associated with the various packages within a project or any customisation to any of the profiles associated with the packages

[Question: If the above is correct, what is the point of Generating an MDG technology file from an existing project]

2) The only profile which can customised is the UML profile

3) The only way to customise the UML profile is by using steretypes and associating them with metaclasses as described in

4) Other profiles, such as database profiles, cannot be customised

5) Once a profile has been customised there is no easy way to apply it to an existing model.

I am not exactly getting stuck, just getting confused.

I have the folllowing structure:

Root Node - ABC
--------------------Package - ABC1
--------------------Package - ABC2
--------------------Package - ABC3

Package ABC1 uses UML2, classes and activities, where I have added custom stereotypes, using Project\Settings\UML Types

Package ABC2 uses UML2, mainly components

Package ABC3 contains mainly database models, currently all Oracle

When I run the MDG creation on the root node and go through all screens, the reuslting MDG profile is essentially empty, except for the name version and description. With empty I mean it does not contain any metaclasses, it does not contain any of the custom stereotypes on ABC1, it also does not contain anything related to the Oracle pattern.

Perhaps, I am missing something but I was empty the MDG Creation to do something similar to reverse engineering my packages and construct something I can use to extend the metamodel. I am probably wrong but have no idea where I missed a step.


Yes Geert, I know about this link and I have followed the steps in Looking at the ouput, the problem must be that the wizard does let me select any Profiles, Patterns or Diagrams.

You can to check the box next to the MDG technology "MDG Technology Builder" to make it active.
That MDG technology contains toolboxes and helpers to create MDG technologies.

It is enabled and active. What next, where can I find the helpers and toolboxes?

Extensions|MDG Technologies and then check the technology called "MDG Technology Builder"

Version 1.

I cam even see the MDG I want to generate, it says location: Model.

You are missing the MDG Technology Builder MDG technology.

What do you exactly mean? I am using a Coporate edition and have an option under Tools called Generate MDG Technology File which does virtually nothing, of course I might have forgotten how to use it.

2) 3) you can extend existing profiles. See, you cannot change existing profiles.
Somehow I sense this is not as straight forward as it may sound. The help in the above link reads:
In the Project Browser, locate the Package with the <<profile>> Stereotype and open its child diagram.

If you do not have an existing <<profile>> Package, use the 'MDG Technology Builder' option in the Model Wizard to create a new technology, then open the diagram from the newly created <<profile>> Package.
But I, of course, cannot see a 'MDG Technology Builder' on my Model Wizard. What am I missing here?

Thanks to all for the replies.
I suspect "here be dragons". 

I'm not sure we're necessarily understanding what the OP is asking.

But, assuming it's:  "I've created my own MDG and I want to apply it to an existing repository", I suspect q's point about dragging and dropping the new element type over the old element type MANUALLY is the best option as (hopefully) Sparx have (behind the scene) executed the use cases involved.

Trying to do it via scripts (especially if you're not familiar with EA's internals) could e a recipe for disaster.  Making sure "all the i's are crossed and t's dotted" :) is not trivial.  It's not rocket science, but not trivial.

We are evolving multiple MDGs into one while the repository is "in flight" and it's doable, but there's a lot of "balls to keep in the air".  We have nearly 80,000 items so, manual is not possible.

- There is an EA meta model
- The meta model has not been exported to an MDG because it is not complete, I will rather include changes to existing profiles
- Points 1, 2, and 3 on my OP refer to the creation of the meta model
- Point 4 applies to applying an evolving meta model, possibly using an MDG, to an exisitng "in flight" repository. Doing this manually is not very realistic becuase of the number of elements in the repository

I am developing a meta model and would like to apply it to an existing model. I would appreciate some advice tegarding the following;

1) How do I apply the meta model to an existing project?
2) How can I include existing profiles into the meta model (aka Database Engineering)?
3) How do I customise existing profiles (aka Database Engineering)?
4) How can I get this done iteratively? I have version 0.5 of the meta model but I strongly suspect that quite a number of elements will be added to the meta model overtime?

The project is stored in a SQL Server database repository.

General Board / Re: Class without relationships
« on: March 19, 2016, 03:53:30 am »
There isn't really a script that does what you need, but I have open sourced all of my scripts here:

Also look at the EAScriptLib MDG technology and the samples provided by Sparx.

Thanks Geert very useful.

General Board / Has EA 12.0.1215 has trouble printing A2 to PDF?
« on: March 10, 2016, 03:53:28 am »
Does anybody know if EA 12.0.1215 has trouble printing A2 to PDF? A3 works fine what when printing an A2 to PDF EA does not print the full connector lines, it whites out part of the connectors.

General Board / Re: Class without relationships
« on: March 10, 2016, 02:21:09 am »
Not OOTB, but you could of course write a little script to do that.

Or a query which looks for elements in t_object which have count 0 for their object_id in either end of t_connector.


P.S. Try
Code: [Select]
SELECT * from t_object o WHERE (select count(c.Start_Object_ID) from t_connector c where c.Start_Object_ID = o.Object_ID) = 0 AND (select count(c.End_Object_ID) from t_connector c where c.End_Object_ID = o.Object_ID) = 0You might wish to reduce to certain object types.
Thanks to both, where can I find an example of how to do this with a script?

General Board / Class without relationships
« on: March 05, 2016, 01:48:25 am »
Is there a way to automatically higlight (change its colour) classes in diagram without relationships to any other classes?

General Board / Re: Baselines
« on: March 02, 2016, 01:10:32 am »
But a view people unfortunately are forced to be interested in the past as well.

We baseline some well-defined higher level packages (requirements package, architecture package,…). Those packages can have deep package levels underneath but element references (classifiers, associations,..) are only allowed to a defined set of other “higher level packages.
The baselines are used to prove what state of the packaged was e.g. verified and to analyze what has changed, because we have to provide change details, once a product is shipped (safety related stuff).

Another use case is to baseline “the View Package” where all our stuff of a certain system level is in. This is because we have “another View Package” where shared model stuff is in (some kind of read only Library).
Before we update to a new Library version, we baseline “the view Package” and the current “another View Package (LIB)” (just to be able to go back in case of disaster), afterwards we switch to the new Library Version and then we restore the baseline of “the view Package” we created shortly before. By doing so, associations added from our model to the old library version will be kept (hopefully in any future version of EA).

Thanks Peter I will explore and feedback on this thread.

Pages: 1 2 3 [4] 5 6 ... 11