All database models are derived from IT specifications. IT specifications come from analysts and designers which get their information from future IT users. Both software and database need input from users. A database design is in most cases technically oriented, using artificial keys, additional indexes and much more.

The technical details are for tuning performance; maintaining information consistency and adding required security. They are database system dependent and have little to do with the original specification phase.

Once database systems are implemented and used it may prove to be very difficult to alter the design when specifications are misunderstood from the beginning. Design is very important; all other technical details can be added later.

Improving the original design to reduce future maintenance needs exact and valid specifications from your future users. The more a user is involved in this phase the less chance you have getting mistakes in your design. The more you base your design on the verbalisations of your users, the less chance you have to make mistakes in the design.

CaseTalk captures the original examples and verbalisations from your future users. From this CaseTalk constructs a non-technical information model. CaseTalk can generate database scripts for several database systems and versions. While CaseTalk does not support a very technical level of database tweaking and tuning the generated scripts can be used immediately or used as a base for DBA's and other technical staff.