Show simple item record

dc.contributor.advisorDaniel E. Whitney.en_US
dc.contributor.authorThebeau, Ronnie E. (Ronnie Emile), 1970-en_US
dc.contributor.otherSystem Design and Management Program.en_US
dc.date.accessioned2005-09-27T21:01:11Z
dc.date.available2005-09-27T21:01:11Z
dc.date.copyright2001en_US
dc.date.issued2001en_US
dc.identifier.urihttp://hdl.handle.net/1721.1/29168
dc.descriptionThesis (S.M.)--Massachusetts Institute of Technology, System Design & Management Program, 2001.en_US
dc.descriptionIncludes bibliographical references (p. 149).en_US
dc.description.abstractA system architecture was developed and analyzed for a basic elevator system using a limited number of system level components. A Design Structure Matrix was created which represented the complex interactions of the system components. These components were derived from a decomposition of system requirements, code and safety requirements, and evaluation of scenario operational requirements. Clustering routines using cost assignment of interactions aided in optimizing the cluster assignment of components. These cost assignments reflect cost and time associated with managing interactions inside and outside of subsystems. Management and optimization of the interfaces between the clustered components leads to an architecture that minimizes complexity and will hopefully lead to quicker and less costly product development cycles. Using this approach, near-optimal architectures can be analyzed and alternatives can be evaluated for system level impact. As was observed with this test case, highly complex or integrative systems are difficult to analyze, even with the tools utilized. These tools provided a structured approach that utilizes an objective process. This approach provides documentation and analysis of the architecture that is normally managed on the fly as product development progresses. The results of the analysis can provide a framework for an organizational structure of the product development process, provide an avenue for dialogue between design teams responsible for different subsystems, provide a process for evaluation of architecture alternatives, and identify the interactions between subsystems that must be managed carefully.en_US
dc.description.statementofresponsibilityby Ronnie E. Thebeau.en_US
dc.format.extent149 p.en_US
dc.format.extent9117533 bytes
dc.format.extent9117289 bytes
dc.format.mimetypeapplication/pdf
dc.format.mimetypeapplication/pdf
dc.language.isoengen_US
dc.publisherMassachusetts Institute of Technologyen_US
dc.rightsM.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.en_US
dc.rights.urihttp://dspace.mit.edu/handle/1721.1/7582
dc.subjectSystem Design and Management Program.en_US
dc.titleKnowledge management of system interfaces and interactions from product development processesen_US
dc.typeThesisen_US
dc.description.degreeS.M.en_US
dc.contributor.departmentSystem Design and Management Program.en_US
dc.identifier.oclc48272131en_US


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record