Design Patterns
Every one who is in the software industry has heard it about design pattern,have worked on it (knowingly an unknowingly) . Software engineers with 1-2 years of experience gets impressed with people, who is talking on design patterns and explaining one or two patterns. Everyone is interested in learning and knowing design patterns, a single search in Google would give 1000 of search pages, explaining design but for some reason it never been explained in a simple or lucid way. At least the type of material available make it more complex and second most important is the time invested in understanding them and trying to implement them.
In this and future post I will explain what design patterns are in an easy and simple language (avoiding the jargon).
Take an example.. while making a recipe /cooking, we do one of the two things, 1. start cooking (if we know cooking ) or 2. search on the web for recipes before we start to cook, so that we can get help and make make a dish.. We try following exactly the same steps, use the same same ingredients and quantity, so that recipe comes out good, a lot of them succeed in getting the recipe to the mark and this continues.. people follow it..
Design pattern are some what, recipes – they were tried and tested solutions and now they have been documented for other to use. Design pattern are not a complete solution to software problem, but guide you to in getting started to solve the problem..
The 3 mains areas where in design pattern are in creating objects.., defining structure of software solution/ Architectural and defining communication between objects. This clearly indicates design patterns revolve around object creation, architectural structure and object communication..
They are broadly classified..
1. Creational
2. Structural
3. Behavioral.
Thanks,
Hussain
No comments:
Post a Comment