Project SCS

1
Project SCS

• a lightweight source control system for Windows
  platforms

2
The Need for Source Control

• Projects are not done by an individual
• Projects are not done at the same location
• This is especially true with open source and
  free software, where large projects have
  developers across the world.

3
The Need for Source Control

• Important drawbacks of no source control
• Same file may be simultaneously edited by more
  than one developer, which will eventually cause
  consistency problems .
• Some previous working version of the software
  might be required (and storing all versions is a
  huge waste of space).

4
Similar Systems

• An excellent version control and source control
  system exists for Linux known as the CVS
  (Concurrent Versions System).
• A port of CVS for Windows called WinCVS is
  available (though not as mature).
• Visual SourceSafe is available for development
  with Microsoft Visual Studio.

5
Basic Architecture

• The SCS System consists of
• The SCS Server (local or remote) acting as a
  repository
• SCS Clients

SCS Server
SCS Client A
SCS Client B
6
Overview of Features

• Does not depend on the programming language or
  IDE used.
• Is quite lightweight and well-suited for medium
  sized projects.
• Supports integrated editing with the editor
  chosen by the developer.
• Allows regeneration of source files of previous
  versions but stores only the differences in each
  version (not implemented yet).

7
The SCS Server

• The server may be local or remote, and starts
  as soon as the Administrator logs in to the SCS
  system using the following interface

8
The SCS Server (contd.)

• This loads the view of the Projects in the
  SCS server where information about each project
  is displayed.

9
The SCS Server (contd.)

• The view may be changed to show the details
  of every user along with the projects he/she is
  involved in

10
The SCS Server (contd.)

• There are modules for managing (adding,
  deleting, editing etc.) users and projects.

11
The SCS Client

• The client logs into the server using a
  dialog, which enables him to use a local or
  remote SCS server.
• The default port used is 2401 (which is the
  same tcp port used by cvs on Linux).

12
The SCS Client (contd.)

• The client now successively selects the
  project, the files and the editor and starts
  working. At the end the changes are committed to
  the SCS server.

13
Improvements Planned

• Instead of storing the entire files for all the
  versions it is desirable to store only the
  differences (using an algorithm similar to the
  one used in the UNIX diff utility).
• Automatic publishing of a projects status on the
  web.
• Encrypting the network data transfer for security
  (using SSH is a possibility).

14
Thank You

• Project Team
• Shibdas Bandyopadhyay (IIIT-C)
• Rajorshi Biswas (IIIT-C)