Systems and software engineering — Software life cycle processes
Introduction: The complexity of software systems continues to increase to unprecedented levels. Technology change has led to new opportunities, but also to increased challenges for the organizations that create and utilise systems. There is a continuum of human-made systems from those that use little or no software to those in which software is the primary interest. It is rare to encounter a complex system without software, and all software systems require physical system elements (hardware) to operate, either as part of the software system-of-interest (SoI) or as an enabling system or infrastructure. These challenges exist throughout the life cycle of a system and at all levels of architectural detail. The purpose of this document is to provide a defined set of software life cycle processes. This document provides a common process framework for engineering the life cycle of systems created by humans, adopting a software engineering approach. Software engineering is an interdisciplinary approach and means to enable software. This document concerns software systems that are configured with software elements and with one or more of the following: hardware elements, data, humans, processes, services, procedures, and facilities. This document provides processes for use by acquirers, suppliers, and other stakeholders in the life cycle of a software system, such as developers, integrators, operators, maintainers, managers, quality managers, and users of software services and products. It covers
Scope: This document establishes a common framework for software life cycle processes. Its terminology can be referenced and applied across the software industry. It contains processes, activities and tasks that can be applied during the acquisition of a software system, product, or service and during the supply, development, operation, maintenance, and disposal of software products and services. This is accomplished through the involvement of stakeholders, with the goal of achieving customer satisfaction. This document includes those aspects of system definition needed to provide the context for software systems and services. This document also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project. This document is applicable to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customised, adaptable software systems. Software includes the software portion of firmware. It applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger more complex and complete systems of systems (SoS). The processes, activities, and tasks of this document can also be applied during the acquisition of a system that contains software. This document applies to the full life cycle of software systems, products, and services, including conception, development, operations, support, and retirement, and to their acquisition and supply, whether performed internally or externally to an organization. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document can be applied in organizations and software projects using a variety of formal engineering approaches. It is applicable for agile approaches and methods, which are most widely used for software development, sustainment, and maintenance, and which are believed to be more affordable and to deliver usable products more quickly. This document does not identify or require any specific software life cycle model, development methodology, method, mo