1、 IEEE Standard for Application of Systems Engineering 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
2、; and 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 r
3、elated 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 availa
4、ble, IEEE 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
5、judgment 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 CONSEQUENT
6、IAL DAMAGES (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 O
7、F THE 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
8、is translated, 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 p
9、osition 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
10、the personal 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 advic
11、e pertaining 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 ques
12、tions 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 th
13、e same 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 Ho
14、es Lane 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
15、are responsible 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 sta
16、ndards 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
17、promotion 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-
18、exclusive 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 9
19、78 750 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 tim
20、e by the 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 IE
21、EE standard 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 c
22、heck to 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/standa
23、rds.jsp 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: h
24、ttp:/standards.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 posi
25、tion is 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
26、.org/about/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 a
27、pplicants 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 P
28、atents 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
29、 patent 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 Engineer
30、ing Standardization Working Group had the following membership: Garry Roedler, Chair David Davis, Vice Chair William Bearden Dave Berwald Tom Channell Daniel Christensen Stephen Christensen Penelope Cloft Luke Daniels Mike Davis Geoff Draper John Evers Ronald Fradenburg Theresa Hunt Cheryl Jones Ste
31、ve Jones Ed Matheson Revis Napier Larry Pennell Chris Ptachik Bob Scheurer John Schnackenberg Brian Shaw Zachary Taylor Gan Wang The following members of the individual balloting committee voted on this standard. Balloters may have voted for approval, disapproval, or abstention. William Bearden Bill
32、 Brown Susan Burgess William Byrd Tom Channell Daniel 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
33、 Edward McCall James Moore Edward Moshinsky Revis Napier Larry Pennell Chris Ptachik Annette Reilly William Riski Garry Roedler Bartien Sayogo Bob Scheurer John Schnackenberg Brian Shaw Carl Singer John Snoderly Eugene Stoudenmire Walter Struppler Marcy Stutzman Michael Swearingen Zachary Taylor Dav
34、id Walden Gan Wang Nancy Weaver Clifford Whitcomb Michael Yokell Matthew Young Kenneth Zemrowski Daidi Zhong vii Copyright 2015 IEEE. All rights reserved. When the IEEE-SA Standards Board approved this standard on 10 December 2014, it had the following membership: John Kulick, Chair Jon Walter Rosda
35、hl, Vice Chair Richard 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 Pete
36、rson Adrian Stephens 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 M
37、anagement Malia Zaman IEEE-SA Technical Program Operations viii Copyright 2015 IEEE. All rights reserved. Introduction This introduction is not part of IEEE Std 15288.1-2014, IEEE Standard for Application of Systems Engineering on Defense Programs. For effective and efficient application of ISO/IEC/
38、IEEE 15288 on defense programs, additional application requirements are needed. 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 defense contracts. This standard implements ISO/IEC/IEEE 15288 for application on defense programs, providing the defense-specific language and terminology to help ensure the correct application of acquirer-supplier requirements for a
40、defense program. This standard includes the expected/required outputs and associated attributes. ix Copyright 2015 IEEE. All rights reserved. Contents 1. Overview 1 1.1 Scope . 1 1.2 Purpose 1 1.3 Conformance . 2 2. Normative references 2 3. Definitions, acronyms, and abbreviations 3 3.1 Definitions
41、 . 3 3.2 Acronyms and abbreviations . 4 4. This clause is a placeholder to align clauses with ISO/IEC/IEEE 15288 . 5 5. Key concepts and application of this international standard 5 5.1 Introduction . 5 5.2 System concepts 5 5.3 Organization and project concepts . 5 5.4 Life cycle concepts 6 5.5 Pro
42、cess concepts 6 5.6 Processes in this standard 6 5.7 Process application 7 5.8 Process reference model 8 6. System life cycle processes 8 6.1 Agreement processes . 8 6.2 Organizational Project-Enabling processes 10 6.3 Technical Management processes 14 6.4 Technical processes 24 Annex A (normative)
43、Tailoring process 44 Annex B (informative) Example process information items .45 Annex C (informative) Process reference model for assessment purposes .46 Annex D (informative) Process integration and process constructs 47 Annex E (informative) Process views .48 Annex F (informative) Architecture mo
44、deling 49 Annex G (informative) Application of system life cycle process to a system of systems .50 Annex H (informative) Bibliography 51 1 Copyright 2015 IEEE. All rights reserved. IEEE Standard for Application of Systems Engineering on Defense Programs IMPORTANT NOTICE: IEEE Standards documents ar
45、e not intended to ensure safety, security, health, or environmental protection, or ensure against interference with or from other devices or networks. Implementers of IEEE Standards documents are responsible for determining and complying with all appropriate safety, security, environmental, health,
46、and interference protection practices and all applicable laws and regulations. This IEEE document is made available for use subject to important notices and legal disclaimers. These notices and disclaimers appear in all publications containing this document and may be found under the heading “Import
47、ant Notice” or “Important Notices and Disclaimers Concerning IEEE Documents.” They can also be obtained on request from IEEE or viewed at http:/standards.ieee.org/IPR/disclaimers.html. 1. Overview 1.1 Scope This standard establishes the requirements for systems engineering activities to be performed
48、 on projects of the United States (US) Department of Defense (DoD) and other defense agencies across the entire system life cycle, including the planning, acquisition, modification, and sustainment of defense systems. It provides the foundation for systems engineering within the context of ISO/IEC/I
49、EEE 152881and the acquisition environment of DoD and other defense agencies at all levels of system hierarchy. This standard provides detailed requirements for the application of the life cycle processes, activities, and tasks of ISO/IEC/IEEE 15288 for use on any defense system and includes the effective integration of agreement processes, technical processes, technical management processes, and essential specialty engineering requirements. 1.2 Purpose This standard provides requirements for the application of ISO/IEC/IEEE 15288 for defense systems engineering needs. This stan
