Scenario modeling
Introduction
4+1 is a model designed by Philippe Kruchten to "describe the architecture of software systems, based on the use of multiple concurrent views".[1]
[2] Views usually describe the system from the point of view of different stakeholders, such as end users, developers or project managers. The four views of the model are: logical view, development view, process view and physical view. Additionally, a selection of use cases or scenarios is often used to illustrate the architecture, serving as another view. Therefore the model contains 4+1 views:[1].
References
- [1] ↑ a b Kruchten, Philippe (1995, November).[1]Architectural Blueprints — The “4+1” View Model of Software Architecture., IEEE Software 12 (6), pp. 42-50.: http://www.cs.ubc.ca/~gregor/teaching/papers/4+1view-architecture.pdf
- [2] ↑ Kruchten, Philippe (1995, November) (Versión en español).[2]Planos Arquitectónicos: El Modelo de “4+1” Vistas de la Arquitectura del Software.: https://juliopezblog.files.wordpress.com/2021/04/planos-arquitectonicos-el-modelo-de-4-1-vistas-de-la-arquitectura-del-software.pdf
- [3] ↑ a b c d Mikko Kontio (2008, July) Architectural manifesto: Designing software architectures, Part 5.: http://www.ibm.com/developerworks/architecture/library/ar-archman5/