logging in or signing up CHCF QA aSGuest43126 Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINT lite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 14 Category: Science & Tech.. License: All Rights Reserved Like it (0) Dislike it (0) Added: April 20, 2010 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript CHCF Quality Assurance : CHCF Quality Assurance “To measure is to know” Lord Kelvin IEEE Standard 1061-1992 : IEEE Standard 1061-1992 This framework is a hierarchy of 4 levels. Level 1 Quality Requirement---Quality of a Software Product The product will provide the necessary functionality required to accomplish some task description Level 2 Quality Factor: Functionality An attribute that bears on the existence of certain properties and functions that satisfy stated or implied needs of users. Level 3: Quality Subfactors: Completeness: The degree to which software possesses necessary and sufficient functions to satisfy user needs. Correctness: The degree to which all software functions are specified. Availability (from the Reliability Quality Subfactor): The degree to which software remains operable in the presence of system failures. Security: The degree to which software can detect and prevent information leak, loss, illegal use and resource destruction. Level 4: Direct Metrics Completeness: Test Coverage Correctness: Defect Density Availability: Percentage of time the software is available to users Security: Data Integrity It is the Level 4 direct metrics which quantify the software under test. IEEE Standard 1061-1099 diagram : IEEE Standard 1061-1099 diagram Direct Metrics – Completeness : Direct Metrics – Completeness Completeness Completeness is defined as test coverage; e.g. test cases with traceability to requirements. Is there adequate coverage (which traverse the AUT (application under test)) Coverage requires at a minimum: User Interface Data Layer Functionality Functional Integration Direct Metric - Correctness : Direct Metric - Correctness Correctness Correctness is defined as Defect Density, derived from the coverage execution. Correctness requires (as close to) 100% coverage to ensure the reported metric is represented accurately. EX: IF a system has 25% coverage and the derived defect density is 0, does this represent a quality system? No, 75 % of the system remains untested. DIRECT METRIC - Availablity : DIRECT METRIC - Availablity Reliability (Availability) Reliability requires that: The application must remain operating correctly within project guidelines. The application can be restored to operational state within project guidelines, if it fails. DIRECT METRIC - Security : DIRECT METRIC - Security Security/Integrity Integrity requires that: The system is secure. The system is safe. CHCF Applications Under test : CHCF Applications Under test CAMS --- over 350 test cases TPA – over 250 test cases FRU – over 100 test cases Test Suite configuration : Test Suite configuration EXCEL format Multiple worksheets Extensible Scalable Familiarity EXCEL Columns ID Req. Use Case number Input Steps Expected Output Actual Output Pass/Fail Layer III SQL Instruction worksheet Snap-shot : Instruction worksheet Snap-shot Workbook worksheets This workbook is comprised of (10) named work-sheets. They are: 1. Version Control: This worksheet identifies the changes made 2. Instructions: This worksheet is used to describe various QA elements and the manual approach to test case execution 3. Test Cycle Reporting: This worksheet captures and reports the pass/fail results of an executed Test Cyle. 4. Test Data: This worksheet is used to define the Test Data to be used in the CAMS build under test during Test Cycle execution. 5. Smoke Test: This worksheet identifies and executes test cases against each deployed build to QA for Acceptance 6. User Interface Verification: This worksheet identifies and performs V&V against the CAMS Internet User Interface 7. Data Layer verification: This worksheet identifies and performs V&V against the CAMS User Interface data 8. Functional Integration: This worksheet identifies and executes test cases to ensure application integration. 9. Functionality: This worksheet identifies and executes functional test cases 10. Scenario Testing: This worksheet provides functional tests by Use Case. User Interface (Ui) Worksheet snap-shot : User Interface (Ui) Worksheet snap-shot Functianl Test Case Snap-SHOT : Functianl Test Case Snap-SHOT Metric Reporting Worksheet Snap-shot : Metric Reporting Worksheet Snap-shot Whats Next : Whats Next Predictive Analysis Automation (Regression) Extend existing Test Suites Project Management Tracking System : Project Management Tracking System JIRA - Web enabled Define, create and manage projects 2 dimensional view – Status, and Resolution Status Open, In Progress, Resolved, Fixed Fixed, Wont Fix, Duplicate, Incomplete Cannot Reproduce, Postponed Pending Investigation Resolution Fixed Wont Fix Duplicate Incomplete Cannot Reporduce Postponed Pending Inve Closing : Closing When you measure what you are speaking about, and express it in numbers, you know something about it; but when you cannot measure it, when you cannot express it in numbers, your knowledge is of a meager and unsatisfactory kind; it may be the beginning of knowledge, but you have scarcely in your thoughts advanced to the stage of science. You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.
CHCF QA aSGuest43126 Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINT lite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 14 Category: Science & Tech.. License: All Rights Reserved Like it (0) Dislike it (0) Added: April 20, 2010 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript CHCF Quality Assurance : CHCF Quality Assurance “To measure is to know” Lord Kelvin IEEE Standard 1061-1992 : IEEE Standard 1061-1992 This framework is a hierarchy of 4 levels. Level 1 Quality Requirement---Quality of a Software Product The product will provide the necessary functionality required to accomplish some task description Level 2 Quality Factor: Functionality An attribute that bears on the existence of certain properties and functions that satisfy stated or implied needs of users. Level 3: Quality Subfactors: Completeness: The degree to which software possesses necessary and sufficient functions to satisfy user needs. Correctness: The degree to which all software functions are specified. Availability (from the Reliability Quality Subfactor): The degree to which software remains operable in the presence of system failures. Security: The degree to which software can detect and prevent information leak, loss, illegal use and resource destruction. Level 4: Direct Metrics Completeness: Test Coverage Correctness: Defect Density Availability: Percentage of time the software is available to users Security: Data Integrity It is the Level 4 direct metrics which quantify the software under test. IEEE Standard 1061-1099 diagram : IEEE Standard 1061-1099 diagram Direct Metrics – Completeness : Direct Metrics – Completeness Completeness Completeness is defined as test coverage; e.g. test cases with traceability to requirements. Is there adequate coverage (which traverse the AUT (application under test)) Coverage requires at a minimum: User Interface Data Layer Functionality Functional Integration Direct Metric - Correctness : Direct Metric - Correctness Correctness Correctness is defined as Defect Density, derived from the coverage execution. Correctness requires (as close to) 100% coverage to ensure the reported metric is represented accurately. EX: IF a system has 25% coverage and the derived defect density is 0, does this represent a quality system? No, 75 % of the system remains untested. DIRECT METRIC - Availablity : DIRECT METRIC - Availablity Reliability (Availability) Reliability requires that: The application must remain operating correctly within project guidelines. The application can be restored to operational state within project guidelines, if it fails. DIRECT METRIC - Security : DIRECT METRIC - Security Security/Integrity Integrity requires that: The system is secure. The system is safe. CHCF Applications Under test : CHCF Applications Under test CAMS --- over 350 test cases TPA – over 250 test cases FRU – over 100 test cases Test Suite configuration : Test Suite configuration EXCEL format Multiple worksheets Extensible Scalable Familiarity EXCEL Columns ID Req. Use Case number Input Steps Expected Output Actual Output Pass/Fail Layer III SQL Instruction worksheet Snap-shot : Instruction worksheet Snap-shot Workbook worksheets This workbook is comprised of (10) named work-sheets. They are: 1. Version Control: This worksheet identifies the changes made 2. Instructions: This worksheet is used to describe various QA elements and the manual approach to test case execution 3. Test Cycle Reporting: This worksheet captures and reports the pass/fail results of an executed Test Cyle. 4. Test Data: This worksheet is used to define the Test Data to be used in the CAMS build under test during Test Cycle execution. 5. Smoke Test: This worksheet identifies and executes test cases against each deployed build to QA for Acceptance 6. User Interface Verification: This worksheet identifies and performs V&V against the CAMS Internet User Interface 7. Data Layer verification: This worksheet identifies and performs V&V against the CAMS User Interface data 8. Functional Integration: This worksheet identifies and executes test cases to ensure application integration. 9. Functionality: This worksheet identifies and executes functional test cases 10. Scenario Testing: This worksheet provides functional tests by Use Case. User Interface (Ui) Worksheet snap-shot : User Interface (Ui) Worksheet snap-shot Functianl Test Case Snap-SHOT : Functianl Test Case Snap-SHOT Metric Reporting Worksheet Snap-shot : Metric Reporting Worksheet Snap-shot Whats Next : Whats Next Predictive Analysis Automation (Regression) Extend existing Test Suites Project Management Tracking System : Project Management Tracking System JIRA - Web enabled Define, create and manage projects 2 dimensional view – Status, and Resolution Status Open, In Progress, Resolved, Fixed Fixed, Wont Fix, Duplicate, Incomplete Cannot Reproduce, Postponed Pending Investigation Resolution Fixed Wont Fix Duplicate Incomplete Cannot Reporduce Postponed Pending Inve Closing : Closing When you measure what you are speaking about, and express it in numbers, you know something about it; but when you cannot measure it, when you cannot express it in numbers, your knowledge is of a meager and unsatisfactory kind; it may be the beginning of knowledge, but you have scarcely in your thoughts advanced to the stage of science.