Doors Quality Center Integration

  • 4,618 views
Uploaded on

 

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
4,618
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
290
Comments
0
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Quality Assurance Begins with Requirements An integration between Telelogic DOORS and HP Quality Center
  • 2. Integrating the project team
  • 3. Requirements Driven Testing Tests based on requirements ensure deliverables meet customer expectations Quality is conformance to requirements Process Automation and Increased Focus The test team is working against the right set of requirements Requirements Management Test Status Test Design Test Execution Test Planning DOORS Quality Center Test Status Test Planning Test Design Test Execution Requirements Management
  • 4. Benefits of Requirements Driven Testing
    • Providing a requirements based integration between DOORS and Quality Center enables:
      • The Requirements Analyst to focus on delivering testable requirements with fully defined qualification criteria
      • The QA/Tester to focus on developing tests against a known set of requirements
      • Release Management can be performed based on requirement quality measures rather than on statistics of test pass/failure
  • 5. DOORS – Quality Center Integration Overview
    • Fully role based, bringing functionality and data to a users preferred tool
      • Both DOORS users and also Quality Center users
  • 6. Role: Analyst
    • The Analyst is a DOORS user principally interested in Requirements Management
    • Specifies 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
    Tests ? The Analyst
  • 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
    • Test failure investigation
    Requirements ? The QA/Tester
  • 8. Role: Manager (System Review Board)
    • The SRB
      • Analyze impact of defects (priority, severity)
      • Have the final say regarding release decision
    • Test managers
      • influence the SRB in the confidence that they have an efficient test process working against the requirements
    • Development managers
      • influence the SRB based on the latest test information against their development efforts
    • Analyst manager
      • influence the SRB with the full business impact of making a release based on requirements 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 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 Quality Center
    • See DOORS data inside of requirements tab in Quality Center
      • Test against requirements rather than simply against what is built
  • 12. Facilities within Quality Center
    • Map DOORS data into other parts of Quality Center such as the test design
    • Modify DOORS data to aid communication
      • Constrained to user defined attributes
  • 13. What happens next?
    • Qualification criteria can be reviewed and comments entered inside of Quality Center
    • Existing functionality within Quality Center
      • Automatic generation of template test information from the qualification criteria
      • Control over requirement changes through traceability alerts
        • Similar to DOORS suspect links
    • Test execution raises defects that are indirectly associated to requirements
  • 14.
    • Manually instigate transfer of information between DOORS and Quality Center
    Facilities within DOORS
  • 15. Facilities within DOORS
    • Associations created within Quality Center seen as DOORS links
      • Use standard DOORS facilities to review tests
      • Suspect links so that requirements changes are not missed
  • 16. Facilities within DOORS
    • Quality Center information seen as DOORS modules
      • Requirements, tests, defects, etc…
      • full impact analysis including test data
    • “ Statement of Quality” 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
  • 20. Detailed analysis
    • Analyst now has detailed information to 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 DOORS and Test Director
      • Attribute mapping:
        • Configures how DOORS information is seen in Quality Center
        • Configures how Quality Center information is seen in DOORS
    • Client installation for remote administration
    • Individual named user authentication for improved security
  • 23. Synchronization controls
    • Configure synchronization
      • Automated
      • or Manual
  • 24. So what?
  • 25. Analyst Benefits
    • Better visibility of test plan increases systems quality
      • Review construction of the audit trail to ensure that requirements have been planned to be tested
      • Monitor test status against requirements to identify business impact
    • Fully role based integration within DOORS
      • Traceability columns on requirements and test
      • Reporting facilities
      • Suspect Links
  • 26. QA/Testers benefits
    • Work against a defined set of requirements
      • Maximize system quality while controlling an efficient test process
      • How much testing is enough?
    • Efficient test autopsy
      • is a defect in the test, implementation or requirement?
      • Traverse audit trails back to original requirements analysis
    • Fully role based integration
      • Combined reports from within Quality Center
      • Traceability alerts so requirements changes are never lost
  • 27. Manager Benefits
    • Quality Assurance statistics alongside requirements ensure that:
      • Full business criticality understood and traced back to user need
      • Overall development process prioritized commercially rather than technically
    • Statistics aggregated up through the requirements hierarchy
      • Fast identification of overall systems quality
      • Easier to communicate quality assurance to the end customer
  • 28. Overall benefits
    • More cohesive organizations with minimal learning curves
      • See information from other disciplines without the need to move outside of a preferred working environment
    • Increased systems quality
      • Providing a connection between the Analysts and the Testers ensures that clear acceptance objectives are both defined and met.
  • 29. © Copyright IBM Corporation 2008. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.
    • Learn more at:
    • IBM Rational software
    • IBM Rational Software Delivery Platform
    • Process and portfolio management
    • Change and release management
    • Quality management
    • Architecture management
    • Rational trial downloads
    • Leading Innovation Web site
    • developerWorks Rational
    • IBM Rational TV
    • IBM Business Partners
    • IBM Rational Case Studies