I think of RRC V3.0.1 as having six kinds of "integrations"

1. Lifecycle integrations using OSLC. Internet-style "linked lifecycle data" provides traceability to planning, tasks, development activities, and test activities. This creates traceability and information visibility across teams. Products that use this integration today include Rational Team Concert, Rational Quality Manager, RSA Design Manager, and Rhapsody Design Manager. The Focal Point team is working on an integration; you can find the defined scenarios here: https://jazz.net/forums/viewtopic.php?t=18237

In addition one could write utilities to make use of these OSLC APIs to create requirements information in RRC and/or relate it to information in other repositories using a self-standing utility, spreadsheet macros, or as part of another application.

See the CLM project here on jazz.net for more information on supported lifecycle scenarios. Also the jazz.net blog is a good place to learn about what we are doing and why.

2. "Integration by information mashup" combines data sources into (A) dashboards (mashups), which uses OSLC interfaces; (b) into documents, using the built-in Rational Reporting for Document Generation (RRDG) or workstation-based Rational Publishing Engine (RPE); or (C) web-based status reporting based on the Rational Reporting for Development Intelligence (RRDI) component or Rational Insight; both use ETL jobs to load a data warehouse, and reports are created from that data.

3. "Integration by import / export" involves using "lowest common denominator" formats to exchange information. These typically include spreadsheet data (stored in comma-separated value (CSV) files) and documents in a Word processing format (typically MS Word, but also RTF and OpenDocument Text (ODT) formats). RRC can import from and export to these formats.

4. "Integration by URL." You can manually create a link to any URL reachable on the Internet or your intranet. So you can reference standards, web sites, or artifacts in other repositories. Likewise every RRC artifact has its own URL, so you can store a link to it in some other tool's artifacts, for example MS SharePoint or iRise Definition Center.

5. Upload files created by other tools. Let's imagine you like to do your thinking in mind maps. Great. You can upload your maps into your RRC project area, give them attributes, relate them to other artifacts in RRC, include them in collections, include them in review and approval workflows, have group conversations about them. Each file gets its own unique URL, so you can link to it from elsewhere. Requirements information often starts out in PowerPoint presentations or Word docs; these too can be stored "as is" in the RRC project area. When you ask for an uploaded file, RRC (through your web browser) passes the file to the external application registered in your browser for that mime type.

6. Import from RequisitePro. This is a special kind of integration. As I write this RRC V3.0.1 fixpack 1 is available for download here on jazz.net in beta form ( https://jazz.net/downloads/rational-requirements-composer/milestones/3.0.1.1M3 ). The beta functionality reads a RequisitePro baseline and converts the data, requirement types, comments, etc. into RRC native formats. We are working on this, because RRC is the "next-generation RequisitePro" and we want to make it easy for teams to move forward into RRC with information they will reuse on future projects (use cases, terms, non-functional requirements, business rules, etc. etc.).

I hope this is helpful. Integrations are an important part of enabling teams to improve their requirements process and project outcomes. One of the key limiting factors for many teams is that their information is locked into "data islands" (typically office files, but sometimes a repository). RRC can help you to "free" your requirements information for more effective use by a larger set of stakeholders and across the many roles of your project team.