Software Architecture
It is interesting to know about Software Architecture. It is an excellent tool to make software because we have the advantages to improve our code, make it more legible, scale it easier, and the most important: make our software simple. However, we need to take in mind different viewpoints. Not all systems and requirements are the same. We have to evaluate each part to fulfill all user needs if possible.
It is possible that currently things can work in other way. The software and technologies change every day so we need to be up to date with all these tools. Nevertheless this chapter shows us a brief description of how we can improve our performance as software architect. Personally, I would like to gain sufficient experience to be a brilliant architect. I like being a software developer, but I think that becoming a software architect might be more complex and funny.
Obviously, each work has its advantages and disadvantages. Even so, for the moment I will just talk about the possibilities along with the tasks that have an architect. As the author said throughout the book, we will be good architects if we make a simple architecture because it will allow us make an elegant solution. What can we understand for elegant solution? In my opinion an elegant solution is one that is easy to understand for each stakeholder without the need to explain complex terms.
In addition, it is a total challenge make an accurate solution. We need to have in mind that our settlement must have space to make the software maneuverability. In my point of view, this is essential inasmuch as it makes our software extensive and modifiable. As I mentioned previously the technologies, user requirements or business models can change immediately hence we don't want to spend time trying to enhance our architecture if the solution doesn't adapt to the needs.
Clearly, there are more things that we must keep in mind because software architecture is an very board world. This chapter is a little introduction of what kind of things we need to consider as software architect. The truth is each person has their own solutions and thoughts about how an architecture can be structured, there will always be a lot of solutions. These aspects are just tools so that our system is not truncated and can be scaled in the posterity to make our life as simple as possible.
Goodliffe, P. (2006). Software Architecture, Code craft: the practice of writing excellent code. San Francisco: No Starch Press.
Gif taken from Google.
Obviously, each work has its advantages and disadvantages. Even so, for the moment I will just talk about the possibilities along with the tasks that have an architect. As the author said throughout the book, we will be good architects if we make a simple architecture because it will allow us make an elegant solution. What can we understand for elegant solution? In my opinion an elegant solution is one that is easy to understand for each stakeholder without the need to explain complex terms.
In addition, it is a total challenge make an accurate solution. We need to have in mind that our settlement must have space to make the software maneuverability. In my point of view, this is essential inasmuch as it makes our software extensive and modifiable. As I mentioned previously the technologies, user requirements or business models can change immediately hence we don't want to spend time trying to enhance our architecture if the solution doesn't adapt to the needs.
Clearly, there are more things that we must keep in mind because software architecture is an very board world. This chapter is a little introduction of what kind of things we need to consider as software architect. The truth is each person has their own solutions and thoughts about how an architecture can be structured, there will always be a lot of solutions. These aspects are just tools so that our system is not truncated and can be scaled in the posterity to make our life as simple as possible.
Goodliffe, P. (2006). Software Architecture, Code craft: the practice of writing excellent code. San Francisco: No Starch Press.
Gif taken from Google.
Comentarios
Publicar un comentario