Fujaba Hits the Wall(-E)

0

No comments posted yet

Comments

Slide 1

Fujaba hits the Wall(-e) From a children's tale to initial modeling insights Pieter Van Gorp Ruben Jubeh Bernhard Grusie Anne Keller

Slide 2

Trigger

Slide 3

Presentation Structure 2

Slide 4

Background: Story Boarding [Diethelm et al.] 3

Slide 5

Background: Mindstorms [Jubeh et al.] 4

Slide 6

Presentation Structure 5

Slide 7

Fujaba/NXT @UAntwerp... [Van Gorp & Keller] 6

Slide 8

FactoryBot (2/5) 7

Slide 9

FactoryBot (3/5) 8

Slide 10

FactoryBot (4/5): eDOBS 9

Slide 11

FactoryBot (5/5): Story Diagrams 10

Slide 12

Fujaba/NXT demo, created by UA students 11

Slide 13

Presentation Structure 12

Slide 14

Assessment: Framework Use of EDOBS and Pictures Visual Patterns Recognizable 13 However, early on:  Story Diagrams with undesirable details Subtle differences in blocking vs non-blocking Many collab-statements, Little rewriting (RHSs) Inherent Complexity:  Hardware cable failures… Platform Issues (Lejos bugs, Bluetooth, …)

Slide 15

Assessment: Examples 14 followLine with “crippled hardware” “Wall-E rescues EVE” Need example for <16yr olds Wall-E = hot topic Problematic Story Diagrams Statechart approach = promising

Slide 16

Fujaba NXT “2.0”  15

Slide 17

Presentation Structure 16

Slide 18

17 Remaining Issue: Recognize bad style, i.e. know potential of statecharts Agenda: Extend set of examples

Slide 19

Wall-E Rescues EVE: followLine 18

Slide 20

Wall-E Example: Didactics 19

Slide 21

Open Issues (NXT Framework) Distributed Development Fujaba CVS merges OK at model-level, but CPU, Bluetooth, … differences hinder reproducibility Video recordings  Use of simulation adapters Also needed with >100 students… How to make simulator produce meaningful light sensor values based on motor movements? Full-blown environment modeling needed? Debugging e.g., stopping motors when suspending VM Leverage “design level debugging”, “JUnit codegen”, … [Geiger et al.] 20

Slide 22

Presentation Structure 21

Slide 23

Wall-E: Survey Results See http://cms.ieis.tue.nl/Beta/Files/WorkingPapers/Beta_wp294.pdf Bottom Line: Role-playing is fun, but the actual robot is cooler Hard to generalize, especially with heterogeneous groups 22 eDOBS “Instructor” interacts directly with motors, kids decide (instruct)

Slide 24

Conclusions 23

Summary: These slides describe how Fujaba supports the model-driven development of LEGO Mindstorms robots. See http://cms.ieis.tue.nl/Beta/Files/WorkingPapers/Beta_wp294.pdf and http://is.ieis.tue.nl/staff/pvgorp/events/fujabadays2009/

Tags: uml "story diagram" statecharts "teaching object orientation" tue "model driven development" lego mindstorms nxt

URL:
More by this User
Most Viewed