Who Needs an Architect?

The author really "takes a stab" as he said trying to define "architecture" and "architect". He define these words as a way to make "desing" and "designer" sound important. As I said at the previous blog entry, the blueprints in the software context are a tool used to describe at a high-level way, the software model. This article, complets this description, explaining that the software's architecture is the organizattion of the principal and more important components, and how they interact and the smaller pieces that compose them. Later, the article do an unexpected "plot twist", arguing that this description fall in a technicism area, because the "high-level" decription is just useful for the expert developers that are familiarized with TI concepts. 

The abstraction of the most important components is unprecise becuse these components importance is defined by the architect. Something that is true, because this way to represent and abstract a system is technical, as the architects blueprints, not everyone can read them, and understand them. Just the knowlers may be able to work with this specifications. In other hand, the author describes the architecture as a "set of design decisions that mus be specified early in a project", this description takes in count the programming language. In addition to this, we have to consider that the architect is another important thing to take in count. The architect responsabilities include the requirements communication, programming participance, and so on. 

My conclussion of this article, is that the concept at the beginning is hard to accept, but later on it's easier to understand. After this, I understand architecture as all the parts of a software that compose it, and the necessary functionality that all the developers need to understand. And something that is not necessarily unmutable, that is not tied to just one model through the development. The architecture may be changed and its something useful nowadays because the requirements are changed regularly. But, this need to be driven carefully, because the complexity of a system may be incresed if we try to.