Scribd
Upload
481 views

Active IEEE Standards For Software Development

This document provides a summary of active IEEE standards for software development, organized into sections on system planning, system analysis, system design, and system implementation. Some of the standards described include IEEE 1058-1998 for software project management plans, IEEE 1058.1-1987 for the format and contents of software project management plans, and IEEE 830-1998 for software requirements specifications. In total, 14 different IEEE standards related to software development processes are summarized.

Uploaded by

poojanew
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
481 views

Active IEEE Standards For Software Development

This document provides a summary of active IEEE standards for software development, organized into sections on system planning, system analysis, system design, and system implementation. Some of the standards described include IEEE 1058-1998 for software project management plans, IEEE 1058.1-1987 for the format and contents of software project management plans, and IEEE 830-1998 for software requirements specifications. In total, 14 different IEEE standards related to software development processes are summarized.

Uploaded by

poojanew
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

A Survey: Active IEEE Standards for Software Development

Dr.Cagatay Undeger

16.02.2008

1 SYSTEM PLANNING
1.1 1058-1998 IEEE standard for software project management plans
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.

1.2 1058.1-1987 IEEE standard for software project management plans


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.

1.3 828-2005 IEEE Standard for Software Configuration Management Plans


Describes the IEEE standard for software configuration management plans, establishes the minimum required
contents of a software configuration management plan and defines the specific activities to be addressed and
their requirements for any portion of a software product's life cycle.

1.4 730-2002 IEEE Standard for Software Quality Assurance Plans


Uniform, minimum acceptable requirements for the preparation and content of software quality assurance
plans (SQAPs) are provided. This standard applies to the development and maintenance of critical software.
For non-critical software, or for software that has already been developed, a subset of the requirements of this
standard may be applied

1.5 1012-2004 IEEE Standard for Software Verificiation and Validation


Software verification and validation (V&V) processes, which determine whether development products of a
given activity conform to the 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

1.6 1074-2006 IEEE Standard for Developing a Software Project Life Cycle Process
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.

1.7 1061-1998 IEEE standard for a software quality metrics methodology


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.
1.8 1028-1997 IEEE Standard for Software Reviews
The IEEE standard for software reviews defines five types of software reviews, together with procedures
required for the execution of each review type. This standard is concerned only with the reviews; it does not
define procedures for determining the necessity of a review, nor does it specify the disposition of the results of
the review. Review types include management reviews, technical reviews, inspections, walk-throughs, and
audits.

1.9 1062-1998 IEEE recommended practice for software acquisition


A set of useful quality practices that can be selected and applied during one or more steps in a software
acquisition process is described. This recommended practice can be applied to software that runs on any
computer system regardless of the size, complexity, or criticality of the software, but is more suited for use on
modified-off-the-shelf software and fully developed software.

2 SYSTEM ANALYSIS
2.1 830-1998 IEEE recommended practice for software requirements specifications
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 the requirements of
software to be developed, but can also be applied to assist in the selection of in-house and commercial
software products. Guidelines for compliance with IEEE/EIA Std 12207.1-1997 are also provided.

3 SYSTEM DESIGN
3.1 1016-1998 IEEE recommended practice for software design descriptions
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.

4 SYSTEM IMPLEMENTATION
4.1 829-1998 IEEE standard for software test documentation
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.

4.2 1008-1987 IEEE standard for software unit testing


An integrated approach to systematic and documented unit testing is described. The approach uses unit design
and unit implementation information, in addition to unit requirements, to determine the completeness of the
testing.

4.3 1044-1993 IEEE standard classification for software anomalies


A uniform approach to the classification of anomalies found in software and its documentation is provided.
The processing of anomalies discovered during any software life cycle phase are described, and
comprehensive lists of software anomaly classifications and related data items that are helpful to identify and
track anomalies are provided. This standard is not intended to define procedural or format requirements for
using the classification scheme. It does identify some classification measures and does not attempt to define
all the data supporting the analysis of an anomaly.

4.4 1063-2001 IEEE standard for software user documentation


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.

You might also like