next up previous
Next: Efferent Coupling ( ) Up: Coupling Previous: Change Dependency Between Classes


Change Dependency Of Classes ($ CDOC$ )

Works with all instances of a common meta-model, regardless of whether they were produced with the Java or the UML front-end. The respective extends (Java) or generalization (UML) relations expressing the inheritance between two classes are mapped onto relations of type inheritance in the common meta-model (and the $ CDOC$specific view).
Handle
$ CDOC$
Description
The Change Dependency Of Classes ($ CDOC$) measures the class level coupling. It is a measure assigned to classes describing how dependent other classes (client classes) are on this class (server class). This allows conclusions on the follow-up work to be done in all client class, when the server class is changed in the course of re-engineering. It is a accumulation of the $ CDBC$metric, for a server class ($ SC$) and all its client classes ($ CC$).
Scope
Class
View
$ {V}^{CDOC} = ({G}^{CDOC}, {R}^{CDOC})$
  • Grammar $ {G}^{CDOC} = (\{\textrm{class}^{CDOC}\}, \emptyset, \textrm{class}^{CDOC})$
  • Relations $ {R}^{CDOC} = \{\emptyset\}$
  • Mapping $ \alpha^{CDOC}$:
    $\displaystyle \alpha^{CDOC}(\textrm{Class})$ $\displaystyle \mapsto$ $\displaystyle \textrm{class}^{CDOC}$  

Definition
The $ CDOC$value of a class $ c \in class^{CDOC}$is defined as:
$\displaystyle CDOC(c)$ $\displaystyle =$ $\displaystyle \sum_{s \in class^{CDOC} \backslash c }{CDBC(s,c)}$  

Scale
Absolute.
Domain
Integers in $ 0..\infty$, 0 means there is no change dependency between the class to any other class in the system.
Highly Related Software Quality Properties
 
Re-Usability 2.4
is negatively influenced by coupling.
Understandability for Reuse 2.4.1:
Parts having a high (outgoing) efferent coupling may be highly inversely related to understandability, since they are using other parts of the system which need to be understood as well.

Understandability decreases with increasing CDOC.

Attractiveness 2.4.4:
Parts that have a high (outgoing) efferent coupling may be highly inversely related to attractiveness, since they are using other parts of the system which need to be understood as well, and represent dependencies.

Attractiveness decreases with increasing CDOC.

Maintainability 2.6
decreases with increasing CDOC.
Analyzability 2.6.1:
Parts that have a high (outgoing) efferent coupling may be highly inversely related to analyzability, since they are using other parts of the system which need to be analyzed as well.

Analyzability decreases with increasing CDOC.

Changeability 2.6.2:
Parts that have a high (outgoing) efferent coupling may be inversely related to changeability, since they are using other parts of the system which might need to be changed as well.

Changeability decreases with increasing CDOC.

Stability 2.6.3:
Parts showing a high (outgoing) efferent coupling may be inversely related to stability, since they are using other parts of the system, which are can affect them.

Stability decreases with increasing CDOC.

Testability 2.6.4:
Parts that have a high (outgoing) efferent coupling may be highly inversely related to testability, since they are using other parts of the system which increase the number of possible test paths.

Testability decreases with increasing CDOC.

Portability 2.7
decreases with increasing CDOC.
Adaptability 2.7.1:
Parts that have a high (outgoing) efferent coupling may be inversely related to adaptability, since they are using other parts of the system that might need to be adapted as well.

Adaptability decreases with increasing CDOC.

Related Software Quality Properties
 
Functionality 2.1
is both negatively and positively influenced by coupling.
Interoperability 2.1.3:
Parts that have a high (outgoing) efferent coupling may be directly related to interoperability, since they are using/interacting with other parts of the system.

Interoperability might increase with increasing CDOC.

Security 2.1.4:
Parts that have a high (outgoing) efferent coupling may be inversely related to security, since they can be affected by security problems in other parts of the system.

Security might decrease with increasing CDOC.

Reliability 2.2
might decrease with increasing CDOC.
Fault-tolerance 2.2.2:
Parts that have a high (outgoing) efferent coupling may be inversely related to fault-tolerance, since they can be affected by faults in other parts of the system.

Fault-Tolerance might decrease with increasing CDOC.

Recoverability 2.2.3:
Parts that have a high (outgoing) efferent coupling may be inversely related to recoverability, since their data is distributed in other parts of the system making their recovery difficult.

Recoverability might decrease with increasing CDOC.

Re-Usability 2.4
might decrease with increasing CDOC.
Learnability for Reuse 2.4.2:
Parts that have a high (outgoing) efferent coupling may be inversely related to learnability, since they are using other parts of the system which need to be understood as well.

Learnability might decrease with increasing CDOC.

Operability for Reuse - Programmability 2.4.3:
Parts that have a high (outgoing) efferent coupling may be inversely related to learnability, since they are using other parts of the system, which represent dependencies.

Programmability might decrease with increasing CDOC.

Efficiency 2.5
might decrease with increasing CDOC.
Time Behavior 2.5.1:
Parts that have a high (outgoing) efferent coupling may be inversely related to time behavior, since they are using other parts of the system, thus execution during test or operation does not stay local, but might involve huge parts of the system.

Time behavior might get worse with increasing CDOC.

Resource Utilization 2.5.2:
Parts that have a high (outgoing) efferent coupling may be inversely related to resource utilization, since they are using other parts of the system, thus execution during test or operation does not stay local, but might involve huge parts of the system.

Resource utilization might get worse with increasing CDOC.

References
 
  • CDOC is implemented in the VizzAnalyzer Metrics Suite.
Since
Compendium 1.0

next up previous
Next: Efferent Coupling ( ) Up: Coupling Previous: Change Dependency Between Classes
Copyright © 2008-2009, ARiSA AB. Phone: +46-(0)470 70 8495 Email: info@arisa.se Valid CSS! Valid XHTML 1.0 Transitional