Models and Measurements for Quality Assessment of Software
ACM Computing Surveys (CSUR)
Warming up to computers: A study of cognitive and affective interaction over time
CHI '82 Proceedings of the 1982 Conference on Human Factors in Computing Systems
Toward an effective software reliability evaluation
ICSE '78 Proceedings of the 3rd international conference on Software engineering
User-perceived quality of interactive systems
ICSE '78 Proceedings of the 3rd international conference on Software engineering
Quantitative evaluation of software quality
ICSE '76 Proceedings of the 2nd international conference on Software engineering
“Software reliability in online real time environment”
Proceedings of the international conference on Reliable software
Software metrics: an introduction and annotated bibliography
ACM SIGSOFT Software Engineering Notes
Encyclopedia of Computer Science
ANN model for predicting software function point metric
ACM SIGSOFT Software Engineering Notes
An approach to software reliability prediction and quality control
AFIPS '72 (Fall, part II) Proceedings of the December 5-7, 1972, fall joint computer conference, part II
Studying software evolution using artefacts' shared information content
Science of Computer Programming
A framework for integrated software quality prediction using Bayesian nets
ICCSA'11 Proceedings of the 2011 international conference on Computational science and Its applications - Volume Part V
Evaluating maintainability with code metrics for model-to-model transformations
QoSA'10 Proceedings of the 6th international conference on Quality of Software Architectures: research into Practice - Reality and Gaps
Software project control centers: concepts and approaches
Journal of Systems and Software
Hi-index | 0.00 |
A black-box approach typifies current software quality assurance procedures: a program is good it it satisfies certain operating specifications. While it is common to manage the development of software under quality assurance systems previously devised for hardware, the tools of measurement are not transferable owing to the very basic differences in the nature of hardware and software. In the absence of specific, applicable quantitative measurement tools there exists no means of defining the desired level of quality in a computer program, where quality is considered as something beyond correct program functioning, nor of ascertaining whether the desired level has been achieved. A user should be able to specify precisely how good a product he wishes to buy, such things as how easy the program should be to run production with and how easily it can be modified. Rarely can the user even discuss these factors, much less specify the extent of their importance to him.