One of the questions I get on a regular basis is "What's the difference?" What they are asking is what's the difference between your SHO Technology and Simulation. Well the answer I usually give is that simulation is just that, simulation... and SHO walkes the user through the steps within the live application.
Now, I have seen it a thousand times, and once you see it "record and playback" (yes, I think we may need to change our terminology) you will fully understand the difference but until then, here's the scoop.
SHO: User is guided while working inside the actual software application by performing real interactions with the software application instead of simulated interaction.
Simulation: User works in a separate simulation window and must figure out how to apply what was done in the simulation window to the actual software application. The learning environment is disconnected from actual software application.
SHO: User creates real data during the learning or guidance process.
Simulation: User does not create real data during the learning process. Any "data" created in the simulation window is lost once the simulation ends.
SHO: Does not rely on video, animation or screen capture, so visual presentations are dynamic and can adjust to the current appearance and position of the software application and its interface components (toolbars, dialog boxes, etc).
Simulation: Creates static visual presentations of software interfaces that do not adjust to user-defined configurations (toolbar and dialog box placement, interface settings, etc.).
SHO: Majority of content remains viable across new versions of the software application, resulting in longer content shelf life.
Simulation: Visual presentation must be updated with each new version of the software application.
SHO: Reduces bandwidth requirements for remote content.
Simulation: Heavier bandwidth requirements for remote content.
SHO: Visual presentation is language neutral to allow for easy localization.
Simulation: Visual presentation is static and language specific and must be recaptured for other languages.
SHO: Provides intelligent verification of how the user is using the software inside the actual software application.
Simulation: Verifies user interactions with the simulation window only.
SHO: Eliminates the need to switch back and forth between the software application and a training or simulation window.
Simulation: User must switch back and forth between the software application and the simulation window.
SHO: Eliminates the need to resize windows in order to display a separate simulation window.
Simulation: User must adjust window sizes to display both the actual software application and the simulation window.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment