Correctability Requirement
- Correctability Requirement
- any user-oriented
maintainability requirement
that specifies a minimum required amount of the
quality factor
correctability
The typical objectives of a correctability requirement are
to:
- Ensure that minor defects in an application or component
can be easily and quickly:
- Identified,
- Understood, and
- Corrected.
- Minimize defect correction costs.
The following are typical examples of correctability
requirements:
- “The average person-time required to fix a category
3 defect (including regression testing and documentation
update) shall not exceed two person days.”
- “The average person-time required to fix a category
2 defect (including regression testing and documentation
update) shall not exceed one person week.”
The following guidelines have been found to be useful when
producing correctability requirements:
- The scope of a correctability requirement can be:
- Correctability should include:
- Correcting defects in or updating the associated
documentation.
- Regression or new testing.
- Because correctability requirements only refer to
correction that occur between releases of major new
versions of the application or component (i.e., development
that involves changes to the architecture and significant
portions of the design and implementation), they are
restricted to the correction of minor defects.
- Correctability requirements may be specified in terms
of average person-time or cost to correct the different
categories of minor defects.
- Because correctability requirements are difficult to
quantify, they may occasionally be specified more as desired
goals rather than as validatable requirements. Nevertheless,
they should
not be unnecessarily specified in terms of
architectural, design, and implementation constraints and the
use of industry best practices that tend to produce
correctable applications when followed such as:
- Layered architectures.
- Modular software.
- Information hiding of implementation.
- Well-defined interfaces.
- Object-orientation and component-based
development.
- Complete and current documentation.
- Adherence to project conventions.