[ubl-ndrsc] FW: First daft of OO-Design

["Stuhec, Gunther" <gunther.stuhec@sap.com>]

Hello all,

I send the examples from Dave Carlson now.
You need a Acrobart SVG viewer for the svg-files.

Kind regards,

	Gunther

-----Original Message-----
From: Dave Carlson [mailto:dcarlson@ontogenics.com]
Sent: Mittwoch, 7. August 2002 06:06
To: Stuhec, Gunther
Subject: Re: First daft of OO-Design


Hi Gunther,
OK, I've got some comments on your paper and have also attached the reverse
engineered model as a Rose file.  Obviously I agree with the general
principles stated in section 2.2, because I've been writing about this for
more than 2 years now!

My hyperModel design tool has been completely rewritten since you saw the
Web-based version last October at the UBL meeting.  The tool is now embedded
as a plugin to the Eclipse IDE (see www.eclipse.org) and supports both
reverse engineering XSD into UML and generating XSD from UML.  XMI files are
exported for use in other tools, such as Rose.  I've been in beta test for
2-3 months and am preparing to launch version 1.0.

The attached ZIP includes 3 SVG diagrams that are generated within my tool.
This layout is 100% automated -- only 2-3 mouse clicks from your schemas to
these diagrams.  (Install the Adobe SVG viewer, and if you are not familiar
with it, open a diagram, click the right mouse button and select "Help" to
see how to zoom and move around the diagram.  Hint: hold down the Alt key
and use the left mouse button to move around the diagram.)  The diagrams
must be manually created from within Rose, using its very bad layout
algorithm.

Also, the XSD source that you sent has 3 errors: the element types are
missing for three children of CompanyDetails.  My reverse engineered model
assigns these as "anyType".

Now to your paper.

It's confusing that the class and attribute names used in the UML diagrams
to not agree with the XSD examples.  Which naming scheme are you
recommending?  Do you really want to insert the "." into UML class and type
names?

You'll notice that my reverse engineering tool strips off the "Type" suffix
from type names.  I recommend creating O-O diagrams that can be used for
other purposes, such as generating RDBMS or Java.  No Java programmer puts
"Type" on the names of all his/her classes.  This can be re-appended when
generating XSD from the model.

In general, you mix presentation of UBL naming and design rules, their use
in XSD, the mapping to O-O & UML, and Core Components terminology.  You
should be more consistent in how you present these topics.  Do you expect
that your reader is already familiar with NDR recommendations?  The core
components metamodel?

I'd recommend this approach:

1. Introduce a naming and design rule from the NDR spec (with section
reference).

2. Show how the rule is realized in an O-O modeling approach and a UML class
diagram.

3.  Show how the UML diagram maps to an XML Schema (and thus implements the
NDR guideline).

Then repeat these steps 1 thru 3 for several other NDR guidelines.

Alternatively, you could reverse steps 2 and 3, by presenting the XSD for
the NDR guideline, then showing its presentation as a UML diagram.  Your
current paper organization is closer to this approach, having more emphasis
on XSD examples from XML Spy diagrams and less emphsis on UML class
diagrams.  So it's more like a discussion of O-O approach to XSD design, but
the recommendation for how and where to use UML class diagrams is less
clear.  But pick a consistent approach to presenting examples and
recommendations.

I hope this helps!

Regards,
  Dave Carlson

----- Original Message -----
From: "Stuhec, Gunther" <gunther.stuhec@sap.com>
To: "'Dave Carlson'" <dcarlson@ontogenics.com>
Sent: Tuesday, August 06, 2002 10:39 AM
Subject: RE: First daft of OO-Design


> Hello Dave,
>
> that's fine. Thank you very much. I attached the schemas onto this mail
now. Could send me your results?
>
> Kind regards,
>
> Gunther
>
>
>

Attachment: DeliveryNotification-UML.zip
Description: Zip compressed data