From: bbadour@golden.net (Bob Badour) Newsgroups: comp.databases,comp.databases.object,comp.databases.theory,comp.lang.java.databases,comp.lang.java.programmer Subject: Re: Clean Object Class Design -- What is it? Date: 5 Jun 2001 22:23:10 -0700 Organization: http://groups.google.com/ Lines: 22 Message-ID: References: NNTP-Posting-Host: 63.68.16.100 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 991804990 14394 127.0.0.1 (6 Jun 2001 05:23:10 GMT) X-Complaints-To: groups-support@google.com NNTP-Posting-Date: 6 Jun 2001 05:23:10 GMT > > What constitutes a "clean" object class design? How does one achieve the > > goal of "cleanliness"? How does one recognize a "clean" design vs an > > "unclean" design? Are the steps for achieving a "clean" design documented > > anywhere? Can we deterministically determine whether a given design is > > "clean" ? > > > > How? > > The big difference is that (good) Classes are "designed" around their > behavior; _not_ their "data". > > See Designing Object-Oriented Software by Wirfs-Brock, Wilkerson and Wiener Thanks for the reference. I checked out Wirfs-Brock et al at http://mogwai.simplenet.com/mood/DOOS.htm I do not see how DOOS differs from the conceptual modelling stage of database design. Everything there certainly applies to relational domain design. I do not see how the conceptual analysis transforms into a "clean" logical design, and I am still unclear on the meaning of "clean".