Table of content:
Note that each Wiki page has its own table of content about the details on that page.
Table of content:
Note that each Wiki page has its own table of content about the details on that page.
Verification of a design as well as verification of a fabricated real object is enabled by a formal (computer interpretable) specification of requirements provided that the design or the observed real objectdata are also expressed in Gellish. In other words, when requirements are expressed according to the Gellish Modeling Method and the delivered information that intents to satisfy those requirements is delivered also according to the Gellish Modeling Method, then that enables computer-aided verification of the completeness and other quality aspects of the delivered information.
For example, it may be a requirement that when an object of a particular kind is delivered that then a particular kind of document shall be delivered as well and that the object shall have a particular kind of part for which spare parts shall be delivered. The Gellish Modeling Method enables that such requirements are automatically verified, provided that the information about the delivered documents, parts and spare parts is also delivered according to the Gellish Modeling Method.
The Gellish Modeling Method includes a process to verify the requirement that objects of a kind shall have a particular kind of aspect. The core of that process is the following.
For every object that is classified by a kind of object for which a requirement is specified the computer should search for relations of a kind that satisfy the requirement. This implies that there is a relation between an expression of a requirement and an expression of a fact that satisfies the requirement. This relation is a <can be fulfilled by a> relation between a <shall have as aspect a> relation and a <has as aspect> relation.
For example, assume that a facility owner has expressed the requirement that a vessel shall have a length between tangent as follows (omitting the UID's):
Name of left hand object | Name of relation type | Name of right hand object |
---|---|---|
vessel | shall have as aspect a | length between tangent lines |
Furthermore, assume that a piece of equipment, called V-1206, is delivered to the above facility owner and that V-1206 is classified as a vessel. Then the database system of the receiving party can automatically ‘know’ from the above described specification of requirements that the delivered data is only complete when V-1205 has a length between tangent lines with a value. Furthermore, assume that the data about the equipment is delivered in the form of a Gellish Database table as follows:
UID of left hand object | Name of left hand object | UID of fact | UID of relation type | Name of relation type | UID of right hand object | Name of right hand object | UID of UoM | UoM |
---|---|---|---|---|---|---|---|---|
1 | V-1206 | 101 | 1225 | is classified as a | 520243 | vessel | ||
1 | V-1206 | 102 | 1727 | has as aspect | 2 | length of V-1206 | ||
2 | length of V-1206 | 103 | 1225 | is classified as a | 550362 | length between tangent lines | ||
2 | length of V-1206 | 104 | 5025 | has on scale a value equal to | 922365 | 3100 | 570423 | mm |
This enables that the software can verify the data automatically and can report that the requirement is satisfied. This enables to verify automatically the progress of the delivery of the data it also enable to determine an information quality Key Performance indicator for completeness of the data.
The requirement as well as the qualification can also be expressed by variants of the relation type, such as:
The specification of the requirement that the aspect values may only be selected from a list of standard qualitative aspects is also possible.
The verification of other kinds of facts follow a similar process.
Continue with Automated Translation