DOD-STD-2168

29 APiil 1988 SUPERSEDING MIL-S-52779A 1 August 1979

MILITARY
DEFENSE SOFTWARE

STANDARD
SYSTEM PROGRAM

QUALITY

. .-

AMSC NO. A4389 DISTRIBUTION STATEMENT A. Approved

AREA for public releaae: distribution iaunlimited.

QCIC

DOD-STD-2168

DEPARTMENT
Washington,

OF DEFENSE
D.C. 20301

Defense

System

Software

Quality

Program

1. This Military Defense.

Standard

is

approved

for

use

by

all

Depatiments

and

Agencies

of the Department

of

2. Beneficial comments (recommendations, additions, deletions) andanypertinent data which maybe of uae in improving this document should be addressed to: Ho /ARDEC/SMCAR-FSC, Picatinny Arsenal, NJ 0780&5000, byuaing theself-addresed Standardization Document improvement Proposal (DD Form 1426) appearing at the end of this document or by letter.

DOD-STD-2168

1. This sofhvare sofhvare, activities

standard contains requirements for the development, documentation, and implementation of a quality program. This program includes planning for and conducting evaluations of the quality of aaaociated documentation, and related activities, and planning for and conducting the follow-up necessary to assure timely and effective resolution of problems. military specifications and standards governing software specification practicea, project reviews and audits, and for achieving, deterfnining, and maintaining quality in software inco~orates theapphcable requirements of MlL-STD-1520 and

This standard, together with other 2. development, configuration management, subcontractor management, provide ameans andaasociated documentation. This standard MlL-STD-l 535.

3. This standard implements the policies of DODD 4155.1, Quality Program, and provides all of the quality program applicable to sofhvare development and S.UppOft. neceasa~ elements of a comprehensive
This standard interprets the applicable requirements of MIL-O-9858, Quality Program Requirements, for software.

4. The Data Item Description (DID) applicable to this standard is identified in Section 6. When used in conjunction with this standard, this DID provides avehicle for documenting and communicating information relevant to the requirements specified herein. Production of deliverable data using automated techniques is encouraged.

Ill

DOD-STD-2168

CONTENTS Paraaraoh

E6L9Q
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3 4

I. SCOPE. . . . . . . Purpose. . . . . . . . 1.1 1.2 Application. . . . . 1.2.1 Non-deliverablesoftware 1.2.2 Firmware. . . . . 1.2.3 Soffwaresupport . . 1.2.4 Governmentagencies. 1.3 Contractingagency. . . 1.4 Tailoring. . . . . 2.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . .

. . . . . .

. . . . . .

. . . . . . . . .

. . . . . . . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . . . .

. . . .

. . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . .

. . . . . . . . . . . . . . . . . . . . .

REFERENCEDDOCUMENTS. . . . . . . . . . . . . . . Governmentdocuments. . . . . . . . . . . . . . . . . 2.1 2.1.1 Specifications,standards,andhandbooks . . . . . . . 2.1.2 Other Government documen&, drawings, and publications. . . 2.2 Otherpublications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.DEFINITIONS . . . . . . . . . . . . . . . . Certification . . . . . . . . . . . 3.1 3.2 Evaluation. . . . . . . . . . . . . . Non-deliverablesoftware . . . . . . . . . 3.3 3.4 Softwareplans. . . . . . . . . . . . . . 3.5 Soflwarequality. . . . . . . . . . . . . 3.6 TermadefinedinDOD-STD-480 . . . . . . 3.7 TermsdefinedinDOD-STD-2167. . . . . . 3.6 Definitions of.acronyms used inthis standard 4.GENERALREQUIREMENTS. . . . . . . . . 4.1 Objectiveofthesofiwarequalityprogram . 4.2 Responaibilityforthesoftwarequalifyprogram 4.3 Documentationforthesoftwerequalityprogram. 4.4 Softwarequalityprogramplanning . . . 4.5 Softwarequalityprogramimpiementation. 4.6 Softwarequalityevaluationa. . . . . . 4.7 Sofhvarequalityrecords. . . . . . . . 4.7.1 Softwarequalityevaluationrecords. . 4.7.2 Othersoftwarequalityrecorda. . . . 4.8 Soflwarecorrectiveaction. . . . . . . 4.9 Certification . . . . . . . . . . . 4.10 Management review of thesoftware quality 4.11 Accessforcontracfingagencyreview .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . , . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . program. . . . .

. . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .
. .

5. DmAILEDREQulREMENTs . . . . . . . . . . . . . Evaluafionofsoftware. . . . . . . . . . . . 5.1 5.2 Evaluationofaofhvaredocumentation . . . . . . . . . . 5.2.1 Evaluationofsoftwareplans. . . . . . . . . .

. . . . . . . . . .
. . .

. . . . . . .
.

iv

DOD-STD-2168

CONTENTS Paraaraoh

- Continued Ea9!?

development. . . . 5.3 Evaluation of the processes used in software 5.3.1 Evaluation ofsoftware management . . . . . . . . . Evaluation ofsoftware engineering. . . . . . . . . . . . . 5.3.2 Evaluation ofsoftware qualification. . . . . . . . . . . . . 5.3.3 Evaluation of software configuration management. . . . 5.3.4 Evaluation of thesofkware corrective actions . . . . . . . . 5.3.5 Evaluation of documentation and media distribution . . . . . 5.3.6 Evaluation of storage, handling, and delivery . . . . . . . . 5.3.7 Evaluation of other processes used in software development. 5.3.8 5.4 Evaluation of the software development library . . . . . . . . . 5.5 Evaluation of non-developmental software . . . . . . . . . . 5.6 Evaluation ofnon-deliverable software . . . . . . . . . . . . . Evaluation of deliverable elements of the software engineering and 5.7 5.8 Evaluation of subcontractor management. . . . . . . . . . 5.9 Evaluations associated with acceptance inspection and preparation 5.10 Participation in formal reviews and audits . . . . . . . . . . . . 6. NOTES . . . . . . . . . . . . . . 6.1. intended use . . . . . . . . . 6.2, Datarequirements listand cross 6.3 Subject term(keyword) listing. . . . . . . . . . . reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . test environments . . . . . for delive~ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . .

4 4 4 4 4 4 4 4 5 5 5 5 5 5 6 6 6 6 6 6

. . . . . . . . . . . . . . . . .

DOD-STD-2168

1. SCOPE

2.

REFERENCED

DOCUMENTS

1.1 PuroOaQ. The purpose of this standard ia to establish requirements for a software quality program to be applied during the acquisition, development, and support of software systems. 1.2 Aoolication. This standard applies to the extent specified in the contract clauses, the Statement of Work (SOW), and the Contract Data Requirements I&t (CDRL). The term aoflware quality program requirements aa used herein refers to the collective requirements of this standard. Requirements 1.2.1 Non-deliverable software. for non-deliverable software are identified in paragraph 5.6. This standard applies to the 1.2.2 Firmware. software element of deliverable firmware. Paragraph 5.6 identifies requirements for the software element of non-deliverable firmware. Softwa r e SUODOQ. applied to software support, the term software development should be interpreted to mean software support, and the requirements of the standard apply to the organization performing the software support. 1.2.3 When this standard ia

2.1

Government

documents.

2.1.1 fiec ificat ions. sta ndards, and handbooks. otherwise specified, the following Unless specification, standarda, and handbooks of the issue listed in that issue of the Department of Defense Index of Specifications and Standards (DODISS) specified in the solicitation form a parl of this standard to the extent specified herein.

MILITARY STANDARDS DOD-STD-480 Configuration Control Engineering Changes, Deviationa, and Waivera Defense System Software Development

DOD-STD-2167

2.1.2 Other Go vemment docu ments. drawinas. ~nd oub lication~. The following other Government documents, drawings, and publications form a part of this standard to the extent specified herein. None. (Copies of specifications, standards, handbooks, drawings, and publications required by contractors in connection with specific acquisition functions should be obtained from the contracting activity or as directed by the contracting officer). 2.2 None. Other publications.

1.2.4 of Go vemment aa enciea. The provisions this standard may be applied to Government agencies. When a Government agency petforms software quality pmgrsm functibna in accordance with this standard, the term contractor refers to term that Government agency and the subcontractor refers to any contractor of that Government agency. 1.3 Contract ino a aencv. In each case in which this standard uaea the term contracting agency, it shall be interpreted to mesn contracting agency or its authorized representative. 1.4 Tailorinq. This Wandard containa a set of requirements designed to be tailored for each contract by the contracting agency. The tailoring process intended for this standard is the deletion of non-applicable requirements.

