Discussion Questions Chapter 4.5-4-6

  1. How is can completeness be checked?

  2. What techniques can be used to check the realism of requirements?

  3. Are there any tools we can use for our projects that would help with requirements storage and traceability management?

  4. How do you handle realizing the changes that need to be made would be too costly, either of time or money?

  5. What software tools should we be looking to use to keep a check on our requirements and possible changes that may arise within them?

  6. How do you deal with a client that repeatedly changes the requirements on you?

  7. How often should the requirements document be reviewed with the stakeholder?

  8. How do requirements engineers know how much time and money different requirements are going to cost?

  9. “Agile development processes have been designed to cope with requirements that change during the development process. In these processes, when a user proposes a requirements change, this change does not go through a formal change management process.” Who is the “user”?
  10. How much does tool support cost in the requirements engineering process?

  11. What kind of requirements management plans are used in the waterfall processing models?

  12. Obviously, time is the most stringent budgetary constraint in the context of our projects. Do you have any tips on approaching time management in a group project setting?

  13. What might you say to a stakeholder who is demanding two contradictory system features?

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2018-02-05 - JimSkon
  • Edit
  • Attach
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback