specifications - Formal way to describe protocols -
Is there a formal / traditional way to describe the data / command exchange protocol? For example, there are many approaches to describing syntax and semantics (such as :) for programming languages.
The approach I am looking for is useful (as opposed to academic). While working on specifications, I need something for day-to-day usage for data exchange details, just to transfer / spread the views of other people. Therefore, if there is anything that is not recognized as a D-Facto standard but useful - it's OK too.
I took a look at the UML sequence diagrams and the details of the "payloads" in the pre-system are missing by "formal method for communication protocol specificity and verification, Carl A. Sunshine, 1979" (less than Less what I had understood), while the other is rather an enlightening letter, which describes ideas rather than methods (although I am still going through this letter).
Thanks in advance
Send the protocol according to a series of interactions Are the messages.
I have seen that the best way to specify the protocol is
based on CPN ("not useless"), which synchronizes parallel activities, for example, Message responses, using place to represent possible states, token-in-places to represent the state, and transit (synchronization) gates shows that parallel states are used to represent Must match to Rgti. Petri trap finite state machines (an FSA is a PN which is always a "single token", for example, "current status") and therefore can do a generalization; In fact, they can compress some FSAs "very quickly" in very small details and thus can be quite brief for complex interaction scenes. But does not solve the data of a traditional PN exchanges.
CPN is normally a strange way of saying "color" ("data type") to the token to add data types to PNS and the transition can not be synchronized only, but the tokens can not be synchronized with other tokens. To add to production, for example, calculate new values.
A protocol CPN is thus the message content as the data type, and PNS has asked to point out the synchronization. If you have never used CPN, then you really have trouble knowing what they are, because they are doing very generalization of FSA.
There are "useful" comments about OP, very good tools available, including graphical modeling and code generation.
Comments
Post a Comment