Page tree

The informational material contained in this section is provided as a courtesy for use by CAST’s clients. The material in this section is not considered part of any CAST product’s official Documentation. CAST does not warrant that the information is current or that it addresses all potential issues. Licensing details are documented on this page: https://www.gnu.org/licenses/lgpl-3.0.en.html

Skip to end of metadata
Go to start of metadata

Modules represent executable software components or tightly coupled sets of executable software components, developed and deployed together, that deliver some of the functionality provided by an Application.

By default the automatic "Full Module Content" module will always be created unless you change the settings - i.e. source code from all Analysis Units will be placed in one module. This default module belongs to the "My System" system. You can choose to create your own user defined modules in addition to or instead of the default, or you can use the other automatic Module strategy "one module for each Analysis Unit". 

The definition of Modules within Applications impacts the accessibility and usability of Application assessment results. Specifically, in the CAST AIP quality and quantity model, the Module is the smallest assessment entity. The definition of a Module can improve the relevance of the analysis results by linking modules to development teams and application functional layers etc.

For further consideration about the pros and cons of user defined module creation see also:

Objects produced during the analysis of an application which are not included in a User Defined Module will not appear in the Architecture Checker, Transaction Configuration Center or TRI data. All objects generated during the analysis of your application must be included in a User Defined Module even if the objects are produced by a Content Enrichment tool.

CAST recommends creating a Module for each functional component of an application. Modules can be built in the CAST Management Studio automatically or manually for maximum configuration flexibility:

CAST offers three automatic modules for display of source code in the CAST dashboards:

Full ContentThis Module is selected by default. It corresponds to all the source code for all Analysis Units configured in your Application. It will be called "<Application name> full content". If this content is sufficient for your needs, you do not need to select any other automatic or User Defined Modules.
Analysis Unit ContentIf you select this option, the CAST Management Studio will create one Module per Analysis Unit in your Application. Each Module will be called "<Analysis Unit name> content".
Unassigned Objects ContentThis option should be activated when you are exclusively using User Defined Modules (i.e. the Full Content and Analysis Unit Content are not ticked). When ticked, an automatic Module will be created containing any objects that were not assigned to one of your User Defined Modules, enabling you to see them in the CAST AIP dashboards.
  • No labels