3. DEFINITIONS

A process, which may be 3.1 Certification. incremental, by which a contractor provides objective evidence to the contracting agency that an item satisfies its specified requirements. The 3.2 Evaluation. whether an item or criteria. process of determining activity meets specified

DOD-STD-2168

Software that 3.3 Non-deliverable so ftware. not required to be delivered by the contract.

is

A collective term used to 3.4 Sofhva re planS. describe the contractor% plans, procedures, and standards for sofhvare management, software qualification, software software engineering,
product management. evaluation, and software configuration

for the software auslity 4.2 Resoonsibilitv groaram. Contractor personnel responsible for ensuring compliance with the software quality program requirements shall have the resources, organizational respansibility, and authority, freedom to permit objective evaluations and to The initiate and verify corrective actions. persons conducting the evaluation of a product or activity shall nat be the persons who developed the product, performed the activity, or are responsible for the product or activity. This does nat preclude members of the development team The from participating in these evaluations. contractor shall assign responsibility for the fulfillment of, and for ensuring compliance with, the software quality program requirements. software 4.3 ouality Docu mentat ion for the proaram. The software quality program, including procedures, processes, and products, shall be documented in contractor format and shall provide implementing instructions for each of the requirements in sections 4 and 5 of this standard. The software quality program is subject to review by the contracting agency snd may ba disapproved by the contratilng agency whenever the program does not meet the requirements of the contract. The 4.4 Softwa re aua Iitv mo a ram Dlanninq. contractor shall conduct a complete review of the contract to identify and make timely provision for acquiring or developing the resources and skills required for implementing the software quality program. The contractor shall prepare the plans for applying the documerited softwsre quality program to the contract. These plsna shall be documented in a Software Quality Program Plan (SQPP). The contractor shall place the SQPP to prior under configuration control implementation. 4.5 s ~. are Ii The contractor shall implement the software quality program in accordance with the SQPP and shall adhere to the program for the duration of the contract. The software quality program shall be fully integrated with the activities required by the contract.

3.5 Software aua Iity. The ability of a software product to satisfy ita specified requirements. 3.6 Terms defined in DOD-STD-48Q. The following terms used in this standard are defined in DOD-STO-480 Baaeline Configuration Control 3.7 Terms defined in DOO-STD-21 87. The following terms used in this standard are defined in DOD-STD-216Z Computer software (or software) Computer software documentation Firmware Non-developmental software Qualification Software development library Software engineering environment Software suppott Software test environment 3.8 Definitions of ac ronvms used in this eta nda rd. The following acronyms are used in this standard: CDRL DID DOD DODD FAR SQPP Contract Data Requirements List Data Item Description Department of Defense Depatiment of Defense Directive Federal Acquisition Regulation Software Quality Program Plan

4. GENERAL

REQUIREMENTS

4.1 Qbiective of the softwa re a ualitv moaram. sotiare qualify The objective of the contractors program shall be to aaaure the quality of (a) deliverable software and its documentation, (b) the oroceaaes used to moduce deliverable software, and se specified in ~c) nondeliverab;e software, psragraph 5.6 of this standard.

DOD-STD-2168

4.6 so ftware aua Iitv evaluat ions. The contractor shall conduct on-going evaluations of the processes used in aofhvara development and the resulting and ssaociated documentation aa software These evaluations shall specified in Section 5. include a final evaluation of all sofhvare and associated documentation to assure that all contract requirements have been met and that in internal coordination has been conducted accordance with the soflware plans.

c.

Track the status of all problems detected in canying out the requirements of this standard.

4.9 Gert ification. The contractor shall maintain and make available to the contracting agency documented, objective evidence that the software and associated documentation and activities required by the contract meet contractual requirements. Management review of the sofhvare auality The contractor% management shall Sm29@ll review the software quality program at intervals as specified in the SQPP to assure that the program complies with the contract and adheres to the SQPP. 4.11 Access for contracting aaencv review. The contractor shall pravide the contracting agency with access ta contractor facilities for review of all sofhvare products and activities required by the contract to determine compliance with the contract. Contracting agen@ review shall not constitute acceptance, nor shall it in any way replace evaluation by the contractor or otherwise relieve the contractor of his responsibility to furnish acceptable software and associated documentation. 4.10

