|
Interaktive Software-Demos werden immer häufiger Bestandteil Technischer Online-Dokumentation. Was sollten Sie bei der Auswahl eines Werkzeuges zur Erstellung solcher Demos beachten?
Die folgende Checkliste kann Ihnen helfen das Tool zu finden, das sich mit Ihren individuellen Anforderungen am besten deckt.
Tipp:
Eine Liste empfehlenswerter Programme finden Sie unter dem Thema Software Demo Tools.
 Beitrag in englischer Sprache
Dieser Beitrag richtet sich an ein internationales Publikum und ist ausschließlich in englischer Sprache verfügbar. Er ist jedoch so geschrieben, dass er auch für Nicht-Muttersprachler einfach zu verstehen ist. Bitte lesen Sie weiter...
When you evaluate tools to create software demos, it is important to understand that there are two general groups of tools:
| ▪ | The group of frame-based tools creates animations based on a few static images ("frames" or "slides"). A new frame or slide is only created when something new actually took place in the software (when a new window opened, for example). The mouse cursor will not be visible on the frames. Movements of the mouse and user inputs will be simulated separately by the tool. |
| ▪ | The group of full-motion-based tools records a "genuine" movie. It generates about 30 frames per second, regardless of what is actually happening on the screen. Usually, the mouse cursor will be visible on all of these frames. |
Both groups have specific advantages and disadvantages. Frame-based tools are pushed to their limits when it comes to recording dynamic processes. Example: Imagine that you wish to record how you draw a shape in a drawing program with the paintbrush tool. In this case, you are most likely to have just the start (empty workspace) and the end (finished shape) in your movie, as most frame-based tools only create a new frame when the mouse button is pressed or released. The images for the steps in between (dragging operation with the mouse) will be missing and cannot be interpolated later on.
The big advantage of frame-based recordings, however, is the fact that significantly fewer, individual images are created. This makes the subsequent post-processing considerably simpler, and even makes it possible to replace individual frames later on, without having to record the entire movie all over again. Also, the cursor paths can be changed subsequently. This is an advantage that can hardly be underestimated, because it is rarely that a recording turns out to be perfect at the first attempt. While recording a full motion movie, the person guiding the operations must be careful all the time to move the cursor in smooth movements, without covering any of the important contents on screen at the same time. Thus, the visual impression achieved will depend clearly on the skills of the person creating the recording.
The trend goes to combine the best of the two worlds: In the standard case, the recordings will be frame based, but when there is a drag & drop action (or upon manual request), a full-motion based recording begins.
|
Recording
| ▪ | which recording methods are possible? Frame-based recording, full-motion based recordings, or both? |
| ▪ | Can you create demos also based on imported, static screenshots? This is especially helpful when the software is still under development. |
| ▪ | Can you import externally created videos as well? This will be important if, in addition to the interaction with the software, you also wish to show what is to be done with some specific hardware. |
Editing
| ▪ | What objects such as texts or arrows can you insert? |
| ▪ | Can you create formatting templates and change the design of callouts, arrows, etc.? |
| ▪ | How extensive are the animation options? |
| ▪ | Can you incorporate interactive buttons and stop points into the demo, to prevent the demo from running too fast for viewers who are slow readers? |
| ▪ | Can you add a quiz to test whatever has been learnt? |
| ▪ | Can you port the results of a quiz to a learning management system (LMS)? |
| ▪ | How precisely and how easily can you control the timing of individual objects? |
| ▪ | How well and at what level can you insert and edit audio files? |
Output
| ▪ | What output formats are supported? |
| ▪ | Can you customize the appearance of the viewer? |
| ▪ | Is it possible to add a navigation menu, so that viewers can jump from one scene to another? |
User-friendliness
When a product undergoes changes, all that needs to be done in the case of text-based documentation is to modify the texts and maybe to replace some individual images. In the case of multimedia contents, this becomes several times more time-consuming: If the crucial spots cannot be edited later on, you will have to recreate entire scenes, including the timing, animation and interaction. Therefore, in case of multimedia content the question of how easily existing content can be changed is even more important than with conventional documentation.
| ▪ | Can you delete or add individual sequences? What happens to the mouse cursor in this case? Is it possible to achieve a seamless integration with the preceding scene? |
| ▪ | Is it possible to replace individual screenshots? |
| ▪ | Is it possible to edit the mouse paths? |
| ▪ | Is it possible to make changes later on to the design, for example to all arrows or callouts that have been inserted, and to unify them? |
Translation process
| ▪ | Here again it is important: Is it possible to replace individual screenshots? |
| ▪ | Is it possible to replace the audio as well? |
| ▪ | Can you export the text contained as a file (preferably XML), translate it externally, and then re-import it back after translation? |
| ▪ | Is the software Unicode-compatible, if required? |
Usability
Finally of course, it is also crucial how easy you find it to work with the software. Only if you really feel comfortable with the software, you will be able to produce top-quality results.
| ▪ | Is there a good documentation? |
| ▪ | Do you need long training, or can you get started immediately? |
| ▪ | What is you personal preference? |
|
