There is a good chance that you all are aware of the SOLID principles. There are many more principles for us to consider and adhere to while developing OO software.
These are the Principles of Object Oriented Class Design popularly known as the SOLID Principles.
- The Single Responsibility Principle [SRP]
- The Open/Closed Principle [OCP]
- The Liskov Substitution Principle [LSP]
- The Interface Segregation Principle [ISP]
- The Dependency Inversion Principle [DIP]
The next two set of principles, are related to packaging. Package here refers to a deployable component, or simply something you would ‘release’ for others to use - like a jar file. These are the Principles of Package Architecture.
Package Cohesion Principles
- The Release Reuse Equivalency Principle [REP]
- The Common Closure Principle [CCP]
- The Common Reuse Principle [CRP]
Package Coupling Principles
- The Acyclic Dependencies Principle [ADP]
- The Stable Dependencies Principle [SDP]
- The Stable Abstractions Principle [SAP]
Bertrand Meyer’s Principles
Note that some of the principles listed above are also originally described by Mayer.
- The Linguistic Modular Units principle
- The Self-Documentation principle
- The Uniform Access principle
- The Open-Closed principle
- The Single Choice principle
__G__eneral __R__esponsibility __A__ssignment __S__oftware __P__rinciples
Guidelines for assigning responsibility to classes and objects in object-oriented design. Helps us in deciding which responsibility should be assigned to which object/class. Identify the objects and responsibilities from the problem domain, and also identify how objects interact with each other.
GRASP are more than base principles. These techniques have not been invented to create new ways of working, but to better document and standardize old, tried-and-tested programming principles in object-oriented design.
- Information Expert
- Low Coupling
- High Cohesion
- Protected Variations
- Pure Fabrication