Software Quality Assurance Techniques
The word 'quality' is an elusive term and is difficult to define precisely. Its meaning, and the steps to achieve it,
may differ from one organization to another, and standards for quality may vary. There are, however, certain
characteristics that appear to be well understood and are being used to measure quality in software products.
The ‘Quality Model’ established in the first part of the 'ISO 9126 Standard', ‘ISO 9126-1’, defines
a framework for software quality in a structured set of characteristics and sub-characteristics.
The IEEE Standard 610-1990 defines software quality as follows:
In all cases, any meaningful definition of quality must include two essential characteristics for any
substantive discussion about quality. These characteristics are:
1) Quality must be measurable, and
2) Quality should be predictable.
We offer the following services:
< Back to 'Consulting' page
The word 'quality' is an elusive term and is difficult to define precisely. Its meaning, and the steps to achieve it,
may differ from one organization to another, and standards for quality may vary. There are, however, certain
characteristics that appear to be well understood and are being used to measure quality in software products.
The ‘Quality Model’ established in the first part of the 'ISO 9126 Standard', ‘ISO 9126-1’, defines
a framework for software quality in a structured set of characteristics and sub-characteristics.
The IEEE Standard 610-1990 defines software quality as follows:
- The degree to which a system, component, or process meets specified requirements; and
- The degree to which a system, component, or process meets customer or user needs or expectations.
In all cases, any meaningful definition of quality must include two essential characteristics for any
substantive discussion about quality. These characteristics are:
1) Quality must be measurable, and
2) Quality should be predictable.
We offer the following services:
- Help building a sustainable foundation for a culture of quality in the organization
- Definition of 'Quality Goals' and development of 'Software Quality Assurance Plans'
- Definition of quality 'Entry and Exit Criteria' for each step of the development process from concept to
delivery and beyond
- Help reviewing product documentation including requirements and design specification, test plans, and
release and user documentation
- Provide metrics to demonstrate convergence (or lack thereof) to a defined general release criteria
- Pre-release quality evaluation and risk analysis in order to support the 'Ship/NoShip' decision
- Post-release quality evaluation in order to contain failures and potential damage in the field
< Back to 'Consulting' page
OnTest
| Software Testing & Quality Engineering |
 | |  | |  | |  | |  |
| All rights reserved |