2026-09-18T20:09:49Zhttps://dspace.mit.edu/server/oai/requestoai:dspace.mit.edu:1721.1/348012022-01-13T07:55:19Zcom_1721.1_7582com_1721.1_7581col_1721.1_131023
Olivier de Weck.
Málaga Chocano, Eduardo, 1974-
System Design and Management Program.
System Design and Management Program.
2006-11-08T16:40:27Z
2006-11-08T16:40:27Z
2004
2004
http://hdl.handle.net/1721.1/34801
57553849
Thesis (S.M.)--Massachusetts Institute of Technology, System Design & Management Program, 2004.
Includes bibliographical references (p. 71-72).
After Royce introduced the Waterfall model in 1970, several approaches looking to provide the software development process with a formal framework have been elaborated and tested. While some of these followed the sequential line of thought presented by Royce and Boehm, other methodologies have suggested the use of iterations since early stages of the lifecycle as a mean to introduce feedback and gain understanding. This thesis takes a look at both types of approaches in an attempt to identify their strengths and weaknesses and based on this build criteria to recommend a particular approach or approach's elements for a given a set of conditions. Literary research and interviews with experienced project managers were conducted to identify software development issues and understand how these can be better addressed by the use of development methodology. Based upon this research a system dynamics model was developed. This model was used to simulate the effects that different approaches might have on a software project under similar and different situations. Analysis of the data suggests that, under certain conditions, iterative approaches are more effective to increase productivity due to learning and therefore more likely to finish earlier. They also promote a better distribution of time diminishing developers' idle time. On the other hand, sensitivity analysis shows that sequential approaches are more stable in terms of duration and quality and therefore a less risky option when initial conditions are uncertain.
by Eduardo Málaga Chocano.
S.M.
92 p.
4170352 bytes
4180712 bytes
application/pdf
application/pdf
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
System Design and Management Program.
A comparative study of iterative prototyping vs. waterfall process applied to small and medium sized software projects
Thesis
application/pdf
false
Publication
unknown
unknown
<Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="546301bb-15b2-4d56-b057-4ee706ad9a13">
<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>A comparative study of iterative prototyping vs. waterfall process applied to small and medium sized software projects</Title>
<PublishedIn>
<Publication>
</Publication>
</PublishedIn>
<PublicationDate>2004</PublicationDate>
<Authors>
<Author>
<DisplayName>Málaga Chocano, Eduardo, 1974-</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>System Design and Management Program.</Keyword>
<Abstract>After Royce introduced the Waterfall model in 1970, several approaches looking to provide the software development process with a formal framework have been elaborated and tested. While some of these followed the sequential line of thought presented by Royce and Boehm, other methodologies have suggested the use of iterations since early stages of the lifecycle as a mean to introduce feedback and gain understanding. This thesis takes a look at both types of approaches in an attempt to identify their strengths and weaknesses and based on this build criteria to recommend a particular approach or approach's elements for a given a set of conditions. Literary research and interviews with experienced project managers were conducted to identify software development issues and understand how these can be better addressed by the use of development methodology. Based upon this research a system dynamics model was developed. This model was used to simulate the effects that different approaches might have on a software project under similar and different situations. Analysis of the data suggests that, under certain conditions, iterative approaches are more effective to increase productivity due to learning and therefore more likely to finish earlier. They also promote a better distribution of time diminishing developers' idle time. On the other hand, sensitivity analysis shows that sequential approaches are more stable in terms of duration and quality and therefore a less risky option when initial conditions are uncertain.</Abstract>
<Access xmlns="http://purl.org/coar/access_right"
>
</Access>
</Publication>