CEN 4010 EXAM 2 WITH ALL CORRECT & 100%
VERIFIED ANSWERS
Six Design Principles ✔Correct answer-
Stamp coupling ✔Correct answer-complex data structures are passed between modules
Data coupling ✔Correct answer-only data values not structured data are passed.
List the coupling types from most tight to low coupling ✔Correct answer-Content->common-
>contorl->Stamp->Data->uncoupled
Cohesion ✔Correct answer-the dependence within and among a module's internal elements.
Coincidental ✔Correct answer-worst degree of cohesion. Parts are unrelated to one another.
Logical ✔Correct answer-Parts are related only by logic strucuture of code
Temporal ✔Correct answer-module's data and functions are related because they are used at the
time in an exectution
procedural ✔Correct answer-similar to temporal and functions pertain to some related action or
purpose
communication ✔Correct answer-operates on same data set
functional ✔Correct answer-ideal degree-all elements essential to a single function are contained
in one module and all the elements are essential to the performance of the function
Informational ✔Correct answer-adaption of functional cohesion to data cohesion
Interface ✔Correct answer-defines what services the software unit provide to the rest of the
system and how other units can access thsoe services.
Information hiding ✔Correct answer-results in software units that are loosley coupled
Fan In ✔Correct answer-refers to the number of units that use a particular software unit (not a bad
thing)parallelization
Fan-out ✔Correct answer-refers to the number of unit used by a particular software unit.(can be a
bad thing)
Sandwiching ✔Correct answer-break a cycle in the uses graph. break mutual dependencies in
tightly coupled unit or long dependency chains
polymorphism ✔Correct answer-inheritance
generic types
method overloads(Vehicles->cars0<trucks)
Interfaces
VERIFIED ANSWERS
Six Design Principles ✔Correct answer-
Stamp coupling ✔Correct answer-complex data structures are passed between modules
Data coupling ✔Correct answer-only data values not structured data are passed.
List the coupling types from most tight to low coupling ✔Correct answer-Content->common-
>contorl->Stamp->Data->uncoupled
Cohesion ✔Correct answer-the dependence within and among a module's internal elements.
Coincidental ✔Correct answer-worst degree of cohesion. Parts are unrelated to one another.
Logical ✔Correct answer-Parts are related only by logic strucuture of code
Temporal ✔Correct answer-module's data and functions are related because they are used at the
time in an exectution
procedural ✔Correct answer-similar to temporal and functions pertain to some related action or
purpose
communication ✔Correct answer-operates on same data set
functional ✔Correct answer-ideal degree-all elements essential to a single function are contained
in one module and all the elements are essential to the performance of the function
Informational ✔Correct answer-adaption of functional cohesion to data cohesion
Interface ✔Correct answer-defines what services the software unit provide to the rest of the
system and how other units can access thsoe services.
Information hiding ✔Correct answer-results in software units that are loosley coupled
Fan In ✔Correct answer-refers to the number of units that use a particular software unit (not a bad
thing)parallelization
Fan-out ✔Correct answer-refers to the number of unit used by a particular software unit.(can be a
bad thing)
Sandwiching ✔Correct answer-break a cycle in the uses graph. break mutual dependencies in
tightly coupled unit or long dependency chains
polymorphism ✔Correct answer-inheritance
generic types
method overloads(Vehicles->cars0<trucks)
Interfaces
