Rationale Management in Software Engineering: Concepts and Techniques

[1]  Raymond McCall,et al.  Rationale Management in Software Engineering , 2006 .

[2]  Christopher G. Lasater,et al.  Design Patterns , 2008, Wiley Encyclopedia of Computer Science and Engineering.

[3]  Eric S. K. Yu,et al.  Dealing with change: An approach using non-functional requirements , 2005, Requirements Engineering.

[4]  Raymond McCall,et al.  Capture of Software Requirements and Rationale through Collaborative Software Development , 2005 .

[5]  Frank M. Shipman,et al.  Formality Considered Harmful: Experiences, Emerging Themes, and Directions on the Use of Formal Representations in Interactive Systems , 1999, Computer Supported Cooperative Work (CSCW).

[6]  Allen H. Dutoit,et al.  A Rationale-based Analysis Tool , 2004, IASSE.

[7]  Barbara Paech,et al.  Eliciting and Maintaining Knowledge for Requirements Evolution , 2003 .

[8]  Barbara Paech,et al.  Rationale-Based Use Case Specification , 2002, Requirements Engineering.

[9]  Frank M. Shipman,et al.  Spatial hypertext: an alternative to navigational and semantic links , 1999, CSUR.

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

[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]  René Bañares-Alcántara,et al.  Design support systems for process engineering—III. Design rationale as a requirement for effective support , 1997 .

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

[14]  Jesus M. de la Garza,et al.  Using Parameter Dependency Network to Represent Design Rationale , 1997 .

[15]  Feniosky Peña-Mora,et al.  Augmenting design patterns with design rationale , 1997, Artificial Intelligence for Engineering Design, Analysis and Manufacturing.

[16]  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.

[17]  Mark Klein.  An Exception Handling Approach to Enhancing Consistency, Completeness, and Correctness in Collaborative Requirements Capture , 1997 .

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

[19]  Frank Maurer,et al.  Integrating software process models and design rationales , 1996, Proceedings of the 11th Knowledge-Based Software Engineering Conference.

[20]  Frank M. Shipman,et al.  Supporting knowledge-base evolution with incremental formalization , 1994, CHI '94.

[21]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[22]  Janet L. Kolodner,et al.  Case-Based Reasoning , 1989, IJCAI 1989.

[23]  Frank M. Shipman,et al.  Supporting communication between designers with artifact-centered evolving information spaces , 1992, CSCW '92.

[24]  Vasant Dhar,et al.  Supporting Systems Development by Capturing Deliberations During Requirements Engineering , 1992, IEEE Trans. Software Eng..

[25]  Mark Klein,et al.  DRCS: An Integrated System for Capture of Designs and Their Rationale , 1992 .

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

[27]  P MoranThomas,et al.  Questions, options, and criteria , 1991 .

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

[29]  Mary Beth Rosson,et al.  Deliberated Evolution: Stalking the View Matcher in Design Space , 1996, Hum. Comput. Interact..

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

[31]  Frank M. Shipman,et al.  PHIDIAS: Integrating CAD Graphics into Dynamic Hypertext , 1992, ECHT.

[32]  Raymond McCall.  PHI : A Conceptual Foundation For Design Hypermedia , 1990 .

[33]  Raymond McCall,et al.  MIKROPLIS: a hypertext system for design , 1989 .

[34]  Raymond McCall,et al.  Design environments for constructive and argumentative design , 1989, CHI '89.

[35]  Thomas W. Malone,et al.  Object lens: a “spreadsheet” for cooperative work , 2018, TOIS.

[36]  Michael L. Begeman,et al.  gIBIS: a hypertext tool for exploratory policy discussion , 1988, CSCW '88.

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

[38]  Jonathan Grudin,et al.  Why CSCW Applications Fail: Problems in the Design and Evaluation of Organization of Organizational Interfaces. , 1988 .

[39]  D. Schoen,et al.  The Reflective Practitioner: How Professionals Think in Action , 1985 .

[40]  Raymond Joseph McCall.  On the structure and use of issue system in design , 1978 .

[41]  Max Jacobson,et al.  A Pattern Language: Towns, Buildings, Construction , 1981 .

[42]  H. Rittel,et al.  Dilemmas in a general theory of planning , 1973 .

[43]  S. Toulmin.  The uses of argument , 1960 .