MSF CMMI系列之 Storyboard Scenarios (Screenshots/Screen Flow Diagram) 无为而为


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/p/360938.html