《IEEE-1058-1998.pdf》由会员分享,可在线阅读,更多相关《IEEE-1058-1998.pdf(26页珍藏版)》请在三一文库上搜索。
1、 IEEE Std 1058-1998 (Revision and redesignation of IEEE Std 1058.1-1987, incorporating IEEE Std 1058-1998 and IEEE Std 1058a-1998) IEEE Standard for Software Project Management Plans Sponsor Software Engineering Standards Committee of the IEEE Computer Society Approved 8 December 1998 IEEE-SA Standa
2、rds Board Abstract: The format and contents of software project management plans, applicable to any type or size of software project, are described. The elements that should appear in all software project management plans are identified. Keywords: management plans, software project management plans
3、The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA Copyright 1998 by the Institute of Electrical and lectronics Engineers, Inc. All rights reserved. Published 22 December 1998. Printed in the United States of America. Print: ISBN 0-7381-144
4、7-2SH94690 PDF: ISBN 0-7381-1448-0SS94690 No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
5、Committees of the IEEE Standards Association (IEEE-SA) Standards Board. Members of the committees serve voluntarily and without compensation. They are not necessarily members of the Institute. The standards developed within IEEE represent a consensus of the broad expertise on the subject within the
6、Institute as well as those activities outside of IEEE that have expressed an interest in participating in the development of the standard. Use of an IEEE Standard is wholly voluntary. The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, m
7、arket, or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. E
8、very IEEE Standard is subjected to review at least every fi ve years for revision or reaffi rmation. When a document is more than fi ve years old and has not been reaffi rmed, it is reasonable to conclude that its contents, although still of some value, do not wholly refl ect the present state of th
9、e art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affi liation with IEEE. Suggestions for changes in documents should be in the form of a pro
10、posed change of text, together with appropriate supporting comments. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specifi c applications. When the need for interpretations is brought to the attention of IEEE, the Institute will in
11、itiate action to prepare appropriate responses. Since IEEE Standards represent a consensus of all concerned interests, it is important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and Standards C
12、oordinating Committees are not able to provide an instant response to interpretation requests except in those cases where the matter has previously received formal consideration. Comments on standards and requests for interpretations should be addressed to: Secretary, IEEE-SA Standards Board 445 Hoe
13、s Lane P.O. Box 1331 Piscataway, NJ 08855-1331 USA Authorization to photocopy portions of any individual standard for internal or personal use is granted by the Institute of Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. To arrang
14、e for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; (978) 750-8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Cente
15、r. Note: Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. The IEEE shal
16、l not be responsible for identifying patents for which a license may be required by an IEEE standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Copyright 1998 IEEE. All rights reserved. iii Introduction (This introduction is not p
17、art of IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans.) Overview This standard contains four clauses. Clause 1 defi nes the scope and purpose of the standard. Clause 2 provides references to other IEEE standards that should be followed when applying this standard. Clause 3 p
18、rovides defi nitions of terms that are used throughout the standard. Clause 4 contains an overview and detailed specifi cation of the standard, including required components that shall be included, and optional components that may be included in software project management plans (SPMPs) based on thi
19、s standard. The sequence of the elements presented in Clause 4 does not imply that SPMPs must be developed in the order of presentation. In most instances, SPMPs based on this standard will be developed by repeated iteration and refi nement of the various elements in the plan. Purpose This standard
20、specifi es the format and content of SPMPs. This standard does not specify the exact techniques to be used in developing an SPMP, nor does it provide examples of SPMPs. Each organization using this standard should develop a set of practices and procedures to provide detailed guidance for preparing a
21、nd updating of SPMPs based on this standard. These practices and procedures should take into account the environmental, organizational, and political factors that infl uence application of the standard. Not all software projects are concerned with development of source code for a new software produc
22、t. Some software projects consist of a feasibility study and defi nition of product requirements. Other software projects terminate upon completion of product design, and some projects are concerned with major modifi cations to existing software products. This standard is applicable to all types of
23、software projects; applicability is not limited to projects that develop source code for new products. Project size or type of software product does not limit application of this standard. Small projects may require less formality in planning than large projects, but all components of the standard s
24、hould be addressed by every software project. Software projects are sometimes component parts of larger projects. In these cases, the SPMP may be a separate component of a larger plan or it may be merged into a system-level or business-level project management plan. Audience This standard is intende
25、d for use by software project managers and other personnel who prepare and update project plans and monitor adherence to those plans. Evolution of plans Developing the initial version of the SPMP should be one of the fi rst activities to be completed in a software project. As the project evolves the
26、 nature of the work to be done will be better understood and plans will become more detailed. Thus, each version of the plan should be placed under confi guration management, and each version should contain a schedule for subsequent updates to the plan. Terminology This standard follows the IEEE Sta
27、ndards Style Manual . In particular, the word shall is used to indicate mandatory requirements to be strictly followed in order to conform to the standard and from which no deviation is permitted. The word should is used to indicate that among several possibilities one is recommended as particularly
28、 suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain course of action is deprecated but not prohibited. iv Copyright 1998 IEEE. All rights reserved. The word may is used to indicate a
29、 course of action permissible within the limits of the standard. The word can is used for statements of possibility and capability, whether material, physical, or causal. History The project authorization request for development of this standard was approved by the IEEE Standards Board on 13 Decembe
30、r 1984. The fi rst version of this standard (IEEE Std 1058.1-1987) was approved on 10 December 1987. The standard was reaffi rmed 2 December 1993. IEEE Std 1058a was approved by the IEEE-SA Standards Board on 17 September 1998; the revision of the full standard was approved on 8 December 1998. The c
31、hanges in this version of the standard are based on comments from users of the 1987 standard and the desire for conformance with IEEE/EIA 12207.0-1996. Contributors This standard was developed by the Software Project Management Plans Working Group of the Software Engineering Standards Committee of t
32、he Computer Society of the IEEE. The following individuals contributed to the development of this standard: Richard E. FairleyJohn M. GlabasRichard H. Thayer The following persons were on the balloting committee of IEEE Std 1058a: Torben Aabo T. J. Al-Hussaini R. W. Allen Leo Beltracchi H. Ronald Be
33、rlack Richard E. Biehl Juris Borzovs David W. Burnett Edward R. Byrne Michael Caldwell Keith Chan Antonio M. Cicu Theo Clarke Franois Coallier Virgil Lee Cooper W. W. Geoff Cozens Paul R. Croll Thomas Crowley Geoffrey Darnton Taz Daughtrey Raymond Day Bostjan K. Derganc Sanjay Dewal Perry R. DeWeese
34、 Sherman Eagles Christof Ebert William Eventoff Jonathan H. Fairclough Richard E. Fairley John W. Fendrich Jay Forster Kirby Fortenberry Eva Freund Karol Fruehauf Barry L. Garner Marilyn Ginsberg-Finner John Garth Glynn Julio Gonzalez-Sanz Lewis Gray L. M. Gunther David A. Gustafson Jon D. Hagar Joh
35、n Harauz Rob Harker Robert T. Harley Herbert Hecht William Hefley Mark Heinrich Debra Herrmann Umesh P. Hiriyannaiah Peter L. Hung George Jackelen David Johnson Frank V. Jorgensen Vladan V. Jovanovic William S. Junk George X. Kambic Ron S. Kenett Judith S. Kerner Robert J. Kierzyk Thomas M. Kurihara
36、 John B. Lane J. Dennis Lawrence Mary Leatherman Randal Leavitt William M. Lively James J. Longbucco Stan Magee David Maibor Robert A. Martin Mike McAndrew Patrick D. McCray James W. Moore Pavol Navrat Donald J. Ostrom Mike Ottewill Indradeb P. Pal Mark Paulk John G. Phippen Alex Polack Peter T. Poo
37、n Lawrence S. Przybylski Kenneth R. Ptack Larry K. Reed Donald J. Reifer Annette D. Reilly Dennis Rilling R. Waldo Roth Andrew P. Sage Helmut Sandmayr Stephen R. Schach Norman Schneidewind David J. Schultz Lisa A. Selmon Robert W. Shillato David M. Siefert Lynn J. Simms Carl A. Singer Melford E. Smy
38、re Alfred R. Sorkowitz Julia. Stesney Fred J. Strauss Christine Brown Strysik Toru Takeshita Richard H. Thayer Booker Thomas Patricia Trellue Mark-Rene Uchida Theodore J. Urbanowicz Glenn D. Venables Delores Wallace -,-,- Copyright 1998 IEEE. All rights reserved. v John W. Walz Camille S. White-Part
39、ain Scott A. Whitmire P. A. Wolfgang Paul R. Work Natalie C. Yopconka Janusz Zalewski Geraldine Zimmerman Peter F. Zoll The following persons were on the balloting group of IEEE Std 1058.1 (renumbered as 1058): Syed Ali Theodore K. Atchinson H. Ronald Berlack Richard E. Biehl Juris Borzovs David W.
40、Burnett James E. Cardow Leslie Chambers Keith Chan Antonio M. Cicu Theo Clarke Rosemary Coleman Darrell Cooksey Virgil Lee Cooper W. W. Geoff Cozens Paul R. Croll Thomas Crowley Taz Daughtrey Hillary Davidson Bostjan K. Derganc Perry R. DeWeese Audrey Dorofee Carl Einar Dragstedt Jonathan H. Fairclo
41、ugh Richard E. Fairley John W. Fendrich Kirby Fortenberry Eva Freund Karol Fruehauf Roger U. Fujii Barry L. Garner Marilyn Ginsberg-Finner John Garth Glynn Julio Gonzalez-Sanz Donald Gotterbarn L. M. Gunther Robert T. Harley William Hefley Manfred Hein Debra Herrmann S. H. Stephen Huang George Jacke
42、len Frank V. Jorgensen Vladan V. Jovanovic William S. Junk George X. Kambic Diana Kang Ron S. Kenett Judith S. Kerner Robert J. Kierzyk Shaye Koenig Thomas M. Kurihara John B. Lane J. Dennis Lawrence Randal Leavitt Michael Lines Dieter Look John Lord Stan Magee Tomoo Matsubara Patrick D. McCray Russ
43、ell McDowell Sue McGrath Jerome W. Mersky Alan Miller James W. Moore Pavol Navrat Mike Ottewill David E. Peercy John G. Phippen Peter T. Poon Kenneth R. Ptack Annette D. Reilly Andrew P. Sage Helmut Sandmayr Norman Schneidewind David J. Schultz Lisa A. Selmon Robert W. Shillato Lynn J. Simms Carl A.
44、 Singer James M. Sivak Alfred R. Sorkowitz Julia Stesney Fred J. Strauss Christine Brown Strysik Toru Takeshita Richard H. Thayer Douglas H. Thiele Booker Thomas Patricia Trellue Leonard L. Tripp Mark-Rene Uchida Theodore J. Urbanowicz Andre Villas-Boas Udo Voges Ronald L. Wade Scott A. Whitmire P.
45、A. Wolfgang Paul R. Work Natalie C. Yopconka Geraldine Zimmerman The IEEE-SA Standards Board approved IEEE Std 1058a on 16 September 1998. When it approved IEEE Std 1058 on 8 December 1998, it had the following membership: Richard J. Holleman , Chair Donald N. Heirman , Vice Chair Judith Gorman , Se
46、cretary Satish K. Aggarwal Clyde R. Camp James T. Carlo Gary R. Engmann Harold E. Epstein Jay Forster* Thomas F. Garrity Ruben D. Garzon James H. Gurney Jim D. Isaak Lowell G. Johnson Robert Kennelly E. G. “Al” Kiener Joseph L. Koepfinger* Stephen R. Lambert Jim Logothetis Donald C. Loughry L. Bruce
47、 McClung Louis-Franois Pau Ronald C. Petersen Gerald H. Peterson John B. Posey Gary S. Robinson Hans E. Weinrich Donald W. Zipse *Member Emeritus Kristin Dittmann IEEE Standards Project Editor vi Copyright 1998 IEEE. All rights reserved. Contents 1. Overview.1 2. References.2 3. Definitions.2 4. Ele
48、ments of the software project management plan .3 4.1 Overview (Clause 1 of the SPMP). 5 4.2 References (Clause 2 of the SPMP). 6 4.3 Definitions (Clause 3 of the SPMP). 6 4.4 Project organization (Clause 4 of the SPMP) 6 4.5 Managerial process plans (Clause 5 of the SPMP) 6 4.6 Technical process pla
49、ns (Clause 6 of the SPMP). 10 4.7 Supporting process plans (Clause 7 of the SPMP) 10 4.8 Additional plans (Clause 8 of the SPMP) 12 4.9 Plan annexes. 12 4.10 Plan index. 12 Annex A (informative) Bibliography.13 Annex B (informative) Guidelines for compliance with IEEE/EIA 12207.1-1997.14 Copyright 1998 IEEE. All rights reserved. 1 IEEE Standard for Software Project Management Plans 1. Overview This standard prescribes the format and content of software project management plans (SPMPs). An SPMP is the controlling document for managing
链接地址:https://www.31doc.com/p-3769488.html