<?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-11-21T02:02:48Z</responseDate><request verb="GetRecord" identifier="oai:macsphere.mcmaster.ca:11375/27262" metadataPrefix="dim">https://prod-ms-be.lib.mcmaster.ca/server/oai/request</request><GetRecord><record><header><identifier>oai:macsphere.mcmaster.ca:11375/27262</identifier><datestamp>2026-09-24T01:28:12Z</datestamp><setSpec>com_11375_271</setSpec><setSpec>col_11375_272</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">Anand, Christopher</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author">Hosseinkord, Maryam</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">Computer Science</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2022-01-04T21:03:58Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2022-01-04T21:03:58Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued">2021</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/11375/27262</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">https://doi.org/10.71548/14133</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">How can observation of a legacy system be used for design? To answer this question, we observed a teacher doing live coding with a conventional code editor and used the observations to design an editor better suited to this style of teaching. In particular, we found strong evidence that a projectional editor would better meet this need. Reflecting on this experience, we describe two types of requirements which can be inferred from observing a user using a legacy system: hidden requirements, in which users use existing features in unexpected ways, and novel requirements inferred from pain points observed in current system use.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degreetype" lang="en_US">Thesis</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">Master of Applied Science (MASc)</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso" lang="en_US">en</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Projectional Editors</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Code Editors</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Design Thinking</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Designing a Projectional Editor for Live Coding Using Design Thinking to Improve Teaching</dim:field>
   <dim:field mdschema="dc" element="type" lang="en_US">Thesis</dim:field>
   <dim:field mdschema="others" element="access-status">open.access</dim:field>
</dim:dim></metadata></record></GetRecord></OAI-PMH>