verification_of_designs
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
verification_of_designs [2011/11/18 20:14] peterbuenk [1. The verification process] |
verification_of_designs [2017/11/15 11:15] (current) |
||
|---|---|---|---|
| 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 <can be fulfilled by a> relation between a <shall have as aspect a> relation and a <has as aspect> 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 <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): // | + | 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 | | ||
verification_of_designs.1321643661.txt.gz · Last modified: 2017/11/15 11:06 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
