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

Sergio Delgado Castellanos

dblp:223/0443 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2018
—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 · 61% Program analysis · 30% Software maintenance and evolution · 9%

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

TopicWeightPapersLastEvidence papers
Software testing › test generation
specification-based test generation
0.312018
Translating code comments to procedure specifications · ISSTA 2018
Program analysis
specification mining
0.312018
Translating code comments to procedure specifications · ISSTA 2018
Software testing
test generation
0.312018
Translating code comments to procedure specifications · ISSTA 2018
Software maintenance and evolution
software documentation
0.112018
Translating code comments to procedure specifications · ISSTA 2018

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

semantic matching · 0.3pattern matching · 0.3natural language processing · 0.3lexical matching · 0.3
YearPublicationVenuePosition
2018 Translating code comments to procedure specifications
abstract
Procedure specifications are useful in many software development tasks. As one example, in automatic test case generation they can guide testing, act as test oracles able to reveal bugs, and identify illegal inputs. Whereas formal specifications are seldom available in practice, it is standard practice for developers to document their code with semi-structured comments. These comments express the procedure specification with a mix of predefined tags and natural language. This paper presents Jdoctor, an approach that combines pattern, lexical, and semantic matching to translate Javadoc comments into executable procedure specifications written as Java expressions. In an empirical evaluation, Jdoctor achieved precision of 92% and recall of 83% in translating Javadoc into procedure specifications. We also supplied the Jdoctor-derived specifications to an automated test case generation tool, Randoop. The specifications enabled Randoop to generate test cases of higher quality.
Arianna Blasi, Alberto Goffi, Konstantin Kuznetsov 0001, Alessandra Gorla, Michael D. Ernst, Mauro Pezzè, Sergio Delgado Castellanos
ISSTA7