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.

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 document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or www.iec.ch/members_experts/refdocs).

IEEE Standards documents are developed within IEEE Societies and subcommittees of IEEE Standards Association (IEEE SA) Board of Governors. IEEE develops its standards through an accredited consensus development process, which brings together volunteers representing varied viewpoints and interests to achieve the final product. IEEE standards are documents developed by volunteers with scientific, academic, and industry-based expertise in technical working groups. Volunteers are not necessarily members of IEEE or IEEE SA 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.

ISO and IEC draw attention to the possibility that the implementation of this document may involve the use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not received notice of (a) patent(s) which may be required to implement this document. However, implementers are cautioned that this may not represent the latest information, which may be obtained from the patent database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held responsible for identifying any or all such patent rights.

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. In the IEC, see www.iec.ch/understanding-standards.

This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Systems and Software Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards Development Organization cooperation agreement between ISO and IEEE.

This second edition cancels and replaces the first edition (ISO/IEC/IEEE 24748-7:2019), which has been technically revised.

The main changes are as follows:

aligned content to ISO/IEC/IEEE 15288:2023 which was recently revised
converted from original IEEE Std format to ISO format
updated necessary defence specific language to include outputs
Added/updated defence references

A list of all parts in the ISO/IEC/IEEE 24748 series can be found on the ISO and IEC websites.

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 and www.iec.ch/national-committees.

Introduction

For effective and efficient application of ISO/IEC/IEEE 15288 on defence 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 defence projects that facilitate effective implementation of an acquirer-supplier agreement, such as use in defence contracts.

This document implements ISO/IEC/IEEE 15288 for application on defence programs, providing the defence-specific language and terminology to help ensure the correct application of acquirer-supplier requirements for a defence program. It 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. This document includes the expected or required outputs and associated attributes.

1 Scope

This document establishes the requirements for systems engineering activities to be performed on projects of defence agencies, including the United States (US) Department of Defense (DoD), across the entire system life cycle. This document implements ISO/IEC/IEEE 15288 for use by defence agencies in acquiring systems or systems engineering support, including the planning, acquisition, operation, modification, and sustainment of defence systems. It provides the foundation for systems engineering within the context of ISO/IEC/IEEE 15288. This document provides detailed requirements for the application of the life cycle processes, activities, and tasks of ISO/IEC/IEEE 15288 for use on any defence system and includes the effective integration of agreement processes, technical processes, technical management processes, organizational project enabling processes, and essential specialty engineering requirements. While primarily supporting the acquirer-supplier agreement mode, this document also can be used to support the other modes: use by organizations, projects, and process assessors.

2 Normative references

3 Terms, definitions and abbreviated terms

3.1 Terms and definitions

3.2 Abbreviated terms

4 Conformance

4.1 Intended usage

4.2 Full conformance

4.3 Tailored conformance

5 Key concepts and their application

5.1 General

5.2 System concepts

5.3 Organizational concepts

5.4 System of systems concepts

5.5 Life cycle concepts

5.6 Process concepts

5.7 Processes in this document

5.8 Process application

5.9 Concept and system definition

5.10 Assurance and quality characteristics

5.11 Process reference model

6 System life cycle processes

6.1 Agreement processes

6.2 Organizational project-enabling processes

6.3 Technical management processes

6.4 Technical processes

Bibliography