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

Ramesh Vasudevan

dblp:85/5882 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2004
—ORCID · unresolved

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.

Databases, data mining, and information retrieval
1 paper
Transaction processing and concurrency control · 100%
Software engineering, system software, and programming languages
1 paper
Software testing · 100%

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

TopicWeightPapersLastEvidence papers
Transaction processing and concurrency control › transaction models
long-lived transactions
0.012004
Using Data Versioning in Database Application Development · ICSE 2004
Transaction processing and concurrency control
versioning
0.012004
Using Data Versioning in Database Application Development · ICSE 2004
Software testing › database testing
database application testing
0.012004
Using Data Versioning in Database Application Development · ICSE 2004

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

versioning · 0.1
YearPublicationVenuePosition
2004 Using Data Versioning in Database Application Development
abstract
Database applications such as enterprise resource planning systems and customer relationship management systems are widely used software systems. Development and testing of database applications is difficult because the program execution depends on the persistent state stored in the database. In this paper we show that how versioning of the persistent data stored in the database can solve some critical problems in the development and testing of database applications can be solved by versioning the data stored in the database. Our solution framework is based on long transaction management, a well-researched branch of database systems. We also present empirical results that show the proposed framework's effectiveness in practice.
Ramkrishna Chatterjee, Gopalan Arun, Sanjay Agarwal, Ben Speckhard, Ramesh Vasudevan
ICSE5