<?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-19T07:05:35Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/59231" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/59231</identifier><datestamp>2026-06-06T01:06:00Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>col_1721.1_131023</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">Alan MacCormack.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Davis, Jeffrey (Jeffrey Ethan)</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="contributor" qualifier="department">Massachusetts Institute of Technology. Engineering Systems Division</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2010-10-12T18:49:15Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2010-10-12T18:49:15Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2010</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2010</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/59231</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">666449210</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M. in System Design and Management)--Massachusetts Institute of Technology, Engineering Systems Division, 2010.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Cataloged from PDF version of thesis.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Although large scale software reuse has been studied and practiced in industry for more than 20 years, there are some practice areas where it has presented both technical and business challenges. A sector notable for exhibiting these challenges is defense electronics, the home business arena of the client organization. We have gathered information from academic and broad industry work to compare with the sponsor's experience over the past 15 years. Their organization has built a software reuse program over this time, and benefits from significant exploration of component, module, and software. product line' reuse models. In this context, we try to make sense of and understand patterns of the sponsor's cases, also concentrating on the business and technological environment and the resultant constraints that bound software projects. Our general hypothesis is that success of a reuse program is affected by: project organization type, the team's support and performance, and the design-for-reuse quality of the product. The business success that flows from the reuse program is dependent upon the strategic decisions made with reuse in mind as well as the suitability of the program's structure to the overall business model. In the sponsor's case, this suitability was less than perfect due to the nuances of the defense industry. We draw valuable insights from these cases and present them in a manner useful by similar projects. Further, experience with the product platform technique presents cases that may reveal how it requires the rigor of strict product focus to best serve the business. The main output of this work is to offer conclusions that can be used to shape business area strategy and reuse techniques based on specific conditions of the potential projects or product families.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Jeffrey Davis.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M. in System Design and Management</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">88 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">Engineering Systems Division.</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">Software reuse in defense electronics : a study of organization and architecture approaches in a challenging business and technical environment</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="56223b51-2a30-4342-b8cf-668828b0cf0d">
	&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>Software reuse in defense electronics : a study of organization and architecture approaches in a challenging business and technical environment&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2010&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Davis, Jeffrey (Jeffrey Ethan)&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>Engineering Systems Division.&lt;/Keyword>
    &lt;Keyword>System Design and Management Program.&lt;/Keyword>
   	&lt;Abstract>Although large scale software reuse has been studied and practiced in industry for more than 20 years, there are some practice areas where it has presented both technical and business challenges. A sector notable for exhibiting these challenges is defense electronics, the home business arena of the client organization. We have gathered information from academic and broad industry work to compare with the sponsor&amp;apos;s experience over the past 15 years. Their organization has built a software reuse program over this time, and benefits from significant exploration of component, module, and software. product line&amp;apos; reuse models. In this context, we try to make sense of and understand patterns of the sponsor&amp;apos;s cases, also concentrating on the business and technological environment and the resultant constraints that bound software projects. Our general hypothesis is that success of a reuse program is affected by: project organization type, the team&amp;apos;s support and performance, and the design-for-reuse quality of the product. The business success that flows from the reuse program is dependent upon the strategic decisions made with reuse in mind as well as the suitability of the program&amp;apos;s structure to the overall business model. In the sponsor&amp;apos;s case, this suitability was less than perfect due to the nuances of the defense industry. We draw valuable insights from these cases and present them in a manner useful by similar projects. Further, experience with the product platform technique presents cases that may reveal how it requires the rigor of strict product focus to best serve the business. The main output of this work is to offer conclusions that can be used to shape business area strategy and reuse techniques based on specific conditions of the potential projects or product families.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>