verification_of_designs
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
verification_of_designs [2011/10/20 23:19] peter created |
verification_of_designs [2017/11/15 11:15] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Verification of designs ===== | + | ====== Verification of designs ====== |
| 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. | 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. | 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. | ||
| - | ===== 1. The verification process ===== | + | ====== 1. The verification process ====== |
| 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. | 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 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): [[br]] | + | 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: [[br]] | + | 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.1319145583.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
