Search: onr:"swepub:oai:research.chalmers.se:a9c9ad61-03ff-45b4-8eb0-c193ae0deb71" >
Understanding forma...
Understanding formal specifications through good examples
-
- Gerdes, Alex, 1978 (author)
- Gothenburg University,Göteborgs universitet,Institutionen för data- och informationsteknik (GU),Department of Computer Science and Engineering (GU)
-
- Hughes, John, 1958 (author)
- Chalmers tekniska högskola,Chalmers University of Technology
-
- Smallbone, Nicholas, 1986 (author)
- Chalmers tekniska högskola,Chalmers University of Technology
-
show more...
-
- Hanenberg, Stefan (author)
- Universität Duisburg-Essen,University of Duisburg-Essen
-
- Ivarsson, Sebastian (author)
- Chalmers tekniska högskola,Chalmers University of Technology
-
- Wang, Meng, 1980 (author)
- University Of Kent
-
show less...
-
(creator_code:org_t)
- 2018-09-29
- 2018
- English.
-
In: Erlang 2018 - Proceedings of the 17th ACM SIGPLAN International Workshop on Erlang, co-located with ICFP 2018. - New York, NY, USA : ACM. ; , s. 13-24
- Related links:
-
https://research-inf...
-
show more...
-
https://doi.org/10.1...
-
https://research.cha...
-
https://research.cha...
-
https://gup.ub.gu.se...
-
show less...
Abstract
Subject headings
Close
- Formal specifications of software applications are hard to understand, even for domain experts. Because a formal specification is abstract, reading it does not immediately convey the expected behaviour of the software. Carefully chosen examples of the software’s behaviour, on the other hand, are concrete and easy to understand—but poorly-chosen examples are more confusing than helpful. In order to understand formal specifications, software developers need good examples. We have created a method that automatically derives a suite of good examples from a formal specification. Each example is judged by our method to illustrate one feature of the specification. The generated examples give users a good understanding of the behaviour of the software. We evaluated our method by measuring how well students understood an API when given different sets of examples; the students given our examples showed significantly better understanding.
Subject headings
- NATURVETENSKAP -- Data- och informationsvetenskap -- Annan data- och informationsvetenskap (hsv//swe)
- NATURAL SCIENCES -- Computer and Information Sciences -- Other Computer and Information Science (hsv//eng)
- NATURVETENSKAP -- Data- och informationsvetenskap -- Programvaruteknik (hsv//swe)
- NATURAL SCIENCES -- Computer and Information Sciences -- Software Engineering (hsv//eng)
- NATURVETENSKAP -- Data- och informationsvetenskap -- Datavetenskap (hsv//swe)
- NATURAL SCIENCES -- Computer and Information Sciences -- Computer Sciences (hsv//eng)
Keyword
- QuickCheck
- property-based testing
- examples
- Formal specification
- Formal specification
- QuickCheck
- examples
- property-based testing
Publication and Content Type
- kon (subject category)
- ref (subject category)
To the university's database