| Opaque specification of an operation's behaviour [message #626166] |
Mon, 10 March 2008 18:13 |
 Felix Dorner
Messages: 676
Registered: July 2009 |
Senior Member |
|
|
Hey,
I am designing a small Action Language that can be used to specify the
behaviour of the operations in a class model. I am looking for good ways
to link the textual specification of an operation to the operation in
the model.
After some reading, I think the preferred way to do this, is to create
an OpaqueBehaviour for every operation I'd like to specify in my language.
One thing is however disturbing: Every Parameter of the Operation must
be created twice. One owned by the Operation, and the other owned by the
OpaqueBehaviour.
I don't see the point in that. Could't this association be "derived", or
even completely ommited from the metamodel, or are there any reasons why
there is the need for this data to be specified with such a redundancy?
Felix
|
|
|
Powered by
FUDForum. Page generated in 0.06623 seconds
] 
Search
Help
Register
Login
Home
