Active design reviews: Principles and practices

Parnas, David Lorge; Weiss, David M.

doi:10.1016/0164-1212(87)90025-2

Cited by 140 publications

(113 citation statements)

References 1 publication

Supporting

Mentioning

113

Contrasting

Order By: Relevance

“…A set of displays is complete if, for each specification of a non-standard subprogram found in part (3), there is exactly one display in which this specification forms part (1). Completeness can be checked mechanically.…”

Section: University Of Limerickmentioning

confidence: 99%

See 1 more Smart Citation

Software Inspections We Can Trust

Parnas

2004

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Software is devilishly hard to inspect. Serious errors can escape attention for years. Consequently, many are hesitant to employ software in safety-critical applications and developers and users are finding the correction of software errors to be an increasingly burdensome cost.This talk describes a procedure for inspecting software that consistently finds subtle errors in software that is believed to be correct. The procedure is based on four key principles:• All reviewers actively use the code.• Reviewers exploit the hierarchical structure of the code rather than proceeding sequentially through the code.• Reviewers focus on small sections of code, producing precise summaries that are used when inspecting other sections. The summaries provide the "links" between the sections. • Reviewers proceed systematically so that no case, and no section of the program, gets overlooked.The inspectors produce and review mathematical documents. The mathematics allows them to check for complete coverage; tabular notation allows the work to proceed systematically in small steps.

show abstract

Section: University Of Limerickmentioning

confidence: 99%

“…A display is correct if the program in part (2) will satisfy the specification in part (1) provided that all invoked programs satisfy the specifications in part (3).…”

Section: University Of Limerickmentioning

confidence: 99%

Software Inspections We Can Trust

Parnas

2004

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…Previous experimental work has been done to understand and improve software review and inspection procedures with respect to defect detection [3,16,20,22,23]. Inspections have been shown to be an effective tool for defect detection in software artifacts.…”

Section: Individual Variation Among Inspectorsmentioning

confidence: 99%

“…There were a series of studies that identified multiple groups of potential inspectors based on their knowledge of the application domain. Then subjects for the study were drawn only from those groups that had high domain knowledge [11,22]. These choices indicated that Domain Knowledge was a potential variable.…”

Section: Carver Identifying Implicit Process Variables and Basilimentioning

confidence: 99%

Identifying implicit process variables to support future empirical work

Carver¹,

Basili²

2003

J. Braz. Comp. Soc.

View full text Add to dashboard Cite

“…The essence of the technique is to detect errors in programs by human inspectors through reading and analyzing programs, based on some criteria. Many researchers have contributed to the progress of the technology by establishing various reading techniques [2,3,4,5] and inspection processes [6,7,8], but most of the existing techniques do not take formal speci…cation into account in program inspection, simply because formal speci…cation is not available in most industrial software development projects. With the continual development of formal methods, however, many industrial sectors have gradually adopted formal speci…cation techniques [9,10,11,12].…”

Section: Introductionmentioning

confidence: 99%

An Automated Approach to Specification-Based Program Inspection

Liu

Nagoya

Chen

et al. 2005

Formal Methods and Software Engineering

View full text Add to dashboard Cite

In this paper, we describe how formal speci…cation is adopted to improve the commonly used veri…cation and validation technique known as program inspection, in order to establish a more rigorous, repeatable, and e¢ cient inspection process than the conventional practice. We present a systematic approach to inspecting program code on the basis of the relation between functional scenarios de…ned in a speci…cation and execution paths implemented in its program. We report a prototype tool for the approach to support both forward and backward inspection strategies, and a case study of inspecting an Automatic Teller Machine system to evaluate the performance of the approach and the tool.

show abstract

Active design reviews: Principles and practices

Cited by 140 publications

References 1 publication

Software Inspections We Can Trust

Software Inspections We Can Trust

Identifying implicit process variables to support future empirical work

An Automated Approach to Specification-Based Program Inspection

Contact Info

Product

Resources

About