1 / 4

Polymorphic Actor-Oriented Design for Heterogeneous Embedded Software

Polymorphic Actor-Oriented Design for Heterogeneous Embedded Software. Edward A. Lee Professor UC Berkeley Seventh Annual Workshop on Embedded Computing HPEC, Sept. 23, 2003 Boston, MA, USA. Center for Hybrid and Embedded Software Systems. What flows through an object is sequential control.

leann
Télécharger la présentation

Polymorphic Actor-Oriented Design for Heterogeneous Embedded Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Polymorphic Actor-Oriented Design for Heterogeneous Embedded Software Edward A. Lee Professor UC Berkeley Seventh Annual Workshop on Embedded Computing HPEC, Sept. 23, 2003 Boston, MA, USA Center for Hybrid and Embedded Software Systems

  2. What flows through an object is sequential control class name data methods call return Actor-Oriented Design • Object orientation: • Actor orientation: What flows through an object is data streams actor name data (state) parameters Input data Output data ports

  3. Problems and Solutions • Some Problems: • OO says little or nothing about concurrency and time • Components implement low-level communication protocols • Components are designed to fixed middleware APIs • Re-use potential is disappointing • Some Partial Solutions • Adapter objects (laborious to design and deploy) • Model-driven architecture (still fundamentally OO) • Executable UML (little or no analyzable structure) • Our Solution is Based on Actor-Oriented Design with: • Behavioral, polymorphic type system • Meta modeling of semantics Interface definition gives requirements and guarantees only, not implementations. E.g.“Give me text and I’ll give you speech” rather than “I have void initialize(), void notify(), boolean isRead(), double[ ] getSpeech() ….”

  4. Example of Actor-Oriented Design(in this case, with a visual syntax) Director from a library defines component interaction semantics Ptolemy II example: Component Large, domain-polymorphic component library. • Model of Computation: • Messaging schema • Flow of control • Concurrency Key idea: The model of computation is part of the framework within which components are embedded rather than part of the components themselves.

More Related