Citation
Edward A. Lee, Stephen Neuendorffer, Xiaojun Liu. "Classes and Inheritance in Actor-Oriented Design". Technical report, University of California, Berkeley, UCB/EECS-2006-154, November, 2006; See http://chess.eecs.berkeley.edu/pubs/429.html for the published version.

Abstract
Actor-oriented components emphasize concurrency and temporal semantics and are used for modeling and designing embedded software and hardware. Actors interact with one another through ports via a messaging schema that can follow any of several concurrent semantics. Domain-specific actor-oriented languages and frameworks are common (Simulink, LabVIEW, SystemC, etc.). However, they lack many modularity and abstraction mechanisms that programmers have become accustomed to in object-oriented components, such as classes, inheritance, interfaces, and polymorphism. This paper shows a form that such mechanisms can take in actor-oriented components, gives a formal structure, and describes a prototype implementation.

Electronic downloads

• http://www.eecs.berkeley.edu/Pubs/TechRpts/2006/EECS-2006-154.html

• HTML

  Edward A. Lee, Stephen Neuendorffer, Xiaojun Liu. <a
  href="http://chess.eecs.berkeley.edu/pubs/314.html"><i>Classes
  and Inheritance in Actor-Oriented
  Design</i></a>, Technical report,  University of
  California, Berkeley, UCB/EECS-2006-154, November, 2006; See
  <a
  href="http://chess.eecs.berkeley.edu/pubs/429.html"
  >http://chess.eecs.berkeley.edu/pubs/429.html</a>
  for the published version.

• Plain text

  Edward A. Lee, Stephen Neuendorffer, Xiaojun Liu.
  "Classes and Inheritance in Actor-Oriented
  Design". Technical report,  University of California,
  Berkeley, UCB/EECS-2006-154, November, 2006; See <a
  href="http://chess.eecs.berkeley.edu/pubs/429.html"
  >http://chess.eecs.berkeley.edu/pubs/429.html</a>
  for the published version.

• BibTeX

  @techreport{LeeNeuendorfferLiu06_ClassesInheritanceInActorOrientedDesign,
      author = {Edward A. Lee and Stephen Neuendorffer and Xiaojun
                Liu},
      title = {Classes and Inheritance in Actor-Oriented Design},
      institution = {University of California, Berkeley},
      number = {UCB/EECS-2006-154},
      month = {November},
      year = {2006},
      note = {See <a
                href="http://chess.eecs.berkeley.edu/pubs/429.html"
                >http://chess.eecs.berkeley.edu/pubs/429.html</a>
                for the published version.},
      abstract = {Actor-oriented components emphasize concurrency
                and temporal semantics and are used for modeling
                and designing embedded software and hardware.
                Actors interact with one another through ports via
                a messaging schema that can follow any of several
                concurrent semantics. Domain-specific
                actor-oriented languages and frameworks are common
                (Simulink, LabVIEW, SystemC, etc.). However, they
                lack many modularity and abstraction mechanisms
                that programmers have become accustomed to in
                object-oriented components, such as classes,
                inheritance, interfaces, and polymorphism. This
                paper shows a form that such mechanisms can take
                in actor-oriented components, gives a formal
                structure, and describes a prototype
                implementation.},
      URL = {http://chess.eecs.berkeley.edu/pubs/314.html}
  }
  

Posted by Christopher Brooks on 7 Jun 2007.
Groups: ptolemy
For additional information, see the Publications FAQ or contact webmaster at chess eecs berkeley edu.