Software architecture
In this entry of the book is good to know that Software Architecture really means both of its parts, that it uses real architecture and building as an analogy of how the development should be, from the blueprint, detailing all the modules and how they connect one to another, just like in the blueprints used in buildings, to even the point of view that in my opinion are not as closely based, it says they are based on different points of view of the building, one from structure, wiring, plumbing, etc., and they are comparing it to the conceptual, implementation, process and deployment, I can se the relation but I don’t think is as close as talking about the 1 to 1 that are blueprints. Apart from the blueprints they also talk about requirements and how the arquitects must know super well the primal need of their clients, and have a clear view of the project, because bad decisions early are much cheaper that bad decisions in a later stage of the game with the error running through all ...