The DOI matches its Crossref record.
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.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cited by
Two case studies of open source software development: Apache and Mozilla
Mockus, A., Fielding, R. T., & Herbsleb, J. D. (2002) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/567793.567795 · Cited by 1,685
Rcs — a system for version control
Tichy, W. F. (1985) · Software: Practice and Experience · doi:10.1002/spe.4380150703 · Cited by 944
AnO(ND) difference algorithm and its variations
Myers, E. W. (1986) · Algorithmica · doi:10.1007/bf01840446 · Cited by 893
Predicting fault incidence using software change history
Graves, T. L., Karr, A. F., Marron, J. S., & Siy, H. (2000) · IEEE Transactions on Software Engineering · doi:10.1109/32.859533 · Cited by 753
Knowledge management in software engineering
Rus, I., & Lindvall, M. (2002) · IEEE Software · doi:10.1109/ms.2002.1003450 · Cited by 742
“While Design Rationale is an explicit approach to creating an organizational memory, regular tools for version control such as the Source Code Control System (SCCS) (Rochkind, 1975) represent a class of tools that indirectly create such a memory.”
Predicting faults using the complexity of code changes
Hassan, A. E. (2009) · 2009 IEEE 31st International Conference on Software Engineering · doi:10.1109/icse.2009.5070510 · Cited by 708
Seesoft-a tool for visualizing line oriented software statistics
Eick, S. C., Steffen, J. L., & Sumner, E. E. (1992) · IEEE Transactions on Software Engineering · doi:10.1109/32.177365 · Cited by 616
Version models for software configuration management
Conradi, R., & Westfechtel, B. (1998) · ACM Computing Surveys · doi:10.1145/280277.280280 · Cited by 586
A state-of-the-art survey on software merging
Mens, T. (2002) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2002.1000449 · Cited by 532
Identifying reasons for software changes using historic databases
Mockus, & Votta (2000) · Proceedings 2000 International Conference on Software Maintenance · doi:10.1109/icsm.2000.883028 · Cited by 472
Predicting risk of software changes
Mockus, A., & Weiss, D. M. (2002) · Bell Labs Technical Journal · doi:10.1002/bltj.2229 · Cited by 429
Empirical studies of software engineering: a roadmap
Perry, D. E., Porter, A. A., & Votta, L. G. (2000) · Proceedings of the Conference on The Future of Software Engineering · doi:10.1145/336512.336586 · Cited by 356
Design, implementation, and evaluation of a Revision Control System
Tichy, W. F. (1982) · Purdue e-Pubs (Purdue University System) · doi:10.5555/800254.807748 · Cited by 300
The C information abstraction system
Chen, Y.-F., Nishimoto, M. Y., & Ramamoorthy, C. V. (1990) · IEEE Transactions on Software Engineering · doi:10.1109/32.48940 · Cited by 278
Automatically documenting program changes
Buse, R. P. L., & Weimer, W. R. (2010) · Proceedings of the IEEE/ACM international conference on Automated software engineering · doi:10.1145/1858996.1859005 · Cited by 219
Early Detection of Collaboration Conflicts and Risks
Brun, Y., Holmes, R., Ernst, M. D., & Notkin, D. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2013.28 · Cited by 82
Metadata
- Authors
- Rochkind, M. J.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 1975-12
- Volume
- SE-1
- Issue
- 4
- Pages
- 364-370
- ISSN
- 0098-5589 (ISSN-L)
- 1939-3520
- 2326-3881
- OpenAlex
- W1990244497
- Cited by
- 708
- References
- 0
- FWCI
- 22.94
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.