Applying Entry-Level Process Definition Standards: ISO/IEC/IEEE

Part 2

guidance in implementing the process. Well, in Annex G of 12207 and Annex F of 15288, there is material entitled, “Relationship to other IEEE Standards”. Most of the text is a big table with a row for each process. Here’s the row for Software Configuration Management:









7.2 Software support processes


Software Configuration Management Process


This standard specifies the content of a software configuration management plan along with requirements for specific planning activities.

This entry references a 27-page IEEE standard that provides substantial additional detail on planning for software configuration management.

So, in short, for our example, Software Configuration Management, the 12207 standard provides:

    • A brief, outcome-oriented description;
      • A slightly less brief, task-oriented description;
        • A reference to a standard providing even more detail; and
          • The permission to use a more general configuration management standard if appropriate

          This example is not unusual. All of the processes provide the first two levels of detail, many provide the third item, and several (in 12207) provide the fourth item.

          Part 2
          Part 2 of this article, Applying Entry-Level Process Definition Standards: ISO/IEC/IEEE  describes how ISO/IEC/IEEE 12207 and 15288 stack up against the needs of users who are just entering into process definition.

          About the Author:

          James W. Moore is a 40-year veteran of software engineering in IBM and, now, the MITRE Corporation. He serves as the IEEE Computer Society's Vice-President for Professional Activities and as a member of its Board of Governors. He was an Executive Editor of the Society's 2004 "Guide to the Software Engineering Body of Knowledge" and a member of the Editorial Board of the recent revision of the "Encyclopedia of Software Engineering." He performs software and systems engineering standardization for the IEEE, serving as its liaison to ISO/IEC JTC1/SC7 and as a member of the Executive Committee of the IEEE Software and Systems Engineering Standards Committee. The IEEE Computer Society has recognized him as a Charter Member of their Golden Core; the IEEE selected him as a recipient of their Third Millennium Award and recently named him as a Fellow of the IEEE. His latest book on software engineering standards was published in 2006 by John Wiley & Son. He holds two US patents and, dating to times when software was not regarded as patentable, two "defensive publications". He graduated from the University of North Carolina with a BS in Mathematics, and Syracuse University with an MS in Systems and Information Science.

          [1] The writers of the standard did not consider themselves competent to describe all of the business processes of an organization, so they deliberately described the minimum necessary organization-level processes.

          About the author

          AgileConnection is a TechWell community.

          Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.