Groundbreaking changes to Eclipse Papyrus?

That's what a short, pithy saying can become: At the end of last year, jaxenter asked me, Which software product disappointed me in 2015. Unfortunately, I could not avoid mentioning Papyrus, an Eclipse component for modeling in UML and SysML. This statement was made by the Papyrus Blog whereupon jaexenter entered into a respectful dialog on German and English with Charles Rivet organized. I don't want to repeat here what has already been discussed there. Instead, I would like to summarize here what has changed at Papyrus this year and why I have high expectations for the Neon release.
What is papyrus?
Papyrus is many things: In the market it is perceived as a UML modeling tool. There is some truth in that, but it doesn't quite capture it. Yes, you can use it download and start modeling immediately. However, this has not been possible for very long, as Papyrus was originally a component that could be added to existing Eclipse installations.
Incidentally, not only UML is supported, but also SysML. And there are many extensions, such as the extension for real-time modeling (RT).
Misunderstood: Papyrus is a framework, not a tool
Until recently, Papyrus was regarded by developers as a component to be installed, a framework technology. As such, it is perfectly suited. However, this was not communicated well, as Charles Rivet admits. It is therefore not surprising that users became frustrated.
Papyrus was presented as an all-encompassing UML-based modeling tool, whereas many of us now believe that it should have been presented as a framework or platform (Charles Rivet)
This is suggested by the picture above, which is taken from the Elevator Pitch Video comes from. There it is arranged on a staircase, which suggests that users do not have to build a tool platform from scratch, but can start with a solid basic technology. However, it also shows that a few more steps need to be invested in order to reach the goal of a functioning tool chain.
Open source comes of age
Despite this communication problem, it is amazing what expectations we now have of free or open source software. And that is certainly one of the reasons for my initial comment. Because it is impressive what Papyrus can do. What I am particularly pleased about is the standard-compliant implementation of the UML and SysML standards: I have always been an advocate of providing an open source reference implementation for standards (which is also one of the reasons why I have been using the Eclipse Requirements Modeling Framework I helped bring into being).
The game changer: Papyrus Industrial Consortium
The fact that open source has grown up and can be underpinned by a solid business model is what the Papyrus Industrial Consortium (IC) show. The IC is made up of four groups: Users, providers, contributors and universities. The IC has strong partners and therefore has enough financial and human resources to make a real difference. As the IC is just starting its work, it will influence the Neon release for the first time.
High expectations for Papyrus Neon
Charles Rivet gives a preview of what we can expect in Neon. Installation and general user experience are to be improved to make it easier to get started. There will also be product lines. The resulting specialized tools would have a clearer focus, which would increase their added value.
My recommendation
The move from Kepler to Luna has already improved a lot in Papyrus, and I'm also hearing a lot of good things about Mars. I assume that we will see many improvements in Neon. This is the first time that the IC has had an influence on this version. As there will also be a version jump from 1.x to 2.0 with Neon, I recommend anyone interested who can wait to jump straight into Neon, which will be released in June 2016. As soon as it is available, I will evaluate it and present it here.






Quote „to start directly with Neon, which was published in June 2016.
will be. As soon as it is available, I will evaluate it and post it here
imagine.“ .... When I search for „neon“ here, I only find this page here.
Papyrus Neon is available here: https://www.eclipse.org/papyrus/download.html
Apart from that, Papyrus for Information Modeling is said to be quite good. The „Development Build“ is also based on Neon: https://wiki.eclipse.org/Papyrus_for_Information_Modeling#Development_build
To my shame, however, I have to admit that I haven't tried either of them yet.
Greetings,
- Michael
Thanks for the quick feedback!
I'll download it and give it a try.
Greetings, Harald