<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-09-19T18:42:51Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/43097" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/43097</identifier><datestamp>2022-01-13T07:55:19Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>com_1721.1_80738</setSpec><setSpec>com_1721.1_1773</setSpec><setSpec>col_1721.1_131023</setSpec><setSpec>col_1721.1_80739</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="advisor" lang="en_US">Donna H. Rhodes.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Flynn, Timothy Daniel</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2008-11-07T19:02:01Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2008-11-07T19:02:01Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2007</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2007</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/43097</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">244630857</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, 2007.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. [126]-128).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">The need for robust systems engineering in product development has been understood by those developing product in the aerospace and defense industries since the days of the Atlas ballistic missile program. In recent times industries developing systems of similar complexity have come to respect the value of systems engineering. Systems engineering is the glue which binds a large technical team and focuses the engineering effort towards satisfying a set of realizable customer needs. EIA/IS-632 definition of systems engineering is as follows; "Systems engineering is an interdisciplinary approach encompassing the entire technical effort to evolve and verify an integrated and life-cycle balanced set of system people, product and process solutions that satisfy customer needs."To control and improve a process a viable set of measures must be in place. Existing measures of the strength of the systems engineering process in a specific project address only project execution (e.g. earned value) and technical performance. When applied properly these metrics provide valuable insight into the status (cost and schedule) of a project and a products ability to meet customer needs. However, few of these existing measures are progressive in nature and as such fail to provide early warnings of systems engineering process failure. What are needed are prognostics for the systems engineering effort; gauges to provide predictions of future events which impact product cost, schedule and/or performance. The Lean Aerospace Initiative (LAI), working with the International Council on Systems Engineering (INCOSE), released a guide (in Beta form) in December of 2005 outlining a progressive set of thirteen leading indicators to address this need. This set of metrics has yet to be been verified against an active or historical project but provides a starting ground for additional research.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Timothy Daniel Flynn.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">128 p.</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso" lang="en_US">eng</dim:field>
   <dim:field mdschema="dc" element="publisher" lang="en_US">Massachusetts Institute of Technology</dim:field>
   <dim:field mdschema="dc" element="rights" lang="en_US">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.</dim:field>
   <dim:field mdschema="dc" element="rights" qualifier="uri" lang="en_US">http://dspace.mit.edu/handle/1721.1/7582</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Evaluation and synthesis of methods for measuring system engineering efficacy with a project and organization</dim:field>
   <dim:field mdschema="dc" element="type" lang="en_US">Thesis</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dspace" element="entity" qualifier="type">Publication</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="cerif" element="openaire" authority="" confidence="-1">&lt;Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="81675def-d035-4873-965f-667dfafe654e">
	&lt;Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843&lt;/Type>
	&lt;Language>eng&lt;/Language>
   	&lt;Title>Evaluation and synthesis of methods for measuring system engineering efficacy with a project and organization&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2007&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Flynn, Timothy Daniel&lt;/DisplayName>
         	&lt;Affiliation>
         		&lt;OrgUnit>
         		&lt;/OrgUnit>
         	&lt;/Affiliation>
      	&lt;/Author>
	&lt;/Authors>
   	&lt;Editors>
	&lt;/Editors>
    &lt;Publishers>
        &lt;Publisher>
            &lt;DisplayName>Massachusetts Institute of Technology&lt;/DisplayName>
            &lt;OrgUnit />
        &lt;/Publisher>
    &lt;/Publishers>
    &lt;License>http://dspace.mit.edu/handle/1721.1/7582&lt;/License>
    &lt;Keyword>System Design and Management Program.&lt;/Keyword>
   	&lt;Abstract>The need for robust systems engineering in product development has been understood by those developing product in the aerospace and defense industries since the days of the Atlas ballistic missile program. In recent times industries developing systems of similar complexity have come to respect the value of systems engineering. Systems engineering is the glue which binds a large technical team and focuses the engineering effort towards satisfying a set of realizable customer needs. EIA/IS-632 definition of systems engineering is as follows; &amp;quot;Systems engineering is an interdisciplinary approach encompassing the entire technical effort to evolve and verify an integrated and life-cycle balanced set of system people, product and process solutions that satisfy customer needs.&amp;quot;To control and improve a process a viable set of measures must be in place. Existing measures of the strength of the systems engineering process in a specific project address only project execution (e.g. earned value) and technical performance. When applied properly these metrics provide valuable insight into the status (cost and schedule) of a project and a products ability to meet customer needs. However, few of these existing measures are progressive in nature and as such fail to provide early warnings of systems engineering process failure. What are needed are prognostics for the systems engineering effort; gauges to provide predictions of future events which impact product cost, schedule and/or performance. The Lean Aerospace Initiative (LAI), working with the International Council on Systems Engineering (INCOSE), released a guide (in Beta form) in December of 2005 outlining a progressive set of thirteen leading indicators to address this need. This set of metrics has yet to be been verified against an active or historical project but provides a starting ground for additional research.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>