Correctness verification: alternative to structural software testing

Dyer, M.; Kouchakdjian, Ara

doi:10.1016/0950-5849(90)90046-t

Cited by 6 publications

(6 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Such activities ascertain whether the developed software matches customer expectations and design specifications early in the software development life cycle. Practices promoting early detection and correction of errors help to design quality into the delivered software products (e.g., Laitenberger and DeBaud 2000, Slaughter et al 1998, Dyer and Kouchakdjian 1990. Consistent with prior research, we therefore expect the following.…”

Section: Software Process Maturity Andmentioning

confidence: 72%

Quality Improvement and Infrastructure Activity Costs in Software Development: A Longitudinal Analysis

Harter

Slaughter

2003

Management Science

View full text Add to dashboard Cite

This study draws upon theories of task interdependence and organizational inertia to analyze the effect of quality improvement on infrastructure activity costs in software development. Although increasing evidence indicates that quality improvement reduces software development costs, the impact on infrastructure activities is not known. Infrastructure activities include services like computer operations, data integration, and configuration management that support software development. Because infrastructure costs represent a substantial portion of firms' information technology budgets, it is important to identify innovations that yield significant cost savings in infrastructure activities. We evaluate quality and cost data collected in nine infrastructure activity centers over 10 years of product development in a major software firm undergoing a quality transformation. Findings indicate that infrastructure activities do benefit from quality improvement. The greatest marginal cost savings are realized in infrastructure activities that are highly interdependent with development and that occur later in the software development life cycle. Organizational inertia influences the rapidity with which the infrastructure activities benefit from higher product quality, especially for the more specialized activities. Finally, our findings suggest that although the savings in infrastructure from quality improvement are substantial, there are diminishing returns to quality improvement in infrastructure activities.Infrastructure Activity Costs, Software Product Development, Software Process Improvement, Software Quality, Capability Maturity Model, Organizational Inertia

show abstract

Section: Software Process Maturity Andmentioning

confidence: 72%

Quality Improvement and Infrastructure Activity Costs in Software Development: A Longitudinal Analysis

Harter

Slaughter

2003

Management Science

View full text Add to dashboard Cite

show abstract

“…It is surprising and encouraging that something as loosely defined as paraphrasing can be as effective in reducing the number of errors as Fagan and Russell have reported. Dyer and Kouchakdijan (1990) have gone a step further and introduced a technique of program verification in both the writing of the code and its inspection. The reported result is not only improved code quality, but also increased productivity.…”

Section: Code Inspections According To Fagan and To Russellmentioning

confidence: 99%

“…The discovery reported by Dyer and Kouchakdijan (1990) may have been made so late because of fundamental misunderstandings concerning the role of proofs in mathematics and in programming. Although the work of DeMillo ef al.…”

Section: Code Inspections According To Fagan and To Russellmentioning

confidence: 99%

See 1 more Smart Citation

Structured inspections of code

Emden

1992

Software Testing Verif & Rel

View full text Add to dashboard Cite

Cleanroom programming and code inspections independently provide evidence that it is more efficient to postpone the testing of code to a later stage than is usually done. This paper argues that an additional gain in quality and efficiency of development can be obtained by structuring inspections by means of an inspection protocol. The written part of such a protocol is prepared by the programmer before the inspection. It is modelled on Floyd's method for the verification of flowcharts. However, the protocol differs from Floyd's method in being applicable in practice. Structured inspections gain this advantage by not attempting to be a proof; they are no more than an articulation of existing forms of inspection. With the usual method of structured programming it may be difficult to prepare the inspection protol. On the other hand, ‘assertion‐driven programming’ (of which an example is included in this paper) not only facilitates protocol preparation, but also the coding itself.

show abstract

“…Software inspections (Fagan, 1986), mathematical approaches for specification and reliability (e. g. Dyer and Kouchakdjian, 1990;Mills et al, 1987) and software metrics (e. g. Fenton, 1991) help to review and control the development output as it becomes available. This encourages the early identification and correction of defects.…”

Section: Software Qualitymentioning

confidence: 99%