Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!helios.ee.lbl.gov!ncis.llnl.gov!afit-ab!wbralick
From: wbralick@afit-ab.arpa (William A. Bralick)
Newsgroups: comp.software-eng
Subject: Architecture
Summary: A good model?
Message-ID: <1014@afit-ab.arpa>
Date: 28 Mar 89 02:45:24 GMT
Reply-To: wbralick@blackbird.afit.af.mil (William A. Bralick)
Distribution: na
Organization: Air Force Institute of Technology; WPAFB, OH
Lines: 17

It seems to me that architecture (as in buildings, not computer systems :-) 
should provide a useful set of lessons for software engineers.  The parallels
between software engineering and architecture (especially for a large, unique
building) are striking -- both are labor intensive, lengthy, expensive, 
prone to schedule slippages and cost overruns, require not only a sound
design but also good management practices, both can benefit from standardized
parts, etc.  Has any formal attempt been made to draw on (this pun
is intentionally left blank) architecture as a model for solving some
of the problems in software engineering?

Regards,

-- 
Will Bralick : wbralick@afit-ab.arpa  |  If we desire to defeat the enemy,
Air Force Institute of Technology,    |  we must proportion our efforts to 
                                      |  his powers of resistance.
with disclaimer;  use disclaimer;     |               - Carl von Clauswitz