IEEE-1074-2006.pdf
《IEEE-1074-2006.pdf》由会员分享,可在线阅读,更多相关《IEEE-1074-2006.pdf(116页珍藏版)》请在三一文库上搜索。
1、IEEE Std 1074-2006 (Revision of IEEE Std 1074-1997) IEEE Standard for Developing a Software Project Life Cycle Process I E E E 3 Park Avenue New York, NY 10016-5997, USA 28 July 2006 IEEE Computer Society Sponsored by the Software Engineering Standards Committee IEEE Standard for Developing a Softwa
2、re Project Life Cycle Process Sponsored by the Software Engineering Standards Committee of the IEEE Computer Society Approved 30 March 2006 IEEE-SA Standards Board Abstract: This standard provides a process for creating a software project life cycle process (SPLCP). It is primarily directed at the p
3、rocess architect for a given software project. Keywords: software project life cycle, software project life cycle model, software project life cycle process _ The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright 2006 by the Institute of El
4、ectrical and Electronics Engineers, Inc. All rights reserved. Published 28 July 2006. Printed in the United States of America. IEEE is a registered trademark in the U.S. Patent +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obta
5、ined through the Copyright Clearance Center. -,-,- Introduction This introduction is not part of IEEE Std 1074-2006, IEEE Standard for Developing a Software Project Life Cycle Process. Background IEEE Std 1074 is a standard for the generation of the process governing software development and mainten
6、ance for a project. This standard requires selection of a users software project life cycle model (SPLCM) based on the organizations mission, vision, goals, and resources. It is not intended to define or imply a software project life cycle (SPLC) of its own nor does it presume or suggest any particu
7、lar SPLCM. This standard describes the individual activities that are to be mapped within the selected model and provides examples of mapping onto typical SPLCMs. However, this standard is not an instructional guide. In addition to providing for the generation of a project process, this standard may
8、 also be used to develop organizational processes to support software development and maintenance or to develop special, single-function processes within a project. This standard applies to the management and support activities that continue throughout the entire projects life cycle as well as all a
9、spects of the software life cycle from concept exploration through retirement. The activities listed in this standard are not executable processes. They are components of processes and not intended to stand alone. The activities are generic and do not imply a sequential order. They have been adminis
10、tratively grouped for convenience and may be likened to a dictionary where words and meanings are arranged to allow the user to quickly locate a desired activity and its components. This standard provides activities to be addressed in a software life cycle. It allows the user great flexibility in th
11、e manner in which activities are mapped onto the selected model and software project life cycle (SPLC) while preserving a normative standard to which to conform. Utilization of these activities maximizes the benefits to the user when the use of this standard is initiated early in the software projec
12、ts life cycle. A project that has proceeded past the initialization phase when this standard is invoked should gradually move into conformance to this standard. This standard was written for any organization responsible for managing and conducting software projects. It will be useful to project mana
13、gers, software developers, quality assurance organizations, purchasers, users, and maintainers. It can be used where software is the total system or where software is embedded in a larger system. This standard is also useful for projects that do not span the full software life cycle (i.e., developin
14、g a software specification or designing, writing, and verifying software that is based upon specifications developed by another organization, company, or previous project). This standard allows for continuing harmonization with IEEE/EIA 12207.0 B3a and its successors. The standard may be used to dev
15、elop the primary and supporting life cycle processes specified in IEEE/EIA 12207. This standard supports the development of organizational standard processes and the selection of a standard, defined project process that is tailored from an organizations set of standard processes (organizational proc
16、ess definition) and integrated project management for each individual project.b _ a The numbers in brackets correspond to the numbers of the bibliographic references listed in Annex F. b Process improvement models that meet these criteria include the SEI CMMI model. This information is given for the
17、 convenience of users and does not constitute an endorsement by the IEEE of these models. Equivalent models may be used if they can be shown to lead to the same results. iv Copyright 2006 IEEE. All rights reserved. History Since this standards original publication, considerable worldwide attention h
18、as been paid to software project life cycle processes (SPLCPs). Use of and comments on IEEE Std 1074-1991/1995/1997, and other quality system and life cycle standards activity, have been carefully considered in preparing this substantive revision of this standard. The 1995 version was a minor revisi
19、on to correct specific errors found in the 1991 version. The 1997 version saw the following changes: Activities were rearranged into more logical groupings (called activity groups) such as placing all planning activities into the new Project Planning Activity Group, collecting all project initiation
20、 activities, and collecting and expanding all review activities. The term process as used in earlier versions of this standard was replaced with the term activity group to identify collections of activities. Some users of this standard were misinterpreting the collections as actual processes and try
21、ing to execute them as such. The term activity group is intended to eliminate this misconception. The importance of risk management led to the addition of a new activity, manage risks. The recognition that software can be acquired from other sources, for use in the system being developed, led to the
22、 addition of the Software Importation Activity Group. The following changes are among those included in this current version: The focus of the standard was more clearly centered on a single process for a given project. The term compliance was changed to conformance to reflect international standards
23、 usage. Recognition of the importance of release management led to the addition of release management activities. The emerging importance of, and increased attention to, software security led to the addition of two activities: determine security objectives and confirm security accreditation. Notice
24、to users Errata Errata, if any, for this and all other standards can be accessed at the following URL: http:/ standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL for errata periodically. Interpretations Current interpretations can be accessed at the foll
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- IEEE 1074 2006
链接地址:https://www.31doc.com/p-3771158.html