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 - Paolo F Cantoni

Pages: [1] 2 3 ... 415
How can we surface the scenarios (for an element) onto a diagram?  I was expecting a compartment (similar to Requirements and Constraints) but no such luck.

We can use a Linked Note, but this is quite cumbersome and is not directly attached to the element.


That's probably not an EA bug, I guess?

I DID send in a defect that the final compress should be part of the project transfer functionality, but I guess that was fixed in a different timeline (binge-watching Continuum on Netflix).


General Board / Re: Empty tags of a class not shown in diagram
« on: September 20, 2018, 09:41:22 am »
Instances of the type.

Where 5 is an instance of int, "" or "value" are instances of string.
So just to be clear...
Technically, when you apply a stereotype to an element, you create an instance of that stereotype, which references the target element (a property). The tag is a slot referencing the property for that element, and the tagged value is zero or more instances of the property type.

Have I got it right now?

Hey Rich,

After you transfer the project, you need to compact the file.  This will reset the internal counters (MSA's equivalent of sequences).  What's happening is that the counters haven't been updated to show the last record added to the DB, so when you add a new record, there's already a record with that ID.


General Board / Re: Empty tags of a class not shown in diagram
« on: September 19, 2018, 04:20:12 pm »
By here I meant on this forum. If I remember correctly, with the two of us taking slightly different sides.

Yes, tagged values haven't been officially called that since UML 2.0 was released. However, it's still an easier term to use.

Technically, when you apply a stereotype to an element, you create an instance of that stereotype, which references the target element. The tag is a slot referencing the property, and the tagged value is zero or more of the type for the property.
By here I meant at my workplace...  ;)  The discussion being amongst an "Argument" of Architects.

BTW: did you mean: "and the tagged value is zero or more of the value(s) for the property."  If not what's the difference?


General Board / Re: Empty tags of a class not shown in diagram
« on: September 19, 2018, 09:46:25 am »
It was an intentional change. Probably to clear some unnecessary clutter since there is no value there. (Although we have had some discussions here about whether an empty string is a value)

nterestingly, we also had the same discussion.
The UML v2.5 specification has exactly 3 occurrences of the term "Tagged Value".

It says...
Just like a Class, a Stereotype may have Properties, which have traditionally been referred to as Tag Definitions. When a Stereotype is applied to a model element, the values of the Properties have traditionally been referred to as tagged values.

So, the things are actually Tags, the Tag Definitions define which values are possible against which Stereotypes.  If the Tag has a value, then that value is known as a Tagged Value.  However, it doesn't seem to preclude a Tag existing, but not having a value.

It seems to me that we've got the terminology wrong (myself included) when we talk about the tag as the tagged value.


General Board / Re: Disable the abilty to Manage Add-Ins
« on: September 19, 2018, 09:33:27 am »
[SNIP] (it certainly wouldn't stop me  ;D).
Yes, but you're Belgian - and not to be trusted!   ;) ;D

PS: Almost as bad as the French!

PPS: This is an attempt at Aussie inter-mate humour (see the icon).  It may fail...

Bugs and Issues / Re: Bizarre bug in QuickLinker!
« on: September 18, 2018, 07:01:34 pm »
Thanks, Simon,

Food for thought!


Bugs and Issues / Re: Bizarre bug in QuickLinker!
« on: September 17, 2018, 12:52:49 pm »
It's completely new and doesn't generate anything that earlier versions know to look for.

In terms of backwards compatibility, it will override an existing QuickLinker table if one exists. (If you have a metamodel only stereotypes not mentioned in the metamodel will be taken from the QuickLinker table.) So your technology can include both.
Thanks, Simon, for the clarification.

As I now understand what you've said, we can continue to generate the v13 QuickLinker section and overlay it with the V14 QuickLinker and distribute the one MDG until all our users have converted to v14.  Is that correct?  I am assuming that the new QuickLinker is in a new section.


Bugs and Issues / Re: Bizarre bug in QuickLinker!
« on: September 17, 2018, 09:44:34 am »
I'm not astonished that Sparx still sticks to that dinosaur format for the QL. However, I wonder why people don't really insist on something more handy that really seem to use it. Go kick their butt. Or the trainer's to send a "feature" request which requires improving (actually I mean replacing) it.

Q, in fact, they did. In v14 you can now model metamodel constraints to control the quicklinker.
A big improvement over the old quicklinker CSV definition.

I did notice however that the new method is not backwards compatible. No quicklinker in v12.1 when defined via meta model in v14.

Hi Geert,
As I mentioned elsewhere, we're looking to move to the v14 mechanism once we get some time.  We first have to manually reverse engineer our bespoke, handcrafted, MDG.  However, I am now concerned that we will lose backwards compatibility (we're not anticipating moving the users to v14 soon).  Does the v14 method still create the QuickLinker element (to be placed into the MDG file)?  Is it a formatting or a structural problem?


