Who needs an architect?

Who needs an architect?

This week the assign reading was "Who Needs an Architect?" by Martin Fowler. He starts explaining that architecture is a term when “we want to talk about design but want to puff it up to make it sound important”. He also gives a more formal definition of software architecture “the highest-level concept of a system in its environment. The architecture of a software system (at a given point in time) is its organization or structure of significant components interacting through interfaces”

As we can see the architecture could be considered as a basic and important element in the process of creating a new software. Talking about why is so important in more common words in software it is the representation, a kind of map, in which the developing will be settle in.

A comment that have a lot of sense for me is “In most successful software projects, the expert developers working on that project have a shared understanding of the design” and ok, it happens in every type of project and then the cherry in the cake “This shared understanding is called ‘architecture.’ ”

Taking the previous paragraph as base is logic to think that is essential for the architecture the communication between the developers and of course the development areas, in this way the problem could be understood in a general way and approached in a most convenient form. Why? Easy, the problem will have a better understanding if we can see different perspectives and the join them together.

Fowler defines two types of architects.

Architectus Reloadus: is the person who makes all the important decisions, this person needs to ensure the system’s conceptual integrity. He usually defines a plan which is followe for the team members because he thinks that the team members are not sufficiently skilled to make those decisions. (how sweet)


Architectus Oryzus: is someone who responsability is be involved with the project at a high level because needs to "be very aware of what's going on in the project, looking out for important issues and tackling them before they become a serious problem” 

Comentarios

Publicar un comentario

Entradas populares de este blog

Is Design Dead?

Is Design Dead? I am going to write about the article “is Design Dead?” By Martin Fowler, it was a interesting article and was written in a unfamiliar way considering the title. He starts talking about the extreme programming and how it is one of the causes of the poor pre design that nowadays is (barely) used for big or small development. Software development needs like almost everything a design which defines not only how it will work, but how to make the specific modules and what job they are going to perform to accomplish a global goal. And well he basically explains the differences between planned design an evolutionary design, that is the reason why I think the title is funny, two kinds of design but he says it is dead, basically what happens is that, the extreme programming and the constant use of the technique pushes the developers to use the evolutionary design. Why? Easy, the extreme programming is a practice thas searchs the simplicity in the creation of...
Leer más

Software Architecture

Software Architecture This week I read the chapter 14 of the book "Code Craft: The Practice of Writing Excellent Code" titled " SOFTWARE ARCHITECTURE Laying the Foundations of Software Design" the first thing we should do is define what is software architecture, as we use the word architecture sounds logical that a building comes to our mind, but talking about software we can take the idea of a structure, so the author told us we can join the concepts to create in our brain the idea of high level design but of course the reason of the “similarity” in the concepts comes because the software architecture is used to create a propitious place to make code, at the end this can be used as a guide for the development. Some benefits of the software architecture are that this helps to validate requirements and conditions of a project so it can be used in a more free way for the different areas like design and development and can help to “talk the same language”,...
Leer más

Understanding the SOLID Principles

This week the blog will talk about the article "Understanding the SOLID Principles" written by Edward Guiness, this is a brief summary that presents the definition of the SOLID Principles. The general objective of the SOLID principles, and so the author in the article, is to implement best practices in the creation of objects and classes in specific cases depending on the situation that is presented. And with you, the 5 principles *drumroll*: • Single Responsibility Principle • Open/Closed Principle • Liskov Substitution Principle • Interface Segregation Principle • Dependency Inversion Principle The first of this is the Single Responsibility Principle, it says that a class, should have just exactly one responsibility, just one reason or an only class of reason to exist. This responsibility should be implemented to the class, so for this reason a class just has one reason to be modified. Why implement this? Easy, in a big project you will have lots of classes ...
Leer más