Who needs an architect?

-
After reading the article "Who Needs an Architect?" by Martin Fowler, I found many interesting things that I would like to express through this blog entry. 

One thing I found really interesting is the way the author explains what things architect and architecture do and how they are connected to software programming. I also found interesting the way the text describes software architecture, according to IEEE, software architect is defined as  "the highest level concept of a system in its environment" and Ralph Johnson describes it as a "how the system is divided into components and how the components interact through interfaces". These two definitions may be different but I think there are some similar points between them, they both include the idea of a team. This is a very important concept in software architecture because a complete software is not made only by a person, it is the teamwork that can make this possible. 

Now, talking about architects and architecture, I think that an architect is someone who plans and builds things but after reading the article, I learned that a software architect is someone who will set up the tools and environments for the development of the program, we can say that he will plan all the needed things to build the program. He also manages the work and establishes delegates for the tasks that the development phase will have. 

Finally, the software architect will have to know very good his team, he must know how to improve the abilities of all the team members to make the project evolve, he must guide the team and create an experienced team so after they work by themselves they won't need a coach. 

I keep on learning about software architects and software architecture, I think it is a very important job in the software development industry. 


References: 

- Fowler, M. (2013, July). Who Needs an Architect?[PDF]. IEEE Software.

Comentarios

Publicar un comentario

Entradas más populares de este blog

Microservices

-
After reading the article "Microservices", there are a few things that I would like to discuss, we must start first by defining what does a Microservice is. A Microservice architectural style is an approach to developing a single application into modules, each one running its own process and communicating with each other, so when an update is needed the process of implementing the changes is easier.  One interesting thing is the way the Microservice style is compared to the monolithic style where a monolithic application is built as a single unit. A monolithic server is a natural way to approach building such a system. Explaining in a simple way, a monolithic application puts all its functionality into a single process and scales by replicating the monolith into multiple servers; while a microservice architecture puts each element of functionality into separate service and scales it by distributing these services across servers, replicating as needed.  A Microservice
Leer más

Understanding the SOLID Principles

-
The following blog entry will explain the SOLID Principles based on the book Ace the programming interview: 160 questions and answers for success.  SOLID stands for 5 widely accepted principles of object-oriented programming and design, these are the S ingle Responsibility Principle, O pen/Closed Principle, L iskov Substitution Principle, I nterface Segregation Principle, D ependency Inversion Principle. These principles will be explained through this entry.  - Single Responsibility Principle: This principle says that a class should have only one responsibility. It should have only a reason or a class of reasons that cause it to change. This principle might cause a problem for programmers because deciding what a single responsibility means can be a difficulty. A single responsibility refers to a group of related business processes or it could be broken down in its constituent parts, with each part designated as a responsibility. - Open/Closed Principle: This principle s
Leer más

Ethical Reflection on Ready Player One

-
Everything that has a beginning must have an end and this book is not the exception. During the course of S/W Design and Architecture, we read the book "Ready Player One" by Ernest Cline and I would like to make an ethical reflection of this book through this blog entry. I would like to start with two quotes:  Morrow wrote in his autobiography that he’d left GSS because ... he felt that the OASIS had evolved into something horrible. “It had become a self-imposed prison for humanity,” he wrote. “A pleasant place for the world to hide from its problems while human civilization slowly collapses, primarily due to neglect.” (p. 120)  (Halliday speaking) “I created the OASIS because I never felt at home in the real world. I didn’t know how to connect with people there. I was afraid, for all of my life. Right up until I knew it was ending. That was when I realized, as terrifying and painful as reality can be, it’s also the only place where you can find true happiness. Beca
Leer más