Systems and software engineering - Life cycle processes - Project management
|Publication Date:||15 December 2009|
|ICS Code (Software):||35.080|
This International Standard is intended to aid project managers in managing to successful conclusion those projects concerned with software-intensive systems and software products.
This International Standard specifies the required content of the project management plan (PMP). This International Standard also quotes the extracted purpose and outcome statements from the project processes of ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), and adds detailed guidance for managing projects that use these processes for software products and softwareintensive systems.
Field of application
This International Standard is written for those who use or plan to use ISO/IEC 15288:2008 (IEEE Std 15288- 2008) and ISO/IEC 12207:2008 (IEEE Std 12207-2008) on projects dealing with software-intensive systems and software products, regardless of project scope, product, methodology, size or complexity. The field of application of this International Standard spans the whole software or system life cycle, and addresses everybody who plays a role in project management - project managers and others, specifically:
• those responsible for establishing and continuously improving ISO/IEC 12207:2008 (IEEE Std 12207- 2008) software life cycle processes and ISO/IEC 15288:2008 (IEEE Std 15288-2008) system life cycle processes;
• those responsible for executing any ISO/IEC 12207:2008 (IEEE Std 12207-2008) software life cycle process or ISO/IEC 15288:2008 (IEEE Std 15288-2008) system life cycle process at a project level;
• organizations or individuals subcontracting a project management effort.
In many organizations, the various responsibilities of project management are assigned to more than one person. Where the term "project manager" is used in this International Standard, the guidance, advice or normative requirement applies to the applicable role within the organization.
This International Standard is intended to provide guidance for two-party situations and may be equally applied where the two parties are from the same organization. This International Standard can also be used by a single party as self-imposed tasks.
This International Standard can also serve as guidance in multi-party situations, where high risks are inherent in the supply and integration of complex software-based systems, and procurement can involve several vendors, organizations or contracting parties.
The normative content specifications for project management plans and the guidance for management of the project processes are limited to projects dealing with software-intensive systems and software products.