I've reading through the ISO 9126 Standard doc (in case you don't have ISO numbers memorized, it's
Software engineering - Product quality) and amongst other interesting things thus far, I encountered a section titled "Quality model for external an internal quality" which outlines areas of an application that should be tested; test types, in essence.
Of those test types, one was Reliability. It defined Reliability as:
The capability of the software product to maintain a specified level of performance when used under specified conditions.
...but what really grabbed me was the first note under that definition:
NOTE 1 Wear or ageing does not occur in software. Limitations in reliability are due to faults in requirements, design, and implementation. Failures due to these faults depend on the way the software product is used and the program options selected rather than on elapsed time.
This blatantly points the finger to
requirements, design, and implementation for when dealing with reliability.
I think to some, this might seem to be a "duh" statement, but that whole note is quite enabling as a software test engineer.
No comments:
Post a Comment