Section summary

This section of the cookbook describes how to measure the Application and works through the four main steps:

• Configuring aspects required to provide "quality" information on the source code:
  
  • Architecture Models
  • User Input Security
  • Assessment Model
• Defining a module strategy - i.e. creating User Defined Modules if necessary
• Configuring aspects required to provide "Function Point" information on the source code
• Snapshot generation and validation

The steps listed below are the recommended steps and how to perform them

• Quality Configuration
  • Architecture Model configuration
  • Enable User Input Security checks
  • Fine tuning the Assessment Model
• Define a Module strategy (User Defined Modules)
• Transaction management
  • Function Points - background information
  • Transaction configuration
  • Transaction review
  • Transaction calibration
  • Transactional function completeness
• Snapshot generation and validation

Expected outputs

At the conclusion of this section, it would be expected that:

• Any configuration necessary for a "quality" analysis scenario is completed
• A Module strategy has been defined if necessary
• Any configuration necessary for a "Function Point" analysis scenario is completed
• Snapshot is generated and validated through CAST dashboards