ISO/IEC/IEEE 24748-7:2019

INTERNATIONAL ISO/IEC/
STANDARD IEEE
24748-7
First edition
2019-02
Systems and software engineering —
Life cycle management —
Part 7:
Application of systems engineering on
defense programs
Ingénierie des systèmes et du logiciel — Gestion du cycle de vie —
Partie 7: Application de l'ingénierie des systèmes aux programmes
de défense
Reference number
©
IEEE 2015
© IEEE 2015
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO or IEEE at
the respective address below or ISO’s member body in the country of the requester.
ISO copyright office Institute of Electrical and Electronics Engineers, Inc
CP 401 • Ch. de Blandonnet 8 3 Park Avenue, New York
CH-1214 Vernier, Geneva NY 10016-5997, USA
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org Email: stds.ipr@ieee.org
Website: www.iso.org Website: www.ieee.org
Published in Switzerland
© IEEE 2015 – All rights reserved
ii
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non‐governmental, in liaison with ISO and IEC, also
take part in the work. In the field of information technology, ISO and IEC have established a joint
technical committee, ISO/IEC JTC 1.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for
the different types of ISO documents should be noted (see www.iso.org/directives).
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEE‐SA) Standards Board. The IEEE develops its
standards through a consensus development process, approved by the American National Standards
Institute, which brings together volunteers representing varied viewpoints and interests to achieve
the final product. Volunteers are not necessarily members of the Institute and serve without
compensation. While the IEEE administers the process and establishes rules to promote fairness in
the consensus development process, the IEEE does not independently evaluate, test, or verify the
accuracy of any of the information contained in its standards.
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does
not constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT),
see www.iso.org/iso/foreword.html.
ISO/IEC/IEEE 24748‐7 was prepared by the Software & Systems Engineering Standards Committee
of the IEEE Computer Society (as IEEE Std 15288.1) and drafted in accordance with its editorial
rules. It was adopted, under the “fast‐track procedure” defined in the Partner Standards
Development Organization cooperation agreement between ISO and IEEE, by Joint Technical
Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems
engineering.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html.
© IEEE 2015 – All rights reserved
iii
IEEE Std 15288.1™-2014
IEEE Standard for Application of
Systems Engineering on Defense
Programs
Sponsor
Software & Systems Engineering Standards Committee
of the
IEEE Computer Society
Approved 10 December 2014
IEEE-SA Standards Board
Abstract: The requirements for the application of ISO/IEC/IEEE 15288, System Life Cycle
Processes for defense systems engineering needs are provided in this standard. This standard
implements ISO/IEC/IEEE 15288 for use by United States Department of Defense (DoD)
organizations and other defense agencies in acquiring systems or systems engineering
support. While primarily supporting the acquirer-supplier agreement mode, this standard also can
be used to support the other modes: use by organizations, projects, and process assessors. This
standard  provides  the basis for selection,  negotiation,  agreement,  and performance of
necessary systems engineering activities and delivery of products, while allowing flexibility for
both innovative implementation and tailoring of the specific systems engineering process(es) to
be used by system suppliers, either contractors or government system developers,
integrators, maintainers, or sustainers.
Keywords: 15288, acquisition, agreement processes, allocated baseline, attributes, defense
program, Department of Defense, functional baseline, IEEE 15288.1™, information management,
life cycle processes, organizational project-enabling processes, outputs, process activities,
process outcomes, process tasks, product baseline, project assessment, system life cycle,
systems engineering, technical management processes, technical processes
•
The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA
All rights reserved. Published 15 May 2015. Printed in the United States of America.
IEEE is a registered trademark in the U.S. Patent & Trademark Office, owned by The Institute of Electrical and Electronics
Engineers, Incorporated.
PDF: ISBN 978-0-7381-9533-9 STD20105
Print: ISBN 978-0-7381-9534-6 STDPD20105
IEEE prohibits discrimination, harassment, and bullying.
For more information, visit http://www.ieee.org/web/aboutus/whatis/policies/p9-26.html.
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission
of the publisher.
vi
© IEEE 2015 – All rights reserved

