Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!hacgate!ashtate!atsun!dwiggins From: dwiggins@atsun.a-t.com (Don Dwiggins) Newsgroups: comp.object Subject: Re: Object-Oriented Requirements Analysis: An Introduction Message-ID: Date: 15 Dec 89 00:21:55 GMT References: <1989Dec7.202059.973@ibmpcug.co.uk> Sender: dwiggins@ashtate.UUCP Organization: Ashton-Tate, Inc. Lines: 29 In-reply-to: daven@ibmpcug.co.uk's message of 7 Dec 89 20:20:59 GMT You write: I could put together a list of references, if there are any readers who believe, as I do, that software development is not unique, but shares problems common to all technological innovation and implantation. So far, I have only found AI people willing to look to other disciplines for answers to their problems, so I doubt that anyone here would be interested. Yes, I'd definitely be interested in references, and I suspect that there are others who would be, too; pleast post. I presume that the harsh tone of the last sentence derives from some disappointing personal experience; let me assure you that there are software folks who are only too happy to learn from any source that seems to have some relevance. For example, Watts Humphrey of SEI has based his work on that of Edward Deming, with notably successful results (see, for example, his article in the March 1988 issue of IEEE Software). There have also been discussions on the net about the parallels between software engineering and other engineering disciplines, particularly electrical, mechanical, and architectural. To clarify any misunderstanding, my questions about the recursive/parallel approach were sincere; I see some potential dangers in the approach, and am interested to see how they're addressed. -- Don Dwiggins "Solvitur Ambulando" Ashton-Tate, Inc. dwiggins@ashtate.a-t.com