This chapter was very interesting for me and helped me to see the great importance of software architecture. As well as the functions it has and the benefits we have by paying attention to this step of the software development process.
For this we have to consider with the reading of other chapters of the class, that there are different types of software architecture, and that we have to choose the one that more adapts to our project or to what we want to do. You also have to take into account if you already have a certain progress or if you start with an already established base. All this must be taken into account to choose the best option.
I like that the author emphasizes points like the points of view, the concept of software architecture, as well as when and where the software architecture should be done, the functions that the development process has, he talks the same about the components, connection components and then he talks about the architecture styles, which are: No architecture, Layered Architecture, Pipe and Filter Architecture, Client/Server, Component based architecture and Framework.
Talking about the styles of architecture, it was a very good idea for the author to relate each style with a type of paste, this helps the reader to remember each one of them and have the idea of its definition. Personally, this helps me a lot to be able to remember it for a long time.
In conclusion, I don't like the theoretical part of my classes very much. I feel that the authors of the books make it very difficult to define the concepts and that the students can remember them after reading them. However, the author of this book managed to explain it in a very graphic way, since software architecture is a topic that should be given a lot of importance.
For this we have to consider with the reading of other chapters of the class, that there are different types of software architecture, and that we have to choose the one that more adapts to our project or to what we want to do. You also have to take into account if you already have a certain progress or if you start with an already established base. All this must be taken into account to choose the best option.
I like that the author emphasizes points like the points of view, the concept of software architecture, as well as when and where the software architecture should be done, the functions that the development process has, he talks the same about the components, connection components and then he talks about the architecture styles, which are: No architecture, Layered Architecture, Pipe and Filter Architecture, Client/Server, Component based architecture and Framework.
Talking about the styles of architecture, it was a very good idea for the author to relate each style with a type of paste, this helps the reader to remember each one of them and have the idea of its definition. Personally, this helps me a lot to be able to remember it for a long time.
In conclusion, I don't like the theoretical part of my classes very much. I feel that the authors of the books make it very difficult to define the concepts and that the students can remember them after reading them. However, the author of this book managed to explain it in a very graphic way, since software architecture is a topic that should be given a lot of importance.
Comentarios
Publicar un comentario