What's the Big Deal About CQCs? By: Rick Hess, Pat Theeke 1.

Slides:



Advertisements
Similar presentations
Test Yaodong Bi.
Advertisements

Introducing Formal Methods, Module 1, Version 1.1, Oct., Formal Specification and Analytical Verification L 5.
Testing and Quality Assurance
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
1 Test Cases CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 13, 2007.
Software Testing. Overview Definition of Software Testing Problems with Testing Benefits of Testing Effective Methods for Testing.
1 Samples The following slides are provided as samples and references for the Quarterly Reviews Additional slides will be added.
1 Software Testing and Quality Assurance Lecture 31 – Testing Systems.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
1 Advanced Material The following slides contain advanced material and are optional.
School of Computer ScienceG53FSP Formal Specification1 Dr. Rong Qu Introduction to Formal Specification
Introduction to Software Testing
1CMSC 345, Version 4/04 Verification and Validation Reference: Software Engineering, Ian Sommerville, 6th edition, Chapter 19.
Test Design Techniques
Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
Verification and Validation Yonsei University 2 nd Semester, 2014 Sanghyun Park.
Product Quality, Testing, Reviews and Standards
Software Quality Assurance Lecture #8 By: Faraz Ahmed.
Balancing Practices: Inspections, Testing, and Others JAXA scenario (formal method) Masa Katahira Japanese Space Agency.
Best Practices By Gabriel Rodriguez
Digital Alchemy | 5750 Stratum Drive Fort Worth, Texas | Phone: Fax: | Rate Code Manager Tutorial.
Testing – A Methodology of Science and Art. Agenda To show, A global Test Process which work Like a solution Black Box for an Software Implementation.
Introduction Telerik Software Academy Software Quality Assurance.
INTERMEDIATE PROGRAMMING LESSON By: Droids Robotics My Blocks Overview Step-by-Step Visual Guide to Creating a My Block with Inputs with Outputs.
FireRMS NEMSIS (Part 2) Presented by Laura Small FireRMS Quality Assurance.
Procedures for managing workflow components Workflow components: A workflow can usually be described using formal or informal flow diagramming techniques,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Software Verification, Validation and Testing.
1 / x CMMI Measurement & Analysis Pieter Cailliau Stijn De Vos Measurement & Analysis.
1 Introduction to Software Testing. Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Chapter 1 2.
(1) A beginners guide to testing Philip Johnson Collaborative Software Development Laboratory Information and Computer Sciences University of Hawaii Honolulu.
(SRS) SOFTWARE REQUIREMENT SPECIFICATION(SRS) 1. Topics to be discussed.. What is an SRS? Purpose of an SRS Who reads the SRS? Who writes the SRS? Characteristics.
程建群 博士 (Dr. Jason Cheng) 年 03 月 Software Engineering Part 08.
Using Symbolic PathFinder at NASA Corina Pãsãreanu Carnegie Mellon/NASA Ames.
1 Software Testing Strategies: Approaches, Issues, Testing Tools.
Software Testing Mehwish Shafiq. Testing Testing is carried out to validate and verify the piece developed in order to give user a confidence to use reliable.
Winter 2007SEG2101 Chapter 121 Chapter 12 Verification and Validation.
1 Phase Testing. Janice Regan, For each group of units Overview of Implementation phase Create Class Skeletons Define Implementation Plan (+ determine.
T EST T OOLS U NIT VI This unit contains the overview of the test tools. Also prerequisites for applying these tools, tools selection and implementation.
Reducing a Set Covering Matrix. S I T E S Cost Areas
Manual Testing Concepts Instructor: Surender. Agenda  Content: 1. Testing Overview I. What is testing II. Who does testing III. When to Start Testing.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Tool Support for Testing Classify different types of test tools according to their purpose Explain the benefits of using test tools.
Software Testing and Quality Assurance Practical Considerations (1) 1.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
Software Testing Strategies for building test group
Module: Software Engineering of Web Applications
How To Apply Quality Management
Software Configuration Management (SCM)
Domain Testing Functional testing which tests the application by giving inputs and evaluating its appropriate outputs. system does not accept invalid and.
BA Continuum India Pvt Ltd
Verification and Validation
Effective Test Design Using Covering Arrays
Software engineering – 1
Verification and Validation
CAE-SCRUB for Incorporating Static Analysis into Peer Reviews
9/18/2018 Department of Software Engineering and IT Engineering
Verification and Validation
INTERMEDIATE PROGRAMMING Lesson
Applied Software Implementation & Testing
Introduction to Software Testing
Software Quality Assurance
Requirements Engineering Processes
Dynamic Program Analysis
OWASP Application Security Verification Standard
Applying the ESS EARF in a VIP project: The ESS.VIP Validation example
Overview of Workflows: Why Use Them?
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Software Testing Strategies
OWASP Application Security Verification Standard
Presentation transcript:

What's the Big Deal About CQCs? By: Rick Hess, Pat Theeke 1

Code Quality Characteristics (CQCs, or Checks) What does your project care about looking for? Example source: Goddard Open Learning Design (GOLD) Rules std-1000/gsfc-std-1000.html std-1000/gsfc-std-1000.html Used as Inputs to the Static Code Analysis Method 2

Overview of the Method Created to work with the Evidence-based Assurance effort. Inputs are CQCs, and a list of the tools that are applicable (can handle the given code language(s), limitations of the tools have been considered). Within the method, determine which tool, or combination of tools, provide the most coverage for the CQCs you care about. Output from the method is the analysis results from the tools selected. 3

Determining which tools need to be used. Determine what you want to analyze, before you run your tools – Regarding CQCs, what does the project want to look for? – Which tools can I use to provide coverage among all my CQCs? 4

Verify Software Code Quality using the Static Code Analysis Method – Next Steps – Add a description about a using formal Capability Matrix based upon what the tools can do/say they can do to assist in picking the specific tool. – Add on to the current method to include the following: For the CQCs that cannot be covered by Static Code Analysis, the project then needs to determine whether performing other activities will fill in the ‘gap’, and is it worth the cost? (Manual Analysis, for example) 5

Proposed CD Effort Create a Capability Matrix to show which CQCs are covered and NOT covered by specific tools. – Tools usually broadcast most of what they CAN do. You never hear about the functionality that isn’t available or was removed. – Create a set of validation programs, or scripts assure that we understand the capabilities and limitations of our tools Verify that new tools and new version of existing tools have not limited or removed existing capabilities Help to identify when additional/different tools and/or Methods may be required, and when existing tools no longer meet our needs 6

Questions? 7

Backup Slides 8

Another possible example of CQCs: SWAT Code Defect Categories 9