BASIC DEFINITIONS Errors : An error is a mistake, misconception, or misunderstanding on the part of a software developer. In the category of developer.

Slides:



Advertisements
Similar presentations
1.Quality-“a characteristic or attribute of something.” As an attribute of an item, quality refers to measurable characteristics— things we are able to.
Advertisements

Testing and Quality Assurance
Software Quality Assurance Plan
More CMM Part Two : Details.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
PERTEMUAN - 2 SOFTWARE QUALITY. OBJECTIVES After completing this chapter, you will be able to: ■ Define software, software quality and software quality.
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Overview Lesson 10,11 - Software Quality Assurance
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is software? Software errors, faults and failures Classification.
DAIMIHenrik Bærbak Christensen1 Testing Terminology.
Objectives Understand the basic concepts and definitions relating to testing, like error, fault, failure, test case, test suite, test harness. Understand.
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
Software Process and Product Metrics
Planning and Tracking Software Quality Yordan Dimitrov Telerik Corporation
1 CSc Senior Project Software Testing. 2 Preface “The amount of required study of testing techniques is trivial – a few hours over the course of.
SOFTWARE QUALITY ASSURANCE Asst. Prof. Dr. Selim BAYRAKLI Maltepe University Faculty of Engineering SE 410.
Software Quality Assurance & Testing Mistake in coding is called error, Error found by tester is called defect, Defect accepted by development team then.
OHT 16.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The objectives of training and certification The training and certification.
Chapter 2 What is software quality ?. Outline What is software? Software errors, faults and failures Classification of the causes of software errors Software.
SOFTWARE QUALITY ASSURANCE PRACTICE IN JAPAN
Managing Software Quality
Objectives Understand the basic concepts and definitions relating to testing, like error, fault, failure, test case, test suite, test harness. Explore.
CPIS 357 Software Quality & Testing
Introduction Telerik Software Academy Software Quality Assurance.
Quality Control Project Management Unit Credit Value : 4 Essential
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
This chapter is extracted from Sommerville’s slides. Text book chapter
Software Metrics and Reliability. Definitions According to ANSI, “ Software Reliability is defined as the probability of failure – free software operation.
CPSC 873 John D. McGregor Session 9 Testing Vocabulary.
Chapter 8 Testing. Principles of Object-Oriented Testing Å Object-oriented systems are built out of two or more interrelated objects Å Determining the.
CPSC 871 John D. McGregor Module 8 Session 1 Testing.
TESTING FUNDAMENTALS BY K.KARTHIKEYAN.
1 Phase Testing. Janice Regan, For each group of units Overview of Implementation phase Create Class Skeletons Define Implementation Plan (+ determine.
1 Definition Quality costs Plan Team Characteristics Implementation documentation Reviews & Audit Software Quality Assurance.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
CS223: Software Engineering Lecture 25: Software Testing.
CPSC 372 John D. McGregor Module 8 Session 1 Testing.
Principles of Information Systems Eighth Edition
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Software Configuration Management
Software Quality Control and Quality Assurance: Introduction
Testing Tutorial 7.
John D. McGregor Session 9 Testing Vocabulary
Test Automation CS 4501 / 6501 Software Testing
SEVERITY & PRIORITY RELATIONSHIP
Chapter 8 – Software Testing
Verification & Validation
Quality Quality is “a characteristic or attribute of something.”
د. حنان الداقيز خريف /28/2016 Software Quality Assurance ضمان جودة البرمجيات ITSE421 5 – The components of the SQA.
John D. McGregor Session 9 Testing Vocabulary
Software engineering.
Definitions.
John D. McGregor Session 9 Testing Vocabulary
Engineering Processes
Verification and Validation Unit Testing
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
What is software quality?
Test Automation CS 4501 / 6501 Software Testing
Chapter 13 Quality Management
Chapter 25 Process and Project Metrics
Software Quality Assurance
Dynamic Program Analysis
What is software quality?
Chapter 32 Process and Project Metrics
© Oxford University Press All rights reserved.
Software Reviews.
Presentation transcript:

BASIC DEFINITIONS Errors : An error is a mistake, misconception, or misunderstanding on the part of a software developer. In the category of developer we include software engineers, programmers, analysts, and testers. For example, a developer may misunderstand a design notation, or a programmer might type a variable name incorrectly.

Error guessing has no rules for testing, it only uses the testers previous skills. In error guessing testers can think of situations where software will fail. For example: Division by zero Pressing submit button on form without filling any entries.

Faults (Defects/Bugs) : A fault (defect) is introduced into the software as the result of an error. It is an anomaly in the software that may cause it to behave incorrectly, and not according to its specification. Failures A failure is the inability of a software system or component to perform its required functions within specified performance requirements . ( Unexpected output)

Test case A test case in a practical sense is a test-related item which contains the following information: 1. A set of test inputs. These are data items received from an external source by the code under test. The external source can be hardware, software, or human. 2. Execution conditions. These are conditions required for running the test, for example, a certain state of a database, or a configuration of a hardware device. 3. Expected outputs. These are the specified results to be produced by the code under test.

Test A test is a group of related test cases, or a group of related test cases and test procedures. Test Oracle A test oracle is a document, or piece of software that allows testers to determine whether a test has been passed or failed.

A program, or a document that produces or specifies the expected outcome of a test, can serve as an oracle. Test Bed A test bed is an environment that contains all the hardware and software needed to test a software component or a software system. This includes the entire testing environment, for example, simulators, emulators, memory checkers, hardware probes, software tools, and all other items needed to support execution of the tests.

Software Quality 1. Quality relates to the degree to which a system, system component, or process meets specified requirements. 2. Quality relates to the degree to which a system, system component, or process meets customer or user needs, or expectations.

Quality metric A metric is a quantitative measure of the degree to which a system, system component, or process possesses a given attribute. There are product and process metrics. A very commonly used example of a software product metric is software size, usually measured in lines of code (LOC). Two examples of commonly used process metrics are costs and time required for a given task. Quality metrics are a special kind of metric.

A quality metric is a quantitative measurement of the degree to which an item possesses a given quality attribute. Some examples of quality attributes with brief explanations are the following: correctness—the degree to which the system performs its intended function reliability—the degree to which the software is expected to perform its required functions under stated conditions for a stated period of time usability—relates to the degree of effort needed to learn, operate, prepare input, and interpret output of the software integrity—relates to the system‘s ability to withstand both intentional and accidental attacks portability—relates to the ability of the software to be transferred from one environment to another maintainability—the effort needed to make changes in the software interoperability—the effort needed to link or couple one system to another.

Software Quality Assurance Group The software quality assurance (SQA) group in an organization has ties to quality issues. The group serves as the customers‘ representative and advocate. Their responsibility is to look after the customers‘ interests. The software quality assurance (SQA) group is a team of people with the necessary training and skills to ensure that all necessary actions are taken during the development process so that the resulting software conforms to established technical requirements.

Review A review is a group meeting whose purpose is to evaluate a software artifact or a set of software artifacts. The composition of a review group may consist of managers, clients, developers, testers and other personnel depending on the type of artifact under review.