4.7 Software o ualitv recordq. The contractor shsll prepare and maintain records of soflware quality program activities required by the contract. The software quality records and software problem reports shall be made available for contracting agency review and shall be maintained for the life of the contract. The 4.7.1 Software a ualitv evaluation recorc~. contractor shall prepare a software quality evaluation record far each evaluation required by These records shall be in the the contract. contractors format and shall contain the following items as a minimum: a. b. :. Evaluation date. Evaluation participants. Evaluation criteria. Evaluation results including detected pmbiems, with reference to the appropriate software problem reporta, as applicable. Recommended corrective action. Qther softw are aua Iitv records.
quality format. records shall be prepared

5.DETAILED

REQUIREMENTS

e. 4.7.2
software

All

other
in the

contractors 4.8 or have shall

5.1 Evaluation of softwa re. The contractor shall conduct on-going evaluations of all software to assure that a. b. The software complies with the contract. The sofhvare plans. adheres to the software

act ion. When preblems $oftwa r e co rrective nonconformances with contract requirements been serve detected, se actions. Assure the that defect that and adverse input The they for shall the be documented contracto~s shall: initiated of the are to correct and and and software

corrective a.

contractor ia cauae

action the trends

defect,

5.2 Fvalu etion of sofhva re docu ment ation. The contractor shall conduct on-going evaluations of the follawing software documentation: 5.2.1 Evaluation of software cdans. The contractor shall evaluate the sofhvare plans to be The contractor shall used for the contract. assure that a. All software plans required have been documented. by the contract

identified

reversed.

b.

Monitor specified

the

software

corrective

actions,

se

in

paragraph

5.3.5,

to

assure

timely and positive corrective action.

DOD-STD-2168

b.

The

software

plans

comply

with

the

e.

contract.

All safhvare, hardware, firmware, facilities required for qualification available.

and are

c.

Each

software plans ion

plan and

is consistent with system-level

with

other

software 5.2.2 Evaluat

plans.

of other

softwa

The contractor shall evaluate documentation not covered paragraph to assure that a.

re docu mentat ion. deliverable software in the preceding

5.3.4 The contractor shall evaluate the ma naae ment. software configuration management practices to with the contract and assure compliance adherence to the saftware plans. f the orrectiv 5.3.5 Ev I ian ~? The contractor shall evaluate the a@!2QS. software corrective actians to assure that they comply with the software plans and thati a. All prablems detected in processes and in products that are under internal or contracting agency central are promptly into reported and entered software corrective actions. Each problem is classified, as required by the contract, and analysis ia performed to identify trends in the problems reported. Action on the problems and resolution is achieved, statua is tracked and reported, and records for the life of the are maintained contract. is initiated

Each document
format. Each document

adheres

to the

required

b.

complies with the contract.

5.3 ~Q Eval ati n f th s in sofhvar development. The contractor shall conduct ongoing evaluations of the following processes used in software development The 5.3.1 Evaluation of aoftw are management. contractor shall evaluate the sofhvare management practices to assure compliance with the cantract and adherence to the software plans. The 5.3.2 Evaluation of softwa re enaineerinq. contractor shall evaluate the software engineering prectices to assure compliance with the contract and adherence ta the software plans. 5.3.3 Evaluation of sofhvare au alificatiam The contractor shall evaluate the software qualification planning and conduct required by the cantract to assure that d. b.

c.

adverse trends,

Camective actions are evaluated to: (1) verify that problems have been resolved, (2) verify that adverse trends have been reversed, (3) verify that changes have been correctly implemented in the appropriate PrOceaaea and praducts, and (4) determine whether additional problems have been introduced.

a.

The qualification plans and procedures include provisions. for all sofhvare requirements. Soflware qualification is conducted aa required by the contract and aa specified in the software plans. The version number of each item being item used in the qualified and esch qualification is documented. The results of required qualifications are accurately recorded and analyzed ta determine whether the software meets its specified requirements.

b.

c.

