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

Vincent J. Kruskal

dblp:81/3366 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 2005
—ORCID · none

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

Software engineering, systems software and programming languages · 2

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
2 papers
Programming languages and type systems · 100%

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

TopicWeightPapersLastEvidence papers
Programming languages and type systems
object-oriented programming		 0.011995
Subject-Oriented Composition Rules · OOPSLA 1995
Programming languages and type systems › module systems
software composition		 0.011995
Subject-Oriented Composition Rules · OOPSLA 1995

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

separation of concerns · 0.1
YearPublicationVenuePosition
2005 The concern manipulation environment
abstract
No abstract available
William Chung, William H. Harrison, Vincent J. Kruskal, Harold Ossher, Stanley M. Sutton Jr., Peri L. Tarr, Matthew Chapman, Andrew Clement, Helen Hawkins, Sian January
 ICSE3
1995 Subject-Oriented Composition Rules
abstract
Subject-oriented programming supports composition of object-oriented programs or program fragments called subjects. This paper presents an approach to the composition rules used to specify composition details. Rules can be generic, allowing different subrules to be "plugged into" higher-level rules, and they include a means of specifying exceptions to general rules. We give definitions of a number of useful, generic rules, including merge and override, as a first step towards a generally-useful composition rule library. We also outline an object-oriented framework for implementing rules, which we are currently building as part of our support for subject-oriented programming in C++.
Harold Ossher, Matthew Kaplan 0003, William H. Harrison, Alexander Katz, Vincent J. Kruskal
 OOPSLA5