Tool Support
The "Examiner" (part of the "SPARK Toolset") performs two kinds of static analysis. The first, made up of language conformance checks and flow analysis, checks that the program is "well-formed" and is consistent with the design information included in its annotations. This stage can be incorporated into the coding phase of the development process. After these checks the source is known to be free from erroneous behaviour and free from conditional and unconditional data flow errors (e.g., use of uninitialised data) on a system-wide basis (including abstract state in package bodies).
The second, optional, analysis is verification: showing by proof that the SPARK program has certain specified properties. The most straightforward is a proof that the code is exception free; this adds the Constraint_Error exception to the list of possible errors eliminated by SPARK. This proof can also be used to demonstrate, unequivocally, that the code maintains important safety or security properties. It can also be used to show conformance with some suitable specification.
Read more about this topic: SPARK (programming Language)
Famous quotes containing the words tool and/or support:
“And if thou wilt make me an altar of stone, thou shalt not build it of hewn stone: for if thou lift up thy tool upon it, thou hast polluted it.”
—Bible: Hebrew Exodus 20:25.
“Many people now believe that if fathers are more involved in raising children than they were, children and sons in particular will learn that men can be warm and supportive of others as well as be high achievers. Thus, fathers’ involvement may be beneficial not because it will help support traditional male roles, but because it will help break them down.”
—Joseph H. Pleck (20th century)