Difference between revisions of "Refactoring Models"

From CaseTalk Wiki
Jump to: navigation, search
m
m
Line 12: Line 12:
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.
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 ([https://www.casetalk.com/support/articles/examples/76-replace-identification Replace Identification])
== Replace Object Type ==
* Copy to OTE/FTE
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]
* Edit expression and drag and drop nominalisations
 
* Alter role played by
== Copy to OTE/FTE ==
* Nominalize label type
 
* Delete expression (locally, including OTE's)
== Alter role played by ==
* Delete OTFT
 
* Replace OT
== Nominalize label type ==
* Combine/Split Label Types
 
* Create Fact/Label/Object Type
== Delete expression ==
* Combine slected OTFT in Fact Type
== Edit expression substitution ==
* Create subtype
== Edit expression ==
* Add role
== Delete OTFT ==
* ..
== Combine/Split Label Types ==
== Create Fact/Label/Object Type ==
== Combine into Fact Type ==
== Create subtype ==
== Add role ==

Revision as of 11:42, 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 to OTE/FTE

Alter role played by

Nominalize label type

Delete expression

Edit expression substitution

Edit expression

Delete OTFT

Combine/Split Label Types

Create Fact/Label/Object Type

Combine into Fact Type

Create subtype

Add role