International Organization for Standardization (ISO)/IEC 12207

International Organization for Standardization (ISO)/IEC 12207

The SEI is not the only quality or standards organization concerned with software processes and life cycles. As early as 1989, it was recognized that the standard imposed upon defense and other government contractors, Department of Defense Standard (DOD STD) 2167A, was not well suited to use with projects employing object-oriented design (OOD) or Rapid Application Development (RAD) methods. A new Military Standard (MIL STD) 498 was intended to correct issues with these methods, and it does definitely solve some of the problems. A third approach, International Organization for Standardization (ISO)/IEC 12207, which developed independently from MIL STD 498, is another step forward. It explains the main component processes of a complete software life cycle, their interfaces with one another, and the high-level relations that govern their interactions.

As shown in the following figure, ISO/IEC 12207 lists 12 engineering activities, following process implementation, that are analogous to the phases in a typical SLCM:

 1.   System requirement analysis;
 2.   System architectural design;
 3.   Software requirements analysis;
 4.   Software architectural design;
 5.   Software detailed design;
 6.   Software coding and testing;
 7.   Software integration;
 8.   Software qualification testing;
 9.   System integration;
10.  System qualification testing;
11.  Software installation;
12.  Software acceptance test.

Engineering View of ISO IEC 12207

The ISO/IEC 12207 approach has been explained as an implementation of a Plan-Do-Check-Act (PDCA) cycle, discussed in "Process Overview".

The purpose is that the engineer should check the output of an engineering task before it becomes input to the next task. "The activities of the ISO/IEC 12207 development process have independence from one another they are not ordered in a waterfall sequence and, there are no requirements in the international standard that dictate which of them must be executed first and which next". In fact, ISO/IEC 12207 says clearly, in paragraph, that "these activities and tasks may overlap or interact and may be performed iteratively or recursively". Paragraph 1.5 states that "this international standard does not prescribe a specific life cycle model or software development method". Paragraph states that, unless the contract stipulates one, "the developer shall define or select a software life cycle model appropriate to the scope, magnitude, and complexity of the project. The activities and tasks of the development process shall be selected and mapped onto the life cycle model". The purpose and effect of the language in the international standard are to provide flexibility in ordering activities, and to choose development models to keep away from the waterfall bias of other standards.

Individuals and organizations respected in the software, project management, and quality arenas are in agreement on the requirement of process and life cycle process, in particular. PMI, Boehm, IT-Systems of the Federal Republic of Germany, the SEI, and the ISO have all recommended having a software development life cycle, one that is carefully selected and tailored for project suitability.


software process, life cycle, project management
The contents available on this website are copyrighted by TechPlus unless otherwise indicated. All rights are reserved by TechPlus, and content may not be reproduced, published, or transferred in any form or by any means, except with the prior written permission of TechPlus.
© Copyright 2017 SPMInfoBlog.
Designed by TechPlus