<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore"
    xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc"
    rmc:version="7.2.0" xmi:id="-iOn7_gfX_iELWRNGJ2JKPQ"
    name="glossary,_Wn7HcNcEEdqz_d2XWoVt6Q" guid="-iOn7_gfX_iELWRNGJ2JKPQ" changeDate="2007-12-11T15:20:49.853-0800"
    version="1.0.0">
  <mainDescription>&lt;p>&#xD;
    This artifact&amp;nbsp;helps you avoid miscommunication by providing two essential resources:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        A central location to look for terms and abbreviations that are new to development team members&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Definitions of terms that are used in specific ways within the domain&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Definitions for the glossary terms come from several sources, such as requirements documents, specifications, and&#xD;
    discussions with stakeholders and domain experts.&#xD;
&lt;/p></mainDescription>
  <keyConsiderations>&lt;p>&#xD;
    Although listed as an output from, and an input to tasks associated with the requirements discipline, this artifact can&#xD;
    be updated at any time, by any role, as new terms are identified.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The terms defined in here should be used according to the recorded definitions in all project documentation so that all&#xD;
    stakeholders can clearly see that terms are being used consistently.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    One of the primary decisions when developing&amp;nbsp;this artifact&amp;nbsp;is whether to have all terms in a single glossary,&#xD;
    or to maintain terms in a number of glossaries, business terms artifacts and/or models.&amp;nbsp;If terms are defined in&#xD;
    multiple places, you need to communicate all these sources to the team and decide which take precedence.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    It may be important, even in small projects, to reference and use existing broader glossaries, business terms artifacts&#xD;
    or data models, where they exist.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Industry and organizational-wide glossaries may be referenced and compliance with such specific chosen standards may be&#xD;
    required.&#xD;
&lt;/p></keyConsiderations>
  <purpose>&lt;p>&#xD;
    The purposes of&amp;nbsp;this artifact&amp;nbsp;are:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        To record the terms that are being used on the project so that everyone has a common understanding of them&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        To achieve consistency by promoting the use of common terminology across the project&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        To make explicit different stakeholders' use of the same terms to mean different things or different terms to mean&#xD;
        the same thing&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        To provide important terms to the analysis and design team.&#xD;
    &lt;/li>&#xD;
&lt;/ul></purpose>
  <impactOfNotHaving>Misunderstandings about the meanings of data items account for many failed projects. Increased costs and delayed schedules&#xD;
are associated with projects which are continuing without a common understanding of the terms being used.</impactOfNotHaving>
  <reasonsForNotNeeding>&lt;p>&#xD;
    On small projects (e.g. enhancement projects), which are comprised of a team very familiar with the terms, this&#xD;
    artifact may be omitted.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    If a project team has access to the glossary terms in some other form, this&amp;nbsp;artifact may be&#xD;
    disregarded.&amp;nbsp;&amp;nbsp;&lt;br />&#xD;
&lt;/p>&lt;br /></reasonsForNotNeeding>
  <briefOutline>&lt;p>&#xD;
    A project glossary defines the terms used during all phases of the project. There is a short definition for each term.&#xD;
&lt;/p></briefOutline>
  <representationOptions>&lt;p>&#xD;
    This is a simple alphabetized listing of domain terms and their definitions. It can be captured in a spreadsheet,&#xD;
    document, or published on a Wiki site to simplify access and maintenance.&#xD;
&lt;/p></representationOptions>
</org.eclipse.epf.uma:ArtifactDescription>