Who needs an architect?


I think that the article’s author did a great job for setting a basis for a definition of architecture and for software architecture. I consider that the approach of defining architecture as the part of the design that is considered important, and as something that is difficult to change at later stages of the development. I consider this an accurate approach, since one of the parts we try to define at this stage of our majors is the language we will work on since we are not so versed yet in that field.

That being said, this helps to separate between software architecture and the definition of planning and designing of software development. Considering architecture as something more specific than the design helps understand what the past lecture for the blog tried to tell when defining software architecture and its types.

On the other hand, I quite disagree with the textual approach they took when specifying who determined what is software architecture. I don’t think that only the developers define what part of the system is important, since I think that the requirements that the customers give to the developers also play an important role to define the importance of a module. If a customer considers that one of the main activities of the system is financial calculations, then saving the expenses to the employee who introduced it, then important modules are going to be the calculation part and the storage one. Then is for the developers to decide if the role that the communications are going to play need to be crucial as well in order to decide if that is part of the architecture.

Another thing I think the article got right is to define the software architect as a senior who pushes forward his/her team to improve but still is there when a tricky situation appears. I think that this is an important characteristic that someone playing this role has to have and is quite useful. On the other hand, I don’t know how to feel about the part of his task being that he is not needed. I agree with Johnson that making something so versatile can make the system become complex. I do not believe that is a must, but sometimes I think it can be true.

Comentarios

Publicar un comentario

Entradas populares de este blog

War Games

I think that for us geeks, the movie War Games is considered some sort of mandatory movie. I had not seen it before, and still knew that despite the sci-fi the movie has, it was entertained and funny. What I loved most about the movie, besides the things it showed about machines at that time, like the sound control they had to access the lines, or how you had to connect to the internet, or the low security implemented back then, like in The cuckoos egg, is that they show the limitations we sometimes tend to forget about machines. They. Don’t. Think. In the movie, after the tech people in charge to turn the key fail the test, they replace them with a super advanced programmed with AI machine, because it would not hesitate to do the job if necessary. This started to cause every sort of trouble when David managed to enter via a backdoor the system had, while trying to filter a video games company. Then, thinking that the programs the computer had were games, David makes the comp
Leer más

SOLID

Although the SOLID principles are something that should be, at least, common in object-oriented programs, we programmers tend to forget about some of them and incur in practices that negatively affect our code. From the beginning when we are taught OOP, we might not be aware of these principles even if we tend to gravitate towards some of them depending on how we learn to OOP program. For a start, I think that when we learn to program in the Object-Oriented Mode, we usually are taught to apply Single Responsibility because it is easier to think about classes as a description of an object that has a set of characteristics and one function. It might cost a little at the beginning to effectively accomplish this, but when you gain some practice, for the sake of clarity this is usually the go-to way. The next most usual behavior I follow is the Interface Segregation Principle. Since it is somewhat similar to the Single Responsibility, it is easier to understand and then apply in t
Leer más

Ethical Reflection on R.P.O.

Being RPO a book I really loved and enjoyed from the very first time I read it, I think we can rescue one or two things besides the entertained story and the wholesome references. I hope that those who read the book can see them and think at least a little about those topics. In the book, we have this society that has seek refugee of the reality inside a virtual world called Oasis, because for them, reality was not as interesting, or in some cases reality was really a terrible place to be. There is also this world with almost all the resources wasted and in consequence a lot of people living either in an extreme poverty, or being miserable with the little income they had, which pushed them further into Oasis.   Our reality being not as bad as this world inside R.P.O. nowadays this imaginary situation where people aisle themselves is similar to what we tend to do with technology and social media. We tend to create this image we want other people to see on this media and we car
Leer más