Domain concepts for communication protocols

Juha Pärssinen

Domain concepts for communication protocols

Research output: Chapter in Book/Report/Conference proceeding › Conference article in proceedings › Scientific › peer-review

Abstract

In this paper domain concepts for communication protocols are introduced. These concepts were found from several different protocols, and protocol implementation frameworks and environments. In this paper there are introduced first two different protocol implementation environment, then the domain concepts, and finally how those concepts can be mapped to implementation environments. These concepts were used to support protocol design, implementation, documentation, and also as a learning aid for newcomers to this domain. They were also used when a guideline for standardization was developed in ETSI. The main reason for this work was (and still is) the insufficience of the UML for protocol engineering domain. The limitations of the UML in this domain are introduced briefly in this paper.

Original language	English
Title of host publication	4th OOPSLA Workshop on Domain-Specific Modeling (DSM'04)
Publisher	University of Jyväskylä
Pages	33-43
ISBN (Print)	951-39-1947-1
Publication status	Published - 2004
MoE publication type	A4 Article in a conference publication
Event	4th OOPSLA Workshop on Domain-Specific Modeling, DSM'04 - Vancouver, Canada Duration: 24 Oct 2004 → 24 Oct 2004

Publication series

Series	Computer science and information systems reports. TR, Technical reports
Number	33
ISSN	1239-291X

Conference

Conference	4th OOPSLA Workshop on Domain-Specific Modeling, DSM'04
Country/Territory	Canada
City	Vancouver
Period	24/10/04 → 24/10/04

Access to Document

http://www.dsmforum.org/events/DSM04/Parssinen.pdf

Cite this

@inproceedings{389a9ed05159428c87f4b49adb142b61,

title = "Domain concepts for communication protocols",

abstract = "In this paper domain concepts for communication protocols are introduced. These concepts were found from several different protocols, and protocol implementation frameworks and environments. In this paper there are introduced first two different protocol implementation environment, then the domain concepts, and finally how those concepts can be mapped to implementation environments. These concepts were used to support protocol design, implementation, documentation, and also as a learning aid for newcomers to this domain. They were also used when a guideline for standardization was developed in ETSI. The main reason for this work was (and still is) the insufficience of the UML for protocol engineering domain. The limitations of the UML in this domain are introduced briefly in this paper.",

author = "Juha P{\"a}rssinen",

year = "2004",

language = "English",

isbn = "951-39-1947-1",

series = "Computer science and information systems reports. TR, Technical reports",

publisher = "University of Jyv{\"a}skyl{\"a}",

number = "33",

pages = "33--43",

booktitle = "4th OOPSLA Workshop on Domain-Specific Modeling (DSM'04)",

address = "Finland",

note = "4th OOPSLA Workshop on Domain-Specific Modeling, DSM'04 ; Conference date: 24-10-2004 Through 24-10-2004",

}

Pärssinen, J 2004, Domain concepts for communication protocols. in 4th OOPSLA Workshop on Domain-Specific Modeling (DSM'04). University of Jyväskylä, Computer science and information systems reports. TR, Technical reports, no. 33, pp. 33-43, 4th OOPSLA Workshop on Domain-Specific Modeling, DSM'04, Vancouver, Canada, 24/10/04. <http://www.dsmforum.org/events/DSM04/Parssinen.pdf>

Domain concepts for communication protocols. / Pärssinen, Juha.
4th OOPSLA Workshop on Domain-Specific Modeling (DSM'04). University of Jyväskylä, 2004. p. 33-43 (Computer science and information systems reports. TR, Technical reports; No. 33).

Research output: Chapter in Book/Report/Conference proceeding › Conference article in proceedings › Scientific › peer-review

TY - GEN

T1 - Domain concepts for communication protocols

AU - Pärssinen, Juha

PY - 2004

Y1 - 2004

N2 - In this paper domain concepts for communication protocols are introduced. These concepts were found from several different protocols, and protocol implementation frameworks and environments. In this paper there are introduced first two different protocol implementation environment, then the domain concepts, and finally how those concepts can be mapped to implementation environments. These concepts were used to support protocol design, implementation, documentation, and also as a learning aid for newcomers to this domain. They were also used when a guideline for standardization was developed in ETSI. The main reason for this work was (and still is) the insufficience of the UML for protocol engineering domain. The limitations of the UML in this domain are introduced briefly in this paper.

AB - In this paper domain concepts for communication protocols are introduced. These concepts were found from several different protocols, and protocol implementation frameworks and environments. In this paper there are introduced first two different protocol implementation environment, then the domain concepts, and finally how those concepts can be mapped to implementation environments. These concepts were used to support protocol design, implementation, documentation, and also as a learning aid for newcomers to this domain. They were also used when a guideline for standardization was developed in ETSI. The main reason for this work was (and still is) the insufficience of the UML for protocol engineering domain. The limitations of the UML in this domain are introduced briefly in this paper.

M3 - Conference article in proceedings

SN - 951-39-1947-1

T3 - Computer science and information systems reports. TR, Technical reports

SP - 33

EP - 43

BT - 4th OOPSLA Workshop on Domain-Specific Modeling (DSM'04)

PB - University of Jyväskylä

T2 - 4th OOPSLA Workshop on Domain-Specific Modeling, DSM'04

Y2 - 24 October 2004 through 24 October 2004

ER -

Domain concepts for communication protocols

Abstract

Publication series

Conference

Access to Document

Fingerprint

Cite this