Software quality, non-functional software requirements and IT-business alignment

Software Quality Journal

Volumn 18, Issue 3, 2010, Pages 361-385

  Haigh, Maria ^a  

^a UNIVERSITY OF WISCONSIN MILWAUKEE   (United States)

Author keywords

IT business alignment; Non functional software requirements; Requirements analysis; Software quality; Software stakeholders

Indexed keywords

COMPUTER SOFTWARE SELECTION AND EVALUATION; REQUIREMENTS ENGINEERING;

DEVELOPMENT PROCESS; IT-BUSINESS ALIGNMENTS; NON-FUNCTIONAL; REQUIREMENTS ANALYSIS; SOFTWARE PRODUCTS; SOFTWARE QUALITY; SOFTWARE REQUIREMENTS; STAKEHOLDER GROUPS;

INFORMATION TECHNOLOGY;

EID: 77953478255     PISSN: 09639314     EISSN: 15731367     Source Type: Journal    
DOI: 10.1007/s11219-010-9098-3     Document Type: Article

References (33)

1. Arthur, I. J. (1985). Measuring programmer productivity and software quality. New York: Wiley.
2. Avižienis, A., Laprie, J.-C., et al. (2001). Fundamental concepts of computer system dependability. IARP/IEEE-RAS workshop on robot dependability: Technological challenge of dependable robots in human environments, Seoul, Korea, May 21-22, 2001.
3. Balla, K., Bemelmans, T., et al. (2001). Quality through managed improvement and measurement (QMIM): Towards a phased development and implementation of a quality management system for a software company. Software Quality Journal, 9(3), 177-193.
4. Blalock, H. (1972). Social statistics. McGraw-Hill: New York.
5. Boehm, B. W., Brown, J. R., et al. (1976). Quantitative evaluation of software quality: 2nd International conference on software engineering, IEEE. 1976. New York, NY, USA, pp. 592-605.
6. Boehm, B. W., Brown, J. R., et al. (1978). Characteristics of software quality. North-Holland, 1978: xxxix+158.
7. Boehm, B., & In, H. (1996). Identifying quality-requirement conflicts. IEEE Software, 13(2), 25-35.
8. Cegielski, C. G., Reithel, B. J., et al. (2005). Emerging information technologies: Developing a timely IT strategy, a model for quickly sifting through emerging technologies to find the best organizational fit. Communications of the ACM, 48(8).
9. Cerpa, N., & Verner, J. M. (1996). Practitioners' views of software quality. The International Journal of Computing and Engineering Management, 4(3), 1-15.
10. Chung, L., & Nixon, B. A. (1995). Dealing with non-functional requirements: three experimental studies of a process-oriented approach: 17th International conference on software engineering, New York, NY, USA.
11. Chung, L., Nixon, B. A., et al. (1999). Non-functional requirements in software engineering. Boston: Kluwer Academic Publishers.
12. Dekkers, N. (2001). Maximising customer satisfaction, April 2-4th, 2001: Proceedings of the 12th European software control and metrics conference, London.
13. Deming, W. E. (1988). Out of the crisis: Quality, productivity and competitive position. Cambridge: Cambridge University Press.
14. Deutsch, M. S., & Willis, R. R. (1988). Software quality engineering-a total technical and management approach. Englewood Cliffs: Engineering Prentice-Hall.
15. Dromey, R. G. (1995). A model for software product quality. IEEE Transactions on Software Engineering, 21(2), 146-163.
16. Gentleman, W. M. (1996). Software quality world-wide: What are the practices in a changing environment: Proceeding of the sixth international conference on software quality (6ICSQ), Ottawa, Canada.
17. Gibbons, J. D. (1993). Nonparametric statistics: An introduction. Newbury Park: Sage Publications.
18. Gillies, A. (1997). Software quality theory and management. London: International Thomson Computer Press.
19. Glass, R. L. (1992). Building Quality Software, Prentice Hall.
20. Haigh, M. (2002). Software quality revisited: Diverging priorities between stakeholder groups? CIST. Philadelphia: Drexel University.
21. Haigh, M., & Verner, J. (2005). Examining stakeholder priorities for software quality attribute requirements: Proceedings of the international workshop on requirements engineering for business need and IT alignment, Sorbone, Paris. Sydney: UNSW Press.
22. Jeffery, M., & Leliveld, I. (2004). Best practices in IT portfolio management. MIT Sloan Management Review, 45(3), 41-49.
23. Kusters, R. J., Trienekens, J. J. M. et al. (2002). On the business impact of software process improvement: Proceedings 26th annual international computer software and applications, Los Alamitos, CA, USA. IEEE Comput. Soc.
24. Luftman, J., & Brier, T. (1999). Achieving and sustaining business-IT alignment. California Management Review, 42(1), 109-122.
25. McCall, J. A., Richards, P. K., et al. (1977). Factors in software quality. Nat'l Tech. Information Service 1.
26. McConnell, S. (1993). Code complete: A practical handbook of software construction. Redmond, WA: Microsoft Press.
27. Perry, W. E. (1991). Quality assurance for information systems: Methods, tools and techniques. QED Technical Publishing Group.
28. Putnam, L. H., & Myers, W. (1992). Measures for excellence-reliable software on time, within budget. USA: Prentice-Hall.
29. Russell, R. H. (2003). The state of IT and business alignment-2003. Balanced scorecard report: Insight, experience & ideas for strategy-focused organizations, Harvard Business School: 3.
30. Shumskas, A. F. (1992). Software risk mitigation. total quality management for software (pp. 190-220). New York: G. G. a. J. I. M. Schulmeyer, van Nostrand Reinhold.
31. The Standish Group Report (2004). 2004 CHAOS research report.
32. Trice, H. M. (1993). Occupational subcultures in the workplace. Ithaca: ILR Press.
33. Trienekens, J. J. M., Kusters, R., et al. (2009). Entropy based software processes improvement. Software Quality Journal, 17(3), 231-243.