<?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:25:12Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/79944" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/79944</identifier><datestamp>2022-01-13T07:53:53Z</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">Harvey Bryan.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Fergle, Ronald</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Department 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">2013-08-22T18:40:47Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2013-08-22T18:40:47Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">1986</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">1986</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/79944</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">15466773</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (M.S.)--Massachusetts Institute of Technology, Dept. of Architecture, 1986.</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 (leaves 73-74).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">The influence of the computer is increasing within the architectural profession. One aspect of this is the growing use of microcomputer programs in architectural education. Many of these programs have their roots in the engineering disciplines, and therefore their procedural methodology may no t be compatible with the architectural design process. In addition to this, most of the programs used in the universities are originally designed for the professional practitioner, and may not be appropriate for the academic environment This discussion explores the characteristics of the architectural design process, and what issues programmers need to address when writing software for use by designers. More specifically, how should the programmer approach designing educational software, so that the computer becomes a more effective tool in enabling the student to develop heuristic knowledge about some aspect of architectural design. The programming factors that influence the effectiveness of this type of educational software include: the appropriate use of graphics, flexible input/output sequences, procedural transparency of the program structure, and the iterative comparison of design options. These concepts are analyzed in a series of programming examples involving energy analysis and daylighting analysis. Existing programs are critiqued, and suggestions for improvements are made. The use of processors to facilitate the testing and comparison of results are presented, as well as guidelines for additional developments using knowledge base overlays.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Ronald Fergle.</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">76 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="title" lang="en_US">Improving the computer interface in architectural education</dim:field>
   <dim:field mdschema="dc" element="title" qualifier="alternative" lang="en_US">Architectural education, Improving the computer interface in</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="ad5c249c-a3df-404b-9a8a-a55ac1e3502f">
	&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>Improving the computer interface in architectural education&lt;/Title>
   	&lt;Subtitle>Architectural education, Improving the computer interface in&lt;/Subtitle>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>1986&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Fergle, Ronald&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 influence of the computer is increasing within the architectural profession. One aspect of this is the growing use of microcomputer programs in architectural education. Many of these programs have their roots in the engineering disciplines, and therefore their procedural methodology may no t be compatible with the architectural design process. In addition to this, most of the programs used in the universities are originally designed for the professional practitioner, and may not be appropriate for the academic environment This discussion explores the characteristics of the architectural design process, and what issues programmers need to address when writing software for use by designers. More specifically, how should the programmer approach designing educational software, so that the computer becomes a more effective tool in enabling the student to develop heuristic knowledge about some aspect of architectural design. The programming factors that influence the effectiveness of this type of educational software include: the appropriate use of graphics, flexible input/output sequences, procedural transparency of the program structure, and the iterative comparison of design options. These concepts are analyzed in a series of programming examples involving energy analysis and daylighting analysis. Existing programs are critiqued, and suggestions for improvements are made. The use of processors to facilitate the testing and comparison of results are presented, as well as guidelines for additional developments using knowledge base overlays.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>