Hitoshi Kume

dblp:90/2283 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1991
—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
Software testing · 44% Software maintenance and evolution · 44% Requirements engineering and software design · 13%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
fault tree analysis
0.011991
A Case History Analysis of Software Error Cause-Effect Relationships · IEEE Trans. Software Eng. 1991
Software testing › fault analysis
software error analysis
0.011991
A Case History Analysis of Software Error Cause-Effect Relationships · IEEE Trans. Software Eng. 1991

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

fault tree analysis · 0.0cross-indexing · 0.0
YearPublicationVenuePosition
1991 A Case History Analysis of Software Error Cause-Effect Relationships
abstract
Approximately 700 errors in four commercial measuring-control software products were analyzed, and the cause-effect relationships of errors occurring during software development were identified. The analysis method used defined appropriate observation points along the path leading from cause to effect of a software error and gathered the corresponding data by analyzing each error using fault tree analysis. Each observation point's data were categorized, and the relationships between two adjoining points were summarized using a cross-indexing table. Four major error-occurrence mechanisms were identified; two are related to hardware and software interface specification misunderstandings, while the other two are related to system and module function misunderstandings. The effects of structured analysis and structured design methods on software errors were evaluated.>
Takeshi Nakajo, Hitoshi Kume
IEEE Trans. Software Eng.2