Design is, at its heart, a decision-making process. The decisions, alternative approaches considered, and the reasons behind the final choices are known as the Design Rationale (DR). The DR is usually not explicitly captured, at least not in an easily retrievable form. One way to reduce the effort in capturing rationale is to obtain the DR from unstructured documents and import it into a Rationale Management System (RMS) that supports incremental formalization. In this paper, we describe how this capability has been added to the ORCA system and how it is used to import rationale from existing design information sources.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Lee J, Lai KY (1996) What's in design rationale? In Moran T, Carroll J (eds) Design Rationale Concepts, Techniques, and Use, Lawrence Erlbaum Associates: 21–51
Conklin J, Burgess-Yakemovic K (1995) A process-oriented approach to design rationale. In Design rationale concepts, techniques, and use, Moran T, Carroll J (eds), Lawrence Erlbaum Associates: 293–428
Baker FT (1972) Chief programmer team management of production programming. IBM Systems Journal 11(1): 56–83
Helmick MT, Kiper JD, Burge J, Cross V, Gannod G (2007) Incorporating Wikis into software repository mining. In Proceedings of Wiki4SE- Wikis for Software Engineering Workshop, Montreal (Canada)
Burge JE, Brown DC (2004) An integrated approach for software design checking using rationale. In Design Computing and Cognition'04, Gero JS (ed) Kluwer Academic: 557–576
Burge JE, Cross V, Kiper J, Maynard-Zhang P, Cornford S (2006) Enhanced design checking involving constraints, collaboration, and assumptions. In Gero JS (ed) Design Computing and Cognition'06, Springer: 655–674
Shipman FM III, Marshall CC (1999) Formality considered harmful: Experiences, emerging themes, and directions on the use of formal representations in interactive systems. Computer-Supported Cooperative Work 8(3):333–352
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, United States: 285–291
Shipman FM, McCall RJ (1999) Supporting incremental formalization with the hyper-object substrate. ACM Trans. Inf. Syst. 17(2): 199–227
Shipman F, McCall R (1997) Integrating different perspectives on design rationale: Supporting the emergence of design rationale from design communication. Artificial Intelligence in Engineering Design, Analysis and Manufacturing 11(2): 141–154
Brandish MJ, Hague MJ, Taleb-Bendiab A (1996) M-LAP: A machine learning apprentice agent for computer supported design. In AID'96 Machine Learning in Design Workshop
Myers KL, Zumel NB, Garcia PE (1999) Automated capture of rationale for the detailed design process. In Proceedings of the Eleventh National Conference on Innovative Applications of Artificial Intelligence (IAAI-99), AAAI, Menlo Park, CA: 876–883
Richter H, Schuchhard P, Abowd G (1998) Automated capture and retrieval of architectural rationale. Georgia Tech Technical Report GIT-GVU-98–37
Schneider K (2006) Rationale as a by-product, In Rationale Management in Software Engineering, Dutoit A, McCall R, Mistrik I, Paech B (eds), Springer Verlag: 91–109
Garcia A, Howard H, Stefik M (1993) Active design documents: A new approach for supporting documentation in preliminary routine design. Stanford Univ., Tech. Report 82
Zaychik V, Regli WC(2003) Capturing communication and context in the software project lifecycle. Research in Engineering Design 14(2): 75–88
Dutoit A, McCall R, MistrÃk I, Paech B (2006) Rationale management in software engineering: Concepts and techniques. In Dutoit A, McCall R, MistrÃk I, Paech B (eds), Rationale Management in Software Engineering, Springer—Verlag: 1–48
Oberto R (2002) FAIR/DART Option #2. Advanced Projects Design Team. NASA Jet Propulsion Laboratory
Burge JE (2005) Software engineering using design rationale. Ph.D. thesis, Worcester Polytechnic Institute
Karsenty L(1996) An empirical evaluation of design rationale documents. In Proceedings of the Conference on Human Factors in Computing Systems, Vancouver, BC: 150–156
Grudin J (1996) Evaluating opportunities for design capture. In Moran T, Carroll J (eds), Design Rationale Concepts, Techniques, and Use, Lawrence Erlbaum Associates, Mahwah, NJ: 453–470
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2008 Springer Science+Business Media B.V
About this paper
Cite this paper
Burge, J.E., Kiper, J.D. (2008). Capturing Decisions and Rationale from Collaborative Design. In: Gero, J.S., Goel, A.K. (eds) Design Computing and Cognition '08. Springer, Dordrecht. https://doi.org/10.1007/978-1-4020-8728-8_12
Download citation
DOI: https://doi.org/10.1007/978-1-4020-8728-8_12
Publisher Name: Springer, Dordrecht
Print ISBN: 978-1-4020-8727-1
Online ISBN: 978-1-4020-8728-8
eBook Packages: Computer ScienceComputer Science (R0)