CAST Architecture Checker - Define Layer or Set Contents on Documentation - V2

CAST Architecture Checker - Define a Data Layer

Mon, 01 Jan 0001 00:00:00 +0000

Example

You have created a Layer called Data (i.e. matches all the source code that runs the Data tier in your application) and you would like to assign all SQL tables that use a specific naming convention (beginning with T_) to this layer. To do this, you can combine a selection based on the object type and another based on the name.

Step-by-step process

In the Types and Properties window, type “SQL” in the Filter textbox. This action filters the CAST Meta-Model properties to show you only the Types that contain the “SQL” string in their name:

CAST Architecture Checker - Define a Business layer

Mon, 01 Jan 0001 00:00:00 +0000

Example

You have created a Layer called Business (i.e. matches all the source code that runs the Business logic in your application) and you would like to assign all classes and interfaces to this layer, i.e. all the objects belonging to the Java package called “com.mycompany.app.BU”.

Step-by-step process

Select the fullname property in the Types and Properties window and drag and drop it to the the Business Layer you’ve already created in Define dependencies mode (see Define Layers, Sets and Dependencies), as shown in the screenshot below:

CAST Architecture Checker - Using Sets

Mon, 01 Jan 0001 00:00:00 +0000

This page explains how you can use sets to configure your architecture model. See Glossary for more information about Sets.

Example

In a large application Architecure Model, it is necessary to create a “BackOffice” layer that must hold all Database and SAP ABAP objects. Moreover, the database and the SAP ABAP objects cannot communicate so it is not necessary check a dependency between the database and the SAP applications. In this scenario, good practice is to create two Sets, one for the database objects and one for the SAP ABAP objects and to include them in the BackOffice Layer. This way the two Sets can be re-used in other models.

CAST Architecture Checker - Using drag and drop from Type and Properties window

Mon, 01 Jan 0001 00:00:00 +0000

When creating Layers and Sets, you can drag items from the Types and Properties window directly into your Layer or Set. This is particularly useful when you need to create a Set that includes all objects of a specific Technology.

In the following example, we want to create a Set that includes all Cobol object types:

Drag the parent Cobol item over to your Set:

The result is that all Cobol objects will be included in the Set:

CAST Architecture Checker - Working with external objects

Mon, 01 Jan 0001 00:00:00 +0000

If you are dragging and dropping identification, types and categories from the Types and Properties window to the Main window (Model tab) to create your selection criteria, by default, the Architecture Checker will use the basic All objects matching criterion. This will match all objects with any of the criteria you add in.

In addition, any external objects (i.e. external to the Application) of the matched object(s) will also be assigned to the layer or set (as well as sub-objects). Including external objects is useful for example if, when a selection criterion matches a Spring bean class, this class will be included in the Layer regardless of whether it belongs to the Application or comes from an external JAR.

CAST Architecture Checker - Working with multiple selection criteria

Mon, 01 Jan 0001 00:00:00 +0000

The example given in Define a Data Layer assigns two criteria to one layer toassign all SQL tables beginning with “T_”. This results in the following layer:

Note that the two criteria are located within the All objects (with sub-objects) matching text box. This ensures that an AND match is created (circled in red) and all criteria in that text box must be met.

If, however you want to assign all SQL tables and all objects (of any type, not just SQL tables) beginning with “T_”, you need to define the layer as follows into separate criteria using the OR condition:

CAST Architecture Checker - Working with sub-objects

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

In addition, any sub-objects of the matched object(s) will also be assigned to the layer or set (as well as external objects). Sub objects are for example packages, classes and interfaces contained in a parent Java Package object.

CAST Architecture Checker - Using the Action menu options to automatically create layers

Mon, 01 Jan 0001 00:00:00 +0000

On this page:

Info

Not applicable when working with Quality Rule Models.

When creating Layers, you can use various automatic layer creation options available in the Action menu:

Create layers from User Defined Module selection

This option is available in the Action menu located on the toolbar. It allows you to create a layer for each Module that belongs to the currently selected Application. All Modules (whether automatically or manually defined) listed in the Module tab of the Application editor in the CAST Management Studio can be selected as the basis for the layer:

CAST Architecture Checker - Using the calls any or called by any layer option

Mon, 01 Jan 0001 00:00:00 +0000

Info

Not applicable when working with Quality Rule Models.

When defining dependencies for your layers, you can, if required, allow a layer to:

call any layer
be called by any layer

To do so:

Right click your layer and select Calls any layer or Called by any layer:

An icon will be displayed in the title bar of your layer:


	Current layer can call any other defined layer
	Current layer can be called by any other defined layer
	Current layer can call any and be called by any defined layer

Info

When you activate either option or both options, dependencies ( arrows) already in the Model tab in the Main window coming from or to the current layer will be remov