Tag Archives: Coupling
Multiple Classes with Single responsibility VS Single Class with Multiple Responsibilities
While taking a session with a set of mobile developers, one of them asked a question that made many of them curious. Why multiple classes when single class can do? The main reasoning for single class was that one would be able to save some lines of code. Also, one would be required to create just one object for multiple functionalities. Lets look at some of the key advantages of multiple classes, each one of them having single functionality. High in cohesion, and hence reduced coupling. This tends to make the class reusable. Lesser costly to change than single class. Following explains the cost structure related with a change: Let’s …
Posted in Maintainability, Software Quality. Tagged with Cohesion, Coupling, Object oriented principles, Single Responsibility Principle.
I found it very helpful. However the differences are not too understandable for me