sábado, 18 de agosto de 2018

Software Architecture


I totally agree with the ideas expressed in the reading titled "ARCHITECTURE OF THE SOFTWARE: laying the foundations of software design" in chapter 14 of the book "Code Craft" by the author Goodliffe. In my short experience working around 3 months in a software company, it can be proven that the lack of a software architecture has negative consequences for most of those involved.

The advantages of having good architecture are remarkable, especially when changes may be required in the future. I think it is necessary to have a document (or several) that at least explains the basic structure of a project that reaches the general understanding of the project, which is very useful when the software passes from one computer to another.

The most complicated thing is not having a software architecture that has to read and know how these components connect with each other. The above, even for excellent programs, is a tedious process and is a task that can take a long time, which translates into lost of money for companies. In addition, a project can be ruined if the code is not documented and does not have good programming practices either.

On the other hand, I also agree that an architecture should consider the scalability of a project. If this is not considered from the beginning, the costs of adding features to a project increase considerably. You should also consider the different work teams that will be involved. Clearly, it is not the same to create an application or a static web page, or a software system that requires several platforms and a database.

Finally, based on my experience, I can say that it is important that the software architecture is updated together with the changes that are made in the project, thus ensuring that all the work teams through which the project passes, add the modules that were added by extension.

No hay comentarios.:

Publicar un comentario