The 4+1 View Model (Comment)

UML everywhere, or that is what every professor at my university has taught me. In addition there are other ways of viewing the software architecture. 4 + 1 View is one of this ways, 4 + 1? Yes! isn't that 5? Well this is because the called "5th View" are the scenarios.


View Name Logical View Development View Process View Physical View Scenarios
Description What components are going to be made and how they will behave What belongs to what during the development Concurrency and synchronized stuff SW (Software) and HW (Hardware) relations AND the how the system looks when finished Interactions between the components
Diagrams
  • Class Diagram
  • Communication Diagram
  • Sequence Diagram
  • State Machine Diagram
  • Object Diagram
  • Component Diagram
  • Package Diagram
  • Activity Diagram
  • Timing Diagram
  • Deployment Diagram
  • Use Cases

The way to create software is by getting a customer/sponsor, gather requirements, design architecture, create such architecture components which in combination receives the name of source code, and after that, it is deployed.

While I was reading the first lines of "The Elephant and the Blind Programmers" the first thing that came to my mind was that the author was talking about a bug which gets into a program that worked fine. When I was almost finishing it I understood that it was making reference to the 4 + 1 View Model in which every part is correct but they describe different aspects.

After that I saw the video "Six blind men" which talks mostly the same as the reading but in a more simple way.

What happens when a software architect, a database developer, a software programmer, a network designer, a software tester and a security developer come and define a system? The system will be defined with the bias that each of them has because of their different study specializations. They all complement with one another but are coupled on its point of view.

One of these views won't be sufficient to describe your software, neither two, neither three, all of them will create a complete description of the system to be described, it happens the same with the electrical, sewer, construction, systems in a house, everyone completes and are part of that house.

Software development can be done by one programmer but after exploring the above content, I think that it is necessary to have more people creating it to really have a more complete program.


References:

Kasurinen, J. (2014). 4+1 View into Software Architeture (Video). Obtained from https://www.youtube.com/watch?v=5r60GuRu8V0

Six Blind Men (Video). Obtained from https://www.youtube.com/watch?v=iBqgr5xZLz0

Booch, G. The Elephant and the Blind Programmers. Obtained from
http://webcem01.cem.itesm.mx:8005/s201713/tc3049/the_elephant_and_the_blind_programmers.pdf 

Comentarios

Publicar un comentario

Entradas populares de este blog

Metaprogramming (Comment)

The first thing that comes to my mind when reading/hearing the term metaprogramming the word metadata comes to my mind but they don't have the same meaning. Metadata is the data of the data of something, and Metaprogram is not the data of a program, it refers to a program that creates other programs. Imagine a program that creates an app for iOS devices and Android, wait! There is already some options in the internet to do such thing, for example Ionic, but metaprogramming is not that new. There are many other metaprograms like gcc, python interpreter, parse generators like bison, and more. A great example that I read was the one of Erika. She was more outstanding than his programming professor and made a program that generated another one. Although she didn't create something revolutionary, it was so good to explain metaprogramming. As mentioned in the lecture, a quine is a program that prints its own source code, but why would this be helpful for something? Imagine that
Leer más

Understanding the SOLID Principles - Comment

Imagen
The SOLID principles are great to reduce the possibility of things going wrong, but how can they do it? Well as the reading says, by minimizing class dependencies. These principles are: S ingle Responsibility Principle  O pen/Closed Principle  L iskov Substitution Principle  I nterface Segregation Principle  D ependency Inversion Principle A great example of the Single Responsibility Principle is the usage of microservices. This services have a main purpose and most of the time they only work for that. For example an OCR (Optical Character Recognition) microservice should only accept an input, try to recognize the text inside the image and return a result, nothing less, nothing more. Any variation should be coded outside the microservice to have a different result. An image that can help you understand it is the next one: For the Open/Closed Principle I think that a good example is the ToString in which you only change the "behavior" of the class you are
Leer más

Is Design Dead? - Comment

In every coding project there are people that will write it and some others will design it but without any question, both of them should know that coding isn't trivial, design errors or coding errors will occur and it is essential to have a risk plan in case that something happens. This allows to have a stablished way of dealing with the problems that will appear as the project grows. Depending on the scope of the coding project, if it will be a program that has some components (an API, a database, users, security, etc.), it is important to design it before beginning to code it. This allows to design it to be scalable, secure, maintainable, and error-prove. If the project is just to write a a program that will resemble a calculator, it is just fine to code it as you go. This means that depending on the complexity of the project, it is necessary to define certain documents to establish the foundations that will allow to create bigger projects (more modules, more people assigned t
Leer más