Re: User documentation as product specs?

Subject: Re: User documentation as product specs?
From: David Ibbetson <ibbetson -at- IDIRECT -dot- COM>
Date: Sat, 20 Apr 1996 16:48:53 -0400

An electronics company I met in England as a result of a merger (we found
ourselves in the same group) started any project, hardware, software, or
whatever, by breaking the product into modules and defining every interface
before anything else was done. This explicitly included at one end the
man-computer interface and at the other end the interface between the
computer and whatever (printer, traffic-signals, fly-by-wire aircraft
This way of proceeding was new to my division. We adopted it and found that
it worked very well. Among other things, with well-defined interfaces the
people working on the various parts could get on with their jobs with the
minimum of interference from people working on other parts. (It's better to
have too much parameter space than too little and too many defined
parameters than too few!)

"Many terms which have now dropped out of favour will be revived, and those
that are at present respectable will drop out, if usage so choose, with whom
lies the decision, the judgement, and the rule of speech" -- Horace, _Ars

David Ibbetson, 133 Wilton St, #506, Toronto, M5A 4A4
ibbetson -at- idirect -dot- com (416)363-6692 fax (416)363-4987

Post Message: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Get Commands: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "help" in body.
Unsubscribe: LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU with "signoff TECHWR-L"
Listowner: ejray -at- ionet -dot- net

Previous by Author: Eudora
Next by Author: Salaries?
Previous by Thread: Re: User documentation as product specs?
Next by Thread: Certificates, diplomas, etc.

What this post helpful? Share it with friends and colleagues:

Sponsored Ads

Sponsored Ads