4+1 View model


When working on a software project, if you do not have a guide and keep in mind the whole picture, sometimes you as an individual that is part of a team, tend to forget about everything else but the part that was assigned to you. That is what the blog of this week is about and what a perfect example was the elephant story.

From a personal perspective, I can say that this is a reality. If not as dramatic as the elephant chaos created by the blind people who failed to get the whole picture, it was quite funny to say the least to face this situation. Our last semester while working in the intelligent system, the front and back teams ran into a difference about the format of the data that had to be passed between applications. This happened because when each team started to work on their part, encapsulated in their task and never reached out to the other team to reach an agreement and in the end even the data mining and the AI teams got involved.

This type of situations tends to emerge when since the beginning you do not have a stablished guide, and that is where the 4+1 model works best. When involved in a big project it is something essential to have at least one clear picture of everything, and I think that this model works great because it attacks every important aspect of a project, its internal structure, how will it interact with other components, with the hardware and also the users and how it is expected to behave.

In some cases you may need more than that, and in others, like working with smaller projects you probably won’t need as much or you will be required to work with other type of tools and documentation, but what is fundamental is to never loose the whole picture and the final goals.

Comentarios

Entradas populares de este blog

War Games

SOLID

Ethical Reflection on R.P.O.