Please enable JavaScript.
Coggle requires JavaScript to display documents.
Software Quality (Example:ISO/IEC 9126 (Intention (2.Explicitly address…
Software Quality
(By IEEE)The degree to which a system, component, or process meets specified requirements and customer or user needs or expectations.
-
(By ISO)the totality of features and characteristics of a product or service that bear on its ability to satisfy specified or implied needs.
Example:ISO/IEC 9126
-
-
-
-
Intention
2.Explicitly address user needs of a product by allowing for a common language for specifying user requirements that is understandable by users, developers and evaluators.
-
-
-
-
Experiment
3.0 Aim:Investigate
Whether the characteristics, sub characteristics and metrics as described in ISO/IEC 9126 standard of Internal Metrics are applicable to the design
products as suggested by the standard.
How the ISO/IEC 9126 quality attributes can be incorporated, measured and evaluated for design products.
-
-
-
-
-
Conclusions
It is specific enough to be unclear or misleading yet is meant to be general enough to be applicable to all software products. Thus, it is not specific enough to be useful for any particular design product.
Problems
- The standard ignores other characteristics that might be important in design products such as validity and modularity.
- Simple Counts are insufficient to evaluate the quality of design.
- The standard recognises reliability and maintainability as quality characteristics but does not refer to them when considering design products although most software engineers would agree that both characteristics need to be designed into products.
7.Some measures require information that is not available to the designers, such as functional understandability.
- Overlapping definition of concepts can lead to multiple counting when metrics are constructed.
- Some measures require counting items that are not available from design documents, such as computational accuracy and data exchange.
- Some concept definitions overlap, e.g. functional implementation completeness and functional implementation coverage.
- No guidelines or procedures are defined for accumulating the metrics into an overall evaluation.
1.Some concept definitions are ambiguous, e.g. functional compliance.
In the light of its ambiguities and omissions, we conclude that ISO/IEC 9126 in its present format fails to achieve any of its stated objectives.
