Low Coupling: Single Responsibility Principle vs Cohesion
I’ve read several articles on SRP and cohesion, and they seem to contradict each other as far as low coupling is concerned.
What’s the opposite of cohesive?
I was talking with my architect about some concerns with a particular approach that may result in very low level of cohesion in a set of classes. However, I couldn’t think of the word that represents a low level of cohesion.
Programming by Intention, Depth-First or Breadth-First?
Say I have the following graph of dependencies between procedures/functions/methods:
Fields vs method arguments [closed]
Closed 10 years ago.
Fields vs method arguments [closed]
Closed 10 years ago.
Fields vs method arguments [closed]
Closed 10 years ago.
Fields vs method arguments [closed]
Closed 10 years ago.
Fields vs method arguments [closed]
Closed 10 years ago.
How do I deal with outdated or old concepts taught from the computer science class?
I’ve been studying “cohesion and couplings” in Software engineering course. The ancient PPT slide the professor gave me defines logical and coincidental cohesion like this.
What is the evidence that an API has exceeded its orthogonality in the context of types?
Wikipedia defines software orthogonality as: