Introduction

The IEEE (Eye-triple-E) is a non-profit, technical professional association of more than 360,000 individual members in approximately 175 countries. The full name is the Institute of Electrical and Electronics Engineers, Inc., although the organization is most popularly known and referred to by the letters I-E-E-E.

 Through its members, the IEEE is a leading authority in technical areas ranging from computer engineering, biomedical technology and telecommunications, to electric power, aerospace and consumer electronics, among others.

 

Note: This is a non exhaustive list:

 

 

IEEE Std 610.1 0-1 994 IEEE Standard Glossary of Computer Hardware Terminology
Approved June 14,1994
Abstract:
Terms pertaining to computer hardware are defined. Terms falling under the categories of computer architecture, computer storage, general hardware concepts, peripherals, and processors and components are included.

Keywords: computer, hardware, definition, glossary, terminology

 

IEEE STD 610.12-1990 IEEE Standard Glossary of Software Engineering Terminology

Abstract:
IEEE Std 610.12-1990, IEEE Standard Glossary of Software Engineering Terminology, identifies terms currently in use in the field of Software Engineering. Standard definitions for those terms are established.

IEEE Std 730-2002 (Revision of IEEE Std 730-1998) IEEE Standard for Software Quality Assurance Plans
Approved 12 September 2002
Abstract:
The standard specifies the format and content of software quality assurance plans. It meets the IEEE⁄EIA 12207.1 requirements for such plans.

Keywords: assurance, quality, software quality

IEEE Std 828-1998 (Revision of IEEE Std 828-1990) IEEE Standard for Software Configuration Management Plans
Approved 25 June 1998
Abstract:
The minimum required contents of a Software Configuration Management Plan (SCMP) are established, and the specific activities to be addressed and their requirements for any portion of a software product's life cycle are defined.

Keywords:
configuration control board, configuration items, software configuration management, software configuration management activities

 

IEEE Std 829-1998 (Revision of IEEE Std 829-1983) IEEE Standard for Software Test Documentation
Approved 16 September 1998
Abstract:
A set of basic software test documents is described. This standard specifies the form and content of individual test documents. It does not specify the required set of test documents.

Keywords:
test case specification, test design specification, test incident report, test item transmittal report, test log, test plan, test procedure specification, test summary report

 

IEEE Std 830-1998 (Revision of IEEE Std 830-1993) IEEE Recommended Practice for Software Requirements Specifications
Approved 25 June 1998
Abstract:
The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE⁄EIA 12207.1-1997 are also provided.

Keywords:
contract, customer, prototyping, software requirements specification, supplier, system requirements specifications

 

IEEE Std 1012-1998 (Revision of IEEE Std 1012-1986) IEEE Standard for Software Verification and Validation
Approved 9 March 1998
Abstract:
Software verification and validation (V&V) processes, which determine whether development products of a given activity conform to theIEEE Std 1012-1998 requirements of that activity, and whether the software satisfies its intended use and user needs, are described. This determination may include analysis, evaluation, review, inspection, assessment, and testing of software products and processes. V&V processes assess the software in the context of the system, including the operational environment, hardware, interfacing software, operators, and users.
Keywords:
software integrity, software life cycle processes, verification and validation

 

IEEE Std 1012a-1998(Supplement to IEEE Std 1012-1998)
Supplement to IEEE Standard for Software Verifcation and Validation: Content Map to IEEE⁄EIA 12207.1-1997
Approved 16 September 1998
Abstract:
The relationship between the two sets of requirements on plans for verification and validation of software, found in IEEE Std 1012-1998 and IEEE⁄EIA 12207.1-1997, is explained so that users may produce documents that comply with both standards.

Keywords:
life cycle data plans, qualification test, verification and validation

 

IEEE Std 1016-1998 (Revision of IEEE Std 1016-1987)
IEEE Recommended Practice for Software Design Descriptions
Approved 23 September 1998
Abstract:
The necessary information content and recommendations for an organization for Software Design Descriptions (SDDs) are described. An SDD is a representation of a software system that is used as a medium for communicating software design information. This recommended practice is applicable to paper documents, automated databases, design description languages, or other means of description.

Keywords:
software design, software design description, software life cycle process

 

 

IEEE Std 1058-1998 (Revision and redesignation of IEEE Std 1058.1-1987, incorporating IEEE Std 1058-1998 and IEEE Std 1058a-1998)
IEEE Standard for Software Project Management Plans
Approved 8 December 1998
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.

Keywords:
management plans, software project management plans

 

 

