能写好代码就能写好需求--------外文文献与译文.docVIP

外文文献与译文 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 good requirements. As a result they often struggle， work inefficiently， and sometimes produce substandard requirement specifications. To write good code， developers must know many things: basic concepts such as controls structures and calling conventions; at least one programming language， including its syntax and structure; fundamentals about the operating system; and how to use technologies such as compilers， debuggers， and IDEs. The good news is that they can leverage all of this knowledge to write good requirements. By employing many of the same principles and concepts they already use to write code， developers can effectively serve as requirements engineers. Lets look at some of the programming concepts developers can use. Follow a structure All programming languages have a structure. Structure refers to how various parts of a program are defined and how they relate to each other. Java programs are structured with classes， COBOL programs have various divisions， and C programs have a main program with subroutines. Just as programs have a specific structure， so do requirements. Imagine if you were to put all the code you wrote for a C program into the main program -- it would become unreadable and impossible to maintain. Similarly