BTW, I looked at the slides. Very nice. But there are two inaccuracies in slide 13 on the UML-RT background (perhaps for next time ;)):
1) Capsule diagrams replace UML Composite Structure Diagrams, not Component diagrams. The two are similar, but not really the same.
2) The story of UML-RT goes back a bit longer than 2006. Here's a short summary that Bran gave to me (he can correct if I got it wrong):
1987: Telos project at Bell-Northern Research (acquired by Nortel)
1992: Some people from Telos went on to found ObjectTime. Created the language and tool with the same name.
1994: The language was renamed "ROOM" (Real-Time Object-Oriented Modelling). The ROOM book is published, co-authored by Bran, G. Gullekson and P. Ward.
1998: Bran and Jim Rumbaugh made a UML profile for ROOM. They called it UML-RT.
2000: ObjectTime is acquired by Rational. They create Rational RoseRT based on it.
2006: IBM acquires Rational. They create IBM Rational Software Architect Real-Time Edition (RSA-RTE) based on it.
2014: CEA, Zeligsoft and others partner to create Papyrus-RT
So when the language was born exactly might depend on how much of the original one survives. I'm not sure about the differences between ObjectTime and ROOM, but I think UML-RT is pretty much the same as ROOM, so maybe your slides should point to 1994 instead.
Hi Ernesto,
Feedback was very good in general - students enjoyed hearing about a practical application for what they were learning, and all the bits about robotics really helped them stay engaged. They struggled with the notation a bit, but that was to be expected,
as they had been introduced to state machines only a few lectures before.
Yes please, add the links to the repo and the blog in the wiki. I wanted to start putting some teaching materials out there, since we lacked an integrated explanation from start to finish on how to set up the whole thing.
I'll keep an eye out on the Papyrus-RT one and see how that one pans out for now :-).
Kind regards,
Antonio
--
Antonio Garcia-Dominguez
Lecturer in Computer Science
School of Engineering & Applied Science, Aston University
Aston Triangle, Birmingham, B4 7ET
Room: MB211Q
To: papyrus-ic discussions
Subject: Re: [papyrus-ic] Interactive lecture on UML-RT for the rover in Aston University
Hi Antonio.
Great to hear that students are seeing Papyrus-RT in action! Aside from the preference for a drone (which would be fun!), how was the feedback?
Could we put links to your github repo and blog in the wiki?
PS: as for the notation, I think Papyrus-RT inherits the one from Papyrus. As Peter points out, we have a bug in Papyrus-RT for it, but if it is in base Papyrus that you want this fixes, I suggest opening a bug
in Bugzilla for Papyrus.
--
Ernesto Posse
Zeligsoft
Hi everyone,
On Thursday, we ran a 2 hour lecture on the use of UML-RT models to control the Pololu 5 within the Software Engineering module of our BSc/MSc in Computer Science. It was roughly based on the demo project used for the MoDELS'17 Papyrus-RT tutorial, but we added
two branches: one with a simpler model and one with a more advanced one.
We also added a 5-median filter to the HC-SR04 sensor readings, as we found it very noisy in some indoor environments and it would stop and back up at random times otherwise. Perhaps we could get away with a 3-median filter.
The materials are here, and there is a PDF slide deck in the master branch:
https://github.com/bluezio/rover-demo
I also blogged about the whole process from start to finish, with instructions on how to set up the whole thing:
https://xmleye.wordpress.com/2017/10/17/running-uml-rt-models-on-a-raspberry-pi-based-rover/
We did some informal post-it-based feedback at the end of the session, and students seem to enjoy the lecture quite a bit. It helped them see another practical use for all that UML they were learning, and they really liked the discussion about robotics.
We did not have enough time to have the students actually use Papyrus-RT, but we walked through the process to go from the simple model to the model used in the original tutorial. My plan is to bring the rover to the Aston Robotics Club and allow the most motivated
students to try out using Papyrus to tweak its behaviour, perhaps integrating more sensors into it. Some students have already asked where to buy the various parts.
Some students even asked to see a drone rather than a rover done in Papyrus-RT, but I'm not sure about having something with rotating blades and few smarts buzzing around a classroom ;-).
I'll keep you posted on it, but while we're at it: is the notation for entry and exit behaviour wrong in Papyrus? The UML spec seems to use "entry / behaviour", but Papyrus is showing "/entry behaviour". I'd like to see this fixed if possible, as it may confuse
students that are checking their knowledge against the spec.
Kind regards,
Antonio
--
Antonio Garcia-Dominguez
Lecturer in Computer Science
School of Engineering & Applied Science, Aston University
Aston Triangle, Birmingham, B4 7ET
Room: MB211Q
_______________________________________________
papyrus-ic mailing list
papyrus-ic@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-ic
--
papyrus-ic mailing list
papyrus-ic@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-ic
