<?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-19T13:30:22Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/107609" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/107609</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">Donna H. Rhodes.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Lee, Michael N</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Engineering Systems Division.</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="contributor" qualifier="department" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2017-03-20T19:42:22Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2017-03-20T19:42:22Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2016</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2016</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/107609</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">974918643</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, School of Engineering, System Design and Management Program, Engineering and Management Program, 2016.</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 (pages 102-107).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">The United States has achieved defense superiority in air, land, and sea while using some of the most advanced defense systems in the world. However, underlying this success is a troubled procurement system. Enterprise-wide problems such as poor integration between the three components (JCIDS, DAS, PPBE) of DoD acquisition and inadequate management of procurement personnel have undermined the potential of the Department of Defense. One particular area for improvement is the need for understanding the overlaps, gaps, and interdependencies of the capability portfolio. Information is a precondition to attaining that knowledge. Information is embodied in capability documents and architecture frameworks and drives the critical process of determining the right capability requirements upfront, a vital task in saving costs. (Wirthlin, 1994) The stakeholders need a comprehensive understanding of the capability portfolio during this validation process but information can be trapped in functional stovepipes. DoD Architecture Framework (DoDAF) holds much promise in enhancing the visibility and traceability of information in the capability portfolio to the stakeholders. It is a more structured way to capture and analyze information than free-text documents. The most recent JCIDS manual published in February 2015 added a new requirement to submit seven DoDAF viewpoints during the ICD submission. This indicates the potential of DoDAF viewpoints to be able to provide a full representation of a capability requirement so it can be validated in light of a holistic understanding of the portfolio. The purpose of this thesis is to analyze whether DoDAF alone can provide a holistic understanding of a capability requirement during this early front-end validation. The analysis examines the information captured by the viewpoints by comparing it to ICD information requirements. The results of the analysis reveal the benefits of DoDAF in its ability to capture more detailed information such as resource flows in structured form. A second finding revealed that the seven DoDAF viewpoints were missing key information elements about the capability requirement such as related missions and strategy documents that limit holistic visibility of the capability portfolio. Lastly, there were additional limitations such as the challenge of determining the level of specificity in the viewpoints. Recommendations include changing particular optional data fields to mandatory and adding the CV-1 and OV-3 viewpoints to provide more information about the capability requirement.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Michael N. Lee.</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="format" qualifier="extent" lang="en_US">107 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="subject" lang="en_US">Engineering Systems Division.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Information capture during early front end analysis in the Joint Capabilities Integration and Development System (JCIDS) : a formative study of the capabilities of the Department of Defense Architecture Framework (DoDAF)</dim:field>
   <dim:field mdschema="dc" element="title" qualifier="alternative" lang="en_US">Formative study of the capabilities of the Department of Defense Architecture Framework (DoDAF)</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="0db9b771-248d-4dc4-9291-428a7be7c8e4">
	&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>Information capture during early front end analysis in the Joint Capabilities Integration and Development System (JCIDS) : a formative study of the capabilities of the Department of Defense Architecture Framework (DoDAF)&lt;/Title>
   	&lt;Subtitle>Formative study of the capabilities of the Department of Defense Architecture Framework (DoDAF)&lt;/Subtitle>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2016&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Lee, Michael N&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;Keyword>Engineering Systems Division.&lt;/Keyword>
   	&lt;Abstract>The United States has achieved defense superiority in air, land, and sea while using some of the most advanced defense systems in the world. However, underlying this success is a troubled procurement system. Enterprise-wide problems such as poor integration between the three components (JCIDS, DAS, PPBE) of DoD acquisition and inadequate management of procurement personnel have undermined the potential of the Department of Defense. One particular area for improvement is the need for understanding the overlaps, gaps, and interdependencies of the capability portfolio. Information is a precondition to attaining that knowledge. Information is embodied in capability documents and architecture frameworks and drives the critical process of determining the right capability requirements upfront, a vital task in saving costs. (Wirthlin, 1994) The stakeholders need a comprehensive understanding of the capability portfolio during this validation process but information can be trapped in functional stovepipes. DoD Architecture Framework (DoDAF) holds much promise in enhancing the visibility and traceability of information in the capability portfolio to the stakeholders. It is a more structured way to capture and analyze information than free-text documents. The most recent JCIDS manual published in February 2015 added a new requirement to submit seven DoDAF viewpoints during the ICD submission. This indicates the potential of DoDAF viewpoints to be able to provide a full representation of a capability requirement so it can be validated in light of a holistic understanding of the portfolio. The purpose of this thesis is to analyze whether DoDAF alone can provide a holistic understanding of a capability requirement during this early front-end validation. The analysis examines the information captured by the viewpoints by comparing it to ICD information requirements. The results of the analysis reveal the benefits of DoDAF in its ability to capture more detailed information such as resource flows in structured form. A second finding revealed that the seven DoDAF viewpoints were missing key information elements about the capability requirement such as related missions and strategy documents that limit holistic visibility of the capability portfolio. Lastly, there were additional limitations such as the challenge of determining the level of specificity in the viewpoints. Recommendations include changing particular optional data fields to mandatory and adding the CV-1 and OV-3 viewpoints to provide more information about the capability requirement.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>