Migration to S.O.L.I.D pattern
-
Single Responsibility Principle - a class should have only one job. So if a class has more than one responsibility, it becomes coupled. A change to one responsibility results to modification of the other responsibility.
-
Open-Closed Principle - Software entities(Classes, modules, functions) should be open for extension, not modification.
-
Liskov Subst…
-
Single Responsibility Principle - a class should have only one job. So if a class has more than one responsibility, it becomes coupled. A change to one responsibility results to modification of the other responsibility.
-
Open-Closed Principle - Software entities(Classes, modules, functions) should be open for extension, not modification.
-
Liskov Substitution Principle - The main idea behind Liskov Substitution Principle is that, for any class, a client should be able to use any of its subtypes indistinguishably, without even noticing
-
Interface Segregation Principle - Make fine grained interfaces that are client specific Clients should not be forced to depend upon interfaces that they do not use.
-
Dependency Inversion Principle - Dependency should be on abstractions, not concretions. High-level modules should not depend upon low-level modules.