2008/11/6 Mark Baker <[EMAIL PROTECTED]>:
> On Thu, Nov 6, 2008 at 10:41 AM, Steve Jones <[EMAIL PROTECTED]> wrote:
>> Architect and Design first... what a novel idea.
>>
>> Lets bump that 20 years up to 60 years though.
>
> I was specifically referring to the relatively modern notion of the
> study of the elements of software architecture - components,
> connectors, and data - and the application of constraints on their
> relationships to induce certain properties. That's where the "20"
> comes from, since Perry & Wolfe.

Ian Sommerville's "Software Engineering" (First published 1982) was a
standard text at my Uni and talks about modelling the components,
contraints and interactions between those elements (and the data
flow), this is in the first 2 chapters (the rest goes into more
detail) and set out as the way to go about it (for students).  Betrand
Meyer's (1988, but based on earlier research work) Object-Oriented
Software Construction has a chapter (number 2) about modularity and of
course a whole set about data.  Hoare (book from 1985, work from way
way back) positively rants at the importance of breaking down elements
and understanding both their connections and the data. That is before
I leap into the hardware design books behind me.  These are just the
ones on the shelf behind me that I grabbed to get something from
before 1992.

But the biggest reason I say 60s years is the Mythical Man Month
(1975, based on work from the 60s)
(http://www.fabtime.com/man-month.shtml for someone applying his
lessons to NT) where he talks about the concepts of components and the
challenge of creating robust systems out of a number of diverse
components.

Perry and Wolfe did not create from new software architecture with
their paper, they documented the learnt best practices of the previous
40 years and put together a nice structure in which others could then
build.  They created a separation from "design" to the early stage
processes which then became architecture, but people were doing this
for umpteen years before hand in successful projects.


Steve

>
> Mark.
> 

Reply via email to