The 4 +1 Model

-
After watching "The Elephant and the Blind Programmers" and the "4.6 SEM: 4+1 View into Software Architecture" videos, and reading the article "The Elephant and the Blind Programmers" we will discuss the 4+1 View Model, this a model through this blog entry. The 4 + 1 model is used to organize an application according to what every person needs to see, depending on what is the most import things to them and the ones that are not that important. Here we can use the example of the blind programmers and the elephant, every programmer had a different concept of the elephant, the same happens with a team of engineers. The security engineer will see the relevant parts to his needs, so the administrator. 

The 4 + 1 model has different views, these are:

- Logical View: Class diagram, communication diagram, sequence diagram, state machine diagram, object diagram. Object model: what components will be made and how the will behave. 

- Process View: Concurrency, synchronized aspects. Activity diagram, timing diagram. 

- Physical View: How software and hardware are related, what system looks like when finished. Deployment diagram. 

- Development View: Component diagram, package diagram. Organization of the assets during the development work (which belongs to what). 

- Use Case View: Use case diagram. How the system interacts with the world and systems around it. 

Every view works together with the rest to create a great way to see software and a different way to understand it. We can apply these views to the 3 main parts of software: structural elements of codes and interfaces, the collaboration between structural elements and the composition of elements and their use into larger systems. I think we would have to implement this model in future projects because if not, programmers will work as the blind programmers and it is important that every member of the project knows what others need.

References: 

- Booch, Grady. (2010). The Elephant and the Blind Programmers . Retrieved March 10, 2019, from http://34.212.143.74/apps/s201911/tc3049/activity_4_plus_1/

- DrJKasurinen. “4.6 SEM: 4+1 View into Software Architeture.” YouTube, YouTube, 18 June 2014, www.youtube.com/watch?v=5r60GuRu8V0.

- kanika24fps. “Six Blind Men.” YouTube, YouTube, 18 May 2009, www.youtube.com/watch?v=iBqgr5xZLz0.

Comentarios

Publicar un comentario

Entradas más populares de este blog

Hidden Figures

-
Hidden Figures is a movie directed by Theodore Melfi which relates the story of Katherine Goble, Dorothy Vaughan and Mary Jackson, a mathematician that worked as a human computer in a group where gender discrimination and racism is very present. Katherine and a group of women worked in the West Area Computers of the Langley Research Center in Hampton, Virginia where they were assigned to different jobs as they were needed.  After Yuri Gagarin was launched to space, United States were in a hurry to send their astronauts into space, so Katherine was assigned to work on the program and Mary was assigned to work on the capsule heat shield while Dorothy was still in charge of the rest of the women. After being battered by they job mates, Katherine demonstrated her knowledge to solve difficult equations needed for the launching and for picking up the astronaut, Mary was an essential part of the team that developed the heat shield and finally, Dorothy trained the group of women to progra
Leer más

An Introduction to Metaprogramming

-
After reading the article "An Introduction to Metaprogramming", there are a few things that I would like to discuss through this blog entry, I would like to start by explaining what is a metaprogram. A metaprogram is a program that generates other programs or parts of a program. So, when we talk about metaprogramming we are talking about writing metaprograms. This kind of programs is useful to eliminate or reduce a tedious or error-prone programming task.  There is a special kind of source generator named quines. A quine is a program that generates a copy of its own source text as its complete output. While other programs (dynamic programs) have the feature to modify some parts of the code during runtime without the need to generate a source code. For our course of Software Design and Architecture, we are using Ruby, which employs the feature to automate common programming task, a clear example is on classes, where you use an attr_accessor method to produce the read/wri
Leer más

Microservices

-
After reading the article "Microservices", there are a few things that I would like to discuss, we must start first by defining what does a Microservice is. A Microservice architectural style is an approach to developing a single application into modules, each one running its own process and communicating with each other, so when an update is needed the process of implementing the changes is easier.  One interesting thing is the way the Microservice style is compared to the monolithic style where a monolithic application is built as a single unit. A monolithic server is a natural way to approach building such a system. Explaining in a simple way, a monolithic application puts all its functionality into a single process and scales by replicating the monolith into multiple servers; while a microservice architecture puts each element of functionality into separate service and scales it by distributing these services across servers, replicating as needed.  A Microservice
Leer más