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

Aino Cornils

dblp:37/4037 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1998
—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 · 44% Programming languages and type systems · 44% Software maintenance and evolution · 13%

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

TopicWeightPapersLastEvidence papers
Programming languages and type systems › language design
abstraction mechanisms
0.011998
How to Preserve the Benefits of Design Patterns · OOPSLA 1998
Requirements engineering and software design
design patterns
0.011998
How to Preserve the Benefits of Design Patterns · OOPSLA 1998
Software maintenance and evolution
software documentation
0.011998
How to Preserve the Benefits of Design Patterns · OOPSLA 1998

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

pattern analysis · 0.0
YearPublicationVenuePosition
1998 How to Preserve the Benefits of Design Patterns
abstract
The rapid evolution of Design Patterns has hampered the benefits gained from using Design Patterns. The increase in the number of Design Patterns makes a common vocabulary unmanageable, and the tracing problem obscures the documentation that should be enhanced by using Design Patterns. We present an analysis of Design Patterns that will strongly reduce the number of Fundamental Design Patterns and show how strong language abstractions can solve the tracing problem and thereby enhance the documentation.
Ellen Agerbo, Aino Cornils
OOPSLA2