Chapter 7. Data Gathering
3 ways: Interviews, questionnaires, observation
Key Issues: Goals, participants, triangulation, pilot study
Collection methods: notes, audio recording, photograph, video
What I think is the biggest issue is to find a representative amount of people to participate, and enough of them (without fallout). Especially after the pilot study (the people participating there cannot participate in the final study).
Chapter 8. Data analysis, interpretation and presentation
Quantitative analysis problem: might seem like the most scientific approach, but even numbers can be presented in a biased way (like when picking what numbers to present).
Qualitative analysis problem: How to sort and sift through all the data and make sense of it. One solution is to look for critical incidents. But what meaning do they have if they are only “outliers” (not occuring often)?
What are your thoughts on theoretical frameworks? page 303. I feel like the grounded theory-approach sounds pretty natural in a way…
Chapter 10. Establishing requirements
It’s important to find the problems (requirements) early in the development process since that makes it cheaper to fix them.
Functional and non-functional requirements… I didn’t understand the difference? nvm
What is the difference between general data gathering (chapter 7) and data gathering for requirements? Is it about “knowing” what you are looking for? Is the general one more like the grounded theory, you’ll see what you can do with what you find.
Inga kommentarer:
Skicka en kommentar