| Static Profiles and predefined type system [message #628427] |
Sun, 02 May 2010 11:56 |
 Timothy Marc
Messages: 547
Registered: July 2009 |
Senior Member |
|
|
Hi all,
i want to implement a UML profile that contains a dedicated type system
like a Timer (UML::DataType), etc. Therefor i created two uml files, one
with its root element being a 'Profile' (the core profile specification)
and one containing the predefined types (mostly UML::DataTypes).
But how could that be realized with static profiles? I tried to type an
attribute of the stereotype (eclass) with both UML::DataType and
MyProfile::Timer. The problem is that this requires the separate uml
file to be converted to Ecore too. But by doing so, how is it possible
to reuse the timer in a UML model that has the profile applied? If i
convert the UML predefined types into an Ecore model, it is not anymore
compatible with UML.
The idea with the timer is that a class must contain a timer-typed
attribute so that the stereotype (within a interaction) can point to
that timer by pointing to that timer. (Stereotype::timerRef:Timer). So
both the profile and a system model should reuse the predefined types.
With dynamic profiles, this is quite easy to realize since the
conversion step is not included, but i want to make use of the
advantages of static profiles anyway.
Can anyone give me a hint how to realize this?
Thanks in advance, Timothy
|
|
|
Powered by
FUDForum. Page generated in 0.03442 seconds
Search
Help
Register
Login
Home
