Why is it generally considered good practice to minimize coupling between classes?
A) Low coupling increases the operational efficiency of a program.
B) High coupling implies less interface cohesion.
C) High coupling increases program maintenance and hinders code reuse.
D) Low coupling decreases the probability of code redundancy.
Correct Answer:
Verified
Q1: After you have identified a set of
Q3: You are designing an application to support
Q4: A class (ClassOne) is considered to have
Q5: If many classes of a program depend
Q6: Classes often correspond to _ in a
Q7: In a UML diagram, dependency is denoted
Q8: Which of the following would be an
Q9: A UML class diagram would be most
Q10: What is a general naming convention for
Q11: A/an _ is used to create objects
Unlock this Answer For Free Now!
View this answer and more for free by performing one of the following actions
Scan the QR code to install the App and get 2 free unlocks
Unlock quizzes for free by uploading documents