Important Notices and Disclaimers Concerning IEEE Standards Documents
IEEE documents are made available for use subject to important notices and legal disclaimers. These
notices and disclaimers, or a reference to this page, appear in all standards and may be found under the
heading “Important Notice” or “Important Notices and Disclaimers Concerning IEEE Standards
Documents.”
Notice and Disclaimer of Liability Concerning the Use of IEEE Standards
Documents
IEEE Standards documents (standards, recommended practices, and guides), both full-use and trial-use, are
developed within IEEE Societies and the Standards Coordinating Committees of the IEEE Standards
Association (“IEEE-SA”) Standards Board. IEEE (“the Institute”) develops its standards through a
consensus development process, approved by the American National Standards Institute (“ANSI”), which
brings together volunteers representing varied viewpoints and interests to achieve the final product.
Volunteers are not necessarily members of the Institute and participate without compensation from IEEE.
While IEEE administers the process and establishes rules to promote fairness in the consensus development
process, IEEE does not independently evaluate, test, or verify the accuracy of any of the information or the
soundness of any judgments contained in its standards.
IEEE does not warrant or represent the accuracy or content of the material contained in its standards, and
expressly disclaims all warranties (express, implied and statutory) not included in this or any other
document relating to the standard, including, but not limited to, the warranties of: merchantability; 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 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
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, 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 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 CONSEQUENTIAL 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 OF 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 is translated, only the English version published by IEEE should be considered the
approved IEEE standard.
vii
© IEEE 2015 – All rights reserved

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 position 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 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 advice
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 questions 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 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 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 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 standards 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 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-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 978 750 8400. Permission
to photocopy portions of any individual standard for educational classroom use can also be obtained
through the Copyright Clearance Center.
viii
© IEEE 2015 – All rights reserved

Updating of IEEE Standards documents
Users of IEEE Standards documents should be aware that these documents may be superseded at any time
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 IEEE 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 check 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/standards.jsp or contact IEEE at the address listed previously. For more
information about the IEEE SA or IEEE’s 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://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 position 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.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 applicants 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 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 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.
ix
© IEEE 2015 – All rights reserved

Participants
At the time this IEEE standard was completed, the DoD Systems Engineering Standardization Working
Group had the following membership:
Garry Roedler, Chair
David Davis, Vice Chair
William Bearden Geoff Draper Revis Napier
Dave Berwald John Evers Larry Pennell
Tom Channell Ronald Fradenburg Chris Ptachik
Daniel Christensen Theresa Hunt Bob Scheurer
Stephen Christensen Cheryl Jones John Schnackenberg
Penelope Cloft Steve Jones Brian Shaw
Luke Daniels Ed Matheson Zachary Taylor
Mike Davis 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 Hannibal Iyob John Schnackenberg
Bill Brown Cheryl Jones Brian Shaw
Susan Burgess Piotr Karocki Carl Singer
William Byrd Yuri Khersonsky John Snoderly
Tom Channell Dewitt Latimer Eugene Stoudenmire
Daniel Christensen Edward McCall Walter Struppler
Stephen Christensen James Moore Marcy Stutzman
Luke Daniels Edward Moshinsky Michael Swearingen
David Davis Revis Napier Zachary Taylor
Robert Epps Larry Pennell David Walden
Alan Fitzmorris Chris Ptachik Gan Wang
Ronald Fradenburg
Annette Reilly Nancy Weaver
Randall Groves William Riski Clifford Whitcomb
Denise Haskins Garry Roedler Michael Yokell
Mark Henley Bartien Sayogo Matthew Young
Theresa Hunt Bob Scheurer Kenneth Zemrowski
Noriyuki Ikeuchi Daidi Zhong
x
© IEEE 2015 – 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 Rosdahl, Vice Chair
Richard H. Hulett, Past Chair
Konstantinos Karachalios, Secretary
Peter Balma Michael Janezic Ron Peterson
Farooq Bari Jeffrey Katz Adrian Stephens
Ted Burse Joseph L. Koepfinger* Peter Sutherland
Clint Chaplain David J. Law Yatin Trivedi
Stephen Dukes Hung Ling Phil Winston
Jean-Phillippe Faure Oleg Logvinov Don Wright
Gary Hoffman
T. W. Olsen Yu Yuan
Glenn Parsons
*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 Zaman
IEEE-SA Technical Program Operations
xi
© IEEE 2015 – 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.
ISO/IEC/IEEE 15288
For effective and efficient application of on defense programs, additional
requirements are needed. ISO/IEC/IEEE 15288 is written in a general manner to address all
application
types of systems and different modes of application. Thus, it does not have requirements specific to the
effective implementation of an acquirer-supplier agreement, such
use by defense projects that facilitate
as use in defense contracts.
This standard implements for application on defense programs, providing the
ISO/IEC/IEEE 15288
defense-specific language and terminology to help ensure the correct application of acquirer-supplier
requirements for a defense program. This standard includes the expected/required outputs and
associated attributes
.
xii
© IEEE 2015 – 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 . 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 Process 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) 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 modeling .49
Annex G (informative) Application of system life cycle process to a system of systems .50
Annex H (informative) Bibliography .51
xiii
© IEEE 2015 – All rights reserved

IEEE Standard for Application of
Systems Engineering on Defense
Programs
IMPORTANT NOTICE: IEEE Standards documents are 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, 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 “Important 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 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/IEEE 15288 and 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 standard implements ISO/IEC/IEEE 15288 for use by DoD organizations and other
defense agencies in acquiring systems or systems engineering support. While primarily supporting the
Information on normative references can be found in Clause 2.
© IEEE 2015 – All rights reserved

IEEE Std 15288.1-2014
IEEE Standard for Application of Systems Engineering on Defense Programs
acquirer-supplier agreement mode, this standard also can be used to support the other modes: use by
organizations, projects, and process assessors. This standard provides the basis for selection, negotiation,
agreement, and performance of necessary systems engineering activities and delivery of products, while
allowing flexibility for both innovative implementation and tailoring of the specific systems engineering
process(es) to be used by system suppliers, either contractors or government system developers, integrators,
maintainers, or sustainers.
1.3 Conformance
1.3.1 Intended usage
ISO/IEC/IEEE 15288:2015 2.1 “Intended usage” shall apply.
1.3.2 Full conformance
1.3.2.1 Full conformance to outcomes
ISO/IEC/IEEE 15288:2015 2.2.1 “Full conformance to outcomes” shall apply.
1.3.2.2 Full conformance to tasks
ISO/IEC/IEEE 15288:2015 2.2.2 “Full conformance to tasks” shall apply.
1.3.3 Tailored conformance
ISO/IEC/IEEE 15288:2015 2.3 “Tailored conformance” shall apply with the following additions:
The agreement between the acquirer and supplier shall include the systems engineering requirements based
on the tailoring (or other adaptation) of the requirements of this standard to address the program situation.
The assessment of the supplier is based on the compliance to the agreement. The agreement shall include
the means by which compliance will be determined (which may include accomplishment of outcomes,
completion of tasks, or delivery of outputs).
NOTE—The acquirer request for proposal may include the intended tailoring (or other adaptation) of the systems
engineering requirements from this standard. The supplier may propose changes or alternatives during the steps to
finalize the agreement.
2. Normative references
The following referenced documents are indispensable for the application of this document (i.e., they must
be understood and used, so each referenced document is cited in text and its relationship to this document is
explained). For dated references, only the edition cited applies. For undated references, the latest edition of
the referenced document (including any amendments or corrigenda) applies.
© IEEE 2015 – All rights reserved

