The Community for Technology Leaders
RSS Icon
Issue No.01 - January (1996 vol.13)
pp: 25-32
Discussions of software quality typically focus on the development process or the characteristics of the software product. The third level of quality - the outcome of software development - is usually neglected, although this is perhaps of greatest interest to business management. Outcome depends on how the product is used and determines the business value obtained from the development project. I conducted a study that investigated how a number of Australian organizations make their IT investment decisions. My research focused on how organizations evaluated individual projects, both at the justification stage and after implementation. I also examined how "effectiveness" was interpreted (that is, what was considered to be good business), the extent to which nonfinancial benefits influenced investment decisions, and the type of measures that were considered useful. From this work I developed a comprehensive framework of benefits and measures, and I validated the framework using the actual justifications of 25 projects. Thus, the framework provides a useful model for the analysis and measurement of the multiple dimensions of value that IT can bring to a business.
Pamela Simmons, "Quality Outcomes: Determining Business Value", IEEE Software, vol.13, no. 1, pp. 25-32, January 1996, doi:10.1109/52.476283
49 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool