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
Demo Data from VLDB 2026 / reviewers in the wild / expert

Marc J. Rochkind

dblp:89/5091 · DBLP profile ↗
← Back
2ranked-venue papers
2as first author
1since 2021 · last 2025
0009-0007-5736-0006ORCID · reported

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

Software engineering, systems software and programming languages · 2 · 2 first-author · 1 since 2021

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
Software maintenance and evolution · 77% Empirical software engineering · 23%

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

TopicWeightPapersLastEvidence papers
Software maintenance and evolution › software configuration management
version control		 0.922025
A Retrospective on the Source Code Control System · IEEE Trans. Software Eng. 2025
The Source Code Control System · IEEE Trans. Software Eng. 1975
Empirical software engineering
software engineering history		 0.312025
A Retrospective on the Source Code Control System · IEEE Trans. Software Eng. 2025
Software maintenance and evolution
software configuration management		 0.011975
The Source Code Control System · IEEE Trans. Software Eng. 1975

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

retrospective analysis · 0.9system design · 0.0
YearPublicationVenuePosition
2025 A Retrospective on the Source Code Control System
abstract
The Source Code Control System (SCCS) was first introduced in 1975 [1]. It controlled computer program source code by tracking versions and recording who made changes, when, and why. The present retrospective paper assesses the strengths and weaknesses of SCCS and traces its influence on software engineering over the past fifty years.
Marc J. Rochkind
 IEEE Trans. Software Eng.1
1975 The Source Code Control System
abstract
The Source Code Control System (SCCS) is a software tool designed to help programming projects control changes to source code. It provides facilities for storing, updating, and retrieving all versions of modules, for controlling updating privileges for identifying load modules by version number, and for recording who made each software change, when and where it was made, and why. This paper discusses the SCCS approach to source code control, shows how it is used and explains how it is implemented.
Marc J. Rochkind
 IEEE Trans. Software Eng.1