Hierarchical model for evaluating software design quality

• Autorzy: Martenka P. , Walter B.
• Języki publikacji: EN

Abstrakty

EN

Quality of software design has a decisive impact on several quality attributes of the resulting product. However, simple metrics, despite of their popularity, fail to deliver comprehensive information about the reasons of the anomalies and relation between them and metric values. More complex models that combine multiple metrics to detect a given anomaly are still only partially useful without proper interpretation. In the paper we propose a hierarchical model that extend the Factor-Strategy model defined by Marinescu in two ways: by embedding a new interpretation delivery mechanism into the model and extending the spectrum of data providing input to the model.

Słowa kluczowe

EN

hierarchical model; Factor-Strategy Model; Detection Strategy (DS)

• Wydawca: Oficyna Wydawnicza Politechniki Wrocławskiej
• Czasopismo: e-Informatica Software Engineering Journal
• Rocznik: 2010
• Tom: Vol. 4, nr 1
• Strony: 21--30
• Opis fizyczny: Bibliogr. 23 poz.

Twórcy

autor

Martenka P.

autor

Walter B.

• Institute of Computing Science, Poznan University of Technology

Bibliografia

• [1] I. D. Baxter, A. Yahin, L. Moura, M. Sant’Anna,and L. Bier. Clone detection using abstract syntax trees. In ICSM ’98: Proceedings of the International Conference on Software Maintenance,page 368, Washington, DC, USA, 1998. IEEE Computer Society.
• [2] L. C. Briand, J. W. Daly, and J. K. W¨ust.A unified framework for cohesion measurement in object-oriented systems. Empirical Software Engineering, 3(1):65–117, 1998.
• [3] L. C. Briand, J. W. Daly, and J. K. W¨ust. A unified framework for coupling measurement in object-oriented systems. IEEE Transactions on Software Engineering, 25:1, 1999.
• [4] L. C. Briand, W. L. Melo, and J. W¨ust. Assessing the applicability of fault-proneness models across object-oriented software projects. Technical report, ISERN, 2000.
• [5] L. C. Briand, S. Morasca, and V. R. Basili. Property-based software engineering measurement.IEEE Transactions on Software Engineering,22:68–86, 1994.
• [6] S. R. Chidamber and C. F. Kemerer. A metrics suite for object oriented design. IEEE Transactions on Software Engineering, 20(6):476–493,1994.
• [7] P. Coad and E. Yourdon. Object Oriented Design.Prentice Hall, 1991.
• [8] K. Dhambri, H. A. Sahraoui, and P. Poulin.Visual detection of design anomalies. In 12th European Conference on Software Maintenance and Reengineering 2008, pages 279–283, April 2008.
• [9] F. B. e Abreu and R. Carapu¸ca. Object-oriented software engineering: Measuring and controlling the development process. In Proceedings of the 4th International Conference on Software Quality,1994.
• [10] K. E. Emam. Advances in Software Engineering, chapter Object-Oriented Metrics: A Review of Theory and Practice, pages 23–50. 2002.
• [11] M. Fowler. Refactoring. Improving the Design of Existing Code. Addison-Wesley, 1999.
• [12] M. Fowler, K. Beck, J. Brant, W. Opdyke, and D. Roberts. Refactoring: Improving the Design of Existing Code. Addison-Wesley, 1999.
• [13] R. Glass. On design. Journal of Systems and Software, 52(1):1–2, May 2000.
• [14] T. L. Graves, A. F. Karr, J. Marron, and H. Siy.Predicting fault incidence using software change history. IEEE Transactions on Software Engineering,26:653–661, 2000.
• [15] T. M. Khoshgoftaar, E. B. Allen, R. Halstead,G. P. Trio, and R. M. Flass. Using process history to predict software quality. Computer,31:66–72, 1998.
• [16] S. C. Kothari, L. Bishop, J. Sauceda, and G. Daugherty. A pattern-based framework for 30 Paweł Martenka, Bartosz Walter software anomaly detection. Software Quality Control, 12(2):99–120, 2004.
• [17] R. Marinescu. Measurement and Quality in Object-Oriented Design. PhD thesis, “Politehnica” University of Timi¸soara, 2002.
• [18] R. Martin. OO design quality metrics. An analysis of dependencies. Report on Object Analysis and Design, 2(3), 1995.
• [19] G. Miller. The magical number seven, plus or minus two: Some limits on our capacity for processing information. The Psychological Review, (63):81–97, 1956.
• [20] D. Ratiu, S. Ducasse, T. Grba, and R. Marinescu.Using history information to improve design flaws detection, 2004.
• [21] F. Simon, F. Steinbr¨uckner, and C. Lewerentz. Metrics based refactoring. In Proceedings of the 5th European Conference on Software Maintenance and Reengineering, pages 30–38, 2001.
• [22] E. van Emden and L. Moonen. Java quality assurance by detecting code smells. In Proceedings of the 9th Working Conference on Reverse Engineering, 2002.
• [23] B. Walter and B. Pietrzak. Multi-criteria detection of bad smells in code with UTA method. In Proceedings of XP 2005 conference, pages 154–161, 2005.