Using Learning Styles to Staff and Improve Software Inspection Team Performance

@article{Goswami2016UsingLS,
  title={Using Learning Styles to Staff and Improve Software Inspection Team Performance},
  author={Anurag Goswami and Gursimran Singh Walia and Urvashi Rathod},
  journal={2016 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)},
  year={2016},
  pages={9-12}
}
Software inspections are most widely used technique by industrial practitioners for improving software quality. While inspections are an effective verification technique, evidence suggests that overall performance of an inspection process is highly dependent on an individual inspectors' ability to detect faults. Our work leverages cognitive science research to help improve the inspection team performance. This paper presents the results from two industrial studies that evaluate the effect of… Expand
Using Supervised Learning to Guide the Selection of Software Inspectors in Industry
TLDR
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
Test Case Review Processes in Software Testing
TLDR
The goal of the present paper is to identify the role of review processes in software testing and to achieve this goal, the process of test case review has been implemented during testing. Expand
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
Automated mapping of fault logs to SRS requirements using key-phrase extraction
TLDR
The proposed approach extracts the key-phrases to identify key problems from fault-logs, and then maps them back to group of similar requirements in an SRS document to inspect requirements that may contain a similar types of faults. Expand
Application of back-translation: a transfer learning approach to identify ambiguous software requirements
TLDR
By augmenting requirements using BT, ULMFiT got a higher accuracy than SVM, Logistic Regression, and Multinomial Naive Bayes classifier, and provides some promising insights on how transfer learning and text augmentation can be applied to small data sets in requirements engineering. Expand
Using Learning Styles to Improve Software Requirements Quality: An Empirical Investigation
TLDR
Using nanofiltration membranes for the recovery of phosphorous with a second type of technology for the Recovery of nitrogen is suggest to be a viable process. Expand

References

SHOWING 1-10 OF 29 REFERENCES
A cognitive-based mechanism for constructing software inspection teams
TLDR
This work proposes an approach to add diversity into the software inspection process by using a cognitively-based team selection mechanism to maximize the number of different defects discovered. Expand
The Impact of Background and Experience on Software Inspections
TLDR
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
Advances in software inspections
  • Michael E. Fagan
  • Engineering, Computer Science
  • IEEE Transactions on Software Engineering
  • 1986
TLDR
Studies and experiences are presented which enhance the use of the inspection process and improve its contribution to development of defect-free software on time and at lower cost. Expand
Understanding the sources of variation in software inspections
TLDR
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
How perspective-based reading can improve requirements inspections
TLDR
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
Investigation of individual factors impacting the effectiveness of requirements inspections: a replicated experiment
TLDR
The main result from the original study, which is supported in the replication, was that inspectors whose degree is in a field related to software engineering are less effective during a requirements inspection than inspectors whose degrees are in other fields. Expand
An experiment to assess different defect detection methods for software requirements inspections
  • A. Porter, L. Votta
  • Computer Science
  • Proceedings of 16th International Conference on Software Engineering
  • 1994
TLDR
A scenario-based detection method, in which each reviewer executes a specific procedure to discover a particular class of defects has a higher defect detection rate than either ad hoc or checklist methods. Expand
N-Fold inspection: a requirements analysis technique
TLDR
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
Observational studies to accelerate process experience in classroom studies: an evaluation
TLDR
The results show that the proposed method for gaining experience provided subjects with enough experience to improve their effectiveness in some but not all cases, and there was an indication from the results thatThe proposed method allowed the subjects to become more comfortable with a new technique. Expand
An empirical methodology for introducing software processes
TLDR
An empirical methodology is introduced, based on experiences garnered over more than two decades of work by the Empirical Software Engineering Group at the University of Maryland, for taking a newly proposed improvement to development processes from the conceptual phase through transfer to industry. Expand
...
1
2
3
...