Using extreme characters to teach requirements engineering

Claudia Iacob, Shamal Faily

Research output: Chapter in Book/Report/Conference proceedingConference contribution

86 Downloads (Pure)

Abstract

One of the main challenges in teaching Software Engineering as an undergraduate course is making the need for software processes and documentation obvious. Armed with some knowledge of programming, students may feel inclined to skip any development phase not involving coding. This is most pronounced when dealing with the Requirements Engineering practices. In this paper, we describe a practical approach to teaching Requirements Engineering using Extreme Characters. The exercise aimed to achieve the following learning objectives: a) understanding the need of including the end user in any requirements analysis phase, b) identifying the requirements engineering phase as a iterative process, c) understanding the necessity of constantly double checking the analysts interpretation of the user requirements, d) ensuring the rigorous documentation of both user and system requirements, and e) identifying the place of requirements engineering in the overall development process, and the forces and challenges around this phase of development.
Original languageEnglish
Title of host publication2017 IEEE 30th Conference on Software Engineering Education and Training (CSEE&T)
PublisherIEEE
Pages107-111
Number of pages5
ISBN (Electronic)978-1538625361
ISBN (Print)978-1538625378
DOIs
Publication statusPublished - 7 Dec 2017
Event30th IEEE Conference on Software Engineering and Training: CSEE&T 2017 - Savannah, United States
Duration: 7 Nov 20179 Nov 2017

Publication series

NameIEEE CSEE&T Proceedings Series
ISSN (Electronic)2377-570X

Conference

Conference30th IEEE Conference on Software Engineering and Training
Country/TerritoryUnited States
CitySavannah
Period7/11/179/11/17

Keywords

  • requirements elicitation
  • specification
  • verification

Fingerprint

Dive into the research topics of 'Using extreme characters to teach requirements engineering'. Together they form a unique fingerprint.

Cite this