<?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-19T16:52:49Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/72253" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/72253</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">Ranko Bon.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Cavoulakos, Constantin Elias</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-08-21T15:41:23Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2012-08-21T15:41:23Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">1987</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">1987</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/72253</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">16972431</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (M.S.)--Massachusetts Institute of Technology, Dept. of Architecture, 1987.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 59-60).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">The architectural office of the end of the eighties has been equipped with computers, in an effort to anticipate the needs of the modem working environment and to enhance the informational flow between the various disciplines of modern practice. A basic concern for the architect in the computerized office, is not what is commonly thought, to probe the limits of the machine, or to explore the sophistication of the software in use; rather it is to grasp how the computer affects performance at work, altering the traditional hierarchy of our perception and decision making, in order to strengthen productivity by changing the traditional organization of architectural practice. Development of design software enhances the man-machine interface, encouraging the architect to work directly on the machine, leading towards a true integration of the computer in the practice. While a small computer team, composed by CADD specialists, initially supported the computer facilities in architectural practice, it is particularly important to demonstrate that every professional should be able to access, and work directly on the computer, adding to the dissemination of technical knowledge within the team and of the benefits of the efficiency of the electronic tool. This is beneficial to both the designers of the firm, who are able to minimise redundancy in the creation of graphic documents, and to the CADD support team of the office, that can concentrate in research and development of an increasingly powerful computer-aided design environment. Integrating CADD in architectural practice depends on the organization of the particular office. A crucial question for the architect and the central topic of this thesis is how to put designers at work in front of the screen, and how to control decision making within the CADD environment. My goal is to describe the various issues involved and to suggest a direction in the implementation of CADD in the architectural office. Keywords: CADD, Representations, Horizontal Organization, Vertical Organization, Multi-disciplinarity, Integration, Architectural Practice.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Constantin Elias Cavoulakos.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">M.S.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">60 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" 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="title" lang="en_US">CADD : on reorganizing the practice of architecture</dim:field>
   <dim:field mdschema="dc" element="title" qualifier="alternative" lang="en_US">Computer aided design and drafting : on reorganizing the practice of architecture</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="b97334ea-4c94-4d73-a7d3-2943c82ddcf8">
	&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>CADD : on reorganizing the practice of architecture&lt;/Title>
   	&lt;Subtitle>Computer aided design and drafting : on reorganizing the practice of architecture&lt;/Subtitle>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>1987&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Cavoulakos, Constantin Elias&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>The architectural office of the end of the eighties has been equipped with computers, in an effort to anticipate the needs of the modem working environment and to enhance the informational flow between the various disciplines of modern practice. A basic concern for the architect in the computerized office, is not what is commonly thought, to probe the limits of the machine, or to explore the sophistication of the software in use; rather it is to grasp how the computer affects performance at work, altering the traditional hierarchy of our perception and decision making, in order to strengthen productivity by changing the traditional organization of architectural practice. Development of design software enhances the man-machine interface, encouraging the architect to work directly on the machine, leading towards a true integration of the computer in the practice. While a small computer team, composed by CADD specialists, initially supported the computer facilities in architectural practice, it is particularly important to demonstrate that every professional should be able to access, and work directly on the computer, adding to the dissemination of technical knowledge within the team and of the benefits of the efficiency of the electronic tool. This is beneficial to both the designers of the firm, who are able to minimise redundancy in the creation of graphic documents, and to the CADD support team of the office, that can concentrate in research and development of an increasingly powerful computer-aided design environment. Integrating CADD in architectural practice depends on the organization of the particular office. A crucial question for the architect and the central topic of this thesis is how to put designers at work in front of the screen, and how to control decision making within the CADD environment. My goal is to describe the various issues involved and to suggest a direction in the implementation of CADD in the architectural office. Keywords: CADD, Representations, Horizontal Organization, Vertical Organization, Multi-disciplinarity, Integration, Architectural Practice.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>