This document summarizes the integration between IBM Rational DOORS and HP Quality Center. It provides role-based access that brings functionality and data to users in their preferred tools. The integration facilitates requirements-driven testing by enabling requirements analysts to define testable requirements and qualification criteria, and allowing QA/testers to develop tests against these requirements. It also supports release management based on requirements and quality measures. The integration provides traceability between requirements and tests to help ensure changes are not missed and that testing is sufficient.

1. IBM Rational DOORS – HP Quality Center Integration 1

2. Integrating the project team

3. Requirements-driven testing Test Status Test Design Test Execution Quality is conformance to requirements Requirements Management Requirements Management Rational DOORS Test Status Test Planning HP Quality Center Basing tests onrequirements can help ensure that deliverables meet customer expectations Test Design Test Execution Process automation and increased focusThe test team is working against the right set of requirements

4. Potential benefits of requirements-driven testing Providing a requirements-based integration between Rational® DOORS® and HP Quality Center can help enable: The requirements analyst to focus on delivering testable requirements with clearly defined qualification criteria The quality assurance (QA)/tester to focus on developing tests against a known set of requirements The performance of release management based on requirements/quality measures rather than on statistics of test pass/failure

5. Rational DOORS – Quality Center integration overview Role-based, helping to bring functionality and data to users’ preferred tools Both Rational DOORS users and HP Quality Center users

6. Role: analyst Tests ? Analyst The analyst is a Rational DOORS user principally interested in requirements management Specifies the qualification criteria that must be met by testing Needs to know that requirements are tested Performs impact analysis to cover requirements and test Wants to be involved with release review boards

7. Role: QA/tester The QA/tester is a Quality Center user principally interested in test management and execution Uses the qualification criteria as test requirements Needs to be involved with requirements review Establishes traceability to requirements Investigates test failures Requirements ? HP Quality Center QA/tester

8. Role: manager (system review board) System review board (SRB) Analyzes impact of defects (priority, severity) Has the final say regarding release decision Test managers Influence the SRB through confidence that they have an efficient test process that is based on the requirements Development managers Influence the SRB based on comparing the latest test information against their development efforts Analyst managers Influence the SRB with the full business impact of making a release based on whether requirements have been met or not

9. Role: integration administrator The integration administrator is interested in automating as much of a project lifecycle as possible Restricted to a limited number of people Understands more about the integration than “standard” users Interested in making sure that users are controlled Wants to make sure that the integration runs smoothly with minimal adverse business impact

10. But what does it do?

11. Facilities within HP Quality Center See Rational DOORS data inside the requirements tab in Quality Center Test against requirements rather than simply against what is built

12. Facilities within Quality Center (continued) Map Rational DOORS data into other parts of Quality Center, such as the test design Modify Rational DOORS data to aid communication Limited to user-defined attributes

13. What happens next? Qualification criteria can be reviewed, and comments can be entered into Quality Center Existing functionality within Quality Center Automatic generation of template test information from the qualification criteria Control over requirements changes through traceability alerts Similar to Rational DOORS suspect links Test execution helps raise defects that are indirectly associated with requirements

14. Facilities within Rational DOORS Manually instigate transfer of information between Rational DOORS and Quality Center

15. Facilities within Rational DOORS (continued) Associations created within Quality Center seen as Rational DOORS links Use standard Rational DOORS facilities to review tests Suspect links to help ensure that requirements changes are not missed

16. Facilities within Rational DOORS (continued) Quality Center information seen as Rational DOORS modules Requirements, tests, defects, etc. Full impact analysis, including test data “Statement of quality” (SoQ) alongside requirements Three levels of detail: Boolean, defect list, full test summary Defect monitoring against requirements Business criticality set by analyst for prioritization Traverse into Quality Center if required

17. Statement of quality attributes

18. Roll-up results

19. Roll-up results (continued)

20. Detailed analysis Analyst now has detailed information to help identify what needs to be fixed

21. Synchronize SoQ attributes

22. Facilities available to the integration administrator Data-set definition Defines how much information should be visible when seeing the same information in Rational DOORS and HP TestDirector for Quality Center Attribute mapping Configures how Rational DOORS information is seen in Quality Center Configures how Quality Center information is seen in Rational DOORS Client installation for remote administration Individual named-user authentication to help improve security

23. Synchronization controls Configure synchronization Automated Manual

24. So what?

25. Potential analyst benefits Better visibility of test plan can potentially lead to improved system quality Review construction of the audit trail to help verify that requirements have been planned to be tested Monitor test status against requirements to help identify business impact Role-based integration within Rational DOORS Traceability columns on requirements and test Reporting facilities Suspect links

26. Potential QA/tester benefits Work against a defined set of requirements Help improve system quality while controlling an efficient test process How much testing is enough? More efficient test “autopsy” Is a defect in the test, implementation or requirement? Traverse audit trails back to original requirements analysis Role-based integration Combined reports from within Quality Center Traceability alerts help avoid loss of requirements changes

27. Potential manager benefits Quality assurance statistics alongside requirements can help ensure that: Business criticality can be understood and traced back to user need Overall development process is prioritized commercially rather than technically Statistics aggregated up through the requirements hierarchy Faster identification of overall system quality Easier to communicate quality assurance to the end customer

28. Potential overall benefits More cohesive organizations, smaller learning curves Can see information from other disciplines without having to move outside a preferred working environment Support for improved system quality Providing a connection between the analysts and the testers can improve likelihood that clear acceptance objectives will be both defined and met