Papyrus 4.4 is available

I’m a bit late with this posting…better late than never!

A new version of papyrus 4.4 is available:

SysML1.6 ( a forum topic will be send when the market place is available)

  • SysML 1.6 profile done
  • The SysML requirement diagram shall be implemented
  • The SysML Parametric diagram shall be implemented
  • The SysML BDD shall be implemented
  • The SysML IBD shall be implemented
  • The SysML requirement table shall be implemented
  • The SysML Graphical element type shall be implemented
  • The SysML AF shall be implemented
  • The SysML allocation Matrix shall be implemented
  • The elementype of SysML 1.6 shall be implemented
  • Make SysML 1.6 open source
  • The SysML model explorer customization shall be implemented
  • Add written OCL constraints
  • Implement E3 of SysML 1.6
  • Update SysML 1.6 diagram of profile
  • Add Icon for conjugated Interface block
  • Add compartment of Conjugated Interfaceblock inside BDD
  • The SysML Junit Test shall be implemented
  • Papyrus shall support the migration from SysML 1.4 to 1.6 Papyrus toolsmith

Validation of plugins:

  • you have done your profile to customize papyrus, but you forget extension point, build.xml, dependencies. We have done a work not only to validate profile but the plugin that contains the profile
  • the work has also be done for plugins that contain elementTypes model.

Improve developer experience to use plugin org.eclipse.papyrus.infra.core.sasheditor

  • Decrease the usage of internal eclipse code
  • Papyrus has developed at the beginning a new kind of editor compnoent sasheditor. To be more stable, we have ask to open api to eclipse in order to improve integration to eclipse.
  • Dedicated API have been created from use cases in order to help developer to access to this graphical composite; add a new editor inside papyrus, get active editor…
  • These usecases will be published inside a plugin developer doc :
  • It is will be like a javadoc that has a list of use cases and references API that implement these usecases.


  • Papyrus will provide a documentation generator targeting LibreOffice file (odt).
  • This generator will allow to the user to describe how to cross the UML model to create the document
  • This generator will allow to the user to define a document template to use for the generation
  • This generator will support image and table insertion.

Go try it and send me your comments!


The end of the Papyrus IC

With the end of the Eclipse PolarSys adventure comes that of the Papyrus IC.

In the end, we could not maintain the momentum to move forward.

We failed to grow our community, and in doing so, we failed our community.

But this is not the end of Papyrus! Not by a long shot!

Papyrus is more vibrant than ever.

New variants are still being build, e.g., Papyrus UMLLight, new released are still provided with continued improvements, and a new major release is in the plan for the project.

As well, many companies, research groups, schools, and individuals are still teaching with it, working with it, improving it.

A personal shout out to EclipseSource employees and Queens University’s faculty and students for their dedication to the Papyrus products and to Francis, our glorious leader for his perseverance.!

For the time being, this blog will remain a beacon of light for Papyrus . But here will be a time where it will have to close. Other endeavours await the author.

If anyone one want to help or take it over, please let me know

Getting Started with Papyrus UMLLight

Well… It took some time but there is finally a tutorial for Papyrus UMLLight!

This tutorial was developed within the Papyrus UMLLight wiki, so it is available online .

It covers the audience we targeted for this tool, how Papyrus UMLLight is both different and similar to Papyrus , and provides exercises to show its capabilities.

And yes, you can comment about it (on its discussion page)

And now to start work on the musical! ūüėČ

Papyrus UML Light users

In my previous post, I did mention that we had some users in mind that would benefit from using Papyrus UML Light.

I should have given you a hint as to who they are…

Nicole ‚Äď a Papyrus Novice

Nicole is already knowledgeable in UML at or above the OMG’s OCUP2 Foundation or intermediate level contents.

As the project on which ze worked was completed, ze is being moved to a new team that uses Papyrus, a tool with which ze is not familiar.

Nicole’s goal in using Papyrus UML Light is to quickly get familiar with Papyrus UML Light and how it supports UML-based modeling. Ze appreciates and benefits from Papyrus UML Light’s streamlined editor with the most common concepts of UML, so that ze can focus on getting to know the Papyrus UML Light user interface and way of working without being exposed to the full spectrum of UML model elements.

Steve – a UML Novice and Student

Steve is new to the modeling world and has no familiarity with the UML.

Ze is starting to learn about UML and faces the dual tasks of learning to use UML at the same time as learning to use a UML modeling tool.

Using Papyrus UML Light, Steve will be exposed to fewer language and tool concepts at a time, wich results in a lowering of the learning curve.

In addition, the alignment of Papyrus UML Light to OCUP2 (Foundational) is beneficial, as it ensures that ze first deals with the most most important concepts of UML before tackling the more complex aspects.

Brisha – a Basic UML User

Brisha only uses UML from time to time and then only for basic purposes such as documentation, presentations, discussions, etc. Ze is not interested in a full model-based engineering tool or method and rather uses it to “sketch” using UML to ensure common understanding of the graphics. As such, ze only needs the basic concepts of UML. In this context, an easy to use UML modeling tool such as Papyrus UML Light, which provides a reduces user interface an ease of use is easiest to get and adopt.

So, what do you think of our typical users for Papyrus UML Light?

Papyrus UML Light update

First, I would like to which a happy new year that will keep you all in good health (and modeling with Moi!)!

In a previous posting, I mentioned a new variant of Papyrus (me), Well, Papyrus UML Light has progressed progressing  well since then!

This is what happened thus far:

  • Requirements have been defined, including the subset of UML that is being implemented (which involved many people … and voting…)
  • Personae have been defined for our three principal users (Nicole, Steve, and Brisha and their current names).
  • There is a logo:¬†¬†¬†
  • There have been three internal development releases thus far.
  • The “Getting Started” tutorial is progressing.

As usual, I’ll try to keep you up-to-date!

Papyrus UMLLight is go!

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!