Rational Doors Hp Quality Center Integration


Published on

Rational Doors Hp Quality Center Integration

Published in: Business
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Rational Doors Hp Quality Center Integration

  1. 1. IBM Rational DOORS – HP Quality Center Integration<br />1<br />
  2. 2. Integrating the project team<br />
  3. 3. Requirements-driven testing<br />Test Status<br />Test Design<br />Test Execution<br />Quality is conformance to requirements<br />Requirements Management<br />Requirements Management<br />Rational DOORS<br />Test Status<br />Test Planning<br />HP Quality Center<br />Basing tests onrequirements can help ensure that deliverables meet customer expectations<br />Test Design<br />Test Execution<br />Process automation and increased focusThe test team is working against the right set of requirements<br />
  4. 4. Potential benefits of requirements-driven testing<br />Providing a requirements-based integration between Rational® DOORS® and HP Quality Center can help enable:<br />The requirements analyst to focus on delivering testable requirements with clearly defined qualification criteria<br />The quality assurance (QA)/tester to focus on developing tests against a known set of requirements<br />The performance of release management based on requirements/quality measures rather than on statistics of test pass/failure<br />
  5. 5. Rational DOORS – Quality Center integration overview<br />Role-based, helping to bring functionality and data to users’ preferred tools<br />Both Rational DOORS users and HP Quality Center users<br />
  6. 6. Role: analyst<br />Tests<br />?<br />Analyst<br />The analyst is a Rational DOORS user principally interested in requirements management<br />Specifies the qualification criteria that must be met by testing<br />Needs to know that requirements are tested<br />Performs impact analysis to cover requirements and test<br />Wants to be involved with release review boards<br />
  7. 7. Role: QA/tester<br />The QA/tester is a Quality Center user principally interested in test management and execution<br />Uses the qualification criteria as test requirements<br />Needs to be involved with requirements review<br />Establishes traceability to requirements<br />Investigates test failures<br />Requirements<br />?<br />HP Quality Center<br />QA/tester<br />
  8. 8. Role: manager (system review board)<br />System review board (SRB)<br />Analyzes impact of defects (priority, severity)<br />Has the final say regarding release decision <br />Test managers <br />Influence the SRB through confidence that they have an efficient test process that is based on the requirements<br />Development managers<br />Influence the SRB based on comparing the latest test information against their development efforts<br />Analyst managers <br />Influence the SRB with the full business impact of making a release based on whether requirements have been met or not<br />
  9. 9. Role: integration administrator<br />The integration administrator is interested in automating as much of a project lifecycle as possible<br />Restricted to a limited number of people<br />Understands more about the integration than “standard” users<br />Interested in making sure that users are controlled <br />Wants to make sure that the integration runs smoothly with minimal adverse business impact<br />
  10. 10. But what does it do?<br />
  11. 11. Facilities within HP Quality Center<br />See Rational DOORS data inside the requirements tab in Quality Center<br />Test against requirements rather than simply against what is built<br />
  12. 12. Facilities within Quality Center (continued)<br />Map Rational DOORS data into other parts of Quality Center, such as the test design<br />Modify Rational DOORS data to aid communication<br />Limited to user-defined attributes<br />
  13. 13. What happens next?<br />Qualification criteria can be reviewed, and comments can be entered into Quality Center<br />Existing functionality within Quality Center<br />Automatic generation of template test information from the qualification criteria<br />Control over requirements changes through traceability alerts<br />Similar to Rational DOORS suspect links<br />Test execution helps raise defects that are indirectly associated with requirements<br />
  14. 14. Facilities within Rational DOORS<br />Manually instigate transfer of information between Rational DOORS and Quality Center<br />
  15. 15. Facilities within Rational DOORS (continued)<br />Associations created within Quality Center seen as Rational DOORS links<br />Use standard Rational DOORS facilities to review tests<br />Suspect links to help ensure that requirements changes are not missed<br />
  16. 16. Facilities within Rational DOORS (continued)<br />Quality Center information seen as Rational DOORS modules<br />Requirements, tests, defects, etc.<br />Full impact analysis, including test data<br />“Statement of quality” (SoQ) alongside requirements<br />Three levels of detail: Boolean, defect list, full test summary<br />Defect monitoring against requirements<br />Business criticality set by analyst for prioritization<br />Traverse into Quality Center if required<br />
  17. 17. Statement of quality attributes<br />
  18. 18. Roll-up results<br />
  19. 19. Roll-up results (continued)<br />
  20. 20. Detailed analysis<br />Analyst now has detailed information to help identify what needs to be fixed<br />
  21. 21. Synchronize SoQ attributes<br />
  22. 22. Facilities available to the integration administrator<br />Data-set definition<br />Defines how much information should be visible when seeing the same information in Rational DOORS and HP TestDirector for Quality Center<br />Attribute mapping<br />Configures how Rational DOORS information is seen in Quality Center<br />Configures how Quality Center information is seen in Rational DOORS<br />Client installation for remote administration<br />Individual named-user authentication to help improve security<br />
  23. 23. Synchronization controls<br />Configure synchronization<br />Automated<br />Manual<br />
  24. 24. So what?<br />
  25. 25. Potential analyst benefits<br />Better visibility of test plan can potentially lead to improved system quality<br />Review construction of the audit trail to help verify that requirements have been planned to be tested<br />Monitor test status against requirements to help identify business impact<br />Role-based integration within Rational DOORS <br />Traceability columns on requirements and test<br />Reporting facilities<br />Suspect links<br />
  26. 26. Potential QA/tester benefits<br />Work against a defined set of requirements <br />Help improve system quality while controlling an efficient test process<br />How much testing is enough? <br />More efficient test “autopsy”<br />Is a defect in the test, implementation or requirement?<br />Traverse audit trails back to original requirements analysis<br />Role-based integration<br />Combined reports from within Quality Center<br />Traceability alerts help avoid loss of requirements changes<br />
  27. 27. Potential manager benefits<br />Quality assurance statistics alongside requirements can help ensure that:<br />Business criticality can be understood and traced back to user need<br />Overall development process is prioritized commercially rather than technically<br />Statistics aggregated up through the requirements hierarchy<br />Faster identification of overall system quality<br />Easier to communicate quality assurance to the end customer<br />
  28. 28. Potential overall benefits<br />More cohesive organizations, smaller learning curves<br />Can see information from other disciplines without having to move outside a preferred working environment<br />Support for improved system quality<br />Providing a connection between the analysts and the testers can improve likelihood that clear acceptance objectives will be both defined and met<br />