Alex Papsworth (stating he is a Dogsbody doing unpleasant work) actually did a nice post on his Business Analyst Mentor blog on useful techniques you can use alongside Use-Case modeling.
One of the reasons for using other techniques is that different people respond better to other techniques.
Some people prefer the visual approach of storyboards, wireframes, prototypes. Others are happy with the more formal approach of Use Case modeling (which can be done very interactively).
When choosing techniques, it is alway a good idea to keep in mind the reasons for modeling:
Ales states: "When combined, the techniques bring life to the use cases".
I add: "When combined, missing things are easily identified, resulting in better requirements"