研究生需求分析re21.pptxVIP

Chapter 13:Storyboarding ObjectivesTo introduce and understand storyboarding technique for requirements elicitation.StoryboardA Storyboard is a logical and conceptual description of system functionality for a specific scenario, including the interaction required between the system users and the system. A Storyboard tells a specific story.?Benefits of StoryboardsA storyboard serves multiple purposes– helps understand how requirements impact implementation and test– describes how a system or part of a system is intended to work “before the fact”– documents system functionalityCommunicate and verify functionality with relevant stakeholders– often not technical or programming savvyBenefits of Storyboards (cont.)Conversely, storyboards can be used to document legacy code– convey how a system actually works “after the fact” (at a higher level than code)GUI storyboards help business users to identify issues and gaps early, minimizing the cost of rework. Generating UI specs, functional specs and detailed test scripts saves hundreds of man hours. Benefits of Storyboards (cont.)Because storyboards exist independently of the software system they describe, they have many advantages over regular prototypes. They cannot crash, very easy to share with large groups, do not give the false impression that the system is already developed. feedback is easier to modate.Storyboards, like HCIs and GUIs, communicate design notions more clearly to users than use cases alone can Limitationsone of the biggest problems with storyboards is that they can e outdated very quickly. User interfaces originally defined often change over time, and that creates a maintenance burden.StoryboardingStoryboarding describes highlevel system functionalityProvides a logical model that is common to implementation and test modelsTypically expressed in the form of activity diagrams– to show workflow or performed actions– may be partitioned to show control flow between different classesUsually tied to us