Page 284 - Software and Systems Requirements Engineering in Practice

ç ç 3 O F T W A R E ç ç 3 Y S T E M S ç 2 E Q U I R E M E N T S ç % N G I N E E R I N G ç ) N ç 0 R A C T I C E

3TORYBOARDING
7E DEFINE A PROTOTYPE AS ANY ARTIFACT THAT UNAMBIGUOUSLY REPRESENTS
A CERTAIN ASPECT OF A SYSTEM WITH SUFFICIENT DETAIL TO DRAW MEANINGFUL
CONCLUSIONS OR TO MAKE DECISIONS 7E DON T NECESSARILY HAVE TO
DEVELOP EXECUTABLE SOFTWARE TO PROTOTYPE AN ASPECT OF A SYSTEM 7E
CAN USE A NUMBER OF LOWER COST INTUITIVE TECHNIQUES THAT GIVE VERY
GOOD RESULTS FOR THEIR RESPECTIVE DOMAINS &OR EXAMPLE WE OFTEN USE
STORYBOARDS TO ILLUSTRATE THE SPECIFIC INTERACTION SEQUENCES FOR A
SYSTEM
3TORYBOARDS ARE A VISUAL AND TEXTUAL MEDIUM THAT ALLOWS MULTIPLE
STAKEHOLDERS TO PRODUCE MODIFY AND COMMENT ON THE CONTENT AND
THUS FOSTER RAPID COMMUNICATION AND EVOLUTION OF COMMON
UNDERSTANDING AS WELL AS THE IDENTIFICATION OF POSSIBLE CONFLICTING
AREAS 3TORYBOARDS CAN BE USED FOR HIGH LEVEL MODELING OF USER STORIES
OVER MULTIPLE EVENTS INTERACTIONS AND THEY CAN ALSO BE USED TO MODEL
THE LOW LEVEL USER INTERFACE 5) INTERACTIONS THAT OCCUR FOR A SPECIFIC
APPLICATION OR EVEN ONE OF ITS USER SCREENS 4HE CHOICE OF THE LEVEL OF
REPRESENTATION IS DRIVEN BY THE STAKEHOLDERS AND BY WHAT NEEDS TO BE
MODELED FOR THE EVALUATION 7E HAVE FOUND THAT 0OWER0OINT OFTEN
PROVIDES THE RIGHT LEVEL OF FIDELITY TO REPRESENT THE 5) AND WORKFLOW
COMBINED WITH EASE OF ANNOTATION AND USAGE BY ALL STAKEHOLDERS
3TORYBOARDS ARE EASY TO CREATE IN MOST COMMONLY USED PRESENTATION
EDITING TOOLS BUT 793)79' DOCUMENT EDITORS WORK AS WELL 7E
HAVE MOSTLY USED 0OWER0OINT BUT 6ISIO WAS ALSO SUCCESSFULLY USED
FOR THIS PURPOSE !N EXAMPLE STORYBOARD IS GIVEN IN &IGURE
ILLUSTRATING SIMPLE VISUAL AND TEXTUAL ENTRY SCENARIO SEQUENCE USAGE
OF CAPTURED IMAGES AND DIRECT ANNOTATION
)N ADDITION TO VISUAL SEQUENCES AND TEXT COMMENTS ABOUT THE
CONTENT OF SPECIFIC SLIDES STORYBOARDS CAN BE EXPANDED TO INCLUDE

1, ʙ°ÎÊ Ý>“«iÊÃ̜ÀÞLœ>À`