Difference between revisions of "Refactoring Models"
m |
m |
||
| Line 15: | Line 15: | ||
Replacing an Object Type by another Object Type with a different name and/or structure can be very helpful in comparison to adding a new fact expression elsewhere. This article walks the reader through the steps involved to replace the identity of a modelled Object Type. [https://www.casetalk.com/support/articles/examples/76-replace-identification Replace Identification] | Replacing an Object Type by another Object Type with a different name and/or structure can be very helpful in comparison to adding a new fact expression elsewhere. This article walks the reader through the steps involved to replace the identity of a modelled Object Type. [https://www.casetalk.com/support/articles/examples/76-replace-identification Replace Identification] | ||
== Copy to | == Copy Expressions == | ||
Fact Expressions sometimes look very similar to their Object Type Expressions. Whereas Fact Expressions cannot be substituted in other expressions, the only way forward is to enter the same text as an Object Type Expression. Until you realize there's a function to do that for you. Use the context menu on the expression, and select ''Copy to Object/Fact Type Expression''. This easily copies the text from F1 to O1 or the other way around. It is also a quick way to enter a duplicate for further editing to add different frasings. | |||
F1: "John marries Mary." | |||
O1: 'John marries Mary' | |||
== Alter role played by == | == Alter role played by == | ||
Revision as of 10:48, 21 May 2022
Traditional Modeling
The traditional way of modeling is solely through adding and deleting Fact Expressions. To alter the model this can be a cumbersome approach for it requires the user to understand the many dialogs warning about generalizations, pattern matching, ignoring warnings, and later remove unneeded expressions without breaking the information model as desired.
Validation
The refactoring of fact structures can also be treacherous, for the fact expressions are not validated to start with, these are also refactored. To remember which fact expressions are entered as a whole, or adjusted through refactoring, CaseTalk will mark those affected, and warn users through model well-formedness checking. Every expression affected by it, must be acknowledged to be correct by editing the flagged expressions (optionally fix) and commit by using the ok-buttons.
A warning example:
All generated expressions require validated semantics. * Expression is generated "Graduation Date":"F9"
Refactoring Methods
There are many possible steps to alter an information model, and just as many ways to proceed. The list below shows the available steps, and does not prescribe how to alter your models.
Replace Object Type
Replacing an Object Type by another Object Type with a different name and/or structure can be very helpful in comparison to adding a new fact expression elsewhere. This article walks the reader through the steps involved to replace the identity of a modelled Object Type. Replace Identification
Copy Expressions
Fact Expressions sometimes look very similar to their Object Type Expressions. Whereas Fact Expressions cannot be substituted in other expressions, the only way forward is to enter the same text as an Object Type Expression. Until you realize there's a function to do that for you. Use the context menu on the expression, and select Copy to Object/Fact Type Expression. This easily copies the text from F1 to O1 or the other way around. It is also a quick way to enter a duplicate for further editing to add different frasings.
F1: "John marries Mary." O1: 'John marries Mary'