ArticleslgStudy

computer science

List of version-control software

List of version-control software is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand List of version-control software rather than just read about it. In short: This is a list of notable version control software systems. Common attributes Openness, whether the software is open source or proprietary Repository model, how working and shared source code is handled Shared, all developers use the same file system Client–server, users access a master repository server via a client; typically, a client machine holds only a working copy of a project tree; changes in one working cop…

Key takeaways

  • List of version-control software belongs to computer science; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect List of version-control software to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of List of version-control software from memory before moving on to harder problems.

Reference excerpt

This is a list of notable version control software systems.

Common attributes Openness, whether the software is open source or proprietary Repository model, how working and shared source code is handled Shared, all developers use the same file system Client–server, users access a master repository server via a client; typically, a client machine holds only a working copy of a project tree; changes in one working copy are committed to the master repository before becoming available to other users Distributed, repositories act as peers; typically each user has a local repository clone with complete version history in addition to their working files

Active AccuRev [proprietary, client-server] – source configuration management tool with integrated issue tracking based on "Streams" that manages parallel and global development; replication server is also available; now owned by Micro Focus Autodesk Vault [proprietary, client-server] – Version control tool specifically designed for Autodesk applications managing the complex relationships between design files such as AutoCAD and Autodesk Inventor CADES [proprietary, client-server] – Designer productivity and version control system by International Computers Limited ClearCase [proprietary, client-server] – MSSCCI compliant (Source Control Plug-in API) configuration management system by IBM Rational Software Darcs [open, distributed] – originally developed by David Roundy; track inter-patch dependencies and automatically rearranges and cherry-pick them using a theory of patches Dimensions CM [proprietary, client-server] – software change and configuration management system developed by Micro Focus, formerly Serena Software, that includes revision control Diversion [proprietary, client-server] – A cloud-based version control system for game development and projects with large 3D assets Fossil [open, distributed] – written by D. Richard Hipp for SQLite; distributed revision control, wiki, bug-tracking, and forum (all-in-one solution) with console and web interfaces; single portable executable and single repository file Git [open, distributed] – designed by Linus Torvalds for Linux kernel development; decentralized; goals: fast, flexible, and robust Global Design Platform (GDP) [proprietary, client-server] – design data management for IC design and Perforce infrastructure support Integrity [proprietary, client-server] Perforce P4 (formerly known by Perforce Helix and Perforce Helix Core) [proprietary, client-server] – for large scale development environments Mercurial [open, distributed] – written in Python as an open source replacement to BitKeeper; decentralized and aims to be fast, lightweight, portable, and easy to use OpenCVS – unreleased CVS clone under a BSD license, emphasizing security and source code correctness Panvalet [proprietary, shared] – Around since the 1970s, source and object control for IBM mainframe computers PVCS [proprietary, client-server] – developed by Don Kinzer at Polytron, first released in 1985; now owned by Micro Focus Razor [proprietary, ?] – integrated suite from Visible Systems Revision Control System (RCS) [open, shared] – stores the latest version and backward deltas for the fastest access to the trunk tip compared to SCCS and an improved user interface, at the cost of slow branch tip access and missing support for included/excluded deltas Source Code Control System (SCCS) [open, shared] – part of UNIX; based on interleaved deltas, can construct versions as arbitrary sets of revisions; extracting an arbitrary version takes essentially the same time and is thus more useful in environments that rely heavily on branching and merging with multiple "current" and identical versions StarTeam [proprietary, client-server] – coordinates and manages software delivery process by Micro Focus, formerly Borland; centralized control of digital assets and activities Subversion (SVN) [open, client-server] – versioning control system inspired by CVS Surround SCM [proprietary, client-server] – version control tool by Seapine Software Synergy [proprietary, client-server] – MSSCCI compliant (Source Control Plug-in API) integrated change management and task-based configuration management system, proprietary of IBM Team Concert [proprietary, client-server] – Collaboration and application lifecycle management platform by IBM Rational Software Team Foundation Version Control [proprietary, client-server] – version control system developed by Microsoft for Team Foundation Server, now Azure DevOps Server The Librarian [proprietary, shared] – Around since 1969, source control for IBM mainframe computers; from Applied Data Research, later acquired by Computer Associates Unity Version Control (previously known as Plastic SCM) [proprietary, client-server] – by Codice Software, Inc and Unity Technologies Vault [proprietary, client-server] – version control tool by SourceGear; first installation can be used for free

Obsolete The following have been discontinued or not released in more than a decade.

… excerpt ends here. Continue reading the full article.

Worked examples

Example 1 — a first encounter with List of version-control software

Start with the simplest possible case. Write down what List of version-control software claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to List of version-control software before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about List of version-control software ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of List of version-control software

In research
List of version-control software appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses List of version-control software in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
List of version-control software is common in secondary-school and first-year university syllabi. It links to neighbouring topics Lists of software, Version control systems, so understanding it makes those chapters shorter.
In everyday life
Look for List of version-control software outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study List of version-control software in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what List of version-control software means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain List of version-control software out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is List of version-control software in simple terms?

This is a list of notable version control software systems. Common attributes Openness, whether the software is open source or proprietary Repository model, how working and shared source code is handled Shared, all developers use the same file system Client–server, users access a master repository…

Why does List of version-control software matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study List of version-control software?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on List of version-control software.

Tags

  • Lists of software
  • Version control systems

Keep exploring