4+1 view model

4+1 view model

This time I am going to write about two videos and an article.

Video 4+1 View into Software Architecture:

Usually, the creation of software development is preceded of many UML diagrams, which try to create a model of the system. UML contemplates many views of the design, considering manmy points of view, and providing tools (Different diagrams) that make easy the comprehension of the ideas, you could use interaction diagrams, Behavior diagrams and many others. 
  
The problem is that UML is not a development language, so it could not be clear in all the situations. Different situations may use different ways to express how something functions so, Use cases, Class diagrams, Deployment diagrams, Sequence diagram, State machines are options to describe interactions.

The video describes a special view, which could help us to complement the vision of a system, to not focus only in one specific layer, With you, ladies and gentleman, the "4+1 View Into Architecture" basically it describes 4 views, Logical View, Development View, Process View and Physical View, and the “+ 1”, the Use Case View/Scenarios.

So, below the explanation of each one:

  • Logical view: What sort of objects we are going to be building for the product.
  • Development view: How the system is organized also called Implementation view.
  • Process view: describe the concurrency and synchronized aspects of the software.
  • Physical view: how the software and hardware are related.
  • Use Case view: Explanation of how the system is expected to behave.

All separate layers help to complement the others

Video Six Blind Men:

This video was fun, it talks about 6 blind men who decide to touch an elephant So they could know how it looks like. What actually happens is that each one of them touch the animal but everyone touches a different part of the elephant, so obviously they end having a different opinion of how an elephant looks like. the story ends with a fight between all of them because there were not equal opinions, even though they all touch the same animal.

Article The Elephant and the Blind Programmers:


Ok, what happens here is the same problem the blind men have with the elephant, everybody can distinguish something but the experience make them to appreciate different things, at the end a wise man tell them “All you are right but all of you are not considering the whole animal”, the lesson, don’t focus in just one part. 

Comentarios

Publicar un comentario

Entradas populares de este blog

Is Design Dead?

Is Design Dead? I am going to write about the article “is Design Dead?” By Martin Fowler, it was a interesting article and was written in a unfamiliar way considering the title. He starts talking about the extreme programming and how it is one of the causes of the poor pre design that nowadays is (barely) used for big or small development. Software development needs like almost everything a design which defines not only how it will work, but how to make the specific modules and what job they are going to perform to accomplish a global goal. And well he basically explains the differences between planned design an evolutionary design, that is the reason why I think the title is funny, two kinds of design but he says it is dead, basically what happens is that, the extreme programming and the constant use of the technique pushes the developers to use the evolutionary design. Why? Easy, the extreme programming is a practice thas searchs the simplicity in the creation of...
Leer más

Software Architecture

Software Architecture This week I read the chapter 14 of the book "Code Craft: The Practice of Writing Excellent Code" titled " SOFTWARE ARCHITECTURE Laying the Foundations of Software Design" the first thing we should do is define what is software architecture, as we use the word architecture sounds logical that a building comes to our mind, but talking about software we can take the idea of a structure, so the author told us we can join the concepts to create in our brain the idea of high level design but of course the reason of the “similarity” in the concepts comes because the software architecture is used to create a propitious place to make code, at the end this can be used as a guide for the development. Some benefits of the software architecture are that this helps to validate requirements and conditions of a project so it can be used in a more free way for the different areas like design and development and can help to “talk the same language”,...
Leer más

Understanding the SOLID Principles

This week the blog will talk about the article "Understanding the SOLID Principles" written by Edward Guiness, this is a brief summary that presents the definition of the SOLID Principles. The general objective of the SOLID principles, and so the author in the article, is to implement best practices in the creation of objects and classes in specific cases depending on the situation that is presented. And with you, the 5 principles *drumroll*: • Single Responsibility Principle • Open/Closed Principle • Liskov Substitution Principle • Interface Segregation Principle • Dependency Inversion Principle The first of this is the Single Responsibility Principle, it says that a class, should have just exactly one responsibility, just one reason or an only class of reason to exist. This responsibility should be implemented to the class, so for this reason a class just has one reason to be modified. Why implement this? Easy, in a big project you will have lots of classes ...
Leer más