IEEE

[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.

[External] ANSI/IEEE Std 1042-1987 - IEEE Guide to Software Configuration Management

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
Abstract

The guide provides guidance in planning software configuration management (SCM) practices that are compatible with ANSI/IEEE Std 828-1983, IEEE Standard for Software Configuration Management Plans. Three groups are served by this guide: developers of software, software management community, and those responsible for preparation of SCM plans. The developers of software will be interested in the different ways SCM can be used to support the software engineering process. The management community will be interested in how the SCM plan can be tailored to the needs and resources of a project. Those preparing plans for SCM will be interested in the suggestions and examples for preparation of a plan. The introduction of this guide presents a technical and philosophical overview of the SCM planning process. Subsequent paragraphs in the body of the guide contain general statements of principles, commentary on issues to consider, and lessons learned for the corresponding paragraph in the outline of the ANSI/IEEE Std 828-1983 Plan. Four Appendixes illustrate how the ANSI/IEEE Std 828-1983 can be used for a variety of different projects. A fifth Appendix lists current references that may be useful in planning SCM.

[External] IEEE Std 1028-2008 - IEEE Standard for Software Reviews and Audits

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

Five types of software reviews and audits, together with procedures required for the execution of each type, are defined in this standard. This standard is concerned only with the reviews and audits; procedures for determining the necessity of a review or audit are not defined, and the disposition of the results of the review or audit is not specified. Types included are management reviews, technical reviews, inspections, walk-throughs, and audits.

[External] IEEE Std 1016-2009 - IEEE Standard for Information Technology-Systems Design - Software Design Descriptions

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 required information content and organization for software design descriptions (SDDs) are described. An SDD is a representation of a software design to be used for communicating design information to its stakeholders. The requirements for the design languages (notations and other representational schemes) to be used for conformant SDDs are specified. This standard is applicable to automated databases and design description languages but can be used for paper documents and other means of descriptions.

[External] IEEE Std 730-2002 - IEEE Standard for Software Quality Assurance 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 standard specifies the format and content of software quality assurance plans. It meets the IEEE/EIA 12207.1 requirements for such plans.

[External] IEEE Std 1012-2004 - IEEE Standard for Software Verification and Validation

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

Software verification and validation (V&V) processes determine whether the development products of a given activity conform to the requirements of that activity and whether the software satisfies its intended use and user needs. Software V&V life cycle process requirements are specified for different software integrity levels. The scope of V&V processes encompasses software-based systems, computer software, hardware, and interfaces. This standard applies to software being developed, maintained, or reused [legacy, commercial off-the-shelf (COTS), non-developmental items]. The term software also includes firmware, microcode, and documentation. Software V&V processes include analysis, evaluation, review, inspection, assessment, and testing of software products

[External] IEEE Std 1008-1987 - IEEE Standard for Software Unit Testing

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 standard is presented. The primary objective is to specify a standard approach to software unit testing that can be used as a basis for sound software engineering practice. A second objective is to describe the software engineering concepts and testing assumptions on which the standard approach is based. A third objective is to provide guidance and resource information to assist with the implementation and usage of the standard unit testing approach.

[External] IEEE Std 1002-1987 - IEEE Standard Taxonomy for Software Engineering Standards

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

Describes the form and content of a software engineering standards taxonomy. Applicability is not restricted by software application, size, complexity, criticality, or hardware environment. This taxonomy applies to standards (from the related disciplines of engineering management, systems engineering, computer hardware engineering, computer science, and information science) with which a software engineer would be reasonably acquainted. This taxonomy is application independent. The document 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.

Standard: IEEE Std 1298 - Software Quality Management System. Part 1: Requirements. Adopted From Standards Australia

a.k.a.: 
AS 3563.1-1991

From IEEE Software Engineering Standards Collection:

IEEE Std 1298. This is Australian Standard AS 3563.1-1991. This standard establishes requirements for a software developer’s quality management system. It identifies each of the elements of a quality management system to be designed, developed, and maintained by the developer with the objective of ensuring that the software will meet the requirements of a contract, purchase order, or other agreement.

Defining external document(s)

Standard: IEEE Std 1219 - IEEE Standard for Software Maintenance

ARCHIVAL: this content has been flagged as archival or historical.

From IEEE Software Engineering Standards Collection:

Draft IEEE Std 1219. This standard defines the process for performing the maintenance of software. It prescribes requirements for process, control and management of the planning, execution and documentation of the software maintenance activities.

Replaced by ISO/IEC 14764 IEEEStd 14764-2006
Status (as a standard)
status: 
replaced
Defining external document(s)
Syndicate content