Re: 2167A

[Ken Garlington <73672.2025@COMPUSERVE.COM>]

Lee_Robert_Willis@CUP.PORTAL.COM writes:

<< Usually the tailoring must be done way in advance.... It has been my
unfortunate experience that the people involved before phase X don't know or
give a damn about the 2167A docs for phase X, and thus very little tailoring
happens. >>

Sounds like a lousy customer. We're on rev. "C" of our F-22 SDP, and we've done
lots of Just In Time tailoring. It also helps if you've got some experience
with mil-spec contracts, so you know in advance what's worthless ;)

Trying to maintain some semblance of Ada relevance, we've got an optional
tailoring of Section 4 (Detailed Design) of the SDD that's built from the Ada
code. We use the Cadre a_reveng tool to build Ada Structure Graphs from
suitable collections of Ada units, and then use a feature called Active Links
in our Interleaf documents to extract Ada source code (with appropriate
comments describing requirements traceability, etc.) from the CM system, format
it, and put it in the document at the right paragraph with all the security
markings automatically generated from the comments. Once you have the structure
of the document set up, the document updates itself. We can also build
identifier indexes, requirements traceability tables, etc. right from the code.
Very low-cost approach to produce good-looking (and current!) documentation.