We've done our use cases and a state machine diagram, so now let's move on to the next step, which is to create our storyboards. We are going to decompose our use cases further in order to understand the various tasks our robot must undertake on our behalf in the course of its two missions. I've created some quick little drawings to illustrate each point.
The concept of storyboards is borrowed from the movie industry, where a comic-strip like narration is used to translate words on a page in the script into a series of pictures or cartoons that convey additional information not found in the script, such as framing, context, movement, props, sets, and camera moves. The practice of storyboarding goes all the way back to silent movies, and is still used today.
We can use storyboards in robotics design for the same reasons: to convey additional information...
