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

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

Compare with Current View Page History

Version 1 Current »

The aim of this document is for the application SME to capture representative 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 (eBlue Print - Analysis Configuration and Execution).

 

Download the document template from here  Transactional_Code_Flows_appName.docx .  The template contains an example representative code flow, shown below, of what is required.   If an equivalent document already exists which shows what is required then provide that instead of creating a new document.  

 

Typical example where an application has the following technology interactions between entry and end points then one representative flow is required for each of the following:

  1. HTML /JSP (entry points)  -> Struts Action -> JAVA -> Hibernate -> Database (end points)
  2. HTML/JSP (entry points) -> Struts Action -> JAVA -> Spring Beans -> Hibernate -> Database (end points)
  3. HTML /JSP (entry points)  -> Struts Action -> JAVA  (end points) -> MQ 
  4. MQ -> MDB (entry points) -> JAVA -> Spring Beans -> Hibernate -> Database


The representative code flows must also include and show, where applicable, how the application :

  1. interacts with the application databases and external databases
  2. database is inserted/updated/deleted/queried by external applications or SQL Scripts 
  3. how the application interact with external applications (non-database)  e.g. sends and/or receive file feeds, ETL Tools, JMS, MQ, MDB, etc
  4. uses batch processes
  5. interacts with webservices (consumer/provider)
  6. uses configuration code and mapping of any Custom XML files  e.g. custom xml mapping files that define relationship such as stored procedure name with corresponding variable name within the code


 

What are Entry and End Points?

In order to compute the transaction Function Points, the transactions need to be identified from the entry points to the transaction end points. An application entry point identifies a resource that is an access point to an application such as Web service called by another application, webpages, batch files, JCL, COBOL Program, Interfaces, classes which receive external messages e.g. MQ. An application end point is a user interface end point or a service end point such as database tables, files operations, call to another system by websevice, classes which send external messages e.g. MQ, OutputStream.

 

The  template shows the following example :

  • No labels