IEEE 1058.1-1987 PDF | Request Standard
Latest

IEEE 1058.1-1987

IEEE Standard for Software Project Management Plans

Standard by IEEE, 1988

Available Formats:

  • Availability: Immediate Download
  • Language: English
  • License Type: Single User
  • Updates: Not Included
  • Availability: Request Quote
  • Language: English
  • License Type: Enterprise / Multi User
  • Updates: Included

About This Item

Legal Notices*

IEEE 1058.1-1987 is a software project management plans standard that defines a structured way to prepare and review project plans for software work. In the context of Components, Circuits, Devices and Systems, it is useful where software deliverables support engineered products and controlled development processes. IEEE 1058.1-1987 helps teams document scope, responsibilities, scheduling, and management controls so project expectations are clearer and easier to track.

Overview of IEEE 1058.1-1987

This standard focuses on the content and organization of a software project management plan, giving projects a consistent framework for planning and oversight. It is typically relevant when software development must be managed with defined milestones, resources, and review points. As a technical document, IEEE 1058.1-1987 supports disciplined project definition and helps align management, engineering, and delivery activities around the same plan.

Typical use cases

IEEE 1058.1-1987 is commonly used when software is part of a larger engineered system, such as control software, device-support tools, or system integration projects. It may guide planning for development teams working on components, circuits, devices, and related system functions where schedule control and documented responsibilities matter. The standard is also relevant for procurement or contract work that requires a defined project management plan before implementation begins.

Why it matters

Using IEEE 1058.1-1987 can improve consistency in how software projects are planned, reviewed, and managed. A clear management plan supports better coordination, reduces ambiguity around tasks and deliverables, and can lower project risk. For organizations handling technical systems, the standard may also help with compliance expectations, internal control, and traceability across development and verification activities. That makes it valuable when repeatable project governance is important.

  • Software project management plan structure
  • Scope, roles, and responsibilities
  • Schedule and milestone tracking
  • Management controls and review points
  • Support for engineered system projects
SKU: 1d93441dc0c3

  • Publication Date: 1988
  • Standard Status: Superseded
  • Publisher: IEEE
  • Subject: Components, Circuits, Devices and Systems
  • Official IEEE: Doi link

Please request information about the document. Contact Page

Online Standart App

Need This Standard?

Need This Standard?

Summarize with AI

ChatGPT Perplexity Google AI Claude Grok

Online Standart Disclaimer

OnlineStandart.com is an authorized reseller of international standards through partnerships with authorized distributors. We do not own the copyrights or trademarks of the standards we sell, including but not limited to those of API, ASHRAE, BSI, SAE, ASTM, IEEE, IEC, ASME, ISO, and others.

All product names, logos, and brands are property of their respective owners. All company, product, and service names used on this website are for identification purposes only. Use of these names, trademarks, and brands does not imply endorsement.

The content provided on this website is for informational purposes only and is intended to promote our reselling services. OnlineStandart.com is not affiliated with or endorsed by any of the standard organizations unless explicitly stated.