Requirements Evolution: Relating Functional and Non-Functional Requirement Change on Student Project Success

Abstract

This paper presents findings from a study of the evolution of requirements in eight parallel student semester long design projects. Weekly requirements documents were collected and analyzed for the number of functional and non-functional requirements defined by each team. Trends were compared with end of project performance success. The findings provide suggestive, not definitive, evidence that (a) a higher number of defined requirements predicted higher project success, (b) early functional requirement definition relates to project success, and (c) it is important to continually evolve the requirements throughout the project. A set of guidelines and recommendations are developed.