Difference between revisions of "Modeler:Tutorial/Integrity Checks"

From CaseTalk Wiki
Jump to: navigation, search
m (Marcow moved page Modeler:Integrity Checks to Modeler:Tutorial/Integrity Checks without leaving a redirect)
m
 
(88 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Model Well-formedness =
This window shows the well-formedness rules for the active model. This window shows the basic rules to which your model should comply. It shows both errors and warnings. Errors need to be solved before any model generation can be started. Warnings are optional and are indicators to the modeler where to potentially improve the model.


== Check 1 ==
It is advised to perform these rule checks regularly to keep the model in order.


Every fact type must have an intra UC.
[[File:ModelWellFormedness9.png]]
Message(s)
The fact type has no intra UC.
Type
Error.


== Check 2 ==
The disablement of rules is saved inside the current project settings.


The N rule must be valid for every nominalized fact type.
= Full List =
Message(s)
The N rule is not valid for . UC should cover all N roles. The N rule is not valid for . should contain all roles. (The fact type has no intra UC.)
Type
Warning.
Remarks
Most generalizations and common subtype violate this rule.


== Check 3 ==
Click here for a full list of validation rules and their description: [[Modeler:12/RepositoryRules|Integrity Checks]].


The N-1 rule must be valid for every fact type.
----
Message(s)
The N-1 rule is not valid for . (The fact type has no intra UC.)
Type
Warning.


== Check 4 ==
Back: [[:Modeler:Tutorial/Subtype and Generalisation|Subtype and Generalisation]]


The subtype rule must be valid for every subtype.
Next: [[:Modeler:Tutorial/Version Management|Version Management]]
Message(s)
Subtype role in should be covered by a narrow UC. Subtype role in should be played by a non-lexical object type. Subtype role in cannot be mandatory.
Type
Error.
 
== Check 5 ==
 
The alias of an object/fact type must be unique.
Message(s)
The alias of conflicts with the alias of . The alias of conflicts with the name of .
Type
Error.
 
== Check 6 ==
 
All object type expressions must be used.
Message(s)
The object type expression is not used.
Type
Warning.
 
== Check 7 ==
 
Non-lexical object types without totality constraints must have a fact type expression.
Message(s)
The population of might not be verbalizable.
Type
Warning.
Remarks
After the GLR process has been run tuples of the reported fact types might no longer be verbalizable.
 
== Check 8 ==
 
The actual population of every fact type must be verbalizable.
Message(s)
The population of one or more object types / fact types should/will be corrected.
Type
Warning, makes corrections.
Remarks
If the checks finds tupels which cannot be verbalized, these tupels will be removed.
 
== Check 9 ==
 
A strict equality constraint must apply on each subtype tupel.
Message(s)
The subtype has invalid tupels.
Type
Error.
Remarks
A strict equality constraint will be enforced on the tupels of common subtypes.
 
 
 
== Check 10 ==
 
Fact types may not contain redundant role combinations.
Message(s)
...
Type
Warning.
Remarks
Multiple facts are found which play the same combination of roles. Therefor these common roles may be objectified to reduce redundancy.
 
 
 
== Check 11 ==
 
The population should match the Value Constraints
Message(s)
...
Type
Warning.
Remarks
The Value Constraint is checked on the sample population. It is an indication that either the sample is incorrect or the constraint is incomplete.
 
[[Category:Modeler]]

Latest revision as of 05:34, 4 July 2023

Model Well-formedness

This window shows the well-formedness rules for the active model. This window shows the basic rules to which your model should comply. It shows both errors and warnings. Errors need to be solved before any model generation can be started. Warnings are optional and are indicators to the modeler where to potentially improve the model.

It is advised to perform these rule checks regularly to keep the model in order.

ModelWellFormedness9.png

The disablement of rules is saved inside the current project settings.

Full List

Click here for a full list of validation rules and their description: Integrity Checks.


Back: Subtype and Generalisation

Next: Version Management