能写好代码就能写好需求--------外文文献与译文.doc
约14页DOC格式手机打开展开
能写好代码就能写好需求--------外文文献与译文,writing good requirements is a lot like writing good codeauthor :jim heumann14 jul 2004from the rational edge: by employing many of the same principles and conc...
内容介绍
此文档由会员 wanli1988go 发布
Writing good requirements is a lot like writing good code
author :Jim Heumann
14 Jul 2004
from The Rational Edge: By employing many of the same principles and concepts they already use to write code， developers can effectively serve as requirements engineers. This article reviews those principles and explains how to apply them to create good requirements.
Many software development teams do not have requirements engineers; developers elicit， write， and manage all requirements. This makes sense in terms of resource efficiency: Developers can collect and write requirements during their down time， before serious coding begins. However， the drawback is that programmers are not usually trained in the techniques and tools for writing
能写好代码就能写好需求
作者：Jim Heumann
2005 年 4 月 01 日
来自 Rational Edge：通过应用许多与他们编写代码时相同的原则和概念，开发人员可以有效地担当起需求工程师的职责。本文回顾了这些原则，并解释了如何将其应用于创建好的需求。
许多软件开发团队没有需求工程师；开发人员捕获、编写和管理所有的需求。这在资源效率方面是有意义的：开发人员可以在正式编码之前，在系统停机时间收集和编写需求。然而这一做法的缺点是，通常程序员没有在编写需求方面受过技术和工具的培训，结果他们总是费力和低效地工作，而且有时做出的需求规约不符合规范。
为了写出好的代码，开发人员必须知道很多事情：诸如控制结构和调用约定之类的基本概念；至少一门程序设计语言，包括它的语法和结构；操作系统基础；以及如何使用诸如编译器、调试器、集成环境这类的技术。好在他们能以所有这些知识为跳板
author :Jim Heumann
14 Jul 2004
from The Rational Edge: By employing many of the same principles and concepts they already use to write code， developers can effectively serve as requirements engineers. This article reviews those principles and explains how to apply them to create good requirements.
Many software development teams do not have requirements engineers; developers elicit， write， and manage all requirements. This makes sense in terms of resource efficiency: Developers can collect and write requirements during their down time， before serious coding begins. However， the drawback is that programmers are not usually trained in the techniques and tools for writing
能写好代码就能写好需求
作者：Jim Heumann
2005 年 4 月 01 日
来自 Rational Edge：通过应用许多与他们编写代码时相同的原则和概念，开发人员可以有效地担当起需求工程师的职责。本文回顾了这些原则，并解释了如何将其应用于创建好的需求。
许多软件开发团队没有需求工程师；开发人员捕获、编写和管理所有的需求。这在资源效率方面是有意义的：开发人员可以在正式编码之前，在系统停机时间收集和编写需求。然而这一做法的缺点是，通常程序员没有在编写需求方面受过技术和工具的培训，结果他们总是费力和低效地工作，而且有时做出的需求规约不符合规范。
为了写出好的代码，开发人员必须知道很多事情：诸如控制结构和调用约定之类的基本概念；至少一门程序设计语言，包括它的语法和结构；操作系统基础；以及如何使用诸如编译器、调试器、集成环境这类的技术。好在他们能以所有这些知识为跳板
