Using Rationale for Software Engineering Education

Software engineering courses often use industrial modeling tools for their infrastructure, as it exposes students to the state-of-the practice and increases their awareness about the complexity of their craft. However, this approach has the risk of expending a disproportionate amount of effort on tools as opposed to teaching concepts. Moreover, industrial tools often do not include didactic concepts needed for education. In this paper, we discuss our experience with an integrated, rationale-based modeling tool in a variety of software engineering courses. By providing an integrated modeling environment, students use a single tool for requirements, system design, test planning, and collaboration. By attaching rationale to the models, students are encouraged to reflect on their work while instructors can monitor them and provide more insightful feedback

[1]  John M. Carroll,et al.  Design rationale: concepts, techniques, and use , 1996 .

[2]  David G. Ullman,et al.  Design rationale: Concepts, techniques, and use , 1997 .

[3]  Robert F. Coyne,et al.  Teaching More Comprehensive Model-Based Software Engineering: Experience with Objectory's Use Case Approach , 1995, CSEE.

[4]  Thomas P. Moran,et al.  Questions, Options, and Criteria: Elements of Design Space Analysis , 1991, Hum. Comput. Interact..

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

[6]  Tom Carey,et al.  HCI Design Rationales as a Learning Resource , 1996 .

[7]  Philippe Massonet,et al.  Goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learnt , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[8]  Daniel Port,et al.  Empirical research in the software engineering classroom , 2004, 17th Conference on Software Engineering Education and Training, 2004. Proceedings..

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

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

[11]  Nick Hammond,et al.  Argumentation-based design rationale: what use at what cost? , 1994, Int. J. Hum. Comput. Stud..

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

[13]  James E. Tomayko,et al.  Reflection processes in the teaching and learning of human aspects of software engineering , 2004, 17th Conference on Software Engineering Education and Training, 2004. Proceedings..