| <?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><a id="XE_xp__metaphor_(system_of_names)" name="XE_xp__metaphor_(system_of_names)"></a><a |
| id="XE_metaphor_(system_of_names)__practice_of" name="XE_metaphor_(system_of_names)__practice_of"></a><a |
| id="XE_engineering_practices__metaphor_(system_of_names)" name="XE_engineering_practices__metaphor_(system_of_names)"></a> |
| <h3> |
| Description |
| </h3> |
| <p> |
| 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. |
| </p> |
| <p> |
| 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. |
| </p> |
| <p> |
| 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. |
| </p> |
| <p> |
| An example of a metaphor would be something like: "It's like a subway system with passengers and stations, tickets and |
| turnstiles, etc.". |
| </p> |
| <h3> |
| Benefits |
| </h3> |
| <ul> |
| <li> |
| <b>Communication</b>: customer and developer define a common language they can use to talk about the system. |
| </li> |
| <li> |
| <b>Direction</b>: the metaphor helps guide the developers towards the solution. |
| </li> |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |