RE: java for the database
- From: "Mark W. Farnham" <mwf@xxxxxxxx>
- To: <Christian.Antognini@xxxxxxxxxxxx>, "Dennis Williams" <oracledba.williams@xxxxxxxxx>
- Date: Wed, 15 Mar 2006 18:03:55 -0500
At 466 pages, including the index, "Structured Design: Fundamentals of a
Discipline of Computer Program and Systems Design" by Edward Yourdon and
Larry L. Constantine, circa 1977, is an extremely efficient read for just
about everything you need to know about designing systems. Some of the 3rd
generation programming references are a little antique, but they make all
the requisite points very clearly.
Whether someone did the shorthand in their head, or formally with tools or
diagrams, all the best systems I've seen were constructed in a manner that
fits neatly with dataflow diagrams and transform centered design.
More modern systems typically have a high emphasis on the human interface,
which is just one of the afferent legs toward the transform center for input
and and efferent legs for painting the screen and reporting. Use cases can
be similarly mapped to a transform centered design, and thus you can make a
sensibly integrated java environment and schema design. If you don't
understand your data flow and transform centers, I don't understand how
someone can sensibly engage in tossing together UML to document the system
being built. Maybe that's my lack of understanding.
You don't have to use the antique hand drawn pictures, but once you imprint
them on your brain it will change how you think (in a good way) forever. It
is probably out of print, but usually you can find it on ebay. The Second
Edition is much better than the First (or so I've been told - I only have
the Second Edition).
Regards,
mwf
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Christian Antognini
Sent: Wednesday, March 15, 2006 5:02 PM
To: Dennis Williams
Cc: oracle-l@xxxxxxxxxxxxx
Subject: RE: java for the database
Dennis
> The problem I've experienced is that the Java people
> will try to create their class diagrams first, and
> directly create the database schema from those, ie.,
> create a table to persist each class.
I experienced the same illness. Of course, at least for non-simple
applications, this is catastrophic.
The point is that the opposite, i.e. basing the classes on the database
design, isn't better.
Regards,
Chris
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
