Good news! The Papyrus Industry Consortium’s steering committee has approved the creation of a “Papyrus Light” addition to the product line!
My insiders have been telling me that work is ongoing on the requirements for this new tool.
Would you like to have a voice? Well you can do so through the Papyrus IC public Tuleap repo’s product management forum! (You may remember my previous post about Tuleap).
In previous posts (here and here), I mentioned the increased focus on Papyrus Toolsmiths.
In this context, the Papyrus development team is putting together a “Papyrus coding day” just before EclipseCon France.
During this free coding day, they will provide you with:
- Hands-on sessions to get an insight on Papyrus SDK capabilities
- Discussions with the Papyrus development team
Registration is mandatory as there is a limit on the number of attendees is limited.
And rejoice in that attendance is free (and includes coffee and snacks)!
There are, however, prerequisites:
- Knowledge of Java (at least intermediate level)
- EMF and UML experience is an plus!
So whether you are already invested in Papyrus, just curious, a toolsmith or a hacker, this may be of interest to you!
You can contact me is this is of interest and I will put you in touch with the organizers!
(The information you provide will only be used to put you in touch with the organizer and then deleted)
I received an interesting email today. Someone asked why the logo contained a flamingo!
Well, that my image is that of an Ibis, not a flamingo!
An Ibis a bird that is found in Egypt, where papyrus was used as paper (or even computers nowadays). That, and the Egyptian god Toth was often depicted as a man with the head of an ibis (I’ll let you make the link between that an me… 😉 )…
Well, I hope this clarifies that for everyone!
The Mondo Project‘s mondo-hawk now supports my models!
You can read more about this on their announcement page!
Note that they only index my semantic model (i.e., the “.uml” files) and not the diagrams, which makes sense in their context given that diagrams are not semantic elements.
Still, this is so cool!
The Papyrus layers functionality has been in incubation for a while, and some may be wondering what it’s all about:
The Layers mechanism allows to build different views of an underlying UML diagrams by applying selections rules as well as graphical transformation operators.
You can read the description of this function in the Papyrus Wiki, and you can also see it in action in this YouTube video:
Yesterday, my minion Maximilian went to the Automotive Software Development Conference (Euroforum) and presented me and my Industry Consortium!
I hope I made a good impression (I’m sure Maximilian did a great job)!
Maybe one day, you will be driving a car with software designed with my help!
Thanks to my Minion Sébastien for pointing this out:
System modelling in AMASS with Papyrus
If you work with Cyber-Physical Systems (CPS) and do not know about AMASS, I invite you to have a look at their objectives.
This is another great example of the strength of the Papyrus solution, especially when mixed with other Eclipse and PolarSys solutions!
One of my minions (from Queens’ University) pointed out an interesting document titled “Robotics 2020 Multi-Annual Roadmap.” from Spark -The Partnership for Robotics in Europe.
It is a very interesting read, especially for those, like me, who are involved in the Eclipse PolarSys Rover project and the Papyrus Industry Consortium!
I especially like the following blurbs:
From printed page 248 (go to page 258 in the PDF):
“Model based methods are needed at the core of all complex robot systems and through
the lifecycle. To address increasing complexity, a shift from human-oriented document-driven
approaches to computer-assisted tools and a computer processable model-driven approach is
needed in order to gain from design support processes”
And from printed page 251 (go to page 261 in the PDF):
“Model-driven software development and domain specific languages are core technologies
required in order to achieve a separation of roles in the robotics domain while also improving
composability, system integration, and also addressing non-functional properties”
Many of these aspects are are already part of work that has been one on me.
This is exactly where I can and will make a difference!
Shoutout to my minion GD for making me aware of this!
For the upcoming Oxygen release, I am getting a new, improved architecture framework that is aligned with ISO 42010.Now, I’m not (yet) an expert in this, but my minions are! And they have created a nice YouTube video explaining what it does and what it provides to Toolsmiths
Now, I’m not (yet) an expert in this, but my minions are! And they have created a nice YouTube video explaining what it does and what it provides to Toolsmiths.
If you are a toolsmith for Me, hope to become one or are just curious, you must go see it (and the other Me videos on YouTube)!
If you are not aware of the Modeling Languages blog, you are missing one of the best sources of up-to-date modelling information on the web! And I’m not just saying that because of the recent great interview about me!
Modeling Languages’s Jordi Cabot provides us all with a great interview of Francis Bordeleau, chairman of my Industry Consortium and Ericsson employee, about my past, growth, and future.
In this post, Jordi stated:
I believe this interview is interesting not only for people using Papyrus (or looking for a Eclipse-based modeling tool to use) but it includes many valuable insights for all of you trying to push various open source initiatives and aim for their sustainable development.
And I can’t agree more!
The discussion covers a lot, from Ericsson’s belief that they need to control their tool destiny and that the best way to do this is to be part of it (hint: Open source ME!), to my evolution and the creation of the Me Industry Consortium, enabling many companies to work together to make me better and providing me with more minions!
Thanks to Jordi and Francis for this exposé!