1、 IEEE Standard for Technical Reviews and Audits on Defense Programs Sponsored by the Software fitness for a particular purpose; non-infringement; and quality, accuracy, effectiveness, currency, or completeness of material. In addition, IEEE disclaims any and all conditions relating to: results; and
2、workmanlike effort. IEEE standards documents are supplied “AS IS” and “WITH ALL FAULTS.” Use of an IEEE standard is wholly voluntary. The existence of an IEEE standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related
3、 to the scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. In publishing and making its standards available, I
4、EEE is not suggesting or rendering professional or other services for, or on behalf of, any person or entity nor is IEEE undertaking to perform any duty owed by any other person or entity to another. Any person utilizing any IEEE Standards document, should rely upon his or her own independent judgme
5、nt in the exercise of reasonable care in any given circumstances or, as appropriate, seek the advice of a competent professional in determining the appropriateness of a given IEEE standard. IN NO EVENT SHALL IEEE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DA
6、MAGES (INCLUDING, BUT NOT LIMITED TO: PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
7、PUBLICATION, USE OF, OR RELIANCE UPON ANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE AND REGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE. Translations The IEEE consensus development process involves the review of documents in English only. In the event that an IEEE standard is tra
8、nslated, only the English version published by IEEE should be considered the approved IEEE standard. Official statements A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board Operations Manual shall not be considered or inferred to be the official positio
9、n of IEEE or any of its committees and shall not be considered to be, or be relied upon as, a formal position of IEEE. At lectures, symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall make it clear that his or her views should be considered the pe
10、rsonal views of that individual rather than the formal position of IEEE. Comments on standards Comments for revision of IEEE Standards documents are welcome from any interested party, regardless of membership affiliation with IEEE. However, IEEE does not provide consulting information or advice pert
11、aining to IEEE Standards documents. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Since IEEE standards represent a consensus of concerned interests, it is important that any responses to comments and questions
12、also receive the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant response to comments or questions except in those cases where the matter has previously been addressed. For the same
13、 reason, IEEE does not respond to interpretation requests. Any person who would like to participate in revisions to an IEEE standard is welcome to join the relevant IEEE working group. Comments on standards should be submitted to the following address: Secretary, IEEE-SA Standards Board 445 Hoes Lan
14、e Piscataway, NJ 08854 USA Laws and regulations Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with the provisions of any IEEE Standards document does not imply compliance to any applicable regulatory requirements. Implementers of the standard are re
15、sponsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be construed as doing so. Copyrights IEEE draft and approved standards
16、 are copyrighted by IEEE under U.S. and international copyright laws. They are made available by IEEE and are adopted for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promot
17、ion of engineering practices and methods. By making these documents available for use and adoption by public authorities and private users, IEEE does not waive any rights in copyright to the documents. Photocopies Subject to payment of the appropriate fee, IEEE will grant users a limited, non-exclus
18、ive license to photocopy portions of any individual standard for company or organizational internal use or individual, non-commercial use only. To arrange for payment of licensing fees, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; +1 978 750
19、 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. Updating of IEEE Standards documents Users of IEEE Standards documents should be aware that these documents may be superseded at any time by t
20、he issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the document together with any amendments, corrigenda, or errata then in effect. Every IEEE sta
21、ndard is subjected to review at least every ten years. When a document is more than ten years old and has not undergone a revision process, it is reasonable to conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautioned to check t
22、o determine that they have the latest edition of any IEEE standard. In order to determine whether a given document is the current edition and whether it has been amended through the issuance of amendments, corrigenda, or errata, visit the IEEE-SA Website at http:/ieeexplore.ieee.org/xpl/standards.js
23、p or contact IEEE at the address listed previously. For more information about the IEEE SA or IEEEs standards development process, visit the IEEE-SA Website at http:/standards.ieee.org. Errata Errata, if any, for all IEEE standards can be accessed on the IEEE-SA Website at the following URL: http:/s
24、tandards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errata periodically. Patents Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position i
25、s taken by the IEEE with respect to the existence or validity of any patent rights in connection therewith. If a patent holder or patent applicant has filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE-SA Website at http:/standards.ieee.org/a
26、bout/sasb/patcom/patents.html. Letters of Assurance may indicate whether the Submitter is willing or unwilling to grant licenses under patent rights without compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimination to applica
27、nts desiring to obtain such licenses. Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is not responsible for identifying Essential Patent Claims for which a license may be required, for conducting inquiries into the legal validity or scope of Patents
28、 Claims, or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the validity of any paten
29、t rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association. Copyright 2015 IEEE. All rights reserved. vi Participants At the time this IEEE standard was completed, the DoD Systems Engineering St
30、andardization Joint Working Group had the following membership: Garry Roedler, Chair David Davis, Vice Chair Bill Bearden Dave Berwald Tom Channell Dan Christensen Stephen Christensen Luke Daniels Geoff Draper John Evers Ronald Fradenburg Mark Henley Theresa Hunt Cheryl Jones Ed Matheson Revis Napie
31、r Larry Pennell Chris Ptachik Bob Scheurer John Schnackenberg Brian Shaw Zachary Taylor Gan WangThe following members of the individual balloting committee voted on this standard. Balloters may have voted for approval, disapproval, or abstention. Bill Bearden Bill Brown Susan Burgess William Byrd To
32、m Channell Dan Christensen Stephen Christensen Luke Daniels David Davis Robert Epps Alan Fitzmorris Ronald Fradenburg Randall Groves Denise Haskins Mark Henley Theresa Hunt Noriyuki Ikeuchi Hannibal Iyob Cheryl Jones Piotr Karocki Yuri Khersonsky Dewitt Latimer James Moore Edward Moshinsky Revis Nap
33、ier Olileanya Ogbonna Larry Pennell Chris Ptachik Annette Reilly William Riski Garry Roedler Bartien Sayogo Bob Scheurer John Schnackenberg Brian Shaw Carl Singer David Singleton John Snoderly Eugene Stoudenmire Walter Struppler Marcy Stutzman Michael Swearingen Zachary Taylor David Walden Gan Wang
34、Nancy Weaver Clifford Whitcomb Michael Yokell Matthew Young Kenneth Zemrowski David Zhong Copyright 2015 IEEE. All rights reserved. vii When the IEEE-SA Standards Board approved this standard on 10 December 2014, it had the following membership: John Kulick, Chair Jon Walter Rosdahl, Vice Chair Rich
35、ard H. Hulett, Past Chair Konstantinos Karachalios, Secretary Peter Balma Farooq Bari Ted Burse Clint Chaplain Stephen Dukes Jean-Phillippe Faure Gary Hoffman Michael Janezic Jeffrey Katz Joseph L. Koepfinger* David J. Law Hung Ling Oleg Logvinov T. W. Olsen Glenn Parsons Ron Peterson Adrian Stephen
36、s Peter Sutherland Yatin Trivedi Phil Winston Don Wright Yu Yuan *Member Emeritus Also included are the following nonvoting IEEE-SA Standards Board liaisons: Richard DeBlasio, DOE Representative Michael Janezic, NIST Representative Catherine Berger IEEE-SA Content Production and Management Malia Zam
37、an IEEE-SA Technical Program Operations Copyright 2015 IEEE. All rights reserved. viii Introduction This introduction is not part of IEEE Std 15288.2-2014, IEEE Standard for Technical Reviews and Audits on Defense Programs. For effective and efficient application of ISO/IEC/IEEE 15288 on defense pro
38、grams, additional requirements are needed for the assessment of those programs. ISO/IEC/IEEE 15288 is written in a general manner to address all types of systems and different modes of application. Thus, it does not have requirements specific to the use by defense projects that facilitate effective
39、implementation of an acquirer- supplier agreement, such as use in DoD contracts. This standard responds to the needs of DoD and other defense agencies to have more specific and detailed requirements for technical reviews and audits as part of the assessment of projects during the life cycle. The req
40、uirements and guidance in this standard have been written at the most general level possible so that they might meet not only DoDs needs but also those of other defense agencies, either by direct application or by tailoring for an agencys specific needs. This standard was developed with input from g
41、overnment and non-government resources. This standard does not supersede or supplant any other law, regulation, directive, contractual provision, or requirement. Accordingly, users of this standard must verify, conform and complete the technical review and audit of any governmental programs to meet
42、the requirements specified by the government at the time of the technical review and audit. The user is instructed to consult the governmental contact or commissioning party for specific instructions and requirements, which may be different from this standard. Users may also have to comply with othe
43、r applicable laws, regulations, and agency requirements in the undertaking and completion of any such technical reviews and audits, including but not limited to confidentiality, security clearance, access to protected areas, and document management. It is the users responsibility to determine all ap
44、plicable laws and requirements. Copyright 2015 IEEE. All rights reserved. ix Contents 1. Overview 1 1.1 Scope . 1 1.2 Purpose 1 1.3 Field of application 2 1.4 Organization of this standard . 2 1.5 Conformance . 3 2. Normative references 4 3. Definitions, acronyms, and abbreviations 4 3.1 Definitions
45、 . 4 3.2 Acronyms and abbreviations . 5 4. Overview of technical reviews and audits 9 4.1 Technical reviews and audits defined 9 4.2 The role of technical reviews and audits in the US DoD acquisition life cycle . 9 4.3 Technical reviews and audits in the context of Technical Management processes . 9
46、 4.4 Key participants for technical reviews and audits 10 4.5 Program considerations for technical reviews and audits .11 4.6 Media selection for products discussed in this standard .17 5. Requirements for technical reviews and audits .17 5.1 General .17 5.2 Alternative systems review (ASR) .19 5.3
47、System requirements review (SRR) 21 5.4 System functional review (SFR) .24 5.5 Preliminary design review (PDR) .26 5.6 Critical design review (CDR) .29 5.7 Test readiness review (TRR) 32 5.8 Functional configuration audit (FCA) 34 5.9 System verification review (SVR) 36 5.10 Production readiness rev
48、iew (PRR) 38 5.11 Physical configuration audit (PCA) 40 6. Detailed criteria to be addressed for each technical review and audit .43 6.1 General .43 6.2 Alternative systems review (ASR) detailed criteria 43 6.3 System requirements review (SRR) detailed criteria 48 6.4 System functional review (SFR)
49、detailed criteria .55 6.5 Preliminary design review (PDR) detailed criteria .60 6.6 Critical design review (CDR) detailed criteria .69 6.7 Test readiness review (TRR) detailed criteria 77 6.8 Functional configuration audit (FCA) detailed criteria .83 6.9 System verification review (SVR) detailed criteria 87 6.10 Production readiness review (PRR) detailed criteria 92 6.11 Physical configuration audit (PCA) detailed criteria 98 7. Technical review and audit application guidance for defense programs .103 7.1 General .103 7.2 Alternative systems review (ASR) application guidance103
