From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: Wed, 6 May 1992 15:15 EDT
From: SAHARBAUGH@ROO.FIT.EDU
Subject: Reference to SPC Guidlines in SRS?
Message-ID: <9205061916.AA04261@ajpo.sei.cmu.edu>
List-Id: <comp.lang.ada>

Imagine that you are perfroming system analysis, system
design etc. and you are writing a software requirements
specification (SRS) per 2167A.  Imagine that you know
Ada and are familiar with the Software Productivity
Consortium's Ada style guide, version 2.  The question is:
What, if any, reference do you make to the SPC guideline
in the SRS?  I can imagine the following answers:
1. In the quality section say that the SPC book shall
be utilized with interpretations and choices specified in
the Software Design Document (SDD).
2. In the quality section of the SRS state all of the
choices and options from the SPC book that are to be used.
3. same as either 1 or 2 but refer to a separate document
with project specific or company specific choices
and interpretations.
4. Be silent in the SRS and put references to SPC book in
the SDP (software development plan).
5. Be silent totally on the SPC book and mention it
for the first time in the SDD.

   I am soliciting experience/opinions.  This will benefit
an Air Force project and I will not charge them for
any of your opinions/suggestions that I use and therefore
WE will save money, etc. etc. (I think its called reuse,
or maybe its laziness hmmm!).  Thanks in advance.
   to SPC personnel: Maybe you have a document called:
"Referencing and Utilizing the SPC Ada Stylebbok on
DoD Projects" or something like that.  If necessary I
can show traceability to an SPC member company.   

sam harbaugh
---