Search
×
FR

Placeholder headline

This is just a placeholder headline

API STD 521: Guide for Pressure-relieving and Depressuring Systems – Edition 6

$

682

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 653: Tank Inspection, Repair, Alteration, and Reconstruction – Edition 4

$

507

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z662:19 – Oil and gas pipeline systems

$

1197

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z341 Series-18: Storage of hydrocarbons in underground formations

$

878

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z246.2-14 – Emergency preparedness and response for petroleum and natural gas industry systems

$

596

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z341 Series:22 – Storage of hydrocarbons in underground formations

$

878

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z731-09 (R2014) – Emergency Preparedness and Response

$

177

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z662:23 – Oil and gas pipeline systems

$

1197

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA Z341 Series:26 – Storage of Hydrocarbons in underground formations

$

878

BUY NOW

Placeholder headline

This is just a placeholder headline

CSA B51:24 Boiler, Pressure Vessel, and Pressure Piping Code

$

389

BUY NOW

ISO 12207:2017

ISO 12207:2017 Systems and software engineering – Software life cycle processes

CDN $422.00

SKU: 0f33f72a00ee Categories: , ,

Description

ISO/IEC/IEEE 12207:2017 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 document can also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288:2015, Systems and software engineering?System life cycle processes.

In the context of this document and ISO/IEC/IEEE 15288, 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 document 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 documents have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively.

Edition

1

Published Date

2017-11-28

Status

PUBLISHED

Pages

145

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

ISO/IEC/IEEE 12207:2017 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 document can also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288:2015, Systems and software engineering?System life cycle processes.

In the context of this document and ISO/IEC/IEEE 15288, 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 document 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 documents have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively.

Previous Editions

Can’t find what you are looking for?

Please contact us at: