Fundamentals of Software Engineering
As we know, software design isn’t the code itself but the way that code must be structured in order to have a higher level of control over it. Patterns themselves are repeatable solutions to problems that occur constantly in software design. These type of structured ways of designing software aren’t finished designs that can be already transformed into code but they are descriptions that show how to solve certain problems. They are normally templates used in order to have a richer idea on what it will be developed in the future.
There are mainly 3 types of design patterns:
These patterns approach design by the instantiation of classes. They are divided in class creation which inherit in the instantiation step and object creational patterns that use delegation as it should be in order to achieve certain task. Some of these are:
This type of pattern takes a look on how classes and objects are composed. The creation of compose interfaces is mainly by using iheritance. Some of these are:
The interaction between objects inside a class happens in a behavioral pattern. These patterns are mainly focused with communication between objects. Some examples of these are:
Bloggers involved in the creation of this post:
All this information was taken from Sourcemaking.com and all rights belong to them.
Accordingly to The UCAR (University Corporation for Atmospheric Research), software design is the process of defining methods, functions objects and the structure and interaction of the code in order to have fully functional programs and satisfaction of the users.
Here’s a really clear video taken from TED x conferences with Jackson Stone showing the importance of S.D.
Software design is all about thinking in the users themselves and giving them the opportunity to have a full experience when approaching to technology by letting them have a nice experience.
