{"id":{"repo_id":"clemson","oai_identifier":"oai:open.clemson.edu:all_theses-3624"},"canonical_url":"https://search.ndltd.org/etd/clemson/oai:open.clemson.edu:all_theses-3624","repository":{"repo_id":"clemson","name":"Clemson University","base_url":"https://open.clemson.edu/do/oai/"},"display":{"title":"Requirement Culture at a Large Scale Medical Device Developer: A Case Study","abstract":"This case study explores requirements evolution of a multimillion-dollar medical device under development for cancer therapy. The study focuses on the analysis of requirements across a twelve month window via interviews with involved parties and document analysis of the company's design requirements. Three engineering directors (mechanical, software, and systems) were interviewed contemporaneously with the analysis of eight revisions to the design functional specifications, consisting of over 1,000 total design requirements. Significant requirement change was observed and associated with 1) change in requirements leadership, 2) market strategy including scope towards regulatory approval, and 3) requirement learning curve with respect to writing testable requirements. From analysis of the interview transcripts and company requirement evolution, a requirements culture emerged highlighting a need for greater understanding of company requirements cultures in situ. Further, analysis of the company's biomedical requirement behavior align with those found in the avionics and automobile industries suggesting requirements evolution, and therefore problem understanding, occur similarly irrespective of domain or problem size.","abstract_html":"This case study explores requirements evolution of a multimillion-dollar medical device under development for cancer therapy. The study focuses on the analysis of requirements across a twelve month window via interviews with involved parties and document analysis of the company&#x27;s design requirements. Three engineering directors (mechanical, software, and systems) were interviewed contemporaneously with the analysis of eight revisions to the design functional specifications, consisting of over 1,000 total design requirements. Significant requirement change was observed and associated with 1) change in requirements leadership, 2) market strategy including scope towards regulatory approval, and 3) requirement learning curve with respect to writing testable requirements. From analysis of the interview transcripts and company requirement evolution, a requirements culture emerged highlighting a need for greater understanding of company requirements cultures in situ. Further, analysis of the company&#x27;s biomedical requirement behavior align with those found in the avionics and automobile industries suggesting requirements evolution, and therefore problem understanding, occur similarly irrespective of domain or problem size.","abstract_has_math":false,"creators":["DelSpina, Brandon Matthew"],"institution":null,"degree_name":"Master of Science (MS)","degree_level":"Thesis","degree_discipline":"Mechanical Engineering","degree_department":null,"school":null,"contributors":["Joshua D. Summers, Committee Chair","John DesJardins","Mary Elizabeth Kurz","Gregory Mocko"],"advisors":[],"committee_chairs":[],"committee_members":[],"year":null,"date_issued":"","date_published":null,"updated_at":"2026-11-19T07:15:06Z","subjects":["Case Study","Industry Requirements","Requirements Change","Requirements Change Propagation","Requirements Culture","Requirements Evolution"],"languages":[],"rights":[],"rights_urls":[],"identifier_entries":[],"person_identifier_entries":[]},"links":{"outbound_url":"https://open.clemson.edu/all_theses/2617","outbound_label":"Repository record","outbound_source":"dc:identifier","record_url":"https://open.clemson.edu/all_theses/2617","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-3624","prefix":"oai_etdms"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:contributor","label":"Contributor","values":["Joshua D. Summers, Committee Chair","John DesJardins","Mary Elizabeth Kurz","Gregory Mocko"]},{"key":"dc:creator","label":"Author","values":["DelSpina, Brandon Matthew"]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"dc:date.created","label":"Dc Date Created","values":["2017-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":["Case Study","Industry Requirements","Requirements Change","Requirements Change Propagation","Requirements Culture","Requirements Evolution"]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier","label":"Identifier","values":["https://open.clemson.edu/all_theses/2617"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description.abstract","label":"Abstract","values":["This case study explores requirements evolution of a multimillion-dollar medical device under development for cancer therapy. The study focuses on the analysis of requirements across a twelve month window via interviews with involved parties and document analysis of the company's design requirements. Three engineering directors (mechanical, software, and systems) were interviewed contemporaneously with the analysis of eight revisions to the design functional specifications, consisting of over 1,000 total design requirements. Significant requirement change was observed and associated with 1) change in requirements leadership, 2) market strategy including scope towards regulatory approval, and 3) requirement learning curve with respect to writing testable requirements. From analysis of the interview transcripts and company requirement evolution, a requirements culture emerged highlighting a need for greater understanding of company requirements cultures in situ. Further, analysis of the company's biomedical requirement behavior align with those found in the avionics and automobile industries suggesting requirements evolution, and therefore problem understanding, occur similarly irrespective of domain or problem size."]},{"key":"dc:title","label":"Title","values":["Requirement Culture at a Large Scale Medical Device Developer: A Case Study"]}]}],"canonical_facts":{"dc:contributor":["Joshua D. Summers, Committee Chair","John DesJardins","Mary Elizabeth Kurz","Gregory Mocko"],"dc:creator":["DelSpina, Brandon Matthew"],"dc:date.created":["2017-05-01T07:00:00Z"],"dc:description.abstract":["This case study explores requirements evolution of a multimillion-dollar medical device under development for cancer therapy. The study focuses on the analysis of requirements across a twelve month window via interviews with involved parties and document analysis of the company's design requirements. Three engineering directors (mechanical, software, and systems) were interviewed contemporaneously with the analysis of eight revisions to the design functional specifications, consisting of over 1,000 total design requirements. Significant requirement change was observed and associated with 1) change in requirements leadership, 2) market strategy including scope towards regulatory approval, and 3) requirement learning curve with respect to writing testable requirements. From analysis of the interview transcripts and company requirement evolution, a requirements culture emerged highlighting a need for greater understanding of company requirements cultures in situ. Further, analysis of the company's biomedical requirement behavior align with those found in the avionics and automobile industries suggesting requirements evolution, and therefore problem understanding, occur similarly irrespective of domain or problem size."],"dc:identifier":["https://open.clemson.edu/all_theses/2617"],"dc:subject":["Case Study","Industry Requirements","Requirements Change","Requirements Change Propagation","Requirements Culture","Requirements Evolution"],"dc:title":["Requirement Culture at a Large Scale Medical Device Developer: A Case Study"],"thesis:degree_discipline":["Mechanical Engineering"],"thesis:degree_level":["Thesis"],"thesis:degree_name":["Master of Science (MS)"]},"updated_at":"2026-11-19T07:15:06Z"}