|
|
|
|
Re: project specific property [message #1698412 is a reply to message #1698408] |
Mon, 15 June 2015 11:57 |
Camille Letavernier Messages: 952 Registered: February 2011 |
Senior Member |
|
|
Hi,
I think you are confusing the UML Metamodel (Defining Class, Association, ...) and the UML Standard Profile, which is actually a Profile, defining some Stereotypes (<<Derive>>, <<Refine>>, <<Metaclass>>, ....)
A Profile defines some Stereotypes, and Stereotypes can "extend" (Via an "Extension") a UML Metaclass, or inherit (Via a "Generalization") from another Stereotype.
You can add new Profiles and/or new Stereotypes and/or new Properties on any model, at any point in time
Camille
Camille Letavernier
|
|
|
Re: project specific property [message #1698445 is a reply to message #1698412] |
Mon, 15 June 2015 18:02 |
Rolf Schumacher Messages: 60 Registered: January 2014 |
Member |
|
|
Thank you, Camille - i think you are right, my whish is not the way it will go.
Doing a model I did not use any profile, just plain UML.
After that I found out that I need non-standard properties, e.g. for elements like Class, Association, ... , properties like SIL, DOC-SEQ, ...
Now I am going to define a profile for that.
In <<EPackage>> Standard Profile I find the <Package Import>UML 2.5.0 Metamodel, where I can extend the Metaclasses, say I do me a new Class stereotype extending Class and a new Association stereotype extending Association from UML 2.5.0 Metamodel, giving them the required new properties, e.g. SIL, DOC-SEQ...
I guess I have to exchange any plain-UML element in my plain-UML model by my new stereotypes in order to get hold of the properties, right?
Do you know of any other way to attach project-specific information to UML elements?
Is using comments the only way?
Regards
Rolf
[Updated on: Mon, 15 June 2015 18:03] Report message to a moderator
|
|
|
Re: project specific property [message #1698515 is a reply to message #1698445] |
Tue, 16 June 2015 07:47 |
Camille Letavernier Messages: 952 Registered: February 2011 |
Senior Member |
|
|
Hi Rolf,
Stereotypes is actually the right concept for this. You don't "replace" UML Elements with a Stereotype. Instead, you "apply" a Stereotype on an existing UML Element (Class, Association, ...), to add the extra information you need
HTH,
Camille
Camille Letavernier
|
|
|
Powered by
FUDForum. Page generated in 0.04358 seconds