A Domain Specific Approach to Network Software Architecture: Assuring Conformance Between Architecture and Code
2009 (English)In: Fourth International Conference on Digital Telecommunications, 2009. ICDT '09, Piscataway, N.J.: IEEE , 2009, 127-132 p.Conference paper (Refereed)
Network software is typically organized according toa layered architecture that is well understood. However, writingcorrect and efficient code that conforms with the architecture stillremains a problem. To overcome this problem we propose to usea domain specific language based approach. The architecturalconstraints are captured in a domain specific notation that can beused as a source for automatic program generation. Conformancewith the architecture is thus assured by construction. Knowledgefrom the domain allows us to generate efficient code. In addition,this approach enforces reuse of both code and designs, one ofthe major concerns in software architecture. In this paper, weillustrate our approach with PADDLE, a tool that generates packetprocessing code from packet descriptions. To describe packets weuse a domain specific language of dependent types that includespacket overlays. From the description we generate C librariesfor packet processing that are easy to integrate with other partsof the code. We include an evaluation of our tool.
Place, publisher, year, edition, pages
Piscataway, N.J.: IEEE , 2009. 127-132 p.
Network Software Architecture
Telecommunications Engineering and Technology Computer Science
Research subject Computer and Systems Science
IdentifiersURN: urn:nbn:se:oru:diva-15278DOI: 10.1109/ICDT.2009.4ISI: 000274805500026ScopusID: 2-s2.0-70449602416ISBN: 978-0-7695-3695-8OAI: oai:DiVA.org:oru-15278DiVA: diva2:410960
©2009 IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.2011-04-152011-04-152011-04-15Bibliographically approved