Scopes

The nine ways to look at an application in CAST Imaging.

A scope is a predefined way of looking at an application. Each scope shows the same objects but organizes them differently. Choose the scope that matches your current question.

Available scopes

Application scope

Shows the full application, organized by the CAST Taxonomy (front-end, middleware, back-end). This is the default view when you open an application.

Use it to: get a high-level overview, explore component structure.

Module scope

Shows objects grouped into functional or technical modules.

Use it to: understand business boundaries, measure coupling between modules.

Transaction scope

Shows the call graph for one user-facing transaction — from the entry point to the database.

Use it to: trace a business flow end-to-end, understand what a transaction touches.

Data Call Graph scope

Shows all objects that read from or write to a specific database table.

Use it to: understand data ownership, plan a database migration.

Architecture Layer scope

Shows objects organized by architectural tier (UI, business logic, data access).

Use it to: detect layer violations, verify architectural rules.

Service scope

Shows the application’s exposed services — REST endpoints, SOAP operations, and similar entry points.

Use it to: understand the public API surface, assess the impact of changing an endpoint.

Application-to-Application scope

Shows the links between two or more applications in your portfolio.

Use it to: map dependencies across systems, plan a decommission.

Custom scope

A user-defined subset of objects saved for repeated use.

Use it to: focus on a bounded context, share a specific view with the team.

Project Structure scope

Shows source files and folders as they exist on disk.

Use it to: navigate by file, correlate file structure with modules.

Learn more