Skip to content

Blog / Capstone defense · 8 min read ·

How to defend your capstone system in front of a panel

A panel question bank grouped by topic, a slide outline, safe live demo practices, and how to answer questions you cannot answer.

A capstone defense is not a test of whether your system is perfect. It is a test of whether you understand what you built, why you built it that way, and where its limits are. Prepare for the questions, rehearse the demo and know your weaknesses, and a modest system can still defend well.

This guide gives you a question bank grouped by topic, a slide outline, a safe demo checklist, and a method for handling the questions you cannot answer.

What the panel is looking for

Panels differ by school and by panelist, so read your institution's rubric first and ask your adviser what each panelist tends to focus on. Across most capstone defenses, panelists check four things:

  • Problem fit: the system solves a real, documented problem for identified users.
  • Ownership: every member can explain the parts they built and how the parts connect.
  • Soundness: the methodology, data model, and testing are appropriate and honestly reported.
  • Awareness: you know the limitations and can say what you would do next.

Panel question bank

Use these to run mock defenses. Assign each member a topic, but check that everyone can answer at least the scope and limitations questions. Answer out loud, not in your head; an answer that sounds fine silently often falls apart when spoken.

Scope and objectives

  • What specific problem does your system solve, and how did you confirm it exists?
  • Who are the users, and how many did you consult?
  • Why did you choose this client or locale, for example this barangay or this water district?
  • Which features are out of scope, and why?
  • How does each objective map to a feature in the system?
  • What makes this different from existing systems or from what the office already uses?

Methodology

  • Which development methodology did you use, and why does it suit your project?
  • How did you gather requirements, and what did you change based on the results?
  • How did you choose your respondents and your evaluation instrument?
  • Why did you use this evaluation model or standard, and what do its criteria measure?
  • How did you compute and interpret your evaluation results?

Technical design

  • Walk us through your ERD. Why is this a separate table?
  • Why did you choose this language, framework, and database?
  • What happens to the data when a user submits this form? Trace it end to end.
  • How does the system behave with no internet connection?
  • Show us the code for this feature. Who wrote it?
  • How would the system handle ten times the current number of records?

Security and data privacy

  • How are passwords stored?
  • What stops a resident from viewing another resident's records?
  • How do you protect against SQL injection and similar attacks?
  • What personal data do you collect, and how does your system comply with the Data Privacy Act of 2012?
  • Who can delete or edit records, and is that logged?
  • How are backups made, and who is responsible for them?

Testing

  • What kinds of testing did you perform: unit, integration, user acceptance?
  • Show us a test case that failed and how you fixed it.
  • Who were your testers, and were any of them actual end users?
  • How did you test invalid input, such as a negative meter reading or a duplicate student number?

Deployment and sustainability

  • Where will the system run after you graduate, and who pays for hosting?
  • Who will maintain it, and have they been trained?
  • What are the hardware and connectivity requirements for the client?
  • How will the client get updates or bug fixes?

Limitations and future work

  • What are the main limitations of your system?
  • If you had six more months, what would you add first, and why?
  • What would you do differently if you started over?

A slide outline that works

Follow your school's required format if there is one. If not, this structure keeps a 15 to 20 minute presentation focused. Fewer words per slide is better; the panel should be listening to you, not reading.

Suggested defense slide outline
#SlideWhat to show
1TitleSystem title, team members, adviser, date
2ProblemThe current process and its pain points, with evidence from your data gathering
3ObjectivesGeneral objective and specific objectives, numbered
4Scope and limitationsWhat is in, what is out, and why
5MethodologyDevelopment model and how you applied each phase
6System architectureOne diagram showing users, client apps, server, database, external services
7Data modelSimplified ERD with the core entities only
8Live demoSwitch to the system; follow a scripted scenario
9Testing and evaluationTest summary and evaluation results with interpretation
10Conclusions and recommendationsAnswer each objective; list future work

How to demo safely

The live demo is where most defenses go wrong, usually because of something outside the code: the venue Wi-Fi, an expired hosting trial, or a laptop update. Prepare for failure so that a problem costs you a minute, not your credibility.

  1. 01

    Write a demo script

    Pick one realistic scenario per user role, for example: a resident requests a barangay clearance, the secretary approves it, the captain views the monthly report. Rehearse the exact clicks.

  2. 02

    Prepare seed data

    Load the database with realistic but fictional records: invented names, sample addresses, enough rows that reports and search look meaningful. Never demo with real residents' or patients' personal data.

  3. 03

    Run it locally

    Have the full system running on the demo laptop without needing the internet. If a feature needs a network service such as SMS, show a log or a test message instead, and say so.

  4. 04

    Record a backup video

    Screen-record the full demo script a day before. If the live demo fails, say what happened and play the video. Panels generally accept this far better than ten minutes of troubleshooting.

  5. 05

    Reset before you start

    Keep a script or database dump that restores the seed data, so the demo starts from a known state every time.

  6. 06

    Check the room

    Test the projector, the display resolution, and the font size from the back of the room. Turn off notifications and auto-updates.

Handling questions you cannot answer

Every team gets at least one question it did not prepare for. The goal is to respond honestly and show that you can reason about it.

  1. Pause and restate the question. "If I understand correctly, you are asking how we handle two cashiers editing the same bill at the same time." This buys time and confirms you are answering the right question.
  2. Say what you do know. Explain the related part you understand, then point to where your knowledge ends.
  3. Admit the gap plainly. "We did not test that case." Do not guess or invent an answer; panelists usually know when you are bluffing.
  4. Offer a reasoned approach. "Our approach would be to add record locking or a version check on update, and we will include it in our recommendations."
  5. Write it down. Note the question and include it in your revisions. Panels often check whether their comments were addressed.

Agree beforehand who answers which topic, and let that person speak first. Teammates can add to an answer, but avoid contradicting each other in front of the panel; discuss disagreements afterward.

Final week checklist

  • Run at least two full mock defenses with someone outside the team asking questions.
  • Confirm the manuscript, slides, and system all describe the same features and numbers.
  • Freeze features. Only fix bugs in the final days.
  • Prepare printed copies or files of the manuscript as your school requires.
  • Back up the source code, database dump, slides, and demo video in at least two places.
  • Agree on attire, arrival time, and who handles the laptop.

Next step

Hold a full rehearsal this week. Ask a classmate to play the panel, pick five questions from the question bank above and time your demo from login to report. Before that, check that your diagrams still match what you built, using the system diagrams guide.

Building a system for a school, utility or organisation? Book a consultation