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

Bill Mitchell

dblp:34/2678 · DBLP profile ↗
← Back
5ranked-venue papers
4as first author
0since 2021 · last 2008
—ORCID · none

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

Software engineering, systems software and programming languages · 4 · 3 first-authorTheory of computation · 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
3 papers
Requirements engineering and software design · 94% Programming languages and type systems · 6%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › requirements modeling
scenario-based requirements
0.112005
Detecting and resolving semantic pathologies in UML sequence diagrams · ESEC/SIGSOFT FSE 2005
Requirements engineering and software design › specification
scenario-based specification
0.112005
Resolving Race Conditions in Asynchronous Partial Order Scenarios · IEEE Trans. Software Eng. 2005
Requirements engineering and software design › software design notation
UML sequence diagrams
0.112005
Detecting and resolving semantic pathologies in UML sequence diagrams · ESEC/SIGSOFT FSE 2005
Programming languages and type systems › language semantics
behavioral semantics
0.012005
Resolving Race Conditions in Asynchronous Partial Order Scenarios · IEEE Trans. Software Eng. 2005
Requirements engineering and software design
software architecture
0.012005
Detecting and resolving semantic pathologies in UML sequence diagrams · ESEC/SIGSOFT FSE 2005

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

partial order theory · 0.2process algebra · 0.1UML/MSC scenarios · 0.1UML profiling · 0.1
YearPublicationVenuePosition
2008 Characterizing Communication Channel Deadlocks in Sequence Diagrams
abstract
UML sequence diagrams (SDs) are a mainstay of requirements specifications for communication protocols. Mauw and Reniers' algebraic (MRA) semantics formally specifies a behavior for these SDs that guarantees deadlock-free processes. Practitioners commonly use communication semantics that differ from MRA, which may result in deadlocks, for example, FIFO, token ring, etc. We define a process algebra that is an extension of the MRA semantics for regular SDs. Our algebra can describe several commonly used communication semantics. Regular SDs are constructed from concurrent message flows via iteration, branching, and sequential composition. Their behavior is defined in terms of a set of partial orders on the events in the SD. Such partial orders are known as causal orders. We define partial order theoretic properties of a causal order that are particular kinds of race condition. We prove that any of the common communication semantics that we list either guarantees deadlock-free SDs or can result in a deadlock if and only if a causal order of an SD contains one of these types of race condition. This describes a complete classification of deadlocks as specific types of race condition.
Bill Mitchell
IEEE Trans. Software Eng.1
2007 Lazy buffer semantics for partial order scenarios
Bill Mitchell
Autom. Softw. Eng.1
2005 Detecting and resolving semantic pathologies in UML sequence diagrams
abstract
Scenario based requirements specifications are the industry norm for defining communicating systems. These scenarios are often captured in the form of UML/MSC sequence diagrams. Errors are often introduced at this stage of the development process, which are costly to resolve if they are not detected early. This paper is concerned with the automatic detection and resolution of semantic errors that can occur in such scenarios.The paper discusses a semantic interpretation of scenario-based requirements and various types of defects (or pathologies) that can be detected. The paper defines the semantics and defects within a partial order theoretic framework. We introduce a UML 2.0 profile that captures various domain specific communication semantics, which can be used to determine the relevance of detected pathologies when different underlying implementation assumptions are made. The paper also discusses how to automatically resolve pathologies by using this profile to adapt the communication architecture in the requirements model.
Paul Baker, Paul Bristow, Clive Jervis, David J. King, Robert Thomson 0002, Bill Mitchell, Simon Burton 0001
ESEC/SIGSOFT FSE6
2005 Resolving Race Conditions in Asynchronous Partial Order Scenarios
abstract
Scenario-based requirements specifications are the industry norm for defining communication protocols. However, such scenarios often contain race conditions. A race condition occurs when events are specified to occur in a particular order, but in practice, this order cannot be guaranteed. The paper considers UML/MSC scenarios that can be described with standard partial order theoretic asynchronous behavioral semantics. We define these to be partial order scenarios. The paper proves there is a unique minimal generalization of a partial order scenario that is race free. The paper also proves there is a unique minimal race free refinement of the behavioral semantics of a partial order scenario. Unlike the generalization, the refinement cannot be realized in the form of a partial order scenario, although it can always be embedded in one. The paper, also proves the results can be generalized to a subclass of iterative scenarios.
Bill Mitchell
IEEE Trans. Software Eng.1
2004 Inherent Causal Orderings of Partial Order Scenarios
Bill Mitchell
ICTAC1