Basically, it is foreseen to use the SAFacilitator in two different operating modes:

  1. configuration mode;
  2. execution mode.

Configuration Mode



The configuration mode is used at the beginning of a verification and validation project, when the user apllies iteratively the various Static Analyzers to the code base to fine tuning their invocation. Basically the user:

  1. starts from a compilation database generated externally
  2. derives from the compilation database the initial project file
  3. then continues editing the project file till it properly drives the selected Static Analyzers
  4. saves the properly set-up configuration information into "final/normalized" files.


In this working mode the errors messages produced by the Static Analyzers are shown directly in the SAFacilitator console; this way the user can check them and immediately correct the configuration as required.


Execution Mode



In execution mode the SAFacilitator uses the fine-tuned configuration files to drive the Static Analyzers and produces the Analyses Results. Note that the SAFacilitator can work also as console application - so this step can be integrated in the project's continuous integration (CI).