Architectural Blueprints — The “4+1” View Model of Software Architecture
Philippe Kruchten
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, scenariodriven, iterative development process.
Curtis Badke
- Looked at the date the paper was published compared to other software methodologies and planning methods such as Agile or UML. Methodologies change as we develop a better understanding of how software is different from other industries.
- The paper realizes that many different groups of people have to look at software projects despite having different concerns. Separating the views allows each group to get the information they need and communicate with other groups effectively.
- The ideas behind software methodologies are sometimes interpreted incorrectly. Some see agile as a simple checklist or waterfall as a method rather than a consequence.
- Discussed personal experiences with software projects and management.