Code Verification Strategy (Part of Code verification)

[MarcBehrens]

Preparation of grooming:

Verification of DAS2V code:

possible techniques to be groomed:

• Software-in-the-Loop
• � Model-based testing
• � Static analysis (e.g. coding guidelines)
• � Static analysis MISRE @idelatorre
• � Static analysis Syntax checking @idelatorre
• � Static analysis complexity @idelatorre
• � Formal methods (abstract interpretation, deductive verification, model checking)
• � Monitoring

strategy decision question:

• Which kind of verification to do on the C-Code To what extend is the code generator trustworthy to transfer the tests from the code level to the model level? (Part of Code Verification) #131
• Which level of test model to derive tests from (architecture level)?

check on code level:

• functionality (Is he functionality correltly transferred from the SysML- model?) @idelatorre
• generate automatic test cases for the code coming from the model (see strategic decision) @idelatorre
• Which tool can generate the test cases? @idelatorre
• coverage of test cases to the code @idelatorre
• robustness (absence of runtime errors)
• � performance
• � real time behaviour
• � dataflow
• � absence of deadlocks

subpart of #53

@jensgerlach
@BerndHekele