An empirical study of the effect of learning styles on the faults found during the software requirements inspection

  title={An empirical study of the effect of learning styles on the faults found during the software requirements inspection},
  author={Anurag Goswami and Gursimran Singh Walia},
  journal={2013 IEEE 24th International Symposium on Software Reliability Engineering (ISSRE)},
  • Anurag Goswami, G. Walia
  • Published 2013
  • Engineering, Computer Science
  • 2013 IEEE 24th International Symposium on Software Reliability Engineering (ISSRE)
Inspections aid software managers by early detection and removal of faults committed during the creation of requirements and design documents. This helps reduce the rework during the later stages of software development. While inspections are effective in practice, the evidence suggests that the effectiveness of inspectors varies widely. Cognitive psychologists have used Learning Style (LS) to show the improvement in student's score by considering their characteristic strength and preferences… Expand
Using Learning Styles to Improve Cost Effectiveness of Software Inspection Teams
Inspection is a widely known technique to detect faults in requirements document. It helps manager by early detection and removal of faults. Much of the cost can be saved by detecting faults duringExpand
Using a Cognitive Psychology Perspective on Errors to Improve Requirements Quality: An Empirical Investigation
A newly developed Human Error Taxonomy (HET) and a formal Error-Abstraction and Inspection (EAI) process to improve fault detection performance of inspectors during the requirements inspection and provide useful insights into commonly occurring human errors that contributed to requirement faults are described. Expand
Using Supervised Learning to Guide the Selection of Software Inspectors in Industry
This study analyzes the reading patterns (RPs) of inspectors recorded by eye-tracking equipment and evaluates their abilities to find various fault-types, showing that the approach could guide the inspector selection with an accuracy ranging between 79.3% and 94% forVarious fault- types. Expand
Using Eye Tracking to Investigate Reading Patterns and Learning Styles of Software Requirement Inspectors to Enhance Inspection Team Outcome
Analysis of reading trends of effective and efficient inspectors using eye movement and LS data of individual inspectors and virtual inspection teams shows inspectors who detect more faults during inspection, focus significantly more at the fault region to find and report faults as opposed to comprehending requirements information. Expand
Developing and Evaluating Learning Materials to Introduce Human Error Concepts in Software Engineering Courses: Results from Industry and Academia
Whether requirements inspections supported by human errors can be used to deliver knowledge about software engineering human errors as well as knowledge about requirements inspections (a key industry skill) to students is evaluated. Expand
There is a growing demand for software developers that is expected to grow even more in the coming years [1,2] It is important to ensure that students graduating are prepared for their future careersExpand
Improving the Requirements Inspection Abilities of Computer Science Students through Analysis of their Reading and Learning Styles
I am a research-oriented applications developer with more than ten years of professional programming experience primarily in the area of cognitive and vision research. I have been working at theExpand
Automating Key Phrase Extraction from Fault Logs to Support Post-Inspection Repair of Software Requirements
This research paper aims at developing an automated approach to identify fault prone requirements in a software requirement specification (SRS) document to mitigate the fault propagation to laterExpand
Teaching Software Requirements Inspections to Software Engineering Students through Practical Training and Reflection
Teaching Software Requirements Inspections to Software Engineering Students through Practical Training and Reflection and teaching software quality through practical training and reflection. Expand
Effect of Prompting Techniques and Learning Styles on Requirements Elicitation


The Impact of Background and Experience on Software Inspections
This dissertation is an initial study into the relationship between an inspector's characteristics and his or her effectiveness in an inspection, focused on the background and experience of the inspector as the source of variation. Expand
Understanding the sources of variation in software inspections
Acting on the hypothesis that the “inputs” into the inspection process (reviewers, authors, and code units) were significant sources of variation, they were responsible for much more variation in detect detection than was process structure. Expand
Orthogonal Defect Classification - A Concept for In-Process Measurements
The authors define ODC and discuss the necessary and sufficient conditions required to provide feedback to a developer; illustrate the use of the defect type distribution to measure the progress of a product through a process; and open the doors to a wide variety of analysis techniques for providing effective and fast feedback based on the concepts of ODC. Expand
How perspective-based reading can improve requirements inspections
The authors explain their perspective based reading (PBR) technique that provides a set of procedures to help developers solve software requirements inspection problems and shows how PBR leads to improved defect detection rates for both individual reviewers and review teams working with unfamiliar application domains. Expand
Active design reviews: principles and practices
An improved technique for reviewing designs is described, based on the following ideas, drawn from the application of active design reviews to the Naval Research Laboratory's Software Cost Reduction Project. Expand
A case study in root cause defect analysis
  • M. Leszak, D. Perry, D. Stoll
  • Engineering, Computer Science
  • Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium
  • 2000
A retrospective root cause defect analysis study of the defect Modification Requests discovered while building, testing, and deploying a release of a transmission network element product and introduced this analysis methodology into new development projects as an in-process measurement collection requirement for each major defect MR. Expand
Experience with Fagan's inspection method
  • E. Doolan
  • Engineering, Computer Science
  • Softw. Pract. Exp.
  • 1992
Fagan's inspection method was used by a software development group to validate requirements specifications for software functions and in general, they have proved to be favourable. Expand
Design and Code Inspections to Reduce Errors in Program Development (Reprint)
It is shown that by using inspection results, a mechanism for initial error reduction followed by ever-improving error rates can be achieved. Expand
N-Fold inspection: a requirements analysis technique
A comparison of N-fold inspection with other development techniques reveals that N- fold inspection is a cost-effective method for finding faults in the URD and may be a valid technique in the development of mission-critical software systems. Expand
Applications, Reliability and Validity of the Index of Learning Styles*
RICHARD M. FELDER and JONI SPURLIN North Carolina State University, Raleigh, North Carolina 27695±7905, USA. E-mail: The Index of Learning Styles (ILS) is an instrumentExpand