Automated Formal Static Analysis and Retrieval of Source Code - JKU

55
How the database is used. For each method and specification we build the unique key and
retrieve its content. For making persistent the information, we insert it in the database, where the
tables for callables and specifications have the structure from the tables 4.1 and 4.2.
CREATE TABLE IF NOT EXISTS callables (
key INTEGER PRIMARY KEY,
hit def key TEXT NOT NULL,
specification id INTEGER)
Table 4.1: Callables Table
CREATE TABLE IF NOT EXISTS specifications (
key INTEGER PRIMARY KEY,
hit def key TEXT NOT NULL)
Table 4.2: Specification Table
In the callables table there must exist a column where the id of the corresponding specification
has to be inserted, if the specification exists.
With the query:
SELECT callables.hit def key, specifications.hit def key FROM callables,
specifications WHERE callables.specification id = specifications.key,
one can obtain the name of the method and the corresponding specification that are further transformed
into Theorema syntax, syntax recognized by our verification conditions generator.
For full integration of the methods, the Java methods have to be transformed such that the
Return statement occurs on every branch. On the other side, we must add support for the while
statement in the program analysis with FwdVCG.