2026-09-21T19:31:18Zhttps://dspace.mit.edu/server/oai/requestoai:dspace.mit.edu:1721.1/816142022-01-13T07:54:05Zcom_1721.1_7582com_1721.1_7581col_1721.1_131023
Maria Yang.
Morocz Bazzani, Francisco Andres
Massachusetts Institute of Technology. Department of Mechanical Engineering.
Massachusetts Institute of Technology. Department of Mechanical Engineering
2013-10-24T17:35:14Z
2013-10-24T17:35:14Z
2013
2013
http://hdl.handle.net/1721.1/81614
858872629
Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of Mechanical Engineering, 2013.
Cataloged from PDF version of thesis.
Includes bibliographical references (p. 65-68).
This thesis focuses on the early stages of the product development process, during which the set of design requirements is formulated. Given the proven importance of a comprehensive set of design requirements in the market acceptance of a product, we explore the formulation of design requirements and the potential sources of uncertainty that can arise during this early phase of the development process. This thesis seeks to answer two main questions: What events and conditions are likely to increase the project's uncertainty during the formulation of the design requirements? And, in what way can the effects of these events and conditions be avoided or mitigated? Using the information gathered through an extensive literature review, a descriptive framework was compiled. The information used was validated following two different paths: first, the evolution of the set of design requirements of several teams in a product design and development class was analyzed and, second, veterans of industry were interviewed about their experiences during the development process.
by Francisco Andres Morocz Bazzani.
S.M.
68 p.
eng
Massachusetts Institute of Technology
M.I.T. theses are protected by
copyright. They may be viewed from this source for any purpose, but
reproduction or distribution in any format is prohibited without written
permission. See provided URL for inquiries about permission.
http://dspace.mit.edu/handle/1721.1/7582
Mechanical Engineering.
Design requirements formulation : a framework and analysis
Thesis
application/pdf
false
Publication
unknown
unknown
<Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="ceae8674-9f40-44ed-961f-d4c73f495368">
<Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843</Type>
<Language>eng</Language>
<Title>Design requirements formulation : a framework and analysis</Title>
<PublishedIn>
<Publication>
</Publication>
</PublishedIn>
<PublicationDate>2013</PublicationDate>
<Authors>
<Author>
<DisplayName>Morocz Bazzani, Francisco Andres</DisplayName>
<Affiliation>
<OrgUnit>
</OrgUnit>
</Affiliation>
</Author>
</Authors>
<Editors>
</Editors>
<Publishers>
<Publisher>
<DisplayName>Massachusetts Institute of Technology</DisplayName>
<OrgUnit />
</Publisher>
</Publishers>
<License>http://dspace.mit.edu/handle/1721.1/7582</License>
<Keyword>Mechanical Engineering.</Keyword>
<Abstract>This thesis focuses on the early stages of the product development process, during which the set of design requirements is formulated. Given the proven importance of a comprehensive set of design requirements in the market acceptance of a product, we explore the formulation of design requirements and the potential sources of uncertainty that can arise during this early phase of the development process. This thesis seeks to answer two main questions: What events and conditions are likely to increase the project's uncertainty during the formulation of the design requirements? And, in what way can the effects of these events and conditions be avoided or mitigated? Using the information gathered through an extensive literature review, a descriptive framework was compiled. The information used was validated following two different paths: first, the evolution of the set of design requirements of several teams in a product design and development class was analyzed and, second, veterans of industry were interviewed about their experiences during the development process.</Abstract>
<Access xmlns="http://purl.org/coar/access_right"
>
</Access>
</Publication>