<?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-18T22:04:31Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/40308" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/40308</identifier><datestamp>2022-02-01T18:45:33Z</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">Edward F. Crawley.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Cameron, Bruce G. (Bruce Gregory)</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Technology and Policy Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Department of Aeronautics and Astronautics</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Engineering Systems Division</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Technology and Policy Program</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2008-02-27T20:37:10Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2008-02-27T20:37:10Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2007</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2007</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/40308</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">191672900</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of Aeronautics and Astronautics; and, (S.M.)--Massachusetts Institute of Technology, Engineering Systems Division, Technology and Policy Program, 2007.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">This electronic version was submitted by the student author.  The certified thesis is available in the Institute Archives and Special Collections.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 167-170).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">In the design of complex systems serving a broad group of stakeholders, it can be difficult to prioritize objectives for the architecture. I postulate that it is possible to make architectural decisions based on consideration of stakeholder value delivery, in order to help prioritize objectives. I introduce the concept of value network models to map out the indirect benefit delivered to stakeholders. A numerical methodology for prioritizing paths through this network model is presented, with a view to discovering the most important organizational outputs. I show how value network models can be linked to architecture models to provide decision support to the architect. I present a case study to examine the connectivity and sensitivity of a test architecture to value delivery. I conclude that a limited subset of NASA's outputs will discriminate between architectures. In this manner, I show how value considerations can be used to structure the design space before critical technical decisions are made to narrow it. A number of organizational implications for value delivery are generated from this analysis. In particular, I show that benefit flows should be aligned to organizational processes and responsibilities, and that failure to map stakeholder input to architecture evaluation can weaken benefit.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Bruce G. Cameron.</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">170 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">http://dspace.mit.edu/handle/1721.1/7582</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Aeronautics and Astronautics.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Technology and Policy Program.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Value network modeling : a quantitative method for comparing benefit across exploration architectures</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="ccb444dc-9509-4f6b-9d70-cfb0b0c4b536">
	&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>Value network modeling : a quantitative method for comparing benefit across exploration architectures&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2007&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Cameron, Bruce G. (Bruce Gregory)&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>Aeronautics and Astronautics.&lt;/Keyword>
    &lt;Keyword>Technology and Policy Program.&lt;/Keyword>
   	&lt;Abstract>In the design of complex systems serving a broad group of stakeholders, it can be difficult to prioritize objectives for the architecture. I postulate that it is possible to make architectural decisions based on consideration of stakeholder value delivery, in order to help prioritize objectives. I introduce the concept of value network models to map out the indirect benefit delivered to stakeholders. A numerical methodology for prioritizing paths through this network model is presented, with a view to discovering the most important organizational outputs. I show how value network models can be linked to architecture models to provide decision support to the architect. I present a case study to examine the connectivity and sensitivity of a test architecture to value delivery. I conclude that a limited subset of NASA&amp;apos;s outputs will discriminate between architectures. In this manner, I show how value considerations can be used to structure the design space before critical technical decisions are made to narrow it. A number of organizational implications for value delivery are generated from this analysis. In particular, I show that benefit flows should be aligned to organizational processes and responsibilities, and that failure to map stakeholder input to architecture evaluation can weaken benefit.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>