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
Demo Data from EDBT 2026 / reviewers in the wild / expert

Yves Romain

dblp:45/3831 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1986
—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 · 62% Empirical software engineering · 19% Operating systems · 19%

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

TopicWeightPapersLastEvidence papers
Software testing
software reliability		 0.011986
A Statistical Methodology for the Study of the Software Failure Process and Its Application to the ARGOS Center · IEEE Trans. Software Eng. 1986
Operating systems
operating system reliability		 0.011986
A Statistical Methodology for the Study of the Software Failure Process and Its Application to the ARGOS Center · IEEE Trans. Software Eng. 1986

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

statistical analysis · 0.0
YearPublicationVenuePosition
1986 A Statistical Methodology for the Study of the Software Failure Process and Its Application to the ARGOS Center
abstract
The authors propose a stepwise statistical methodology for the study of operating system reliability and associated tools. An example of the application of this method for the ARGOS data processing center of France's CNES is presented. It is shown that each evaluation of software reliability is considered as a special case. Two major consequences are that the reliability models need improvement and that every evaluation must be supported by a statistical analysis of the product and process characteristics.
Robert Troy, Yves Romain
 IEEE Trans. Software Eng.2