The task of building up storyboards is called storyboarding.
建立故事板脚本的任务称故事板。
Develop the Use Case Realizations and the Use Case Storyboards.
开发用例实现和用例情节串连板。
Remember that storyboards do not have branching or looping logic.
记住故事板没有分支或者循环逻辑。
If so, will storyboards, 3d graphics, or plastic models be used?
如果是的话，要使用情节串连图板、3d图像、还是塑料模型？
You can use a part to populate sketches, screen flows, and storyboards.
你可以利用一个局部来填充示意图，屏幕流，以及故事板。
Identify where other storyboards have been or are planned to be developed.
确定其它计划中的或者开发中的故事板的位置。
This is particularly important if you are planning to do a lot of storyboards.
如果你计划进行大量的故事板，这将会对你非常重要。
A persona is an instance of actor, and it can be associated with multiple storyboards.
一个人物就是一个角色实例，并且他能够与多个故事板联系起来。
They even take our storyboards, the little note we put next to our buns, ” he said.
甚至连面包旁边的牌子都不放过，上面写着一些关于产品的小故事。
Use Case Storyboards provide an additional way of describing the realization of a Use Case.
用例情节串联模板提供了另外一种描述用例实现的方式。
Storyboard: Storyboards present a whole user story by frames that are composed of sketches.
记事板：记事板会为由草图组成的框架呈现了整个的用户情况。
Use Visual Storyboards to describe the scenarios, and validate them with Customer representatives.
使用可视化情节串连板来描述场景，并通过客户代表对他们进行验证。
Movie producers feel the same way about scripts, storyboards, set mockups, and costume designs.
电影制作人对剧本、情节串连板、背景设置以及服装设计的感觉也是如此。
Remember that storyboards are meant to complement your use cases, and are not a replacement for them!
记住故事板就是要补充你的用例，而不是它们的替代者！
Simply put: Visualize what you're trying to say; map it out in storyboards; add some cool visuals.
简单地说：将你想说的视觉化，做出故事大纲的路线图，添加一些酷的视图。
You can use storyboards for interactive requirements and use case review sessions with stakeholders.
你可以利用交互式请求和用例的故事板来回顾与股东利益者的会议。
Personas can be useful for keeping your storyboards focused on a very specific user context and user goal.
人物在使你的故事板集中在一个非常具体的用户背景和用户目标上非常有用。
Visual scenario storyboards — and the relationship between business and user goals — are shown in Figure 5.
可视化的场景情节串连板—以及业务和用户目标之间的关系—如图5中所示。
This can help stakeholders relate to the context of the user interfaces and the context of storyboards.
这可以帮助与用户界面背景和事例板背景有关系的涉众。
Again, you can package Storyboards into a top-level package that you can characterize using the stereotype.
再一次说明，您能够将情节串联图板打包到一个顶层包之中，您可以使用模板来刻画它。
For many types of functionality, especially UI-heavy functionality, once you have these storyboards, you're done.
对于许多类型的功能，尤其是大量的用户界面功能，一旦您拥有这些故事，你就大功告成了。
If the process you are modeling has decisions, you can create different storyboards for each path through the process.
如果您正在建模的流程具有决策，您可以为流程中的每个步骤创建不同的故事板。
There are fundamentally two types of storyboard: requirements discovery storyboards or requirements clarification storyboards.
故事板基本上有两种类型：需求查询故事板或者需求澄清故事板。
The visual storyboards should be validated, focusing the verifications on the correctness of the main design ideas behind the GUI.
可视化情节串连板应该被验证，主要关注于验证GUI背后的主要设计思想的正确性。
For example, have a folder for parts, a folder for sketches, a folder for personas, and a set of folders to group related storyboards.
例如，有一个角色文件夹，一个故事梗概文件夹，一个人物文件夹，以及一套为相关故事板分组的文件夹。
After reviewing the two payment storyboards, a stakeholder proposed a change: "The bookstore should support payment by credit cards."
在评审两个支付记事板之后，涉众可以提出一项变更：“书店应该支持使用信用卡作为支付手段”。
Storyboards have also been proven effective in designing the test cases for the User Interface, as a set of paths through the state machine.
情节串联图板也被证明在设计用于用户接口的测试实例时是有效的。
Remember that this is the frame editor, so everything that you do is part of this storyboard and not available for reuse in other storyboards.
记住这是一个框架编辑器，因此你所做的一切都是这个故事板的一部分，并且在其它故事板中是不能重新利用的。
Use storyboards and "SRC CARDS" (service, Responsibility, Collaboration) for services to create smaller work units and higher throughput.
使用服务的情节串连图板(Storyboard)和“src卡片”(服务(Service)、责任(Responsibility)、协作(Collaboration))来创建更小的工作单元和更高的吞吐量。
Use storyboards and "SRC CARDS" (service, Responsibility, Collaboration) for services to create smaller work units and higher throughput.
使用服务的情节串连图板(Storyboard)和“src卡片”(服务(Service)、责任(Responsibility)、协作(Collaboration))来创建更小的工作单元和更高的吞吐量。
应用推荐