Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Glossary


This page describes some of the terms used throughout the Architecture Checker and this user guide.

LayerA Layer represents a layer in your application's architecture. You can assign specific objects to the layer through the use of specific selection criteria.

Layers are checked via the Check model option and have authorized or forbidden dependencies attached.

Layers can be displayed in the Model tab in the Main window.

SetA Set is an element that contains specific selection criteria for assigning objects. These Sets can then be re-used in multiple Layers whenever required through the use of the Member of block or the Excluded from block (see Working with block elements for more information).

Sets are not checked via the Check model option.

Sets can be displayed in the Model tab in the Main window.

UnassignedThe Unassigned item acts like a garbage collector that retrieves all unassigned objects (i.e not assigned to any other Layer in the Architecture Model). Its purpose is to help define the behavior of the Architecture Checker with regard to unassigned objects, authorize dependencies to these objects or keep the default behavior: i.e.  dependencies to unassigned objects are forbidden.

Notes - When you define an Authorized type model (see Define a new Architecture Model), if there are "real life" links to objects that are not part of any layer in your model and you do not assign them to this Unassigned layer, the CAST Architecture Checker will report violations.

- The Unassigned item is checked via the Check model option.

- The Unassigned item can be displayed in the Model tab in the Main window.

DependencyA Dependency simply indicates that one layer depends on another or vice versa. This is indicated by a arrow between layers in the Model tab in the Main window. Note that layers can depend on each other, therefore you can define dependencies in both directions between two layers.
  • No labels