Software Engineering 2 Term Project by: Feras Batarseh Nestor Rivera.

Slides:



Advertisements
Similar presentations
Organizational Environment for Knowledge Management
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.
Chapter 2 The Software Process
Static Technique. Static Technique - Review  A way of testing software work products  Program code, requirement spec., design spec.  Test plan, test.
SE382 Software Engineering Lecture 21b
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.
1 Software Testing and Quality Assurance Lecture 2 Software Verification & Validation.
Quality Management System
Verification and Validation
Quality Control Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill.
1 Software Inspections and Walkthroughs Author: A. Frank Ackerman Presented by Cynthia Johnson EEL6883.
1CMSC 345, Version 4/04 Verification and Validation Reference: Software Engineering, Ian Sommerville, 6th edition, Chapter 19.
OHT 4.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Managing Project Quality
UNIT-II Chapter : Software Quality Assurance(SQA)
Software Inspections and Walkthroughs By. Adnan khan.
© 2000 Hans Schaefer Slide no. 1 Integration between reviews and test Can you save test work after inspections? Self assessment about how you do inspections.
N By: Md Rezaul Huda Reza n
Software Quality Assurance Lecture #4 By: Faraz Ahmed.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 10: Testing and Inspecting to Ensure High Quality Part 4:
Software Inspections. Defect Removal Efficiency The number of defects found prior to releasing a product divided by The number of defects found prior.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
Phil Cronin Anne Hill Allen Schones CIS841 Summer on Campus 1998 IN-PROCESS INSPECTIONS FOR OBJECT ORIENTED DESIGNS.
- Component Inspection. -Usability Testing. -Unit Testing. -System Testing.
Software Quality Assurance Lecture #2 By: Faraz Ahmed.
Chapter 2 Process: A Generic View
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
© 2011 Underwriters Laboratories Inc. All rights reserved. This document may not be reproduced or distributed without authorization. ASSET Safety Management.
By Ritesh Reddy Nagaram.  Organizations which are developing software processes are facing many problems regarding the need for change of already existing.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Product Design Finalization; Inspections.
Formal Technical Reviews Matt Graham 18 November 2004 EECS 814 University of Kansas.
Process Improvement. Improving the Test Process In the Software V&V course, Prof. Uwe asked the question: How to improve the Testing Process?
Jump to first page (C) 1998, Arun Lakhotia 1 Quality Assurance: Reviews and Walkthroughs Arun Lakhotia University of Southwestern Louisiana Po Box
CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE
CS Process Improvement CMM Hans Van Vliet, Software Engineering, Principles and Practice, 3 rd edition, John Wiley & Sons, Chapter 6. W. Humphrey,
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
Formal Methods in Software Engineering
Chapter 12: Software Inspection Omar Meqdadi SE 3860 Lecture 12 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Inspection and Review The main objective of an Inspection or a Review is to Detect Defects. (Today -there may be some other goals or broader definition.
© 2001 Hans Schaefer Slide no. 1 Fast reviews Fast reviews for small immature organizations Hans Schaefer Software Test Consulting N-5281 Valestrandsfossen,
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Inspection and Review The main objective of an Inspection or a Review is to detect defects. This activity and procedure was first formalized by Mike Fagan.
Higher National Certificate in Engineering Unit 36 Lesson 1 - Statistical Process Control.
© Michael Crosby and Charles Sacker, 2001 Systematic Software Reviews Software reviews are a “quality improvement process for written material”.
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
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.
Software Project Management Lecture # 12. Outline Quality Management ( chapter 26 - Pressman )  SQA  Who does it?  SQA Activities  Software reviews.
Verification vs. Validation Verification: "Are we building the product right?" The software should conform to its specification.The software should conform.
1 Software Testing and Quality Assurance Motivation and Review of Software Verification & Validation (2)
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
Software Reviews Ashima Wadhwa.
Software Quality Control and Quality Assurance: Introduction
CIS 375 Bruce R. Maxim UM-Dearborn
Software Configuration Management (SCM)
CSC 480 Software Engineering
Quality Quality is “a characteristic or attribute of something.”
Verification and Validation
Quality Assurance (Unplanned Inspections) Scenario Overview
Quality management standards
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Inspection and Review The main objective of an Inspection or a Review is to detect defects. (Not for Giving Alternative Solutions) This activity and procedure.
Applied Software Project Management
DEN Student Roles In Detail
Chapter # 8 Quality Management Standards
Testing and Inspection Present and Future
Software Reviews.
Presentation transcript:

Software Engineering 2 Term Project by: Feras Batarseh Nestor Rivera

What are the differences between Inspection and Testing? Why people at industry aren't using Inspection? How to use Inspection efficiently?

Assessment behind statement: “Even though several empirical studies which compare inspection more favorably than testing, it is still not as widely used as testing…”

 Achieve software quality greatest challenge.  Testing is most recognized technique -> no practical substitute  Testing downfall: defects uncovered late.  Among other alternatives: Software Inspections

Software Inspections are a disciplined engineering practice for detecting and correcting defects in software artifacts, and preventing their leakage into field operations. Software testing is any activity aimed at evaluating an attribute or capability of a program or system and determining that it meets its required results, making sure that it’s the valid system and verifying its work.

 Planning  Overview  Preparation  Meeting  Rework  Follow-up

 Author  Moderator  Reader  Recorder  Inspector

 Different stages -> Immediate detection  Fagan’s Study: 23% productivity improvement 38% Quality improvement  Self Regulating (feedback)

 Members distributed geographically  Only mature process and organization  Customer demands Personality issues  Give/ receive feedback  Severe stress  Up-front cost  Long run benefits  Tools and training

Virtual/Online Software Inspections: Inspection methods that eliminate meetings are at least as cost-effective as methods that rely heavily on them. The benefits of holding a meeting is less than the benefits of letting individuals work alone.

 Unit testing  Integration testing).  Functional testing  System testing  Acceptance testing

Quantitative approach Automated tool

Defined Testing and Inspection. Analyzed Reasons for why Inspection isn’t used enough. Looked at the future of testing and inspection and recommended new methods.

Thank you for listening!