Re: [hyades-dev] New group

[Serge Lucio <slucio@xxxxxxxxxx>]

Mike,

I think we need to clarify some elements
of the document. My initial reading left a number of issues unspoken (:-)):
1. On your comment "the
test profile allows arbitrary UML behaviours which are not practical for
execution". Althought it is
correct that UML behaviors are rich, I think stating the following is not
correct:
"The Hyades Behavioural Model
is defined as the subset of UML2 that corresponds to BPEL, or more precisely
to a concrete representation of BPEL concepts provided in EMF."
Eclipse is embracing the UML family
of standards (MOF, UML 2.0). Therefore, the Hyades behavioral model is
and should remain UML 2.0 behaviors, without restrictions. The restriction
to BPEL should apply only to the generic execution engine.
2. On the statement "The
SUT is modelled as a WSDL interface – if the SUT does not provide a WSDL
interface a “wrapper” can be built around the actual interface of the
SUT". An interface specification
of the SUT should be a UML 2.0 model of it, and should be part of
the "test" model. Providing a  mechanism to import this
model from a WSDL interface is desirable.
3. On the runtime UI "This,
together with the ability of the runtime UI to modify variables in the
BPEL, defines a new runtime control and monitoring UI which replaces statcon
(and probably won’t look that different)."
I am not sure that stacon is the most suitable interface for that. Why
is this interface different from the generic behavior editor you are proposing?

I think we are trying to achieve a number
of distinct things here that should probably trigger the creation of several
working entitties:
1. Formalization of a testability interface
(i.e. provide a model of the SUT). This is absolutely required for the
test model to be complete. This must be based on UML 2.0 standards.
WSDL is a nice and easy way for Hyades users to describe these interfaces
textually and shouldn't be the standard put forward.
2. Standardization of agents interfaces
for test components to interact with them. This is very important to formalize
the communications of agents beyond the RAC transport layer.
3. Provide a generic execution engine
based on Web Services standards. This is a "nice to have".

I think 1 and 2 definitely belong to
the Hyades platform.  Unfortunately (1) needs to wait for Hyades and
the UML 2.0 project to converge, so we should speak to this topic in light
of UML 2.0 profile alignment post Hyades 3.0 (2) probably doesn't fit in
the 3.0 schedule, but is very relevant. Finally (3) is a completely separate
item, that should be considered as an example for now.

I want to make sure that we (IBM) get
involved in the detailed definition of what is proposed, before we bless
it. At this stage, I think things are not well enough defined: The scope
of the proposal is pretty wide, and I don't want people to go off on the
basis of this document and mess up with the existing Hyades models, and/or
positioning. So, to start with, I would like to see from Anthony (I guess)
a detailed proposal describing the 3 topics I highlighted: testability
interface, agents' interfaces, execution engine (behavior UI, WSDL and
BPEL mappings to UML 2.0, runtime UI).

Finally, I would like to get Mike to
clarify that UML 2.0 remains the primary standard that Hyades/Eclipse supports,
with no restrictions, WSDL and BPEL being specific to this generic
execution engine

Thank you,
Serge

Michael.Norman@xxxxxxxxxxxxx
Sent by: hyades-dev-admin@xxxxxxxxxxx

03/01/2004 01:49 PM

Please respond to
hyades-dev

To	hyades-dev@xxxxxxxxxxx
cc
Subject	[hyades-dev] New group

Following some discussions after the face to face
about our plan post 
3.0, there have been some ongoing discussions around an additional 
choreography layer, and given these are only loosely related to the 
existing group structure the management group has decided to set up an
additional group known as the Platform Group to address them.  It
will 
be run by Antony Miguel antony.miguel@xxxxxxxxxxxxx, although because he
isn't a committer I will represent it at the weekly committer call.

Attached is the current working document for the group  Antony will
set 
up the weekly sessions via Webex.  Please come along and participate.

Regards,

Mike Norman,
Hyades Project Lead

Attachment: The Hyades Platform.doc
Description: Binary data