Rationale Management in Software Engineering
Published 1 January 2006
Allen H. Dutoit, Barbara Paech, MistrÃk, Ivan, Raymond J. McCall
Citations283
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
This is a detailed summary of research on design rationale providing researchers in software engineering with an excellent overview of the subject.
Abstract
To the memory of Horst Rittel, who pioneered the field of design rationale.basic questions, such as What kinds of rationale can there be? ,
Keywords
Computer Science
University of Maribor digital library (University of Maribor)The Unified Modeling Language User Guide
5,529 Citations1999Grady Booch, James Rumbaugh +1 more
In The Unified Modeling Language User Guide, the original developers of the UML provide a tutorial to the core aspects of the language in a two-color format designed to facilitate learning.
Object Oriented Software Engineering: A Use Case Driven Approach
2,943 Citations1992Ivar Jacobson
This book discusses object-oriented software engineering as a process of change, management of object-oriented software engineering, and other object-oriented methods.
Sloan management reviewSUCCESSFUL KNOWLEDGE MANAGEMENT PROJECTS
2,853 Citations1998H Davenport Thomas, W Delong David +1 more
Human-Computer InteractionQuestions, Options, and Criteria: Elements of Design Space Analysis
784 Citations1991Allan MacLean, Richard M. Young +2 more
Managing Knowledge: Building Blocks for Success
689 Citations1999Gilbert Probst, Kai Romhardt +1 more
This book discusses knowledge management in the context of a knowledge base, with a focus on the building blocks of knowledge management.
Communications of the ACMFrom object-oriented to goal-oriented requirements analysis
580 Citations1999John Mylopoulos, Lawrence Chung +1 more
The Unified Modeling Language (UML)—see www.rational.
IEEE ExpertDesign rationale systems: understanding the issues
342 Citations1997J. Lee
Most current design rationale systems fail to consider practical concerns, such as cost-effective use and smooth integration, and the author identifies seven technical and business issues.
INFORMATION TECHNOLOGY AND KNOWLEDGE MANAGEMENT
321 Citations2018
This paper considers the deference between information and knowledge simply, but considers deeply the power or ability to convert from one to another, which is the ability to understand and learn things, or to think and understand things instinctively or automatically.
Human-Computer InteractionA Process-Oriented Approach to Design Rationale
297 Citations1991E. Jeffrey Conklin, K. C. Burgess Yakemovic
ComputerUsing the WinWin spiral model: a case study
286 Citations1998Barry Boehm, Alexander Egyed +4 more
Fifteen teams used the WinWin spiral model to prototype, plan, specify, and build multimedia applications for USC's Integrated Library System, extending the model's utility and cost-effectiveness in a second round of projects.
International Journal of Human-Computer StudiesArgumentation-based design rationale: what use at what cost?
279 Citations1994Simon Buckingham Shum, Ν. G. L. Hammond
This analysis of argumentation research sets an agenda for future work driven by a concern to support the designer in the whole process of externalizing and structuring DR, from initially ill-formed ideas to more rigorous, coherent argumentation.
International Conference on Software EngineeringRecording the reasons for design decisions
273 Citations1988Colin Potts, Glenn Bruns
Requirements EngineeringEnhancing a requirements baseline with scenarios
197 Citations1997Julio César Sampaio do Prado Leite, Gustavo Rossi +5 more
This proposal is framed by Leite’s work on a client-oriented requirements baseline, which aims to model the external requirements of a software system and its evolution, and adopts a broader view of scenarios.
Medical Entomology and ZoologyObject Oriented Software Engineering, Conquering Complex and Changing Systems
169 Citations2002Bernd Bruegge, Allen A. Dutoit
This book is a cohesive, class-tested presentation of object-oriented software engineering in a step-by-step format based on ten years of teaching and real-world software engineering experience and teaches practical experience in developing complex software appropriate for software engineering project courses, as well as industry R & D practitioners.
Making Argumentation Serve Design
141 Citations2020Gerhard Fischer, Andreas Lemke +2 more
Artificial intelligence for engineering design analysis and manufacturingIntegrating different perspectives on design rationale: Supporting the emergence of design rationale from design communication
122 Citations1997Frank Shipman, Raymond J. McCall
This work proposes an integrated approach to design rationale where design communication is captured and, over time, incrementally structured into argumentation and other formalisms to enable improved retrieval and use of this information.
An empirical evaluation of design rationale documents
96 Citations1996Laurent Karsenty
The results of an empirical evaluation of DR documents are presented, led to conclude that DR should be useful, at least for some designers who use it as a support to their reasoning, but not sufficient.
ScenIC: a strategy for inquiry-driven requirements determination
85 Citations2003Colin Potts
The paper presents a summary of the ScenIC strategy and guidelines and outlines method-specific reminders and resolution guidelines activated by the state of episodic or semantic memory.
Experience with SCRAM, a SCenario Requirements Analysis Method
78 Citations2002Alistair Sutcliffe, M. Ryan
The method worked well but there were problems in the use of design rationale and control of turn taking in RE sessions, and future improvements for the method are discussed.
Analyzing the Usability of a Design Rationale Notation
70 Citations2020Simon Buckingham Shum
This chapter examines how designers use a DR notation during design problem solving, and compares the account of the QOC–design relationship which emerges from these studies, with reports of other DR approaches in use.
Evaluating Opportunities for Design Capture
59 Citations2020Jonathan Grudin
Four kinds of software development environments are described and the opportunities and obstacles for using design rationale in each are outlined and the need for researchers to distinguish carefully between the requirements of science and those of engineering is considered.
Transatlantic project courses in a university environment
49 Citations2002Bernd Bruegge, Allen H. Dutoit +2 more
The experience with teaching three distributed software engineering project courses, where students were exposed first hand to distribution issues, encountering challenges introduced by different cultures, languages, standards and time zones, and facing them with tools such as groupware, videoconferencing, distributed repositories and travel.
Modelling Contextual Information about Scenarios
43 Citations1999Klaus Pohl, Peter Haumer
A comprehensive set of concepts needed to represent contextual usage knowledge of scenarios is defined, and it is proposed to relate contextual knowledge not only to the whole scenario, but also to the scenario components and single or sets of interactions between the system and the user of the system.
IEEE ExpertRepresenting and maintaining process knowledge for large-scale systems development
36 Citations1994B. Ramaesh, Vasant Dhar
Discusses how the Remap system uses a semiformal representation that supports the design and maintenance of large-scale software systems and enhances the understandability of designs and offers a mechanism for propagating change in design decisions into changes in design solutions.
Supporting long-term collaboration in software maintenance
21 Citations1993Robert Lougher, Tom Rodden
This paper presents a system which supports long-term collaboration in software maintenance by allowing maintenance rationale to be captured and shared by maintenance engineers.
Systems EngineeringComparing software system requirements negotiation patterns
21 Citations1999Alexander Egyed, Barry Boehm
It is found that the more realistic projects required more time to resolve conflicts and to identify options (alternatives) than the hypothetical ones, and that the 1996 projects created more artifacts although they exhibited less artifact interconnectivity, implying a more divide and conquer negotiation approach.
HCI Design Rationales as a Learning Resource
7 Citations2020Tom Carey, Diane McKerlie +1 more