Path: utzoo!mnetor!uunet!littlei!ogcvax!pase
From: pase@ogcvax.UUCP (Douglas M. Pase)
Newsgroups: comp.software-eng
Subject: Naive Question
Message-ID: <1523@ogcvax.UUCP>
Date: 5 Jan 88 20:09:15 GMT
Reply-To: pase@ogcvax.UUCP (Douglas M. Pase)
Organization: Oregon Graduate Center, Beaverton, OR
Lines: 19

I have been exposed to a (small) number of different approaches to software
engineering in both commercial and academic settings.  However, it has been
a few years, and even so I was not satisfied with the approaches I used.
The approaches I used divided the software development into two parts: the
function, and the implementation.  This was usually reflected by having a
functional document of some type, which spelled out the intended functionality
and requirements of the software.  The second part was the documented code.
Different approaches had different formats for the information, and some
variation of the exact material to be included.

It seems more appropriate to divide the process into three sections --
functionality, *algorithm*, and implementation.  In the previous approaches,
the algorithm was not adequately serviced in either document, and was often
divided between the two.

QUESTION:  Does anyone know of an approach which *does* deal with each part
separately?  I am hoping for material which is readily available (articles
or books which are well known) rather than commercial products or obscure
titles.