Eclipse Community Forums: Papyrus » Best route for managing requirements

Home » Modeling » Papyrus » Best route for managing requirements

Best route for managing requirements [message #1156382]

Sat, 26 October 2013 10:12

Eclipse User

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

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

Tue, 12 November 2013 05:11

Eclipse User

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

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

Tue, 12 November 2013 11:53

Eclipse User

Hi Michael!

Sounds very interesting, any time frame (weeks, months, a year)?

Regards,
Tomas

Re: Best route for managing requirements [message #1183396 is a reply to message #1183118]

Tue, 12 November 2013 16:05

Eclipse User

Hi Tomas,

Quote:

Sounds very interesting, any time frame (weeks, months, a year)?

Hopefully this year.

Best,

- Michael

Previous Topic:	Notation file blank after failed search
Next Topic:	loop node

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 25 23:09:25 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter