OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Questions on metamodel example



Jim and Bob,
Thanks for the walk-thru of the example.
Sorry we ran out of time. We should schedule a continuation walk-thru.
I continued through the example and have the following questions on the FSV:

(In the following pardon my strange syntax. I am using ^^ to surround names of 
stereotypes because my mailer tries to interpret the double left and right 
brackets as mail directives, and returns the mail to me)

Neither the Network Component Collaboration diagram or the Sequence diagram
have stereotypes marked, so I may be guessing a little here, but:

I see from Network Component class diagram that 
ProductionScheduler is a functional role (stereotype of a class)
Shipper is a Organizational role (subtype of a functional role)

I see from the unnamed diagram (number 11 in the guide) that
ShipmentAuthorizationDocument  maps to a ShipmentAuthorization. 
ShipmentAuthorizationDocument is a ^^BusinessDocument^^ (stereotype of class)
ShipmentAuthorization is a ^^commitment^^ (stereotype of class)

Now I look at the the collaboration diagram and see that a ProductionScheduler
sends a ShipmentAuthorization to a Shipper. So here a FunctionalRole sends a
commitment to a OrganizationalRole. Is that the intention? Should it be a
ShipmentAuthorizationDocument being sent?

And concerning the mapping to UML:
In a collaboration diagram the sender and receiver are ClassifierRoles and
that which is sent is a Message. But in the example, if we use the underlying
UML structures underneath the stereotypes, then a class sends a class to a
class. Is that the intention, or should the stereotypes actually be mapped to
ClassifierRole and Message (and AssociationRole)?

The basis of this question is whether the intention is to use the UML
collaboration model that the collaboration diagram normally maps to, or
whether we are simply using the collaboration diagram for convenience and will
constrain or otherwise map it to the "class" based stereotypes?

A separate question is the use of the word "Business Action".
On the business action class diagram ShipmentAuthorizationAction is a
^^BusinessAction^^. I cannot find that stereotype defined anywhere in the
metamodel. Should it be ^^BusinessActionMessage^^?

Thanks in advance for your clarifications.

-karsten

---------------------------------------------------
Karsten Riemer,
Director, Information Architecture,
Enterprise Management Architecture Group
Sun Microsystems Inc.,
MailStop UBUR03-313
1 Network Drive,
Burlington, MA 01803-0903

ph. 781-442-2679
fax 781-442-1599
e-mail karsten.riemer@sun.com



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC