RE: [ubl-lcsc] Newest version of the OO-design position paper.

["Chan, Sally M" <sally.m.chan@boeing.com>]

Gunther,

In OO design, the focus is on object behavior and emphasis on data
encapsulation (hiding data behind its public interface).  In XML or data
model, the focus is on exposing the data, not behavior.  Using OO design to
design data, is it the right thing to do?  this could lead to classes that
don't have behavior, not good OO design!

In OO application development, you need both class model and data model.
The challenge is how one can align the two to achieve seamless integration
between the object model and data model, show me how an OO-design data model
helps me write less code when I need to access the XML data from an OO (or
non-OO) application will be a value to me. 

Regards,

Sally Chan
Associate Technical Fellow
The Boeing Company
Boeing Commercial Airplanes
IS - Architecture & eBusiness
425-965-0141



-----Original Message-----
From: Stuhec, Gunther [mailto:gunther.stuhec@sap.com]
Sent: Tuesday, August 20, 2002 1:57 PM
To: 'ubl-lcsc@lists.oasis-open.org'; 'ubl-ndrsc@lists.oasis-open.org'
Subject: [ubl-lcsc] Newest version of the OO-design position paper.



Hello all,

this is our newest version of the OO-design position paper. It describes
generally the definition of aggregate core components as well as the
aggregated business information entities. 

In this paper all aggregates representing an object. The subelements which
are basic business information entities representing the attributes of an
objects. An the aggregates insided of an objects are further objects or
parts of an objects. The object itself refers to these furhter objects. 

In addition all containers are avoided, consciously.  Because it is not
possible to represents containers as objects with attributes and influence
the representation of a conclusive class diagram unfavorably.  

Please review this document and send me your comments and remarks.

Kind regards,

      Gunther