IEEE Std 15288.1-2014
IEEE Standard for Application of Systems Engineering on Defense Programs
IEEE Std 15288.2™-2014, IEEE Standard for Technical Reviews and Audits on Defense Programs.
ISO/IEC/IEEE 15288:2015(E), Systems and software engineering—System life cycle processes.
SAE/EIA-649-1 (2014), Configuration Management Requirements for Defense Contracts.
3. Definitions, acronyms, and abbreviations
3.1 Definitions
For the purposes of this document, the following terms and definitions apply. The IEEE Standards
Dictionary Online should be consulted for terms not defined in this clause.
allocated baseline: The approved requirements for a product, subsystem or component, describing the
functional, performance, interoperability, and interface requirements that are allocated from higher-level
requirements and the verifications required to demonstrate achievement of those requirements, as
established at a specific point in time and documented in the allocated configuration documentation. (SAE/
EIA-649-1).
baseline: (A) noun: A formally controlled and maintained set of data that serves as the basis for defining
change. (B) verb: To establish and approve a set of data. (Adapted from SAE/EIA-649-1.)
NOTE—This standard uses the noun form of baseline to refer only to configuration baselines managed by the
configuration management process, including the functional baseline, allocated baseline, and product baseline. It does
not refer to other baselines used in DoD such as the acquisition program baseline.
configuration item: Any system element or aggregation of system elements that satisfies an end use
function and is designated by the acquirer for separate configuration control. (Adapted from SAE/EIA-649-
1.)
functional baseline: Describes the system’s performance (functional, interoperability, and interface
characteristics) and the verification required to demonstrate the achievement of those specified
characteristics. (SAE/EIA-649-1)
NOTE—The functional baseline is directly traceable to the operational requirements contained in the initial capabilities
document or equivalent document.
product baseline: Describes the detailed design at a specific point in time, for production,
fielding/deployment, and operations and support. (SAE/EIA-649-1)
IEEE publications are available from The Institute of Electrical and Electronics Engineers, 445 Hoes Lane, Piscataway, NJ 08854,
USA (http://standards.ieee.org/).
ISO/IEC publications are available from the ISO Central Secretariat, 1, ch. de la Voie-Creuse, CP 56, CH-1211 Geneva 20,
Switzerland (http://www.iso.org/). ISO/IEC publications are available in the United States from the American National Standards
Institute, 25 West 43rd Street, 4th Floor, New York, NY 10036, USA (http://www.ansi.org/).
SAE publications are available from the Society of Automotive Engineers, 400 Commonwealth Drive, Warrendale, PA 15096, USA
(http://www.sae.org/).
IEEE Standards Dictionary Online subscription is available at:
http://www.ieee.org/portal/innovate/products/standard/standards_dictionary.html.
Notes in text, tables, and figures of a standard are given for information only and do not contain requirements needed to implement
this standard.
© IEEE 2015 – All rights reserved

IEEE Std 15288.1-2014
IEEE Standard for Application of Systems Engineering on Defense Programs
NOTE 1— The product baseline prescribes all necessary physical (form, fit, or function) characteristics and selected
functional characteristics designated for production acceptance testing and production test requirements.
NOTE 2— The product baseline is also known as the product configuration baseline. It is intended as the production
configuration.
system effectiveness analysis: An analytical approach used to determine how well a system performs in its
intended utilization environment.
3.2 Acronyms and abbreviations
The following acronyms and abbreviations appear in this standard:
CAPE cost assessment and program evaluation
CDR critical design review
CDRL contract data requirements list
CI configuration item
CM configuration management
CWBS contract work breakdown structure
DEMIL demilitarization
DIA Defense Intelligence Agency
DISR DoD Information Technology Standards Registry
DoD Department of Defense
DoDAF DoD architecture framework
DT&E developmental test and evaluation
ECP engineering change proposal
ECR engineering change request
ESOH environment, safety, and occupational health
EVM earned value management
FMECA failure mode, effects, and criticality analysis
GFE government-furnished equipment
GFI government-furnished information
IMP integrated master plan
IMS integrated master schedule
IOT&E initial operational test and evaluation
JCIDS Joint Capabilities Integration and Development System
LCSP life cycle sustainment plan
NDI non-development item
OpsCon operational concept
PDR preliminary design review
PSA product support analysis
SEMP systems engineering management plan
SEP systems engineering plan
SIP system integration plan
© IEEE 2015 – All rights reserved

IEEE Std 15288.1-2014
IEEE Standard for Application of Systems Engineering on Defense Programs
SOO statement of objectives
SoS system of systems
SOW statement of work
TPM technical performance measures
US United States
WBS work breakdown structure
4. This clause is a placeholder to align clauses with ISO/IEC/IEEE 15288
5. Key concepts and application of this international standard
5.1 Introduction
ISO/IEC/IEEE 15288:2015 5.1 “Introduction” applies as stated.
5.2 System concepts
5.2.1 Systems
ISO/IEC/IEEE 15288:2015 5.2.1 “Systems” applies as stated.
5.2.2 System structure
ISO/IEC/IEEE 15288:2015 5.2.2 “System structure” applies as stated.
5.2.3 Enabling systems
ISO/IEC/IEEE 15288:2015 5.2.3 “Enabling systems” applies as stated.
5.3 Organization and project concepts
5.3.1 Organizations
ISO/IEC/IEEE 15288:2015 5.3.1 “Organizations” applies as stated.
5.3.2 Organization and project-level adoption
ISO/IEC/IEEE 15288:2015 5.3.2 “Organization and project-level adoption” applies as stated.
© IEEE 2015 – All rights reserved

IEEE Std 15288.1-2014
IEEE Standard for Application of Systems Engineering on Defense Programs
5.4 Life cycle concepts
5.4.1 System Life Cycle Model
ISO/IEC/IEEE 15288:2015 5.4.1 “System Life Cycle Model” applies as stated.
NOTE—For use in US DoD programs, see Operation of the Defense Acquisition System (DoDI 5000.02) [B4] for a
discussion of the DoD System Life Cycle Model. For use on other defense programs, refer to the applicable life cycle
model of the acquisition organization.
5.4.2 System life cycle stages
ISO/IEC/IEEE 15288:2015 5.4.2 “System life cycle stages” applies as stated.
NOTE—For use in US DoD programs, see Operation of the Defense Acquisition System (DoDI 5000.02) [B4] for a
discussion of the DoD system life cycle stages. For use on other defense programs, refer to the applicable life cycle
model of the acquisition organization.
5.5 Process concepts
5.5.1 Criteria for processes
ISO/IEC/IEEE 15288:2015 5.5.1 “Criteria for processes” applies as stated.
5.5.2 Description of processes
ISO/IEC/IEEE 15288:2015 5.5.2 “Description of processes” applies as stated with the following addition:
For the DoD application, each process includes systems engineering outputs with attributes.
5.5.3 General characteristics of processes
ISO/IEC/IEEE 15288:2015 5.5.3 “General characteristics of processes” applies as stated.
5.5.4 Tailoring
ISO/IEC/IEEE 15288:2015 5.5.4 “Tailoring” applies as stated.
5.6 Processes in this standard
5.6.1 Introduction
ISO/IEC/IEEE 15288:2015 5.6.1 “Introduction” applies as stated.
The numbers in brackets correspond to those of the bibliography in Annex H.
© IEEE 2015 – All rights reserved

IEEE Std 15288.1-2014
IEEE Standard for Application of Systems Engineering on Defense Programs
5.6.2 Agreement processes
ISO/IEC/IEEE 15288:2015 5.6.2 “Agreement processes” applies as stated.
5.6.3 Organizational project-enabling processes
ISO/IEC/IEEE 15288:2015 5.6.3 “Organizational project-enabling processes” applies as stated.
5.6.4 Technical management processes
ISO/IEC/IEEE 15288:2015 5.6.4 "Technical management processes" applies as stated.
5.6.5 Technical processes
ISO/IEC/IEEE 15288:2015 5.6.5 “Technical processes” applies as stated.
5.7 Process application
ISO/IEC/IEEE 15288:2015 5.7 “Process application” applies as stated with the following addition:
Project Planning, System Analysis, and Project Assessment and Control are key systems engineering
processes, with emphasis on their contribution to enabling technical decision making. These processes
coordinate and control the performance of the other processes across the life cycle for the systems
engineering application. This set of process applications:
 Identifies the work to be performed and develops schedules and costs estimates for the effort.
 Coordinates the other process activities and helps ensure that all are operating from the same set of
agreements and system definition iteration.
 Evaluates the outputs of the other activities and conducts independent studies to determine which
alternate approach is best suited to the application.
 Determines when results of one activity require the action of another activity and directs the action
to be performed.
 Documents the results of analyses and studies, maintains control of the evolving configuration, and
measures and reports progress.
The success of any project or program is dependent upon the systems engineering planning and control of
the project and its processes. Project Planning not only contributes to planning the work to be performed
and the schedule for the effort, it is used to plan how all the other technical and technical management
processes will be employed throughout the system life cycle. Planning and control of the systems
engineering processes includes all of the other technical management processes.
The systems engineering control function is dependent upon the analyses (requirements analysis, tradeoff
studies, or design analysis) of the data and information upon which to base decisions. These analyses,
conducted for each iteration of the systems engineering processes, are performed to support any of the
Technical Management processes (5.3) and the Technical processes (5.4) that require the analytical data to
support decisions. Also, note that performance of the processes focused on concept and system definition
© IEEE 2015 – All rights reserved

IEEE Std 15288.1-2014
IEEE Standard for Application of Systems Engineering on Defense Programs
require input from processes that focus on system realization, deployment, and use. All this needs to be
accomplished across the life cycle. Figure 1 illustrates the interrelationships among these clauses.
Continual planning, assessment and control
Technical Management Processes Clauses 6.3.1 – 6.3.8
across all processes and life cycle stages
Project
Project Risk Decision Configuration Information Quality
Assessment & Measurement
Planning Management Management Management Management Assurance
Control Clause 6.3.7
Clause 6.3.1 Clause 6.3.4 Clause 6.3.3 Clause 6.3.5 Clause 6.3.6 Clause 6.3.8
Clause 6.3.2
Invoked by
Org. Project Enabling Processes Clauses
processes
6.2.1 –
Portfolio Knowledge
6.2.6
as needed
Management Management
…
throughout life
Clause 6.2.3 Clause 6.2.6
cycle for trades
System System Deployment and Use
Analysis
Operation
Technical Processes Transition
Clause 6.4.6
Clause 6.4.10 Clause 6.4.12
Clauses 6.4.1 - 6.4.14
Definition and Modification Loop
Maintenance Disposal
Clause 6.4.14
Clause 6.4.13
Concept Definition
Stakeholder Needs and
Business or Mission Analysis
Clause 6.4.1 Requirements Definition
System Realization
Clause 6.4.2
Validation
Validation
Clause 6.4.11
Loop
System Definition
Functional
Verification
System Baseline
Clause 6.4.9
Requirements
Allocated
Architecture
Definition
Baseline
Definition
Clause 6.4.3
Clause 6.4.4 Integration
Verification and Integration Loops
Clause 6.4.8
Implementation
Design Definition Product
Clause 6.4.7
Baseline
Clause 6.4.5
(Initial & Final)
Figure 1 —Systems engineering planning, assessment, and control interfaces
with the systems engineering technical activities
5.8 Process reference model
ISO/IEC/IEEE 15288:2015 5.8 “Process reference model” applies as stated.
6. System life cycle processes
6.1 Agreement processes
The Agreement processes description from ISO/IEC/IEEE 15288:2015 applies as stated with the following
additions:
NOTE—The acquirer-supplier agreement developed by the Agr
...