Functionality of RRC3.0 M13

Several questions with RRC M13.

How do you integrate or import requirements from RequisitePro with M13 of RRC, I could import a RequistiePro baseline in M12 but there is nothing to support this or integrate with RequisitePro in M13?

The RTC 3.0 M13 eclipse client cannot connect to the RRC applicaiton as it identifies the client to be a different versions than the server, how do we access requirements stored in RRC in eclipse?

The ReqPro data migration utility was enabled in the M9 (Beta 2a - Dec 10th 2010) to allow customers to have the early opportunity of testing their own data in RRC and get a better feel for how their development process would be supported. The feedback from these early mile stones has been very helpful for customers and IBM development alike.

The ReqPro migration utility has now been disabled in the M13 mile stone as further work goes on to enable RRC to support ReqPro data fully. Specifically we know that we need to still support multi-enumerated attributes, handle a wider variety of ReqPro data shapes and sizes, etc..

We anticipate that we will expose the utility again shortly when development feel it is in a state to do so. We clearly still intend to support ReqPro migration for RRC.

If you need to still test your ReqPro data in RRC you will need to focus on using one of the previous milestones (M9 or M12) at this time.

Jared Pulham
Product Manager - Requirements Management Tools

Several questions with RRC M13.

How do you integrate or import requirements from RequisitePro with M13 of RRC, I could import a RequistiePro baseline in M12 but there is nothing to support this or integrate with RequisitePro in M13?

The RTC 3.0 M13 eclipse client cannot connect to the RRC applicaiton as it identifies the client to be a different versions than the server, how do we access requirements stored in RRC in eclipse?

The ReqPro data migration utility was enabled in the M9 (Beta 2a - Dec 10th 2010) to allow customers to have the early opportunity of testing their own data in RRC and get a better feel for how their development process would be supported. The feedback from these early mile stones has been very helpful for customers and IBM development alike.

The ReqPro migration utility has now been disabled in the M13 mile stone as further work goes on to enable RRC to support ReqPro data fully. Specifically we know that we need to still support multi-enumerated attributes, handle a wider variety of ReqPro data shapes and sizes, etc..

We anticipate that we will expose the utility again shortly when development feel it is in a state to do so. We clearly still intend to support ReqPro migration for RRC.

If you need to still test your ReqPro data in RRC you will need to focus on using one of the previous milestones (M9 or M12) at this time.

Jared Pulham
Product Manager - Requirements Management Tools

Jared,

Thanks for the feed back we have used the import facility in the previous mentioned milestones, but they had other stability issues that was causing lots of problems just playing and validating our process. M13 has so far had much less issues, but wanted to demonstrate the platform with both a new project and existing. Will wait for Beta3 to see if the functionality is enabled there.

Do you plan on having RRC integrated with Eclipse or is the view to only allow the Web RRC interface.

Regards

Trevor.

Several questions with RRC M13.

How do you integrate or import requirements from RequisitePro with M13 of RRC, I could import a RequistiePro baseline in M12 but there is nothing to support this or integrate with RequisitePro in M13?

The RTC 3.0 M13 eclipse client cannot connect to the RRC applicaiton as it identifies the client to be a different versions than the server, how do we access requirements stored in RRC in eclipse?

The ReqPro data migration utility was enabled in the M9 (Beta 2a - Dec 10th 2010) to allow customers to have the early opportunity of testing their own data in RRC and get a better feel for how their development process would be supported. The feedback from these early mile stones has been very helpful for customers and IBM development alike.

The ReqPro migration utility has now been disabled in the M13 mile stone as further work goes on to enable RRC to support ReqPro data fully. Specifically we know that we need to still support multi-enumerated attributes, handle a wider variety of ReqPro data shapes and sizes, etc..

We anticipate that we will expose the utility again shortly when development feel it is in a state to do so. We clearly still intend to support ReqPro migration for RRC.

If you need to still test your ReqPro data in RRC you will need to focus on using one of the previous milestones (M9 or M12) at this time.

Jared Pulham
Product Manager - Requirements Management Tools

Jared,

Thanks for the feed back we have used the import facility in the previous mentioned milestones, but they had other stability issues that was causing lots of problems just playing and validating our process. M13 has so far had much less issues, but wanted to demonstrate the platform with both a new project and existing. Will wait for Beta3 to see if the functionality is enabled there.

Do you plan on having RRC integrated with Eclipse or is the view to only allow the Web RRC interface.

Regards

Trevor.

The next major version of RRC will be web only supporting IE 7,8 and Firefox 3.5, 3.6