Process Improvement. Improving the Test Process In the Software V&V course, Prof. Uwe asked the question: How to improve the Testing Process?

Slides:



Advertisements
Similar presentations
Importance of Questioning and Feedback Technique in developing 3 Cs
Advertisements

Formal Process of QA and quality related certifications Formal Process of QA and quality related certifications MIM 3 rd year – Sem V Abhishek Mishra –
By Veronika Movagharianpour and Adam Brakel. Software Developers face challenges:  Producing high-quality software  with low-defect levels  while doing.
Identifying enablers & disablers to change
Inspection (c) 2007 Mauro Pezzè & Michal Young Ch 18, slide 1 Photo credit jurvetson on Flickr.com; creative commons attribution license.
Testing Without Executing the Code Pavlina Koleva Junior QA Engineer WinCore Telerik QA Academy Telerik QA Academy.
Stepan Potiyenko ISS Sr.SW Developer.
Effective Project Management: Traditional, Agile, Extreme
SE 555 Software Requirements & Specification Requirements Validation.
Teaching Methods Chapters 7 and 8 Instructors and Their Jobs and additional resources.
(c) 2007 Mauro Pezzè & Michal Young Ch 3, slide 1 Basic Principles.
Verification and Validation
Other Planning Processes: Final Planning Touches
Security Assessments FITSP-M Module 5. Security control assessments are not about checklists, simple pass-fail results, or generating paperwork to pass.
Safety Management Strategies for Extended Care Facilities.
OHT 4.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Prof. Mohamed Batouche Quality Control.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Name: Abdullah Mohammed Alhatmi ID:86497 Course: Quality &Assurance Name: Abdullah Mohammed Alhatmi ID:86497 Course: Quality &Assurance Start.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management 1.
Strategies for IT Adoption in the Building Industry © 2002 Prof. C.M. Eastman & Dr. R. Sacks Modeling business, engineering and management processes.
*Graduate School of Engineering Science, Osaka University
Security Assessments FITSP-A Module 5
Applying the Inspection Process. What Software Artifacts Are Candidates for Inspection? Software Requirements Software Designs Code Test Plans.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 10: Testing and Inspecting to Ensure High Quality Part 4:
Software Quality Assurance Activities
RUP Implementation and Testing
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Software Inspections. Defect Removal Efficiency The number of defects found prior to releasing a product divided by The number of defects found prior.
© Mahindra Satyam 2009 Defect Management and Prevention QMS Training.
S Q A.
Problem Solving and Algorithm Design. 2 Problem Solving Problem solving The act of finding a solution to a perplexing, distressing, vexing, or unsettled.
PBL in Team Applied to Software Engineering Education Liubo Ouyang Software School, Hunan University CEIS-SIOE, January 2006, Harbin.
Requirements Verification & Validation Requirements Engineering & Project Management.
Software Engineering Saeed Akhtar The University of Lahore Lecture 7 Originally shared for: mashhoood.webs.com.
Formal Technical Reviews Matt Graham 18 November 2004 EECS 814 University of Kansas.
1 Introduction to Software Engineering Lecture 1.
INFO 636 Software Engineering Process I Prof. Glenn Booker Week 9 – Quality Management 1INFO636 Week 9.
Institut Experimentelles Software Engineering Fraunhofe r IESE Sauerwiesen 6 D Kaiserslautern Germany The Architecture-centric Inspection Approach.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Chapter 19 Verification and Validation.
Requirements Engineering Southern Methodist University CSE 7316 – Chapter 3.
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
Reviews and Inspections. Types of Evaluations Formal Design Reviews conducted by senior personnel or outside experts uncover potential problems Inspections.
Chapter 12: Software Inspection Omar Meqdadi SE 3860 Lecture 12 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Code Reviews James Walden Northern Kentucky University.
What does it all mean?. Communication Skills  Communication is the transfer of a message from one person to another. Maybe spoken, written, non-verbal.
Using Open Source Projects in Higher Education: A Two-Way Certification Framework Pantelis M. Papadopoulos, United Nations University Ioannis G. Stamelos,
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Inspections : A Flexible Method to Increase Software Quality By Sylvie Trudel CRIM CUSEC, Concordia University March 2002.
Requirement Engineering
1 Software Testing and Quality Assurance Lecture 17 - Test Analysis & Design Models (Chapter 4, A Practical Guide to Testing Object-Oriented Software)
Mahindra Satyam Confidential Quality Management System Software Defect Prevention.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Software inspections l Involve people examining the source representation with.
Further Investigations into the Development and Evaluation of Reading Techniques for Object-Oriented Code Inspection Alastair Dunsmore, Marc Roper and.
More SQA Reviews and Inspections. Types of Evaluations  Verification Unit Test, Integration Test, Usability Test, etc  Formal Reviews  aka "formal.
Verification vs. Validation Verification: "Are we building the product right?" The software should conform to its specification.The software should conform.
1 Requirements Analysis Lecture # Recap of Requirements Elicitation - 1 Requirements elicitation deals with discovering requirements for a software.
Software Design Process. What is software? mid-1970s executable binary code ‘source code’ and the resulting binary code 1990s development of the Internet.
EDU 675 Week 3 DQ 2 Assessment Strategies Check this A+ tutorial guideline at ASH/EDU-675-Week-3-DQ-2-Assessment-
Software Configuration Management (SCM)
How to Implement an IG Manufacturing Quality Procedure System
Systems Analysis and Design
Conducting Self-Inspections
161 Senior Cadet Development Weekend
Problem Solving and Algorithm Design
Applied Software Project Management
Measure Phase Wrap Up and Action Items
Testing and Inspection Present and Future
Testing, Inspection, Walkthrough
Unit IV – Chapter 2 V-Test Model.
Presentation transcript:

Process Improvement

Improving the Test Process In the Software V&V course, Prof. Uwe asked the question: How to improve the Testing Process?

Improving the Test Process (2) Some answers: 1. Develop a test strategy 2. Use Guidance such as:  checklists  guidelines  templates 3. Improve communication >> How to improve communication? 4. Learn from past experience >> How to consistently learn from the past?

How to Improve Communication? Review:  Request a review of the testing plan  Don't wait for a request Benefits of Review  Improves understanding between members  Team members learn from each other (knowledge transfer)  Improve motivation & sense of participation  Chance to involve senior developers who don't have time to involve directly in testing

What is a Review?

How to Conduct a Review

Inspection  Systematic approach to examining a program (work product) in detail  Goal is to assess the quality of the software product not the quality of the process ensure program is correct verify coding standard

Handling complexity  Use divide and conquer  Examine small parts

Three techniques  checklist Problems with Checklists: questions too general instruction missing detection biased towards previous defects

Three techniques  Use cases check that each object is capable of responding correctly to all scenarios forces the inspector to consider the context in which an object is used interaction diagram is useful create scenarios...

Three Techniques  Abstraction driven start with least dependent class create a natural language abstraction for each part (method) analyze interdependencies between classes analyze dependencies between methods reverse engineer an abstract spec for each method