Re: Definition of COTS Documentation

[Scott Havens <SHavens -at- ELCOTEL -dot- COM>]

Cam,

I don't think that's what I said.  What your customers "might reasonably be
expected to use or need" is not the same as "whatever the customer SAYS they
want or need."  As I pointed out in the sentence that followed, "(t)he
better you know your customers and what they REALLY do w/r/t/ your
equipment, the better you can judge what they need, and justify what you
provide."  I agree with your final statement, however; don't promise things
without knowing the consequences.  And don't leave it entirely up to the
customer to tell YOU what he wants.  Find out as much as you can about his
real needs, then YOU tell him what you're going to provide.

I don't think we really have much of a disagreement here.  Maybe it's just
the innate imprecision of the English language.  (Uh, oh, do I smell another
thread here?)

SRH

> ---Scott Havens <SHavens -at- ELCOTEL -dot- COM> wrote:
> >
> > Kate,
> >
> > In that case, I'd say that your customer ("COTS") documentation should
> > include whatever descriptive, operational, maintenance, and
> > troubleshooting information your customers might reasonably be
> > expected to use or need.
> >
> Wrong.  That puts you on the hook for whatever the customer says they
> want or need...
        <snip>
> Be careful what you promist without talking it over with your
> financial and legal people.
>
> Cam Whetstone
>
> _________________________________________________________
> DO YOU YAHOO!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> From ??? -at- ??? Sun Jan 00 00:00:00 0000=
> =
>


 From ??? -at- ??? Sun Jan 00 00:00:00 0000=