S/W Design and Architecture Blogggggg

On today’s blog we are going to talk about the 4+1 view model, which all of this was taken from two videos. This model says that, when we are creating software we need to focus on 4 things: The logical view: which is the logical design of the software The development view: the way the program interacts between its components The process view: the way the program functions The physical view: the way the software and the hardware interact between each other Now to explain more these 4 things, the logical view refers on what are we going to build, not the actual code, but the design and logic it will have, a good example of it is a class diagram.   The development view refers on how the program is organized and how it communicates between its own parts, the component may be a good example of this because it shows exactly that, how is organized and how it communicates to work. The one that refers on how the program works is the process view, it...

On today’s blog we are going to talk about the SOLID principles, which were discovered by Robert Martin, the famous Uncle Bob from the podcast of the previous entry. This principles are recommended to be used whenever someone wants to create an object oriented program. There are 5 principles where the acronym SOLID comes from which are the following S ingle Responsibility Principle (SRP) -> it says that any class should only have one responsibility. Yet, the author ends up saying that there might be some classes that have two responsibilities (the invoicing class that has some logging routines). In the end, I didn’t understand this principle well because I found the explanation confusing (as the author said, practice is much more difficult than theory).  O pen/Closed Principle (OPC) -> open extension but closed modification Although the author says that if you change a parent class method it might kill another part of the ...