Blogs about Jazz

Blogs > Jazz Team Blog >

Surfing the Collaborative ALM web – RTC, RQM, and RRC

In the user forum and on other occasions the question has come up about how the Jazz based products Team Concert, Quality Manager, and Requirements Composer play together. To help explain this, I’m pleased to point you to a recording of a demo we recently presented at a Rational VOICE of the Customers event. The demo shows a prototype implementation of these product integrations. We used an outside-in approach to define scenarios where analysts, developers, and testers collaborate across these tools on a development project. The demo shows three scenarios:

  1. Create Release Plan – the analyst defines requirements in IBM Rational Requirements Composer. He links his requirement to a Plan Item in Rational Team Concert. He can traverse the link and prioritize the release plan.
  2. Plan Alignment – the teams align their iteration plans. The release plan-items are added to the development iteration plan. The analyst elaborates requirements to add detail to a Story workitem, that is tracked in a Team Concert project. The test team builds their test plan with insight into the development iteration plan and the requirements. Links are created across Requirements Composer defined requirements, Team Concert stories, and Quality Manager Test Cases.
  3. Find and Fix a Test failure – the tester executes a test and discovers a defect. The defect is filed against the Rational Team Concert development project, with bi-directional links back to the test execution. The development team triages and fixes the defect. The tester monitors the status of the defect using his dashboard. When he sees the defect is fixed and the build is ‘green’ he deploys the build then verifies and closes the defect.

A small demo caveat: the application developed by the project is JUnit. JUnit is about developer testing and this can result in confusion in a scenario that is about manual testing. Therefore just consider JUnit as an example application and ignore that it is related to testing.

There is no sound on this demonstration; call-outs are used to explain the action as it occurs on the screen.

The scenarios described above are just the beginning. We plan to improve upon these scenarios in addition to sharing new scenarios. Please tell us what you think.