<?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-23T14:04:01Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/121795" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/121795</identifier><datestamp>2022-01-13T07:55:19Z</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">Page, Austin M.(Austin Markley)</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Engineering and Management Program.</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">Massachusetts Institute of Technology. Engineering and Management Program</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2019-07-18T20:30:06Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2019-07-18T20:30:06Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2019</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2019</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">https://hdl.handle.net/1721.1/121795</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">1103445476</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, System Design and Management Program, 2019</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Cataloged from PDF version of thesis. Vita.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (pages 93-96).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">The Air Force is currently paying a cost for the mismanagement of its software development activities. Software-intensive systems are consistently plagued with cost, schedule, and performance issues, which in the current fiscal environment is unsustainable. There has been much research on the benefits of process improvement, yet the concept of product health is largely ignored. Technical debt - the consequence of making short-term design decisions at the expense of long-term health - has been accumulating within code bases as developers and managers struggle to identify, quantify, and manage it properly. In this thesis, an extensive literature search is performed to define technical debt, explain its implications, and highlight methods to quantify and visualize it so organizations can address it explicitly. Through the use of architectural health analysis tools, a set of metrics is defined and used in case studies to highlight the extent to which the Air Force has lost control of its software and the price it has to pay because of it. Ultimately, eleven recommendations are given on how to incorporate architectural health analysis tools into software development activities to prevent, identify, manage, and reduce the amount of technical debt across product lifecycles.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Austin M. Page.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M. in Engineering and Management</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="collection" lang="en_US">S.M.inEngineeringandManagement Massachusetts Institute of Technology, System Design and Management Program</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">98 pages</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">MIT theses are protected by copyright. They may be viewed, downloaded, or printed from this source but further reproduction or distribution in any format is prohibited without written 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 and Management Program.</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">Technical debt : the cost of doing nothing</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="imported" lang="en_US">2019-07-18T20:30:03Z</dim:field>
   <dim:field mdschema="dspace" element="entity" qualifier="type">Publication</dim:field>
   <dim:field mdschema="mit" element="thesis" qualifier="degree" lang="en_US">Master</dim:field>
   <dim:field mdschema="mit" element="thesis" qualifier="department" lang="en_US">SysDes</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="79c89e56-d18b-4b82-97e8-e4d42d40adb3">
	&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>Technical debt : the cost of doing nothing&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2019&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Page, Austin M.(Austin Markley)&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 and Management Program.&lt;/Keyword>
    &lt;Keyword>System Design and Management Program.&lt;/Keyword>
   	&lt;Abstract>The Air Force is currently paying a cost for the mismanagement of its software development activities. Software-intensive systems are consistently plagued with cost, schedule, and performance issues, which in the current fiscal environment is unsustainable. There has been much research on the benefits of process improvement, yet the concept of product health is largely ignored. Technical debt - the consequence of making short-term design decisions at the expense of long-term health - has been accumulating within code bases as developers and managers struggle to identify, quantify, and manage it properly. In this thesis, an extensive literature search is performed to define technical debt, explain its implications, and highlight methods to quantify and visualize it so organizations can address it explicitly. Through the use of architectural health analysis tools, a set of metrics is defined and used in case studies to highlight the extent to which the Air Force has lost control of its software and the price it has to pay because of it. Ultimately, eleven recommendations are given on how to incorporate architectural health analysis tools into software development activities to prevent, identify, manage, and reduce the amount of technical debt across product lifecycles.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>