Qa Lifecycle Colaci.Com
- 1. 7 Jun 2009 Requirement Defect Integrated & Streamlined IP sharing Leverage existing IP Traceability Pass Plan Function / Process Metrics Intellectual Property Management Lab Test Management – with a Test Repository Test Repository Benefits Timely Detailed Reports SME define application requirements and testing objectives Test managers and project leads design test plans and develop test cases Requirements without Tests. Tests without Requirements. Exit Criteria Gap Analysis Define Phase
- 2. 7 Jun 2009 Requirement Defect IP sharing Leverage existing IP Pass Plan Function / Process Metrics Intellectual Property Management Test Management – with a Test Repository Test Repository Benefits Timely Detailed Reports Lab Integrated & Streamlined QA run man & auto tests, verify results, pass or enter defects Ready to lab test. Developers review and fix defects logged into the database SME define application requirements via Change Requests Traceability Exit Criteria QA develop test plans and analyse for strategies Gap Analysis See, Measure, Manage
- 3. 7 Jun 2009 Requirement Defect IP sharing Traceability Gap Analysis Pass Plan Function / Process Metrics Intellectual Property Management Test Management – with a Test Repository Test Repository Benefits Timely Detailed Reports Exit Criteria Lab Integrated & Streamlined QA testers run manual and automated tests, report execution results, and enter defects Production Support given Admin access & Ready to lab test. Production Support Phase Developers review and fix defects logged into the database Leverage existing IP
- 4. And must be: Unique in scope. Is it the only requirement defining this objective? Precise in wording and not vague at all. Bounded by concrete expectations by being quantifiable Irrefutably a testable statement to build one or many tests Repeatable for other or future projects Good requirements comes from thorough knowledge of customer expectations and business processes: 7 Jun 2009 What makes good requirements? Plan Requirements Lab Defect Pass
- 5. Good requirements comes from thorough knowledge of customer expectations and business processes and will: Aid development & testing Manage moving targets Measure success Give clear expectations Save time & money Be repeatable 7 Jun 2009 Why good requirements? Plan Requirements Lab Defect Pass
- 6. 7 Jun 2009 Business Actions Requirements Define Requirements Structure Agree on Priority Requirements for Regression Ensure meets “good” requirement criteria Start documenting & ready to load All other processes are the same except TD is utilised Plan Requirements Lab Defect Pass
- 7. 7 Jun 2009 Before & After Savings Takes too long Today Building Baseline Approx. 4% savings can be achieved by improving traceability, scheduling, reporting & defect management 47% Leveraging previous requirements & testing analysis driving SDLC costs down Test Repository Savings 47% Savings Must Invest Time & Resource to Build Baseline
- 8. 7 Jun 2009 Establish UAT Test Standards, Process and Standards Jan Jun Test Repository - Timeline Gen 2 - Requirements Management & expand SSM to support business UAT 47% savings possible streamlining test processes & leveraging previous testing Big Savings - must invest time & resources to build baseline Establish Structured Test Director Process and Standards Participants Impact analyse implementation requirements Establish Test Director Hardware & Support Gen 1 – Shared Test Management service Establish TD Repository Establish platform to leverage IP Test Director Operational Mar
Editor's Notes
- #2: Traceability. BA Requirements, TM&C dev plan, gaps,