This standard draws on IEEE Std 12207(TM)-2008 to describe system and software reuse processes.1 It describes the relationship of reuse processes to system life cycle processes described in Clause 6 (System Life Cycle Processes) of IEEE Std 12207-2008 and software life cycle processes described in Clause 7 (Software Specific Processes) of IEEE Std 12207-2008. The standard defines processes and specifies requirements for the processes but does not specify particular techniques. The scope of the… read more specified processes is broader than that of IEEE Std 12207-2008 because reuse activities transcend the life cycle of any particular system. The specified processes are suitable on an organization-wide basis. read less
This standard establishes requirements for initiating, planning, controlling, and executing the Software Quality Assurance (SQA) processes of a software development or maintenance project. This standard is harmonized with the software life cycle process of ISO/IEC/IEEE 12207:20081 and the information content requirements of ISO/IEC/IEEE 15289:2011. NOTE—Annex A presents detailed explanations and mappings between ISO/IEC/IEEE 12207:2008 and IEEE Std 730-2014 subclauses. NOTE--Annex A presents… read more detailed explanations and mappings between ISO/IEC/IEEE 12207:2008 and IEEE Std 730(TM)-2014 subclauses. read less
This standard establishes requirements for initiating, planning, controlling, and executing the software quality assurance processes of a software endeavor. This standard is consistent with and elaborates on the software life cycle processes specified in ISO/IEC/IEEE 12207-2017 and the information content requirements of ISO/IEC/IEEE 15289:2019.
This document establishes a set of process descriptions for the governance and management of a collection of architectures and the architecting of entities. This document also establishes an enablement process description that provides support to these other architecture processes. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects. These processes are applicable throughout the life of an architecture or a… read more collection of architectures. These processes are applicable for managing and performing the activities within any stage in the life cycle of the architecture entities. Annex D describes the relationships between this document and other standards. read less
This International Standard establishes a common framework for software life cycle processes, with well defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software system, product or service and during the supply, development, operation, maintenance and disposal of software products. This is accomplished through the involvement of stakeholders, with the ultimate goal of achieving… read more customer satisfaction. This International Standard applies to the acquisition of software systems, products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of any system, whether performed internally or externally to an organization. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software products and services are included. This International Standard also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project. The processes, activities and tasks of this International Standard may also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288, Systems and software engineering—System life cycle processes. In the context of this International Standard and ISO/IEC/IEEE 15288, it is recognized that 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 components (hardware) to operate, either as part of the software system of interest or as an enabling system or infrastructure. Thus, the choice of whether to apply this International Standard for the software life cycle processes, or ISO/IEC/IEEE 15288:2015, Systems and software engineering-System life cycle processes, depends on the system of interest. Processes in both standards have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively. read less