Rationale Management in Software Engineering

This is a detailed summary of research on design rationale providing researchers in software engineering with an excellent overview of the subject. Professional software engineers will find many examples, resources and incentives to enhance their ability to make decisions during all phases of the software lifecycle. Software engineering is still primarily a human-based activity and rationale management is concerned with making design and development decisions explicit to all stakeholders involved.

[1]  Alistair Cockburn,et al.  Goals and Use Cases , 1997, J. Object Oriented Program..

[2]  Barry Boehm,et al.  The WinWin Approach: Using a Requirements Negotiation Tool for Rationale Capture and Use , 2006 .

[3]  Laurent Karsenty,et al.  An empirical evaluation of design rationale documents , 1996, CHI.

[4]  Lorne Olfman,et al.  Organizational Memory , 1998, Proceedings of the Thirty-First Hawaii International Conference on System Sciences.

[5]  H. D. Thomas,et al.  SUCCESSFUL KNOWLEDGE MANAGEMENT PROJECTS , 1998 .

[6]  Vasant Dhar,et al.  Representing and maintaining process knowledge for large-scale systems development , 1994, IEEE Expert.

[7]  Tom Rodden,et al.  Supporting long-term collaboration in software maintenance , 1993, COCS '93.

[8]  Colin Potts,et al.  Recording the reasons for design decisions , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[9]  Björn Regnell,et al.  Is a Design Rationale Vital when Predicting Change Impact? A Controlled Experiment on Software Architecture Evolution , 2000, PROFES.

[10]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

[11]  Alistair G. Sutcliffe,et al.  Experience with SCRAM, a SCenario Requirements Analysis Method , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[12]  Bernd Brügge,et al.  Transatlantic project courses in a university environment , 2000, Proceedings Seventh Asia-Pacific Software Engeering Conference. APSEC 2000.

[13]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[14]  Michael Pidd,et al.  A Hybrid Approach to Upstream Requirements: IBIS and Cognitive Mapping , 2006 .

[15]  Ralf Kneuper,et al.  Supporting Software Processes Using Knowledge Management , 2001 .

[16]  Jintae Lee,et al.  Design Rationale Systems: Understanding the Issues , 1997, IEEE Expert.

[17]  Deborah Richards,et al.  Capturing and Reusing Rationale Associated with Requirements Engineering Process Improvement: A Case Study , 2006 .

[18]  Tom Carey,et al.  HCI Design Rationales as a Learning Resource , 1996 .

[19]  Simon Buckingham Shum,et al.  Analyzing the Usability of a Design Rationale Notation , 1996 .

[20]  Jintae Lee,et al.  Extending the Potts and Bruns model for recording design rationale , 1991, [1991 Proceedings] 13th International Conference on Software Engineering.

[21]  Gilbert Probst,et al.  Managing Knowledge: Building Blocks for Success , 1999 .

[22]  Barry Boehm,et al.  Comparing software system requirements negotiation patterns , 1999 .

[23]  Jens Knodel,et al.  The Role of Rationale in the Design of Product Line Architectures – A Case Study from Industry , 2006 .

[24]  Michael E. Atwood,et al.  Effective Design Rationale: Understanding the Barriers , 2006 .

[25]  E. Jeffrey Conklin,et al.  A process-oriented approach to design rationale , 1991 .

[26]  Jos Nijhuis,et al.  Design Decisions: The Bridge between Rationale and Architecture , 2006 .

[27]  Klaus Pohl,et al.  Modelling Contextual Information about Scenarios , 1999 .

[28]  Andrew Dillon,et al.  Design rationale: Concepts, techniques, and use , 1997 .

[29]  Remo Pareschi,et al.  Information Technology for Knowledge Management , 1998, Springer Berlin Heidelberg.

[30]  Eric Barboni,et al.  From DREAM to Reality: Specificities of Interactive Systems Development With Respect To Rationale Management , 2006 .

[31]  Raymond McCall,et al.  Making Argumentation Serve Design , 1996, Hum. Comput. Interact..

[32]  Alistair G. Sutcliffe,et al.  Requirements rationales: integrating approaches to requirement analysis , 1995, Symposium on Designing Interactive Systems.

[33]  Frank M. Shipman,et al.  Integrating different perspectives on design rationale: Supporting the emergence of design rationale from design communication , 1997, Artificial Intelligence for Engineering Design, Analysis and Manufacturing.

[34]  David C. Brown,et al.  Rationale-Based Support for Software Maintenance , 2006 .

[35]  Barry W. Boehm,et al.  Using the WinWin Spiral Model: A Case Study , 1998, Computer.

[36]  Nick Hammond,et al.  Argumentation-based design rationale: what use at what cost? , 1994, Int. J. Hum. Comput. Stud..

[37]  Gustavo Rossi,et al.  Enhancing a requirements baseline with scenarios , 1997, Requirements Engineering.

[38]  Patrick Henry Winston,et al.  Artificial intelligence at MIT: expanding frontiers , 1991 .

[39]  Bernd Bruegge,et al.  Object Oriented Software Engineering, Conquering Complex and Changing Systems , 2002 .

[40]  Thomas P. Moran,et al.  Questions, Options, and Criteria: Elements of Design Space Analysis , 1991, Hum. Comput. Interact..

[41]  Jonathan Grudin,et al.  Evaluating Opportunities for Design Capture , 1996 .

[42]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[43]  Colin Potts,et al.  ScenIC: a strategy for inquiry-driven requirements determination , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[44]  Kuntz Werner,et al.  Issues as Elements of Information Systems , 1970 .

[45]  John Mylopoulos,et al.  From object-oriented to goal-oriented requirements analysis , 1999, CACM.