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!

Papyrus’s Photonic 4.0!

It had to happen:¬†Papyrus is now available at version 4.0!¬†That’s Papyrus “Photon” for those of you who follow the Eclipse release names.

Curious about what was done in this release? You can find that in the list of addressed issues (a.k.a., the bug list). The following topics are addressed:

  • A new preference has been introduced to keep stereotype application with¬†their base element see¬†StereotypeApplication Preference
  • The hyperlink navigation has changed see¬†Hyperlink Navigation
  • Add a preference page to configure the visualization of¬† external decorator¬† see¬†External Decorator
  • Add auto-completion to select the type in the property view see¬†¬†Auto complete type
  • Add an export to HTML to see model without papyrus see¬†HTML Export
  • Development and adaptation of the Layer tool for the diagrams¬†Layers¬†.
  • Synchronization with ELK see¬†ELK adaptation
  • Tables improvements:
    • display of a string instead of N/A
    • Matrix improvements
    • save by UUID not the positon
  • Diagrams improvements:
    • some problems about the name label of ports have been fixed
    • some resize action in the class diagram have been fixed.
    • sequence diagram – Better movement¬† management of Elements, introduction of combined fragment, RCPTT tests.
  • ¬†Integrate a¬† tool to adapt your model based on the modification of the profile
  • Architecture framework¬†: stabilization (easier customizations/modifications by the users) and bug corrections

Want to try it out? Here are a few links to help you:


(* In case you were wondering, “RCP” stands for “Rich Client Platform ūüėČ

New Papyrus-based tool!

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).

Papyrus Coding Day 2018

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)