Balance Cube is a set of software sensors, monitors, and reporting tools for developing simulations without wasting time or computing resources on components that may be little used by users. The addition of Balance Cube to the development process allows every simulation item or code segment to be monitored during run-time. Discover exactly what parts of your software are really used during testing. With this information incorporated into development, effort goes exactly where it will benefit end users, not into code that is rarely invoked.

Simulations designed with this essential knowledge available before launch can help reduce your costs since code that users choose to ignore or happen not to see is removed. Code that is frequently triggered by users can be improved to enhance the user experience further. For the first time, cost and benefit of development can be measured by the ultimate arbiter - the user community.

Key goals in Balance Cube design:

• Monitor: Find out what parts of your simulation are most used by users based on concrete, quantitative data on screen time and CPU time.
• Report: Determine the most and least used parts of your simulation during development, helping with truly appropriate resource allocation.
• Balance: Assign resources to the right parts of the simulation, balancing developer resources to the right quantifiable, justifiable user benefit.
• Performance: Learn where your optimization efforts are best spent in order to maximize the accuracy or enjoyment as seen by users, not based on opinion. Code that is highly used is optimized to improve performance, putting an end to spending time on underused code.