|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Jeffrey Voas, "Developing a Usage-Based Software Certification Process," Computer, vol. 33, no. 8, pp. 32-37, August, 2000. | |||
| BibTex | x | ||
| @article{ 10.1109/2.863965, author = {Jeffrey Voas}, title = {Developing a Usage-Based Software Certification Process}, journal ={Computer}, volume = {33}, number = {8}, issn = {0018-9162}, year = {2000}, pages = {32-37}, doi = {http://doi.ieeecomputersociety.org/10.1109/2.863965}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - Computer TI - Developing a Usage-Based Software Certification Process IS - 8 SN - 0018-9162 SP32 EP37 EPD - 32-37 A1 - Jeffrey Voas, PY - 2000 VL - 33 JA - Computer ER - | |||
The methods for certifying software quality continue to multiply. Popular, process-based approaches-- such as ISO 9000 and SEI-CMM--make software publishers take oaths concerning which development standards and processes they will use. These approaches often require auditors to spot-check a publisher's documentation and oaths. Yet even if a certification auditor can verify the publisher's veracity, that verification alone does not guarantee high-quality software.
Given these problems, the author proposes a certification methodology that does not employ publisher oaths and auditors. This certification method employs automated processes to greatly reduce liability while also eliminating the need to dispatch human auditors. The process harnesses the testing resources of end users, drawing upon proven tech-niques such as the methods that made Linux the most popular and reliable of all Unix flavors. Totally product-based, this proposed process assesses how well behaved the software is, not the maturity of the processes used to develop the code.

