Leadge.com首页 > 知识库
文章搜索
需求捕获指南(二)—需求捕获的问题及过程
2007-7-3 9:29:17  作者:网友推荐
  
  需求工程包括的活动有需求捕获,需求定义和需求验证。

  The hardest single part of building a software system is deciding what to build… … No other part of the work so cripples the resulting system, if done wrong. No other part is more difficult to rectify later.

  开发软件系统最艰难的部分在于确定要开发什么。而这一部分又最可能导致系统的失败,最难以在后继的工作中加以矫正。

  Issues involved in this problem area include:1. Achieving requirements completeness without unnecessarily constraining the system design 2. Analysis and validation difficulty 3 Changing requirements over time

  在需求的问题上有这样一些观点:

  1、到达需求的完整性会束缚系统设计。

  2、需求分析和验证比较困难。

  3、改变需求会消耗额外的时间。

  Many requirements errors are passed undetected to the later stages of the life cycle and correcting those errors during or after implementation phase is found to be extremely costly.

  许多未被发现的需求错误被传递到生命周期的后继阶段,在后继阶段更正这些错误将花费更多。

  Problems of RE can be grouped into three categories:。 Problems of scope, in which requirements may address too little or too much information。 Problems of understanding o Users have incomplete understanding of their needs o Analysts have poor knowledge of problem domain o Ease of omitting “obvious” information o Conflicting views of different users o Vague and un-testable requirements e.g. “user friendly” & “robust”

此文章共有5页  上一页 1 2 3 4 5 下一页

文章来源:中国项目管理资源网

软件开发项目管理培训课程方案


发表评论    【推荐】 【打印
我来评两句 查看最新评论〗 
请您注意:
·遵守中华人民共和国的各项有关法律法规
·承担一切因您的行为而导致的法律责任
·本网留言板管理人员有权删除其管辖留言内容
·您在本网的留言,本网有权在网站内转载或引用
·参与本留言即表明您已经阅读并接受上述条款
昵称: 匿名
图片广告
热点文章
论坛精贴