Abstract

This paper presents the findings from a case study conducted to investigate the evolution in the requirements documents of novice engineering designers (students). The case study was conducted with four student teams working in parallel on senior design project. At the beginning of the semester, all four teams were given the design problem and set of initial requirements by the sponsor. For the purpose of this case study, data were collected from all four teams in the form of weekly requirements update. These requirements were then investigated to explore the evolution of requirements and identify the changes in individual requirements from initial weeks to final week. The findings from this case study suggest that the requirements document of novice designers changes in multiple ways. Finally, a set of recommendations and guidelines are developed to help the novice designers to maintain the requirements document and manage the changes in the requirements document.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.