EDBT 2026 Demo / reviewers in the wild / expert
Heiko Petzsch
dblp:50/1698
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 1984
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Programming languages and type systems · 91% Program verification · 9% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Programming languages and type systems › specification language
algebraic specification |
0.0 | 1 | 1984 | SLAN-4 - A Software Specification and Design Language · IEEE Trans. Software Eng. 1984 |
Programming languages and type systems
language design |
0.0 | 1 | 1984 | SLAN-4 - A Software Specification and Design Language · IEEE Trans. Software Eng. 1984 |
Programming languages and type systems
specification language |
0.0 | 1 | 1984 | SLAN-4 - A Software Specification and Design Language · IEEE Trans. Software Eng. 1984 |
Program verification
axiomatization |
0.0 | 1 | 1984 | SLAN-4 - A Software Specification and Design Language · IEEE Trans. Software Eng. 1984 |
Methods — techniques the papers use, named apart from their topics
axiomatic specification · 0.0algebraic specification · 0.0abstract data types · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1984 | SLAN-4 - A Software Specification and Design LanguageabstractSLAN-4 ("Software Language-4") was developed to meet the need for a formal tool for specifying and designing large software systems. It provides language constructs for algebraic and axiomatic specifications and also pseudocode constructs for the design step. A major design goal was to ease subsequent refinements of a (given) specification. The design can start with a very informal specification, which can be implemented later using lower level concepts. This paper gives an overview of the SLAN-4 syntax and semantics. It concentrates on the most important aspects of: abstract data types, algebraic specification of abstract data types, and axiomatic specification of modules. Because the pseudocode part of SLAN-4 consists mainly of control structures similar to those in modern high-level programming languages, this element of the language is not separately described. The paper includes an example of how to use SLAN-4, and also the experiences gained in using the language to formally specify a real-world software product of about 18 000 lines of code written in an IBM internal high-level language. Friedrich W. Beichter, Otthein Herzog, Heiko Petzsch |
IEEE Trans. Software Eng. | 3 |