Michael Breen

dblp:65/4044 · DBLP profile ↗
← Back
2ranked-venue papers
2as first author
0since 2021 · last 2005
—ORCID · none

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

Software engineering, systems software and programming languages · 2 · 2 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%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Embedded and real-time systems · 100%

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

TopicWeightPapersLastEvidence papers
Program verification › formal modeling
finite state machine specification
0.012004
Statestep: A Tool for Systematic, Incremental Specification · ICSE 2004
Requirements engineering and software design
software design tools
0.012004
Statestep: A Tool for Systematic, Incremental Specification · ICSE 2004
Requirements engineering and software design › specification
software specification
0.012004
Statestep: A Tool for Systematic, Incremental Specification · ICSE 2004

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

tabular notation · 0.1finite-state machine modeling · 0.0finite state machine modeling · 0.0
YearPublicationVenuePosition
2005 Experience of using a lightweight formal specification method for a commercial embedded system product line
Michael Breen
Requir. Eng.1
2004 Statestep: A Tool for Systematic, Incremental Specification
abstract
Statestep is an interactive tool for editing and checking specifications based on the finite state machine (FSM) model. The tabular notation supported is a novel yet simple one, first developed to specify the external behaviour of a series of audio compact disc recorders. The technique helps to describe system behaviour in a systematic manner, intended principally to ensure that no unusual scenarios, or corner cases, are overlooked at the specification stage. The notation is readily understandable and can reduce or eliminate the need for internal events or other structuring primitives. It supports a naturally incremental approach to specification and seems especially suited to dealing with the kind of complexity that can arise in embedded user interfaces.
Michael Breen
ICSE1