Evaluat ion of docu mentat ion and media 5.3.6 @#ribution. The contractor shall evaluate the controls exercised on the internal distribution of deliverable media and documentation. The contractor shall assure compliance with the contract and adherence to the software plans. of staraae. Evaluation handlina. and shall evaluate the The contractor @!&Y. storage, handling, packaging, shipping, and external distribution of deliverable software and aseaciated documentation. The contractor shall assure with the contract and compliance adherence to the software plans. 5.3.7

d.

DOD-STD-2168

5.3.8 Evaluation of other cmoceases used in 7he contractor shall software development. evaluate all other processes used in software development that are required by the mntract to assure compliance with the contract and adherence to the software plans. 5.4 Evslu ation of the aoftwa re de velooment

o 0 deliverable e Iemen ts of t he Ev a Iuat inf The sotia re enoineerina and test environments. contractor shall evaluate each deliverable element of the software engineering and test environments to assure that

5.7

a. !MI!Y. me development a. cOntracfOr shall evaluate the sofiare libra~ to assure that

It complies with the contract and adheres to the software plans. Objective evidence exists, prior to its use, that t performs required functions. it was ptaced under internal configuration control prior to its use. The data rights provisions with the contract. are consistent

b.

The library and its operation comply with the contract and adhere to the software plans. The most recent authorized version of m,ateriala under mnfiguration control are clearly identified and are the onea routinely available from the library. of materfala under Previous veraiona configuration control are clearly identified and controlled to provide an audit trail that permits reconstruction of sII changes made to each configuration item.

c.

b.

d.

c.

5.8 Evaluat ion of subco ntracto r manaoe menf. The contractor shall evaluate all subcontractor activity to assure th~. a. All subcontractor developed software and related documentation deliverable ta the contracting agency aatiafies the prime contract requirements. A aet of beeelined requirements eatsbliahed and maintained for software to be developed by aubcontrector. is the the

5.5 Evaluat ion of non-de veloDmental software. The contractor shall evaluate each item of nondevelopmental aofhvare to be incorporated into deliverable software to assure that a. Objective evidence incorporation, that functions. exists, prior to its it performs required

b.

c.

b.

It wee placed under internal configuration control prior to its incorporation. d. The data rights provisions with the contract. are consistent e.

Applicable soflware qualty program requirements are included or referenced in the subcontract or purchase documents for the subcontractor. Access ia available for contractor reviews at subcontractor and vendor facilities. The contracting agency has the right to review all software products and activities required by the subcontract, at subcontractor facilities, to determine with compliance subcontract. the Contracting agency review shall not constitute acceptance, nor shall it in any way replace evaluation by the contractor or otherwise relieve the contractor of his responsibility to furnish acceptable sofhvare and associated documentation.

c.

5.6 .Evaluation of non-de Iiverable contractor shall evaluate each aofhvare item used in the automated of deliverable hardware or in the acceptance of deliverable software assure that a. Objective intended functions. evidence use, that

software. The nondeiiverable manufacturing qualification or or hardware to

exists, prior to its it perfomns required

b.

It wee placed

under

internal

configuration

control prior to its use.

DOD-STD-2168

with ~ 5,9 Evalu ationa associated insDe ction and Drewaration for delive!y. In suppoti of software acceptance inspection and preparation for delive~, the contractor shall assure that a. All required software products are available ready for and contracting agency inspection. All required procedures have been performed and evidence of satisfactory completion of these procedures is available for contracting agency inspection. All deliverable software and documentation has been updated to reflect all changes approved by the contracting scheduled for inclusion. 5.10 a. agency and

performed or uae of internal contractor systems for software quality program activities shall be documented in the SQPP. &2 Data reau irements list and cross reference. When this standard is used in an acquisition which incorporates a DD Form 1423, Contract Data Requirements List (CDRL), the data requirements Identified below shall be developed ss specified by an approved Data Item Description (DD Form 1664) and delivered in accordance with the approved CDRL incorporated into the When the provisions of the DOD contract. Federal Acquisition Regulation (FAR) Supplement 27.475-1 are invoked and the DD Form 1423 is not used, the data specified below shall be delivered by the contractor in accordance with the contract or purchase order requirements. Deliverable data required by this standard are cited in the following subparagraphs. ~ Data Reau irements Tit!e 4.4 Software Quality Program Plan (SQPP) DI-QCIC-80572

b.

