Competition Contributions consist of a contribution paper that describes the competition contribution, including an outline of the concepts, technology, libraries, and tool infrastructure used in the competition, installation instructions, a specification of the version and parameters to be used for the competition, as well as a link to the executable tool (= competition candidate). Contribution papers have a maximum of 3 pages in LNCS style.
Submit your contribution via the SV-COMP'13 submission site of Easychair.
The competition contribution paper should be structured as follows:
Title, Authors, and AbstractThe format is defined in the usual LNCS style. In addition, one author has to be indicated as corresponding author (in case clarification is necessary). It is a good idea to mention the name of the tool and/or technique (or a combination thereof) in the title.
1. Verification ApproachA short overview of the theory that the tool is based on. Description of the abstract domains and algorithms that are used. Reference to the concept papers that describe the technical details.
2. Software Architecture
- Libraries and external tools that the verification tool uses (e.g., parser frontend, SAT solver)
- Software structure and architecture (e.g., components that are used in the competition)
- Implementation technology (e.g., programming language)
3. Discussion of Strengths and Weaknesses of the ApproachEvaluation of the results for the benchmark categories, where was the checker successful, where not, why?
4. Tool Setup and Configuration
- Download instructions (a public web page from which the tool can be downloaded) including a reference to a precise version of the tool (do not refer to ``the latest version'' or such, because that is not stable and reproducible)
- Installation instructions (including references to external public components that need to be installed, the dedicated competition machine runs Ubuntu 12.04 with an x86_64 GNU/Linux kernel and standard development packages, anything beyond that must be provided)
- Configuration definition (there is one global set of parameters for all categories of the benchmark set, a full definition of the parameter set must be provided); check the rules page under Parameters for more details
- If the verification result reported by the tool does not obviously match the defined verification result (cf. rules and definitions) then a mapping needs to be defined in the paper.
5. Software Project and Contributors
- Contact info (web page of the project, people involved in the project)
- Information about the software project, licensing, development model, institution that hosts the software project, acknowledgement of contributors
ReferencesBibliographic references to more in depth papers about the approaches used in the tool.