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

Michael Waterman

dblp:34/9298 · DBLP profile ↗
← Back
3ranked-venue papers
2as first author
0since 2021 · last 2015
—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-authorSystems, architecture and hardware · 1Security and privacy · 1

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

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

TopicWeightPapersLastEvidence papers
Empirical software engineering
agile software development
0.212015
How Much Up-Front? A Grounded theory of Agile Architecture · ICSE (1) 2015
Empirical software engineering › qualitative research
grounded theory
0.212015
How Much Up-Front? A Grounded theory of Agile Architecture · ICSE (1) 2015
Requirements engineering and software design
software architecture
0.212015
How Much Up-Front? A Grounded theory of Agile Architecture · ICSE (1) 2015

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

grounded theory · 0.2
YearPublicationVenuePosition
2015 How Much Up-Front? A Grounded theory of Agile Architecture
abstract
The tension between software architecture and agility is not well understood by agile practitioners or researchers. If an agile software team spends too little time designing architecture up-front then the team faces increased risk and higher chance of failure, if the team spends too much time the delivery of value to the customer is delayed, and responding to change can become extremely difficult. This paper presents a grounded theory of agile architecture that describes how agile software teams answer the question of how much upfront architecture design effort is enough. This theory, based on grounded theory research involving 44 participants, presents six forces that affect the team's context and five strategies that teams use to help them determine how much effort they should put into up-front design.
Michael Waterman, James Noble 0001, George Allan
ICSE (1)1
2013 The Effect of Complexity and Value on Architecture Planning in Agile Software Development
Michael Waterman, James Noble 0001, George Allan
XP1
2010 Application of a fault injection based dependability assessment process to a commercial safety critical nuclear reactor protection system
abstract
Existing nuclear power generation facilities are currently seeking to replace obsolete analog Instrumentation and Control (I&C) systems with contemporary digital and processor based systems. However, as new technology is introduced into existing and new plants, it becomes vital to assess the impact of that technology on plant safety. From a regulatory point of view, the introduction or consideration of new digital I&C systems into nuclear power plants raises concerns regarding the possibility that the fielding of these I&C systems may introduce unknown or unanticipated failure modes. In this paper, we present a fault injection based safety assessment methodology that was applied to a commercial safety grade digital Reactor Protection System. Approximately 10,000 fault injections were applied to the system. This paper presents a overview of the research effort, lessons learned, and the results of the endeavor.
Carl R. Elks, Michael Reynolds, Nishant George, Marko Miklo, Scott Bingham, Ronald D. Williams, Barry W. Johnson, Michael Waterman, Jeanne Dion
DSN8