IEEE

Standard: IEEE Std 1209-1992 - IEEE Recommended Practice for the Evaluation and Selection of CASE Tools [Draft]

ARCHIVAL: this content has been flagged as archival or historical.
TODO: this content is incomplete, unfinished, or under construction.

From IEEE Software Engineering Standards Collection:

This recommended practice provides individuals and organisations a process for the evaluation and selection of computer-aided software engineering (CASE) tools. The recommended practice addresses the evaluation and selection of tools supporting software engineering processes including project management processes, development processes and integral processes.

Status (as a standard)
status: 
withdrawn

Standard: IEEE Std 1063 - IEEE Standard for Software User Documentation

From IEEE Software Engineering Standards Collection:

IEEE Std 1063. This standard provides minimum requirements on the structure and information content of user documentation, It applies primarily to technical substance rather than to style. Users of this standard may develop their own style manual for use within their organisations to implement the requirements of this standard.

Defining external document(s)

Standard: IEEE Std 1061 - IEEE Standard for a Software Quality Metrics Methodology

From IEEE Software Engineering Standards Collection:

Draft IEEE Std 1061. This standard provides a methodology for establishing quality requirements and identifying, implementing, analysing, and validating the process and product of software quality metrics. This standard does not prescribe specific metrics. It does include examples of metrics together with a complete example of the standard’s use.

Defining external document(s)

Standard: IEEE Std 1058 - IEEE Standard for Software Project Management Plans

From IEEE Software Engineering Standards Collection:

IEEE Std 1058.1. This standard specifies the format and contents of software project management plans. It does not specify the procedures or techniques to be used in the development of project management plans, or does it provide examples of project management plans, instead the standard sets a foundation for an organisation to build its own set of practices and procedures for developing project management plans.

Defining external document(s)

Standard: IEEE Std 1045 - IEEE Standard for Software Productivity Metrics

From IEEE Software Engineering Standards Collection:

IEEE Std 1045. This standard defines a framework for measuring and reporting productivity of the software process. It focuses on definitions of how to measure software process productivity and what to report when giving productivity results. It is meant for those who want to measure the productivity of the software process for creating code and documentation products.

Defining external document(s)

Standard: IEEE Std 1042 - IEEE Guide to Software Configuration Management

From IEEE Software Engineering Standards Collection:

IEEE Std 1042. The purpose of this guide is to provide guidance in planning Software Configuration Management (SCM) practices that are compatible with IEEE Std 828. The guide focuses on the process of SCM planning and provides a broad perspective for the understanding of software configuration management.

Defining external document(s)

Standard: IEEE Std 1028 - IEEE Standard for Software Reviews and Audits

From IEEE Software Engineering Standards Collection:

IEEE Std 1028. Software reviews and audits are a basic part of the ongoing evaluation of software products as they pass along the software development life cycle. This standard provides direction to the reviewer or auditor on the conduct of evaluations. Included are processes applicable to both critical and non-critical software and the procedures required for the execution of reviews and audits.

Defining external document(s)

Standard: IEEE Std 1016 - IEEE Standard for Information Technology-Systems Design - Software Design Descriptions

From IEEE Software Engineering Standards Collection:

IEEE Std 1016. A software design description is a representation of a software system. It is used as a medium for communicating software design information. This recommended practice describes that documentation of software designs. It specifies the necessary information content and the recommended organisation for a software design description.

Defining external document(s)

Standard: IEEE Std 1012 - IEEE Standard for Software Verification and Validation

From IEEE Software Engineering Standards Collection:

IEEE Std 1012. This standard has a threefold purpose:

a. to provide, for both critical and non-critical software, uniform and minimum requirements for the format and content of Software Verification and Validation Plans (SVVPs);

b. to define, for critical software, specific minimum Verification and Validation (V&V) tasks and their required inputs and outputs that shall be included in SVVPs; and

c. to suggest optional V&V tasks to be used to tailor SVVPs as appropriate for the particular V&V effort.

Defining external document(s)

Standard: IEEE Std 1002 - IEEE Standard Taxonomy for Software Engineering Standards

From IEEE Software Engineering Standards Collection:

This standard describes the form and content of a software engineering standards taxonomy. It explains the various types of software engineering standards, their functional and external relationships, and the role of various functions participating in the software life cycle. The taxonomy may be used as a method for planning the development or evaluation of standards for an organisation. It could also serve as a basis for classifying a set of standards or for organising a standards manual.

Status (as a standard)
status: 
withdrawn
Defining external document(s)

Standard: IEEE 729

TODO: this content is incomplete, unfinished, or under construction.

Standard: IEEE Std 990 - IEEE Recommended Practice for Ada as a Program Design Language

From IEEE Software Engineering Standards Collection:

IEEE Std 990. This recommended practice provides recommendations reflecting state-of-the-art and alternate approaches to good practice for characteristics of Program Design Languages (PDLs) based on the syntax and semantics of the Ada Programming Language. In this document, these are referred to as Ada PDLs.

Status (as a standard)
status: 
withdrawn
Defining external document(s)

Standard: IEEE Std 982.2 - IEEE Guide for the Use of IEEE Standard Dictionary of Measures to Produce Reliable Software

From IEEE Software Engineering Standards Collection:

IEEE Std 982.2 is a companion to IEEE Std 982.1 and provides guidance in the use of the measures in IEEE Std 982.1. It provides information needed by industry to make the best use of IEEE Std 982.1.

Defining external document(s)

Standard: IEEE Std 982.1 - IEEE Standard Dictionary of Measures to Produce Reliable Software

From IEEE Software Engineering Standards Collection:

IEEE Std 982.1. This standard provides definitions of selected measures. The measures are intended for use throughout the software development life cycle in order to produce reliable software. The standard does not specify or require the use of any of the measures. Its intent is to describe the individual measures and their use.

Defining external document(s)

Standard: IEEE Std 830 - IEEE Recommended Practice for Software Requirements Specifications

From IEEE Software Engineering Standards Collection:

IEEE Std 830. This guide describes alternate approaches to good practice in the specification of software requirements. To enable the reader to make knowledgeable choices, extensive tutorial material is provided. This guide covers the attributes of a good software requirements specification, as well as specification methodologies and associated formats.

Defining external document(s)

Standard: IEEE Std 730 - IEEE Standard for Software Quality Assurance Plans

From IEEE Software Engineering Standards Collection:

IEEE Std 730. This standard has legal liability as its basic rationale. It is directed toward the development and maintenance of critical software, that is, where failure could impact safety or cause large financial or social losses. The orientation is toward delineating all of the planned and systematic actions on a particular project that would provide adequate confidence that the software product conforms to established technical requirement. The standard establishes a required format and a set of minimum contents for software quality assurance plans. ... read more

Defining external document(s)
Syndicate content