application , compliances , projects , security

Good Requirements Development Questions

June 21, 2012

Requirements Development

  1. Have you had extensive user involvement in developing the requirements?
  2. Do all stakeholders understand and agree on how the system will be used?
  3. Are all stakeholders satisfied with the requirements?
  4. Do the developers understand the requirements?
  5. Are all requirements clear and unambiguous?
  6. Have you distinguished between needs and wants?
  7. Are requirements relevant?
  8. Are requirements consistent with each other (i.e., they don’t conflict.)
  9. Are requirements complete?
  10. Do the requirements cover everything that is supposed to be accomplished?
  11. Has design detail been left out of the requirements?
  12. Are all requirements testable?
  13. Are requirements verifiable?
  14. Have the requirements been prioritized?
  15. Are requirements feasible with respect to cost, schedule, and technical capability?
  16. Is the system boundary clearly defined; what is in scope, what is not?
  17. Are all external interfaces to the system clearly defined?
  18. Is the specification written so that it can be modified when necessary, with minimal impact to the rest of the document?
  19. Are you conducting formal and informal reviews of requirements documents?
  20. Did you verify your requirements and gain acceptance from your stakeholders ?

Requirements Management

  1. Have all requirements been entered into the requirements repository?
  2. Are the requirements traces sorted to allow requirements lookup by requirement ID, or other useful index?
  3. Can all requirements be traced to original business requirements?
  4. Are all business requirements allocated to lower level, user and functional requirements?
  5. Do you have a requirements change process documented and in place?
  6. Have you identified members of the requirements change board?
  7. Is adequate impact analysis performed for proposed requirements changes?
  8. Do you know who is responsible for making the changes?
  9. Have requirement changes been traced upward and downward through the higher and lower-level specifications?
  10. Do you have a process in place to maintain and control the different versions of the requirements specification?

www.bestitdocuments.com