Xref: utzoo comp.software-eng:4961 comp.specification:273 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!bionet!uwm.edu!spool.mu.edu!uunet!igor!yoda!jls From: jls@yoda.Rational.COM (Jim Showalter) Newsgroups: comp.software-eng,comp.specification Subject: Re: Program Specifications - What to require from programmers. Keywords: PROGRAM SPECIFICATION DOCUMENTATION Message-ID: Date: 1 Mar 91 23:07:20 GMT References: <1991Feb28.184021.22862@ms.uky.edu> Sender: news@Rational.COM Followup-To: comp.software-eng Lines: 13 Regarding specifications, I have always felt the right way to do it was to write the user's manual first, and make that the formal spec for the product. From the standpoint of the user, this is all that matters anyhow (I include system administrators in the user category). If the members of the user-community-to-be read the manual and don't like parts of it, you can make changes at very low cost. I'm told at least some divisions/projects at HP use/used this approach. -- ***** DISCLAIMER: The opinions expressed herein are my own. Duh. Like you'd ever be able to find a company (or, for that matter, very many people) with opinions like mine. -- "When I want your opinion, I'll beat it out of you."