This article presents a model for describing the architecture of software-intensive systems, based on the use of multiple, concurrent views. This use of multiple views allows to address separately the concerns of the various stakeholders of the architecture: end-user, developers, systems engineers, project managers, etc., and to handle separately the functional and non functional requirements. Each of the five views is described, together with a notation to capture it. The views are designed using an architecture-centered, scenario-driven, iterative development process.
@article{arxiv.2006.04975,
title = {Architectural Blueprints: The 4+1 View Model of Software Architecture},
author = {Philippe Kruchten},
journal= {arXiv preprint arXiv:2006.04975},
year = {2020}
}
Comments
Early draft, better quality than IEEE published version