Software Architecture

The design stage is one of the most important from my point of view, since it is the first stage where special features of the program that we want to develop are set. As mentioned in the book, it is very important to have a detailed and accurate design, where the program requirements are included, the dependencies of classes, their relationship classes and in case that you are using interfaces, how it is related with the other classes.

The main point of the design phase is to identify the errors as soon as possible, since the more you delay to identify, will be more expensive to remove. For example, suppose you are in the design stage and we realize that we are committing an error related to the requirements, if we continue with the process and you get to the stage of development that involves code, and when we realize the program does not work as expected, it will take hours or even days, depending on the difficulty of the program, to find the error. However, if the error is identified in the first stage, the cost will be much lower.

The part that explains the different design styles relating them with names of pastas, I think that was a good idea because it made better understand the concept. It is good to note that the design is like the foundation of a house, and if they are not strong enough, all subsequent jobs can come down for a minimum error. I remember that in the course of Fundamentals of Design was said that, the program design was optimal, if this stage takes at least half the time it took to develop this program, for example if it takes eight hours to develop program, it is expected spend at least 4 hours in the design stage.