IEEE

[External] IEEE Std 990-1987 - IEEE Recommended Practice for Ada as a Program Design Language

EXTERNAL: this content refers to a remote source that is external to this web site.
ARCHIVAL: this content has been flagged as archival or historical.
Download from
Defines standard
Status (as a standards document)
archived
Abstract

The report provides recommendations reflecting the state of the art and alternative approaches to good practice for characteristics of program design languages (PDLs) based on the syntax and semantics of Ada. The recommended practice addresses the characteristics of an Ada PDL and not the use of an Ada PDL. While it is widely recognized that graphic representations may enhance the design activity, there is no clear consensus concerning graphic representations. As such, this document is principally concerned with aspects of textual representations.

[External] IEEE Std 982.1-1988 - IEEE Standard Dictionary of Measures to Produce Reliable Software

EXTERNAL: this content refers to a remote source that is external to this web site.
Download from
Defines standard
Status (as a standards document)
archived
Abstract

The standard provides a set of measures indicative of software reliability that can be applied to the software product as well as to the development and support processes. There is a need for measures than can be applied early in the development process that may be indicators of the reliability of the delivered product. The standard provides a common, consistent definition of a set of measures that may meet those needs. The document contains four sections. Section 1: Scope, establishes the goals and boundaries of the standard. Section 2: Definitions, serves as a central location for key terms used throughout the body of the document. Section 3: Functional Classification of Measures, provides a taxonomy with respect to measure objectives. Section 4: Measures for Reliable Software, presents the measures ordered in general by complexity.

[External] IEEE Std 830-1998 - IEEE Recommended Practice for Software Requirements Specifications

EXTERNAL: this content refers to a remote source that is external to this web site.
Download from
Defines standard
Status (as a standards document)
active

[External] IEEE Std 829-2008 - IEEE Standard for Software and System Test Documentation

EXTERNAL: this content refers to a remote source that is external to this web site.
Download from
Defines standard
Status (as a standards document)
active
Abstract

Test processes determine whether the development products of a given activity conform to the requirements of that activity and whether the system and/or software satisfies its intended use and user needs. Testing process tasks are specified for different integrity levels. These process tasks determine the appropriate breadth and depth of test documentation. The documentation elements for each type of test documentation can then be selected. The scope of testing encompasses software-based systems, computer software, hardware, and their interfaces. This standard applies to software-based systems being developed, maintained, or reused (legacy, commercial off-the-shelf, Non-Developmental Items). The term "software" also includes firmware, microcode, and documentation. Test processes can include inspection, analysis, demonstration, verification, and validation of software and software-based system products.

[External] IEEE Std 828-2005 - IEEE Standard for Software Configuration Management Plans

EXTERNAL: this content refers to a remote source that is external to this web site.
Download from
Defines standard
Status (as a standards document)
active
Abstract

The minimum required contents of a Software Configuration Management (SCM) Plan are established via this standard. This standard applies to the entire life cycle of critical software (e.g., where failure would impact safety or cause large financial or social losses). It also applies to noncritical software and to software already developed. The application of this standard is not restricted to any form, class, or type of software.

[External] IEEE Std 610.12-1990 - IEEE Standard Glossary of Software Engineering Terminology

EXTERNAL: this content refers to a remote source that is external to this web site.
Download from
Defines standard
Status (as a standards document)
active
Abstract

Describes the IEEE Std 610.12-1990, IEEE standard glossary of software engineering terminology, which identifies terms currently in use in the field of software engineering. Standard definitions for those terms are established.

[External] IEEE Std 1074-1991 - IEEE Standard for Developing Software Life Cycle Processes

EXTERNAL: this content refers to a remote source that is external to this web site.
Download from
Defines standard
Status (as a standards document)
active

[External] IEEE Std 1061-1992 - IEEE Standard for a Software Quality Metrics Methodology

EXTERNAL: this content refers to a remote source that is external to this web site.
Download from
Status (as a standards document)
archived
Abstract

