Glossary
The Glossary pattern creates a link to the Project Glossary where terms and their definitions can be entered. This allows the terms to be used when modeling by including the terms as hyperlinks from elements notes. Another, and perhaps more flexible method is to model the terms as UML Class elements and to add definitions as element notes. 

Figure 1. Shows a Custom diagram that contains a link to the Project glossary.

Discussion
The purpose of the pattern is to create a common and accepted vocabulary (lexicon) for the team so that all team members and other stakeholders who view the models are on the same page with respect to the meanings of terms. The most straight forward method of working with Glossary items is to record them in the Project Glossary which allows terms to be grouped by user defined types.
The alternative way is to model the terms and their relationships as UML Classes, this provides flexibility as additional fields can be entered against each term including system defined properties such as status and user defined terms defined by Tagged Values.
Both methods allow the terms to be accessed by model users and also included in documentation.

The following is a list of some things you may want to do when working with this pattern.
·	Define your own types for the Project Glossary.
Enter terms and their types and definitions into the Project Glossary.
Change the name of the name of the Package and the diagram for the Element terms.
Change the name of the Classes and their notes that define the terms and their definitions

The following is a list of some of the next steps available when applying the pattern.
·	Generate documentation that focuses on the terms and their definitions.
Create hyperlinks from other elements notes to the terms defined in the glossary.
Reference
The following help topics will assist you learn about how to work with this pattern.
Glossary
Model Glossary
Business Analysis Body of Knowledge (BABOK)
Traceability Tools
Documentation

The following are some of the tools that will be helpful when working with this pattern.
Document Generator
The Document Generator is a powerful facility in Enterprise Architect that allows a Database Engineer or other stakeholder to create high quality corporate or technical documentation directly from the model, suitable for internal or external audiences. For more details see the Documentation help topic or the more general topic on Model Publishing.
Element Discussions
The Element Discussion facility is a fully featured collaboration tool allowing modelers and model viewers and reviewers to communicate with each other directly inside the repository. Modelers using the full client or occasional viewers using WebEA can both post and reply to discussions and communicate and engage in chat. For more details see the Element Discussions help topic.
Specification View
The Specification View can be used as a way of working with any element type in a spreadsheet or word process view. It is particularly useful when there are a large number of elements as is typically the case when describing a system of any appreciable size. For more details see the Specification View help topic.
Relationship Matrix
The Relationship Matrix provides a spreadsheet like view of two groups of elements and the relationships that exist between them. It can be a used as a powerful analysis mechanism to visually indicate how elements are related to each other and to discover which elements are missing relationships. For more details see the Relationship Matrix  help topic.
Traceability Window
The Traceability Window automatically displays the relationships that exist between Use Cases and other model elements including up-process and down-process elements. The traceability tree view can be conveniently expanded to see deeper relationships and elements displayed in the window can be located in all diagrams in which they appear. For more details see the Traceability Window  help topic.

© 2000 - 2018  Sparx Systems Pty Ltd.  All rights Reserved.