Abstract
At present, various means have been proposed for specifying services and protocols for the different layers in a communication system. The specifications form the basis for design validation and serve as references for implementors. For validating the correctness of implementations, tests can be derived from specifications. According to [Lisk86], a specification can be considered an abstraction from a set of implementations. The primary purpose of the abstraction is to focus on the functional requirements of a system that can be met in various ways by possible implementations [Viss86b]. To achieve this purpose, specifications need to be general enough so that they do not exclude admissible implementations unnecessarily, but also have to be restrictive enough to rule out unacceptable ones. Desirable properties of specifications include preciseness, consistency, completeness, and structuredness (compare [Brin88a]).
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Notes
The DTE-DTE case is not used in this thesis.
In [Brin88a], an FDT is called constructive if there exists an interpretation algorithm for the symbolic execution of specifications.
Rights and permissions
Copyright information
© 1992 Friedr. Vieweg & Sohn Verlagsgesellschaft mbH, Braunschweig/Wiesbaden
About this chapter
Cite this chapter
Schneider, J.M. (1992). Protocol Specification with Formal Description Techniques. In: Protocol engineering. Vieweg+Teubner Verlag. https://doi.org/10.1007/978-3-322-83979-4_2
Download citation
DOI: https://doi.org/10.1007/978-3-322-83979-4_2
Publisher Name: Vieweg+Teubner Verlag
Print ISBN: 978-3-528-05243-0
Online ISBN: 978-3-322-83979-4
eBook Packages: Springer Book Archive