Page History

...

Subject Matter Expert (SME)-friendly graphical notation

• Uses consultant-proven, SME-friendly graphical notation.
• Facilitates real-time interactions with SMEs to model real-world business concepts and their relationships.
• Requires no camel case names.
• Sets visibility of properties to public by default.
• Encourages clean, hyperlinked micro-subject-area diagrams.

The automatic styling of a Concept Model through AutoStyler plugin

Large-scale concept models often contain information that is tangled in a complex web of relationships, and, therefore, are difficult read and follow. Through the AutoStyler plugin for MagicDraw, the cumbersome task of untangling information becomes much simpler, and it assists the concept modeler in producing diagrams that are concise, focused, and presentable to stakeholders.

...

AutoStyler is currently a separate plugin for MagicDraw, but is expected to become part of the base MagicDraw product in the future.

Automatic glossary generation

Using a glossary saves time by ensuring consistent usage of terminology in the organization. It also improves the communication between team members since terms are understood in the same way and definitions become visible everywhere the terms are used.

...

For more information, please refer to the user manual for MagicDraw 18.0 SP4 or higher.

Concept model authoring

Concept Modeler can do the following:

...

To see all elements that Concept Modeler can import or export, refer to Concept Modeling Semantics and UML to Equivalent OWL in OWL Functional Syntax.

UML model traceability

The Concept Modeler uses UML to build models. Therefore, concept models built by the Concept Modeler can be traced to any UML model, (e.g., NIEM-UML).

Semantic integration of multiple information models

A concept model built by the Concept Modeler provides the semantics to integrate multiple information models “subsetted” from the concept model:

• Information at rest (e.g., relational and XML databases).
• Information in motion (e.g., XSD schema and NIEM-UML).

Natural language glossary

In addition to glossary tables, the Concept Modeler provides a separate feature for generating a natural-language glossary. Natural language glossaries are intended for technical and non-technical people alike. For instance, concept modelers can ensure that the model indeed says what was intended. Subject matter experts can ensure that the model captures their business knowledge correctly. And system builders can find definitions for the terms used in requirements in much more detail than usual.

...

Users will find that the better the model, the clearer the auto-generated glossary.

Annotation properties in the natural language glossary

Cameo Concept Modeler offers a project option that allows the selection of which annotation properties will be shown or hidden in every natural language glossary entry, in addition to the definitions generated from the semantics of a concept model. You can select any number of annotation properties. Elements in the report such as Classes or Properties that are annotated with a «Annotation» stereotyped UML comment that contains one of these annotation properties will display the UML comment body in the report. When no comment body exists the name of the annotation property will display by itself.

In our software, the feature is labeled “Natural Language Glossary annotation property list” and it consists of a list of pre-loaded annotation properties.

Preferred annotation property

Cameo Concept Modeler offers a project option that speeds up the creation of one of many possible kinds of annotations, and specifies which kind of annotation to treat as documentation. You can select a preferred annotation property to be assumed whenever the user adds a UML Comment or an annotation. Comments and Annotations that explicitly use that annotation property will then be shown in the documentation panel, and in the Natural Language Glossary, as the human-specified definition (as opposed to the model-generated definition). 

...

If your project is a TWC project, Concept Modeler will attempt to lock the project’s elements. If any of the elements cannot be locked, whether it is locked by another user, then several message windows will appear, notifying you of the problem and allowing you to see which elements are not locked.

Creation of multiple data models from one concept model and connection of multiple existing data models to one concept model

Updating symbol styles

Cameo Concept Modeler diagrams are intended to be as non-technical as possible for subject matter experts. As new features are added to the Concept Modeler, sometimes symbol styles may expose technical details that are not appropriate for that kind of audience. Cameo Concept Modeler therefore offers to tweak the styles called "Default" and "Defined Elsewhere". However, if you have tweaked those styles yourself, you may wish to either defer this, or make Concept Modeler stop asking you altogether.

This new feature of updating symbol styles in older projects; more specifically, we added versioning to symbol styles which allows you to programmatically update a project’s symbol styles. Please note that this feature only works in 18.2+ and is not compatible in 18.0 and 18.1. Additionally, updating symbol styles will overwrite the existing styles, so if you manually made changes to the styles or added new features to the existing styles, those values will not be retained.

Creation of multiple data models from one concept model (Diagram preservation after ontology import)

In addition to the Concept Modeler’s import capability, the software allows for diagram preservation after an ontology import. More specifically, while importing an ontology, the concept modeler will update the existing concept model. An ontology is imported into a CCM project that contains one or more concept models. Each ontology is imported into a concept model that may already be present in the project in which the ontology is imported. Ontology elements get translated into concept model elements.

The following table describes the conditions, evaluated by Concept Modeler, of each resource from ontology that is being imported. The condition determined by Concept Modeler will dictate how Concept Modeler will create/merge/delete the model element.

The table below groups all the concept model elements and explains how they handle the “preservation” for each of the four conditions explained above.

*https://link.springer.com/referenceworkentry/10.1007%2F978-1-4419-9863-7_734