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

Masato Tada

dblp:41/2262 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1993
—ORCID · none

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

Software engineering, systems software and programming languages · 1

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 · 56% Empirical software engineering · 44%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software design representation
design documentation
0.011993
A Case History Development of a Foolproofing Interface Documentation System · IEEE Trans. Software Eng. 1993

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

foolproofing · 0.0case study · 0.0
YearPublicationVenuePosition
1993 A Case History Development of a Foolproofing Interface Documentation System
abstract
The authors discuss information transmission errors occurring between design engineers involved in software development and describe an interface design documentation system that can prevent them. The equivalence of human errors in software design and hardware manufacturing activities is established. The characteristics that must be included in an interface documentation system to prevent communication errors in software design activities, based on foolproofing principles that were identified for hardware manufacturing, are discussed. Utilizing these characteristics, an example of an interface documentation system for software products which control measuring equipment is presented. Its effects on the resultant number of communication errors between hardware and software engineers is subsequently experimentally evaluated.>
Takeshi Nakajo, Isao Azuma, Masato Tada
IEEE Trans. Software Eng.3