A methodology for establishing quality requirements and identifying, implementing, analyzing, and validating the process and product of software quality metrics is defined. The methodology spans the entire software life cycle. Although this standard includes examples of metrics, it does not prescribe specific metrics.

[External] IEEE Std 1061-1998 - IEEE Standard for a Software Quality Metrics Methodology

EXTERNAL: this content refers to a remote source that is external to this web site.
Download from
Defines standard
Status (as a standards document)
active
Replaces
Abstract

A methodology for establishing quality requirements and identifying, implementing, analyzing and validating the process and product software quality metrics is defined. The methodology spans the entire software life-cycle.

[External] IEEE Std 1063-1987 - IEEE Standard for Software User Documentation

EXTERNAL: this content refers to a remote source that is external to this web site.
ARCHIVAL: this content has been flagged as archival or historical.
Download from
Status (as a standards document)
archived
Abstract

Two factors motivated the development of this standard: the concern of the software user communities over the poor quality of much user documentation, and a need for requirements expressed by producers of documentation. This standard applies only to traditional documentation, either printed on paper or stored in some other medium in the format of a printed document and used in a manner analogous to the way a printed document is used. This standard does not cover the actual writers and publishers of user documentation. The responsibility for ensuring that satisfactory software user documentation is produced rests with the organization that generates the software. Responsibility for ensuring that software user documentation is satisfactorily updated rests with the organization that repairs or modifies the software. Configuration management of the documentation is outside the scope of this standard.

[External] IEEE Std 1063-2001 - IEEE Standard for Software User Documentation

EXTERNAL: this content refers to a remote source that is external to this web site.
Download from
Defines standard
Status (as a standards document)
active
Replaces
Abstract

Minimum requirements for the structure, information content, and format of user documentation, including both printed and electronic documents used in the work environment by users of systems containing software, are provided in this standard.

[External] IEEE Std 1058-1998 IEEE Standard for Software Project Management Plans

EXTERNAL: this content refers to a remote source that is external to this web site.
Download from
Defines standard
Status (as a standards document)
active
Replaces
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.

[External] IEEE Std 1058.1-1987 IEEE Standard for Software Project Management Plans

EXTERNAL: this content refers to a remote source that is external to this web site.
ARCHIVAL: this content has been flagged as archival or historical.
Download from
Status (as a standards document)
archived
Abstract

This standard specifies the format and contents of software project management plans. It does not specify the exact techniques to be used in developing project plans, nor does it provide examples of project management plans. This standard is applicable to all types of software projects; applicability is not limited to projects that develop operational versions of new products. Application of this standard is not limited by project size. It contains three sections. Section 1 defines the scope of the standard and provides references to other IEEE standards that should be followed when applying this standard. Section 2 provides definitions of terms that are used throughout the standard. Section 3 contains an overview and a detailed specification of the standard, including required components that must be included, and optional components that may be included in project plans based on this standard. The sequence of project plan elements presented in Section 3 does not imply that project plans should be developed in the order of presentation. In most instances, project plans based on this standard will be developed by repeated iteration and refinement of the various elements in the plan.

[External] IEEE Std 1045-1992 - IEEE Standard for Software Productivity Metrics

EXTERNAL: this content refers to a remote source that is external to this web site.
ARCHIVAL: this content has been flagged as archival or historical.
Download from
Defines standard
Status (as a standards document)
archived
Abstract

A consistent way to measure the elements that go into computing software productivity is defined. Software productivity metrics terminology are given to ensure an understanding of measurement data for both source code and document production. Although this IEEE standard prescribes measurements to characterize the software process, it does not establish software productivity norms, nor does it recommend productivity measurements as a method to evaluate software projects or software developers. This standard does not measure the quality of software. This standard does not claim to improve productivity, only to measure it. The goal of this standard is for a better understanding of the software process, which may lend insight to improving it.

Syndicate content