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 ... 11
General Board / Types of relationships allowed between elements
« on: October 30, 2017, 10:36:19 pm »
Sparx EA (v 13) only allows certain types of relationships to be drawn between elements for certain types of (UML) diagrams. For instance, I have a structural diagram and cannot draw an association, I can only draw dependencies, traces and information flows. Could somebody please point me in the direction of which relationships are allowed for which diagrams?

General Board / Re: Filtering Matrices
« on: October 03, 2017, 02:12:26 am »
Note the source of the row or columns of the matrix could be a selected package or a search. If you select a search, you can specify the search filter using the parameters you want, as the stereotype and any other.
That's the route we've taken.

We've found we use a lot of TVs to enable us to control which items appear on which matrix.

Thanks Arquesoft and Paolo. Will give a try.

Paolo - what do you mean with TVs.

General Board / Filtering Matrices
« on: September 29, 2017, 11:20:04 pm »
Matrices can be filtered by (element) Type -  e.g., Actor, Class, Component and so on - but is there a way to also filter the contents of a matrix by stereotype. To give some context to the question, the stereotypes I have in mind are extensions of the base classes using a UML profile.

In a nutshell we are ending up with matrices with too much superfluous data, if we could filter by stereotype they will just have the relevant data.

General Board / Re: Shape script on profile
« on: September 28, 2017, 11:42:45 pm »
Interesting this appears to fix the problem without upgrading - same idea different coding.

Just 3 additional questions:

1) is there anyway I can make the fonts of "stereotypecompartment" and "namecompartment" different and independent/
2) can I set the fill color of "stereotypecompartment" to mid-gray?
3) how I increase the line width of the enclosing rectangle?

Code: [Select]
shape main{


addSubshape("stereotypecompartment", 50, 50);

addSubshape("namecompartment", 100, 100);

shape stereotypecompartment
h_align = "left";
v_align = "top";

editablefield = "stereotype";




shape namecompartment
h_align = "center";

editablefield = "name";



General Board / Re: Shape script on profile
« on: September 28, 2017, 10:48:25 pm »
I tried with 1351.

Thanks, I will check if an upgrade fixes the problem.

General Board / Re: Shape script on profile
« on: September 28, 2017, 10:33:45 pm »
I could not reproduce either of the effects you see.

Which version of EA are you running?

General Board / Shape script on profile
« on: September 28, 2017, 09:19:41 pm »
I have created a profile with a number of extensions to base classes. I have attached the shape script below to one of the stereotypes extending the base class. The script draws the right geometry but the connectors look odd. There are 2 problems:

1) one end of the connector, the bottom end, is a few pixels inside the rectangle
2) if I change the stereotype of an element in the diagram to the stereotype with the same scripts, a significant amount of white space appears between the bottom of the shape and the end of the connectors

Have I missed anything? (Sparx EA version is 13.0.1310 Build 1310).

Code: [Select]
shape main{


addSubshape("stereotypecompartment", 100, 20);

addSubshape("namecompartment", 100, 20);

shape stereotypecompartment
h_align = "right";

editablefield = "stereotype";




shape namecompartment
h_align = "center";

editablefield = "name";



General Board / Re: Diagram elements showing a red A
« on: September 21, 2017, 01:47:31 am »
Thanks qwerty, this is indeed the answer.

General Board / Diagram elements showing a red A
« on: September 20, 2017, 11:45:13 pm »
I have a diagram with some elements, but not all, showing a red A in the bottom right corner. Could somebody please remind me what this means and how to get rid of it?

Being formally correct often pays off. And it prevents from getting in situations like the here mentioned. However, being holier than the Pope does not seem to make sense either. I got so much used to be Sparxian, I could beat myself for doing so many stupid things...

We probably all do many stupid things with Sparx and without ...

I have now 3 profiles, including 1 for toolboxes and another for diagram extensions, and have hit the 1st problem I cannot seem to solve, once the profile is imported I cannot stereotype diagrams. I can stereotype anything else, classes, relationships and packages but not diagrams. Am I missing something?

Thanks Uffe, thanks qwerty.

That aggregation is probably my fault. My sample model still has the aggregation as a consequence of transforming the profile from a meta model and not removing the aggregation information. Since EA doesn't care, I simply did not alter that. Also for the extends, it looks as if the sample has been broken at some time, somehow. The book uses the solid triangle extends and that had been made using the sample model. Well, shit happens. I'll make a correction.


P.S. I have uploaded a model with according annotations.
The aggregation is indeed qwerty's fault but I am not going to blame him for that  ;) It also provides me with a nice excuse to slightly redirect the conversation.

This way to "develop" a meta model works well; on version 13 works better than in any previous versions. However, it is very "sparxian" because it works with stereotypes and using aggregations between stereotypes could be a bit of a heresy. Of course, if I was going to this on a non-sparxian way, as I have done before, I will use proper UML class diagrams to do this and aggregations could play a role on this; the difficulty/effort is in converting them to the sparxian way of developing meta models.

P.S. You could download the sample MDG from the book once again. Some constructs might give you the kick in the right direction.
The 1st thing I did is to download the sample MDG  :), it was a good refresher as I don't develop meta models very often.

1) I compared V12/13 and found both extends relations to appear the same way.
On the sample MDG extension is handled with an Association with a <<extends>> stereotype, while in version 13 it is handled through an Extension with no stereotype, hence the question. i know this slightly pedantic.

4) Without having verified this would be my guess that the Package meta type is just for that purpose.
I will give it a try and report the findings.

I noticed 2 options under Technology/Publish that look interesting: Technology/Publish/Publish Diagram as Pattern and Technology/Publish/Package as UML Profile. Any comments on what they do and if they are new will be much appreciated.
They have been there forever; just the names have changed. (Previously Save Diagram as UML Pattern and Save Package as UML Profile, from memory).
They might have been there forever but the ribbon makes them much more visible than before.

Thanks I will get the service desk to install this.

I have gone through both your book and article before and I am just reacquainting myself with it. Just a number of observations I would like to note, not sure if this has anything to do with the fact that I am using version 13, instead of 11 or 12:

1) The Extend relationship seems to have changed to a line ending into a black triangle, I am assuming this is the correct relationship
2) I am having some difficulty relating 2 stereotypes via an aggregation
3) EA no longer has a Diagram_Class metaclass, what has taken its place, the DiagramFrame metaclass
4) Could somebody please remind me if the Package metaclass could be used to extend the types of packages that can be created inside a model?

Just an update on this, the answer to 3) appears to be the Diagram_Logical metaclass which is added to the profile when using Add Diagram Extension helper

It appears the answer to 2) is to link 2 stereotypes with any other relationship and change the type to an Aggregation. This is very sparxian, is there a better way of doing this.

Thanks qwerty, I will try to see if we can move MySQL forward; at some point I also thought about PostgreSQL.

Regarding the meta model, I have no problem starting one from scratch as I have a good idea of what I want to achieve. Are there any changes to the way you create a meta model in v13. I noticed 2 options under Technology/Publish that look interesting: Technology/Publish/Publish Diagram as Pattern and Technology/Publish/Package as UML Profile. Any comments on what they do and if they are new will be much appreciated.

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