Data Abstraction Coupling ($DAC$ )

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 $DAC$specific view).

Handle

$DAC$

Description

The DAC measures the coupling complexity caused by Abstract Data Types (ADTs). This metric is concerned with the coupling between classes representing a major aspect of the object oriented design, since the reuse degree, the maintenance and testing effort for a class are decisively influenced by the coupling level between classes. Basically same as $DAC$, but coupling limited to type references.

Scope

Class

View

${V}^{DAC} = ({G}^{DAC}, {R}^{DAC})$

• Grammar ${G}^{DAC} = (\{\textrm{class}^{DAC}\}, \emptyset, \textrm{class}^{DAC})$
• Relations ${R}^{DAC}: \{\textrm{referencestype}^{DAC} : \textrm{class}^{DAC} \times \textrm{class}^{DAC}\}$
• Mapping $\alpha^{DAC}$:
  

  $$\alpha^{DAC}(\textrm{Class}) \mapsto \textrm{class}^{DAC}$$

  $$\alpha^{DAC}(\textrm{IsOfType}) \mapsto \textrm{referencestype}^{DAC}$$

  
  

Definition

The $DAC$value of a class $c \in class^{DAC}$is defined as:

$$DAC(c) = \left\vert succ(c, \textrm{referencestype}^{DAC}) \backslash c \right\vert$$

Scale

Absolute.

Domain

Integers $\in 0..\infty$.

Highly Related Software Quality Properties

 

Re-Usability 2.4

is negatively influenced by coupling.

Understandability for Reuse 2.4.1:

A part of a system that has a high (outgoing) efferent coupling may be highly inversely related to understandability, since it is uses other parts of the system which need to be understood as well.

Understandability decreases with increasing DAC.

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 DAC.

Maintainability 2.6

decreases with increasing DAC.

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 DAC.

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 DAC.

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 DAC.

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 DAC.

Portability 2.7

decreases with increasing DAC.

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 which might need to be adapted as well.

Adaptability decreases with increasing DAC.

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 DAC.

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 DAC.

Reliability 2.2

might decrease with increasing DAC.

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 DAC.

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 DAC.

Re-Usability 2.4

might decrease with increasing DAC.

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 DAC.

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 DAC.

Efficiency 2.5

might decrease with increasing DAC.

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 DAC.

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 DAC.

References

 

• DAC is extensively discussed and validated in [14,2,4,11,19],
• it is implemented in the VizzAnalyzer Metrics Suite.

Since

Compendium 1.0

Copyright © 2008-2009, ARiSA AB. Phone: +46-(0)470 70 8495 Email: info@arisa.se