{"id":{"repo_id":"clemson","oai_identifier":"oai:open.clemson.edu:all_theses-4553"},"canonical_url":"https://search.ndltd.org/etd/clemson/oai:open.clemson.edu:all_theses-4553","repository":{"repo_id":"clemson","name":"Clemson University","base_url":"https://open.clemson.edu/do/oai/"},"display":{"title":"An Experimental Study Exploring the Influence of Different Representation of Requirements on Idea Generation","abstract":"This research aims to understand the influence of different representations of requirements on idea generation concerning the quantity, addressment, sketch detail, novelty, and variety of conceptual sketches. To solve design problems, engineers use the needs, desires, and wishes of stakeholders. The requirements document the targets of a project because it contains constraints and design criteria. Also, requirements can be used to track project progress. In essence, specifications are the raison d'être of any engineering project. While there is research studying the effect of requirements on the conceptual sketch, little study has focused on the impact of different requirement representations (contextual) on solution development. An experimental study was conducted with 52 undergraduate mechanical engineering students in their fourth year. Two design problems were formulated with three different representations: a problem statement with embedded requirements (Problem Statement), a problem statement and a traditional requirement list (Traditional), and a problem statement with contextualized scrum stories (Contextual). For each design problem, each student received different representations of requirements. They were given 15 minutes each to read and sketch concept solutions. These were then analyzed using quantity, addressment, sketch detail, novelty, and variety. It was found that the use of contextualized scrum story representations had a statistically significant impact on the conceptual sketch in terms of novelty of solution fragments and requirements addressed. Further, there was no significant change in variety, sketch detail, or quantity. The contextualized representation did positively affect all metrics but the sketch detail. Another finding was that there was no relationship between the amount of sketch generated (quantity) and addressment, novelty, variety, or sketch detail. Therefore, it is recommended that requirements be molded as scrum stories in projects. Also, this study has shown that implementation of the agile process in hardware development is not hindered by the contextual representation of requirements.","abstract_html":"This research aims to understand the influence of different representations of requirements on idea generation concerning the quantity, addressment, sketch detail, novelty, and variety of conceptual sketches. To solve design problems, engineers use the needs, desires, and wishes of stakeholders. The requirements document the targets of a project because it contains constraints and design criteria. Also, requirements can be used to track project progress. In essence, specifications are the raison d&#x27;être of any engineering project. While there is research studying the effect of requirements on the conceptual sketch, little study has focused on the impact of different requirement representations (contextual) on solution development. An experimental study was conducted with 52 undergraduate mechanical engineering students in their fourth year. Two design problems were formulated with three different representations: a problem statement with embedded requirements (Problem Statement), a problem statement and a traditional requirement list (Traditional), and a problem statement with contextualized scrum stories (Contextual). For each design problem, each student received different representations of requirements. They were given 15 minutes each to read and sketch concept solutions. These were then analyzed using quantity, addressment, sketch detail, novelty, and variety. It was found that the use of contextualized scrum story representations had a statistically significant impact on the conceptual sketch in terms of novelty of solution fragments and requirements addressed. Further, there was no significant change in variety, sketch detail, or quantity. The contextualized representation did positively affect all metrics but the sketch detail. Another finding was that there was no relationship between the amount of sketch generated (quantity) and addressment, novelty, variety, or sketch detail. Therefore, it is recommended that requirements be molded as scrum stories in projects. Also, this study has shown that implementation of the agile process in hardware development is not hindered by the contextual representation of requirements.","abstract_has_math":false,"creators":["Patel, Akash"],"institution":null,"degree_name":"Master of Science (MS)","degree_level":"Thesis","degree_discipline":"Mechanical Engineering","degree_department":null,"school":null,"contributors":["Joshua Summers","Cameron Turner","John Wagner"],"advisors":[],"committee_chairs":[],"committee_members":[],"year":null,"date_issued":"","date_published":null,"updated_at":"2026-11-19T07:28:28Z","subjects":["Agile Process","Contextual","Design Process","Requirements","SCRUM"],"languages":[],"rights":[],"rights_urls":[],"identifier_entries":[],"person_identifier_entries":[]},"links":{"outbound_url":"https://open.clemson.edu/all_theses/3546","outbound_label":"Repository record","outbound_source":"dc:identifier","record_url":"https://open.clemson.edu/all_theses/3546","record_label":"Repository record","record_kind":"record","record_source":"dc:identifier","download_url":null,"download_label":null,"download_source":null,"access_status":null,"embargo_until":null,"access_note":null},"source_record":{"url":"https://open.clemson.edu/do/oai/?verb=GetRecord&metadataPrefix=oai_etdms&identifier=oai%3Aopen.clemson.edu%3Aall_theses-4553","prefix":"oai_etdms"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:contributor","label":"Contributor","values":["Joshua Summers","Cameron Turner","John Wagner"]},{"key":"dc:creator","label":"Author","values":["Patel, Akash"]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"dc:date.created","label":"Dc Date Created","values":["2021-05-01T07:00:00Z"]},{"key":"thesis:degree_discipline","label":"Discipline","values":["Mechanical Engineering"]},{"key":"thesis:degree_level","label":"Degree Level","values":["Thesis"]},{"key":"thesis:degree_name","label":"Degree Name","values":["Master of Science (MS)"]}]},{"id":"subjects_keywords","label":"Subjects and Keywords","entries":[{"key":"dc:subject","label":"Dc Subject","values":["Agile Process","Contextual","Design Process","Requirements","SCRUM"]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier","label":"Identifier","values":["https://open.clemson.edu/all_theses/3546"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description.abstract","label":"Abstract","values":["This research aims to understand the influence of different representations of requirements on idea generation concerning the quantity, addressment, sketch detail, novelty, and variety of conceptual sketches. To solve design problems, engineers use the needs, desires, and wishes of stakeholders. The requirements document the targets of a project because it contains constraints and design criteria. Also, requirements can be used to track project progress. In essence, specifications are the raison d'être of any engineering project. While there is research studying the effect of requirements on the conceptual sketch, little study has focused on the impact of different requirement representations (contextual) on solution development. An experimental study was conducted with 52 undergraduate mechanical engineering students in their fourth year. Two design problems were formulated with three different representations: a problem statement with embedded requirements (Problem Statement), a problem statement and a traditional requirement list (Traditional), and a problem statement with contextualized scrum stories (Contextual). For each design problem, each student received different representations of requirements. They were given 15 minutes each to read and sketch concept solutions. These were then analyzed using quantity, addressment, sketch detail, novelty, and variety. It was found that the use of contextualized scrum story representations had a statistically significant impact on the conceptual sketch in terms of novelty of solution fragments and requirements addressed. Further, there was no significant change in variety, sketch detail, or quantity. The contextualized representation did positively affect all metrics but the sketch detail. Another finding was that there was no relationship between the amount of sketch generated (quantity) and addressment, novelty, variety, or sketch detail. Therefore, it is recommended that requirements be molded as scrum stories in projects. Also, this study has shown that implementation of the agile process in hardware development is not hindered by the contextual representation of requirements."]},{"key":"dc:title","label":"Title","values":["An Experimental Study Exploring the Influence of Different Representation of Requirements on Idea Generation"]}]}],"canonical_facts":{"dc:contributor":["Joshua Summers","Cameron Turner","John Wagner"],"dc:creator":["Patel, Akash"],"dc:date.created":["2021-05-01T07:00:00Z"],"dc:description.abstract":["This research aims to understand the influence of different representations of requirements on idea generation concerning the quantity, addressment, sketch detail, novelty, and variety of conceptual sketches. To solve design problems, engineers use the needs, desires, and wishes of stakeholders. The requirements document the targets of a project because it contains constraints and design criteria. Also, requirements can be used to track project progress. In essence, specifications are the raison d'être of any engineering project. While there is research studying the effect of requirements on the conceptual sketch, little study has focused on the impact of different requirement representations (contextual) on solution development. An experimental study was conducted with 52 undergraduate mechanical engineering students in their fourth year. Two design problems were formulated with three different representations: a problem statement with embedded requirements (Problem Statement), a problem statement and a traditional requirement list (Traditional), and a problem statement with contextualized scrum stories (Contextual). For each design problem, each student received different representations of requirements. They were given 15 minutes each to read and sketch concept solutions. These were then analyzed using quantity, addressment, sketch detail, novelty, and variety. It was found that the use of contextualized scrum story representations had a statistically significant impact on the conceptual sketch in terms of novelty of solution fragments and requirements addressed. Further, there was no significant change in variety, sketch detail, or quantity. The contextualized representation did positively affect all metrics but the sketch detail. Another finding was that there was no relationship between the amount of sketch generated (quantity) and addressment, novelty, variety, or sketch detail. Therefore, it is recommended that requirements be molded as scrum stories in projects. Also, this study has shown that implementation of the agile process in hardware development is not hindered by the contextual representation of requirements."],"dc:identifier":["https://open.clemson.edu/all_theses/3546"],"dc:subject":["Agile Process","Contextual","Design Process","Requirements","SCRUM"],"dc:title":["An Experimental Study Exploring the Influence of Different Representation of Requirements on Idea Generation"],"thesis:degree_discipline":["Mechanical Engineering"],"thesis:degree_level":["Thesis"],"thesis:degree_name":["Master of Science (MS)"]},"updated_at":"2026-11-19T07:28:28Z"}