The 4+1 View Model

Hi, today’s blog entry is going to talk about 2 videos and one article called The Elephant and the Blind Programmers, by Grady Booch. The first video was about de 4+1 view, while the was more related to the article as both explains the Elephant and blind programmers’ case.

In the case of the 4+1 view, there are five main aspects to consider:

1.    Logical view: It’s the logical software’s design and what components will be made and how the should behave. Class diagram.
2.    Development view: It’s concerned with the organization during development and the interaction between the program and its components. Component diagram.
3.    Process view: Activity Diagram, it includes de concurrency and synchronized aspects, and also how the program functions.
4.    Physical view: It’s how the software and hardware are related and their interaction, how the system looks like when finished. Deployment diagram.
5.    Use Case view: It’s how the system interacts with the world, customers, and systems around. It is basically how the system must behave.

Then there’s the second video and the article, which talks about the elephant and the blind programmer’s case. Basically, there was a new large, noisy, smelly thing, and the blind programmers wanted to examine the beast and guess with their minds and reason by touching the creature. In the end, they argued about what they perceived about the creature and the problem was that they were both right and wrong since each one inspected a different part or in a different way the animal. There were different perspectives. What this metaphor is trying to explain is an example of the 4+1 view model, telling us that we have to consider all the perspectives in order to get all the right characteristics and by joining them, we get the complete object we’re analyzing.


I liked this one, because it gave us a clear and funny example that helped us to understand better the main concept.

Comments

Post a Comment

Popular posts from this blog

Understanding the SOLID Principles

Hi, this entry is going to talk about a section called “Understanding the SOLID principles” from the book “Ace the Programming Interview: 160 Questions and Answers for Success” by Wiley in 2013. Basically, the acronym SOLID is explained a round this book section. This acronym stands for five accepted principles about object-oriented programming and design: 1.       S ingle Responsibility Principle: It stays that a class should have just one responsibility. Despite the fact that this principle sounds easy, I found it a little bit complicated, because the explanation wasn’t direct and simplified. Also, the author mentioned that there might be cases in which a class might have two responsibilities. So, at the end, what exactly does this principle stands for? 2.       O pen/Closed Principle: It stays that a class or a function should be open for extension but closed for modification. What does this mean? Our code must have the capability of being extended, but we have to always
Read more

Microservices

Hi, today’s entry is going to talk about an article written by James Lewis and Martin Fowler called “Microservices” in 2014. Basically, by calling microservices, they are referring to like a particular way of designing software applications as suites of independently deployable services. But something interesting is that there is not a precise definition of that type of architectural style, there are only common characteristics around distinct organizations, business capability, automated deployment, intelligence in endpoints and also decentralized control of languages and data. This was the first time I heard this term, and something strange is that despite I didn’t notice about its existence I’d used them sometimes. Later in the articles, the authors gave us some characteristics that any Microservice Architecture must have. They are the following: 1.       Componentization via Services:  This is telling us that by building software, we put together components. So, this archite
Read more

WarGames

Hi, for this entry I’m going to talk about a 1983 movie directed by John Badham called WarGames. The story told in the movie is in the times of the cold war. Basically, there is a gifted and very skilled kid (talking about computers) who were able to hack the US Government defense computer. That computer was expected to be capable of analyzing and taking decisions, kind of machine learning, because, over time, it was learning. The genius kid, David Lightman, just wanted to enter to that computer just to play games, in this case, “Global Thermonuclear War”. The game started and, in order to stop the arrival of the 3rth World War, David and the creator stopped the machine. I had never seen this movie before, actually just heard about it one time in the novel we’re reading for this class (Ready Player One). This movie surprised me, despite the fact that I saw it 40 years approximately after its release. A computer capable of learning by itself and by the time? and also capable of sta
Read more