20111115 e trice eclipse demo camp munich


Published on

Develping Embedded Systems with Eclipse eTrice

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

20111115 e trice eclipse demo camp munich

  1. 1. Develping Embedded Systems with eTrice Thomas Schütz Protos Software GmbHEclipse Demo Camp Munich, 15. November 2011
  2. 2. Scope of eTrice  eTrice is a Modeling Toolset for eventdriven, distributed embedded systems© 2011 Protos Software GmbH 2 15.11.2011
  3. 3. Scope of eTrice  provide an implementation of the modeling language Real Time Object Oriented Modeling (ROOM)  build ready to use editors for ROOM models (textual and graphical)  create code generators and portable target runtime libraries for Java, C++, and C (and …)  provide built-in support for model level debugging of the running target software: state machine animation, data inspection and manipulation and message injection  provide built-in possibilities for sequence diagram creation from the running software  support heterogenous distributed systems out of the box© 2011 Protos Software GmbH 3 15.11.2011
  4. 4. Why ROOM and not UML2?  it‘s all about reduction of complexity !!! UML2 Meta Model ROOM Meta Model© 2011 Protos Software GmbH 4 15.11.2011
  5. 5. ROOM: Basic Features  hierarchical Actor structures supporting component building  hierarchical state machines  message based systems can be realized with 3 modeling elements => ActorClass => Port => Protocol© 2011 Protos Software GmbH 5 15.11.2011
  6. 6. Shift of the Object Paradigm thread of control 1 System  classic objects just provide Object 3 Object 1 information hiding  classic objects do not solve concurrency issues thread of control 2 Object 2 thread of control 3 Actor1 Actor2  ROOM interprets an object as a „logical machine“ with its own thread of control thread of thread of control control  this thinking is much more general than Actor3 the classic object oriented paradigm thread of control  „logical machines“ solve the concurrency active issue by providing a run to completion Object semantic© 2011 Protos Software GmbH 6 15.11.2011
  7. 7. ROOM Editors: Actors & Ports Hierarchical Components called Actors define the Structure of a System Graphical Editors Textual Editors (Graphiti) (XText)Ports are the only Interfaces of an actor and define a specificrole in its environment.  Models can be edited with graphical or textual editors© 2011 Protos Software GmbH 7 15.11.2011
  8. 8. ROOM Editors: Statemachines hierarchical Statemachines define the dynamical behaviour of Actors© 2011 Protos Software GmbH 8 15.11.2011
  9. 9. Model Level Debugging: MSC Generator The events can be logged on the target to create Message Sequence Charts (MSC) of the running application Logs can be viewed with Trace2UML (http://trace2uml.tigris.org/)© 2011 Protos Software GmbH 9 15.11.2011
  10. 10. Motivation (Part 2)  it‘s all about reduction of complexity !!! reducing …structural complexity explicit modeling of hierarchical Actor containment and layeringbehavioral complexity hierachical statemachinesteamwork complexity loosely coupled Actors provide a natural way to structure team work simple branching/merging with textual model notationcomplexity of concurrent & distributed systems loosely coupled Actors are deployable to threads, processes, nodes© 2011 Protos Software GmbH 10 15.11.2011
  11. 11. Motivation (Part 2)  it‘s all about reduction of complexity !!! reducing …complexity of variant handling and reuse (e.g. for product lines) composition of existing Actors to new structures Protocols and Ports make Actors replacable inheritance for structure, behavior and Protocols model level librariescomplexity of debugging model level debugging: state machine animation, data inspection and manipulation, message injection, generated message sequence charts model checking easier for model than for code (detect errors before they occur)© 2011 Protos Software GmbH 11 15.11.2011
  12. 12. eTrice Demo© 2011 Protos Software GmbH 12 15.11.2011
  13. 13. Project Plan: Current Status  Eclipse Process: incubation phase  gathering of community  currently 3 committers of 2 companies  first industry projects:  automation (Java Generator)  automotive (C Generator)  release of version 0.1 scheduled for 30. November© 2011 Protos Software GmbH 13 15.11.2011
  14. 14. Project Plan: Next Steps  gathering of community  further versions  generators and middleware for other languages (C, C++, …)  more model level debugging (state machine animation, data inspection and manipulation and message injection )  model level support for distributed systems  detail level (expression) language  model checking (e.g. abstract execution of Statemachines)© 2011 Protos Software GmbH 14 15.11.2011
  15. 15. Thank you for your attentionThomas Schützhttp://www.eclipse.org/etrice