A Software Quality Predictive Model

Elisabetta Ronchieri, Marco Canaparo

Abstract

Software development is facing the problem of how to improve the quality of software products. The lack of quality can easily lead to major costs and delays in the development and maintenance of the software. Its improvement can be guaranteed by both the definition of a software quality model and the presence of metrics that are designed and measured to plan and monitor productivity, effectiveness, quality and timing of software. Integrating the metrics into the model contributes to collecting the right data for the handling of the analysis process and to establishing a general view to the control of the overall state of the process. This paper aims at introducing a mathematical model that links software best practices with a set of metrics to predict the quality of software at any stage of development. Two software projects have been used to analyze the defined model as a suitable predictive methodology in order to evaluate its results. The model can improve the level of the software development process significantly and contribute to achieving a product of the highest standards. A replication of this work on larger data sets is planned.

References

  1. Aiftimiei, C., Ceccanti, A., Dongiovanni, D., Meglio, A. D., and Giacomini, F. (2012). Improving the quality of emi releases by leveraging the emi testing infrastructure. Journal of Physics: Conference Series, 396(5).
  2. Briand, L. C., Basili, V. R., and Hetmanski, C. J. (1993). Developing interpretable mmodel with optimized set reduction for identifying high-risk software components. IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, 19.
  3. Brooks, F. P. (1995). The mythical man-month. AddisonWesley Boston.
  4. Butler, S. (2012). Mining java class identifier naming conventions. In Software Engineering (ICSE), 2012 34th International Conference, pages 1641-1643.
  5. Chhabra, J. and Gupta, V. (2010). A survey of dynamic software metric. Journal of Computer Science and Technology, 25:1016-1029.
  6. Chidamber, S. R. and Kemerer, C. F. (1994). A metrics suite for object oriented design. Transactions on Software Engineering, 20(6):476-493.
  7. Coleman, D., Ash, D., Lowther, B., and Auman, P. (1994). Using metrics to evaluate software system maintainability. IEEE Computer, 27(8):44-49.
  8. Fang, X. (2001). Using a coding standard to improve program quality. In Quality Software 2001. Proceedings Second Asia-Pacific Conference, pages 73-78.
  9. Fawler, M., Beck, K., Brant, J., Opdyke, W., and Roberts, D. (1999). Refactoring: Improving the Design of Existing Code [Hardcover]. Addison-Wesley Professional.
  10. Fenton, N. (1990). Software metrics: theory, tools and validation. Software Engineering, 5(1):65-78.
  11. Flissi, A., Dubus, J., Dolet, N., and Merle, P. (2008). Deploying on the grid with deployware. In Cluster Computing and the Grid, 2008. CCGRID 7808. 8th IEEE International Symposium, pages 177-184.
  12. GCCTeam (2012). Gcc coding conventions.
  13. Harel, D. and Rumpe, B. (2004). Meaningful modeling: What's the semantics of "semantics"? Computer, 37(10):64-72.
  14. IEEE90 (1990). IEEE Standard Glossary of Software Engineering Terminology, ieee std 610.12-1990, institute of electrical and electronic engineers, inc., new york, ny, edition.
  15. Jansen, S. and Brinkkemper, S. (2006). Evaluating the release, delivery, and deployment processes of eight large product software vendors applying the customer configuration update model. In WISER 7806 Proceedings of the 2006 international workshop on interdisciplinary software engineering research, pages 65-68.
  16. Khoshgoftaar, T. M. and Seliya, N. (2003). Analogy-based practical classification rules for software quality estimation. Empirical Software Engineering Journal, 8(4):325-350.
  17. Kim, S., Zimmermann, T., Jr, E. W., and Zeller, A. (2007). Predicting faults from cached history. pages 489-498. IEEE Computer Society Washington DC, USA.
  18. Kopec, D. and Tumang, S. (2007). Failures in complex systems: case studies, causes, and possible remedies. SIGCSE Bulletin, 39(2):180-184.
  19. Li, X. S. and Prasad, C. (2005). Effectively teaching coding standards in programming. In SIGITE'05, pages 239- 244, Newark, New Jersey, US. ACM New York, NY, USA.
  20. Majchrzak, T. A. (2010). Best practices for technical aspects of software testing in enterprises. In Information Society (i-Society), 2010 International Conference, pages 195-202.
  21. McConnell, S. (1996). Who cares about software construction? IEEE Software, 13(1):127-128.
  22. Mengel, S. A. and Tappan, D. A. (1995). Program design in file structures. In Frontiers in Education Conference, 1995. Proceedings., 1995, pages 4b2.11 - 4b2.16 vol.2.
  23. Merlo, E., Kontogiannis, K., and Girard, J. (1992). Structural and behavioral code representation for program understanding. In Computer-Aided Software Engineering, 1992. Proceedings., Fifth International Workshop, pages 106-108.
  24. Munson, J. C. and Khoshgoftaar, T. M. (1992). The detection of fault-prone programs. IEEE Transactions on Software Engineering, 18(5):423-432.
  25. Oman, P. W. and Cook, C.-P. (1988). A paradigm for programming style research. ACM SINGPLAN Notices, 23(12):69-78.
  26. Pighin, M. and Zamolo, R. (1997). A predictive metric based on discriminant statistical analysis. In The 19th International Conference on Software Engineering, ICSE'97, pages 262-270, Boston, Massachusetts, USA.
  27. Ronchieri, E., Dibenedetto, M., Zappi, R., Aiftimiei, C., Vagnoni, V., and Venturi, V. (2012). T-storm: a storm testing framework. In PoS(EGICF12-EMITC2), number 088, pages 1-11.
  28. Ronchieri, E., Meglio, A. D., Venturi, V., and Muller-Wilm, U. (2009). Guidelines for adopting etics as build and test system.
  29. Rossum, G. V. and Warsaw, B. (2001). Style guide for python code.
  30. Salomoni, D., Italiano, A., and Ronchieri, E. (2011). Wnodes, a tool for integrated grid and cloud access and computing farm virtualization. Journal of Physics: Conference Series, 331(331).
  31. SunMicrosystems (1997). Java code conventions.
  32. Top, S., Nørgaard, H. J., Krogsgaard, B., and Jørgensen, B. N. (2004). The sandwich code file structure - an architectural support for software engineering in simulation based development of embedded control applications. In Press, A., editor, IASTED International Conference on Software Engineering.
  33. Wingerd, L. and Seiwald, C. (1998). High-level best practices in software configuration management. In Eighth International Workshop on Software Configuration Management Brussels.
  34. Zappi, R., Ronchieri, E., Forti, A., and Ghiselli, A. (2011). An Efficient Grid Data Access with StoRM. Lin, Simon C. and Yen, Eirc, Data Driven e-Schience. Springer New York.
Download


Paper Citation


in Harvard Style

Ronchieri E. and Canaparo M. (2013). A Software Quality Predictive Model . In Proceedings of the 8th International Joint Conference on Software Technologies - Volume 1: ICSOFT-EA, (ICSOFT 2013) ISBN 978-989-8565-68-6, pages 186-197. DOI: 10.5220/0004492001860197


in Bibtex Style

@conference{icsoft-ea13,
author={Elisabetta Ronchieri and Marco Canaparo},
title={A Software Quality Predictive Model},
booktitle={Proceedings of the 8th International Joint Conference on Software Technologies - Volume 1: ICSOFT-EA, (ICSOFT 2013)},
year={2013},
pages={186-197},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0004492001860197},
isbn={978-989-8565-68-6},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 8th International Joint Conference on Software Technologies - Volume 1: ICSOFT-EA, (ICSOFT 2013)
TI - A Software Quality Predictive Model
SN - 978-989-8565-68-6
AU - Ronchieri E.
AU - Canaparo M.
PY - 2013
SP - 186
EP - 197
DO - 10.5220/0004492001860197