<?xml version="1.0"?>
<api>
  <query>
    <search>
      <p ns="0" title="JITAS Design Study" snippet="This simply hides the fact that the password gets encrypted, &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; classes (Tutor) can make new Students without knowing about Encryption. I c&#10;" size="34281" wordcount="4952" timestamp="2010-11-25T03:11:51Z" />
      <p ns="0" title="Model the real world" snippet="...icleAndRoadController&#039;&#039; probably isn&#039;t very good. A class name that has no &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; outside of the computer program may be a sign you are not modeling the real&#10;" size="1442" wordcount="239" timestamp="2010-11-25T03:11:57Z" />
      <p ns="0" title="Flyweight" snippet="* object identity is not important for the application, &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; that the application will work the same if objects are shared rather than i&#10;" size="4505" wordcount="702" timestamp="2010-11-25T03:23:06Z" />
      <p ns="0" title="Coupling and cohesion" snippet="...ne module modifies or relies on the internal workings of the other module, &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; that changes to the latter module will cause changes to the dependent modul&#10;" size="7140" wordcount="1071" timestamp="2010-11-25T03:21:45Z" />
      <p ns="0" title="Model the room" snippet="Somewhat unrelatedly, I would argue that modelling a room has no &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; or point without an idea of what you are modelling the room for. The point &#10;" size="736" wordcount="122" timestamp="2010-10-21T00:57:40Z" />
      <p ns="0" title="Facade" snippet="...ade makes subsystems easier to use because it provides a simple interface, &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; that clients do not need to access and understand subsystem objects. &#10;* It decouples the subsystem from its clients, &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; that the subsystem can be modified without affecting clients.&#10;" size="3029" wordcount="460" timestamp="2010-11-25T03:22:16Z" />
      <p ns="0" title="2008 Exam answers" snippet="...the coupling between those parts of the system and the rest of the system, &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; that the rest of the system will not need to change if the encapsulated par&#10;" size="20169" wordcount="3132" timestamp="2010-11-25T03:17:36Z" />
      <p ns="0" title="BaseBean" snippet="*This practice also confuses the &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; of the domain class and pollutes it with methods that are not really part o&#10;" size="2415" wordcount="389" timestamp="2010-11-25T03:05:54Z" />
      <p ns="0" title="Janina&#039;s Design Study" snippet="...t. A constraint on my project was that I could not modify the code in JST, &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; that I could not add the behavior I needed to JST classes. Therefore, using&#10;" size="45384" wordcount="7435" timestamp="2009-09-22T08:58:54Z" />
      <p ns="0" title="Aidan&#039;s Design Study" snippet="..., and so on in alternating order.  This requires the view to interpret the &lt;span class=&#039;searchmatch&#039;&gt;meaning&lt;/span&gt; of each token.  If this representation were to change, the view would also &#10;" size="50067" wordcount="7782" timestamp="2009-10-04T20:20:05Z" />
    </search>
  </query>
  <query-continue>
    <search sroffset="10" />
  </query-continue>
</api>