Understand architectural layers
Overview
This guide shows you how to view an application through its architectural layers - for example presentation, business logic, and data access - and how to investigate the dependencies between them. Architecture layers are defined by an Architecture Model, so this view is available only when a model is associated with the application.
Before you start
| Who this is for | Architect, team lead |
| Role required | Viewer or higher |
| Prerequisites | The application has been imported into CAST Imaging, and an Architecture Model built in the Architecture Studio is associated with it - see Architecture configuration |
The Architecture Layer scope is disabled in the viewer if no Architecture Model is associated with the application.
Step 1 - Open the Architecture Layer scope
In the left panel, select the Architecture Layer scope. An Architecture Layer is a subset of an Architecture Model whose content is defined by rules that group objects during analysis. Select an individual layer to focus on it.
Step 2 - Read the layer diagram
Each node represents an architectural layer and the links between nodes show the dependencies that exist between them. Use this diagram to confirm that the application is structured the way you expect.
Step 3 - Drill into a layer
Drill into a layer node to reveal the objects it contains. This lets you move from the high-level tier view down to the specific objects responsible for a given dependency.
Step 4 - Review compliance
An Architecture Model can define which dependencies between layers are permitted. Review the model’s compliance results to find dependencies that breach the intended architecture - see Architecture configuration for how models and their rules are defined.