Software Architecture

Software architecture is something that is said a lot to us students but we really never had the chance to grasp it, we where always told that having a good architecture is the key to having a software that is easy to debug, read, and cheap to maintain and that this things are good in the long run even if at the beginning having a good architecture and implementing it seems to be expensive in both money and time.

For both buildings and software it is very important to have a plan on how you are going to do things before actually doing them, because this design will be what will maintain things afloat, it might seem that software architecture is not very relevant because it seems possible to build software that  complacently lacks architecture and design and the code can be useful, but designing things before doing them is important, that can make things better and cheaper now and in the future, a good design can mean having software that is cheaper even in the near future because it make it easier to find mistakes, it makes it easier to understand what is actually going to be done in the near future and it ensures less changes in what the code will be doing. Changes are a part of almost everything and they may happen even with a great design and architecture, but it is very different to have to change something because your client changed his mind and having to change something because your lack of design made it difficult for you to see what you were going to do.

A good design can be the difference between something working like it was intended or not and it can make things cheaper to make and maintain so it most be used every time we make a program, specially if the program haves a very big scope.