Requirements play a critical role in the design process. Much of the project time is spent eliciting the requirements. However, it is observed that students primarily only consider requirements while evaluating the concepts. This paper presents a case study conducted with senior mechanical engineering design students in a capstone course to begin to understand requirement evolution throughout a project. Data in the form of weekly requirements was collected from four teams working in parallel on the same industry sponsored project. The paper introduces the concepts of completeness and specificity that could allow the use of requirements as a tool for measuring project health. The findings from the case study reveal that the completeness and specificity of requirements increase from initial week to final week.

This content is only available via PDF.
You do not currently have access to this content.