Formal specification: a roadmap
By Axel van Lamsweerde. International Conference on Software Engineering, 2000
339 citations recorded by the source corpus.
Formal specifications have been a focus of software engineering research for many years and have been applied in a wide variety of settings. Their industrial use is still limited but has been steadily growing. After recalling the essence,role, usage, and pitfalls of formal specification, the paper reviews the main specification paradigms to date and discuss their evaluation criteria. It then provides a brief assessment of the current strengths and weaknesses of today’s formal specification technology. This provides a basis for formulating a number of requirements for formal specification to become a core software engineering activity in the future.
Subfields: Artificial Intelligence, Computational Theory and Mathematics, Software
View Paper: https://www.semanticscholar.org/paper/dd5ef1ea2ef20fa7534556299c6760b60b152a97
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
- Shin Yoo
- Alexander Pretschner
- Mark Harman
- Mark Utting
- Earl T. Barr
- Bruno Legeard
- Stefan Winkler
- Jens Henning von Pilgrim
In Computational Theory and Mathematics
- Shin Yoo
- Alexander Pretschner
- Mark Harman
- Mark Utting
- Earl T. Barr
- Bruno Legeard
- Stefan Winkler
- Jens Henning von Pilgrim
In Software
- Mark Harman
- Phil McMinn
- Shin Yoo
- Earl T. Barr
- Mark Utting
- Bruno Legeard
- Muzammil Shahbaz
- Alexander Pretschner
Citations in the corpus
- A taxonomy of model‐based testing approaches (2012, methodology): “It is convenient to group them into the following paradigms, adapted from van Lamsweerde [22].”
- A survey of traceability in requirements engineering and model-driven development (2010, background): “Van Lamsweerde [184] reports several applications of formal specifications relevant to traceability: refinement of specifications, derivation of test cases, and extraction of specifications from source code are transforming activities which can produce traceability links as by-products.”
- The Oracle Problem in Software Testing: A Survey (2015, background): “in the literature [101], [109], [182], [183].”