c.

Particioation in formal reviews and aud i&..

Aoolicable DID No. preparations have been

(2).

(The Data Item Description related to this standard and identified in section 6 will be aPPraved and listed as such in DOD 5010.12-L, AMSDL. Capies of DIDa required by contractors in connection with specific acquisition functions shauld be oMained from the Naval Publications and Forms Center or as directed by the contracting officer.) 6.3 Sub iect term (kev word) listing. Evaluation Certification Software Soflware Quality Software Quality Program Software Quality Program Plan

I c.

At each formal review and audit, the contractor shall present an evaluation of the statua and quality of each of the development products reviewed. Following each formal review and audit, the contractor shall assure that all softwarerelated action items asaigned to the contractor have been performed.

6. NOTES

6.1 Intended usQ. In planning for the software qualitv program, it is Permissible for the contr&to; t; augment the activities required by the contract to satisfy internal requirements, aa long as the additional policies and procedures do nat conflict with the contract. It ia further intended that the contractor use existing internal systems for the software quality program to the extent that they satisfy the requirements of this standard. Any augmentation of the activities to be
6

DOD-STD-2168

Custodians: Navy Army Air Force

EC AR 10,26

Preparingactivity: Army - AR
QCIC-0072) (project

Reviewing Activities:
Navy Amry Air Force MC, TD, OM, SH, AS SC, CR, Ml, AV 02, 14, 15, 17,23,95

Agent:

Air Force - 10

INSTRUCTIONS:

In s mntinuing

effort tonuke our standardization documenbbetter, theDoD providen this formfor w in

mbmitting commenti andq ggestiau for improvements. AU tuemofmiiitary Andardization documenti are invited toprovide % formIMY ha detackd, folded along thelima indicated, taped along theloose edge (DO NOT STAPLE), and U-S such u wording which required int=metit ion, Wmailed. In block 6, ha M SPOCKICM pasible aboutPuticular problem toorigid, restrictive, loom, ambiguoua, orwasincompatible, arid give Propomd wordii changes which wouldalleviate the problems. Enter inblock 6 any remrks not related toaspecific paragraph ofthe document. If Mock7 u fried out, an acknowledge-nt wikl hamailed toYouwithin 30days tolet Youknowthat your comments mm received andam being considered.
SUggatiom

NOTE: Tbu formIMY not haused tomwmstcwiea ofdocuments, nortorequest waivers, deviations, orclarification of specifbtion requiremr.IIts on current contmti.COMIMII-submitted onthbform donot constitute orimply mtbmization ofthemfmermaddocument(t) ortoamendcontmctud requirements. to waiveany portion

(Fold alON tm Uln)

(Fold doll, this Ulw)

i UNITED STATES I I I
OFFICIAL BUSINE=

PENALTY FOR PRIVATE USE S300

BRusjNEssNoR~PL~HMAl}c
POSTAGE WILL BE PAID 8Y THE DEPARTMENT OF THE ARMY

HQ, AHOEC ATTN : SMCAR-FSC Picatinny Arsenal,

NJ

078065000

STANDARDIZATION
GOCUWINT NUMBER

DOCUMENT IMPROVEMENT PROPOSAL

(See Instndiom - Rfwrie Side)

DOD-STD-2168

Defense

System

Software

Quality

Program
4.TYPE OF ORGANIZATION (Mar4 .atu)

NAME OF SU8MllT1N0 ORGANIZATION

VENDOR

I I I I I

u
AOOREm@sms, cm. 8Sa* m cods)

I&En

MANUFACTURER

u
PROBLEM AREM * PNumb andWOrdlw.

0,,!4,spcC,/y,,

h wOdlllw

e.-{mtioknl.

1. R.

I
I

I
I
I i I I I

REMARKS

. .. -

I
,1 1 1

I
I
L

NAME 0.= SUBMITTER

d, Fimt, mu - OWIOIIOI

b.won~ TELEi=+tONE NUMBER (hd.d9 Am. C*) - Olxl.x!.l 8. DATE OF SUOMISSION(VYMMDD)

MAILING AOORESS (Shwd, CiSY, Stati. ZIP Co&l - OCMOOI

I I
-m
w

----LRR

. . . .
14zti

PREVIOUS EDITION ISO@.SOLETE.