Software Supportability Standards
There are not many standards addressing software support or software supportability. This site is as of today probably the only place that provides a complete listing of these standards and where to acquire them. In those cases where these standards are publicly available (e.g., military standards), these documents have been included here. In all other cases, a link to the appropriate site has been provided.
The standards have been listed by completeness of all covered software supportability topics.
Software-supportability.org explicitly thanks the U.S. DoD and the UK MoD for making their standards publicly available.
SAE AIR 5121 Software Supportability - An Overview (January 1997 - Reaffirmed November 2003)
Overview:
This Aerospace Information Report (AIR) provides an overview of the issues
relating to the support & supportability of software in computer-based
systems.
Application:
General applicability to all sectors of industry and commerce and to all
types of equipment that contain software.
Organization: Society of Automotive Engineers (SAE)
Address: 400 Commonwealth Drive Warrendale PA 15096-0001 USA
Phone: (+1-877) 606-7323
Fax: (+1-724) 776-5760
Current status: Active
SAE JA1004 Software Supportability Program Standard (July 1998 - Reaffirmed November 2003)
Overview:
This standard defines recommended practices for the achievement of suitable
supportability and through-life support arrangements for software within
an overall systems engineering framework. The Software Supportability
Plan (goals to achieve) and the Software Supportability Case (demonstration
of achievement) are presented as the basis for program management. This
standard is applicable to all projects incorporating software, and aims
to meet the needs of end-users and of organizations that acquire, develop
or provide post-delivery support for software.
Application:
The recommended process is applicable to all projects incorporating software.
The target audience for this document includes software acquisition organizations,
logisticians, developers, supporters, and customers.
Organization: Society of Automotive Engineers (SAE)
Address: 400 Commonwealth Drive Warrendale PA 15096-0001 USA
Phone: (+1-877) 606-7323
Fax: (+1-724) 776-5760
Current status: Active - under reaffirmation
SAE JA1005 Software Supportability Program Implementation Guide (May 2001 - Reaffirmed November 2003)
Overview:
This document identifies recommended practices for the implementation
of a supportability program for software within an overall systems engineering
framework. Guidelines for implementation of a Software Supportability
Plan and associated Software Supportability Case are presented. Recommended
practices are described for establishing a software supportability program
through selection of life cycle activity tasks tailored for the application.
Recommended models and process methods to achieve the life cycle activity
tasks are briefly reviewed and/or referenced.
Application:
The recommended practices are applicable to all projects incorporating
software. The target audience for this document includes software acquisition
organizations, logisticians, developers, supporters, and customers.
Organization: Society of Automotive Engineers (SAE)
Address: 400 Commonwealth Drive Warrendale PA 15096-0001 USA
Phone: (+1-877) 606-7323
Fax: (+1-724) 776-5760
Current status: Active
SAE JA1006 Software Support Concept (June 1999 - Reaffirmed November 2003)
Overview:
This document provides a framework for the establishment of a software
support concept related to the support and supportability of both custom-developed
and Off The Shelf (OTS) software. This document provides information needed
to understand the support aspects that should be covered by a software
supportability program.
Application:
The recommended concept is applicable to all projects incorporating software.
The target audience for this document includes software acquisition organizations,
logisticians, developers, supporters, and customers.
Organization: Society of Automotive Engineers (SAE)
Address: 400 Commonwealth Drive Warrendale PA 15096-0001 USA
Phone: (+1-877) 606-7323
Fax: (+1-724) 776-5760
Current status: Active
IG 70-12 Management process for operational software programs (February 1993)
Overview:
This document establishes the process for the requirements and user analysis,
development, anomaly reporting, problem analysis, assessment of enhancement
proposals, maintenance, testing, configuration, operational test and evaluation,
release, installation and withdrawal of operational programs within the
Spanish Air Force (SAF). This very extensive and complete document (over
300 pages) describes in detail the software support process within the
SAF, not only for operational flight programs (OFPs), but also for ground
systems. Indexes of key documents (e.g., requirements documents, or user
manuals) and formats (e.g., for anomaly reports) are provided. We have
not encountered any other document in the field of software supportability
that is so exhaustive in the description about how to address the full
software life-cycle, including elements which are usually forgotten, such
as replication of software, distribution of documentation, installation
on aircraft and withdrawal of obsolete versions. As a curiosity, it should
be highlighted that the originating body is the Logistic Support Command
of the SAF (MALOG).
Application:
This standard is applicable to all Spanish Air Force projects requiring
the development or support of airborne or ground software.
Organization: Spanish Air Force - MALOG
AFOTEC-PAM-99-102 Volume 2 Software Support Life Cycle Process Evaluation guide (August 1994)
File: (PDF, 8478 kB)
Overview:
The purpose of this pamplet is to provide the U.S. Air Force Operational
Test and Evaluation Center (AFOTEC) software test manager and the deputy
for software evaluation information needed to eveluate software life cycle
processes as they influence overall software supportablity. In this pamplet
are the means to track the processes affecting software supportability,
beginning as early as necessary to provide insight into the quality of
the evolving software products, software support resources, and operational
support life cycle procedures themselves. A questionnaire is provided
indicating the issues to be raised at each moment of the sofwtare life-cycle,
including the rationale underlying such questions..
Application:
This guide is internal to the USAF Operational Test and Evaluation Center
(AFOTEC).
Organization: U.S.A.F. Operational Test and Evaluation Center
Address: Kirtland AFB, New Mexico, U.S.A.
Current status: Unknown
MIL-HDBK-347 Mission-Critical Computer Resources Software Support (May 1990)
File: (PDF, 3785 kB)
Overview:
This document is an attempt by the DoD to improve the operational viability
of its weapons systems while keeping support costs under control, standarizing
related concepts and management procedures. The document covers pre- and
post-deployment software support operations. In addition to a standard
definition and detailed description of software support and the post-deployment
software support process, this handbook provides guidance in the areas
of post-deploymen software support and transition planning, support resource
analysis, resource requirements planning and support concept alternatives.
Application:
The recommended guidelines are applicable to all US DoD projects requiring
development of software.
Organization: US Department of Defense (DoD)
Address:
Chief, Bibliographic Systems
U.S. Government Printing Office
Sales Management Division (SSMB)
Washington, DC 20402
Current status: Active
MIL-HDBK-1467 Acquisition of Software Environments and Support Software (December 1997)
File: (PDF, 175 KB)
Overview:
This document provides an overview about the US DoD recommendations for
the acquisition of software environments and support software, mainly
for the development phase, but in principle also for the support phase.
Though very oriented towards the US DoD acquisition, it is an interesting
document insofar it provides insight about the aspects to be considered
for the acquisition of these elements, which may significantly impact
any long-term support.
Application:
The recommended guidelines are applicable to all US DoD projects requiring
development of software.
Organization: US Department of Defense (DoD)
Address:
Chief, Bibliographic Systems
U.S. Government Printing Office
Sales Management Division (SSMB)
Washington, DC 20402
Current status: Active
DEF STAN 00-60 Integrated Logistic Support - Part 3: Guidance for Application Software Support (Issue 3, 24th September 2004)
File: (PDF, 334 kB)
Overview:
This document describes the UK MoD policy and requirements for the application
of Logistic Support Analysis (LSA) to software aspects of systems. It
is divided into two sections, the first of which provides an introduction,
defines terms and abbreviations, introduces the software life-cycle and
lists a number of related documents. Information on the management and
planning of LSA for software is also provided, together with a description
of a number of factors that have been identified as impacting on software
supportability. The second section describes the application of LSA to
software aspects of systems. It provides tools, interpretations and guidelines
to support the application of the LSA tasks and subtasks, as described
in Part 1 of DEF STAN 00-60, to systems that include software.
Application:
The recommended process is applicable to all UK MoD systems containing
software. The intended audience are both customers and contractors.
Organization: UK Ministry of Defence (MoD) - Directorate of Standardization
Address: Kentigern House, 65 Brown Street, Glasgow G2 8EX, UK
Phone: +44 (0)141-224-2531/2
Fax: +44 (0)141-224-2503
E-mail: enquiries@dstan.mod.uk
Current status: Active
CRLCMP - Computer Resources Life-Cycle Management Plan (1998)
Overview:
A set of document templates prepared by the U.S. Army CECOM Software Engineering Center, the Computer Resources Life Cycle Management Plan (CRLCMP) contains the acquisition, development, transition, and support requirements for the computer resources of an Army system. The CRLCMP identifies the organizations/individuals responsible for the performance of related tasks over the system's life cycle. Being a stand alone document, the CRLCMP can also be used as an annex to the Acquisition Plan, and Integrated Logistics Support Plan (ILSP).
Application:
The recommended process is applicable to U.S. Army systems containing
software.
Organization: U.S. Army CECOM Software Engineering Center
Current status: Active
IEEE 1044 - IEEE Standard Classification for Software Anomalies (1993)
Overview:
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.
Application:
In principle all software systems.
Organization: Institute of Electrical and Electronics Engineers (IEEE)
Address: IEEE Operations Center, 445 Hoes Lane, Piscataway, New
Jersey 08854-1331, USA
Phone: (+1-732)-981-0060
Fax: (+1-732)-981-1721
Current status: Active - Reaffirmed 2002
IEEE 1063- IEEE Standard for Software User Documentation (2001)
Overview:
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.
Application:
In principle all software systems.
Organization: Institute of Electrical and Electronics Engineers (IEEE)
Address: IEEE Operations Center, 445 Hoes Lane, Piscataway, New
Jersey 08854-1331, USA
Phone: (+1-732)-981-0060
Fax: (+1-732)-981-1721
Current status: Active
IEEE 1219 - IEEE Standard for Software Maintenance (1998)
Overview:
The process for managing and executing software maintenance activities
is described.
Application:
In principle all software systems.
Organization: Institute of Electrical and Electronics Engineers (IEEE)
Address: IEEE Operations Center, 445 Hoes Lane, Piscataway, New
Jersey 08854-1331, USA
Phone: (+1-732)-981-0060
Fax: (+1-732)-981-1721
Current status: Active
J-STD-016-1995 Standard for Information Technology/Software Life Cycle Processes/Software Development/Acquirer-Supplier Agreement (1995)
Overview:
This standard defines a set of software development activities and resulting
software products. It provides a framework for software development planning
and engineering. It is also intended to merge commercial and Government
software development requirements within the framework of the software
life cycle process requirements of the Electronic Industries Association
(EIA), Institute of Electrical and Electronics Engineers (IEEE) and International
Organization for Standardization (ISO). The term "software development"
is used as an inclusive term encompassing new development, modification,
reuse, reengineering, maintenance, and all other processes or activities
resulting in software products.
Application:
In principle all purchased software systems.
Organization: Institute of Electrical and Electronics Engineers (IEEE)
Address: IEEE Operations Center, 445 Hoes Lane, Piscataway, New
Jersey 08854-1331, USA
Phone: (+1-732)-981-0060
Fax: (+1-732)-981-1721
Current status: Isued for Trial use
ISO 14764 - Information technology -- Software maintenance (1999)
Overview:
No overview available yet - please send
us one!
Application:
In principle all software systems.
Organization: International Organization for Standardization (ISO)
Address: 1, rue de Varembé, Case postale 56 - CH-1211 Geneva
20, Switzerland
Phone: (+41) 22-749-01-11
Fax: (+41) 22-733-34-30
Current status: Active
ISO 12207 - Information technology -- Software life cycle processes (1995)
Overview:
Establishes a system for software life cycle processes with well-defined
terminology. Contains processes, activities and tasks that are to be applied
during the acquisition of a system that contains software, a stand-alone
software product and software services. It also addresses software maintenance.
Application:
In principle all software systems.
Organization: International Organization for Standardization (ISO)
Address: 1, rue de Varembé, Case postale 56 - CH-1211 Geneva
20, Switzerland
Phone: (+41) 22-749-01-11
Fax: (+41) 22-733-34-30
Current status: Active
ISO/IEC TR 15271 - Guide for ISO/IEC 12207 (Software Life Cycle Processes) (1998)
Overview:
The purpose of this technical report is to provide guidance to the application
of ISO/IEC 12207. This Technical Report elaborates
on factors which should be considered when applying ISO/IEC 12207 and
does this in the context of the various ways in which this standard can
be applied. This guidance is not intended to provide the rationale for
the requirements of the ISO/IEC 12207 standard. The three fundamental
life cycle models are discussed and examples of tailoring are provided.
Application:
In principle all software systems.
Organization: International Organization for Standardization (ISO)
Address: 1, rue de Varembé, Case postale 56 - CH-1211 Geneva
20, Switzerland
Phone: (+41) 22-749-01-11
Fax: (+41) 22-733-34-30
Current status: Active
Any standard missing? Please inform our Webmaster.
14th March 2008
Hosted by:
Exobits