27th International Symposium on Software Reliability Engineering

Slides:



Advertisements
Similar presentations
Software Requirements
Advertisements

Static Technique. Static Technique - Review  A way of testing software work products  Program code, requirement spec., design spec.  Test plan, test.
Stepan Potiyenko ISS Sr.SW Developer.
درس مهندسی نیازمندی ها استاد دکتر عبداله زاده دانشجو خیرالنسا مرچانت Dealing with NFR : Three Experimental Studies of a Process-Oriented Approach.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Dealing.
Validating and Improving Test-Case Effectiveness Author: Yuri Chernak Presenter: Lam, Man Tat.
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The need for comprehensive software quality requirements Classification.
Dealing with NFRs Vahid Jalali Amirkabir university of technology, Department of computer engineering and information technology, Intelligent systems laboratory,
 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 Testing Verification and validation planning Software inspections Software Inspection vs. Testing Automated static analysis Cleanroom software.
COMPGZ07 Project Management Presentations Graham Collins, UCL
Dr. Tom WayCSC Code Reviews & Inspections CSC 4700 Software Engineering.
Development and application of guidance documents – industry view Dr Martin Schaefer ECCA-ECPA Conference March 2014.
Verification and Validation Overview References: Shach, Object Oriented and Classical Software Engineering Pressman, Software Engineering: a Practitioner’s.
Software Metrics and Reliability. Definitions According to ANSI, “ Software Reliability is defined as the probability of failure – free software operation.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Software Verification, Validation and Testing.
Inspection of Software Requirements Document Gursimran Singh Walia North Dakota State University Training 2: Inspection using.
FACILITATOR Prof. Dr. Mohammad Majid Mahmood Art of Leadership & Motivation HRM – 760 Lecture - 25.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Inspection of Software Requirements Document Gursimran Singh Walia North Dakota State University Training 1: Inspecting SRS using.
Software quality factors
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
SWE 513: Software Engineering
Information Technology Project Management Managing IT Project Risk.
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.
© Michael Crosby and Charles Sacker, 2001 Systematic Software Reviews Software reviews are a “quality improvement process for written material”.
Information Systems Dr. Ken Cosh Lecture 9.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Challenges in Promoting RCR: Reflections from a Public Funder´s Perspective Secretariat on Responsible Conduct of Research [Canadian Institutes of Health.
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
A Study on Human Factors in Maintenance of a Nuclear Power Plant Park Young Ho Dept. of Nuclear & Quantum Engineering Korea Advanced Institute of Science.
Inspecting Software Requirement Document
Evaluation Requirements for MSP and Characteristics of Designs to Estimate Impacts with Confidence Ellen Bobronnikov March 23, 2011.
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Using Human Errors to Inspect SRS
Software Quality Control and Quality Assurance: Introduction
Preventing HCAI’s through an education programme for nurses
CIS 375 Bruce R. Maxim UM-Dearborn
African-American Stimuli
Software Configuration Management (SCM)
Approaches to ---Testing Software
Software Verification and Validation
SEVERITY & PRIORITY RELATIONSHIP
Chapter 18 Maintaining Information Systems
Visiting human errors in IR systems from decision making perspective
Differentiating Psychopathic and Alexithymic Emotional Traits With Thin Slices of Verbal Behaviour K. Kaseweter, M.Sc. Candidate, University of Northern.
Preface to the special issue on context-aware recommender systems
Verification and Validation Overview
Chapter 11: Learning Introduction
Software Requirements
The science subject knowledge
Human Errors and the Error Abstraction Process
Writing Scientific Manuscripts
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
Software Engineering (CSI 321)
Chapter 3: The Requirements Workflow
Engineering Processes
Software Quality Engineering
Successful IT Projects By Darren Dalcher & Lindsey Brodie
Lesson 5. Lesson 5 Extraneous variables Extraneous variable (EV) is a general term for any variable, other than the IV, that might affect the results.
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.
Software Verification, Validation, and Acceptance Testing
Features of a Good Research Study
QA Reviews Lecture # 6.
September 10/11, 2014 OBJECTIVE: Students will evaluate the ethics of psychological research in order to examine and re-evaluate student-designed experiments,
Software Reviews.
Requirement Validation
Exploring Exploratory Testing
CR-GR-HSE-302 Management of change
Management of Change GROUP HSE RULE (CR-GR-HSE-302)
Presentation transcript:

27th International Symposium on Software Reliability Engineering ISSRE’2016 Error Abstraction Accuracy and Fixation during Error-based Requirements Inspections Supported by National Science Foundation Awards 1423279 and 1421006 Authors: Vaibhav Anu, Gursimran Walia (North Dakota State University) Wenhua Hu, Jeffrey C. Carver (University of Alabama) Gary Bradshaw (Mississippi State University)

Human Errors Human Errors Slips Lapses Mistakes Failure in the execution of plan Failure in the plan of action EXECUTION EXECUTION PLANNING e.g., lack of attention. e.g., inadequate planning, mostly from a lack of knowledge. e.g., forgetting one or more steps in a process. 2

Proposed APPROACH: Error ABSTRACTION AND INSPECTION (EAI) Error Abstraction (EA) Process What caused that fault? List of Human Errors List of New Faults (found during human error based reinspection) Reinspection (human error based) Requirements Document (SRS) List of Faults (found during FC Inspection) Inspection (FC based)

THE Human Error taxonomy (HET) Requirements Phase Human Errors STEP 1: Identifying Requirements Phase Human Errors from Software Engineering Literature STEP 2: Human Error Classification System Identified from Cognitive Psychology Literature Clerical Errors SLIPS LAPSES MISTAKES Lack of consistency in Requirement Specifications Loss of information from stakeholders Accidentally overlooking requirements Application errors Environment errors Information Management errors Wrong assumptions Low understanding of each other’s roles Mistaken belief that it is impossible to specify non-functional requirements in a verifiable form Not having a clear demarcation between client and users Lack of awareness of sources of requirements Problem-Solution errors Inadequate Requirements Process Syntactic errors

Purpose of current RESEARCH The current study examines the impact of Error Abstraction (EA) accuracy on inspectors’ fault detection effectiveness (during human error based reinspection). Another aspect of this research evaluates the “fixation tendencies” of inspectors during EA.

Empirical study design Training: Inspecting SRS using HET PRE-TEST Error Report Form Re-inspect SRS for remaining faults New Fault List 3 1 Reflection 2 Abstract and Classify Errors Inspectors POST -TEST 3 1 2 New Fault Form Fault Form Error Report Form Dr. Walia, I do not have the original experiment design figure. The one I have is monochromatic. Can you please replace this with the original. Inspect SRS using Errors Fault Checklist Error Abstraction Inspectors Post Study Questionnaire and Discussion with Subjects

Results of data analysis RQ1: Can an inspector’s EA accuracy predict their fault detection effectiveness during an error-based requirements inspection? Result: For both pre-test and post-test, it was found that EA accuracy was strongly and significantly correlated with the number of additional faults found using abstracted human errors. Implications for project managers employing error based inspections: it is important to ensure that inspectors are able to correctly perform the EA step, which in turn would help them detect more faults and ensure software quality. Pre-test (PGCS): EA Accuracy vs Fault Detection Effectiveness (r = 0.79, p = 0.0003) Post-test (RIM): EA Accuracy vs Fault Detection Effectiveness (r = 0.61, p = 0.0121)

Results of data analysis RQ2: Is there a potential for fixation bias during EA? Results: Inspectors tend to fixate on certain human error classes. More formal training on human error identification and improved error abstraction guidelines are required to help inspectors avoid fixation. Implications: Avoiding fixation is likely to improve EA accuracy, which consequently will improve fault detection effectiveness during error based inspections (as EA accuracy is strongly correlated with fault detection effectiveness). Effect of EA Fixation Clerical Errors Application Errors Lack of Consistency Errors Reported number of errors in RIM SRS (by all 16 subjects) 174 58 52 # of errors that were correctly abstracted (out of the reported number) 44 4 2 Top 3 most reported human errors classes (of HET) by subjects: Clerical errors (Slip) Application errors (Mistake) lack of consistency (Slip) Severe negative impact on EA accuracy

conclusion Results showed that EAI and HET can help provide significant gains in fault detection effectiveness Subjects provided suggestions for improving both, the error abstraction process, and the re-inspection (using abstracted errors) process More empirical studies under academic and industrial settings are required to generalize the results (particularly the results on human error insights).

Ongoing - Human ERROR ABSTRACTION ASSIST (HEAA)

27th International Symposium on Software Reliability Engineering ISSRE’2016 Error Abstraction Accuracy and Fixation during Error-based Requirements Inspections Supported by National Science Foundation Awards 1423279 and 1421006 Authors: Vaibhav Anu, Gursimran Walia (North Dakota State University) Wenhua Hu, Jeffrey C. Carver (University of Alabama) Gary Bradshaw (Mississippi State University)