Technical overview - goals

The core goal behind the technical choices is that the CAWI (defined as the interview script running on the server, with the data on the server) and CAPMI (defined as the interview script running on the client, with data on the client) will be a single unified system, with the same code running on the server or in the browser, depending on the method of deployment.

It is envisaged that the two deployment methods will converge more closely, for example with the question display code always running on the server, communicating with the "engine" which could either be local (in the browser) or remote.

In addition, the new CAWI should be:

• Modular - small, managable components with clearly defined roles and interfaces.

• Documented

• Easily accessible to anyone in GIDE to incorporate into their own projects and workflows

• Open to new developers within GIDE