2009年3月12日 星期四

軟體需求定義與管理-Checklist from borland

  1. Who owns or is responsible for this requirement?
  2. What business or user justification is there for this?
  3. Where is the meaningful discussion for this requirement documented?
  4. What is its status, priority and feasibility assessment?
  5. Where is the validation procedure for this requirement?
  6. Where does this requirement trace to and from enabling quick and
  7. Has this requirement changed? If so, who changed it, when was it changed, what was changed and why was it changed? How were people notified?
  8. accurate requirement change management?
exercise:
FR3.2.2.1.5 The system shall be able to identify allocated COTS licenses that will expire within 60 and 120 days. The system shall provide the capability to generate an Expiring License Summary Report that will include a list of the COTS licenses, or associated maintenance agreements, by project/user organization, that will expire in the selected timeframe (either <=60 days, or <=120 days). The list will include the product version/revision, vendor, platform, license expiration date, maintenance agreement expiration date and Point-of-Contact information (name, phone, organization, address, etc.)

沒有留言: