<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-2OU2wQP_WNWX5zzWzx4ANw" name="metaphor_system_of_names,4.884861766532753E-306" guid="-2OU2wQP_WNWX5zzWzx4ANw" changeDate="2006-11-08T16:24:49.021-0800" version="1.0.0">
  <mainDescription>&lt;a id=&quot;XE_xp__metaphor_(system_of_names)&quot; name=&quot;XE_xp__metaphor_(system_of_names)&quot;&gt;&lt;/a&gt;&lt;a
id=&quot;XE_metaphor_(system_of_names)__practice_of&quot; name=&quot;XE_metaphor_(system_of_names)__practice_of&quot;&gt;&lt;/a&gt;&lt;a
id=&quot;XE_engineering_practices__metaphor_(system_of_names)&quot; name=&quot;XE_engineering_practices__metaphor_(system_of_names)&quot;&gt;&lt;/a&gt; 
&lt;h3&gt;
    Description
&lt;/h3&gt;
&lt;p&gt;
    This metaphor is a design overview. It is a way of defining the system using a commonly understandable vocabulary with
    its associated relationships. It allows the whole team to talk about the structure of the software in a convenient and
    memorable way. A good metaphor is one that all team members can understand easily, remember, and always keep in the
    back of their minds. It provides a unifying direction that developers can follow as they build the system a small piece
    at a time.
&lt;/p&gt;
&lt;p&gt;
    Metaphors are not always easy to find at the start of a project. In that case, teams can simply identify the key
    objects and their interactions in the system (System of Names). The real metaphor might emerge later on. When everybody
    on the team can explain quickly the system through its major objects and their interactions, the goal has been reached.
&lt;/p&gt;
&lt;p&gt;
    The iterative nature of XP causes the architecture of our system to evolve over time. The metaphor is not static; it
    will change and hopefully improve over time as our understanding of the system improves.
&lt;/p&gt;
&lt;p&gt;
    An example of a metaphor would be something like: &quot;It's like a subway system with passengers and stations, tickets and
    turnstiles, etc.&quot;.
&lt;/p&gt;
&lt;h3&gt;
    Benefits
&lt;/h3&gt;
&lt;ul&gt;
    &lt;li&gt;
        &lt;b&gt;Communication&lt;/b&gt;: customer and developer define a common language they can use to talk about the system.
    &lt;/li&gt;
    &lt;li&gt;
        &lt;b&gt;Direction&lt;/b&gt;: the metaphor helps guide the developers towards the solution.
    &lt;/li&gt;
&lt;/ul&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>