<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>About CAST Imaging on CAST Imaging Documentation</title>
    <link>https://a477574b.claude-generated-a3n.pages.dev/docs/about/</link>
    <description>Recent content in About CAST Imaging on CAST Imaging Documentation</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://a477574b.claude-generated-a3n.pages.dev/docs/about/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What is CAST Imaging?</title>
      <link>https://a477574b.claude-generated-a3n.pages.dev/docs/about/what-is-cast-imaging/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://a477574b.claude-generated-a3n.pages.dev/docs/about/what-is-cast-imaging/</guid>
      <description>&lt;p&gt;CAST Imaging is a browser-based tool that turns application source code into an interactive graph. You can explore the structure of any enterprise application without reading code line by line.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-problem-does-it-solve&#34;&gt;What problem does it solve?&lt;/h2&gt;&#xA;&lt;p&gt;Large applications can contain millions of lines of code spread across many technologies. Understanding how the parts connect — and what breaks when you change something — is very difficult without a visual map.&lt;/p&gt;&#xA;&lt;p&gt;CAST Imaging reads the output of a static code analysis and displays the results as a navigable graph. You can zoom in from a high-level architecture view all the way down to individual methods and database calls.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The CAST Imaging Stack</title>
      <link>https://a477574b.claude-generated-a3n.pages.dev/docs/about/the-cast-imaging-stack/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://a477574b.claude-generated-a3n.pages.dev/docs/about/the-cast-imaging-stack/</guid>
      <description>&lt;p&gt;CAST Imaging is not a single program. It is a set of four components that each do a specific job. You need all four to go from source code to a visible graph.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-four-components&#34;&gt;The four components&lt;/h2&gt;&#xA;&lt;h3 id=&#34;aip-console&#34;&gt;AIP Console&lt;/h3&gt;&#xA;&lt;p&gt;AIP Console is a web application you use to register applications, deliver source code, and start analyses. It is the main control panel for the analysis pipeline. You access it through a browser.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Applications and Snapshots</title>
      <link>https://a477574b.claude-generated-a3n.pages.dev/docs/about/applications-and-snapshots/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://a477574b.claude-generated-a3n.pages.dev/docs/about/applications-and-snapshots/</guid>
      <description>&lt;h2 id=&#34;application&#34;&gt;Application&lt;/h2&gt;&#xA;&lt;p&gt;In CAST Imaging, an &lt;strong&gt;application&lt;/strong&gt; is the unit of work. It corresponds to one software system — for example, a banking back-end or an e-commerce website. Each application has its own graph in the viewer.&lt;/p&gt;&#xA;&lt;p&gt;An application is created in AIP Console, where you also deliver the source code and run analyses.&lt;/p&gt;&#xA;&lt;h2 id=&#34;snapshot&#34;&gt;Snapshot&lt;/h2&gt;&#xA;&lt;p&gt;A &lt;strong&gt;snapshot&lt;/strong&gt; is the result of one analysis run. Each time you run a full analysis, CAST produces a new snapshot. A snapshot captures the state of the application at a point in time: all objects, all links, all metrics.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Objects, Nodes, and Links</title>
      <link>https://a477574b.claude-generated-a3n.pages.dev/docs/about/objects-nodes-and-links/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://a477574b.claude-generated-a3n.pages.dev/docs/about/objects-nodes-and-links/</guid>
      <description>&lt;p&gt;Every graph in CAST Imaging is made of three things: objects, nodes, and links.&lt;/p&gt;&#xA;&lt;h2 id=&#34;objects&#34;&gt;Objects&lt;/h2&gt;&#xA;&lt;p&gt;An &lt;strong&gt;object&lt;/strong&gt; is a code artifact. Examples include:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;A Java class or method&lt;/li&gt;&#xA;&lt;li&gt;A C# interface&lt;/li&gt;&#xA;&lt;li&gt;A SQL table or stored procedure&lt;/li&gt;&#xA;&lt;li&gt;A REST endpoint&lt;/li&gt;&#xA;&lt;li&gt;A configuration file&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;CAST Imaging discovers objects automatically during analysis.&lt;/p&gt;&#xA;&lt;h2 id=&#34;nodes&#34;&gt;Nodes&lt;/h2&gt;&#xA;&lt;p&gt;A &lt;strong&gt;node&lt;/strong&gt; is the visual representation of an object on the canvas. At high zoom levels (Level 1–4), a node can represent a group of objects — for example, an entire technology layer or a module. At the lowest level (Objects level), each node represents one individual object.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Scopes</title>
      <link>https://a477574b.claude-generated-a3n.pages.dev/docs/about/scopes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://a477574b.claude-generated-a3n.pages.dev/docs/about/scopes/</guid>
      <description>&lt;p&gt;A &lt;strong&gt;scope&lt;/strong&gt; 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.&lt;/p&gt;&#xA;&lt;h2 id=&#34;available-scopes&#34;&gt;Available scopes&lt;/h2&gt;&#xA;&lt;h3 id=&#34;application-scope&#34;&gt;Application scope&lt;/h3&gt;&#xA;&lt;p&gt;Shows the full application, organized by the CAST Taxonomy (front-end, middleware, back-end). This is the default view when you open an application.&lt;/p&gt;&#xA;&lt;p&gt;Use it to: get a high-level overview, explore component structure.&lt;/p&gt;&#xA;&lt;h3 id=&#34;module-scope&#34;&gt;Module scope&lt;/h3&gt;&#xA;&lt;p&gt;Shows objects grouped into functional or technical modules.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Aggregation Levels</title>
      <link>https://a477574b.claude-generated-a3n.pages.dev/docs/about/aggregation-levels/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://a477574b.claude-generated-a3n.pages.dev/docs/about/aggregation-levels/</guid>
      <description>&lt;p&gt;Within any scope, objects are organized into &lt;strong&gt;levels&lt;/strong&gt;. Levels let you start with a broad view and drill down to the detail you need.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-levels&#34;&gt;The levels&lt;/h2&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Level&lt;/th&gt;&#xA;          &lt;th&gt;What you see&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Level 1&lt;/td&gt;&#xA;          &lt;td&gt;Very large groups — for example, one node per technology family&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Level 2&lt;/td&gt;&#xA;          &lt;td&gt;Smaller groups — for example, one node per application layer&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Level 3&lt;/td&gt;&#xA;          &lt;td&gt;Components or subsystems&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Level 4&lt;/td&gt;&#xA;          &lt;td&gt;Packages or modules&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Level 5&lt;/td&gt;&#xA;          &lt;td&gt;Individual classes, procedures, or similar objects&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Objects level&lt;/td&gt;&#xA;          &lt;td&gt;The same as Level 5 but with full drill-down capability and contextual actions&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;p&gt;Not all levels are available in every scope. The Transaction scope starts at Level 4, for example.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Call Graphs</title>
      <link>https://a477574b.claude-generated-a3n.pages.dev/docs/about/call-graphs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://a477574b.claude-generated-a3n.pages.dev/docs/about/call-graphs/</guid>
      <description>&lt;p&gt;A &lt;strong&gt;call graph&lt;/strong&gt; shows the objects involved in a transaction or a data access path, and the links between them. Because some transactions touch thousands of objects, CAST Imaging offers three display modes to balance detail against performance.&lt;/p&gt;&#xA;&lt;h2 id=&#34;reduced-call-graph&#34;&gt;Reduced call graph&lt;/h2&gt;&#xA;&lt;p&gt;The default mode. CAST Imaging removes objects that are less important to understanding the flow. The result loads quickly and is easier to read.&lt;/p&gt;&#xA;&lt;p&gt;Use this mode first. Switch to a different mode only if you need more detail.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tags and Annotations</title>
      <link>https://a477574b.claude-generated-a3n.pages.dev/docs/about/tags-and-annotations/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://a477574b.claude-generated-a3n.pages.dev/docs/about/tags-and-annotations/</guid>
      <description>&lt;p&gt;CAST Imaging gives you two ways to add information to objects: &lt;strong&gt;tags&lt;/strong&gt; and &lt;strong&gt;annotations&lt;/strong&gt;. Both are stored on the server and visible to all users who have access to the application.&lt;/p&gt;&#xA;&lt;h2 id=&#34;tags&#34;&gt;Tags&lt;/h2&gt;&#xA;&lt;p&gt;A &lt;strong&gt;tag&lt;/strong&gt; is a short label you attach to one or more objects, transactions, or modules. Tags are searchable. You can use them to:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Group objects that belong to the same migration effort (for example, &lt;code&gt;migration-target&lt;/code&gt;).&lt;/li&gt;&#xA;&lt;li&gt;Mark objects that need review (for example, &lt;code&gt;high-risk&lt;/code&gt;).&lt;/li&gt;&#xA;&lt;li&gt;Filter long lists of transactions to find the ones that matter.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;You can add tags manually one object at a time, or import them in bulk from a CSV file.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Modules and Custom Aggregation</title>
      <link>https://a477574b.claude-generated-a3n.pages.dev/docs/about/modules-and-custom-aggregation/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://a477574b.claude-generated-a3n.pages.dev/docs/about/modules-and-custom-aggregation/</guid>
      <description>&lt;h2 id=&#34;modules&#34;&gt;Modules&lt;/h2&gt;&#xA;&lt;p&gt;A &lt;strong&gt;module&lt;/strong&gt; is a group of objects that belong together from a functional or technical point of view — for example, a payment processing module or an authentication module.&lt;/p&gt;&#xA;&lt;p&gt;CAST Imaging computes modules automatically during the analysis. The analysis engine groups objects based on how they call each other and how they are organized in the source code. You can see modules in the &lt;a href=&#34;../discover-application-architecture/explore-application-modularity/&#34;&gt;Module scope&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;custom-aggregation&#34;&gt;Custom aggregation&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;Custom aggregation&lt;/strong&gt; lets you create your own groupings when the automatically computed modules do not match your team&amp;rsquo;s understanding of the application.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tenants and Roles</title>
      <link>https://a477574b.claude-generated-a3n.pages.dev/docs/about/tenants-and-roles/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://a477574b.claude-generated-a3n.pages.dev/docs/about/tenants-and-roles/</guid>
      <description>&lt;h2 id=&#34;tenants&#34;&gt;Tenants&lt;/h2&gt;&#xA;&lt;p&gt;A &lt;strong&gt;tenant&lt;/strong&gt; is an isolated workspace inside one CAST Imaging instance. Each tenant has its own set of applications, users, and settings. Users in one tenant cannot see the applications in another tenant.&lt;/p&gt;&#xA;&lt;p&gt;Tenants are useful when:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;You host applications for multiple clients on one server.&lt;/li&gt;&#xA;&lt;li&gt;You want to separate production and test environments.&lt;/li&gt;&#xA;&lt;li&gt;Different teams need isolated workspaces.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;A &lt;strong&gt;Super Admin&lt;/strong&gt; can create and manage tenants.&lt;/p&gt;&#xA;&lt;h2 id=&#34;roles&#34;&gt;Roles&lt;/h2&gt;&#xA;&lt;p&gt;A &lt;strong&gt;role&lt;/strong&gt; controls what a user can see and do inside a tenant. Every user must have at least one role before they can access application data.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
