file Archimate - add tagged values / attributes?

11 months 1 week ago #5394 by matthew.james
Bump ... ?
Anyone got any thoughts on this ? Am I dreaming ... ?

Please Log in or Create an account to join the conversation.

11 months 1 week ago - 11 months 1 week ago #5395 by osl
Hi, let's make your dream come true ;)

1. create a new 'Maturity' Stereotype in your LocalProfile
2. create a 'Maturity' PropertyTableDefinition under your Stereotype
3. create a 'Maturity' PropertyDefinition under your PropertyTableDefinition
4. create a 'MaturityLevel' EnumeratedPropertyType in your LocalModule
5. create three EnumerationLiterals under your EnumeratedPropertyType: 'high', 'medium', and 'low'.
6. edit your 'Maturity' PropertyDefinition and type it 'MaturityLevel
7. create an ArchiMate view and a Capacity in it
8. select the Capability and open the Symbol tray (to the right of your diagram
9. check the 'Show tags' box
10. right-click on your Capability and run the 'Add Stereotype' command
11. add the <<Maturity>> Stereotype to the Capability
12. open the 'Properties' tab
13. select 'LocalModule > Maturity'
14. select a value in the drop-down list of the 'Maturity' value field

Result:


General view:


BR

Go pro
Attachments:

Please Log in or Create an account to join the conversation.

11 months 1 week ago #5396 by matthew.james
Thanks for the awesome and detailed response - I can now see how this works, and how to use / apply stereotypes and enumerations to different elements. Opens up lots of possibilities. And I doubt I would have got there by muddling through myself.

Now for the $1m question ... I can add properties / tagged values to individual elements (one at a time), but is there a way to add these as a default to the underlying element type ? (meta-class?)
Using Archimate Capability again as an example, the above approach lets me add Maturity to an instance of the Capability meta-class. Is there a way to do something so that *every* Capability gets this property (or at least every new Capability when added).

Please Log in or Create an account to join the conversation.

11 months 1 week ago - 11 months 1 week ago #5397 by osl
Hi,

This is actually the same process except you have to create a 'MetaclassReference' instead of a Stereotype at step 1:





However, although the property would actually exist in the model in Modelio 3.7.1, you'll have to migrate to Modelio 3.8 to be able to see it in the Properties tab:



Please let me know when you can transfer the million dollar.

BR

Go pro
Attachments:

Please Log in or Create an account to join the conversation.

11 months 1 week ago #5398 by matthew.james
Thanks again :-)
I had actually tried that but it didn't seem to be working - after "Create Element -> Metaclass Reference" I was just getting an empty, unnamed element in the project browser, no dialogues or ability to specific the metaclass to reference, so I was assuming this wasn't working. I have found that I can link the new element to the right metaclass after it has been created. After that the process was simple as you'd described :-)
(Once I get hold of the $1m I'll be sure to send it your way ...!)

A couple of follow up questions:
- What is supposed to happen when you remove a stereotype from an element? I have found that when I remove the stereotype (created as per your first message above), the stereotype and tag disappear from the element properties, but the tagged value is still displayed on the element in diagrams. So it's kind of left behind in some weird way
- What is supposed to happen with default values on tags? I have created the metaclass reference (as described in your second message above) and now when I add a new Capability it has the tagged value as a property. However when I add the element to a diagram the default value for the tag isn't showing, even if I click on "Show tags" for that element.It only display once I change it from the default value

Please Log in or Create an account to join the conversation.

11 months 1 week ago #5399 by osl
Hi,

- What is supposed to happen when you remove a stereotype from an element? I have found that when I remove the stereotype (created as per your first message above), the stereotype and tag disappear from the element properties, but the tagged value is still displayed on the element in diagrams. So it's kind of left behind in some weird way

This is the normal behaviour, although it may not appear so. If you want to remove the tagged values in your case, you can use the Semantic view:

Keys:
1. Activate the Semantic view
2. Open the Semantic view
3. Synchronize the Semantic view
4. Select your Capability
5. Deploy the Semantic model down to the PropertyTable and delete it

You can file an evolution request in the Forge .


- What is supposed to happen with default values on tags? I have created the metaclass reference (as described in your second message above) and now when I add a new Capability it has the tagged value as a property. However when I add the element to a diagram the default value for the tag isn't showing, even if I click on "Show tags" for that element.It only display once I change it from the default value

The default value only shows in the Properties tab as a reminder that the user should probably choose a value. But it would make sense that this also shows in the diagram. You can also file a request for this.

BR

Go pro
Attachments:

Please Log in or Create an account to join the conversation.

Moderators: tmachmebr
Time to create page: 0.728 seconds
^ Back to Top