Software Engineering Using RATionale

Journal of Systems and Software

Volumn 81, Issue 3, 2008, Pages 395-413

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

^a MIAMI UNIVERSITY   (United States)

^b Worcester Polytechnic Institute   (United States)

Author keywords

Assumptions; Inference; Rationale; Requirements; Software maintenance

Indexed keywords

COMPUTER SOFTWARE MAINTENANCE; DECISION MAKING; INFORMATION USE; REQUIREMENTS ENGINEERING;

INFERENCE; RATIONALE SYSTEMS;

SOFTWARE ENGINEERING;

EID: 43049125855     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.jss.2007.05.004     Document Type: Article

References (54)

1. In: Aurum A., Jeffrey R., Wohlin C., and Handizic M. (Eds). Managing Software Engineering Knowledge (2003), Springer
2. ASME, 2005. Responses to "Question of the month, December 2004", Mechanical Engineering Magazine, ASME, January, p. 10.
3. Basili V., Caldiera G., and Rombach G. The goal question metric approach. In: Marciniak J. (Ed). Encyclopedia of Software Engineering (1994), Wiley 528-532
4. Bennett, K.H., Rajlich, V.T., 2000. Software maintenance and evolution: a roadmap. In: Proceedings of the Conference on the Future of Software Engineering, Limerick, Ireland, pp. 73-87.
5. Boehm, B., Bose, P., 1994. A collaborative spiral software process model based on theory W. In: Proceedings of the Third International Conference on the Software Process, Reston, VA, pp. 59-68.
6. Bose, P., 1995. A model for decision maintenance in the WinWin collaboration framework. In: Proceedings of the Conference on Knowledge Based Software Engineering (KBSE'95), Boston, MA, pp. 105-113.
7. Bratthall, L., Johansson, E., Regnel, 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.
8. Brown D.C. Design. In: Shapiro S. (Ed). Encyclopedia of Artificial Intelligence vol. 1 (1992), Wiley, New York 331-339
9. Brown, D.C., Birmingham, W.P. (Eds.), 1997. Special double issue on "AI in Design", IEEE Expert: Intelligent Systems & their Applications, March/April, May/June.
10. Bruegge B., and Dutoit A. Object-Oriented Software Engineering: Conquering Complex and Changing Systems (2000), Prentice Hall
11. Buckingham Shumm S.J., Selvin A.M., Sierhuis M., Conklin J., Haley C.B., and Nuseibeh B. Hypermedia support for argumentation-based rationale: 15 years on from gIBIS and QOC. In: Dutoit A., McCall R., Mistrik I., and Paech B. (Eds). Rationale Management in Software Engineering (2006), Springer-Verlag, Berlin 111-132
12. Burge, J., 2005. Software Engineering Using RATionale, Ph.D. Thesis, Worcester Polytechnic Institute, Worcester, Massachusetts.
13. Burge, J., Brown, D.C., 2000. Inferencing over design rationale. In: Gero, J.S. (Ed.), Proceedings of the Conference on Artificial Intelligence in Design '00, Worcester, MA, pp. 611-629.
14. Burge J., and Brown D.C. An integrated approach for software design checking using rationale. In: Gero J. (Ed). Proceedings of the Conference on Design Computing and Cognition'04 (2004), Kluwer Academic Publishers, Netherlands 557-576
15. Burge J., and Brown D.C. Rationale-based support for software maintenance. In: Dutoit A., McCall R., Mistrik I., and Paech B. (Eds). Rationale Management in Software Engineering (2006), Springer-Verlag, Berlin 273-296
16. Canfora G., Casazza G., and De Lucia A. A design rationale based environment for cooperative maintenance. International Journal of Software Engineering and Knowledge Engineering 10 5 (2000) 627-645
17. Charette R., Adams K., and White M. Managing risk in software maintenance. IEEE Software 14 3 (1997) 43-50
18. Chung L., Nixon B.A., Yu E., and Mylopoulos J. Non-Functional Requirements in Software Engineering (2000), Kluwer Academic Publishers
19. CMU, 2002. Quality measures taxonomy, .
20. Conklin J., and Burgess-Yakemovic K. A process-oriented approach to design rationale. In: Moran T., and Carroll J. (Eds). Design Rationale Concepts, Techniques, and Use (1995), Lawrence Erlbaum Associates, Mahwah, NJ 293-428
21. Dellen B., Kohler K., and Maurer F. Integrating software process models and design rationals. Proceedings of the Conference on Knowledge-based Software Engineering (1996), IEEE Computer Society Press, Syracuse, NY 84-93
22. In: Dutoit A., McCall R., Mistrik I., and Paech B. (Eds). Rationale Management in Software Engineering (2006), Springer-Verlag, Berlin
23. Dutoit A., and Paech B. Rationale management in software engineering. In: Chang S.K. (Ed). Handbook of Software Engineering and Knowledge Engineering (2001), World Scientific Publishing 787-816
24. Edwards J.S. Managing engineers and their knowledge. In: Aurum A., Jeffery R., Wohlin C., and Handzic M. (Eds). Managing Software Engineering Knowledge (2003), Springer 5-27
25. Falessi, D., Cantone, G., Becker, M., 2006. Document design decision rationale to improve individual and team design decision making: an experimental evaluation. In: Proceedings of the 2006 ACM/III International Symposium on Empirical Software Engineering, Rio de Janeiro, Brazil, pp. 134-143.
26. Filman, R.E., 1998. Achieving ilities. In: Proceedings of the Workshop on Compositional Software Architectures, Monterey, California.
27. Garcia, A., Howard, H., Stefik, M., 1993. Active design documents: a new approach for supporting documentation in preliminary routine design. Technical Report 82, Stanford University Center for Integrated Facility Engineering, Stanford, CA.
28. Ishino Y., and Jin Y. An information value based approach to design procedure capture. Advanced Engineering Informatics 20 (2006) 89-107
29. Jiro K. KJ Method: A Scientific Approach to Problem Solving (2000), Kawakita Research Institute, Tokyo
30. Jung H., Kim S., and Chung C. Measuring software product quality: a survey of ISO/IEC 9126. IEEE Software 21 5 (2004) 88-92
31. 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.
32. Klein, M., 1997. An exception handling approach to enhancing consistency, completeness and correctness in collaborative requirements capture. Concurrent Engineering Research and Applications, March, pp. 37-46.
33. Ko, A.J., Aung, H., Myers, B.A., 2005. Eliciting design requirements for maintenance-oriented IDEs: a detailed study of corrective and perfective maintenance tasks. In: Proceedings of the 27th International Conference on Software Engineering, pp. 126-135.
34. Kunz, W., Rittel, H., 1970. Issues as elements of information systems. Working Paper 131, Center for Urban and Regional Development, University of California, Berkeley.
35. Lee, J., 1991. Extending the Potts and Bruns model for recording design rationale. In: Proceedings of the 13th International Conference on Software Engineering, Austin, TX, pp. 114-125.
36. Lee J. Design rationale systems: understanding the issues. IEEE Expert 12 3 (1997) 78-85
37. Levery M. Outsourcing maintenance - a question of strategy. Engineering Management Journal 8 1 (1998) 34-40
38. Likert R. A technique for measuring attitudes. In: Hayes N. (Ed). Principles of Social Psychology (1932), Laurence Erlbaum Associates 110
39. Lougher R., and Rodden T. Group support for the recording and sharing of maintenance rationale. Software Engineering Journal November (1993) 295-306
40. MacLean A., Young R.M., Bellotti V., and Moran T.P. Questions, options and criteria: elements of design space analysis. In: Moran T., and Carroll J. (Eds). Design Rationale Concepts, Techniques, and Use (1995), Lawrence Erlbaum Associates, NJ 201-251
41. Maurer, F., 1996. Coordinating system development processes. In: Proceedings of the Knowledge Acquisition Workshop 1996 (KAW-96), Banff, vol. 2, pp. 49/1-49/20.
42. In: Moran T., and Carroll J. (Eds). Design Rationale Concepts, Techniques and Use (1995), Lawrence Erlbaum Associates, Mahwah, NJ
43. Peña-Mora F., and Vadhavkar S. Augmenting design patterns with design rationale. Artificial Intelligence for Engineering Design, Analysis and Manufacturing 11 (1996) 93-108
44. Potts, C., Bruns, G., 1988. Recording the reasons for design decisions. In: Proceedings International Conference on Software Engineering, Singapore, pp. 418-427.
45. Ramesh B., and Dhar V. Representing and maintaining process knowledge for large scale systems development. IEEE Expert 9 4 (1994) 54-60
46. Reiss, S.P., 2002. Constraining software evolution. In: Proceedings of the International Conference on Software Maintenance, Montreal, Quebec, Canada, pp. 162-171.
47. Sim, S., Duffy, A., 1994. A new perspective to design intent and design rationale. In: Notes of Artificial Intelligence in Design Workshop on "Representing and Using Design Rationale", August, pp. 4-12.
48. Stahovich T.F. Artificial intelligence for design. In: Antonsson E.K., and Cagan J. (Eds). Formal Engineering Design Synthesis (2001), Cambridge University Press 228-269
49. Sutcliffe, A., 1995. Requirements rationales: integrating approaches to requirement analysis. In: Proceedings of the Conference on Designing interactive Systems: Processes, Practices, Methods, & Techniques, Ann Arbor, Michigan, pp. 33-42.
50. Sutcliffe, A.G., Ryan, M., 1998. Experience with SCRAM, a SCenario requirements analysis method. In: Proceedings of the IEEE International Symposium on Requirements Engineering: RE'98, Colorado Springs, CO, pp. 164-171.
51. Tong C., and Sriram D. Introduction. In: Tong C., and Sriram D. (Eds). Artificial Intelligence in Engineering Design vol. 1 (1992), Academic Press 1-53
52. Toulmin S. The Uses of Argument (1958), Cambridge University Press, Cambridge
53. Wohlin C., Runeson P., Höst M., Ohlsson M., Regnell B., and Wesslén A. Experimentation in Software Engineering: An Introduction (2000), Kluwer Academic Publishers
54. Zaychik V., and Regli W.C. Capturing communication and context in the software project lifecycle. Research in Engineering Design 14 2 (2003) 75-88