Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page
Demo Data from EDBT 2026 / reviewers in the wild / expert

Heather Alexander

dblp:21/5595 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1988
—ORCID · unresolved

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 first-author

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
Requirements engineering and software design · 67% Program verification · 33%

Topics — the 2 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Program verification
axiomatization		 0.011988
Comments on "Formal Specification of User Interfaces: A Comparison and Evaluation of Four Axiomatic Approaches" · IEEE Trans. Software Eng. 1988
Requirements engineering and software design
formal specification		 0.011988
Comments on "Formal Specification of User Interfaces: A Comparison and Evaluation of Four Axiomatic Approaches" · IEEE Trans. Software Eng. 1988

Methods — techniques the papers use, named apart from their topics

z notation · 0.0formal specification · 0.0
YearPublicationVenuePosition
1988 Comments on "Formal Specification of User Interfaces: A Comparison and Evaluation of Four Axiomatic Approaches"
abstract
A recent paper (see ibid., vol.11, no.8, p.671-88, Aug. 1985) compared several axiomatic methods of formal specification, one of which was Z. As a result of a comparison made with Z and a similar, but executable, specification language called Me too, it was pointed out that one of the Z specifications given was not correct. In this response, the erroneous function is described and some conclusions are drawn about the process of formal specification.>
Heather Alexander
 IEEE Trans. Software Eng.1