The 4+1 View Model

I think the connection between the five blind programmer and the 4 + 1 models is that each programmer represented one part of this models. In other words,  each blind programmer described the beast from one point of view. While one programmer described it from a logical approach, other programmer described it from a development approach.

The moral of this story is that each person look at the problem from your own point of view and immediately we put away the opinion of others. However, we can build a proper systems if we take this five points of view. For example, we try to suit each opinion in one of the 4 + 1 views.

If the view describes the system as an objects model or it represents a set of abstractions then it could be a logical view because it shows the parts that comprise the system and their interaction and focuses in classes and objects. With this in mind so we can represent  other part of the 4 + 1 model.
  • Process view shows any communication between the system processes and explores what needs to happen inside itself.
  • Physical view models the system's execution environment and maps software artifact onto the hardware that hosts them.
  • Development view describes the system's modules, components, packages, subsystems and class libraries. Furthermore, it gives a building-block view of the system.
  • Use case view illustrates what the system is supposed to do, captures user goals and scenarios and offers and outside-world perspective on the system. 
Even so, I keep thinking that this model only applies to big projects where we have a lot of objects, classes, packages, modules and so on. It could be an good idea to know how this model behaves in little or medium projects, maybe it'll perform in the same way.

Booch, G. (2010). Software Design and Architecture. Retrieved April 26, 2020, from http://34.212.143.74/s202011/tc3049/the_elephant_and_the_blind_programmers.pdf

rmb1905. (2009, March 9). 2.01_The 4 1 Model [Video]. Youtube. https://www.youtube.com/watch?v=yp2-_YbCuyM

kanika24fps. (2009, May 18). Six Blind Men [Video]. Youtube. https://www.youtube.com/watch?v=iBqgr5xZLz0

Comentarios

Publicar un comentario

Entradas más populares de este blog

Software cratfsmanship

Imagen
Listening to the podcast seemed quite interesting to me because it touches different points that are important for software development. Like everything, following good programming practices will always help keep the code in good condition. In addition, the methodologies also help not only to have the code in good condition, they also improve the performance of the application and its quality. Ever since I started working as a software developer and as a computer systems engineering student, I have constantly wondered how I could ensure the quality of my software. Because I work in a startup, all the code is developed by me and consequently I have to keep myself up to date on the techniques they used to better understand it and so that someone else is also able to understand it at their time. Clearly the idea is a bit hasty, but it allows me to see in what ways I could start to grow as a student and as a developer. As Bob Martin mentions, what is sought when following certain work
Leer más

Moon Machines: The Navigation Computer

Imagen
Currently, we live in a world where we use different tools that were made for people and teams with enormous skills in their area. One of the most important aeronautic and computational systems invention was the navigation system.  It is inimaginable to try to dimension how prepared are the people that made the navigation system that the NASA used to launch a rocket to the moon. When the principal organization of aeronautic of USA chose the MIT as first team with the intention to send a little crew to our most important satellite, they knew they were putting their trust in people capacitated to complete this task in time and form.  I remember that when I was watching the video, it seemed interesting how the team thought about all these components and how they could make the navigation system with the simple fact of designing a prototype and then implementing it. I think they had to be really intelligent and trained people in order to create a system never constructed before. 
Leer más

Software Architecture

Imagen
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 po
Leer más