需求规格文档书写规范（ntzhangwb（冰冰）译）

Functional   Specification   Guidelines  
  Tips   for   Addressing   Product   Features   in   Functional   Specifications  
  Here   are   some   questions   the   author   of   a   functional   specification   might   want   to   ask   before   spelling   out   product   feature   specifications   in   a   functional   specification.  
  1.Who   is   the   user   of   this   feature?  
  2.How   does   the   user   approach   the   feature?   How   is   the   user   made   aware   of   the   feature?   Is   the   path   obvious,   intuitive?  
  3.What   motivates   the   user   to   use   this   feature?  
  4.How   does   the   user   get   around   in   the   user   interface   (UI)?   What   is   the   logical   flow   through   the   UI?   Is   the   result   what   users   expect?  
  5.What   happens   if   the   user   is   not   successful   in   completing   the   task   or   using   the   feature?   What   can   he   or   she   do   about   it?   Is   the   next   step   obvious?  
  6.After   implementing   the   feature   (or   completing   a   task),   is   the   user   returned   to   the   appropriate   place   to   continue   working?    
  7.Is   the   exit   from   the   feature   or   procedure   obvious?   Can   the   user   exit   easily   in   the   case   of   accidental   feature   activation?   Can   the   user   back   out   gracefully?  
  8.Is   the   feature   undoable?  
  9.Are   there   other   ways   to   accomplish   the   same   task   or   implement   the   feature?   What   are   they?  
  10.What   does   the   user   need   to   know   to   use   this   feature?   Does   the   feature   require   special   knowledge   you   can’t   expect   the   customer   to   have   (for   example,   what   type   of   printer   driver   is   needed   or   the   type   of   net   card   available)?    
  11.How   many   tasks   must   the   customer   perform   that   have   nothing   to   do   with   the   main   task   (also   known   as   job   1)?   For   example,   does   the   user   need   to   know   the   specific   printer   driver   in   order   to   write   a   resume?  
  12.Is   the   dialog   box/result   consistent   between   multiple   procedures?  
  13.Is   the   same   dialog   used   for   more   than   one   task?   Does   the   dialog   name   or   options/buttons   change   depending   on   the   task?  
  14.Is   the   user   likely   to   combine   the   feature   with   other   features   or   procedures?    
  15.Is   the   feature   or   procedure   consistent   with   other   features   or   procedures   in   the   product   or   in   similar   products?  
  16.Are   other   teams   working   on   corresponding   features   or   procedures?   Are   both   teams   working   consistently?  
  17.Are   any   changes   needed   to   make   the   feature   or   procedure   appropriate   to   a   foreign   market?    
  18.What   will   need   to   be   changed   for   different   languages?  
  19.Will   different   versions   implement   the   feature   differently   in   the   future?  

翻译

 

功能规格指导  
  功能规格中提出产品特点的技巧  
  在写出功能规格中产品特点说明前，功能规格的作者也许要回答以下一些问题：  
  1.谁会使用这一特点?  
  2.用户如何使用该特点?用户如何弄明白该特点?路径是否直接了当?  
  3.什么激发用户使用该特点?  
  4.用户如何在用户界面中操作?用户界面的逻辑顺序是什么?结果是否是用户期望的?  
  5.如果用户不能成功的完成任务或使用该特点会怎样?下一步操作是否明显?  
  6.实施该特点(或完成一个任务)后,用户是否回到合适的地方继续工作?  
  7.该特点或过程的出口是否明显?用户能否从突发情况下很容易的退出?用户是否能友好地回来?  
  8.该特点是否不可行?  
  9.有没有其它方法完成相同的任务或实现该特点?列出其它方法?  
  10.要使用该特点用户需要知道什么?该特点是否需要你不能指望用户会有的特殊知识(比如,需要什么型号的打印机驱动程序或网卡类型)?  
  11.用户必须招待多少与主任务无关的任务(也称为job   1)?比如,用户是否需要知道特定的打印机驱动以写履历?  
  12.对话框或结果在多个过程间是否一致?  
  13.同样的对话框是否用于两个以上的任务?对话框的名字或选项/按钮是否因任务而改变?  
  14.用户是否希望将该特点与其它特点或过程合并?  
  15.该特点或过程是否与本产品或相似产品的其它特点或过程一致?  
  16.其它组是否也在搞相应的特点或过程?两个组的工作一致吗?  
  17.是否需要作出改变以让该特点或过程适用于海外市场?  
  18.对于不同的语言需要改变什么?  
  19.将来不同的版本实现该特点是否不同?