2026-09-22T23:06:35Zhttps://dspace.mit.edu/server/oai/requestoai:dspace.mit.edu:1721.1/97442025-10-27T18:00:46Zcom_1721.1_7582com_1721.1_7581col_1721.1_131023
Michael A. Cusumano.
Arwe, John E. (John Elliott), 1964-
System Design and Management Program.
2005-08-19T19:52:31Z
2005-08-19T19:52:31Z
1999
1999
http://hdl.handle.net/1721.1/9744
42768168
Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 1999.
Includes bibliographical references (leaves 83-86).
The choice of project architecture - the structure of and interrelationships between product, processes, and organization - alters the project's risk profile. While most analyses take project scope as an input, I propose the examination of multiple project decompositions take place as part of project planning and project monitoring. The subÂprojects created by each decomposition will have unique risk profiles, suggesting different process and organizational adaptations that lower overall project risk. By selecting project decompositions that partition risk and then adapting the structure of each sub-project to mitigate its particular risks, the probability of risk occurrence is reduced and the severity of consequences may be reduced. Case studies of four IBM mainframe system software projects illustrate lessons regarding project architecture, some general and some project- or process-specific. These projects employ both waterfall and iterative process models, managed using varying degrees of functional, lightweight, and heavyweight organizations.
by John E. Arwe.
S.M.
86 leaves
9066652 bytes
9066414 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
Reducing system software project risk through choice of project architecture
Thesis
application/pdf
false
Publication
unknown
unknown
<Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="63c2a6e3-3492-4b88-bd36-1edcfba1d288">
<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>Reducing system software project risk through choice of project architecture</Title>
<PublishedIn>
<Publication>
</Publication>
</PublishedIn>
<PublicationDate>1999</PublicationDate>
<Authors>
<Author>
<DisplayName>Arwe, John E. (John Elliott), 1964-</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>The choice of project architecture - the structure of and interrelationships between product, processes, and organization - alters the project's risk profile. While most analyses take project scope as an input, I propose the examination of multiple project decompositions take place as part of project planning and project monitoring. The subÂprojects created by each decomposition will have unique risk profiles, suggesting different process and organizational adaptations that lower overall project risk. By selecting project decompositions that partition risk and then adapting the structure of each sub-project to mitigate its particular risks, the probability of risk occurrence is reduced and the severity of consequences may be reduced. Case studies of four IBM mainframe system software projects illustrate lessons regarding project architecture, some general and some project- or process-specific. These projects employ both waterfall and iterative process models, managed using varying degrees of functional, lightweight, and heavyweight organizations.</Abstract>
<Access xmlns="http://purl.org/coar/access_right"
>
</Access>
</Publication>