Tags: %TAGME{ tpaction="" web="Main" tag="" }% view all tags

Discussion Question

Chapter 4 - Requirements Engineering

  1. What specific aspects of the work culture/ethic are important in ethnography?
  2. Are there any other disadvantages to ethnography other than that it is not very conducive to innovation?
  3. How does one evaluate if requirements are complete?
  4. How does one encourage a stakeholder to describe a scenario/use case in a sufficient level of detail?
  5. What do you do when a client is using a lot of domain jargon and you do not understand what they are saying?
  6. Can we elaborate on the ethnography section? Is the ethnographer a member of the team that joins and contributes their findings towards the developing project?
  7. How can we build optimal systems when most stakeholders donít know what they really want?
  8. During requirements validation, in the verifiability portion, how could requirements ďbe checked?Ē
  9. How can you ensure that large systems which have diverse user communities have optimal final system requirements?
  10. What is a good way to get the goals of your system across to a system developer?
  11. As a software developer, how can you gauge how much your client knows about system engineering?
  12. Do customers write both the user requirement and the detailed system requirement?
  13. When a system has multiple stakeholders, who decides what the general user requirements are?
  14. Who does the interviewing in the RE process? Are the developers themselves involved or do they have co-workers to do this for them?
  15. In requirements elicitation, should all kinds of stakeholders (end users, system managers, system owner, external stakeholders) participate in all stages (requirements discovery, requirements classification and organization, requirements prioritization and negotiation, requirements specification)?
  16. Who are external stakeholders and to what extent do they participate in each requirements elicitation stages?
  17. What kinds of requirements can be verified using test-case generation techniques?
  18. What are some examples that the people who pay for a system and the users of that system are not the same people?
  19. Is there a best way to manage change best for the relatively small projects we are given?
  20. Many of the techniques in this book are so far combinations of other techniques. How much ambiguity is there in the way a team should engineer software to be most efficient?
  21. Is requirement elicitation feasible for projects that are completely innovative?
  22. If different stakeholders have different or conflicting requirements, how do you choose between them?
  23. How do businesses manage one party wanting to change requirements after a contract has been agreed to?
  24. On different sized projects, how many people are involved in requirements development?
  25. How would the ethnographic technique actually work in practice?
  26. I donít fully understand traceability policies. How is it different from a requirements document? Also, what tools can manage traceability and how?
  27. How often do stakeholders and system developers have to meet to discuss and specify requirements and to minimize misinterpretations? How long does the requirements validations stage take in relation to the requirements validation and elicitation stages?

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