<?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:50:32Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/29884" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/29884</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">Earll Murman.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Ippolito, Brian J. (Brian James), 1970-</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">2006-03-24T17:59:50Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2006-03-24T17:59:50Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2000</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2000</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/29884</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">45289269</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, System Design &amp; Management Program, 2000.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 133-134).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Lean principles focus on employing value added activities to reduce product development cycle time, increase quality, and reduce cost. Lean originated in the automotive industry and has since been centered in the manufacturing domain. Lessons learned on implementing Lean initiatives have been captured by the in the Lean Aerospace Initiative (LAI) and incorporated into the Lean Enterprise Model (LEM) (http://lean.mit.edu/public/index.html). To the author's knowledge, this is the first research effort specifically designed to apply the Lean principles and the Lean Enterprise Model to the aerospace software requirement derivation process. Data supporting this research is the result of a comprehensive two-year research effort involving three detailed case studies with 45 case study interviews, 125 stakeholder surveys collected from ten aerospace software upgrades, feedback from numerous aerospace industry practitioners and Massachusetts Institute of technology (MIT) faculty. Ten aerospace software upgrades were analyzed at both an enterprise level and an organizational level to identify the presence of Lean practices. At the enterprise level, metrics typically used to measure enterprise performance (Flow Time, Stakeholder Satisfaction, Quality Yield, and Resource Utilization) were found to be appropriate for the software requirement process but not adequately implemented. An organizational analysis observed five of the twelve Lean practices as effectively implemented and identified opportunities to implement four more Lean practices.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Brian J. Ippolito.</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">134 p.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">8206393 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">8224099 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</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">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">Identifying lean practices for deriving software requirements</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="authorsordered">false</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="69f7de6d-0e48-4fc0-84ab-d225fe89ebb3">
	&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>Identifying lean practices for deriving software requirements&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2000&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Ippolito, Brian J. (Brian James), 1970-&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>Lean principles focus on employing value added activities to reduce product development cycle time, increase quality, and reduce cost. Lean originated in the automotive industry and has since been centered in the manufacturing domain. Lessons learned on implementing Lean initiatives have been captured by the in the Lean Aerospace Initiative (LAI) and incorporated into the Lean Enterprise Model (LEM) (http://lean.mit.edu/public/index.html). To the author&amp;apos;s knowledge, this is the first research effort specifically designed to apply the Lean principles and the Lean Enterprise Model to the aerospace software requirement derivation process. Data supporting this research is the result of a comprehensive two-year research effort involving three detailed case studies with 45 case study interviews, 125 stakeholder surveys collected from ten aerospace software upgrades, feedback from numerous aerospace industry practitioners and Massachusetts Institute of technology (MIT) faculty. Ten aerospace software upgrades were analyzed at both an enterprise level and an organizational level to identify the presence of Lean practices. At the enterprise level, metrics typically used to measure enterprise performance (Flow Time, Stakeholder Satisfaction, Quality Yield, and Resource Utilization) were found to be appropriate for the software requirement process but not adequately implemented. An organizational analysis observed five of the twelve Lean practices as effectively implemented and identified opportunities to implement four more Lean practices.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>