Questions about the workflow between Textual Analysis and Glossary, and the behavior of Synonym/Ignore

General Questions/Discussions
1

Hello VP Team,

I am currently exploring Visual Paradigm for modeling legal documents and regulations. So far, I have found both Textual Analysis and the Glossary to be very useful.

However, after reading the official tutorials, I noticed that they mainly demonstrate how to add Terms from Textual Analysis. I could not find any documentation describing the recommended workflow that integrates Textual Analysis and the Glossary as part of a complete terminology management process. Is there any best practice or guideline for using these two features together?

I also have some questions regarding the Synonym and Ignore functions for Candidate Items.

When I assign a Candidate Item as a synonym or mark it as ignored, the only visible change seems to be an icon or a change in text color. I do not see any further indication of what has actually happened.

After some experimentation, I found that the Analysis view can display synonym relationships, but these relationships do not seem to be well integrated into the Textual Analysis workflow. In addition, I am not sure whether Candidate Items are intentionally designed without a Specification dialog. If so, once I have assigned a synonym or ignored a Candidate Item, I have no obvious way to review or edit those settings.

Another observation is that when I create a Term from a Candidate Item that has a synonym assigned, the corresponding synonym Candidate Item does not appear to be automatically added as an Alias of that Term in the Glossary. I was expecting the synonym information to be carried over, but that does not seem to happen.

Best regards,

Liao

2

Thank you for your inquiry. The Textual Analysis feature is designed for one goal: to allow user identified terms from a piece of text as candidate item, and later on convert them into model elements to be used in various visual models/diagrams. i.e. identify text as actors and use cases and model them with UML Use Case Diagram.

The Term is one of the candidate element can be identify from Textual Analysis, and allow user to create Glossary Term model from it. Once two Term candidates having synonym link established, then create Glossary Term model using “Create Term Model Element” menu will automatically set the synonym linked candidate as alias of the Glossary Term model. This basically is same to you manually create a Glossary Term model in Glossary Grid, and then set synonym/alias for it.

The usage of Glossary Term in project is to let user define standardize meaning for particular terminology. Once a text being defined as Glossary Term then the same text in all diagram/description field will show with underline, and allow user navigate to it to see its detail meaning.

In short, if you want to define standardize terminologies for your project then it should be defined as Glossary Term. It can be directly define from the Glossary Grid, by highlight specific text in diagram to send it to Glossary Grid, or identify text using Textual Analysis then set it as Term candidate, and create Glossary Term for it.

Feel free to contact me for any questions.