volume_mute
Five Uses of Application Architecture Models
publish date: 2026/06/10 22:54:0.668637 UTC
volume_muteAs a software designer, you can use models of application architectures in a number of ways. Match each use 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
Use
Starting point for architectural design
Assessing components for reuse
Design checklist
Organising work of the development team
Vocabulary for talking about application types
Description
Base your initial design on a generic architecture, specialising it for the specific system being developed
Compare your developed architectural design with the generic architecture to check consistency
The architecture identifies stable structural features that can be developed in parallel by different team members
Compare existing components against the generic structure to see whether comparable components exist for reuse
Use concepts from the generic architecture to discuss and compare applications of the same type
Correct Answer
(1) Starting point for architectural design,Base your initial design on a generic architecture, specialising it for the specific system being developed
(2) Design checklist,Compare your developed architectural design with the generic architecture to check consistency
(3) Organising work of the development team,The architecture identifies stable structural features that can be developed in parallel by different team members
(4) Assessing components for reuse,Compare existing components against the generic structure to see whether comparable components exist for reuse
(5) Vocabulary for talking about application types,Use concepts from the generic architecture to discuss and compare applications of the same type
Explanation
The five uses of application architecture models are: (1) starting point for design; (2) design checklist for validation; (3) organizing development team work using parallel development of stable structural features; (4) assessing reuse opportunities by comparison; and (5) providing a vocabulary for discussing application types.
Reference
Software Engineering, Ian Sommerville, 10th edition