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