<?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-19T03:38:01Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/75491" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/75491</identifier><datestamp>2022-01-13T07:54:12Z</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">Gary Hack.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Krum, Wendy G</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Dept. of Architecture.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Department of Architecture</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2012-12-13T18:36:51Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2012-12-13T18:36:51Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">1981</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">1981</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/75491</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">08176116</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (M. Arch.)--Massachusetts Institute of Technology, Dept. of Architecture, 1981.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">MICROFICHE COPY AVAILABLE IN ARCHIVES AND ROTCH.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">A conservative estimate based on 1975 building construction figures, including residential, office,commercial and factory construction, ascribed two thirds of all building to real estate developers. Yet in their traditional roles as private practitioners, architects have to a great extent been pushed aside or left out of development projects. An inflationary economy has welcomed competition from related businesses such as the "package dealers" who can give guarantees of project cost and delivery time. When involved in development projects, architects have often exercised limited design control, largely due to their late arrival or exclusion from major portions of the decision making process. Recently, many architects have begun to see that to change this pattern, they must broaden the scope of their knowledge, and that by assuming an entrepreneurial role in development projects, they can begin to achieve greater decision making capability and design control within the development process. This thesis first looks at why new roles are emerging within the architectural profession relating to development work, and then looks at new ways in which architects are working with developers. The traditional way of working, utilizing a standard owner-architect agreement, is compared with recent variations to it, which include providing partial architectural services, taking an equity position in a project, participating in a design/build arrangement, and assuming direct responsibility as developer. Three case studies are presented, representing three of these different architect-developer arrangements, which focus on the issues of design control and design process as a function of the professional relationship which the architect assumed in each project. A number of factors were found to contribute to the architect's control over the design and the design process, some or all of which may be applied to, or are intrinsic to, each of the various ways of working. The research concludes with a discussion of the implications for future practice, a description of some of the new roles for architects which have emerged as a result of new ways of working with developers, and addresses the role of education in training architects for development work.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Wendy G. Krum.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">M.Arch.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">v, 156 leaves</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" lang="en_US">http://dspace.mit.edu/handle/1721.1/7582</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Architecture.</dim:field>
   <dim:field mdschema="dc" element="subject" qualifier="lcsh" lang="en_US">Architects</dim:field>
   <dim:field mdschema="dc" element="subject" qualifier="lcsh" lang="en_US">Architecture Vocational guidance</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Architects in the development process : emerging professional roles</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="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="84866677-6dd6-4253-b58f-5e94bc1809bd">
	&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>Architects in the development process : emerging professional roles&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>1981&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Krum, Wendy G&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>Architecture.&lt;/Keyword>
   	&lt;Abstract>A conservative estimate based on 1975 building construction figures, including residential, office,commercial and factory construction, ascribed two thirds of all building to real estate developers. Yet in their traditional roles as private practitioners, architects have to a great extent been pushed aside or left out of development projects. An inflationary economy has welcomed competition from related businesses such as the &amp;quot;package dealers&amp;quot; who can give guarantees of project cost and delivery time. When involved in development projects, architects have often exercised limited design control, largely due to their late arrival or exclusion from major portions of the decision making process. Recently, many architects have begun to see that to change this pattern, they must broaden the scope of their knowledge, and that by assuming an entrepreneurial role in development projects, they can begin to achieve greater decision making capability and design control within the development process. This thesis first looks at why new roles are emerging within the architectural profession relating to development work, and then looks at new ways in which architects are working with developers. The traditional way of working, utilizing a standard owner-architect agreement, is compared with recent variations to it, which include providing partial architectural services, taking an equity position in a project, participating in a design/build arrangement, and assuming direct responsibility as developer. Three case studies are presented, representing three of these different architect-developer arrangements, which focus on the issues of design control and design process as a function of the professional relationship which the architect assumed in each project. A number of factors were found to contribute to the architect&amp;apos;s control over the design and the design process, some or all of which may be applied to, or are intrinsic to, each of the various ways of working. The research concludes with a discussion of the implications for future practice, a description of some of the new roles for architects which have emerged as a result of new ways of working with developers, and addresses the role of education in training architects for development work.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>