The 4+1 View Model
In this reading we learned about the 4+1 view model, this model is basically a mechanism or methodology designed to separate the different aspects of software into different views or parts so that the stakeholders can focus into all the different parts of software and have a better understanding about this and this not only benefits stakeholders, as it is segmented it benefits every person working into the system from developers to management and this is a great example of why it is smart to segment the architecture into distinct views.
The most important point here is that we have a use case view which makes modelling far more efficient and in each project we will have different modeling tools that will support the 4+1 approach and basically this will allow us to have templates that will make everything easier from de the development, to the implementation, to the understanding.
The views work in this way, the logical view has the information about the system in general and in an UML the logical view is modeled using class, object, state machine and interaction diagrams, the process view then describes the concurrent processes within the system and in the UML. Then activity diagrams are used to model the process view and this evolves the development of the system and finally the use case view describes the functionality of the system from the perspective of the outside world.
As we can see the 4+1 view model basically wants to make everything easier for everyone.
Comentarios
Publicar un comentario