Not to repeat myself, I guess I already have written that oil hydraulics test rigs is my prime line and I computerize the controls and data logging as a value addition. The code could be in anything from C-Code for 8051, to VB to LabVIEW.

And no big team develops all the code - just me and my other software engineer. In fact I hardly do actual coding and restrict myself to structuring, flowcharts and such.

And till date SVC happens like this :

- The code is commented well.
- The first functional code is V1.00 and the the full details of the code are in a VERSION.TXT file that is part of the code folder.
- Any change to code is documented in the VERSION.TXT file and given a "Date-Time-PersonInitial" tag reference and the previous copy is archived. And the version number is changed. We of course have our own rules - minor , major etc.
- The version number is part of the Splash screen and when a problem is reported we ask for the Version number and I can pull up THAT code from archive.

Till date I have 35+ machines running with my code and just last week I was able to restore a machine with a code developed in 1998.

What more does a commercial SVC software like Vault or Perforce do beyond the above practices FOR A TWO MEMBER TEAM of code developers as I mentioned above ?

Maybe this is a naive question but still I just thought I will ask the experts. This is not to belittle the commercial SVC programs - but then we are not talking of things like MANY programmers, geographical distancing etc.

Thanks

Raghu