IEEE Std 1059-1993 IEEE Guide for Software Verification and Validation Plans
Approved December 2,1993
Abstract: Guidance in preparing Software Verification and Validation Plans (SVVPs) that comply with IEEE Std 1012-1986 are IEEE Std 1012-1986 specifies the required content for an SVVP. This guide recommends approaches to Verification and Validation (V&V) planning. This guide does not present requirements beyond those stated in IEEE Std 1012-1986.
Keywords: baseline change assessment, life cycle phases, master schedule, V&V tasks

 

 

IEEE Std 1061-1998 (Revision of IEEE Std 1061-1992) IEEE Standard for a Software Quality Metrics Methodology
Approved 8 December 1998

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.

Keywords:
direct metric, metrics framework, quality factor, quality subfactor, software quality metric

 

IEEE Std 1063-2001 (Revision of IEEE Std 1063-1987) IEEE Standard for Software User Documentation
Approved 5 December 2001

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.

Keywords:
online help, software user documentation, user manual

 

IEEE Std 1074-1997 (Revision of IEEE Std 1074-1995; Replaces IEEE Std 1074.1-1995) IEEE Standard for Developing Software Life Cycle Processes
Approved 9 December 1997
Abstract:
A process for creating a software life cycle process is provided. Although this standard is directed primarily at the process architect, it is useful to any organization that is responsible for managing and performing software projects.

Keywords:
software life cycle, software life cycle model, software life cycle process

 

IEEE Std 1220-1998 (Revision of IEEE Std 1220-1994) IEEE Standard for Application and Management of the Systems Engineering Process
Approved 8 December 1998

Abstract:
The interdisciplinary tasks, which are required throughout a systemÕs life cycle to transform customer needs, requirements, and constraints into a system solution, are defined. In addition, the requirements for the systems engineering process and its application throughout the product life cycle are specified. The focus of this standard is on engineering activities necessary to guide product development while ensuring that the product is properly designed to make it affordable to produce, own, operate, maintain, and eventually to dispose of, without undue risk to health or the environment.

Keywords:
component, hardware, interface, life cycle processes, software, system life cycle, systems engineering

IEEE Std 1233-1998 (Includes IEEE Std 1233-1996 and IEEE Std 1233a-1998) IEEE Guide for Developing System Requirements Specifications
IEEE Std 1233-1996 Approved 17 April 1996
IEEE Std 1233a-1998 Approved 8 December 1998
Abstract:
Guidance for the development of the set of requirements, System Requirements Specification (SyRS), that will satisfy an expressed need is provided. Developing an SyRS includes the identification, organization, presentation, and modification of the requirements. Also addressed are the conditions for incorporating operational concepts, design constraints, and design configuration requirements into the specification. This guide also covers the necessary characteristics and qualities of individual requirements and the set of all requirements.

Keywords:
requirement, SyRS, system, system requirements specification

 

IEEE Std 1320.1-1998 IEEE Standard for Functional Modeling Language-Syntax and Semantics for IDEF0
Approved 25 June 1998

Abstract:
IDEF0 function modeling is designed to represent the decisions, actions, and activities of an existing or prospective organization or system. IDEF0 graphics and accompanying texts are presented in an organized and systematic way to gain understanding, support analysis, provide logic for potential changes, specify requirements, and support system-level design and integration activities. IDEF0 may be used to model a wide variety of systems, composed of people, machines, materials, computers, and information of all varieties and structured by the relationships among them, both automated and nonautomated. For new systems, IDEF0 may be used first to define requirements and to specify functions to be carried out by the future system.
As the basis of this architecture, IDEF0 may then be used to design an implementation that meets these requirements and performs these functions. For existing systems, IDEF0 can be used to analyze the functions that the system performs and to record the means by which these are done.

Keywords:
enterprise, functional modeling language, IDEF0, language, modeling language

 
IEEE Std 1320.2-1998 IEEE Standard for Conceptual Modeling Language Syntax and Semantics for IDEF1X97 (IDEFobject)
Approved 25 June 1998

Abstract:
IDEF1X97consists of two conceptual modeling languages. The key-style language supports data⁄information modeling and is downward compatible with the US government s 1993 standard, FIPS PUB 184. The identity-style language is based on the object model with declarative rules and constraints. IDEF1X97 identity style includes constructs for the distinct but related components of object abstraction: interface, requests, and realization; utilizes graphics to state the interface; and defines a declarative, directly executable Rule and Constraint Language for requests and realizations. IDEF1X97 conceptual modeling supports implementation by relational databases, extended relational databases, object databases, and object programming languages. IDEF1X97 is formally defined in terms of first order logic. A procedure is given whereby any valid IDEF1X97 model can be transformed into an equivalent theory in first order logic. That procedure is then applied to a meta model of IDEF1X97 to define the valid set of IDEF1X97 models.

