There are fundamental methodological differences between organizing native system development and organizing Unix/Linux and Windows development. ARCAD is extremely effective because it bridges these differences so that you can meet all your needs with one tool.

Open system developers have additional functions available that do not exist in native code:

• They can download all of an application’s source code onto their local PC at the start of a project,
• They have an additional token system that lets them manage synchronization of components between developers on the same project.

This token is exclusive within the project, but it can also be non exclusive for different projects underway at the same time.
Synchronization has two roles: it allows developers to load their own modifications onto the server, and to receive the modifications of other developers on the project. This process is often used by developers to back up their source code. During the synchronization phase, a local archive is produced as ZIP files. Developers can consult these archives and launch comparisons between versions for total monitoring of changes.

In this way, ARCAD creates unified batches of heterogeneous components. These batches are transported synchronously to test and production, with the same automatic functions.