Verification based inspection

Dyer, M.

doi:10.1109/hicss.1992.183255

Cited by 8 publications

(3 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…An inspector repeats this procedure until the final function of the inspected code artifact has been abstracted and can be compared to the specification. This reading technique is limited to code artifact, though it provides a more formal approach for inspectors to check the functional correctness [37]. We found little information on the inspection process after the individual defect detection step.…”

Section: Team Selectionmentioning

confidence: 91%

“…This weakness led to the development of more procedural reading techniques. Techniques providing more structured and precise reading instructions include both a reading technique denoted "Reading by Stepwise Abstraction" for code documents advocated by the Cleanroom community [36] The technique "Reading by Stepwise Abstraction" was described in the context of the Verification-based Inspection approach [37]. This is an inspection variation used in conjunction with the Cleanroom software development method.…”

Section: Team Selectionmentioning

confidence: 99%

See 1 more Smart Citation

A Survey of Software Inspection Technologies

LAITENBERGER¹

2002

Handbook of Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Software inspection is a proven method that enables the detection and removal of defects in software artifacts as soon as these artifacts are created. It usually involves activities in which a team of qualified personnel determines whether the created artifact is of sufficient quality. Detected quality deficiencies are subsequently corrected. In this way an inspection can not only contribute towards software quality improvement, but also lead to significant budget and time benefits. These advantages have already been demonstrated in many software development projects and organizations. After Fagan's seminal paper presented in 1976, the body of work in software inspection has greatly increased and matured. This survey is to provide an overview of the large body of contributions in the form of incremental improvements and/or new methodologies that have been proposed to leverage and amplify the benefits of inspections within software development and even maintenance projects. To structure this large volume of work, it introduces, as a first step, the core concepts and relationships that together embody the field of software inspection. In a second step, the survey discusses the inspection-related work in the context of the presented taxonomy. The survey is beneficial for researchers as well as practitioners. Researchers can use the presented survey taxonomy to evaluate existing work in this field and identify new research areas. Practitioners, on the other hand, get information on the reported benefits of inspections. Moreover, they find an explanation of the various methodological variations and get guidance on how to instantiate the various taxonomy dimensions for the purpose of tailoring and performing inspections in their software projects.

show abstract

Section: Team Selectionmentioning

confidence: 91%

Section: Team Selectionmentioning

confidence: 99%

A Survey of Software Inspection Technologies

LAITENBERGER¹

2002

Handbook of Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

show abstract

“…Cleanroom Inspection is a component of Cleanroom software development [4]. In general, Cleanroom Inspection consists of individual review, followed by consolidation by the review leader.…”

Section: Formal Technical Review Methodsmentioning

confidence: 99%

Design for instrumentation: high quality measurement of formal technical review

Johnson

1996

Software Qual J

View full text Add to dashboard Cite

All current software quality assurance methods incorporate some form of formal technical review (FTR), because structured analysis of software artifacts by a team of skilled technical personnel has demonstrated ability to improve quality. However, FTR methods come in a wide variety of forms with varying effectiveness, incur significant overhead on technical staff, and have little computer support. Measurements of these FTR methods are coarse-grained, frequently low quality, and expensive to obtain. This paper describes CSRS, a highly instrumented, computer-supported system for formal technical review, and shows how it is designed to collect high quality, fine-grained measures of FTR process and products automatically. The paper also discusses some results from over one year of experimentation with CSRS; describes how CSRS improves current process improvement approaches to FTR; and overviews several novel research projects on FTR that are made possible by this system.

show abstract

Code Reading Techniques

Zhu

2016

Software Reading Techniques

View full text Add to dashboard Cite

Verification based inspection

Cited by 8 publications

References 4 publications

A Survey of Software Inspection Technologies

A Survey of Software Inspection Technologies

Design for instrumentation: high quality measurement of formal technical review

Code Reading Techniques

Contact Info

Product

Resources

About