volume_mute
Krutchen's 4+1 View Model
publish date: 2026/06/10 09:23:14.409264 UTC
volume_muteKrutchen's well-known 4+1 view model proposes four fundamental architectural views related by use cases or scenarios. Match each view with its correct description.
To complete the line match
- Click on an item in the first group
- Click on the match in the second group
To delete a match, double click on a line
View
Physical view
Logical view
Development view
Process view
Description
Shows key abstractions in the system as objects or object classes; requirements can be related to entities in this view
Shows how, at run-time, the system is composed of interacting processes; useful for judging non-functional characteristics like performance and availability
Shows how the software is decomposed for development, broken into components implemented by a single developer or team; useful for software managers and programmers
Shows the system hardware and how software components are distributed across processors; useful for systems engineers planning deployment
Correct Answer
(1) Logical view,Shows key abstractions in the system as objects or object classes; requirements can be related to entities in this view
(2) Process view,Shows how, at run-time, the system is composed of interacting processes; useful for judging non-functional characteristics like performance and availability
(3) Development view,Shows how the software is decomposed for development, broken into components implemented by a single developer or team; useful for software managers and programmers
(4) Physical view,Shows the system hardware and how software components are distributed across processors; useful for systems engineers planning deployment
Explanation
Krutchen's 4+1 model: (1) Logical view — key abstractions as objects/classes; (2) Process view — run-time process composition, used for non-functional analysis; (3) Development view — software decomposition for development teams; (4) Physical view — hardware and software deployment mapping. The '+1' refers to use cases/scenarios that relate the views.
Reference
Software Engineering, Ian Sommerville, 10th edition