Rationale management in software engineering: Concepts and techniques

Rationale Management in Software Engineering

Volumn , Issue , 2006, Pages 1-48

  Dutoit, Allen H ^b   McCall, Raymond ^a   Mistrík, Ivan ^c   Paech, Barbara ^d  

^a UNIVERSITY OF COLORADO   (United States)

^b TECHNICAL UNIVERSITY OF MUNICH   (Germany)

^c Publication and Information Systems   (Germany)

^d UNIVERSITY OF HEIDELBERG   (Germany)

Author keywords

design rationale; rationale management; software architecting; software engineering; software requirements

Indexed keywords

ENGINEERING; INDUSTRIAL ENGINEERING;

DESIGN RATIONALE; FUTURE RESEARCH DIRECTIONS; SOFTWARE ARCHITECTING; SOFTWARE REQUIREMENTS; STATE OF THE ART; TOOL SUPPORT;

SOFTWARE ENGINEERING;

EID: 48649085868     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/978-3-540-30998-7_1     Document Type: Chapter

References (63)

1. Alexander C, Ishikawa S, Silverstein M, King I, Angel S, Jacobson M (1977) A Pattern Language: Towns, Buildings, Construction. Oxford University Press, Oxford
2. Banares-Alcantara R, King JMP (1997) Design support systems for process engineering - design rationale as requirement for effective support. Comput. Chem. Eng. 21(3):202-212
3. Boehm B, Egyed A, Kwan J, Port D, Shah A, Madachy R (1998) Using the WinWin spiral model: A case study. IEEE Computer 31(7):33-44
4. Burge J (1998) Design rationale. Technical Report, Worcester Polytechnic Institute, Computer Science Dept., In: http://www.cs.wpi.edu/Research/aidg/ DRRpt98.html (accessed: 02/17/2005).
5. Burge J, Brown DC (2004) An integrated approach for software design checking using rationale. In: Gero, J (ed) Design Computing and Cognition'04. Kluwer Academic Publishers, Netherlands, pp. 557-576
6. Carroll JM, Rosson MB (1996) Deliberated evolution: Stalking the view matcher in design space. In: Moran T P, Carroll J M (eds.) Design Rationale: Concepts, Techniques, and Use. Lawrence Erlbaum Associates, Mahwah, NJ, pp. 107-145
7. Churchman CW (1967) Wicked problems. Guest editorial, Manage. Sci., 14(4):141-142
8. Conklin J, Begeman M (1988) gIBIS: A hypertext tool for exploratory policy discussion. ACM Trans. Off. Inform. Syst. 4:303-331
9. Conklin J, Burgess-Yakemovic K C (1991) A process-oriented approach to design rationale. Hum.-Comp. Interact. 6:357-391
10. Chung L, Nixon BA, (1996) Dealing with change: An approach using non-functional requirements. Requir. Eng. J. 4:238-260
11. Dellen B, Kohler K, Maurer F (1996) Integrating software process models and design rationales. In: Proceedings of 11th Knowledge-Based Software Engineering Conference (KBSE'96) September 25-28, Syracuse, NY, pp. 84-93
12. Dutoit AH, Paech B (2000) Supporting evolution: Rationale in use case driven software development. In: Proceedings of the International Workshop on Requirements Engineering: Foundations of Software Quality (REFSQ'2000), Stockholm, June, pp. 99-112
13. Dutoit AH, Paech B (2001) Rationale management in software engineering. In: Chang SK (ed.) Handbook of Software Engineering and Knowledge Engineering. Vol. 1. rWorld Scientific, Singapore
14. Dutoit AH, Paech B (2002) Rationale-based use case specification. Requir. Eng. J. 1:3-9
15. Dutoit AH, Paech B (2003) Eliciting and maintaining knowledge for requirements evolution. In: Aurum A, Jeffery R, Wohlin C, Handzic M (eds.) Managing Software Engineering Knowledge. Springer, Berlin, pp. 135-156
16. Wolf T, Dutoit AH (2004) A rationale-based analysis tool. 13th International Conference on Intelligent and Adaptive Systems and Software Engineering, July 1-3, Nice, France
17. Fischer G, Lemke A, McCall R, Morch A (1996) Making argumentation serve design. In: Moran TP, Carroll JM (eds.) Design rationale: Concepts, techniques, and use. Lawrence Erlbaum, Mahwah, NJ, pp. 267-294
18. Fischer G, McCall R, Morch A (1989) Design environments for constructive and argumentative design. In: Proceedings of the SIGCHI Conference on Human Factors in Computing Systems: Wings for the Mind, March, ACM New York, pp. 269-275
19. Gamma E, Helm R, Johnson R, Vlissides J (1995) Design patterns. Addison-Wesley, Reading, MA
20. Ganeshan R, Garrett J Jr, Finger S (1994) A framework for representing design. Int. J. Design Stud. 1:59-84
21. de la Garza J, Alcantara P (1997) Using parameter dependency network to represent design rationale. J. Comput. Civil Eng., 2(2):102-112
22. Gotel O, Finkelstein A (1995) Contribution structures. In: Proceedings International Symposium on Requirements Engineering, IEEE, York, pp. 100-107
23. Gruber TR, Russell DM (1996) Generative design rationale: Beyond the record and play paradigm. In: Moran TP, Carroll JM (eds.) Design Rationale: Concepts, Techniques, and Use. Lawrence Erlbaum, Mahwah, NJ, pp. 323-349
24. Grudin J (1988) Why CSCW applications fail: problems in the design and evaluation of organization of organizational interfaces.. In: Proceedings of the 1988 ACM Conference on Computer-supported Cooperative Work, ACM, New York, pp. 85-93
25. Grudin, J (1996) Evaluating opportunities for design capture. In: Moran TP, Carroll JM (eds.) Design Rationale: Concepts, Techniques, and Use., Lawrence Erlbaum, Mahwah, NJ, pp. 453-470
26. King JMP, Banares-Alcantara R (1997) Extending the scope and use of design rationale. Artificial Intelligence for Engineering Design, Analysis and Manufacturing, 11(2):155-167
27. Klein M (1993) DRCS: An integrated system for capture of designs and their rationale. In Gero J (ed.) Artificial Intelligence in Design'92. Kluwer Academic Publishers, Boston, pp. 393-412
28. Klein M (1997) An exception handling approach to enhancing consistency, completeness and correctness in collaborative requirements capture.. Concurrent Engineering Research and Applications, 5(1):37-46
29. Kolodner J (1993) Case-based reasoning. Morgan Kaufmann, San Mateo, CA
30. Kunz W, Rittel H (1970) Issues as elements of information systems. Working Paper 131, Center for Urban and Regional Development, University of California, Berkeley.
31. Lai K, Malone T, Yu K (1989) Object lens: A 'Spreadsheet' for cooperative work. ACM Transaction on Office Information Systems, 6(4):332-353
32. Lee J (1990) SIBYL: a tool for managing group design rationale. In: Proceedings of the ACM Conference on Computer-supported Cooperative Work, ACM, New York, pp. 79-92
33. Lee J (1990) SIBYL: A qualitative decision management system. Artificial intelligence at MIT expanding frontiers. MIT Press, Cambridge, MA
34. Lee J (1991) Extending the Potts and Bruns model for recording design rationale. In: Proceedings of the 13th International Conference on Software Engineering (ICSE'13), IEEE Computer Society Press, Los Alamitos, CA, pp. 114-125
35. Lee J, Lai K (1996) What is design rationale? In: Moran TP, Carroll JM (eds.) Design Rationale: Concepts, Techniques, and Use. Lawrence Erlbaum Associates, Mahwah, NJ, pp. 21-52
36. Lee J (1997) Design rationale systems: Understanding the issues. AI in Design, IEEE Expert, May/June: 78-85
37. Lewis C, Rieman J, Bells B (1996) Problem-centered design for expressiveness. In: Moran TP, Carroll JM (eds.) Design Rationale, Concepts, Techniques and Use, Lawrence Erlbaum Associates, Mahwah, NJ, pp. 147-184
38. MacLean A, Young RM, Bellotti VME, Moran T (1996) Questions, Options and Criteria. In: Moran TP, Carroll JM (eds.) Design Rationale, Concepts, Techniques and Use, Lawrence Erlbaum Associates, Mahwah, NJ, pp. 53-106
39. McCall R (1989) MIKROPLIS: A hypertext system for design. Des. Stud. 10(4):228-239
40. McCall R (1991) PHI: a conceptual foundation for design hypermedia. Des. Stud. 1:30-41
41. McCall R (1979) On the structure and use of issue systems in design., Doctoral Dissertation 1978, University of California, Berkeley, University Microfilms
42. McCall R, Bennett P, d'Oronzio P, Ostwald J, Shipman F, Wallace N (1990) PHIDIAS: A PHI-based design environment integrating CAD graphics into dynamic hypertext. In: Rizk A, Streitz N, André J (eds.), Proceedings of the European Conference on hypertext (ECHT'90), INRIA, France, Cambridge University Press, New York, NY, pp. 152-165
43. McCall R, Bennett P, D'Oronzio P, Oswald J, Shipman FM III, Wallace N (1992) PHIDIAS: Integrating CAD graphics into dynamic hypertext. In: Streitz N, Rizk A, André J (eds.), Hypertext: Concepts, Systems and Applications, Cambridge University Press, New York, NY, pp. 152-165
44. McCall R, Mistrík I, Schuler W (1981) An integrated information and Communication system for problem solving. In: Proceedings of the Seventh International CODATA Conference, Kyoto, Japan, pp. 107-115
45. McCall R, Mistrík I (2005) Capture of software requirements and rationale through collaborative software development. In: Maté JL, Silva A (eds.) Requirements Engineering for Sociotechnical Systems. Information Science Publishing, pp. 303-317
46. Moran TP, Carroll JM (1996) Design Rationale: Concepts, Techniques and Use, Lawrence Erlbaum Associates, Mahwah, NJ
47. Myers KL, Zumel NB, Garcia PE (1999) Automated rapture of rationale for the detailed design process. In: Proceedings of the Eleventh National Conference on Innovative Applications of Artificial Intelligence (IAAI-99), AAAI Press, Menlo Park, CA, pp. 876-883
48. Pena-Mora F, Vadhavkar S (1996) Augmenting design patterns with design rationale. Artificial Intelligence for Engineering Design, Analysis and Manufacturing, 11:93-108
49. Potts C, Bruns G (1988) Recording the reasons for design decisions. In: Proceedings of the 10th International Conference on Software Engineering (ICSE'10). Los Alamitos, CA, pp. 418-427
50. Potts C, Takahashi K, Anton A (1994) Inquiry-based requirements analysis. IEEE Software, March,: 21-32
51. Ramesh B, Dhar V (1992) Supporting systems development by capturing deliberations during requirements engineering. IEEE Trans. Softw. Eng. 18(6):498-510
52. Reeves B, Shipman FM III (1992) Supporting communication between designers with artifact-centered evolving information spaces In: Proceedings of the 1992 ACM Conference on Computer-supported Cooperative work, November 1-4, Toronto, Ont., Canada, pp. 394-401
53. Rittel H (1985) personal communication
54. Rittel H, Weber M (1973) Dilemmas in a general theory of planning. Policy. Sci. 4:155-169
55. Rittel HWJ (1972) On the planning crisis: Systems analysis of the first and second generations. Bedriftsokonomen, Norway, 8:390-396
56. Schön D (1983) The reflective practitioner. How professionals think in action. Temple Smith, London
57. Shipman FM III, Marshall CC (1999) Formality considered harmful: Experiences, emerging themes, and directions on the use of formal representations in interactive systems.. Comput. Support. Cooperat. Work 8(4):333-352
58. Shipman FM III, McCall R (1994) Supporting knowledge-base evolution with incremental formalization. In: Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Boston, Massachusetts, US, pp. 285-291
59. Shipman FM III (1993) Supporting knowledge-base evolution with incremental formalization. PhD dissertation, Technical Report CU-CS-658-93, Department of Computer Science, University of Colorado, Boulder
60. Shipman FM III, McCall R (1997) Integrating different perspectives on design rationale: Supporting the emergence of design rationale from design communication.. Artif. Intell. Eng. Des., Anal., Manuf., 11(2):141-154
61. Shipman FM III, Marshall C (1999) Spatial hypertext: An alternative to navigational and semantic links. ACM Computing Surveys, ACM, New York, 31 (4es):14
62. Sutcliffe A, Ryan M (1998) Experience with SCRAM, a scenario requirements analysis method. In: Proceedings of the 3rd International Conference on Requirements Engineering, Colorado Springs, CO, pp. 164-173
63. Toulmin S (1958) The Uses of Argument. Cambridge University Press, UK