Data-Collection Evidence Template
Use this page to structure the analysis evidence package students build before writing the SRS.
How to use this template
Students should only keep the method sections that actually apply to their project. If they conduct two interviews, they should duplicate the interview section. If they do not use observation, they should delete that section.
Cover Information
| Field | Student entry |
|---|---|
| Project title | |
| Student name | |
| Date | |
| Version |
1. Purpose of This Evidence Package
Write a short paragraph explaining:
- what this document is for
- which data-collection methods were used
- how the evidence will inform the SRS
2. Summary of Methods Used
| Method used | Who or what was involved | Date completed | Why this method was chosen |
|---|---|---|---|
| Interview | |||
| Survey / questionnaire | |||
| Observation | |||
| Report / secondary data |
3. Interview Evidence
Interview 1
Participant role
Example: client, teacher, receptionist, coach, student user.
Date and format
Example: in person, phone call, Teams meeting, written response.
Reason this participant was selected
Explain why this person's perspective matters to the project.
Interview questions
Interview notes or responses
Record the actual notes, key quotes or paraphrased responses.
What this interview tells me
- Possible functional requirements:
- Possible non-functional requirements:
- Possible constraints:
- User needs or frustrations identified:
- Technical environment details identified:
Duplicate this section for each additional interview.
4. Survey or Questionnaire Evidence
Survey details
| Item | Student entry |
|---|---|
| Target respondents | |
| Number of responses | |
| Date distributed | |
| Date closed | |
| Delivery method |
Survey questions
Results summary
Summarise the results clearly. This could be counts, percentages, ranked results, or short themes from open-ended responses.
What this survey tells me
- Possible functional requirements:
- Possible non-functional requirements:
- Possible constraints:
- User preferences identified:
- Common issues or patterns:
5. Observation Evidence
Observation details
| Item | Student entry |
|---|---|
| Process or system observed | |
| Date and location | |
| Who or what was observed | |
| Duration |
Observation focus
State exactly what you were watching for.
Observation notes
Record what actually happened. Focus on workflow, delays, bottlenecks, confusion, repeated tasks, errors, workarounds or missing features.
What this observation tells me
- Problems in the current process:
- User actions that must be supported:
- Constraints or limitations noticed:
- Technical environment details noticed:
6. Report or Secondary Data Evidence
Source details
| Item | Student entry |
|---|---|
| Report or source title | |
| Author or organisation | |
| Date | |
| Where it came from |
Relevant findings or extracts
Record only the parts that are useful to the project.
Why this source is useful
Explain how the source helps identify needs, requirements, constraints or current issues.
What this source tells me
- Possible functional requirements:
- Possible non-functional requirements:
- Possible constraints:
- Relevant facts about the current system or process:
Duplicate this section for each additional report or source.
7. Consolidated Findings for the SRS
Use this section to pull the evidence together before writing the SRS.
Likely functional requirements
-
Likely non-functional requirements
-
Likely constraints
- Economic:
- Legal:
- Social:
- Technical:
Likely scope notes
In scope ideas
-
Out of scope ideas
-
Technical environment notes
- hardware:
- software:
- operating system:
- network or connectivity:
- data sources:
8. Appendix Checklist
- [ ] interview questions included
- [ ] interview notes or responses included
- [ ] survey questions included
- [ ] survey results included
- [ ] observation notes included
- [ ] report or secondary source details included
- [ ] evidence is clearly labelled
- [ ] findings are linked to the SRS