| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>\openup_basic\workproducts\glossary.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: glossary.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_Wn7HcNcEEdqz_d2XWoVt6Q CRC: 1240688917 -->Glossary<!-- END:presentationName,_Wn7HcNcEEdqz_d2XWoVt6Q --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_Wn7HcNcEEdqz_d2XWoVt6Q CRC: 3150292985 -->This artifact defines important terms used by the project. These terms are the basis for effective collaboration with the stakeholders and other team members.<!-- END:briefDescription,_Wn7HcNcEEdqz_d2XWoVt6Q --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-iOn7_gfX_iELWRNGJ2JKPQ CRC: 1353371380 --><p> |
| The Glossary 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><!-- END:mainDescription,-iOn7_gfX_iELWRNGJ2JKPQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: keyConsiderations<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:keyConsiderations,-iOn7_gfX_iELWRNGJ2JKPQ CRC: 1818373714 --><p> |
| 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. |
| </p> |
| <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><!-- END:keyConsiderations,-iOn7_gfX_iELWRNGJ2JKPQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: purpose<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:purpose,-iOn7_gfX_iELWRNGJ2JKPQ CRC: 1386461132 -->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 system. |
| <!--StartFragment --> |
| The goal is not to record all possible terms, but only those |
| that are unclear, ambiguous, or require elaboration.<!-- END:purpose,-iOn7_gfX_iELWRNGJ2JKPQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: impactOfNotHaving<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:impactOfNotHaving,-iOn7_gfX_iELWRNGJ2JKPQ CRC: 1584332027 -->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.<!-- END:impactOfNotHaving,-iOn7_gfX_iELWRNGJ2JKPQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: representationOptions<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:representationOptions,-iOn7_gfX_iELWRNGJ2JKPQ CRC: 1782748874 --><p> |
| The Glossary is a simple alphabetized listing of domain terms and their definitions. It can be captured in a |
| spreadheet, document, or published on a Wiki site to simplify access and maintenance. |
| </p><!-- END:representationOptions,-iOn7_gfX_iELWRNGJ2JKPQ --> |
| </body> |
| </html> |