Skip to main content

OOPs beyond the Four Pillars - SOLID and GRASP

As we know Object oriented programming is a type of programming paradigm based around programming classes and instances of classes called objects. These can be objects that appear on the screen (e.g., pictures, textboxes, etc.) or are part of the programming (e.g. actors, connections, particles, etc as mentioned in my post http://www.developerscloud.org/2013/02/what-is-oop-basic-concepts.html written ages ago.

Here we are going to extend the oops beyond its four pillars i.e.


  1. Abstraction
  2. Encapsulation
  3. Polymorphism and
  4. Interfaces i.e. Inheritance


So first we will go through SOLID and then GRASP



SOLID Principles are principles of class design.

•SRP: Single Responsibility Principle
–An object should have only a single responsibility & all the responsibility should be entirely encapsulated by the class.
–There should never be more than one reason for a class to change
•OCP: Open/Closed Principle
–Software entities should be open for extension, but closed for modification
•LSP: Liskov Substituion Principle
–Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program
•ISP: Interface Segregation Principle
–many client specific interfaces are better than one general purpose interface
–once an interface has gotten too 'fat' split it into smaller and more specific interfaces so that any clients of the interface will only know about the methods that pertain to them. No client should be forced to depend on methods it does not use
•DIP: Dependency Inversion Principle
–Depend upon Abstractions. Do not depend upon concretions.

–Dependency Injection (DI) is one method of following this principle.

GRASP


•Acronym for General Responsibility Assignment Software Patterns.
•Assigning responsibilities to classes is a critical aspect of object-oriented design.
•Appropriate assignment of responsibilities to classes is the key to successful design.
•There are fundamental principles in assigning responsibilities that experienced designers apply.
•These principles are summarized in the GRASP patterns.
•Has nine core principles that object-oriented designers apply when assigning responsibilities to classes and designing message interactions.


Nine Principles:
•Expert.
•Creator.
•Controller.
•Low Coupling.
•High Cohesion.
•Polymorphism.
•Pure Fabrication.
•Indirection.
•Don’t Talk to Strangers.

I think this article is not so great in terms of visualizations but indeed if you read it, it will help you to brush up your concepts and increase your productivity as well...


In Continuation Next Post: http://www.developerscloud.org/2014/09/extending-object-oriented-programming.html

Comments

Popular posts from this blog

Convert your datatable into generic poco object in c# using linq, ado and reflections.

Follow @harshit_parshii The most common problem that we face these days is to create a common class and method that can be used across all the projects and codes. So today I will be sharing my code where you can see how to make and create a generic function without using entity framework for ado. net. The scenario is like you have an old software that uses stored procedure to return set of entities as a data-table, you do not want to re-write the back-end code as you are creating a web API in c# which needs to be delivered asap. You need to map these data tables to models as you might be using MV* pattern. So here we will be doing one to one mapping of model to data- table, and in similar fashion insert or update can also be done. So basically we are converting a data-table to list of strongly typed object model to do CRUD operations. So we have following things before hand. A helper class is referenced as the database(dbFactory) which executes ado. ne...

With new experiences comes great responsibility

Hello Everyone, I am an ordinary person with some highly looked after skills, not boasting about myself. But after coding in this IT industry for almost 5 years for the first time I am thinking:- Is delivering the code my only responsibility or is there anything else I need to look into as well? From last few month's I was highly involved in some entirely new domain which is financial, and when you play with the number you need to be highly focused, so unable to update my blog as well. When I was working on the urgent deadlines and tight estimates and being from a healthy UI background like css3, html5, responsive design, knockout js, less etc. I was put on the SQL server and asp.net with grid views and some freaked out Telerik controls. I know it's a learning for me and I can see why UX matters to every person in this entire world but not UI and you can write it on stamp paper. User Experience, with logical and functionally correct code, is the need of the hour to...

Run CSS specific to Internet Explorer - Browser Hack

Run CSS specific to Internet Explorer - Browser Hack Referencing to the following blog post, we are going to make CSS targeting exclusively to IE browser, to make it work first we should know what are media queries. A media query consists of a media type and at least one expression that limits the style sheets' scope by using media features, such as width, height, and color. Media queries, added in CSS3, let the presentation of content be tailored to a specific range of output devices without having to change the content itself. For Ex: < style > @media (max-width : 600px) { .facet_sidebar { display : none ; } } So below we will wrap the IE specific CSS rules in @media blocks and trick IE into rendering @media blocks that use media queries. Targeting only IE browsers Style rules defined in the following blocks will only be applied in IE, other browsers will ignore them. IE 6 and 7  @media screen\9 {     body { background: red; ...