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.

Christina M. Kennedy

dblp:22/5393 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2003
—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 maintenance and evolution · 100%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution
artifact consistency
0.012003
CLIME: An Environment for Constrained Evolution Demonstration Description · ICSE 2003
Software maintenance and evolution › software configuration management
consistency management
0.012003
CLIME: An Environment for Constrained Evolution Demonstration Description · ICSE 2003

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

constraint-based consistency checking · 0.0
YearPublicationVenuePosition
2003 CLIME: An Environment for Constrained Evolution Demonstration Description
abstract
We are building a software development environment that uses constraints to ensure the consistency of the different artifacts associated with software. This approach to software development makes the environment responsible for detecting most inconsistencies between software design, specifications, documentation, source code, and test cases. The environment provides facilities to ensure that these various dimensions remain consistent as the software is written and evolves. The environment works with the wide variety of artifacts typically associated with a large software system. It handles both the static and dynamic aspects of software. Moreover, it works incrementally so that consistency information is readily available to the developer as the system changes. The demonstration will show this environment and its capabilities.
Steven P. Reiss, Christina M. Kennedy, Tom Wooldridge, Shriram Krishnamurthi
ICSE2