Keywords:
conceptual schema, data model, IDEF1X, IDEF1X97, identity style, information model,key style, object model

 

IEEE Std 1471-2000 IEEE Recommended Practice for Architectural Description of Software-Intensive Systems
Approved 21 September 2000
Abstract:
This recommended practice addresses the activities of the creation, analysis, and sustainment of architectures of software-intensive systems, and the recording of such architectures in terms of architectural descriptions . A conceptual framework for architectural description is established.
The content of an architectural description is defined. Annexes provide the rationale for key concepts and terminology, the relationships to other standards, and examples of usage.

Keywords:
architectural description, architecture, software-intensive system, stakeholder concerns, system stakeholder, view, viewpoint

 

 

IEEE Std 1490-2003 (Revision of IEEE Std 1490-1998) IEEE Guide Adoption of PMI Standard A Guide to the Project Management Body of Knowledge
Year: 2004

Abstract: No abstract available

 

IEEE 2001 Draft 7.3 2001-08 22 IEEE Draft Recommended Practice for the Internet--Web Site Engineering, Web Site Management and Web Site Life Cycle.
Abstract:
This document is an unapproved draft of a proposed IEEE-SA Standard USE AT YOUR OWN RISK.
As such, this document is subject to change. Permission is hereby granted for IEEE Standards Committee participants to reproduce this document for purposes of IEEE standardization activities only. Prior to submitting this document to another standard development organization for standardization activities, permission must first be obtained from the Manager, Standards Licensing and Contracts, IEEE Standards Activities Department. Other entities seeking permission to reproduce portions of this document must obtain the appropriate license from the Manager, Standards Licensing and Contracts, IEEE Standards Activities Department. The IEEE is the sole entity that may authorize the use of IEEE owned trademarks, certification marks, or other designations that may indicate compliance with the materials contained herein.

 

 

 

ISO⁄IEC 12207.0-1996 lndustry Implementation of International Standard (ISO⁄IEC 12207) Standard for Information Technology- Software life cycle processes
March 1998

Abstract: ISO⁄IEC 12207 provides a common framework for developing and managing software. IEEE⁄EIA 12207.0 consists of the clarifications, additions, and changes accepted by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Association (EIA) as formulated by a joint project of the two organizations. IEEE⁄EIA 12207.0 contains concepts and guidelines to foster better understanding and application of the standard. Thus this standard provides industry a basis for software practices that would be usable for both national and international business.

Keywords: acquisition process, audit, configuration management, development process, maintenance process, operation process, quality assurance, supply process, tailoring process, validation, verification

 

IEEE⁄EIA 12207.1-1997 (A Joint Guide Developed by IEEE and EIA) IEEE⁄EIA Guide Industry Implementation of International Standard ISO⁄IEC 12207: 1995 (ISO⁄IEC 12207) Standard for Information Technology Software life cycle processes Life cycle data
April 1998

Abstract:
ISO⁄IEC 12207 provides a common framework for developing and managing software. IEEE⁄EIA 12207.0 consists of the clarifications, additions, and changes accepted by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Association (EIA) as formulated by a joint project of the two organizations. IEEE⁄EIA 12207.1 provides guidance for recording life cycle data resulting from the life cycle processes of IEEE⁄EIA 12207.0.

Keywords: acquisition process, audit, configuration management, development process, maintenance process, operation process, quality assurance, supply process, tailoring process, validation, verification

 

IEEE⁄EIA 12207.2-1997 Industry lmplementation of International Standard ISO⁄IEC 12207: 1995 (ISO⁄IEC 12207) Standard for Information Technology Software life cycle processes lmplementation considerations
April 1998
Abstract:

 ISO⁄IEC 12207 provides a common framework for developing and managing software. IEEE⁄EIA 12207.0 consists of the clarifications, additions, and changes accepted by the lnstitute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Association (EIA) as formulated by a joint project of the two organizations. IEEE⁄EIA 12207.2 provides implementation consideration guidance for the normative clauses of IEEEIEIA 12207.0. The guidance is based on software industry experience with the life cycle processes presented in IEEE⁄EIA 12207.0.

Keywords: acquisition process, audit, configuration management, development process, maintenance process, operation process, quality assurance, supply process, tailoring process, validation, verification