Question

1. How might coupling and reusability be related? How might cohesion and reusability be related? Explain your answer and provide one example for each.

Answer 1

Coupling forms a measure which defines the level of
inter-dependability among the elements of modules of
software. It represents at which level there is interaction
and interference existing among the modules4
. Lower
the extent of coupling, better will the program and thus
higher will be the reusability. Coupling also exhibits a
supplier relationship and a client server relationship
within the design elements5
.
Intra-modular coupling density (ICD): is a mea-
sure which defines the connection between coupling and
cohesion among the elements of modules in a module
based software system6
.
Import coupling: It gives a measure on the count of
services taken from other modules by a dependent mod-
ule. Import coupling which is denoted by Iv, represents
the value of the extent to which packages is dependent on
other design elements.
Export coupling: It gives a measure of services which
offered to another dependent module by a module. For
the component to be reusable export should be more than
import

Cohesion defines the level of intra-dependability among

elements contained in a module. Greater the cohesion

better will be the program design. Modules which are

highly cohesive are considered to be highly reusable.

Higher cohesion enables easier maintenance of a software

system3

.

connections between different methods8

. At the point

when the proposed methodology was exactly assessed it

represented to the upsides of joining the basic and seman-

tic measures alongside the advantages of the proposed

technique and shows it as a component for software

development environment. The paper spoke to different

methodologies identified with class cohesion distinguish

refactoring opportunities utilizing distinctive measure-

ments which decide the structural connections among

the methods in a class.

The complexity, cohesion and coupling to the security

failures of the software when they are in their operational

stage9

. They proposed how CCC metric can be used to

indicate vulnerabilities and thus made this metric to aid

in the conception of the architecture which is even more

secure which further promised a secure, design, code and

eventually a better software.

Presented a static analysis tool to determine the cou-

pling in order to reduce the extent of coupling among

the java classes and make the software highly cohesive10.

This static analysis tool was made to detect the coupling

based on the source code. They discussed coupling in

the software on the basis of object-oriented relationships

between the classes, with a focus on the types of couplings

that are not detected till the implementation is complete

and proposed a tool for static analysis which measured

the couplings among classes in Java packages.

Several metrics that had been proposed in order to

measure how much the class members related .and use of

Connectivity-based class cohesion metrics for measuring

the extent of dependencies within the class members11.

They proposed new metric for class cohesion which has

higher discriminative power than cohesion metrics which

had already existed.

A study to look at relationship amongst contrasts and

appreciation abilities of optional school youngsters who

were made to peruse writings about science subjects of

various levels of attachment12. They watched measures of

learning in the wake of perusing the content with high

and low coupling. The content was characterized by reit-

eration of things and expressions being rehashed.

An intelligent risk analysis model to determine the

reusable modules in a java project13. This model takes a

java project as input and gives its reusable components

as output. All packages, sub packages and classes in those