Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » UML2 » Behavior Execution Specification overlapping
Behavior Execution Specification overlapping [message #478244] Mon, 16 March 2009 09:55 Go to next message
Gabriel Merin Cubero is currently offline Gabriel Merin CuberoFriend
Messages: 12
Registered: July 2009
Junior Member
Hello everyone!
In the OMG's UML2 specification,the BehaviorExecutionSpecifications
(BES) can be overlapped (to represent sub-executions). However, there is
no explanation of how to achiveve this. In other words, how do you
represent a sub-BES in a UML2 model?

Can anyone give me a hint?

Thanks in advance.

Regards,
Gabriel.
Re: Behavior Execution Specification overlapping [message #478247 is a reply to message #478244] Tue, 17 March 2009 16:18 Go to previous messageGo to next message
james bruck is currently offline james bruckFriend
Messages: 1724
Registered: July 2009
Senior Member
Hi Gabriel,

The Interaction would have an ordered list of InteractionFragment (see
Interaction:getFragments() ).
The start and end points of the BehaviorExecutionSpecification would be
OccurrenceSpecification's that would be ordered in such a way as to make the
execution appear "overlapped".

For example, the Fragments collection could have the following elements.

"start_big" - ExecutionOccurrenceSpecification
"big" - BehaviorExecutionSpecification
"start_small" - ExecutionOccurrenceSpecification
"small" - BehaviorExecutionSpecification
"finish_small" - ExecutionOccurrenceSpecification
"finish_big " - ExecutionOccurrenceSpecification


Cheers,
- James.


"Gabriel Merin Cubero" <gmerin@integranova.com> wrote in message
news:gpl7mq$mtf$1@build.eclipse.org...
> Hello everyone!
> In the OMG's UML2 specification,the BehaviorExecutionSpecifications (BES)
> can be overlapped (to represent sub-executions). However, there is no
> explanation of how to achiveve this. In other words, how do you represent
> a sub-BES in a UML2 model?
>
> Can anyone give me a hint?
>
> Thanks in advance.
>
> Regards,
> Gabriel.
Re: Behavior Execution Specification overlapping [message #478250 is a reply to message #478247] Fri, 20 March 2009 13:40 Go to previous messageGo to next message
Gabriel Merin Cubero is currently offline Gabriel Merin CuberoFriend
Messages: 12
Registered: July 2009
Junior Member
Hi James,

Thanks for your quick answer, but I don't understand your explanation.
Which is the "root" BES and the "affixed" BES in your example? Would you
mind giving me more details in your example?

In addition, I use the start/finish properties of the to store the end
of the first/last message connected to it. Thanks to this and to the
fact that all my MOS are ordered (via GOs), I know where a Message is
really contected to.

I hope I have explained myself and thanks again for your help.

Note:
BES : BehaviorExecutionSpecification
MOS : MessageOccurrenceSpecification
GO : GeneralOrdering

Regards,
Gabriel.



James Bruck escribió:
> Hi Gabriel,
>
> The Interaction would have an ordered list of InteractionFragment (see
> Interaction:getFragments() ).
> The start and end points of the BehaviorExecutionSpecification would be
> OccurrenceSpecification's that would be ordered in such a way as to make the
> execution appear "overlapped".
>
> For example, the Fragments collection could have the following elements.
>
> "start_big" - ExecutionOccurrenceSpecification
> "big" - BehaviorExecutionSpecification
> "start_small" - ExecutionOccurrenceSpecification
> "small" - BehaviorExecutionSpecification
> "finish_small" - ExecutionOccurrenceSpecification
> "finish_big " - ExecutionOccurrenceSpecification
>
>
> Cheers,
> - James.
>
>
> "Gabriel Merin Cubero" <gmerin@integranova.com> wrote in message
> news:gpl7mq$mtf$1@build.eclipse.org...
>> Hello everyone!
>> In the OMG's UML2 specification,the BehaviorExecutionSpecifications (BES)
>> can be overlapped (to represent sub-executions). However, there is no
>> explanation of how to achiveve this. In other words, how do you represent
>> a sub-BES in a UML2 model?
>>
>> Can anyone give me a hint?
>>
>> Thanks in advance.
>>
>> Regards,
>> Gabriel.
>
>
Re: Behavior Execution Specification overlapping [message #478252 is a reply to message #478250] Mon, 23 March 2009 18:19 Go to previous message
james bruck is currently offline james bruckFriend
Messages: 1724
Registered: July 2009
Senior Member
Hi Gabriel,

What you are calling "root" BES, I am calling "big". What you are calling
"affixed" I am calling "small".
The "root" BES has a start and finish that I called "start_big" and
"finish_big".
The order of fragments in the fragments collection is in the order listed
previously.

The order is the key point that indicates nesting.

- James.


"Gabriel Merin Cubero" <gmerin@integranova.com> wrote in message
news:gq06cq$lai$1@build.eclipse.org...
> Hi James,
>
> Thanks for your quick answer, but I don't understand your explanation.
> Which is the "root" BES and the "affixed" BES in your example? Would you
> mind giving me more details in your example?
>
> In addition, I use the start/finish properties of the to store the end of
> the first/last message connected to it. Thanks to this and to the fact
> that all my MOS are ordered (via GOs), I know where a Message is really
> contected to.
>
> I hope I have explained myself and thanks again for your help.
>
> Note:
> BES : BehaviorExecutionSpecification
> MOS : MessageOccurrenceSpecification
> GO : GeneralOrdering
>
> Regards,
> Gabriel.
>
>
>
> James Bruck escribi
Re: Behavior Execution Specification overlapping [message #627441 is a reply to message #478244] Tue, 17 March 2009 16:18 Go to previous message
james bruck is currently offline james bruckFriend
Messages: 1724
Registered: July 2009
Senior Member
Hi Gabriel,

The Interaction would have an ordered list of InteractionFragment (see
Interaction:getFragments() ).
The start and end points of the BehaviorExecutionSpecification would be
OccurrenceSpecification's that would be ordered in such a way as to make the
execution appear "overlapped".

For example, the Fragments collection could have the following elements.

"start_big" - ExecutionOccurrenceSpecification
"big" - BehaviorExecutionSpecification
"start_small" - ExecutionOccurrenceSpecification
"small" - BehaviorExecutionSpecification
"finish_small" - ExecutionOccurrenceSpecification
"finish_big " - ExecutionOccurrenceSpecification


Cheers,
- James.


"Gabriel Merin Cubero" <gmerin@integranova.com> wrote in message
news:gpl7mq$mtf$1@build.eclipse.org...
> Hello everyone!
> In the OMG's UML2 specification,the BehaviorExecutionSpecifications (BES)
> can be overlapped (to represent sub-executions). However, there is no
> explanation of how to achiveve this. In other words, how do you represent
> a sub-BES in a UML2 model?
>
> Can anyone give me a hint?
>
> Thanks in advance.
>
> Regards,
> Gabriel.
Re: Behavior Execution Specification overlapping [message #627444 is a reply to message #478247] Fri, 20 March 2009 13:40 Go to previous message
Gabriel Merin Cubero is currently offline Gabriel Merin CuberoFriend
Messages: 12
Registered: July 2009
Junior Member
Hi James,

Thanks for your quick answer, but I don't understand your explanation.
Which is the "root" BES and the "affixed" BES in your example? Would you
mind giving me more details in your example?

In addition, I use the start/finish properties of the to store the end
of the first/last message connected to it. Thanks to this and to the
fact that all my MOS are ordered (via GOs), I know where a Message is
really contected to.

I hope I have explained myself and thanks again for your help.

Note:
BES : BehaviorExecutionSpecification
MOS : MessageOccurrenceSpecification
GO : GeneralOrdering

Regards,
Gabriel.



James Bruck escribió:
> Hi Gabriel,
>
> The Interaction would have an ordered list of InteractionFragment (see
> Interaction:getFragments() ).
> The start and end points of the BehaviorExecutionSpecification would be
> OccurrenceSpecification's that would be ordered in such a way as to make the
> execution appear "overlapped".
>
> For example, the Fragments collection could have the following elements.
>
> "start_big" - ExecutionOccurrenceSpecification
> "big" - BehaviorExecutionSpecification
> "start_small" - ExecutionOccurrenceSpecification
> "small" - BehaviorExecutionSpecification
> "finish_small" - ExecutionOccurrenceSpecification
> "finish_big " - ExecutionOccurrenceSpecification
>
>
> Cheers,
> - James.
>
>
> "Gabriel Merin Cubero" <gmerin@integranova.com> wrote in message
> news:gpl7mq$mtf$1@build.eclipse.org...
>> Hello everyone!
>> In the OMG's UML2 specification,the BehaviorExecutionSpecifications (BES)
>> can be overlapped (to represent sub-executions). However, there is no
>> explanation of how to achiveve this. In other words, how do you represent
>> a sub-BES in a UML2 model?
>>
>> Can anyone give me a hint?
>>
>> Thanks in advance.
>>
>> Regards,
>> Gabriel.
>
>
Re: Behavior Execution Specification overlapping [message #627446 is a reply to message #478250] Mon, 23 March 2009 18:19 Go to previous message
james bruck is currently offline james bruckFriend
Messages: 1724
Registered: July 2009
Senior Member
Hi Gabriel,

What you are calling "root" BES, I am calling "big". What you are calling
"affixed" I am calling "small".
The "root" BES has a start and finish that I called "start_big" and
"finish_big".
The order of fragments in the fragments collection is in the order listed
previously.

The order is the key point that indicates nesting.

- James.


"Gabriel Merin Cubero" <gmerin@integranova.com> wrote in message
news:gq06cq$lai$1@build.eclipse.org...
> Hi James,
>
> Thanks for your quick answer, but I don't understand your explanation.
> Which is the "root" BES and the "affixed" BES in your example? Would you
> mind giving me more details in your example?
>
> In addition, I use the start/finish properties of the to store the end of
> the first/last message connected to it. Thanks to this and to the fact
> that all my MOS are ordered (via GOs), I know where a Message is really
> contected to.
>
> I hope I have explained myself and thanks again for your help.
>
> Note:
> BES : BehaviorExecutionSpecification
> MOS : MessageOccurrenceSpecification
> GO : GeneralOrdering
>
> Regards,
> Gabriel.
>
>
>
> James Bruck escribi
Previous Topic:Create Object from String
Next Topic:Create Object from String
Goto Forum:
  


Current Time: Sun Mar 29 07:15:32 GMT 2020

Powered by FUDForum. Page generated in 0.01997 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top