The path to successful integration...
Specification using SySpec
SySpec is the specification tool in the SyDat toolset which facilitates the formal definition of technical interfaces between systems. Once defined, the data is stored in a SyDat database that can be used by the other tools in the SyDat toolset.
The SyDat database can also be shared amongst system and subsystem vendors such that everyone has a common understanding of the defined interfaces. In this way, misinterpretation of written interface specifications is avoided resulting in fewer system integration problems later.
Using customized add-ins, existing interface specifications can be imported directly into the SyDat database.
Define message contents
The layout of each message transmitted over an interface is defined by specifying each message field. SySpec 
provides a set of default field types that can be used to model any type of message, including fields that are relative to the contents of other fields and variable length fields. The valid ranges for each field value can also be defined such that later validity checking whilst monitoring with SyMon can be performed.
provides a set of default field types that can be used to model any type of message, including fields that are relative to the contents of other fields and variable length fields. The valid ranges for each field value can also be defined such that later validity checking whilst monitoring with SyMon can be performed.
In addition, SySpec provides powerful nesting capability where common fields and structures within messages can be defined and reused within other messages. Intelligent 
compatibility checking allows users to selectively update current messages with any changes to nested content without forcing it, thereby providing a degree of multiple build control.
compatibility checking allows users to selectively update current messages with any changes to nested content without forcing it, thereby providing a degree of multiple build control.
SySpec allows message content to be defined in a human readable way. This is achieved by using enumerations to represent data values such as “Valve Open” or “Valve Closed” (instead of simply a ‘1’ or ‘0’ ) or even to define a message name e.g. “Reset Message”, rather than just a numeric ID such as ‘5’. All these enumerations are fully user definable.