blob: 5cb0aa13fea3d4206819d4106b0034594e4dbf1d [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="" xmlns:org.eclipse.epf.uma="" epf:version="1.0.0" xmi:id="-iOn7_gfX_iELWRNGJ2JKPQ" name="glossary,_Wn7HcNcEEdqz_d2XWoVt6Q" guid="-iOn7_gfX_iELWRNGJ2JKPQ" changeDate="2006-12-21T14:23:00.396-0500" version="1.0.0">
The Glossary helps you avoid miscommunication by providing two essential resources:
A central location to look for terms and abbreviations that are new to development team members
Definitions of terms that are used in specific ways within the domain
Definitions for the Glossary terms come from several sources, such as requirements documents, specifications, and
discussions with Stakeholders and domain experts.
In some projects that do not involve business or domain modeling, the Glossary is the primary artifact for capturing
information about the project's business domain.
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.
<purpose>The goal is for the Glossary to provide a common
vocabulary agreed upon by all Stakeholders. It can
help people from different functional groups reach a mutual
understanding of the&amp;nbsp;system.
&lt;!--StartFragment --&gt;
The goal is not to record all possible terms, but only those
that are unclear, ambiguous, or require elaboration.</purpose>
<impactOfNotHaving>Misunderstandings about the meanings of data items account for many failed projects.
Some of them become obvious only in the late stages of system testing and can
be extremely expensive to correct.</impactOfNotHaving>
The Glossary is a simple alphabetized listing of domain terms and their definitions.&amp;nbsp; It can be captured in a
spreadheet,&amp;nbsp;document, or&amp;nbsp;published on a Wiki site to simplify access and maintenance.