<?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-18T21:57:13Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/29158" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/29158</identifier><datestamp>2022-01-13T07:55:19Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>com_1721.1_80738</setSpec><setSpec>com_1721.1_1773</setSpec><setSpec>col_1721.1_131023</setSpec><setSpec>col_1721.1_80739</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">Eric Rebentisch.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Wirthlin, Joseph Robert, 1970-</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="date" qualifier="accessioned">2005-09-27T20:57:51Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2005-09-27T20:57:51Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2000</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2000</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/29158</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">45425494</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, System Design &amp; Management Program, 2000.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Vita.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 291-299).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">An idealized process framework for the front-end of product development was developed. The framework covers the process space from an initial need (or recognition of a need) to the decision for a product/development program launch. The framework focuses on the activities required for the development of requirements needed for a business case decision. The framework was developed through a thorough examination of the literature relating to product development and addresses not only the activities required to traverse the front-end of product development, but also metrics and a process maturity matrix by which an organization's process can be evaluated. Using case studies of the front-end processes of eight commercial organizations and eight military organizations in addition to the US Air Force, the applicability of the framework was tested. All of the organizations demonstrated the existence of the four fundamental activities contained in the framework but a discussion of the existing process enablers revealed various interpretations of required features. The maturity matrix was used to evaluate each of the organizations (commercial and military) relative to an idealized and mature front-end process. The analysis revealed a significant gap between commercial and military process performance. Additionally, the existence and application of the process enablers was significantly correlated with the organization's performance in the four process activities of the front-end framework. The implications of the research indicate that military organizations in general will need to reevaluate the current practices in the front-end and the application of process enablers within their organizations. Further, military organizations should reexamine if the current process structure for system development in the front-end needs significant changes.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Joseph Robert Wirthlin.</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">299 p.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">26261426 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">26261184 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</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">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Best practices in user needs/requirements generation</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="7073b5f4-3b5d-4881-923e-dbed45501556">
	&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>Best practices in user needs/requirements generation&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2000&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Wirthlin, Joseph Robert, 1970-&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>System Design and Management Program.&lt;/Keyword>
   	&lt;Abstract>An idealized process framework for the front-end of product development was developed. The framework covers the process space from an initial need (or recognition of a need) to the decision for a product/development program launch. The framework focuses on the activities required for the development of requirements needed for a business case decision. The framework was developed through a thorough examination of the literature relating to product development and addresses not only the activities required to traverse the front-end of product development, but also metrics and a process maturity matrix by which an organization&amp;apos;s process can be evaluated. Using case studies of the front-end processes of eight commercial organizations and eight military organizations in addition to the US Air Force, the applicability of the framework was tested. All of the organizations demonstrated the existence of the four fundamental activities contained in the framework but a discussion of the existing process enablers revealed various interpretations of required features. The maturity matrix was used to evaluate each of the organizations (commercial and military) relative to an idealized and mature front-end process. The analysis revealed a significant gap between commercial and military process performance. Additionally, the existence and application of the process enablers was significantly correlated with the organization&amp;apos;s performance in the four process activities of the front-end framework. The implications of the research indicate that military organizations in general will need to reevaluate the current practices in the front-end and the application of process enablers within their organizations. Further, military organizations should reexamine if the current process structure for system development in the front-end needs significant changes.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>