Fwd: Support Stereotype & Producer/Consumer concepts

Begin forwarded message:

> From: Heiko Braun <ike.braun@googlemail.com>
> Subject: Re: Support Stereotype & Producer/Consumer concepts
> Date: January 10, 2013 12:04:46 PM GMT+01:00
> To: Paolo Bottoni <bottoni@di.uniroma1.it>
> 
> 
> Thanks for the explanation Paolo.
> One question though: If there is only the "supports" concept, how would you model the "producing" and the "consuming" side of things? Maybe I am complete off track, but my lines of thinking come from the question how the model and it's realisation as CUI can be validated. It seems to me that the direction of these relationship matters.
> 
> From my point of view any distinct relation between structure and behaviour will always be unidirectional and qualified by the consumed resource type. 
> 
> Typical examples are:
> 
> - Trigger (structure) leads to function call (behaviour)
> - Navigation (behaviour) leads to activation of interaction unit (structure)
> - Functional Call (behaviour) leads to navigation (behaviour)
> - System event (context of use) leads to activation of interaction unit (structure)
> - [...]
> 
> IMO these relationships, their direction and qualifier (resource: event, data, etc) would need to be expressed within the abstract model that covers structure and behaviour. It's necessary to support the reification across abstraction levels. Especially when moving from abstract UI to concrete/final UI.
> 
> Does that make sense?
> 
> On Jan 8, 2013, at 10:51 PM, Paolo Bottoni <bottoni@di.uniroma1.it> wrote:
> 
>> . What an EventSupport generates
>> is an event of the corresponding type. This constitutes the bridge
>> with the notion of Behaviour, as behaviours produce and consume
>> resources, events are a special type of resource, and interactive
>> behaviours consume interactive events, for example as triggers, or
>> input data to be transformed.
>