Scribd
Upload
9 views

Quick Quiz Zz

Uploaded by

nimxrah23
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
9 views

Quick Quiz Zz

Uploaded by

nimxrah23
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Fundamentals of

Computing System Designs


QUIZ WEB APPLICATION - QUICK QUIZ

By:
Kashyap Gorasiya (2413103)
Manvi Jain (2413105)
Nimra Sayed (2413106)
Nomaan Akhtar (2413108)
Introduction:

This presentation will outline the specifications for a Quiz Web App.
It will cover the functionalities for user registration, login, and logout
for all user roles, including Admin, Teacher, and Student.
Additionally, it will discuss the features and technologies used in the
backend and frontend development of the app, as well as additional
features and the roles and responsibilities of the development team.
Features:
• Supports MCQ, MSQ, NAT question types
• Time-limited quizzes with auto-submit feature
• Shuffled questions for each student
• Teacher-controlled infinite time option for quizzes
• Quiz dashboard for performance analytics
System Architecture:
Working:
1. Start (User Login) 2. Admin Workflow

● Input: User enters credentials. ● Manage Teachers, Students, and Subjects:


● Decision: Identify user role (Admin, Teacher, or ○ Add/Remove Teachers
Student). ○ Add/Remove Students
○ Add/Remove Subjects
● Output: Updates are saved in the SQLite3 database.

4. Student Workflow 3. Teacher Workflow

● View Available Quizzes: ● Create Quiz


● Attempt Quiz: ● Assign Quiz
● View Results: ● View Reports
● Output: Quiz answers and results are saved in the ● Output: All quiz and student data are saved or
SQLite3 database. retrieved from the SQLite3 database.
Technology Stack:
Backend (Python/Django) Frontend (HTML, Bootstrap, jQuery)

● Handles: ● Displays:
○ Authentication and user role-based access control. ○ User interface for Admin, Teacher, and Student roles.
○ Session management (prevents login from multiple ○ Quiz interface for students (question navigation, timer).
devices). ○ Dashboards for Admin and Teacher (quiz creation,
○ Validates and processes quiz data. student reports).
○ Enforces quiz rules (time limit, random questions,
auto-submit).

Security
Database (SQLite3)
● Session Control: Prevents multiple logins by the same user on
● Stores: different devices.
○ User data (Admin, Teacher, Student) ● Role-Based Access Control (RBAC): Ensures actions are
○ Quiz data (questions, answers, results) restricted based on user roles (Admin, Teacher, Student).
○ Reports and analytics data for teachers and students. ● Data Flow: Encrypted communication via HTTPS between
frontend and backend.
System Design Perspective:
Modularity Client-Server Architecture
○ Admin Module ○ Frontend (Client):
○ Teacher Module ■ Built using HTML, Bootstrap, and jQuery to
○ Student Module manage user interactions for Admin, Teacher, and
● Each module interacts with the backend and database Student.
independently, reducing coupling and allowing each module to be ○ Backend (Server):
updated or changed without affecting the others. ■ Built using Python Django for managing user
requests, authentication, session control and
session management.
Session Management Concurrency and Scalability
● The system maintains sessions to handle user authentication. ● The system is designed to handle multiple users (Teachers,
○ When a user logs in, a session is created, which is stored
Students) interacting with the application simultaneously.
server-side in the backend and mapped to the database.. ● The system can be scaled horizontally by deploying multiple
○ Sessions are also used to manage quiz time limits and
backend instances, each serving a portion of the users, especially
auto-submit quizzes once the time expires.
when dealing with many students taking quizzes simultaneously.
DJANGO APPS

FRONT END

DATABASE
FILE
Progress:

● 25% Backend completed


● 25% Frontend completed
● 50% Database completed
● 10% session management

● Overoll 30% project Completed

You might also like