能寫好代碼就能寫好需求--------外文文獻(xiàn)與譯文.doc
約14頁DOC格式手機(jī)打開展開
能寫好代碼就能寫好需求--------外文文獻(xiàn)與譯文,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...
內(nèi)容介紹
此文檔由會員 wanli1988go 發(fā)布
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：通過應(yīng)用許多與他們編寫代碼時相同的原則和概念，開發(fā)人員可以有效地?fù)?dān)當(dāng)起需求工程師的職責(zé)。本文回顧了這些原則，并解釋了如何將其應(yīng)用于創(chuàng)建好的需求。
許多軟件開發(fā)團(tuán)隊(duì)沒有需求工程師；開發(fā)人員捕獲、編寫和管理所有的需求。這在資源效率方面是有意義的：開發(fā)人員可以在正式編碼之前，在系統(tǒng)停機(jī)時間收集和編寫需求。然而這一做法的缺點(diǎn)是，通常程序員沒有在編寫需求方面受過技術(shù)和工具的培訓(xùn)，結(jié)果他們總是費(fèi)力和低效地工作，而且有時做出的需求規(guī)約不符合規(guī)范。
為了寫出好的代碼，開發(fā)人員必須知道很多事情：諸如控制結(jié)構(gòu)和調(diào)用約定之類的基本概念；至少一門程序設(shè)計(jì)語言，包括它的語法和結(jié)構(gòu)；操作系統(tǒng)基礎(chǔ)；以及如何使用諸如編譯器、調(diào)試器、集成環(huán)境這類的技術(shù)。好在他們能以所有這些知識為跳板
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：通過應(yīng)用許多與他們編寫代碼時相同的原則和概念，開發(fā)人員可以有效地?fù)?dān)當(dāng)起需求工程師的職責(zé)。本文回顧了這些原則，并解釋了如何將其應(yīng)用于創(chuàng)建好的需求。
許多軟件開發(fā)團(tuán)隊(duì)沒有需求工程師；開發(fā)人員捕獲、編寫和管理所有的需求。這在資源效率方面是有意義的：開發(fā)人員可以在正式編碼之前，在系統(tǒng)停機(jī)時間收集和編寫需求。然而這一做法的缺點(diǎn)是，通常程序員沒有在編寫需求方面受過技術(shù)和工具的培訓(xùn)，結(jié)果他們總是費(fèi)力和低效地工作，而且有時做出的需求規(guī)約不符合規(guī)范。
為了寫出好的代碼，開發(fā)人員必須知道很多事情：諸如控制結(jié)構(gòu)和調(diào)用約定之類的基本概念；至少一門程序設(shè)計(jì)語言，包括它的語法和結(jié)構(gòu)；操作系統(tǒng)基礎(chǔ)；以及如何使用諸如編譯器、調(diào)試器、集成環(huán)境這類的技術(shù)。好在他們能以所有這些知識為跳板
