Video Representation Script:
Video Presentation Guidelines (Advised):
1. A short Intro (not more than 30 sec)
2. How did you approach the problem statement? (30 sec)
3. Highlight key features of the application (90 sec)
4. Any Additional feature(s) implemented other than core requirements (30 sec)
Video Presentation Guidelines Recap
From the document:
1. Short Intro (not more than 30 seconds)
2. How Did You Approach the Problem Statement? (30 seconds)
3. Highlight Key Features of the Application (90 seconds)
4. Any Additional Features Implemented Beyond Core Requirements (30 seconds)
5. Total Duration: 5-10 minutes (aim for ~5-7 minutes to stay concise).
6. Optional: Keep your video feed on (screencast with facecam recommended but not
required).
7. Purpose: Clear explanation of your work for examiners to review before/during the viva.
1. Short Intro (0:00 - 0:30, ~30 seconds)
What to Say:
o "Hi, I’m [Sudhanshu Kumar], I presenting my project of Modern application
development 1, which is Quiz Master. This is a Flask-based web application
designed for exam preparation, that has an admin that is called the quiz master
that can manage quizzes and users attempt them."
What to Show:
o or a title slide with "Quiz Master - MAD-1 Project" and your name.
Tips:
o Keep it short and confident.
o If using a screencast, start with your browser open to the app.
2. How Did You Approach the Problem Statement?
What to Say:
o "I approached this project by following the core milestones. I started with setting
up a GitHub repository and I define SQLite database models using Flask-
SQLAlchemy. Then, I implemented authentication for admin and user login and
user registration, and then I created the dashboards for both roles, and added quiz
attempt features and quiz summary stats with charts,."
What to Show:
o Display the codes part that you say, Display your app’s homepage
([Link]
Tips:
o Focus on the process, not details—mention milestones to tie to the document.
o Transition quickly to features.
To make this application I have used read and show the technology you used
This is my database schema looks like show the er diagram and the code
So now let me run and present the project that Is my quizquest applicaiont
3. Highlight Key Features of the Application (1:00 - 4:00, ~3 minutes)
What to Say and Show:
o Split this into short demos of Milestones 1-7 (20-30 seconds each):
1. Database Setup (Milestone 1):
"The app uses SQLite with tables like User, Quiz, and Question,
created programmatically."
Show: Open your models/[Link] file or a screenshot of your
ER diagram.
2. Authentication (Milestone 2):
"Users can register and log in, while the admin is predefined with
no registration."
Show: Demo /register (fill out a form), /login (log in as a user), and
/admin/login (log in as admin).
3. Admin Dashboard (Milestone 3):
"Admins can manage subjects, chapters, quizzes, and questions,
plus view users."
Show: Navigate to /admin/dashboard, add a quiz (e.g.,
/admin/chapter/1/add_quiz), and show /admin/users (non-admins
only).
4. User Dashboard & Quiz Attempts (Milestone 4):
"Users see subjects and quizzes, attempt them with a server-side
timer, and get feedback."
Show: Go to /user/dashboard, start a quiz (/quiz/start/<quiz_id>),
answer a question, and submit.
5. Score Management (Milestone 5):
"Scores are stored and displayed with past attempts."
Show: View results at /quiz/result/<attempt_id> after submission.
6. Search Functionality (Milestone 6):
"Admins and users can search for content."
Show: Demo a search bar (e.g., /admin/search or /user/search) if
implemented.
7. Quiz Time & Duration (Milestone 7):
"Admins set quiz dates and durations; users can only attempt
within that timeframe."
Show: Edit a quiz to set date_of_quiz and time_duration, then try
starting it outside the timeframe (e.g., get a flash message).
Tips:
o Keep demos quick—e.g., "Here’s the admin adding a quiz" (click, type, submit).
o Narrate as you go: "This shows the timer enforcing quiz duration."
o If a feature isn’t fully polished, say, "This is a basic implementation of [feature]."
4. Any Additional Features Beyond Core Requirements (4:00 - 4:30, ~30 seconds)
What to Say:
o If you haven’t done Milestones 8-11:
"I’ve focused on the core requirements (Milestones 0-7) so far. Future
work could include APIs or charts from the recommended functionalities."
5. Wrap-Up and Outro (4:30 - 5:00, ~30 seconds)
What to Say:
o "That’s an overview of Quiz Master, covering all core features required for MAD-
1. The app is fully functional locally using Flask and SQLite, and I’ve tracked
progress via Git commits. Thank you for watching!"
What to Show:
o Return to the homepage or a "Thank You" slide with your name and ID.
Tips:
o End with a clear closing statement.
o Stop recording at ~5 minutes unless you have more to show.
To make this application I have used
* Flask: for Backend application logic.
• Jinja2: for rendering dynamic HTML pages.
• HTML/CSS: Structures, styles.
• SQLite: Database for storing users, quizzes, and scores data
• Flask-SQLAlchemy: ORM for defining SQLite database models.
• Flask-Migrate: For database schema migrations.
• Flask-Bcrypt: for Password hashing
• Flask-Login: for Managing User sessions
• Flask-Wtf: for Creating authentication forms
• Matplotlib: for charts generation.