Difference between revisions of "Software quality"
Karl Jones (Talk | contribs) (→See also) |
Karl Jones (Talk | contribs) (→External links) |
||
| Line 24: | Line 24: | ||
* [https://en.wikipedia.org/wiki/Software_quality Software quality] @ Wikipedia | * [https://en.wikipedia.org/wiki/Software_quality Software quality] @ Wikipedia | ||
| + | |||
| + | [[Category:Computer science]] | ||
Revision as of 08:06, 3 April 2016
In the context of software engineering, software quality refers to two related but distinct notions that exist wherever quality is defined in a business context.
Software functional quality
Software functional quality reflects how well it complies with or conforms to a given design, based on functional requirements or specifications. That attribute can also be described as the fitness for purpose of a piece of software or how it compares to competitors in the marketplace as a worthwhile product;
Functional quality is typically enforced and measured through software testing.
Software structural quality
Software structural quality refers to how it meets non-functional requirements that support the delivery of the functional requirements, such as robustness or maintainability, the degree to which the software was produced correctly.
Structural quality is evaluated through the analysis of the software inner structure, its source code, at the unit level, the technology level and the system level, which is in effect how its architecture adheres to sound principles of software architecture outlined in a paper on the topic by OMG.
See also
External links
- Software quality @ Wikipedia
