| Sketch Recognition in Software Design (2008) | |||||||||||||||
Abstract | |||||||||||||||
| The Problem: Sketching is a natural and integral part of software design. Software developers use sketching to aid in the brainstorming of ideas, visualizing programming organization, and understanding of requirements. Unfortunately, when it comes to coding the system, the drawings are left behind. We see sketch recognition as a way to bridge that gap. In addition to the vast amount of information given by a sketch, a plethora of other design information may be voiced during a software design meeting. We can capture the spoken and visual software design meeting information by videotaping the meeting and any white-boards used. By indexing these videos, we make it easy to retrieve the videotaped information without watching the entire video from start to finish. Motivation: We want to allow software design meetings to continue as they are, with software designers discussing the design and drawing free-hand sketches of these designs on a white-board. Using our system, designers can sketch naturally, as we place few requirements on the sketcher. We recognize and interpret these diagrams using sketch recognition. Because the diagrams are interpreted, we provide natural editing capabilities to the designers, allowing the users to edit their original strokes in an intuitive way. For instance, the designer can drag their drawn class from the center and move all | |||||||||||||||
Publication details | |||||||||||||||
| |||||||||||||||