MultiMaker 2 Documentation

Program, examples and documentation © 2005 David Rowbory.
david@rowbory.net

Introduction

MultiMaker 2 (MM2) is a complete rewrite of the original HyperCard™-based multiple choice test editing, marking and printing program written around 1995-6. This new version is written using Java, JavaScript, XML and HTML to be very flexible (not just BuzzWord®-compliant) and to run on all kinds of computer systems. The test files themselves will be easy to edit and read into other software to make the data entry future-safe.

The idea is that someone who wants to write a new multiple-choice test uses the MultiMaker program.

How to install

First install the Sun Java engine:
	Windows: http://java.sun.com
	Mac OS X: should already be installed
	Mac OS 9: MRJ from Apple.

Then copy the MultiMaker folder to your hard disc and run it from there.

How to make tests with MultiMaker

Run the MultiMaker application:
	Mac OS: double-click MultiMaker application
	Windows: Double-click RunMM.bat

This opens a window with a menu bar. Choose New or Open... from the File menu to create a new blank test or open an existing one.

1. Each test has a title and a description which will be displayed in the final self-marking test.
2. Click New Question to add a new question. Questions are numbered automatically. Click Del beneath a question to delete it.
3. Type the question text in the large box. If you want to add a picture, click on the pic button and choose the file. It is best to choose a file in the same directory as the test is saved, or one directory all the computers can reach.
4. Type in text for each option and click Add Option to add more. Each question can have as many options as you like.
5. Click on the checkbox to set an option as a correct answer. You can have as many correct answers as you like. All-or-nothing marking is used so the question must be answered completely right to gain credit.
6. To delete options click on - Option. (Slight bug here: you must delete options from the last one down or slightly bad things can happen as it gets confused with how many options there are.)
7. Click Save to save the test (a good idea to do that as you go along).
8. Click Save As to save it somewhere else or under a different name. Make sure you end the file with .mmtest otherwise you will be unable to reopen it.
9. Click Produce Test to create the HTML/web test file which pupils will use.

Please remember to save the file. You will not be reminded if you close the window. All your changes will disappear unless you explicitly save them.

Once the test html files have been created you can copy them onto a website or other computers. That leads us into how to use the tests:

How to use tests

Produce a test using MultiMaker. You should save it as an html file. Copy this file and the mark.js and stylesheet.css files (these 2 are vital support files) onto the computer where you want to carry out the test. When ready to start the test, double-click the test html file. A web browser should start.

The student should type in their name and choose their class, then go through the questions ticking the boxes of correct answers. When satisfied with their work, they click 'Mark' and the test will be marked. 

As well as working out the score, the background of the questions will change to show what was right and wrong. Red indicates the student ticked a box they should not have ticked, and orange that they did not tick a box they should have done. Green indicates correct answers!

The tick boxes and buttons are disabled as soon as marking has finished so the test can not just be resubmitted or forged.

After the student is told the score they should show the page to their teacher to record it. Later, we plan to make it possible to email scores through to teachers.

Licence

This software was developed privately, mainly initially for Ross Hall Academy RME department who commissioned the update of the freely produced MultiMaker 1.2.5. Redistribution is only permitted with express email/written permission of the author, David Rowbory, or Ross Hall Academy RME department. Otherwise, the test-producing software and documentation may not be copied. HTML Test files are exempt from this restriction.

Areas for development

Class names must be entered manually into the program by me, the programmer. So in the short term I need a list of the class names required. In the longer term, we need some easy way of modifying this list.

Make it warn you when you close a window and haven't saved.

Email results to teachers.

Auto-save

Less junk on output.

Better graphics and GUI.

Obscure the answers in the test file to avoid cheating.

Different ways of scoring partial matches to be more generous.