This document presents six metrics for object-oriented design proposed by Chidamber and Kemerer: Weighted Methods per Class, Depth of Inheritance Tree, Number of Children, Coupling Between Object Classes, Response for a Class, and Lack of Cohesion in Methods. It provides definitions and examples of calculating each metric. The metrics are based on measurement theory and aim to evaluate OO designs from the perspective of software developers. Further research is needed to better understand how OO designs may differ from traditional approaches in desired design features.

1. A Metric Suite for Object Oriented DesignShyam R. Chidamber and Chris F. KemererAri WibisonoBambangAdhiAchmadRohman

2. Outline

3. Contribution

4. Research Probelms

5. Theoritical Criticism

6. OO design and development.

7. Objective

8. Theory Base for OO Metrics

9. Measurement Theory Base

10. Empirical Data Collection

11. Software Dev Organization

12. Results

13. Metric 1 : Weighted Method Per Class

14. Character Graphics

15. Matrix 1 : Weight Method per ClassCase Study : Character GraphicsNumber of Class Observed : 8Number of Method Observed : 59

16. How TO ObserveD

17. Cyclomatic complexity

18. Weight Method per Class (Statistics)

19. Weight Method per Class (Character Graphics)

20. WMC ResultCyclomatic ComplexityTestabilityUnderstandability(SATC 1995)

21. Matrix 3 : Depth of Inheritance TreeDIT is the maximum length from a node to the root (base class)Viewpoints:Lower level subclasses inherit a number of methods making behavior harder to predictDeeper trees indicate greater design complexity

22. Matrix 2 : Depth of inheritance Tree

23. Matrix 2 : Depth of inheritance Tree

24. Matrix 3 : Number of ChildrenNOC is the number of subclasses immediately subordinate to a class

25. Viewpoints:

26. As NOC grows, reuse increases - but the abstraction may be diluted

27. Depth is generally better than breadth in class hierarchy, since it promotes reuse of methods through inheritance

28. Classes higher up in the hierarchy should have more sub-classes then those lower down

29. NOC gives an idea of the potential influence a class has on the design: classes with large number of children may require more testingMatrix 3 : Number of Children

30. Matrix 4 : Class between objectsCBO is the number of collaborations between two classes (fan-out of a class C)

31. the number of other classes that are referenced in the class C (a reference to another class, A, is an reference to a method or a data member of class A)

32. Viewpoints:

33. As collaboration increases reuse decreases

34. High fan-outs represent class coupling to other classes/objects and thus are undesirable

35. High fan-ins represent good object designs and high level of reuse

36. Not possible to maintain high fan-in and low fan outs across the entire system Matrix 4 : Class between objects

37. Matrix 4 : Class between objects

38. Metric 5: Response For a Class (RFC)

39. Metric 5: Response For a Class (RFC)Jikasebuah class terdiriatasbanyak method, besarkemungkinankompleksitasdari class semakintinggi

40. Dan jikabanyak method dapatdipanggiluntukmeresponspesan yang diterimaolehsebuahobyekdarisuatu class besarkemungkinanpemeliharaandan testing menjadilebihkompleks.

41. Responsuntukmetriks class bertujuanuntukmengukurbanyaknya method lokaldanbanyaknya method yang dipanggiloleh method lokal

42. Tidakterdapatnilai threshold spesifikpadametriks RFC. NamunChidamber and Kemerermenyarankansemakinbesarnilai RFC, semakinbesar level pemahaman yang diperlukansebagaibagiandari testerMetric 5: Response For a Class (RFC)Definisi

43. RFC = |RS| dimana RS adalah himpunan respons untuk class yang diberikan

44. RS = {M} Uall i {Ri}

45. dimana {Ri} = himpunan method-method yang dipanggil oleh method i dan