- ✓A research report for a computing project typically includes an introduction, literature review, methodology, findings, discussion, and conclusion.
- ✓The abstract is one of the most important sections of a research report because it is often the first and only part that many readers will read.
- ✓Findings should be presented objectively before being interpreted in the discussion section, where you engage with existing literature and theoretical frameworks.
- ✓Practical artefacts such as software prototypes, system designs, or datasets should be accompanied by clear documentation of their development and limitations.
- ✓Honesty about the limitations of your research demonstrates maturity and strengthens rather than weakens the credibility of your work.
Listen to the full episode inside the course. Enrol to access all 80 episodes, plus assignments, tutor support and Student Finance funding.
Start learning →Alex: Today we're looking at how to communicate research outcomes effectively. Sam, you've done the research; now how do you tell the world what you found?
Sam: The output of a research project takes several forms depending on the audience and purpose. For an academic audience, it's typically a written report or dissertation. For a professional audience, it might be a technical report, a presentation, or a practical artefact like a software prototype or a system design. In many cases, it's several of these things. Each format has its own conventions and expectations.
Alex: Let's start with the written report. What's the standard structure?
Sam: For a computing research project at Level 5, the report typically follows academic conventions. An abstract provides a summary of the entire report in 200 to 300 words: the research question, the methodology, the key findings, and the conclusions. This is often written last but appears first, and many readers will only read it. The introduction sets the context, explains why the research is important, and states the research questions and objectives.
Alex: And the middle sections?
Sam: The literature review surveys the existing knowledge in the area, identifying what is known, where the gaps are, and how your research addresses them. The methodology section describes and justifies your research design and data collection and analysis methods. The findings section presents what you found, without interpretation; this is just the data. Then the discussion interprets the findings in the context of the literature and your research questions, drawing out what they mean and why they matter.
Alex: What about the conclusion?
Sam: The conclusion summarises the key findings and draws together the answers to your research questions. It typically also includes recommendations, either for practice or for future research, and an acknowledgement of the limitations of your study. The conclusion should flow naturally from everything that preceded it; it shouldn't introduce new information or arguments.
Alex: What about presenting research verbally?
Sam: A research presentation needs to be even more selective than a written report, because you have far less time and space. Focus on the most important findings and the clearest evidence. Use visuals to illustrate rather than text to explain. Leave time for questions, which are often where the most valuable conversations happen. And be clear about what your findings mean and what you think should happen as a result.
Alex: What about artefacts, like software you've built as part of your research?
Sam: A practical artefact is accompanied by documentation that explains what it is, how it was designed, how it was built, and how it was evaluated. The documentation should make clear how the artefact demonstrates the findings of your research and what its limitations are. Screenshots, user documentation, and evaluation reports are all part of the artefact's evidence base.
Alex: Any tips for making a research report compelling to read?
Sam: Write clearly and concisely. Avoid unnecessary jargon. Use concrete examples to illustrate abstract points. Make your argument structure clear; the reader should always know where you are in the story and where you're going. And be honest about uncertainty and limitation; hedged, honest claims are more credible than overconfident assertions.
Alex: Brilliant. Thanks Sam. Final lesson in Unit 9 is on reflection.