Rationale-based support for software maintenance

Rationale Management in Software Engineering

Volumn , Issue , 2006, Pages 273-296

  Burge, Janet E ^a   Brown, David C ^b  

^a MIAMI UNIVERSITY   (United States)

^b Worcester Polytechnic Institute   (United States)

Author keywords

design rationale; inference, argumentation; software maintenance

Indexed keywords

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

References (26)

1. Boehm B, Bose P (1994) A collaborative spiral software process model based on theory W. In: Proceedings of the International Conference on the Software Process, Reston, VA, pp. 59-68
2. Bose P (1995) A model for decision maintenance in the WinWin Collaboration Framework. In: Proceedings of the Conference on Knowledge-based Software Engineering, Boston, MA, pp. 105-113
3. Bratthall L, Johansson E, Regnell B (2000) Is a design rationale vital when predicting change impact? A controlled experiment on software architecture evolution.. In: Proceedings of the International Conference on Product Focused Software Process Improvement, Oulu, Finland, pp. 126-139
4. Burge JE (2005) Software Engineering Using design RATionale. Ph. D. thesis, Worcester Polytechnic Institute
5. Burge JE, Brown DC (2002) NFRs: fact or fiction? Technical Report WPI-CS-TR-02-01. Worcester Polytechnic Institute.
6. Burge JE, Brown DC (2004) An integrated approach for software design checking using rationale. In: Design Computing and Cognition'04, Gero J (ed). Kluwer Academic, Dordrecht, pp. 557-576
7. Canfora G, Casazza G, De Lucia A (2000) A Design rationale based environment for cooperative maintenance. International Journal of Software Engineering and Knowledge Engineering 10(5):627-645
8. Chapin N (2000) Software maintenance types - a fresh view. In: Proceedings of the International Conference on Software Maintenance, San Jose, CA, pp. 247-252
9. 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, Mahawah, NJ, pp. 293-428
10. Chung L, Nixon BA, Yu E, Mylopoulos J (2000) Non-Functional Requirements in Software Engineering. Kluwer Academic, Dordrecht
11. Dutoit AH, Paech B (2001) Rationale management in software engineering. In: Handbook of Software Engineering and Knowledge Engineering, Chang SK (ed). World Scientific, Singapore, pp. 787-816
12. Dutoit AH, McCall R, Mistrik I, Paech B (2006) Rationale management in software engineering: Concepts and Techniques. In: Rationale Management in Software Engineering, Dutoit AH, McCall R, Mistrik I, Paech B (eds.). Springer, Berlin Heidelberg New York, pp. 1-48
13. Filman RE (1998) Achieving ilities. In: Proceedings of the Workshop on Compositional Software Architectures, Monterey CA
14. Fischer G, Lemke A, McCall R, Morch A (1995) Making argumentation serve design. In: Design Rationale Concepts, Techniques, and Use, Moran T, Carroll J (eds.). Lawrence Erlbaum, Mahawah, NJ, pp. 267-294
15. Karsenty L (1996) An empirical evaluation of design rationale documents. In: Proceedings of the Conference on Human Factors in Computing Systems. Vancouver, BC, pp. 150-156
16. 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
17. Lee J (1991) Extending the Potts and Bruns model for recording design rationale. In: Proceedings of the International Conference on Software Engineering, Austin, TX, pp. 114-125
18. Lee J (1997) Design rationale systems: understanding the issues. IEEE Expert 12(3):78-85
19. Lehman M (2003) Software evolution cause or effect? Stevens Award Lecture: International Conference on Software Maintenance, Amsterdam
20. Lientz BP, Swanson EB (1988) Software Maintenance Management. Addison-Wesley, Reading, MA
21. Lougher R, Rodden T (1993) Group support for the recording and sharing of maintenance rationale. Software Engineering Journal 8(6):295-306
22. MacLean A, Young RM, Bellotti V, Moran TP (1995) Questions, Options and Criteria: Elements of Design Space Analysis In: Design Rationale Concepts, Techniques, and Use, Moran T, Carroll J (eds.). Lawrence Erlbaum, Mahawah NJ, pp. 201-251
23. Peña-Mora F, Sriram D, Logcher R (1995) Design rationale for computersupported conflict mitigation. ASCE Journal of Computing in Civil Engineering 9(1):57-72
24. Peña-Mora F, Vadhavkar S (1996) Augmenting design patterns with design rationale. Artificial Intelligence for Engineering Design, Analysis and Manufacturing 11(2):93-108
25. Potts C, Bruns G (1988) Recording the reasons for design decisions. In: Proceedings of the International Conference on Software Engineering. Singapore, pp. 418-427
26. Reiss SP (2002) Constraining software evolution. In: Proceedings of the International Conference on Software Maintenance, Montreal, Que. Canada, pp. 162-171