如何撰写一个软件可用性分析报告

1.3.3 How to Write a Usability Aspect Report (UAR)

我将以SSD04的课程为蓝图，来简单讲讲软件可用性分析报告的书写方式。按照软件工程的思想，我们需要将软件开发的点点滴滴以文档的形式保存和传递。

• Usability Aspect Reports
• The Elements of a UAR Report
  • UAR Identifier
  • Succinct Description of the Usability Aspect
  • Evidence for the Aspect
  • Explanation of the Aspect
  • Severity of the Problem or Benefit of the Good Feature
  • Possible Solutions and Potential Trade-Offs
  • Relationship to Other Usability Aspects
• IMPORTANT: Always Step Back and Try to See the Bigger Picture!

Usability Aspect Reports

As you examine an interface with the techniques this course will teach you, you will find aspects of the interface that are problems for users (which you will want to fix in the next version) and aspects that are very helpful to users (which you will want to preserve in the next version). Writing a clear, useful report of these aspects (called a usability aspect report or UAR ) will help to make that next version more usable. In the real world, you will write these reports for other members of your development team who have not seen the usability issue; therefore, your reports must be clear and complete. Even when you are writing these UARs just for yourself, clarity and completeness will help you understand each report six months after you write it, when you finally get around to implementing the changes it suggests.

软件分析报告主要涵盖涉及软件两方面的内容：用户使用中的问题 （用以在下一个版本中指导软件开发者去修补），将对用户使用起到帮助的设计 （用以指导下一个版本的软件升级）。如果我们能够写出一个简单明了且全面的软件可用性报告，将对软件后续的衍生升级起到更大的帮助。在书写这样一份报告时，我们仍然需要遵循良好的书写规范以保证报告的真实、明了、准确 为后续开发维护和升级提供良好的备案支持。我个人在经历了一些开发后也深有感触，我同样支持“文档很重要 ”的论点。软件开发实际上就是将大家平时反复的工作以软件的方式来模拟，开发过程的前前后后涉及到各种工作人员，保证软件质量的唯一办法就是让每一个参与者尽量多的有全局感，能够把握整个体系结构，那么如何保证这种“信息传递的热度 ”呢？强大的文档支持。这种方式其实也适用于敏捷开发，合适的文档规模对敏捷开发也是有巨大好处的。

 

 The Elements of a UAR Report

We advocate a standard form for the report so you remember to include specific pieces of information for each usability aspect. The UAR should include the following slots:

• UAR Identifier