# Gellish Wiki

### Site Tools

verification_of_designs

# Differences

This shows you the differences between two versions of the page.

 verification_of_designs [2011/11/18 20:14]peterbuenk [1. The verification process] verification_of_designs [2011/11/18 20:16]peterbuenk [1. The verification process] Both sides previous revision Previous revision 2011/11/18 20:16 peterbuenk [1. The verification process] 2011/11/18 20:16 peterbuenk [1. The verification process] 2011/11/18 20:14 peterbuenk [1. The verification process] 2011/11/18 20:13 peterbuenk 2011/10/20 23:19 peter created Next revision Previous revision 2011/11/18 20:16 peterbuenk [1. The verification process] 2011/11/18 20:16 peterbuenk [1. The verification process] 2011/11/18 20:14 peterbuenk [1. The verification process] 2011/11/18 20:13 peterbuenk 2011/10/20 23:19 peter created Line 9: Line 9: 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 relation between a relation and a relation. 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 relation between a relation and a 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): ​// + 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^ ^Name of left hand object^Name of relation type^Name of right hand object^ | vessel | shall have as aspect a | length between tangent lines| | 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: ​// + 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^ ^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 | 101 | 1225 | is classified as a | 520243 | vessel |