Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Leon H. Binder

dblp:91/6343 · DBLP profile ↗
← Back
2ranked-venue papers
1as first author
0since 2021 · last 1992
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 2 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Requirements engineering and software design · 44% Software testing · 44% Program verification · 13%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Requirements engineering and software design
formal specification
0.011992
The Automated Production Control Documentation System: A Case Study in Cleanroom Software Engineering · ACM Trans. Softw. Eng. Methodol. 1992
Software testing
statistical testing
0.011992
The Automated Production Control Documentation System: A Case Study in Cleanroom Software Engineering · ACM Trans. Softw. Eng. Methodol. 1992
Program verification › hardware verification
functional verification
0.011992
The Automated Production Control Documentation System: A Case Study in Cleanroom Software Engineering · ACM Trans. Softw. Eng. Methodol. 1992

Methods — techniques the papers use, named apart from their topics

walkthrough · 0.0team reviews · 0.0cleanroom software engineering · 0.0
YearPublicationVenuePosition
1992 The Automated Production Control Documentation System: A Case Study in Cleanroom Software Engineering
abstract
A prototype software system was developed for the U.S. Naval Underwater Systems Center(NUSC) as a demonstration of the Cleanroom Software Engineering methodology. The Cleanroom method is a team approach to the incremental development of software under statistical quality control. Cleanroom's formal methods of Box Structure specification and design, functional verification, and statistical testing were used by a four-person team to develop the Automated Production Control Documentation(APCODOC) system, a relational database application. As is typical in Cleanroom developments, correctness of design and code were ensured through team reviews. Eighteen errors were found during functional verification of the design, and nineteen errors were found during walkthrough of the 1820 lines of FOXBASE code. The software was not executed by developers prior to independent testing (i.e., there was no debugging). There were no errors in compilation, no failures during statistical certification testing, and the software was certified at the target levels of reliability and confidence. Team members attribute the ultimate error-free compilation and failure-free execution of the software to the rigor of the methodology and the intellectual control afforded by the team approach.
Carmen J. Trammell, Leon H. Binder, Cathrine E. Snyder
ACM Trans. Softw. Eng. Methodol.2
1990 Field Experiments with Local Software Quality Metrics
abstract
Abstract The theory for local software quality metrics that appeared in Software‐Practice and Experience in November has been tested in field experiments. Data collected in the experiments and the results are presented here. The theory prescribed two activities, one for articulating rule sets for quality and the other for deriving a statistical metric. The process of deriving the statistical metric has been reduced to easy practice. Effective articulation of rule sets is still under study.
Leon H. Binder, Jesse H. Poore
Softw. Pract. Exp.1