Difference between revisions of "Core.Signatures"

From emotive
Jump to navigation Jump to search
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{DISPLAYTITLE:OTX '''Signatures''' data model}}[[Category:OTX-Core]][[Category:Signatures]]
+
{{DISPLAYTITLE:OTX '''Signatures'''}}[[Category:OTX-Core]][[Category:Signatures]]
 
== Classification ==
 
== Classification ==
{{ClassificationCore | Signatures | OTX signatures data model | [[OTX Core]] | - }}
+
{{ClassificationCore | Signatures | Interface description to another module | [[OtxReference#Core|OTX Core]] | - }}
  
 
== Introduction ==
 
== Introduction ==
OTX signatures support the '''Design By Contract''' (DBC) approach, see Signature Concept . A signature is therefore a description of an interface to another module, so that the user who wants to use this module, you must know nothing about the internal structure.
+
OTX signatures support the '''design by contract''' (DBC) concept, see [[General.Principles|Signature Concept]]. A signature is therefore a description of an interface to another module so that the user, who wants to use this module, needs to know nothing about the internal structure.
  
In OTX there are two types of signature:
+
OTX allows different types of signatures:
  
* The [[OtxProcedureSignatures|Procedure Signatures]]
+
* The [[Core.Signatures.ProcedureSignatures|Procedure Signatures]] describe the interface of a sequence ([[Core.Procedures|Procedures]]).
* The [[ScreenSignatures|Screen Signatures]]
+
* The [[Core.Signatures.ScreenSignatures|Screen Signatures]] describe the interface for input and output within the [[Extensions.HMI|HMI library (Human Machine Interface)]].
 +
* The [[Core.Signatures.DeviceSignatures|Device Signatures]] describe the measurement and control interface of a measurement device or probe.
  
The procedure signature describes the interface of a process ([[OtxProcedures|Procedures]]). The screen signature the interface for input and output within the [[HMI|HMI library (Human Machine Interface)]].
 
  
 
== See also ==
 
== See also ==
[[OtxValidation|Validation (OTX-Checker)]] <br/>
+
[[Core.Validation|Validation (OTX-Checker)]] <br/>
​​[[OtxNamingConventions|Naming Conventions]] <br/>
+
​​[[General.NamingConventions|Naming Conventions]] <br/>
[[OtxDeclarations|Declarations]] <br/>
+
[[Core.Declarations|Declarations]] <br/>
[[OtxVisibilities|Visibilities]] <br/>
+
[[Core.Visibilities|Visibilities]] <br/>
[[OtxImports|Imports]] <br/>
+
[[Core.Imports|Imports]] <br/>
[[OtxValidities|Validities]] <br/>
+
[[Core.Validities|Validities]] <br/>
[[OtxParameters|Parameter Declarations]] <br/>
+
[[Core.Parameters|Parameter Declarations]] <br/>
[[OtxProcedures|Procedures]] <br/>
+
[[Core.Procedures|Procedures]] <br/>
[[OtxComments|Comments]]
+
[[Core.Comments|Comments]]

Latest revision as of 08:49, 23 November 2016

Classification

Name Signatures
Short Description Interface description to another module
Class OTX Core
Pre-Conditions -
Specified by ISO 13209-2

Introduction

OTX signatures support the design by contract (DBC) concept, see Signature Concept. A signature is therefore a description of an interface to another module so that the user, who wants to use this module, needs to know nothing about the internal structure.

OTX allows different types of signatures:


See also

Validation (OTX-Checker)
​​Naming Conventions
Declarations
Visibilities
Imports
Validities
Parameter Declarations
Procedures
Comments