Software Design Patterns for TinyOS

David Gay and Philip Levis and David Culler

EECS Department, University of California, Berkeley

Technical Report No. UCB/CSD-04-1350

2004

This publication is archived. It is kept only for reference purposes, so it is no longer being updated and may not meet accessibility standards. If you need this content in a different format, please email webteam@eecs.berkeley.edu.

http://www2.eecs.berkeley.edu/Pubs/TechRpts/2004/Archive/CSD-04-1350.pdf

We present design patterns used by software components in the TinyOS operating system. They differ significantly from traditional software design patterns due to TinyOS's focus on static allocation and whole-program composition. We describe how nesC has evolved to support design patterns by including a few simple language primitives.

BibTeX citation:

@techreport{Gay:CSD-04-1350,
    Author= {Gay, David and Levis, Philip and Culler, David},
    Title= {Software Design Patterns for TinyOS},
    Year= {2004},
    Url= {http://www2.eecs.berkeley.edu/Pubs/TechRpts/2004/5835.html},
    Number= {UCB/CSD-04-1350},
    Abstract= {We present design patterns used by software components in the TinyOS operating system. They differ significantly from traditional software design patterns due to TinyOS's focus on static allocation and whole-program composition. We describe how nesC has evolved to support design patterns by including a few simple language primitives.},
}

EndNote citation:

%0 Report
%A Gay, David 
%A Levis, Philip 
%A Culler, David 
%T Software Design Patterns for TinyOS
%I EECS Department, University of California, Berkeley
%D 2004
%@ UCB/CSD-04-1350
%U http://www2.eecs.berkeley.edu/Pubs/TechRpts/2004/5835.html
%F Gay:CSD-04-1350