Software Architecture (Code Craft)

For this chapter the author gives us an interesting definition of the software architecture, thinking of this concept as the high level design, the clarity around the all picture. This is interesting when is combined with the anecdote that is told to us, because just reinforce the importance around planning and make design before to start the develop or implementation of a software project.

The emphasis on changing the perspective of architecture from a complete detailed focus to a macro overview it's important and one of the concepts that may affect this whole chapter, as stated in the article, the importance of this is not the implementation, but to give guidance considering just a overall view.

Speaking of views, this is an important point too,  because we need to consider that we can have 4 different perspectives, where the conceptual is the initial one, but during the development you will get probably the other three. Considering that we pass to the part of when, and is interesting the statements considering the architecture design as a step even before the requirements, and almost as an independent entity from the development process.

One of the parts that I consider maybe the most important one in the chapter is when the author tell us what is used for the architecture. Three out of three are about maintaining the idea running just as stated, this shows me the importance that even in early stages of a project or an idea, the architecture will take a main roll in time, giving guidance for discarding or validating the advances and the steps that must be taken in the particular project.

Finally we see some specifications around the connections and components, stating that is an important part of this high level design to specify the general purpose of each component and the relations that must exist between them, but the conclusion that I get is that the decisions you've made in the start of a project or program will impact you during a lot of time and that great realization of the architecture is going to give plenty advantages and facilities, against the hard problems that you can get if you do it wrong or even not considering architecture as a necessary task to do.

Comentarios

Publicar un comentario

Entradas más populares de este blog

Microservices

The microservices architecture is a recent term used for this new perspective for the software architecture, and it's based on getting several small services running into a single application that are communicating constantly with the computer via API using HTTP. This information may appear a little so technical but will get relevant at the time of understanding it's structure and purpose. It may appear that is not that different for the traditional model of architectures like the libraries but the microservices get you benefits like the independence of the services, every service could be used and saving a lot of processing for each application opened. This independence also helps at the moment of creating efficient interfaces and to get explicitly the function of every service. The changes in organization, and the approach changing from a project model to a product model, are also differentiators that makes interesting changes for the microservices perspecti
Leer más

Is Design Dead?

For this article there is several topics that appeared very interesting to me. For the initial themes treated, one was the difference between the traditional structured design, and the evolutionary design, and it's a matter that I've even seen as a difficult topic because of the different perspectives presented even by my own teachers, some of them teaching me that the planned design is extremely important and even forcing this practices into our projects, but in the other perspective, some professors taught me to be evolutionary, and to make incremental design based on prototypes making really confusing the decision for the design every project I've made. Also, one of the things that I've found curious into the article is the association that the author makes between the refactoring and the YAGNI's simplicity to the evolutionary design. It's not that usual to understand the "best practices" of programming as supporting any bigger concept than the co
Leer más

The 4 + 1 Model

For this week we have several material to use, and I found it great. First the video that gets us the theory for the 4 different perspective model architecture plus 1, this part of the homework is connected to video that told us a story about the blind men who touched an elephant, and this two are necessary for fully understand the last article, getting combined into this new story about the programmers that found a new program thing and get to understand it in different ways. Its important to mention first the 4+1 model and each view of it, getting initialy the logical view explaining the behavior of components using state machine or sequence diagrams, the process view that gets the way of communication for the different system processes, also we got the development view that describes the elements and the components for the system in order to be completed, at last for the fourth view we got the physical view giving us the physical distribution for the components as well as the topo
Leer más