Data Modeling: Difference between revisions
(→Import) |
(Removed irrelevant message model stuff) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
==[[Details]]== | ==[[Data Model Details]]== | ||
The details tab is where most of the detailed model editing is done. | The details tab is where most of the detailed model editing is done. Although selecting the [[details]] tab directly does very little, this is where the properties appear once an element has been selected from the [[NavTree]]. | ||
==[[Diagram]]== | ==[[Diagram]]== | ||
Diagrams are a very easy way to visualize models and explore their connectivity. | Diagrams are a very easy way to visualize models and explore their connectivity. A modeling tool would not be complete without some means of building diagrams. While constructing PHENOM's diagramming engine, users expressed their desire for a "modeling scratchpad" capability. This concept allows users to build model content without immediately affecting the data model. This makes it possible to experiment with different modeling ideas without adding a bunch of intermediate content to the model. The new elements become official model content once they are "committed." | ||
Beyond modeling new elements and patterns, the diagram tool can be used to build interface documentation. | Beyond modeling new elements and patterns, the diagram tool can be used to build interface documentation. This functions oppositely from PHENOM's typical mode of documentation. Instead of start with the most specific details and then adding context, this view editing tool starts with the broadest context and narrows down to the most specific details. This approach is difficult to use unless you know the data model. | ||
==[[Health Check]]== | ==[[Health Check|Healthcheck]]== | ||
Rapidly check the overall health of your data model using PHENOM's Health Check. | Rapidly check the overall health of your data model using PHENOM's Health Check. It runs 19 different tests against the model. | ||
Some of the health checks provide tools to help users fix errors. | Some of the health checks provide tools to help users fix errors. | ||
==[[Analytics]]== | ==[[Analytics]]== | ||
These are tools that provide additional insight into the model. | These are tools that provide additional insight into the model. It can show the distribution of entities and attributes used in the documentation. This helps identify areas of the model where refactoring activities can provide the greatest benefit. | ||
==[[Meridian Map]]== | ==[[Meridian Map]]== | ||
The Meridian Map is a type of ribbon diagram that shows the semantic alignment of a collection of views. | The Meridian Map is a type of ribbon diagram that shows the semantic alignment of a collection of views. Drag up to 50 views into the Meridian Map, and it will quickly render the a graph showing all of the 100% semantic matches. | ||
By default, this alignment works at the conceptual level. | By default, this alignment works at the conceptual level. This means that a latitude position will map to a longitude position. In order to further filter using the measurement information, make sure that "Logical Matches Only" is selected. | ||
==[[View Trace]]== | ==[[View Trace]]== | ||
The View Trace tool allows users to map a set of views (one or more) to another set of views (one or more). | The View Trace tool allows users to map a set of views (one or more) to another set of views (one or more). Although the data model automates the View Trace process, there are times when it is necessary to map dissimilar semantics. View Trace is the primary mechanism for overriding semantic mappings. | ||
==[[Import]]== | ==[[Import]]== | ||
Although loading FACE XMI models (.face files) is the primary mechanism for importing bulk data into PHENOM, the import section has some helpful tools for importing data that may not conform to this default format. | Although loading FACE XMI models (.face files) is the primary mechanism for importing bulk data into PHENOM, the import section has some helpful tools for importing data that may not conform to this default format. | ||
PHENOM has the ability to import: [[ | PHENOM has the ability to import: [[Entity and Association| Entities]], [[Entity and Association| Associations]], [[View]]s, [[Platform Type and Enumeration|Enumerations]], [[Constraint]]s, and [[Platform Type and Enumeration|Platform Types]]. | ||
Latest revision as of 12:53, 9 April 2024
Data Model Details
The details tab is where most of the detailed model editing is done. Although selecting the details tab directly does very little, this is where the properties appear once an element has been selected from the NavTree.
Diagram
Diagrams are a very easy way to visualize models and explore their connectivity. A modeling tool would not be complete without some means of building diagrams. While constructing PHENOM's diagramming engine, users expressed their desire for a "modeling scratchpad" capability. This concept allows users to build model content without immediately affecting the data model. This makes it possible to experiment with different modeling ideas without adding a bunch of intermediate content to the model. The new elements become official model content once they are "committed."
Beyond modeling new elements and patterns, the diagram tool can be used to build interface documentation. This functions oppositely from PHENOM's typical mode of documentation. Instead of start with the most specific details and then adding context, this view editing tool starts with the broadest context and narrows down to the most specific details. This approach is difficult to use unless you know the data model.
Healthcheck
Rapidly check the overall health of your data model using PHENOM's Health Check. It runs 19 different tests against the model.
Some of the health checks provide tools to help users fix errors.
Analytics
These are tools that provide additional insight into the model. It can show the distribution of entities and attributes used in the documentation. This helps identify areas of the model where refactoring activities can provide the greatest benefit.
Meridian Map
The Meridian Map is a type of ribbon diagram that shows the semantic alignment of a collection of views. Drag up to 50 views into the Meridian Map, and it will quickly render the a graph showing all of the 100% semantic matches.
By default, this alignment works at the conceptual level. This means that a latitude position will map to a longitude position. In order to further filter using the measurement information, make sure that "Logical Matches Only" is selected.
View Trace
The View Trace tool allows users to map a set of views (one or more) to another set of views (one or more). Although the data model automates the View Trace process, there are times when it is necessary to map dissimilar semantics. View Trace is the primary mechanism for overriding semantic mappings.
Import
Although loading FACE XMI models (.face files) is the primary mechanism for importing bulk data into PHENOM, the import section has some helpful tools for importing data that may not conform to this default format.
PHENOM has the ability to import: Entities, Associations, Views, Enumerations, Constraints, and Platform Types.