<?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-22T21:43:29Z</responseDate><request verb="GetRecord" identifier="oai:uwspace.uwaterloo.ca:10012/4001" metadataPrefix="dim">https://dspacemainprd01.lib.uwaterloo.ca/server/oai/request</request><GetRecord><record><header><identifier>oai:uwspace.uwaterloo.ca:10012/4001</identifier><datestamp>2017-03-21T16:57:03Z</datestamp><setSpec>com_10012_9924</setSpec><setSpec>com_10012_1</setSpec><setSpec>col_10012_9930</setSpec><setSpec>col_10012_6</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:doc="http://www.lyncode.com/xoai" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="author" authority="c171df9f-2b39-4e6a-b9bb-00cc8c18e3c1" confidence="600">Dong, Xinyi</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2008-09-22T17:59:35Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2008-09-22T17:59:35Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued">2008-09-22T17:59:35Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="submitted">2008-09-17</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/10012/4001</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en">An object-oriented software system is composed of a collection of&#xd;
communicating objects that co-operate with one another to achieve some desired&#xd;
goals. The object is the basic unit of abstraction in an OO program; objects&#xd;
may model real-world entities or internal abstractions of the system. Similar&#xd;
objects forms classes, which encapsulate the data and operations performed on&#xd;
the data. Therefore, extracting, analyzing, and modelling classes/objects and&#xd;
their relationships is of key importance in understanding and maintaining&#xd;
object-oriented software systems. However, when dealing with large and complex&#xd;
object-oriented systems, maintainers can easily be overwhelmed by the vast&#xd;
number of classes/objects and the high degree of interdependencies among them.&#xd;
&#xd;
In this thesis, we propose a new model, which we call the Hybrid Model, to&#xd;
represent object-oriented systems at a coarse-grained level of abstraction. To&#xd;
promote the comprehensibility of objects as independent units, we group the&#xd;
complete static description of software objects into aggregate components. Each&#xd;
aggregate component logically represents a set of objects, and the components&#xd;
interact with one other through explicitly defined ports.&#xd;
&#xd;
We present and discuss several applications of the Hybrid Model in reverse&#xd;
engineering and software evolution.&#xd;
&#xd;
The Hybrid Model can be used to support a divide-and-conquer comprehension&#xd;
strategy for program comprehension. At a low level of abstraction, maintainers&#xd;
can focus on one aggregate-component at a time, while at a higher level, each&#xd;
aggregate component can be understood as a whole and be mapped to&#xd;
coarse-grained design abstractions, such as subsystems.&#xd;
&#xd;
Based on the new model, we further propose a set of dependency analysis&#xd;
methods. The analysis results reveal the external properties of aggregate&#xd;
components, and lead to better understand the nature of their&#xd;
interdependencies.&#xd;
&#xd;
In addition, we apply the new model in software evolution analysis. We identify&#xd;
a collection of change patterns in terms of changes in aggregate components and&#xd;
their interrelationships. These patterns help to interpret how an evolving&#xd;
system changes at the architectural level, and provides valuable information to&#xd;
understand why the system is designed as the way it is.</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso" lang="en">en</dim:field>
   <dim:field mdschema="dc" element="publisher" lang="en">University of Waterloo</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en">object-oriented</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en">reverse engineering</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en">software evolution</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en">software architecture</dim:field>
   <dim:field mdschema="dc" element="subject" qualifier="program" lang="en">Computer Science (Software Engineering)</dim:field>
   <dim:field mdschema="dc" element="title" lang="en">A Hybrid Model for Object-Oriented Software Maintenance</dim:field>
   <dim:field mdschema="dc" element="type" lang="en">Doctoral Thesis</dim:field>
   <dim:field mdschema="dc" element="pending" lang="en">false</dim:field>
   <dim:field mdschema="uws-etd" element="degree" qualifier="department" lang="en">School of Computer Science</dim:field>
   <dim:field mdschema="uws-etd" element="degree" lang="en">Doctor of Philosophy</dim:field>
   <dim:field mdschema="uws" element="typeOfResource" lang="en">Text</dim:field>
   <dim:field mdschema="uws" element="peerReviewStatus" lang="en">Unreviewed</dim:field>
   <dim:field mdschema="uws" element="scholarLevel" lang="en">Graduate</dim:field>
   <dim:field mdschema="others" element="access-status">open.access</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>