From: Shark8 <onewingedshark@gmail.com>
Subject: Re: Pre-Ada95 books still worth reading
Date: Sat, 21 Jul 2012 21:15:50 -0700 (PDT)
Date: 2012-07-21T21:15:50-07:00 [thread overview]
Message-ID: <6a07ab1e-a435-4da1-bec2-1b0ff6640e44@googlegroups.com> (raw)
In-Reply-To: <jubagm$4j0$1@dont-email.me>
On Friday, July 20, 2012 4:05:11 AM UTC-6, Brian Drummond wrote:
> On Fri, 20 Jul 2012 08:34:01 +0200, Georg Bauhaus wrote:
>
> > On 19.07.12 20:46, Simon Wright wrote:
> >> Brian Drummond <brian@shapes.demon.co.uk> writes:
> >>
> >>> One not mentioned so far is Grady Booch and Doug Bryan : Software
> >>> Engineering with Ada. I don't know how well it is regarded now, but I
> >>> thought it was good when I read it. Given the Booch Components are
> >>> still around, it may be worth considering.
> >>
> >> The book discusses the Original Booch Components, at
> >> http://www.adapower.com/original_booch/, not the Ada 95 components at
> >> https://sourceforge.net/projects/booch95/.
> >>
> >>
> > I think there are two different books here, the first by Booch and
> > Bryan,
> > Software Engineering with Ada (1994 (3rd ed.) and earlier);
> > the second by Booch: Software Components with Ada (1987).
> >
> > There is one recurring pattern in the first book, maybe worth
> > mentioning:
> >
> > * Identify the objects
> > * Identify the operations
> > * Establish the visibility
> > * Establish the interface
> > (* Evaluate the objects )
> > * Implement each object
> >
> > The authors explain these steps in an introductory section titled "An
> > Object-Oriented Design Method".
>
> Thanks Georg,
> I was unaware of the second book, but thought the first would be a good
> exposition of the thought process behind them.
>
> The design method he describes has a distinctly ... dated, or perhaps
> classical? feel in these days of "extreme programming" and "test driven
> development".
>
> Is it still relevant, outside of areas that can afford the full weight of
> formal methods because they *have* to be right?
>
> I believe both ends of the spectrum have their place. "Write only what
> you need to", "compile and test early and often" are appropriate where
> you really don't know what you are doing - perhaps the customer doesn't
> either, or the hardware you are driving is poorly documented.
>
> But where much of the job is clear, I try to follow the basic approach
> here.
>
> - Brian
Is that the grey book? And did it have a section on "stream-oriented programming" where the idea was to view the program as operating on a stream of info, instead of the 'Stream construct/attribute? (I lost the book and then moved so most of my Ada books aren't available to me ATM.)
next prev parent reply other threads:[~2012-07-26 4:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 21:13 Pre-Ada95 books still worth reading wrp
2012-07-14 21:44 ` Simon Wright
2012-07-15 7:20 ` J-P. Rosen
2012-07-15 11:29 ` Simon Wright
2012-07-15 19:46 ` wrp
2012-07-15 7:18 ` J-P. Rosen
[not found] ` <67e508lh89b705q2d0u82in99p6u15cel9@invalid.netcom.com>
2012-07-15 13:33 ` Ada novice
2012-07-15 15:07 ` Bill Findlay
2012-07-15 20:09 ` wrp
2012-07-15 21:40 ` Patrick
2012-07-19 6:33 ` Randy Brukardt
2012-07-19 7:32 ` Dmitry A. Kazakov
2012-07-19 8:36 ` Brian Drummond
2012-07-19 18:46 ` Simon Wright
2012-07-20 6:34 ` Georg Bauhaus
2012-07-20 7:19 ` Simon Wright
2012-07-20 10:05 ` Brian Drummond
2012-07-22 4:15 ` Shark8 [this message]
2012-07-22 11:55 ` Brian Drummond
2012-07-23 3:49 ` Shark8
2012-07-15 7:49 ` Georg Bauhaus
2012-07-19 19:09 ` wrp
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox