It is highly likely that a wide variety of test protocols will be necessary to fully certify software as operational prior to release, and protocols will have to be extended as features of software change.

Key Protocol Components:

Documentation

Procedure to Follow

Software Version

Software Features Modified Since Last Test

PC Hardware Configuration

PC OS Configuration

Test input (e.g. user commands, STL files, etc.)

Test output (e.g. user experience, software behavior, sliced model, paths, etc.)

Reference output (e.g.expected software behavior, ideal sliced model or best prior result, etc.)

Metrics/tools for comparison of test output to reference output

Draft Protocols