scope:

This standard is applicable to any software, including critical computer software, commercial applications, system software, support software, testware, and firmware during any phase of a system's life cycle. This standard defines the minimum requirements for classifying anomalies, as well as providing additional classifications for projects requiring greater detail. The mandatory classifications are the minimum requirements necessary to establish a standard terminology for anomalies within or between projects and organizations.

To accomplish the classification task, this standard documents the following subjects:

a) Definitions of terms not provided in IEEE Std 610.12-1990¹

b) A basic process (sequence of steps) for classifying and establishing categories of anomalies relating to software products and providing related data and information

c) A standard set of categories and classifications, either mandatory or optional

d) A list of supporting data items

This standard identifies those essential (mandatory) categories needed to establish a common definition. The categories provide a common terminology and concepts to communicate among projects, software development environments, and personnel. It is assumed that all applicable classifications within a mandatory category shall be used for compliance to this standard. This standard also provides categories for additional detail that are not necessarily essential to all projects. These additional categories are identified as optional. This standard is not intended to define procedural or format requirements for using the classification scheme. This standard identifies some classification measures and does not attempt to define all the data supporting the analysis of an anomaly.

The classifications are layered with greater detail in each subsequent layer. For instance, in table 1b the Project phase category has two levels of classifications, and in table 3c the Type category has three levels of classifications. Each project using this classification scheme may choose the level of classification appropriate to that project. Only the first level of classifications is mandatory for each mandatory category.

The classifications in this standard are not exhaustive. Some projects will have requirements that are unique. It is assumed that in those situations the project members will create project-specific categories and/or classifications in addition to the classifications stated in this standard. Anomaly reports generated using the classifications stated in this standard facilitate the generation of statistics and information for trend analysis.

¹Information on references can be found in clause 2.