Papyrus

Introduction

Papyrus is an UML modelling tool based on the Eclipse Modelling Framework (EMF): http://www.eclipse.org/papyrus/ \\ It supports the UML 2.3 standard facilitating the ecore UML meta model and allows for model exchange based on the diagram interfache format (.di). UML profiles ares supported, too. At the moment, you will get Marte as well as SysML profiles to work with.

Papyrus comes with a good documentation. However, on this page you will find best practices and further notes for working with papyrus.

Best Practices

One of the major best practices is: Download the UML 2.3 superstructure documentation and open it on your second screen. Most issues people have by using Papyrus is not because of the tool but because of not beeing familar with the UML ;)

Composite Diagram

Component instances and connectors must be contained by the same parent element (the composite component realized by the component instances). Ports can and should be specified contained in the component specification element.

To define required interfaces of a port, the attribute isConjuncted must be set to true (advanced tab in the properties) and the type of the port must be set to the intended interface. With a right-click on the port, the context menu provides an additonal action to manage the interfaces. However, the interface management dialog does not allow configure the required/provided character of the interface selected as type. Furthermore, don't be confused by the warning that your required interface (in case of isCOnjuncted set to true) will not appear in the provided interface list. (right it doesn't make sense at all ;) )