Design requirements for the WCKER

Some of these requirements will be fulfilled in Java code; some, such as documentation, will not.

End user requirements

An end user is someone using a wizard in WCKER to create a course, e.g. Dr Simons in the EarlyUseCases

1. Clear documentation of what the wizard will do, and how to use it.
2. A clear starting point.
3. Simple progression through the wizard to enter data.
4. Clear descriptions for user inputs, indicating what type of information is needed, and why.
5. Production of HTML templates conforming to data entered
6. Production of SCORM package of editied HTML templates

Developer requirements

A developer is someone who creates wizards for an end user to run in WCKER, e.g. Sarah in the EarlyUseCases

Primary requirements

1. Straighforward wizard format
2. Clear documentation of how to create a wizard
3. Example wizard to examine, reuse

Secondary requirements

1. A wizard builder application (possibly a WCKER wizard itself)
2. Internationalisation support for informative text