It's all about the answers!

Ask a question

Is it possible to merge RRC artifacts in a module

Chris Palmer (251112) | asked Jun 27 '14, 5:36 a.m.
 I have imported various requirement artifacts into RRC with some level of success.

During the import single sections of the artifact have been split into multiple sections and I would like to be able to easily merge these back into a single artifacts. I can do this in a long winded manner using copy and paste but a more efficient method would be very useful.


Accepted answer

permanent link
Mike Jaworski (1.4k6) | answered Jun 27 '14, 8:42 a.m.
 Hi Chris,

I don't think it is currently possible to merge artifacts within a module for RRC. However, I can give you two suggestions:

1) There appears to be an open enhancement request for this functionality, so you can add your voice to this work item: Allow merging/splitting artifacts (in modules) (70433)

2) The RRC/DNG team is currently working on an integration for the product, and are calling this integration "DOORS Next Generation with Configuration Management". The configuration management is happening through an application called VVC (version, variant, and configuration management), which will allow a very diverse set of new functionality, and unless I'm mistaken then merging artifacts within a module should be one of the included features. If you'd like to take a test run of RM-VVC, you can download a beta release here: Rational DOORS Next Generation with Configuration Management 5.0 beta 1

You can also find more information about RM-VVC on this wiki page: RM-VVC

Hope this helps,
Mike Jaworski
Chris Palmer selected this answer as the correct answer

Paul Ellis commented Jun 30 '14, 11:27 a.m.

Just to note that the RM-VVC page quoted here seems to have been usurped by RDNGCMBeta

2 other answers

permanent link
Taly Hotimsky (2714457) | answered Jun 27 '14, 11:52 a.m.
To the best of my knowledge the VVC merge is focused on allowing different versions of the same requirement to be merged, so version A from stream 1 and version B from stream 2 would be merged in version AB.

That's quite different from merging (or combining) different artifacts in a Module. The WI Michael pointed though seems to be the way to get this done. Hopefully it'll be implemented soon (but as the couple past releases were focused on Modules, I wouldn't expect too much effort to go into that for a while). 

permanent link
Kirk Grotjohn (1.2k3) | answered Jun 30 '14, 11:18 a.m.
 Note that the work item referenced above points to an extension that could potentially be used for this purpose:
Taly is correct above... the Configuration Management capability will not help in merging/splitting separate artifacts.

Your answer

Register or to post your answer.