It’s official! The Papyrus IC is a sponsor of Models 2018.
It’s members and users will be there to show me to anyone interested – Please go meet them so they don’t feel too alone out there!
I do not have the details yet, but I will be sure to pressure my minions to get me their game plans so I can let you all know!
There were already a few posts [here] and [here] in which we talked about the new Papyrus UMLLight variant. Well – it is one step closer to completion.
My sources tell me that the scope has been defined and that requirements have been written, and that a request for quotation has been created and will soon be published!
UPDATE: The scope should be similar to of OMG’s OCUP2 Foundation level content.
Stay tuned for more information through official channels!
And of course, you will know about it here!
Good news! The Papyrus Industry Consortium’s steering committee has approved the creation of a “Papyrus UML 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).
Thanks to Eclipse, my industry consortium is taking a leap into Enalean’s Tuleap!
Here are the three projects (communities) that have been created along with their descriptions, taken from each project:
|This project is the Papyrus IC’s way of openly managing the Papyrus projects and products This is our way of informing the Papyrus community about what we are doing and, in return, to get feedback from the Papyrus community. This is a source of information for the community and by the community — this is your community!
|| This project is where the Papyrus product line management lives. This is where we do the nitty-gritty work so that you can enjoy our fabulous Papyrus-based products. Unfortunately, most of what we do here can be boring, day-to-day stuff, and we want our developers, designers, and managers to keep their focus, so we keep them in a quiet, private area.
But don’t worry, any significant news, decision, development, etc. Will be made available in the Papyrus IC project!
|This project is to help the Papyrus Industry Consortium’s Steering community to manage the consortium projects, products, and assets. This project is private to protect confidential information (e.g., user and supplier confidential information, financial information)
But don’t worry, Steering committee information for public consumption will be provided in the Papyrus-IC project!
My minions are still working at the governance of the projects and at transferring information from the Papyrus IC Steering into the other projects (especially to Papyrus-IC), so please be patient with them!
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!
My industry consortium is hosting a Birds of a Feather (BOF) session at EclipseCon Europe!
You are all invited to go, mingle, and talk about me with my minions on Tuesday, October 24, 2017, from 19:30 to 20:30!
And don’t forget to thank my EclipseSource minions for organizing this!
You can also look at the official PolarSys Papyrus Industry Consortium blog posting!
[PS: isn’t a “birds of a feather” session just perfect for me?!]
Well, you can’t be more official than a press release from the Papyrus Industry Consortium! I know I already mentioned this release, but this is more official!
This is what happened today for Papyrus for Real Time (Papyrus-RT) v1.0!
You can see the press release for a limited time on the main Eclipse page and on the Eclipse Foundation Press Releases page, or on its own page!
And two of my minions were nice enoug to provide nice quotes about my real time variant. A special thank you goes out toJean-Michel and Bran!
Interested in trying out a free Domain-Specific, model-driven tool for embedded systems? Give Papyrus-RT a try!
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!
On Friday, March 31th at 16:00 CET, 15:00 GMT, and 11:00 EDT, the Papyrus Industry Consortium’s (Me-IC!) Research and Academia (“PIC-RAC“) committee will host their fourth webinar of the year.
The topic is on an academic perspective on software product lines with speakers from Østfold University College, University of Passau, and TU Braunschweig.
See this link for the connection information.
Although the Papyrus for Real Time (Me-RT) project is not officially on the Eclipse Release Train, that team has indicated, judged on their newly published roadmap.
It should be noted that it is through an initiative of the Papyrus Industry Consortium that these roadmap will become the norm for all the Papyrus product line!
This is a good thing as it should formalise the release schedule for all my variants!
The Papyrus-RT roadmap has also shown us more details about the next two releases:
- Papyrus-RT v0.9 is to be released with Neon.3 in March
- Papyrus-RT v1.0 is to be released with Oxygen in early July
From what I have been told, meeting these deadlines will be feasible, especially as the time between v0.9 and 1.0 will be spent cleaning up the offering for the 1.0 release, with no additional functionality.
All the efforts around me continue to be so interesting!