Commenced in January 2007
Frequency: Monthly
Edition: International
Paper Count: 30124
Teaching Students Collaborative Requirements Engineering: Case Study of Red:Wire

Authors: Dagmar Monett, Sven-Erik Kujat, Marvin Hartmann

Abstract:

This paper discusses the use of a template-based approach for documenting high-quality requirements as part of course projects in an undergraduate Software Engineering course. In order to ease some of the Requirements Engineering activities that are performed when defining requirements by using the template, a new CASE tool, RED:WIRE, was first developed and later tested by students attending the course. Two questionnaires were conceived around a study that aims to analyze the new tool’s learnability as well as other obtained results concerning its usability in particular and the Requirements Engineering skills developed by the students in general.

Keywords: CASE tool, collaborative learning, requirements engineering, undergraduate teaching.

Digital Object Identifier (DOI): doi.org/10.5281/zenodo.1123827

Procedia APA BibTeX Chicago EndNote Harvard JSON MLA RIS XML ISO 690 PDF Downloads 969

References:


[1] K. Wiegers and J. Beatty, Software Requirements, 3rd ed. Redmond, Washington: Microsoft Press, 2014.
[2] I. Sommerville, Software Engineering, 9th ed. Pearson, Addison-Wesley, 2011.
[3] IREB. International requirements engineering board. International Requirements Engineering Board. Accessed: Jan. 14, 2016. (Online). Available: https://www.ireb.org/en
[4] M. Glinz, A Glossary of Requirements Engineering Terminology, IREB e.V. and Department of Informatics, University of Zurich, May 2014.
[5] C. Rupp, “Chapter 1: In medias RE,” in Requirements-Engineering und Management: Aus der Praxis von klassisch bis agil. Hanser, 2011, pp. 1–21.
[6] C. Rupp and E. Wolf, “Chapter 6: The SOPHIST Set of REgulations – Psychotherapy for Requirements,” in Requirements-Engineering und Management: Aus der Praxis von klassisch bis agil. Hanser, 2011, pp. 115–156.
[7] C. Rupp and R. Joppich, “Chapter 7: Templates – Construction Plans for Requirements and for More,” in Requirements-Engineering und Management: Aus der Praxis von klassisch bis agil. Hanser, 2011, pp. 157–176.
[8] SOPHIST. Sophist: Start. Accessed: Jan. 14, 2016. (Online). Available: https://www.sophist.de/en/start/
[9] S. Kleuker, Grundkurs Software-Engineering mit UML: Der pragmatische Weg zu erfolgreichen Softwareprojekten, 2nd ed. Munich: Vieweg+Teubner Verlag, 2011.
[10] C. Rupp, Requirements-Engineering und Management: Aus der Praxis von klassisch bis agil, 6th ed. Munich: Hanser, 2014.
[11] A. Birk and G. Heller. (2015) List of requirements management tools. Accessed: Jan. 14, 2016. (Online). Available: http://makingofsoftware. com/resources/list-of-rm-tools
[12] A. Fuggetta, “A Classification of CASE Technology,” IEEE Computer, vol. 26, no. 12, pp. 25–38, 1993.
[13] M. Senapathi, “A Framework for the Evaluation of CASE Tool Learnability in Educational Environments,” Journal of Information Technology Education, vol. 4, pp. 61–84, 2005.
[14] C. Mazza et al., Guide to the selection and use of CASE tools, ESA Board for Software Standardisation and Control, European Space Agency, May 1994.