1 / 25

An Approach to Measure Java Code Quality in Reuse Environment

An Approach to Measure Java Code Quality in Reuse Environment. Aline Timóteo Advisor: Silvio Meira UFPE – Federal University of Pernambuco alt.timoteo@gmail.com. Summary. Motivation Background Metrics An Approach to Measure Java Code Quality Main Contributions. Motivation. Motivation.

rosa
Télécharger la présentation

An Approach to Measure Java Code Quality in Reuse Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An Approach to Measure Java Code Quality in Reuse Environment AlineTimóteo Advisor: SilvioMeira UFPE – Federal University of Pernambuco alt.timoteo@gmail.com http://www.rise.com.br

  2. Summary • Motivation • Background • Metrics • An Approach to Measure Java Code Quality • Main Contributions http://www.rise.com.br

  3. Motivation http://www.rise.com.br

  4. Motivation • Reuse environment [Frakes, 1994] • Process • Components Certification • Metrics • Tools • Repository • Search engine • Domain tools • … http://www.rise.com.br

  5. Motivation • Component Repository promote reuse success [Griss, 1994] • Some Repository Requirements • Search • Component publishing • Component manage • IDE Integration • Component Indexing • Security • … http://www.rise.com.br

  6. Problem • Artifacts quality must be assured by the organization that maintains a repository? [Seacord, 1999] • Many version of a component on the repository • Lack of context • In other words… How to minimize reuse for low-quality artifacts ? http://www.rise.com.br

  7. Background http://www.rise.com.br

  8. Metrics • “Software metrics is a method to quantify attributes in software processes, products and projects” [Daskalantonakis, 1992] • Metrics Timeline • Age 1: before 1991, where the main focus was on metrics based on the code complexity • Age 2: after 1992, where the main focus was on metrics based on the concepts of Object Oriented (OO) systems http://www.rise.com.br

  9. Age 2: Object Oriented Age 1: Complexity http://www.rise.com.br

  10. Most Referenced Metrics • LOC • Cyclomatic Complexity [McCabe, 1976] • Chidamber and Kemerer Metrics [Chidamber, 1994] • Lorenz and Kidd Metrics [Lorenz, 1994] • MOOD Metrics [Brito, 1994] http://www.rise.com.br

  11. Problems related to Metrics [Ince, 1988 and Briand, 2002] • Metrics Validation • Theoretical Validation • Measurement goal • Experimental hypothesis • Environment or context • Empirical validation • Metrics Automation • Different set of metrics implemented • Bad documentation • Quality attributes x Metrics http://www.rise.com.br

  12. An Approach to Measure Java Code Quality http://www.rise.com.br

  13. An Approach to Measure Java Code Quality • Quality Attributes x Metrics • Metrics Selection and Specification • Quality Attributes measurement http://www.rise.com.br

  14. Quality in a Reuse Environment [Etzkorn, 2001] • ISO 9126 http://www.rise.com.br

  15. Quality Attributes x Metrics http://www.rise.com.br

  16. Quality Attributes x Metrics http://www.rise.com.br

  17. Quality Attributes x Metrics http://www.rise.com.br

  18. Metrics Selection and Specification • - Tools • - Theoretical Validation • - LOC • - Cyclomatic Complexity • - CK Metrics • - Empirical Validation http://www.rise.com.br

  19. Metrics Selection and Specification http://www.rise.com.br

  20. Quality Attributes Measurement (QAM) • QAM = (the number of metrics that have a allowable value) • Heuristically • QAM >= Number of metrics /2 • Example: • 2,5 <= QAM <= 5 Max Testability = 5 Min Testability = 2,5 http://www.rise.com.br

  21. Metrics, Quality, Reuse? • Store assets • Generate their quality attributes • Store asset and quality attributes • In “search time”… • Asset are recovered according search parameters • Quality attributes can be among these parameters

  22. Main Contributions • Introduce quality analysis in a repository • Reduce code problem propagation • Highest Reliability • Quality attributes x Code metrics • ISO 9126 http://www.rise.com.br

  23. Current Stage • Sate-of-the-art in Software Metrics • Approach definition • Prototypal Implementation (partial) • Integration with B.A.R.T. (next step) • Experiment (next step) http://www.rise.com.br

  24. Referências • [Frakes, 1994] W. B. Frakes and S. Isoda, "Success Factors of Systematic Software Reuse," IEEE Software, vol. 11, pp. 14--19, 1994. • [Griss, 1994] M. L. Griss, "Software Reuse Experience at Hewlett-Packard," presented at 16th International Conference on Software Engineering (ICSE), Sorrento, Italy, 1994. • [Garcia, 2006] V. C. Garcia, D. Lucrédio, F. A. Durão, E. C. R. Santos, E. S. Almeida, R. P. M. Fortes, and S. R. L. Meira, "From Specification to Experimentation: A Software Component Search Engine Architecture," presented at The 9th International Symposium on Component-Based Software Engineering (CBSE 2006), Mälardalen University, Västerås, Sweden, 2006. • [Etzkorn, 2001] Letha H. Etzkorn, William E. Hughes Jr., Carl G. Davis: Automated reusability quality analysis of OO legacy software. Information & Software Technology 43(5): 295-308 (2001) • [Daskalantonakis, 1992] M. K. Daskalantonakis, “A Pratical View of Software Measurement and Implementation Experiences Within Motorola”, IEEE Transactions on Software Engineering, vol 18, 1992, pp. 998–1010. • [McCabe, 1976] T. J. McCabe, “A Complexity Measure”. IEEE Transactions of Software Engineering, vol SE-2, 1976, pp. 308-320. • [Chidamber, 1994] S. R. Chidamber, C. F. Kemerer, “A Metrics Suite for Object Oriented Design”, IEEE Transactions on Software Engineering, vol 20, Piscataway - USA, 1994, pp. 476-493. • [Lorenz, 1994] M. Lorenz, J. Kidd, “Object-Oriented Software Metrics: A Practical Guide”, Englewood Cliffs, New Jersey - USA, 1994. • [Brito, 1994] A. F. Brito, R. Carapuça, "Object-Oriented Software Engineering: Measuring and controlling the development process", 4th Interntional Conference on Software Quality, USA, 1994. • [Ince, 1988] D. C. Ince, M. J. Sheppard, "System design metrics: a review and perspective", Second IEE/BCS Conference, Liverpool - UK, 1988, pp. 23-27. • [Briand, 2002] L. C. Briand, S. Morasca, V. R. Basili, “An Operational Process for Goal-Driven Definition of Measures”, Software Engineering - IEEE Transactions, vol 28, 2002, pp. 1106-1125. • [Morasca, 1989] S. Morasca, L. C. Briand, V. R. Basili, E. J. Weyuker, M. V. Zelkowitz, B. Kitchenham, S. Lawrence Pfleeger, N. Fenton, "Towards a framework for software measurementvalidation", Software Engineering, IEEE Transactions, vol 23, 1995, pp. 187-189. • [Seacord, 1999] Robert C. Seacord. Software engineering component repositories. Technical report, Software Engineering Institute (SEI), 1999 http://www.rise.com.br

  25. Aline Timóteo UFPE – Federal University of Pernambuco alt.timoteo@gmail.com http://www.rise.com.br

More Related