[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-241289-105":53,"doc-detail-241289-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","ieee-std-1058-1998-software-project-management-plans","IEEE Std 1058-1998 - Software Project Management Plans","","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.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/ieee-std-1058-1998-software-project-management-plans/241289/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/ieee-std-1058-1998-software-project-management-plans/241289.png","ImageObject",442,249,{"name":88,"@type":89},"Dipper","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-11-03","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":8},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What does IEEE Std 1058-1998 specify?","Question",{"text":108,"@type":109},"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.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"Which types of software projects does the standard apply to?",{"text":113,"@type":109},"It is applicable to any type or size of software project.",{"name":115,"@type":106,"acceptedAnswer":116},"How is the standard organized in terms of clauses?",{"text":117,"@type":109},"The standard contains four clauses: scope and purpose, references, definitions, and an overview plus detailed specification including required and optional components.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},241289,1791742722,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":8,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":141},1374404997633,"https://ap-avatar.wpscdn.com/davatar_a8503ba1806abce46bf441b54a3ca4cd","IEEE Std 1058-1998  \n(Revision and redesignation of IEEE Std 1058. 1-1987, incorporating IEEE Std 1058-1998 and  \nIEEE Std 1058a-1998)  \nIEEE Standard for Software Project Management Plans  \nSponsor  \nSoftware Engineering Standards Committee  \nof the  \nIEEE Computer Society  \nApproved 8 December 1998  \nIEEE-SA Standards Board  \nAbstract: 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.  \nKeywords: management plans, software project management plans  \nThe Institute of Electrical and Electronics Engineers, Inc.  \n345 East 47th Street, New York, NY 10017-2394, USA  \nCopyright © 1998 by the Institute of Electrical and lectronics Engineers, Inc.  \nAll rights reserved. Published 22 December 1998. Printed in the United States of America.  \nPrint: ISBN 0-7381-1447-2 SH94690  \nPDF: ISBN 0-7381-1448-0 SS94690  \nNo 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.  \nIEEE 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.  \nUse 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 five years for revision or reaffirmation. When a document is more than five years old and has not been reaffirmed, it is reasonable to conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard.  \nComments for revision of IEEE Standards are welcome from any interested party, regardless of membership affiliation with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments.  \nInterpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specific 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.  \nComments on standards and requests for interpretations should be addressed to:  \nSecretary, IEEE-SA Standards Board  \n445 Hoes Lane  \nP.O. Box 1331  \nPiscataway, NJ 08855-1331  \nUSA  \nNote: 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","cbCaijzgN1IzeUsL","https://ap.wps.com/l/cbCaijzgN1IzeUsL","pdf",225574,26,"English","# Introduction\n# Overview\n# Purpose\n## Standard scope and purpose\n## References and definitions\n## Clause 4 overview and specification","[{\"question\":\"What does IEEE Std 1058-1998 specify?\",\"answer\":\"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.\"},{\"question\":\"Which types of software projects does the standard apply to?\",\"answer\":\"It is applicable to any type or size of software project.\"},{\"question\":\"How is the standard organized in terms of clauses?\",\"answer\":\"The standard contains four clauses: scope and purpose, references, definitions, and an overview plus detailed specification including required and optional components.\"}]","IEEE Std 1058-1998 - Software Project Management Plans | PDF",1789173150,9]