Re: ada-c++ productivity

[depriest@dtoa1.dt.navy.mil (Depriest)]

In article <20600094@inmet> ryer@inmet.inmet.com writes:
>However, USUALLY design documents are only carefully read by
>separate IV&V contractors who only make sure that the document meets the
>standards for design documents.

I have recent experience with a major aircraft program under 2167 where
the organic IV&V agent (NWC China Lake) went over the design documents
with a fine-tooth comb and forced major improvements in the quality
of the _content_ - not just the compliance with the DID.

IMHO, the usefulness of the documentation produced by a developer is
directly related to how well the _customer_ understands what the documents
are for and how committed the _customer_ is to having them done:
   -  right,
   -  at the right time,
   -  for the right reasons.

I've been on both sides of the issue, and I know that I have a reluctance
to do things that I think have little added value to my tasking if the
customer doesn't express a real interest in them either. However, if
the customer believes in the 'why' of the tasks, I'm willing to do them
to the best of my ability as long as she's willing to pay.

This is a common issue in more than one facet of DoD contracting. We
face the same problems every time we ask for Logistic Support Analysis
(MIL-STD-1388).

- Mike DePriest (depriest@dtoa1.dt.navy.mil)
- Software Technology Branch Manager
- Naval Aviation Depot Jacksonville