Eclipse Community Forums: Papyrus » Best route for managing requirements

Help

Home

Home » Modeling » Papyrus » Best route for managing requirements

Show: Today's Messages :: Show Polls :: Message Navigator

Best route for managing requirements [message #1156382]

Sat, 26 October 2013 14:12

Tomas Sandkvist

Messages: 149
Registered: October 2013

Senior Member

Can anyone elaborate somewhat on what should be considered as the best route for handling requirements withing the Eclipse context for SysML modeling?

Should I start populating my Papyrus model with requirement elements, or should I use ProR and the ReqIf standard?

I would like to have traceability, if not now at least in the near future.

Regards,
Tomas Sandkvist

Report message to a moderator

Re: Best route for managing requirements [message #1182648 is a reply to message #1156382]

Tue, 12 November 2013 10:11

Michael Jastram

Messages: 235
Registered: April 2010
Location: Düsseldorf, Germany

Senior Member

Hello Tomas,

We're currently working on a generic EMF integration, which would allow Papyrus integration, amongst other things. We described it here:

http://formalmind.com/en/blog/using-rmf-integrate-your-models

Instead of having a generic integration, we once built a prototype of a specialized integration that would synchronize SysML Requirements with one attribute of a corresponding ProR Proxy requirement. We didn't develop this further, as we don't have a business case to support it.

Best,

- Michael

Report message to a moderator