Do students recognize ambiguity in software specifications? a multi-national, multi-institutional report

  • Authors:
  • Tammy VanDeGrift;Beth Simon;Dean Sanders;Ken Blaha

  • Affiliations:
  • Electrical Engineering & Computer Science, University of Portland, Portland, OR;Computer Science & Engineering, University of California, San Diego, La Jolla, CA;Computer Science & Information Systems, Northwest Missouri State University, Maryville, MO;Computer Science & Computer Engineering, Pacific Lutheran University, Tacoma, WA

  • Venue:
  • ICSE'05 Proceedings of the 2005 international conference on Software Engineering Education in the Modern Age
  • Year:
  • 2005

Quantified Score

Hi-index 0.00

Visualization

Abstract

Successful software engineering requires experience and acknowledgment of complexity, including that which leads designers to recognize ambiguity within the software design description itself. We report on a study of 21 post-secondary institutions from the USA, UK, Sweden, and New Zealand. First competency and graduating students as well as educators were asked to perform a software design task. We found that graduating seniors were more likely to recognize ambiguities in under-specified problems than first competency students. Additionally, participants who addressed all requirements in the design were more likely than others to recognize ambiguities in the design specification. The behavior of recognizing ambiguity and gathering information appear to be independent of past performance, as measured by course grades.