A Survey of Software Inspection Technologies

LAITENBERGER, OLIVER

doi:10.1142/9789812389701_0023

Cited by 41 publications

(34 citation statements)

References 54 publications

(98 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Participants are identified who will attend the inspection meeting and also the schedule is set. Exit and entry criteria for the inspection meeting are identified [4].…”

Section: A Planningmentioning

confidence: 99%

“…A few limitations are also linked with this phase [4]. Inspection meetings require extensive time and more effort.…”

Section: B Overviewmentioning

confidence: 99%

“…Glib and Graham named review process as "Kickoff Meeting" and classified this process as discretionary process [4]. With the help of it, authors could be able to describe essential aspects of the SRS to the inspection team.…”

Section: B Overviewmentioning

confidence: 99%

See 2 more Smart Citations

Requirements Validation Techniques: An Empirical Study

Bilal¹,

Ilyas²,

Tariq³

et al. 2016

IJCA

View full text Add to dashboard Cite

Requirements validation makes sure that the requirements written in software requirements specification (SRS) must be complete and consistent and are according to the customer's needs. It ensures the validity of user requirements by eliminating ambiguities and inconsistencies from SRS. Several techniques for requirements validation have been discussed in the literature. This paper gives an overview of requirements validation techniques which have been practicing in industry, which includes requirements inspections, requirements prototyping, requirements testing and viewpoint-oriented requirements validation. This paper also highlights pros and cons of these techniques. In requirements testing, special attention is given to TCD inspections.

show abstract

“…Participants are identified who will attend the inspection meeting and also the schedule is set. Exit and entry criteria for the inspection meeting are identified [4].…”

Section: A Planningmentioning

confidence: 99%

“…A few limitations are also linked with this phase [4]. Inspection meetings require extensive time and more effort.…”

Section: B Overviewmentioning

confidence: 99%

See 1 more Smart Citation

Requirements Validation Techniques: An Empirical Study

Bilal¹,

Ilyas²,

Tariq³

et al. 2016

IJCA

View full text Add to dashboard Cite

show abstract

“…To address this problem, project managers focus on software inspections (i.e., reviewing requirements and design documents to identify faults) when they are easiest and cheapest to find and fix. Empirical evidence reports that, inspections at multiple organizations (e.g., IBM, TRW, ICL, Cardiac pacemakers) have led to significant improvements in quality, reduction in fault rate and delivering products within allocated time and cost [14].…”

Section: Introductionmentioning

confidence: 99%

Effectiveness of Human Error Taxonomy during Requirements Inspection: An Empirical Investigation

Anu¹,

Walia

et al. 2016

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Abstract-Software inspections are an effective method for achieving high quality software. We hypothesize that inspections focused on identifying errors (i.e., root cause of faults) are better at finding requirements faults when compared to inspection methods that rely on checklists created using lessons-learned from historical fault-data. Our previous work verified that, error based inspections guided by an initial requirements errors taxonomy (RET) performed significantly better than standard fault-based inspections. However, RET lacked an underlying human information processing model grounded in Cognitive Psychology research. The current research reports results from a systematic literature review (SLR) of Software Engineering and Cognitive Science literature -Human Error Taxonomy (HET) that contains requirements phase human errors. The major contribution of this paper is a report of control group study that compared the fault detection effectiveness and usefulness of HET with the previously validated RET. Results of this study show that subjects using HET were not only more effective at detecting faults, but they found faults faster. Post-hoc analysis of HET also revealed meaningful insights into the most commonly occurring human errors at different points during requirements development. The results provide motivation and feedback for further refining HET and creating formal inspection tools based on HET.

show abstract

“…It is used extensively in all phases of a software-system life cycle [3]. Classical Fagan type inspection defines a number of roles for the participants of a software inspection meeting: moderator, organizer, inspector, author and recorder.…”

Section: Code Review As a Form Of Inspectionmentioning

confidence: 99%