2026-09-19T03:27:38Zhttps://dspace.mit.edu/server/oai/requestoai:dspace.mit.edu:1721.1/1185102022-01-13T07:55:19Zcom_1721.1_7582com_1721.1_7581col_1721.1_131023
Bryan R Moser.
West, Christian J. (Christian Joseph)
Massachusetts Institute of Technology. Integrated Design and Management Program.
Massachusetts Institute of Technology. Engineering and Management Program
Massachusetts Institute of Technology. Integrated Design and Management Program.
2018-10-15T20:23:07Z
2018-10-15T20:23:07Z
2018
2018
http://hdl.handle.net/1721.1/118510
1054722538
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, System Design and Management Program, 2018.
Cataloged from PDF version of thesis.
Includes bibliographical references (pages 99-101).
Engineers and managers of software projects have the daunting task of successfully delivering the right product at the right time for the right price. The path to achieving these lofty goals is commonly not a straightforward endeavor. Due to the dynamic nature of software development, varying organizational circumstances, and situational idiosyncrasies of each project this can be a very difficult and sensitive process. Ideally, software development methodologies bring order to the chaos of software development. An ill-fitting development strategy, however, can create unnecessary friction and further complicate the prospect of a successful product delivery. Researchers and private organizations alike spend substantial resources to understand the strengths and weaknesses of commonly used development practices - the validation of which is highly problematic due to conflicting variables. This research ventures to bring clarity to the question: "Which development methodology is right for a particular situation?" Treating the software development project life-cycle as a socio-technical system, it can be decomposed to the most fundamental elements. Using these elements as the architectural building blocks of a project, Agile, Waterfall, Set-Based, and Spiral are each compared at the molecular level. This thesis evaluates these comparisons and how subsequent research applies to today's software projects.
by Christian J West.
S.M. in Engineering and Management
116 pages
eng
Massachusetts Institute of Technology
MIT theses are protected by copyright. They may be viewed, downloaded, or printed from this source but further reproduction or distribution in any format is prohibited without written permission.
http://dspace.mit.edu/handle/1721.1/7582
Engineering and Management Program.
Integrated Design and Management Program.
A comparison of software project architectures : agile, waterfall, spiral, and set-based
Thesis
application/pdf
Publication
unknown
unknown
<Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="93991305-397b-4349-b007-e4987ca3e83b">
<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 comparison of software project architectures : agile, waterfall, spiral, and set-based</Title>
<PublishedIn>
<Publication>
</Publication>
</PublishedIn>
<PublicationDate>2018</PublicationDate>
<Authors>
<Author>
<DisplayName>West, Christian J. (Christian Joseph)</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>Engineering and Management Program.</Keyword>
<Keyword>Integrated Design and Management Program.</Keyword>
<Abstract>Engineers and managers of software projects have the daunting task of successfully delivering the right product at the right time for the right price. The path to achieving these lofty goals is commonly not a straightforward endeavor. Due to the dynamic nature of software development, varying organizational circumstances, and situational idiosyncrasies of each project this can be a very difficult and sensitive process. Ideally, software development methodologies bring order to the chaos of software development. An ill-fitting development strategy, however, can create unnecessary friction and further complicate the prospect of a successful product delivery. Researchers and private organizations alike spend substantial resources to understand the strengths and weaknesses of commonly used development practices - the validation of which is highly problematic due to conflicting variables. This research ventures to bring clarity to the question: "Which development methodology is right for a particular situation?" Treating the software development project life-cycle as a socio-technical system, it can be decomposed to the most fundamental elements. Using these elements as the architectural building blocks of a project, Agile, Waterfall, Set-Based, and Spiral are each compared at the molecular level. This thesis evaluates these comparisons and how subsequent research applies to today's software projects.</Abstract>
<Access xmlns="http://purl.org/coar/access_right"
>
</Access>
</Publication>