Qarks AVS is built around configurations: code is tied to development tasks, which are themselves tied to bug reports or change requests. Therefore, you are able to follow the evolution of the code, build configurations/releases around certain subsets of changes (e.g. “Customer X wants version N of product Y, but with bugs V and W corrected”). Moreover, checking-out files when changes are needed allow early conflict detection, hardly available on simple versioning systems: developers save time, the whole company saves money and return on investment is very quick!
