Beyond information quality: fitness for purpose and electronic information resource use
Journal of Information Science
Inroads to software quality: “how to” guide and toolkit
Inroads to software quality: “how to” guide and toolkit
Value-based software engineering (VBSE): a value-driven approach to product-line engineering
Proceedings of the first conference on Software product lines : experience and research directions: experience and research directions
Software Risk Management: Principles and Practices
IEEE Software
When the Pursuit of Quality Destroys Value
IEEE Software
Value-based software engineering: reinventing
ACM SIGSOFT Software Engineering Notes
A Model and Prototype Tool to Manage Software Risks
APAQS '00 Proceedings of the The First Asia-Pacific Conference on Quality Software (APAQS'00)
GEQUAMO—A Generic, Multilayered, Customisable, Software Quality Model
Software Quality Control
Information Technology, Security and Risk Management
Information Technology, Security and Risk Management
Integrated modeling of business value and software processes
SPW'05 Proceedings of the 2005 international conference on Unifying the Software Process Spectrum
Information Systems Typology According to Quality Attributes
International Journal of Human Capital and Information Technology Professionals
Hi-index | 0.00 |
The ultimate object of software development should be to deliver value to all stakeholders. The traditional approach to delivering this value is to ensure that the software developed is of the highest quality. A number of quality models have been proposed to specify or describe what constitutes high quality software. The ISO9126 is one such model and perhaps the most comprehensive. Similarly, there are several methods, frameworks and guidelines for ensuring software quality in either the development or use process or both. Software Quality Management and Risk Management are probably the two most popular methods employed by developers during software development and implementation to deliver quality. In this paper the authors examine whether, and to what extent, the implied value propositions of software products as portrayed by the ISO9126 quality model and the prescribed processes in Software Quality Management and Risk Management, map onto user value perceptions and experiences. An ontology of value, in the form of a value tree, is developed and used to identify and analyse the key value dimensions of the ISO9126 quality model and the Software Quality Management and Risk Management process methods. These are then mapped onto contextualised user value characterisations derived from the extant literature. Differences identified are analysed and discussed and the authors suggest approaches that could narrow the perennial gap between idealised quality product and process models and stakeholder perceptions and actualisations of software value.