Object-Oriented Reading Techniques for Inspection of UML Models – An Industrial Experiment

  • Reidar Conradi
  • Parastoo Mohagheghi
  • Tayyaba Arif
  • Lars Christian Hegde
  • Geir Arne Bunde
  • Anders Pedersen
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2743)


Object-oriented design and modeling with UML has become a central part of software development in industry. Software inspections are used to cost-efficiently increase the quality of the developed software by early defect detection and correction. Several models presenting the total system need to be inspected for consistency with each other and with external documents such as requirement specifications. Special Object Oriented Reading Techniques (OORTs) have been developed to help inspectors in the individual reading step of inspection of UML models. The paper describes an experiment performed at Ericsson in Norway to evaluate the cost-efficiency of tailored OORTs in a large-scale software project. The results showed that the OORTs fit well into an incremental development process, and managed to detect defects not found by the existing reading techniques. The study demonstrated the need for further development and empirical assessment of these techniques, and for better integration with industrial work practice.


Unify Modeling Language Class Diagram Sequence Diagram State Diagram Class Description 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Arif, T., Hegde, L.C.: Inspection of Object-Oriented Construction. Diploma (MSc) thesis at NTNU (June 2002), See
  2. 2.
    Basili, V.R., Caldiera, G., Lanubile, F., Shull, F.: Studies on reading techniques. In: Proc. Twenty-First Annual Software Engineering Workshop, NASA-SEL-96-002, Greenbelt, MD, December 1996, pp. 59–65 (1996)Google Scholar
  3. 3.
    Basili, V.R., Green, S., Laitenberger, O., Lanubile, F., Shull, F., Sørumgård, S., Zelkowitz, M.V.: The Empirical Investigation of Perspective-Based Reading. Empirical Software Engineering Journal 1(2), 133–164 (1996)CrossRefGoogle Scholar
  4. 4.
    Booch, G., Rumbaugh, J., Jacobson, I.: The Unified Modeling Language User Guide. Addison-Wesley, Reading (1999)Google Scholar
  5. 5.
    Bunde, G.A., Pedersen, A.: Defect Reduction by Improving Inspection of UML Diagrams in the GPRS Project. Diploma (MSc) thesis at Agder University College (June 2002), See
  6. 6.
    Conradi, R.: Preliminary NTNU Report of the OO Reading Techniques (OORT) exercise in course 7038 on Programming Quality and Process Improvement (Spring 2000), vol. 1.12, p. 80 (October2001)Google Scholar
  7. 7.
    Conradi, R., Marjara, A., Hantho, Ø., Frotveit, T., Skåtevik, B.: A study of inspections and testing at Ericsson, Norway. In: Proc. PROFES 1999, June 22-24, pp. 263–284. VTT (1999)Google Scholar
  8. 8.
    Fagan, M.E.: Design and Code Inspection to Reduce Errors in Program Development. IBM Systems Journal 15(3), 182–211 (1976)CrossRefGoogle Scholar
  9. 9.
    Gilb, T., Graham, D.: Software Inspection. Addison-Wesley, Reading (1993)Google Scholar
  10. 10.
    Jacobson, I., Christerson, M., Jonsson, P., Övergaard, G.: Object-Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley, Reading (1995) (revised printing)Google Scholar
  11. 11.
    Laitenberger, O., Atkinson, C.: Generalized Perspective-Based Inspection to handle Object-Oriented Development Artifacts. In: Proc. ICSE 1999, pp. 494–503. IEEE CS-Press, Los Alamitos (1999)Google Scholar
  12. 12.
    Martin, J., Tsai, W.T.: N-fold Inspection: A Requirements Analysis Technique. Communications of the ACM 33(2), 225–232 (1990)CrossRefGoogle Scholar
  13. 13.
    Melo, W., Shull, F., Travassos, G.H.: Software Review Guidelines, Technical Report ES-556/01, p. 22. Systems Engineering and Computer Science Department, COPPE/UFRJ (shortly reporting OORT case study at Oracle in Brazil) (August 2001),
  14. 14.
    Shull, F., Carver, J., Travassos, G.H.: An Empirical Method for Introducing Software Process. In: Proc. European Software Engineering Conference (ESEC 2001), Vienna, September 10-14, pp. 288–296. ACM/IEEE CS Press (2001) ACM Order no. 594010, ISBN 1-58113-390-1 Google Scholar
  15. 15.
    Sommerville, I.: Software Engineering, 6th edn. Addison-Wesley, Reading (2001)Google Scholar
  16. 16.
    Travassos, G.H., Shull, F., Carver, J., Basili, V.R.: Reading Techniques for OO Design Inspections. In: Proc. Twenty-Forth Annual Software Engineering Workshop, NASA-SEL, Greenbelt, MD (December 1999),
  17. 17.
    Travassos, G.H., Shull, F., Fredericks, M., Basili, V.R.: Detecting Defects in Object-Oriented Designs: Using Reading Techniques to Increase Software Quality. In: Proc. OOPSLA 1999, Denver, November 1-5, ACM SIGPLAN Notices, vol. 34(10), pp. 47–56 (October 1999)Google Scholar
  18. 18.
    Travassos, G.H., Shull, F., Carver, J., Basili, V.R.: Reading Techniques for OO Design Inspections. University of Maryland Technical Report CS-TR-4353 (OORT version 3) (April 2002),
  19. 19.
    Votta, L.G.: Does Every Inspection Need a Meeting? In: Proc. ACM SIGSOFT 1993 Symposium on Foundation of Software Engineering (FSE 1993), pp. 107–114. ACM Press, New York (1993)CrossRefGoogle Scholar
  20. 20.
    Wohlin, C., Runeson, P., Höst, M., Ohlsson, M.C., Regnell, B., Wesslén, A.: Experimentation in Software Engineering, an Introduction. Kluwer Academic Publishers, Dordrecht (2000)zbMATHGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2003

Authors and Affiliations

  • Reidar Conradi
    • 1
  • Parastoo Mohagheghi
    • 2
  • Tayyaba Arif
    • 1
  • Lars Christian Hegde
    • 1
  • Geir Arne Bunde
    • 3
  • Anders Pedersen
    • 3
  1. 1.Department of Computer and Information ScienceNTNUTrondheimNorway
  2. 2.Ericsson Norway - Grimstad, PostuttakGrimstadNorway
  3. 3.Agder University CollegeGrimstadNorway

Personalised recommendations