ROS Resources: Documentation | Support | Discussion Forum | Service Status | Q&A

Safety Working Group meeting - requirements management tools discussion

After a brief hiatus, myself and a few others are making another go of the Safety Working Group.

This time we are going to be starting from a tasks point of view. Our first target is improving the use of and tracing of requirements, as this is a fairly fundamental part of building a safety-critical system.

The meeting will start at 2020-04-30T14:00:00Z and run for up to two hours, depending on how much discussion we have. See the ROS 2 events calendar for the meeting details, including the teleconference link (which is also reproduced below).

We will be having two talks followed by some discussion:

  • Mehul Sagar from Apex.AI will be talking about the tool chain they use to manage and trace their requirements from creation through implementation to test
  • Florian Friesdorf and Marko Durkovic will be talking about the tool they created for Apex.AI, called trice, that provides some simple requirements tracing and which can potentially be open-sourced.

Following these talks, we will discuss what we can do to bring trice to the ROS world as an open-source, simple requirements management tool. Our goal is to provide a base level of requirements tracing.

Please come along if you have interest in this topic, and especially if you want to help out!

Join Zoom Meeting

Meeting ID: 266 509 195

One tap mobile
+19292056099,266509195# US (New York)
+16699006833,266509195# US (San Jose)

Dial by your location
+1 929 205 6099 US (New York)
+1 669 900 6833 US (San Jose)
+81 524 564 439 Japan
+81 3 4578 1488 Japan
+49 69 7104 9922 Germany
+49 30 3080 6188 Germany
+49 30 5679 5800 Germany
+34 917 873 431 Spain
+34 84 368 5025 Spain
+44 203 051 2874 United Kingdom
+44 203 481 5237 United Kingdom
+44 203 966 3809 United Kingdom
+44 131 460 1196 United Kingdom
Meeting ID: 266 509 195
Find your local number:


Thank you to all who attended. We had a good number of attendees at last, and some interesting discussion. The meeting minutes are now available at the working group’s website.

Our next meeting will be in two weeks, at 2020-05-14T14:00:00Z. We will be discussing how we want to use a requirements tool and what work is necessary to get trice to this level.

1 Like

Thanks @gbiggs – this was a great meeting. As discussed, we put together an example repository at to outline some of the features we would expect from a requirements management tool. More details are captured in this issue. Happy to give an overview in our next meeting.

1 Like

I’d suggest not to use something like Rational DOORS. From experince I know that working with it is any other than fun. Biggest pain point is linking production source code to low level requirements, linking test code to low level tests, it’s based on a database which implies that you are limited to mostly text based requirement and test definitions. However in case people have to use these tools it would be great if the ROS2 solution would provide interfaces for integrating with them.


I think I can say with 100% confidence that Rational is not on the table. Aside from the prohibitive cost for any of us working in the open source space (even if for a company), the complexity is ludicrous and the learning curve looks something like the EVE Online learning curve.

If the ability to integrate requirements tools together is desired, there are interchange formats that can do that but I haven’t used any of them directly myself.

Awesome. :smile: I didn’t know the EVE Online Learning Curve. However there are laying around some fallen people w.r.t. Rational DOORS for sure.