Renamed subject line
This posting on behalf of Jeff Anderson.
----- Original Message -----
Sent: Thursday, October 04, 2007 1:52 PM
Subject: FW: [sca-assembly] SCA Visual Modeling
"Standard?"
For some reason my posts do not seem to be making it to
the SCA assembly list if someone could please forward this message to the
list on my behalf that would be much appreciated...
From: Anderson, Jeff T (CA - Toronto)
Sent: Thursday, October 04, 2007 2:10 PM To: sca-assembly@lists.oasis-open.org Subject:
RE: [sca-assembly] SCA Visual Modeling "Standard?"
As discussed, I've put together a first cut at what I
believe is a good UML representation of how an SCA composite could be
diagramed. I found that the component diagrams, especially the UML 2.x
version, were able to cover most of the SCA concepts , although to UML purists
I did have to be a little creative. I know some of the previous
discussion here centered around using "composite" diagrams, however after
doing some further research, I do not believe that UML composites are
appropriate.
I've attached the initial diagrams for reference,
simply explained I applied the following mappings . Composite >a
component with service, components, or references inside
interface >component interface
reference >is simply a UML port from the point of view
of the component, and can be modeled as a delegate to a port when showing an
exposed reference
service >can be modeled as a component interface that
has been exposed to the outside world using a delegate. Properties >with
a little tweaking, realization artifacts contained in a component could be
extended to model properties of a composite or component. This will
allow for much richer modeling of properties than simple squares shown in the
current SCA diagrams. Basically we can use all the notation available in
class diagrams to model the properties.
Does anybody find this UML representation to be useful?
if so, where would we document any decisions that we have around what would be
the "normative" modeling approach using UML? Would have alternate
representations in the actual specifications, ruled me just produce a separate
documentation and with this ride how we are extending UML to cover the
concepts described in SCA?
Any comments would be much
appreciated
Jeff
Anderson Deloitte Inc. 416 874 4471 mobile: 647 444 5932
jeffanderson@deloitte.com
My $0.02 CAD (now on par with $0.02 USD)
There
can be different expressions of the model for different audiences. The
architect/UML heads like myself can make use of the UML models and we can also
chose a simpler convention (concept maps??) for business people. Given
they are both expressions of the same thing, it should not present issues if
modeled properly. I favor UML as the more terse, normative as the binary
relationships can be far more meaningful.
/duane
On 9/28/07
5:17 AM, "David Booz" <booz@us.ibm.com> wrote:
I see that Martin posted an email to raise the
visual modelling issue. I'll not address merits of the issue until we
can formally address the issue, but will only try to address the historical
question you raised.
As you know by now, OSOA produced UML diagrams
to represent the architecture as another way to represent the model.
We did this as another means to explore the design. We (ok,
maybe it's just me) have found UML to be inaccessible to the target audience
for SCA, which is comprised of business logic developers, not middleware
vendors. In light of that, we needed a simpler visual model for
expressing the concepts. In addition, several of the visual SCA tools
that have emerged during OSOA have adopted a similar visual model which
creates a very nice synergy in the community. One of the original SCA
principles is to "keep simple things simple [for the business logic
developer]", and the current visual representation seems to meet that goal
for the target audience.
Dave Booz STSM, SCA and WebSphere
Architecture Co-Chair OASIS SCA-Policy TC "Distributed objects first,
then world hunger" Poughkeepsie, NY (845)-435-6093 or
8-295-6093 e-mail:booz@us.ibm.com http://washome.austin.ibm.com/xwiki/bin/view/SCA2Team/WebHome "Jeffrey A. Estefan"
<jeffrey.a.estefan@jpl.nasa.gov>
"Jeffrey A. Estefan"
<jeffrey.a.estefan@jpl.nasa.gov> 09/27/2007 03:24 PM
Please respond to "Jeffrey A. Estefan"
<jeffrey.a.estefan@jpl.nasa.gov>
To
"Moberg Dale"
<dmoberg@axway.com>, "Martin Chapman"
<martin.chapman@oracle.com>, "Michael Rowley" <mrowley@bea.com>,
<sca-assembly@lists.oasis-open.org>
cc
Subject
Re: [sca-assembly] SCA Visual Modeling
"Standard?"
Dale, Mike, &
Martin,
The
conceptual UML model of SCA as a whole put forth by Mike Edwards is an
excellent one and I have no issue with it. The issue I was raising had
to do with the cartoon-like visual models used throughout the SCA specs that
show properties, services, SCA components, and SCA composites plus their
wiring together.
My
argument is that there is great expressive power with UML 2 that did not
exist in UML 1.x to support component-based development; structured
classifiers in UML 2 (classes and components) can be decomposed and
assembled ("wired") via Parts, Ports, and Connectors in the new Composite
Structure diagrams. I wanted to suggest use of this visual modeling
standard rather than use of custom cartoons for forthcoming SCA specs under
OASIS. And my original question was to the source of these cartoons.
We are exploiting UML 2 in our development of the OASIS Reference
Architecture for SOA, which will be released for public review late this
year or early '08. I also stress that we are using UML 2 as a means to
capture visual models that form architectural views of the overall Reference
Architecture.
As
Duane Nickull (TC chair for the OASIS Reference Model for SOA) points out in
his blog, we are considering use of the term "service aggregation" vice
"service composition" since the latter is more accurate as it describes a
whole-part relationship, meaning you 'delete the whole, you delete the
parts.' This, of course, is not the intent of composite services or
composite applications. We also recognize that the whole industry has
already gained steam on the terminology of composition of services or
"service composition" and therefore, we have not made a final decision on
the language of the RA just yet.
I
did not see an SCA-Assembly issues list on the Kavi site as of yet but once
it is posted, I will update the issues list. It is my understanding
from the recent SCA-Assembly TC minutes that JIRA is still being considered
for tracking issues but has not yet been resolved so I'm sending this note
to the whole TC.
Cheers...
-
Jeff E., JPL
--
********************************************************************** "Speaking
only for myself" Blog - http://technoracle.blogspot.com Community
Music - http://www.mix2r.com My Band -
http://www.myspace.com/22ndcentury MAX
2007 - http://technoracle.blogspot.com/2007/07/adobe-max-2007.html **********************************************************************
**************************************************************************************
Confidentiality Warning: This message and any attachments are intended only
for the use of the intended recipient(s), are confidential, and may be
privileged. If you are not the intended recipient, you are hereby notified
that any review, retransmission, conversion to hard copy, copying, circulation
or other use of this message and any attachments is strictly prohibited. If
you are not the intended recipient, please notify the sender immediately by
return e-mail, and delete this message and any attachments from your system.
Thank you. Information confidentielle: Le présent message, ainsi que tout
fichier qui y est joint, est envoyé à l'intention exclusive de son ou de ses
destinataires; il est de nature confidentielle et peut constituer une
information privilégiée. Nous avertissons toute personne autre que le
destinataire prévu que tout examen, réacheminement, impression, copie,
distribution ou autre utilisation de ce message et de tout fichier qui y est
joint est strictement interdit. Si vous n'êtes pas le destinataire prévu,
veuillez en aviser immédiatement l'expéditeur par retour de courriel et
supprimer ce message et tout document joint de votre système. Merci.
**************************************************************************************
|