Error and Defect Management in context of IFDK reference product.

Slides:



Advertisements
Similar presentations
QuEdge Testing Process Delivering Global Solutions.
Advertisements

Conquering Complex and Changing Systems Object-Oriented Software Engineering Chapter 12, Software Life Cycle.
Computer Science Department
System Integration Verification and Validation
Testing and Quality Assurance
Chapter 4 Quality Assurance in Context
FreeNest Brand Basic Material for testing course.
Rational Unified Process
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
Data Structures and Programming.  John Edgar2.
CSCI ClearQuest 1 Rational ClearQuest Michel Izygon - Jim Helm.
SQA Architecture Software Quality By: MSMZ.
Software Quality Assurance QA Engineering, Testing, Bug Tracking, Test Automation Software University Technical Trainers SoftUni Team.
What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”
1 CMPT 275 Software Engineering Software life cycle.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Cmpe 589 Spring Software Quality Metrics Product  product attributes –Size, complexity, design features, performance, quality level Process  Used.
Planning and Tracking Software Quality.  What Is Software Quality?  Causes of Software Defects  What is Quality Assurance?  Improving the Software.
FreeNest Brand Basic Material for testing course.
Software testing basic. Main contents  Why is testing necessary?  What is testing?  Test Design techniques  Test level  Test type  How to write.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
What is a life cycle model? Framework under which a software product is going to be developed. – Defines the phases that the product under development.
Change Management in context of IFDK reference product.
Identify steps for understanding and solving the
Requirement & Release Management in context of IFDK reference product.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
Sampleminded® Support Overview Last Updated: 1/22/
Martin Cryer Software Development. ‹#› Development Processes Traditional e.g. Waterfall Method Agile –Design Build (Quick to Market) –Combines Engineering,
Unit Testing and Continuous Integration in context of IFDK reference product.
Software Metrics and Reliability. Definitions According to ANSI, “ Software Reliability is defined as the probability of failure – free software operation.
Error and Defect Management in context of IFDK reference product.
Proposed H.323 Forum Testing Program Support Sanjay Mishra – October 24, 2002.
Testing as a Driver for Development Change Wall Street Systems Graham Thomas.
Test Design and Management in context of IFDK reference product.
July, 2008 Impati – Software Test Solutions. July, Contents Testing Service Overview and Approach Test Services and Industries Key Services Offering.
Approaches to ---Testing Software Some of us “hope” that our software works as opposed to “ensuring” that our software works? Why? Just foolish Lazy Believe.
Software Engineering 2003 Jyrki Nummenmaa 1 SOFTWARE ENGINEERING - SOFTWARE LIFECYCLE MODELS These slides contain a few different software lifecycle.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Principles of Software Engineering: Why Study Software Engineering? COSI 120b, Spring 2005.
CPSC 871 John D. McGregor Module 6 Session 2 Validation and Verification.
TESTING FUNDAMENTALS BY K.KARTHIKEYAN.
Software Testing Process
EMI INFSO-RI Software Metric Definitions, Reports and Analysis in EMI Authors: Eamonn Kenny (TCD), Gianni Pucciani (CERN) Date: Tuesday 12 th April.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Introduction to Bugzilla. May 12, 2011 What is Bugzilla? Bugzilla is a defect- or issue-tracking system Allows individual or groups of developers effectively.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
Risk-Based Management and Testing. 2 This is risk-based testing(J. Bach) Make prioritized list of risks Perform testing that explores each risk As risks.
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Chapter3:Software Processes
Maintenance Issues in Software Engineering
SOFTWARE ENGINEERING - SOFTWARE LIFECYCLE MODELS
A Case Study: Automated Continuous Software Engineering Cycle (ACSEC)
Approaches to ---Testing Software
BA Continuum India Pvt Ltd
Chapter 18 Maintaining Information Systems
Topic for Presentaion-2
Chapter 8 – Software Testing
Software Quality Assurance
Design and Implementation
Issue Tracking Systems
Lecture 09:Software Testing
An Overview of Software Processes
Progression of Test Categories
Dynamic Process for Source Control
Welcome to Corporate Training -1
Chapter 7 –Implementation Issues
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
SOFTWARE ENGINEERING LECTURE 2
SOFTWARE DEVELOPMENT LIFE CYCLE
Presentation transcript:

Error and Defect Management in context of IFDK reference product

About this course material -This material if for general training for Error and Defect Management -Material is more supportive in class room -Material will be updated during courses -FreeNest Portable Project Platform is used to demonstrate things only in practice. This is not limiting usage for material for other training environments (I hope ) About material

