Presentation: Computer Science

Top Five Tips

  1. Be 100% clear about your problem and how the context will be different when you solved it
  2. Visualise your project/ problem within the first five slides
  3. Use images, tables and graphs as taking points when talking about (test) data
  4. Link everything back to your context, problem or artefact
  5. Set a time limit for each slide (2 minutes)

What The Marker Is Looking For In Your Viva

  • You can explained the context, problem and solution (visualise your project and here)
    • You understand why it is a problem
    • You understand what the problem is
    • You understand how the solution will impact on the context
  • You have compared alternatives leading to a clear and well justified approach (SWOT analysis)
    • You have considered alternative solutions
    • You have developed/ linked your subject knowledge
    • You have justified why you have discounted alternative solutions
  • You have carried out testing which informed artefact development (testing)
    • You use key research methodology words and terms (see chapter three)
    • Tested the context (baseline) before you make changes
    • Tested the artefact functions correctly (black and white box)
    • Tested the artefact output (used test data to refine your artefact)
    • Tested the artefact output on real world data (not your test data)
  • You have shown that the artefact has made a positive impact on the context
    • You have compared the baseline data with the real word testing data
    • You have concluded if you have achieved your objectives and success criteria (outcomes)
  • You can explain your personal development (skills and knowledge through reflection)
    • What skills or knowledge you have improved
    • What skills or knowledge you have created/ established
    • What you will do differently next time and why
    • What you will do the same next time and why
  • You can answer questions about your project
    • Expect question about all areas of your project
  • Professional standard in all respects of structure, quality, and delivery
    • Your slides feel open and approachable
    • You have used a consistent house-style
      • Colour, fonts, font size etc..
    • The pace of your presentation is just right
      • Too slow, the marker is bored to death and switches off
      • Too fast, the marker cannot keep up
      • Alter your voice tone and enthusiasm
    • Used tables, graphs and images to help visualise your point


Another way of thinking about the viva is to consider the critical factors of any artefact development report, using these as a back bone to your viva.

-) You need to be explicit if you have achieved your success criteria (outcomes) using evidence (data/ feedback).

Table 1) Success Criteria – Achievement Summary

NoSuccess criteriaEvidenceAchieved
1Increase in website salesThe data outlined in the web metric section (pg64) indicates that the number of sales has increased by 10% when comparing the four weeks before the website updated to the four weeks following the website updates.Yes


-) You need to be explicit if the artefact has achieved the stated requirements using evidence (data/ feedback). In your viva, you may want to highlight a few of the critical requirements rather than all of them!

Table 1) Testing of Requirement Summary

NoRequirementSC NoEvidenceAchieved
1The time taken to navigate to an item will be recorded1The test data displayed in table 15 and figure 12 (pg72) indicate that this web metric feature is working. Further testing information is displayed in the test plan (see page 65)Yes


-) You need to evidence your testing (test plan with data) and analysis of your data (tables, graphs and charts). In your viva, you may want to show a sample of this to demonstrate your approach and skills.

-) Link to (show) at least one of your system design drawing(s) (e.g. UML, DFD or ERD) to explain your system.