ACM Home Page
Please provide us with feedback. Feedback
Predictors of customer perceived software quality
Full text PdfPdf (107 KB)
Source International Conference on Software Engineering archive
Proceedings of the 27th international conference on Software engineering table of contents
St. Louis, MO, USA
SESSION: Software quality and process table of contents
Pages: 225 - 233  
Year of Publication: 2005
ISBN:1-59593-963-2
Authors
Audris Mockus  Avaya Research, Basking Ridge, NJ
Ping Zhang  Avaya Research, Basking Ridge, NJ
Paul Luo Li  Carnegie Mellon University, Pittsburgh, PA
Sponsors
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 43,   Downloads (12 Months): 177,   Citation Count: 14
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1062455.1062506
What is a DOI?

ABSTRACT

Predicting software quality as perceived by a customer may allow an organization to adjust deployment to meet the quality expectations of its customers, to allocate the appropriate amount of maintenance resources, and to direct quality improvement efforts to maximize the return on investment. However, customer perceived quality may be affected not simply by the software content and the development process, but also by a number of other factors including deployment issues, amount of usage, software platform, and hardware configurations. We predict customer perceived quality as measured by various service interactions, including software defect reports, requests for assistance, and field technician dispatches using the afore mentioned and other factors for a large telecommunications software system. We employ the non-intrusive data gathering technique of using existing data captured in automated project monitoring and tracking systems as well as customer support and tracking systems. We find that the effects of deployment schedule, hardware configurations, and software platform can increase the probability of observing a software failure by more than 20 times. Furthermore, we find that the factors affect all quality measures in a similar fashion. Our approach can be applied at other organizations, and we suggest methods to independently validate and replicate our results.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
N. Breslow. Statistics in epidemiology: the case control study. JASA, 91(433):14--28, 1996.
 
3
 
4
 
5
S. Chulani. Coqualmo (constructive quality model) a software defect density prediction model. Project Control for Software Quality, 1999.
 
6
S. Chulani, P.Santhanam, D. Moore, and G. Davidson. Deriving a software quality view from customer satisfaction and service data. European Conference on Metrics and Measurement, 2001.
 
7
S. R. Dalal and C. L. Mallows. When should one stop testing software? Journal of American Statist. Assoc, 83:872--879, 1988.
 
8
 
9
 
10
P. L. Li, M. Shaw, K. Stolarick, and K. Wallnau. The potential for synergy between certification and insurance. International Workshop on Reuse Economics in conjunction with ICSR7, April 2002.
 
11
M. R. Lyu. Handbook of Software Reliability Engineering. IEEE Society Press, Los Alamitos, CA, 1996.
 
12
A. Mockus and D. M. Weiss. Predicting risk of software changes. Bell Labs Technical Journal, 5(2):169--180, April-June 2000.
 
13
 
14
 
15
 
16
S. Weisberg. Applied Linear Regression, 2nd Edition. John Wiley & Sons, USA, 1985.
 
17
 
18
P. Zhang, J. Landwehr, and M. Serban. Quantifying the value of remote maintenance: An analysis of customer outage data, 2004.

CITED BY  14

Collaborative Colleagues:
Audris Mockus: colleagues
Ping Zhang: colleagues
Paul Luo Li: colleagues