2-5: The 4+1 View Model

So, in order to understand the 4 + 1 view model we need first to define the components of this view model. In this case, the components of this view model are the following ones: Logical view, Process view, Physical view, Development view and the +1, the Use Case view.

Having this in mind, let me define each one of these views in order to fully understand this view model:

  1. Logical View: Shows the parts that comprise the system, as well as their interactions. It also represents a set of abstractions and emphasizes classes and objects. This view can be represented with the following UML diagrams: class diagrams, state diagrams, object diagrams, sequence diagrams.
  2. Process View: Describes a system's processes. It also shows any communication between those processes, explores what needs to happen inside the system. It is particularly helpful when your system will have a number of simultaneous threads or processes. This view can be represented with the following UML diagrams: activity diagrams.
  3. Physical View: Models the system's execution environment. It also maps software artifacts onto the hardware that hosts them. This view can be represented with the following UML diagrams: Deployment Diagrams.
  4. Development View: Describes the system's modules, or components, including packages, subsystems, and class libraries. It also gives a building-block view of the system. This view can be represented with the following UML diagrams: component diagrams, and package diagrams.
  5. Use Case View (+1): Shows the system's functionality by capturing user goals and scenarios. It offers an outside-world perspective on the system. It is also helpful in defining and explaining the structures and functionality in the other four views. This view can be represented with the following UML diagrams: use case diagrams.

It is important to always be aware of knowing that in software development it does not exists one viewpoint it always exists a multiples viewpoint and all are correct. This is why, we need to come up to a deal in the develop of a software piece in order to construct it the better way possible by taking notice of all the external and internal boundaries of the development.

Comentarios

Publicar un comentario

Entradas populares de este blog

Summary Second Period

Imagen
So far we have been seeing a lot of different things this second period. So it is important to make a summary of all that topics that covered this second period. In this occasion the second record exam will cover the following topics: Design Patterns covered in the theory book. Microservices. SOLID principles. The 4+1 view model. As I said earlier, this blog entry will be a summary of all these topics but I encourage you to see all your notes, programming activities and even read again the theory book of Olsen. Design Patterns Design Patterns are typical solutions to commonly occurring problems in software design. These patterns were proposed by the Gang of Four: Erich Gamma, John Vlissides, Ralph Johnson and Richard Helm. Template Method Pattern The Template Method Pattern is a behavioral design pattern that defines a skeleton of an algorithm in the superclass but lets subclasses override specific steps of the algorithm without changing its structure. In this kind o
Leer más

2-3: Microservices

We can define Microservices as an architectural style which approach is to develop a single application as a suite of small services, each of them, running its own processes and communicating via lightweight mechanisms, often Microservices uses an HTTP resource API. We also need to compare a traditional monolithic application in order to compare and to give a better explanation of what is a Microservice. A monolithic application puts all its functionality into a single process and scales by replicating the monolith on multiple servers. But, microservices do not work like this, a microservices architecture puts each element of functionality into a separate service and scales by distributing these services across servers, replicating as needed. Having this context, we can have a better idea of what is a Microservice. Now, it is time to enumerate the important characteristics of a Microservice Architecture, have in mind that it does not exist a silver bullet in development so, no
Leer más

2-4: Understanding the SOLID Principles

The first thing that came to my mind when I read the title of the lecture was, what does SOLID stands for? So, first let me contextualize what is SOLID and then explain the meaning of all the letters in this acronym. As I said before, SOLID is an acronym that stands for five principles of object-oriented programming and design. The objective of these principles is the avoidance of dependencies, because the more things you depend on, the greater the chance something will go definitively wrong; these 5 principles are the following ones: S => Single Responsibility Principle (SRP): States that a class should have exactly one responsibility. This means, that it should have exactly one reason (or one class of reasons) that cause it to be changed; nevertheless, many programmers have the superstition about the systems they maintain things like "Don't touch this module" or the difficult task of selecting that single responsibility. O => Open/Close Principle (OCP): St
Leer más