Download fulltext - DiVA Portal

Transcript
Kenyon Plug-In
The Kenyon plug-in serves as a wrapper for the KENYON tool, used to implement the
Retrieval and Analysis Process described in the section above. KENYON itself does not
provide a GUI and therefore the plug-in is providing one for the user in order to configure and run KENYON. The plug-in receives database metadata from the DB Converter
component, which are necessary for the GUI, e.g., available projects or status information of the database. When KENYON is invoked by the plug-in, it first initializes the
SCMInterface with metadata from the SCM repository in order to determine which versions have to be retrieved. It then starts to retrieve the source code files of the first version, storing them on the local file system (Source Code Retrieval). After that, KENYON
sequentially invokes the configured Fact Extractors and Metric Loaders to process the
retrieved source code. One Fact Extractor, the RecoderExtractor, has been implemented
for the thesis, whereas Metric Loaders have not been necessary. When the RecoderExtractor has finished, KENYON retrieves the next version and calls the RecoderExtractor again. This procedure continues until the last version has been retrieved and
processed.
RecoderExtractor
The RecoderExtractor realizes the remaining steps of the Retrieval and Analysis Process.
It first invokes RECODERCOMP in order to analyze the retrieved source code, generating
one or more graphs (Analysis). The graphs are then annotated with evolutional information which the RecoderExtractor receives as SCM metadata from the SCMInterface
(Graph Annotation). Finally, the graphs are passed to the internal graph storage of
VIZZANALYZER by passing them through the Kenyon plug-in and/or they are written to
the database, using the DB Converter (Graph Storage).
Summary
This section introduced the two new plug-ins Kenyon and Database that have to be
implemented for the thesis as well as the fact that they comprise a common GUI framework. The next two sections will cover the plug-in interface of VIZZANALYZER and the
GUI framework before the plug-ins themselves are described in the following.
Figure 4.3 shows a package diagram of the implemented components. It illustrates
the architecture on a high level. However, its main purpose is to list all implemented
class.
It is noteworthy that the implemented solution does not use the database storage
capabilities of KENYON (cf. Section 2.3) in order to write graphs to database, even
though it uses a similar approach. One reason for this decision is that it was unclear
whether the data structures used by KENYON for storing analysis results into a database
are flexible enough to accommodate the graphs of VIZZANALYZER without loss of
information. Another reason is that the DB Converter component must be independent
from the Kenyon plug-in, as the user should be able to manually write graphs to database (Requirement R18).
The solution does not allow for converting and storing the generated graphs automatically into other graph formats. However, this functionality could easily be added,
e.g., by utilizing KENYON’s Metric Loader mechanism and the conversion adapters provided by VIZZANALYZER.
33