|Contacts||Henning Groenda (http://sdq.ipd.kit.edu/people/henning groenda/)|
|Is Stand-alone Analysis?||No|
This AddOn for Palladio allows the automated verification and validation of implementations and hardware-independent behavior specifications. It generates the tests based on the specification and compares the behavior of the specification and a running implementation.
Before running a validation, the Behaviour Validation Effort Estimation AddOn allows estimating the number of required test cases for the available coverage criteria. ByCounter in its eclipse version is used for the measurements. The PCM Coverage AddOn allows managing and presenting the covered elements of specifications.
The validation of a specification and implementation requires the following input:
- Accuracy Statements (.quality model files)
- Information on the Test-based Validation Quality (.testbased model files)
- Information on the mapping between specification and implmentation (.link model files)
- (If required) Converters between Palladio data types and implementation data types (Java classes). Default converters are provided for the data types shipped with Palladio as PrimitiveDataTypes and the corresponding Java types Boolean, Byte, Character, Double, Float, Integer, Long, Short, and String.
The validation results in the following output:
- Run Protocol (.results model file). The run protocol contains summarizing as well as detailed information on occured failues.
- (If requested by the Test-based Validation Quality) The achieved PCM Coverage information (.pcmcoverage mode file)
- Technical information on the instrumentation for the ByCounter measurements (.input model file)
- Technical information on the mapping between instrumented areas in ByCounter and Palladio elements (.link model file)
Technical Note: Depending on your Java VM and validated implementation, you might need to increase the upper bounds for memory restrictions in order to prevent memory exceptions. Common safe values are -XX:MaxPermSize=256m and -Xmx2048m. The settings can be made via the eclipse.ini or provided as VM arguments in a launch configuration.
The following examples can be checked out as eclipse projects via anonymous SVN access into an eclipse workspace. They provide run configurations based on jUnit test cases to start the comparisons as well as the result of previous validation runs.