Integration Modeling: Difference between revisions
(Created page with "==Integration 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. ==Integration Model Editor==") |
|||
| Line 3: | Line 3: | ||
==[[Integration Model Editor]]== | ==[[Integration Model Editor]]== | ||
The integration model editor is a very easy way to visualize integration models and explore their connectivity similarly to the [[Diagram]]. While constructing PHENOM's diagramming engine, users expressed their desire for a "modeling scratchpad" capability. This concept allows users to build integration 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." | |||
The integration model editor is also capable of creating composed contexts. These composed contexts allow users to streamline nesting contexts, treating the entire composed context as a single node block. The composed feature enables the encapsulation of modeling elements and patterns while also being able to view or modify the composed context's contents. | |||
Revision as of 13:32, 19 July 2024
Integration 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.
Integration Model Editor
The integration model editor is a very easy way to visualize integration models and explore their connectivity similarly to the Diagram. While constructing PHENOM's diagramming engine, users expressed their desire for a "modeling scratchpad" capability. This concept allows users to build integration 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."
The integration model editor is also capable of creating composed contexts. These composed contexts allow users to streamline nesting contexts, treating the entire composed context as a single node block. The composed feature enables the encapsulation of modeling elements and patterns while also being able to view or modify the composed context's contents.