Papyrus-RT/User/User Guide/Early Adopter

Early Adopter

General Considerations

Papyrus-RT is a work in progress and continually evolving in an agile way, where improvements can occur frequently.

Papyrus-RT also rely on the Papyrus platform which may require changes to improve its capabilities.

Our approach is to use this agile way of working to our advantage to continually drive to a definition for a minimal viable product. In order for this to work, we rely on all interested parties to provide feedback on the tool. This feedback is what drives us forward while continually improving and innovating in a way to meet our users’ needs, expectations, and goals.

Installing Papyrus-RT

There are currently two ways for early adopters to experience Papyrus-RT:

• User installation (you came from there)
• Tester installation

User Installation

Installation instructions found are found in the User Guide: Installing Papyrus for Real Time

This installation procedure provides access to the formal releases, the latest of which is, at the time of this page creation, v0.7.2 from December 2015. This may not provide you with the best view of what is currently available. There have been many major changes since then. However, it does provide you with a stable release that will not change.

Tester Installation

Installation instructions found are found in the Tester installation of Papyrus for Real Time

This installation procedure provides testers with the latest development build of the tool, and it is not unusual to have multiple such builds during the day. This is required for our tester to quickly validate new functionality in order to move forward.

Once installed, the tool will not change unless you explicitly update it.

Because of this approach and the inherent potential instability, there can not be any waranties as to the stability of these builds nor that any particular feature is fully implemented. As such, use at your own risk! This warning appears as part of the installation instructions for this version.

In the context of your evaluation, we will try to keep you informed of the quality of the builds.

Current State

2016-06-03

We consider the following as being the state of the tool:

Structure modeling is at a satisfactory point. This means that the user experience is good and that you can accomplish all tasks related to capsule structure and protocol definition. You may encounter a few isolated usability issues, which we encourage you to report. Note that we do not yet have an implementation of capsule or protocol inheritance.

State machine modeling is probably still at an “expert-friendly” level in many areas. However, this is currently a focus for part of the development team and there will be big improvements in the upcoming weeks. There are also still usability issues and some state machine diagram artefact rendering issues (e.g., with external self-transition after a restart of the tool). Hierarchical state machines are not currently supported, but you can use sub-states in state machines to achieve similar capability (with obvious limitations).

Code generation and the accompanying runtime is currently working well. If a problem is encountered in this area, doing a “make clean” in the CDT project where the code is generated and a “regenerate” is likely to solve any lingering issues.

All other capabilities, e.g., sequence diagrams and activities, are still at the Papyrus UML level and have not yet been adapted to UML-RT.

Feedback

If you have any further questions, please do not hesitate to contact us directly. Evaluating a new, complex tool like Papyrus-RT can be a difficult exercise and we would like to help you getting through it.

Thank you for you interest in this technology.