<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Onboarding Practices on Documentation - V2</title><link>https://doc.castsoftware.com/export-v2/fbp/supporting-information/onboarding-additional-information/onboarding-practices/</link><description>Recent content in Onboarding Practices on Documentation - V2</description><generator>Hugo</generator><language>en</language><atom:link href="https://doc.castsoftware.com/export-v2/fbp/supporting-information/onboarding-additional-information/onboarding-practices/index.xml" rel="self" type="application/rss+xml"/><item><title>Transaction Code Flow</title><link>https://doc.castsoftware.com/export-v2/fbp/supporting-information/onboarding-additional-information/onboarding-practices/transaction-code-flow/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://doc.castsoftware.com/export-v2/fbp/supporting-information/onboarding-additional-information/onboarding-practices/transaction-code-flow/</guid><description>&lt;p&gt;The aim of this document is for the application SME to capture &lt;strong&gt;representative&lt;/strong&gt; transactional code flows snippets between the entry and end points of the application. It is not intended to capture flows between all the individual instances of entry/end points (explained below)  but rather to capture a representative flow through each of the technologies depicted in the Architecture Context Diagram.   This document is used by the CAST Administrator during the analysis configuration workflow stage (&lt;a href="http://doc.castsoftware.com/display/DOC83/eBlue+Print+-+Analysis+Configuration+and+Execution"&gt;eBlue Print - Analysis Configuration and Execution&lt;/a&gt;).&lt;/p&gt;</description></item><item><title>Architecture Context Diagram</title><link>https://doc.castsoftware.com/export-v2/fbp/supporting-information/onboarding-additional-information/onboarding-practices/architecture-context-diagram/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://doc.castsoftware.com/export-v2/fbp/supporting-information/onboarding-additional-information/onboarding-practices/architecture-context-diagram/</guid><description>&lt;p&gt;The aim of this document is for the application SME to depict the logical high level architectural interaction between the various technologies of the application. It also identifies the application boundary, i.e. the scope of the application for which code will be delivered to CAST for analysis, and components which are deemed as external to the application.  This document is used by the CAST Administrator during the analysis configuration workflow stage (&lt;a href="https://doc-legacy.castsoftware.com/display/DOC83/Analysis+Configuration+and+Execution"&gt;Analysis Configuration and Execution&lt;/a&gt;).&lt;/p&gt;</description></item><item><title>Imaging Quality Checks</title><link>https://doc.castsoftware.com/export-v2/fbp/supporting-information/onboarding-additional-information/onboarding-practices/imaging-quality-checks/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://doc.castsoftware.com/export-v2/fbp/supporting-information/onboarding-additional-information/onboarding-practices/imaging-quality-checks/</guid><description>&lt;p&gt;Additional checks should be made in Imaging, just after an initial load to control if the analysis is correct or. This should be used with Imaging. Please refer to the following &lt;a href="https://github.com/CAST-Extend/imagingeligibilityreport/wiki/Documentation"&gt;link&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/CAST-Extend/imagingeligibilityreport/wiki/Documentation"&gt;Imaging Eligibility Report&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>