Definitions Failure - Fault, Defect, Bug - Incident, Failure, Error Example forum thread: ISTQB syllabus Yläotsikko

Customer/Business Requirements Sub System Requirements Component Requirements Component / Unit Testing Integration Testing System Testing Acceptance Testing System Requirements Architecture& Design& Implementatio n Product VALIDATION VERIFICATION Error Database Error Database MAINTENANCE Error Database & Management covers whole product life cycle PRODUCT END timelinetimeline

● TEST CASE ID XXXXX ● Step1 ● Step2 ● Step3. ● Step4. ● TEST CASE ID XXXXX ● Step1 ● Step2 ● Step3. ● Step4. INCIDENTS Bug/Defect Report Bug/Defect Report Error Database System Under Test EXECUTE TEST ! Test Engineer Writes report and provides evidences What means error/defect reporting? Yläotsikko Collects INCIDENTS Can lead to

Example Sources for error report CRM Field Testing Testing Process Customer Feedback / Customer Feedback / Error Report Change Request? Change Request? N x Incidents Yläotsikko

● Defect/Burg/Error ID ● Reporter ● Time ● Founded where ● Which way? ● Test Case ● Test Setup/Configuration ● Describe scenario? ● Attachements? Picture/Log/etc.. ● Defect/Burg/Error ID ● Reporter ● Time ● Founded where ● Which way? ● Test Case ● Test Setup/Configuration ● Describe scenario? ● Attachements? Picture/Log/etc.. Error Database Error Database Id1 Id2 Id1 Id3 Id1 Error/Bug/Defect Report

Id1 Id2 Id4 Id3 Nature of bug? Location? Priority? Severity? Where is the bug is found?Which one should fixed first? How fatal is the bug? Id2 ID N Target? When the bug should be fixed and verified ?

Testing Levels and Error Management UNIT TESTING – Developer's area Implementation Test Framework Error Database Error Database

Integration Testing Implementa tion Test Framework Error Database Error Database Test Plan Test Plan Implementa tion Test Framework Component 2

System & Acceptace Testing Implem entati on Test Framewo rk Error Database Error Database Te st Pl an Te st Pl an Implem entati on Test Framewo rk Component 2 Test Plan Test Plan IFDK HARDWARE DESIGN IFDK HARDWARE DESIGN IFDK HARDWARE PROTOTYPE VERIFICATED IFDK HARDWARE PROTOTYPE VERIFICATED

Error/defect life cycle Yläotsikko

Error fixing and release Week 0 Week 26 Week 52 REL 0.1 REL 0.2 REL 0.5 REL 1.0 Defect Found Defects Found Future ?

Hands On: Bugzilla Error Database ion-list/ ion-list/ What is Bugzilla? Bugzilla is a "Defect Tracking System" or "Bug-Tracking System". Defect Tracking Systems allow individual or groups of developers to keep track of outstanding bugs in their product effectively. Most commercial defect-tracking software vendors charge enormous licensing fees. Despite being "free", Bugzilla has many features its expensive counterparts lack. Consequently, Bugzilla has quickly become a favorite of thousands of organizations across the globe. What is Bugzilla? Bugzilla is a "Defect Tracking System" or "Bug-Tracking System". Defect Tracking Systems allow individual or groups of developers to keep track of outstanding bugs in their product effectively. Most commercial defect-tracking software vendors charge enormous licensing fees. Despite being "free", Bugzilla has many features its expensive counterparts lack. Consequently, Bugzilla has quickly become a favorite of thousands of organizations across the globe.

Reporting, Metrics and daily usage

Bugzilla Yläotsikko

Other Defect Database Solutions JIRA – Commercial Requisite Pro – Commercial Rational Synergy - Commercial Mantis – Open Source

Testlink and Bugzilla Test Management Database Test Management Database Feature Implementation Feature Implementation TestCase Bug Report Error Database Error Database PASS FAIL TestCase Test Plan/Suite SourceCode Version Control SourceCode Version Control BUGZILLA TESTLINK VC + Implementation

Feature or Bug? That's a question!

Yläotsikko

Change Management Sometimes founded defect can lead to change Bug? Change Request? Not Clear Requirements Not Clear Requirements Feature ? Yläotsikko

Traditional SW Project vs Open Source Project Open Source – Crowd Sourcing SW Relase tested without coordination by group of volunteers Release tested by customer Field Testing Test Group Yläotsikko