Useful animations do not require very sophisticated software. A screen allowing the user to scroll through business scenarios displaying the scenario stage instructions and the system behaviour is very effective. If the user can approve or reject the behaviour, or make other comments, even better. The process of deriving behaviours from requirements documents is fairly mechanical. Section by section the document is scanned for functions, conditions and responses and lists are made of each.
Every item listed is referenced to a requirements sentence.
For every function each condition identified is considered. These are added to the table of behaviours. Conditions identified in requirements most often represent equivalence partitions - the analyst can add others if they seem appropriate and so provide more explicit definitions of behaviours for the user to verify. The process of deriving behaviours from a requirements document is an excellent inspection method. The analyst will tabulate the behaviours and as a result, missing and inconsistent responses usually stand out.