The 4+1 View Model

The 4 + 1 View Model

I have some ugly flashbacks of my FIS (Fundamentos de Ingeniería de Software) classes and its subsequent related classes as well, basically this whole thing of architecture and UML diagrams are taught on those classes and, oh boy!, it was complete boredom although necessary even though I don't like it.

When we are told to do something (in this case to program) we like to have everything so the only thing that we worry about is that our code executes correctly but when we have to do all that stuff of documenting and making diagrams or when the program can't go on like it was told and oneself has to do the changes to the diagrams, it is at this point that we really notice how important is to correctly develop this whole understanding process with its related documentation, even more when you are not the only one in the team.

One has its own point of view of each thing and each problem, so on a team the chances that everyone agrees on some model grows smaller as the team grows bigger, like with that blind people examples.

There is bound to be chaos where there is no order, however with people, to have a completely ordered system of thoughts that everyone shares is almost impossible, a common understanding however, can be possible and only then, the beginning of a project can truly start.

The result of this understanding can be seen during the planification and design steps of a project development plan, a team made of one member of each of the teams that work on a project must work unified to develop the neccessary models that the project will be based upon, more precisely, the code models must correctly identify how the system is going to be implemented, related to other systems if needed, build upon and everything that it needs to be specified from the smallest component so that there isn't any room for misunderstandings.