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

Marc K. Zimmerman

dblp:62/3001 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2002
—ORCID · none

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
Empirical software engineering · 38% Requirements engineering and software design · 24% Programming languages and type systems · 19%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
code readability
0.012002
Investigating the readability of state-based formal requirements specification languages · ICSE 2002
Empirical software engineering
controlled experiment
0.012002
Investigating the readability of state-based formal requirements specification languages · ICSE 2002
Empirical software engineering › software engineering research methodology
empirical study
0.012002
Investigating the readability of state-based formal requirements specification languages · ICSE 2002
Programming languages and type systems › specification language
formal specification languages
0.012002
Investigating the readability of state-based formal requirements specification languages · ICSE 2002
Requirements engineering and software design
requirements specification
0.012002
Investigating the readability of state-based formal requirements specification languages · ICSE 2002
Requirements engineering and software design › formal specification
state-based specification
0.012002
Investigating the readability of state-based formal requirements specification languages · ICSE 2002

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

empirical study · 0.0controlled experiment · 0.0
YearPublicationVenuePosition
2002 Investigating the readability of state-based formal requirements specification languages
abstract
The readability of formal requirements specification languages is hypothesized as a limiting factor in the acceptance of formal methods by the industrial community. An empirical study was conducted to determine how various factors of state-based requirements specification language design affect readability using aerospace applications. Six factors were tested in all, including the representation of the overall state machine structure, the expression of triggering conditions, the use of macros, the use of internal broadcast events, the use of hierarchies, and transition perspective (going-to or coming-from). Subjects included computer scientists as well as aerospace engineers in an effort to determine whether background affects notational preferences. Because so little previous experimentation on this topic exists on which to build hypotheses, the study was designed as a preliminary exploration of what factors are most important with respect to readability. It can serve as a starting point for more thorough and carefully controlled experimentation in specification language readability.
Marc K. Zimmerman, Kristina Lundqvist, Nancy G. Leveson
ICSE1