2026-09-27T01:50:01Zhttps://dspace.mit.edu/server/oai/requestoai:dspace.mit.edu:1721.1/96212025-10-27T18:00:47Zcom_1721.1_7582com_1721.1_7581col_1721.1_131023
Steven D. Eppinger.
Adamsen, Paul B. (Paul Bent), 1957-
System Design and Management Program.
2005-08-19T18:59:54Z
2005-08-19T18:59:54Z
1998
1998
http://hdl.handle.net/1721.1/9621
42277953
Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 1998.
Includes bibliographical references (leaves 75-78).
This thesis outlines a structured framework for complex system design and management. There have been and continue to be many efforts focused on defining the elusive generic System Engineering Process. I suggest one reason why industry, government, and academic efforts have had limited success in defining a generalized process applicable to many contexts, is that the time and logical domains have not been explicitly identified and characterized in distinction. When the logical view is combined with the chronological view, the resulting process becomes application specific. When these are characterized in distinction, the overall framework is preserved. This thesis develops a generalized process that maintains this distinction and is thus applicable to many contexts. The design and management of complex systems involves the execution of technical activities together with managerial activities. Because of the organic connection between these two sets of activities, they must be integrated in order to maximize the potential for success. This integration requires a clear definition of what the system development process is in terms of the technical activities and how they logically interact. The" control logic" thus provided is then used to develop the logical connection between the managerial and technical activities.
by Paul B. Adamsen, Jr.
S.M.
78 leaves
5638422 bytes
5638180 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 generalized framework for complex system design and management
Thesis
application/pdf
Publication
unknown
unknown
<Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="62a9fa85-c204-412e-93fe-2a741b59010f">
<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 generalized framework for complex system design and management</Title>
<PublishedIn>
<Publication>
</Publication>
</PublishedIn>
<PublicationDate>1998</PublicationDate>
<Authors>
<Author>
<DisplayName>Adamsen, Paul B. (Paul Bent), 1957-</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>This thesis outlines a structured framework for complex system design and management. There have been and continue to be many efforts focused on defining the elusive generic System Engineering Process. I suggest one reason why industry, government, and academic efforts have had limited success in defining a generalized process applicable to many contexts, is that the time and logical domains have not been explicitly identified and characterized in distinction. When the logical view is combined with the chronological view, the resulting process becomes application specific. When these are characterized in distinction, the overall framework is preserved. This thesis develops a generalized process that maintains this distinction and is thus applicable to many contexts. The design and management of complex systems involves the execution of technical activities together with managerial activities. Because of the organic connection between these two sets of activities, they must be integrated in order to maximize the potential for success. This integration requires a clear definition of what the system development process is in terms of the technical activities and how they logically interact. The" control logic" thus provided is then used to develop the logical connection between the managerial and technical activities.</Abstract>
<Access xmlns="http://purl.org/coar/access_right"
>
</Access>
</Publication>