As outlined in the UI Overview, the Test Tool system is comprised of two separate application programs. The regular teacher program runs on as many client computers as there are users. It provides functionality to create questions and generate, administer, and grade tests. The other program is for students to take tests and view past graded exams.

In the teacher application, the major object in the user program is the Test. It's implementation will need to provide efficient access for a wide range of operations, including access to questions, the ability to be passed to the student application, and to be taken. Hence, it will need to use a moderately sophisticated data structure that supports these various forms of access.

Aside for the Test, the other objects in the regular user test tool should have reasonably straightforward implementations.

In student application, the major object is also the Test. The student will be able to take the tests that are passed from the teacher application and view past graded exams that are graded in the teacher applcation.

The distributed processing of the networked Test Tool environment will require specific development expertise. In particular, the developers need knowledge of client/server design and implementation. Functionality to support client/server architectures is available in many modern libraries. It will make sense for the developers to choose an implementation language in which client/server support is available, dependable, and well documented.