Diagram Verification and Status - need something like TaggedValues

[Gayle]

I'm using EA V12 build 1230 and VB scripts to mark verification of packages, connectors and elements using TaggedValues.  For these items, I created a Tag that I use to enter the verification date (I also created some other custom tags to help track status of the items beyond the available information).  I can use my scripts to add, report and delete the tags.  I was hoping for something similar for diagrams, but I cannot find anything similar that I can use to mark when each diagram has been verified.

Is there any way to create TaggedValues or some maybe a custom property field that can be applied to a diagram and made visible when scripts access the diagram properties?  If not within EA12, but EA13, I'm working on that migration, so if there is something new I can use, I'm willing to speed up the migration.

Any ideas will be appreciated.

Thank you, Gayle

[qwerty]

You could use a stereotype (awkward, somehow).

Or a text element which also could be a visible indicator on the diagram itself.

Or further you can use Hand Drawn as unverified.

And as a very fishy approach you can misuse the Style and place something of your own in there. At the risk that EA will swallow or use it on its own in later editions.

q.

[Gayle]

Thank you for the ideas.  Stereotype might work - the model does not currently have any diagrams stereotyped.  I'm trying to avoid using anything that will physically show up on any diagram - the model is the deliverable to my customer (as HTML) and if we start putting notes on the face of diagrams, they will not understand and will question what we are doing.

I could possibly use the diagram notes field, however, some of the diagrams have descriptions in the notes field and the plan was to add descriptions to all diagrams using that field.

I could not find "style" associated with diagrams in the user manual.

Gayle

[qwerty]

The Style would only be available by scripting (or an add-in). The proposed use is a bit fishy, as said...

q.

[KP]

Another approach is to have each diagram owned by a composite element and to add tagged values to the owning element. That's how we implemented BPMN diagrams, for example.

[Paolo F Cantoni]

We insist that every diagram has a Title Block element (Diagram Note element) we use that element as a proxy for the diagram and attach all properties that cannot be attached to the diagram itself (since they are third class citizens on the Sparx universe) to that item instead.

HTH,
Paolo

[Gayle]

The composite elements or title blocks might work for me. 

For composite elements, do you have any suggestions on which type of elements to use?

For the title block idea, what kind of elements are you using to create them?

Gayle

[Paolo F Cantoni]

Hi Gayle,

As I said, the Title Block is the Diagram Note element - which is NOT the diagram note (hence why I Label it "Title Block"), but that's EAUI.  You'll find it on one of the diagram related toolbars and in the Common section of the toolbox.


HTH,
Paolo

[Edit: in the Help it apparently is called the Diagram Properties Note, but not on the toolbars and status bars. Consistency, Consistency, Consistency! ^TM]

[Gayle]

Thank you.  The "title block" is the element I thought it was.  I now see how a tag can be applied to it.

Gayle

[Glassboy]

We insist that every diagram has a Title Block element (Diagram Note element) we use that element as a proxy for the diagram and attach all properties that cannot be attached to the diagram itself (since they are third class citizens on the Sparx universe) to that item instead.

Having been using a competing product that has a lot more 1st class citizens I can tell you there are a bunch of annoying results of that approach too.

[Paolo F Cantoni]

We insist that every diagram has a Title Block element (Diagram Note element) we use that element as a proxy for the diagram and attach all properties that cannot be attached to the diagram itself (since they are third class citizens on the Sparx universe) to that item instead.

Having been using a competing product that has a lot more 1st class citizens I can tell you there are a bunch of annoying results of that approach too.

Interested to hear your thoughts on your experiences, off-line, if necessary.

Paolo

[Guillaume]

Hi,

A potential large project requires compliancy with the diagrams validation process. As regards managing statuses on diagrams is needed.

Another approach is to have each diagram owned by a composite element and to add tagged values to the owning element. That's how we implemented BPMN diagrams, for example.

This approach puts a lot of constraints on the model structure which doesn't look appropriate. Would it be feasible in a later build to support a status field, if not Tagged Values?