... (there are lots of shit architects out there that cause scepticism in business users).
"in titulo, ergo sum" (with apologies to Rene)  (I am thus titled, therefore I must be)

Happy Friday everybody!


Bugs and Issues / Re: Bizarre bug in QuickLinker!
« on: September 13, 2018, 04:29:40 pm »
You have two choices now ... drink the bottle labelled "DRINK ME" or eat the cake labelled "EAT ME"
I have a litre bottle of Dalwhinnie 15yo Single Malt witing for me...


Bugs and Issues / Do Package entries work in QuickLinker?
« on: September 13, 2018, 02:14:41 pm »
We wish to create QuickLinker entries for Packages (similar to the


), but they don't seem to work. 

If we stereotype the packages and create the appropriate QuickLinker entry e.g.

The entries work.  Smells like a defect to me...


Bugs and Issues / Bizarre bug in QuickLinker!
« on: September 13, 2018, 01:52:22 pm »
In investigating the use of @Element in the QuickLinker, we accidentally discovered (after many hours tracking) a bizarre bug!

You can comment out a line in the QuickLinker by the use of a leading //

So far so good!  We generate the VAST bulk of our QuickLinker file via an automated process and we sprinkle some comments to help break the extremely large file up into sections - such as:

//,//XSD Simple Type,·,//XSD Simple Type,·,·,·,·,·,·,·,·,·,·,·,·,·,·,,,,,

Notice the use of multiple // in the same line!  We've had NO problems with these since we started automating.

We had an entry in the manually managed section of the QuickLinker file concerning @Element:
 //Doesn't Work!   Source Element type needs to be concrete!
We placed this at the start of the section where we were manually managing the concrete source types such as Activity,,@Element,,,@Element,,Nesting,Nstng,to,nesting¯,nesting¯,True,True,True,True,Nesting,0,,,,,


To remind us of the issue.

We had the concrete sources working, and then added the comment.  Sometime later, we found the sources weren't working anymore - although AS USUAL there was NO indication that there was a problem.
After many hours of debugging we tracked it down to:
 //Doesn't Work!   Source Element type needs to be concrete!
(on the same line)
Will KILL any following lines in the QuickLinker file, whereas

//Doesn't Work!   Source Element type needs to be concrete!
(on separate lines)

Doesn't!  How Bizarre!!!


No, you can't change the metatypes in a profile.

My only recommendation is to use a template package.
The profile only deals with stereotypes (that's why they're in the <Stereotype></Stereotype> section.  ;)).  But more seriously, the element that you are placing on the diagram and into the model is a null stereotyped instance of the metaclass (not the metaclass).

You're therefore caught in a Catch-22.  You can't define a null stereotype, because the metaclass isn't specified until after the stereotype is identified in the MDG.  IIRC you can't specify multiple entries with the same stereotype.

As Simon says, you have to use a template package to create a null stereotyped holotype therein to specify how to render it.

A million years ago, I asked for the facility to create null stereotyped shapescripts, but to no avail.  It would require a DB change (at least) to change the primary key for t_stereotypes to allow null stereotypes.


Pages: [1] 2 3 ... 415