图形用户界面规范模板 [英] Graphical User Interface Specification Template

问题描述

在我的工作中，我们在功能规范和技术设计文档中都提供了图形用户界面设计的一些元素。但是，近100％的时间我们正在修改现有的软件，这通常很容易。

如果要为新的软件项目生成用于GUI规范的单独文档，该怎么办？我有一个软件可以帮助我简单的线框，但文档模板大纲是什么样的。你有什么用于模板或大纲？

解决方案

几年前，我是一个非常好的组合的一部分UI规范流程。我们创建了一个文档，其中包含：

1. 整个UI隐喻的概述（例如页面和文件夹，名片）


2. 提出的UI元素（例如帮助按钮，包括图标，下拉列表中使用的样式等）。这些都支持隐喻。


3. 对话框的间距和对齐标准的规格（全部有8个像素或边框，列表框下方的按钮总是x像素等）。 >
   
4. 字体规格（我们是一个非常风格独特的项目）


5. 我们提供了如何提供帮助的规范，但这是一个不寻常的
6. 
   
7. 纳入UI元素的候选屏幕模型，并展示了隐喻。

UI文档不是捕获每个屏幕和每个对话。然而，它必须有足够的信息，有人审查规范将获得一个非常清楚的应用程序的外观和感觉的想法。我们也花了一些时间来解决关键的对话框或隐喻特别重要的对话框。

最后一件事，当我们做了规范时，我们使用了一个平面设计组实际上创建了几个初始候选版本。在团队成员投票通过候选人之后，我们获得了更多的优胜者，并将其更详细地阐述。

At my job we put some elements of the design for graphical user interface in both the functional specification and the technical design documents. However, this is often easy as nearly 100% of the time we are making modifications to existing software.

What would one do if they wanted to produce a separate document for GUI specification that was for a new software project? I have software that can help me with simple wire frames, but what would a document template outline look like. What do you use for a template or outline?

解决方案

I was part of a group a few years back that had a very good UI specification process. We created a document that contained:

1. An overview of the overall UI metaphor (e.g."Page and Folder", "Business Card")
2. Proposed UI elements (e.g. the help buttons including the icons, the styling to be used on pull-down lists, etc.). These all supported the metaphor.
3. Specifications for spacing and justification standards for dialogs (all had 8 pixels or border, buttons below list boxes were always x pixels away, etc.).
4. Font specifications (ours was to be a very stylistically unique project)
5. We included specs on how to provide 'Help' but this was a bit unusual
6. Candidate screen mock-ups that incorporated the UI elements and that demonstrated the metaphor.

UI documentation is not meant to capture every screen and every dialog. However, it must have enough information that someone reviewing the spec would gain a very clear idea of the look and feel of the application. We also took some pains to spell out key dialogs or those where the metaphor was particularly important.

One last thing, when we did the specification, we worked with a graphic design group that actually created several initial, candidate versions. After the team members voted on the candidates, we took the winner and fleshed it out in much more detail.

这篇关于图形用户界面规范模板的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！