CSA - CAN/CSA-ISO/IEC 12207-09
Systems and software engineering — Software life cycle processes
|Publication Date:||1 October 2009|
|ICS Code (Software):||35.080|
This International Standard establishes a common framework for software life cycle processes, with welldefined 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 product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.
This International Standard applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.
This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.
The processes, activities and tasks of this International Standard-either alone or in conjunction with ISO/IEC 15288-may also be applied during the acquisition of a system that contains software.
The purpose of this International Standard is to provide a defined set of processes to facilitate communication among acquirers, suppliers and other stakeholders in the life cycle of a software product.
This International Standard is written for acquirers of systems and software products and services and for suppliers, developers, operators, maintainers, managers, quality assurance managers, and users of software products.
This International Standard is intended for use in a two-party situation and may be equally applied where the two parties are from the same organization. The situation may range from an informal agreement up to a legally binding contract. The International Standard may be used by a single party through a self-imposed set of processes. This clause does not prevent the use of ISO/IEC 12207 by suppliers or developers of off-theshelf software.
This International Standard does not detail the life cycle processes in terms of methods or procedures required to meet the requirements and outcomes of a process.
This International Standard does not detail documentation in terms of name, format, explicit content and recording media. The International Standard may require development of documents of similar class or type; various plans are an example. The International Standard, however, does not imply that such documents be developed or packaged separately or combined in some fashion. These decisions are left to the user of the International Standard.
NOTE ISO/IEC 15289 addresses the content for life cycle process information items (documentation).
This International Standard does not prescribe a specific system or software life cycle model, development methodology, method, model or technique. The parties of the International Standard are responsible for selecting a life cycle model for the software project and mapping the processes, activities, and tasks in this International Standard onto that model. The parties are also responsible for selecting and applying the software development methods and for performing the activities and tasks suitable for the software project.
This International Standard is not intended to be in conflict with any organization's policies, procedures, and standards or with any national laws and regulations. Any such conflict should be resolved before using this International Standard.