1) For risk-specific functionality (at least, in financial world), one of the important guidelines is to allow easy viewing of summary level risk as well as easy drill-down to details (e.g. enterprise-wide down to security level)
2) Plus, don't forget standard GUI design guidelines - there's always Nielsen and there's JoelOnSoftware's Joel Spolsky's design book and series of articles. High level,
make sure your controls are intuitive (do what the user expects them to),
minimize the amount of work (eye and hand movements) user needs to do to accomplish most frequent tasks,
Allow easy linking (e.g. no dead ends - if you are displaying a list of securities, make an easy way to jump from security's name to detail screen for that security)
发布评论
评论（1）
1) 对于特定于风险的功能（至少在金融领域），重要的指导原则之一是允许轻松查看摘要级别的风险以及轻松深入到详细信息（例如，企业范围内的安全级别）
2 ) 另外，不要忘记标准 GUI 设计指南 - 总有 Nielsen 和 JoelOnSoftware 的 Joel Spolsky 的设计书和系列文章。
高级别，
确保您的控件直观（执行用户期望的操作），
最大限度地减少工作量（眼睛和手部动作）用户需要完成最频繁的任务，
允许轻松链接（例如，没有死角 - 如果您正在显示证券列表，请采用一种简单的方法从证券名称跳转到该证券的详细信息屏幕）
始终进行可用性测试。
1) For risk-specific functionality (at least, in financial world), one of the important guidelines is to allow easy viewing of summary level risk as well as easy drill-down to details (e.g. enterprise-wide down to security level)
2) Plus, don't forget standard GUI design guidelines - there's always Nielsen and there's JoelOnSoftware's Joel Spolsky's design book and series of articles.
High level,
make sure your controls are intuitive (do what the user expects them to),
minimize the amount of work (eye and hand movements) user needs to do to accomplish most frequent tasks,
Allow easy linking (e.g. no dead ends - if you are displaying a list of securities, make an easy way to jump from security's name to detail screen for that security)
Always always usability-test.