This report has shown that a systematic design is of great help towards consistent and correct protocol a implementation. It is to date the only known attempted implementation of the connection-oriented class of operation for the 802.2 standard and such has a degree of complexity greatly as exceeding the connectionless class. The analysis of the standard document, first step of the design process, has proven to be a crucial point on which the correctness of the implementation is based. It is during this is reorganized so as to be stage that the information from an implementor's point of view. The satisfactory classification of this information has led to the creation of after some more a general model of implementation which, tests and improvement, can be claimed to be general and applicable to any protocol. providing that it is specified using one of the formal specification techniques known.This model has also shown that hardware assist, such as the use of coprocessors is possible and this will permit improved performance by unloading the main processor from tasks such as handling input/outPut. It is also during this stage that a number of ambiguities have been discovered. This demonstrates that the specification techniques have not yet reached their perfection. Another reason for the previous comment is the fact that a protocol specification, as presented in the 802.2 document, does not permit a partial implementation. The experience with text processing has proven to be difficult and time consuming. Therefore,for automating protocol implementat1on specifications need to be high level language oriented and software tools need be developed to more [6.7.3] . Having said that, 1t 1s important to note that, at the moment, protocol implementation can never be completely automated. There always hand-coded modules are some represent1ng those parts of the protocol left unspecified in the defining document. Examples of this, are the analys1s and the generation of interface events, the identification of connections and the management of multiple connections operating concurrently. Pascal has to be efficient language for proven an protocol implementation purposes. Although, it is not the perfect language for this purpose, it is very well structured and has a strong data type checking. Lastly, it should be stated that a straight implementation in high level language is not very efficient. The code generated by the compiler might be longer than if it were written in assembly, but it allows quicker writing of code and permits easier and quicker maintenance. Instead of 1mplementing 1n assembly, the implementor can always try to optimise the code generated by the compiler. However, in this case more powerful software tools need to be used.