Refactoring Models

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 OTE
• Copy to OTE/FTE
• Edit expression and drag and drop nominalisations
• Alter role played by
• Nominalize label type
• Delete expression (locally, including OTE's)
• Delete OTFT
• Replace OT
• Combine/Split Label Types
• Create Fact/Label/Object Type
• Combine slected OTFT in Fact Type
• Create subtype
• Add role
• ..