IEEE 12207.1 PDF

  • No Comments

IEEE Industry Implementation of International Standard Iso/iec (iso/iec ) Standard for Information Technology – Software Life . of IEEE/EIA , IEEE/EIA Guide for Information Technology— Software life cycle processes—Life cycle data. This standard may be. Industry implementation of International Standard ISO/IEC (ISO/IEC ) standard for information technology – software life cycle processes – life.

Author: Tekazahn Tuzil
Country: Colombia
Language: English (Spanish)
Genre: Software
Published (Last): 16 February 2011
Pages: 164
PDF File Size: 20.80 Mb
ePub File Size: 5.28 Mb
ISBN: 997-2-86496-689-3
Downloads: 26679
Price: Free* [*Free Regsitration Required]
Uploader: Telmaran

The standard establishes a set of processes for managing the lifecycle of software.

No particular set of stages is normative, but it does mention two examples:. Life cycle mode management helps 112207.1 acquisition and supply efforts are supported, while infrastructure and portfolio management supports business and project-specific initiatives during the entire system life cycle.

Acquisition covers all the activities involved in initiating a project. International Organization for Standardization. These 12270.1 deal with planning, assessment, and control of software and other projects during the life cycle, ensuring quality along the way. You are authorised to print the contents provided that this copyright notice is included.

ISO/IEC – Wikipedia

It is expected that particular projects “may not need to use all of the processes provided by this document. The full list includes [1] [2] [16]:.


Retrieved from ” https: The latter permits more variation. The standard “does not prescribe a specific software life cycle model, development methodologymethod, modelling approach, or technique. This plan contains information about the project such as different milestones that need to be reached.

Please click here to complete a registration request form. During the supply phase a project management plan is developed.

Software Engineering Standards for Quality”. If you are not a client of PPI or CTI, limited access which permits download access to many of these resources may be available on an approved-registration 12207.1. Instead, the standard acknowledges that software life cycles vary, and may be divided into stages also called phases that represent major life cycle periods and give rise to primary decision gates. The rest ensure the necessary resources and quality controls are in place to support the business’ project and system endeavors.

American Society for Quality. Hear about relevant training courses in your area.

By using this site, you agree to the Terms of Use and Privacy Policy. From Wikipedia, the free encyclopedia. This page was last edited on 1 Decemberat This can be done through either “full conformance” or “tailored conformance”.

This harmonization of the two standards led to the removal of separate software development and software reuse processes, bringing the total number of processes from 43 down to the 30 processes defined in Clause 4 describes the document’s intended use and conformance requirements.


It also caused changes to the quality management and quality assurance process activities and outcomes. The acquisition phase can be divided into different activities and deliverables that are completed chronologically. Stages aka phases are not the same as processes, and this standard only defines specific processes – it does not define any particular stages.


ISO/IEC 12207

A username and password is required for access to the resources. P P P P P These processes involve technical activities and personnel information technologytroubleshooters, software specialists, etc. The analysis and definition processes early on set the stage for how software and projects are implemented.

Indeed, the life cycle processes that involve planning, performance, and evaluation “should be considered for use at every stage”. Additionally, the definition of ” audit ” and related audit activities were updated.

Site developed by Webel IT Australia. If an organization does not have an appropriate set of organizational processes, a project executed by the organization may apply those processes directly to the project instead.