By Topic

1074-2006  -  IEEE Standard for Developing a Software Project Life Cycle Process

Revision of IEEE Std 1074-1997
StatusInactive  -  Superseded

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$121.0 $94.0
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

This project will develop a revised 1074 Standard for Developing a Software Project Life Cycle Process. The scope of the revision will be consistent with the scope of the original document (and IEEE guidance for the revision effort). The standard provides a process for creating a software project life cycle process.

This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the process architect for a given software project. It is the function of the process architect to develop the SPLCP.This methodology begins with the selection of an appropriate software project life cycle model (SPLCM)for use on the specific project. It continues through the definition of the software project life cycle (SPLC),using the selected SPLCM, the activities provided in Annex A, and the portion of the software life cycle that is relevant to the project. The methodology concludes with the augmentation of the software life cycle with organizational process assets (OPAs) to create the SPLCP.The activities that are provided in Annex A cover the entire life cycle of a software system, from concept exploration through the eventual retirement of the software system. This standard does not address nonsoftware activities, such as contracting, purchasing, or hardware development. It also does not mandate the use of a specific SPLCM, nor does it provide a selection of, or a tutorial on, SPLCMs. This standard presumes that the process architect is already familiar with a variety of SPLCMs, with the criteria for choosing among them and with the criteria for determining the attributes and constraints of the desired end system and the development environment that affects this selection. Finally, this standard does not prescribe how to perform the software activities in Annex A.
This standard defines the process by which an SPLCP is developed. It is useful to any organization that is responsible for managing and performing software projects. It can be used where software is the total system or where software is part of a larger system.