RRC (or DRP) - Requirements Modelling Capabilities

Looking at the capabilities in RRC, it provides (very high level)

1) Requriements Definition - beats word
2) Business Process Modelling - could export and import this into a more enterprise strength BPM tool (maybe)
3) Use Case Modelling - can export and import to and from RSM/RSA for more enterprise strength design
4) Story Boarding - not sure you really need anything better (I can stand corrected)
5) Collections - yes, mini baselines
6) Snapshots - yes, major baselines

At a very basic level it provides a good portion of the capabilities that you need to do requirements capture. The thing that I'm missing is data modelling? Is there something that I'm missing (very possible), that allows a early logical data modelling capacity, as part of the requriements capture phase? Seems to be an omission

Yes RRC does provide most of what you need to requirements capture. Now if the Data Modeling tool diagrams, can be referenced by a URL, then you can link any requirement artifact in RRC (including glossary terms - can be used as pseudo data entities) to the data model. In fact you can link glossary terms not only to data models, but UI sketches as well.

That said there are various enhancements on jazz.net, for example
http://jazz.net/jazz03/web/projects/Rational%20Requirements%20Composer#action=com.ibm.team.workitem.viewWorkItem&id=4934&tab=data%20model

and

http://jazz.net/jazz03/web/projects/Rational%20Requirements%20Composer#action=com.ibm.team.workitem.viewWorkItem&id=11535&tab=%22data%20m

The plan in the future is expand the types of vocabularies support by RRC.

Looking at the capabilities in RRC, it provides (very high level)

1) Requriements Definition - beats word
2) Business Process Modelling - could export and import this into a more enterprise strength BPM tool (maybe)
3) Use Case Modelling - can export and import to and from RSM/RSA for more enterprise strength design
4) Story Boarding - not sure you really need anything better (I can stand corrected)
5) Collections - yes, mini baselines
6) Snapshots - yes, major baselines

At a very basic level it provides a good portion of the capabilities that you need to do requirements capture. The thing that I'm missing is data modelling? Is there something that I'm missing (very possible), that allows a early logical data modelling capacity, as part of the requriements capture phase? Seems to be an omission

Yes RRC does provide most of what you need to requirements capture. Now if the Data Modeling tool diagrams, can be referenced by a URL, then you can link any requirement artifact in RRC (including glossary terms - can be used as pseudo data entities) to the data model. In fact you can link glossary terms not only to data models, but UI sketches as well.

That said there are various enhancements on jazz.net, for example
http://jazz.net/jazz03/web/projects/Rational%20Requirements%20Composer#action=com.ibm.team.workitem.viewWorkItem&id=4934&tab=data%20model

and

http://jazz.net/jazz03/web/projects/Rational%20Requirements%20Composer#action=com.ibm.team.workitem.viewWorkItem&id=11535&tab=%22data%20m

The plan in the future is expand the types of vocabularies support by RRC.


If you provide the integration with RSA/RSM through Rational Collaborative Architecture Management this would solve this important issue for us.

Is it still the intention to support links to Rational modeling tools through Rational Collaborative Architecture Management?

Looking at the capabilities in RRC, it provides (very high level)

1) Requriements Definition - beats word
2) Business Process Modelling - could export and import this into a more enterprise strength BPM tool (maybe)
3) Use Case Modelling - can export and import to and from RSM/RSA for more enterprise strength design
4) Story Boarding - not sure you really need anything better (I can stand corrected)
5) Collections - yes, mini baselines
6) Snapshots - yes, major baselines

At a very basic level it provides a good portion of the capabilities that you need to do requirements capture. The thing that I'm missing is data modelling? Is there something that I'm missing (very possible), that allows a early logical data modelling capacity, as part of the requriements capture phase? Seems to be an omission

Yes RRC does provide most of what you need to requirements capture. Now if the Data Modeling tool diagrams, can be referenced by a URL, then you can link any requirement artifact in RRC (including glossary terms - can be used as pseudo data entities) to the data model. In fact you can link glossary terms not only to data models, but UI sketches as well.

That said there are various enhancements on jazz.net, for example
http://jazz.net/jazz03/web/projects/Rational%20Requirements%20Composer#action=com.ibm.team.workitem.viewWorkItem&id=4934&tab=data%20model

and

http://jazz.net/jazz03/web/projects/Rational%20Requirements%20Composer#action=com.ibm.team.workitem.viewWorkItem&id=11535&tab=%22data%20m

The plan in the future is expand the types of vocabularies support by RRC.


If you provide the integration with RSA/RSM through Rational Collaborative Architecture Management this would solve this important issue for us.

Is it still the intention to support links to Rational modeling tools through Rational Collaborative Architecture Management?

Yes using OSLC for linking.