Storyboard Scenarios ( 3 : RD : 3 : 3.1 ) ( 3 : TS : 1 : 1.2 )

负责人：User Experience Architect

Overview

Storyboarding augments scenarios and provides user interface details. It is only used when user interface detail plays an important role in satisfying the users. Storyboarding can also align projects across organizations. The storyboard can include a variety of graphical elements including screenshots, application mockups, and screen flow diagrams. It might also include a short narrative describing the persona’s path through the product. A visual depiction of the scenario greatly improves comprehension among users and developers. If storyboards are created for each individual scenario, it is possible to combine them into a high-level product overview.

Entry Criteria

Scenarios
The scenario description is written and attached to the scenario work item.

When:

Scenarios are written.

Sub-Activities


1	Consider Scenarios	Identify the sections of the scenario that warrant a storyboard. Consider how these sections relate to other scenarios already written. Group sections into a single storyboard where applicable.
2	Generate Screenshots	Tools that work well for storyboards include Microsoft Visio and Microsoft PowerPoint. Capture the screens that are presented to the persona. Draw out a rough sketch of the user interface called for in the scenario. Collaborate with members of the development team to ensure the user interface is consistent with the user interface metaphor. Organize screenshots into a coherent presentation. Add short text or voice narrative that describes the user interactions.
3	Create Screen Flow Diagram	Use boxes to represent screens, and arrows to indicate linkage. Upload the storyboard to the project portal and link the storyboard to the scenario work item.

Exit Criteria

Storyboards provide sufficient detail to guide and assist product design work.

我认为这是比较重要的工作，可视化的界面，可以极大的方便用户和开发人员的沟通。只要一个草图估计也不会有下面的情况发生：

好了，按照上面指导的流程，
第一步是综合考虑Scenarios，有哪些部分的Scenarios参与这个Storyboard,考虑它们和已经写好的Scenarios之间的关系，考虑哪些Scenarios写进一个Storyboard。
第二步：Screenshots，对我来说，可以用VISIO画，也可以做一个原形，或者做一些拷屏

第三步：做Screen Flow Diagram。
Screenshots是死的，需要串起来，通过操作串起来就是Screen Flow Diagram了。

转载于:https://www.cnblogs.com/cleo/archive/2006/03/28/360938.html

MSF CMMI系列之 Storyboard Scenarios （Screenshots/Screen Flow Diagram）相关推荐

对话屏幕Dynpro(SE51) 屏幕元素屏幕属性 PAI事件的触发、屏幕元素Function Code设置屏幕流逻辑Screen Flow Logic 对话屏幕中的字段命名大小写问题
对话屏幕Dynpro(SE51) 屏幕元素屏幕属性 l 屏幕序号(Screen number).四个数字组成的序列号,用于在程序中确定屏幕,该序号在同一个ABAP程序内部是唯一的. l 屏幕类型 ...
iOS 9 学习系列：Storyboard References
http://www.cocoachina.com/ios/20150922/13474.html 如果你曾经使用 interface builder 创建过一个复杂.界面非常多的应用,你就会明白最后 ...
uml通信图画法_[UML]UML系列——协作图（通信图）collaboration diagram
系列文章引言用例图.活动图.时序图之间的关系? 时序图与协作图之间的关系共同点:二者都是用对象间的交互来描述用例的. 案例:时序图协作图共同点:时序图与协作图均显示了对象间的交互. 不同点: ...
UML系列——协作图（通信图）collaboration diagram
转自:http://www.cnblogs.com/wolf-sun/p/3411175.html 系列文章 [UML]UML系列--用例图Use Case [UML]UML系列--用例图中的各种关系 ...
机器阅读理解系列文章-BiDAF（Bi-Directional Attention Flow for Machine Comprehension）
0. 简介 BiDAF采用多阶段的.层次化处理,使得可以捕获原文不同粒度的特征.同时使用双向的attention流机制以在without early summarization的情况下获得相关问句和原 ...
MSF for CMMI Process Improvement项目体验: Work Items : Requirement （更新版）
从MSF的角度来看: 需求分类: l Customer Requirement:Scenario, quality of service l Product Requi ...
敏捷开发一千零一问系列之十五：同时实施CMMI和敏捷哪个为主？
问题原来问题是这么写的:"一家企业既要过CMMI,又要过ISO,还要实施敏捷,应该怎样做?" 之所以改成"哪个好",是因为如果要多头并存,就要有主次关系. 那 ...
Linux下screen的应用
在linux系统下,通常我们在执行一些运行时间比较长的任务时,放到后台执行或者使用screen和nohup都是不错的选择,因为任务执行的时间太长了,必须等待它执行完毕,在此期间可不能关掉窗口或者断开连 ...
CMMI资质等级之间的区别是什么？
CMMI是软件工程领域全球最具权威的资质评审与认证标准,作为软件开发领域最佳实践集合,CMMI系列模型已然成为业内提升研发管理及流程能力的公认标准,如果企业能达到CMMI的要求,则成功近在咫尺. CM ...

MSF CMMI系列之 Storyboard Scenarios （Screenshots/Screen Flow Diagram）

Entry Criteria

Sub-Activities

Exit Criteria

MSF CMMI系列之 Storyboard Scenarios （Screenshots/Screen Flow Diagram）相关推荐

最新文章

热门文章