<?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-20T11:16:21Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/127176" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/127176</identifier><datestamp>2022-01-31T19:03:57Z</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">Nancy G. Leveson.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Muramoto, Dylan Toshinari.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Institute for Data, Systems, and Society.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Technology and Policy Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Department of Aeronautics and Astronautics.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">Massachusetts Institute of Technology. Institute for Data, Systems, and Society</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">Massachusetts Institute of Technology. Department of Aeronautics and Astronautics</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">Technology and Policy 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">2020-09-03T18:47:59Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2020-09-03T18:47:59Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2020</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2020</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">https://hdl.handle.net/1721.1/127176</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">1191839810</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M., Massachusetts Institute of Technology, School of Engineering, Institute for Data, Systems, and Society, May, 2020</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M., Massachusetts Institute of Technology, Department of Aeronautics and Astronautics, May, 2020</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Cataloged from the official PDF of thesis.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (pages 57-60).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">In order to adapt and respond to threats by near-peer-adversaries that are changing at an increasing pace, the U.S. Department of Defense (DoD) has been focused on reforming software acquisition for rapid development and deployment of software capabilities to the battlefield. Military leaders have been focused on accelerating development and increasing the frequency of deployment, encouraging developers to take risks to reduce schedules. However, military systems have certain levels of performance and quality requirements that must be met to successfully execute missions. Additionally, software systems have many different characteristics that must be considered during development. In this thesis, the DoD software acquisition process and new guidance from the Department and the U.S. Air Force (USAF) regarding software acquisition reforms are detailed first. The existing policy is examined to identify gaps regarding tailoring development processes to different software systems. After providing context on how software is developed and describing four process models to show that different processes are most appropriate for developing systems with certain characteristics, eight specific software system characteristics are identified: user, urgency, lifespan, performance (timing), quality/risk, size, integration, and requirements. Furthermore, recommendations to the USAF and DoD for implementing policy/guidelines that help establish a tailorable software acquisition process based on these eight system characteristics are provided. This thesis hopes to help leaders and managers understand the technical characteristics of software systems and match those with appropriate development process designs and practices, instead of a one-size-fits-all blanket solution, so that the required quality and evolvability of military systems are not compromised in execution of the national security mission.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Dylan Toshinari Muramoto.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="collection" lang="en_US">S.M. Massachusetts Institute of Technology, School of Engineering, Institute for Data, Systems, and Society</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="collection" lang="en_US">S.M. Massachusetts Institute of Technology, Department of Aeronautics and Astronautics</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">60 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 may be protected by copyright. Please reuse MIT thesis content according to the MIT Libraries Permissions Policy, which is available through the URL provided.</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">Institute for Data, Systems, and Society.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Technology and Policy Program.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Aeronautics and Astronautics.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Tailorability-focused recommendations for United States Air Force software acquisition policy</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">2020-09-03T18:47:59Z</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">ESD</dim:field>
   <dim:field mdschema="mit" element="thesis" qualifier="department" lang="en_US">IDSS</dim:field>
   <dim:field mdschema="mit" element="thesis" qualifier="department" lang="en_US">Aero</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="aee07e6d-a1b9-4cd3-ab82-f43b569ed576">
	&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>Tailorability-focused recommendations for United States Air Force software acquisition policy&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2020&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Muramoto, Dylan Toshinari.&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>Institute for Data, Systems, and Society.&lt;/Keyword>
    &lt;Keyword>Technology and Policy Program.&lt;/Keyword>
    &lt;Keyword>Aeronautics and Astronautics.&lt;/Keyword>
   	&lt;Abstract>In order to adapt and respond to threats by near-peer-adversaries that are changing at an increasing pace, the U.S. Department of Defense (DoD) has been focused on reforming software acquisition for rapid development and deployment of software capabilities to the battlefield. Military leaders have been focused on accelerating development and increasing the frequency of deployment, encouraging developers to take risks to reduce schedules. However, military systems have certain levels of performance and quality requirements that must be met to successfully execute missions. Additionally, software systems have many different characteristics that must be considered during development. In this thesis, the DoD software acquisition process and new guidance from the Department and the U.S. Air Force (USAF) regarding software acquisition reforms are detailed first. The existing policy is examined to identify gaps regarding tailoring development processes to different software systems. After providing context on how software is developed and describing four process models to show that different processes are most appropriate for developing systems with certain characteristics, eight specific software system characteristics are identified: user, urgency, lifespan, performance (timing), quality/risk, size, integration, and requirements. Furthermore, recommendations to the USAF and DoD for implementing policy/guidelines that help establish a tailorable software acquisition process based on these eight system characteristics are provided. This thesis hopes to help leaders and managers understand the technical characteristics of software systems and match those with appropriate development process designs and practices, instead of a one-size-fits-all blanket solution, so that the required quality and evolvability of military systems are not compromised in execution of the national security mission.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>