IEEE Std 1058-1998 - Software Project Management Plans

Sep 12, 2026

Uploaded by Dipper

Format and contents of software project management plans are specified for software projects of any type and size. The standard identifies the elements that should be included in all software project management plans and provides a structured basis for required and optional components. It also clarifies the overall organization of the standard, including scope, references, definitions, and a detailed overview of plan components.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages26

Reading Time9 min

AccessFree to download

Introduction

Overview

Purpose

Standard scope and purpose

References and definitions

Clause 4 overview and specification

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 Standards 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 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-1447-2 SH94690 PDF: ISBN 0-7381-1448-0 SS94690 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 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 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, market, 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 ofthe art and comments received from users of the standard. Every IEEE Standard is subjected to review at least every ﬁve years for revision or reafﬁrmation. When a document is more than ﬁve years old and has not been reafﬁrmed, it is reasonable to conclude that its contents, although still of some value, do not wholly reﬂect the present state of the 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 afﬁliation with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to speciﬁc applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate 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 Coordinating 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 Hoes Lane P.O. Box 1331 Piscataway, NJ 08855-1331 USA 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 shall not

FAQs

What does IEEE Std 1058-1998 specify?

It specifies the format and content of software project management plans (SPMPs). It does not define the exact techniques for developing an SPMP or provide SPMP examples.

Which types of software projects does the standard apply to?

It is applicable to any type or size of software project.

How is the standard organized in terms of clauses?

The standard contains four clauses: scope and purpose, references, definitions, and an overview plus detailed specification including required and optional components.

Sep 12, 2026

Uploaded by Dipper