追求项目梦想

2006/7/12 11:28:25 | 6106次阅读 | 来源：网友转载【已有0条评论】发表评论

?
·一项功能完成后,是否需要用户给出注释文字?
·需要同其它软件连接的接口吗?
·用户有什么样的保密要求?
·需不需要系统管理员部门管理员?或者用户自我登记自己管理?
·需不需要系统日期及时间,及上一次的更改日期?
·需不需要系统使用情况的报告以及工作结果的汇总报告?
·报告中的每一个数据是否都需要同源数据建立连接?计算结果是怎样的?
·每一个页面都有什么样的习惯性要求?站点的每一页的每个区域所附带的业务规则是什么？
·当你敲击”Enter”键时,电脑进入下一个新功能区还是显示一系列选择项?
·区域属性：区域长度，角度或文字数字的定义是有要求的或没要求的还是有确定要求的？

这些用户的期望必须反映到系统要求中去,并最终变成编码形成软件.
精确地严格按照正确的顺序来描述你的工作是非常困难的,也是不可能的.如果你的开发组能够紧跟用户要求,把这项工作当作自己工作的一部分,他们就将得到非常精确的客户对该软件的愿望.记录下所定义的客户要求,将他提供给你的开发团队,并随时准备回答他们向你提出的任何问题.如果这一步成功了,就意味作你将有一个成功的首次演示.尽管收集客户需求需要费些时间,但如果能够帮助准确理解客户需求, 那么它最终将帮你节省时间,还帮助你开发出一个让客户满意的用户软件,你所进行的工作也将是更加高效的工作.

原文：
　　　　　　　　　Keep Dreaming
Donna Boyette March 26, 2001

How would you like to hear this from a customer: “We want the application as quickly as possible, but I know we’ll have to invest some serious time in the requirements stage before we’ll know how much time your team will need to develop it. Don’t worry about how long it takes to get a complete set of requirements. We’re ready to work with you. And we ordered pizza for everyone!”
Hey, wake up! Stop dreaming…it will never happen. But you could come close. If you want your next project you to be more successful than the last project, use these hints and the user-requirements explanation at the end of this article to motivate your users to be intimately involved during this stage of the project.
Instead of bemoaning the fact that gathering requirements is as much fun as exploratory surgery, start with the best in mind and see how close you can get. If you could dream up the ideal scenario for gathering requirements, it might go something like this.
Dream Scenario:
Joe used to be a user in the group for which your team is designing a new application. He was then p