Abstract
Software qualities are in many cases tacit and hard to measure. Thus, there is a potential risk that they get lower priority than deadlines, cost and functionality. Yet software qualities impact customers, profits and even developer efficiency. This paper presents a method to evaluate the priority of software qualities in an industrial context. The method is applied in a case study, where the ISO 9126 model for software quality is combined with Theory-W to create a process for evaluating the alignment between success-critical stakeholder groups in the area of software product quality. The results of an exploratory case study using this tool is then presented and discussed. It is shown that the method provides valuable information about software qualities.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Beck, K.: Extreme Programming Explained: Embrace Change. Addison-Wesley, Reading (2000)
Kitchenham, B., Pfleeger, S.: Software quality: The elusive target. IEEE Software 13(1), 12–21 (1996)
Yourdon, E.: When good enough software is best. IEEE Software 12(3), 79–81 (1995)
Boehm, B., Ross, R.: Theory-w software pro ject management principles and examples. IEEE Transactions on Software Engineering 15(7), 902–916 (1989)
Garvin, D.A.: What does “product quality” really mean? Sloan Management Review 26(1), 25–43 (1984)
Hoyer, R.W., Hoyer, B.B.Y.: What is quality? Quality Progress 34(7), 53–62 (2001)
Basili, V.R.: Evolving and packaging reading technologies. Journal of Systems and Software, Achieving Quality in Software 38(1), 3–12 (1997)
Boehm, B., Basili, V.: Software defect reduction top 10 list. Computer 34(1), 135–137 (2001)
Milicic, D.: Software Quality Models and Philosophies. In: Software Quality Attributes and Trade-Offs, pp. 3–19. Blekinge Institute of Technology (2005)
ISO9126: Software engineering – product quality – part 1: Quality model. International Standards Organization (2001)
Dromey, R.: Concerning the chimera. Software, IEEE 13(1), 33–43 (1996)
Chung, L., Nixon, B., Yu, E., Mylopoulos, J.: Non-Functional Requirements in Software Engineering. Kluwer Academic, Dordrecht (2000)
Herzwurm, G., Schockert, S., Pietsch, W.: Qfd for customer-focused requirements engineering. In: 11th IEEE International Requirements Engineering Conference, 2003, pp. 330–338 (September 2003)
Boehm, B., Jain, A.: An initial theory of value-based software engineering. Value-Based Software Engineering, 15–37 (2006)
Leffingwell, D., Widrig, D.: Managing software requirements: a unified approach. Addison-Wesley, Reading (1999)
Barney, S., Wohlin, C.: Software product quality questionnaire (2008), http://www.bth.se/tek/aps/sba
Berander, P., Jönsson, P.: A goal question metric based approach for efficient measurement framework definition. In: Proceedings of the 2006 ACM/IEEE International Symposium on Empirical Software Engineering (ISESE 2006), pp. 316–325. ACM, New York (2006)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2009 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Barney, S., Wohlin, C. (2009). Software Product Quality: Ensuring a Common Goal. In: Wang, Q., Garousi, V., Madachy, R., Pfahl, D. (eds) Trustworthy Software Development Processes. ICSP 2009. Lecture Notes in Computer Science, vol 5543. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-01680-6_24
Download citation
DOI: https://doi.org/10.1007/978-3-642-01680-6_24
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-01679-0
Online ISBN: 978-3-642-01680-6
eBook Packages: Computer ScienceComputer Science (R0)