How mohitkumar6122/online-examination-system works
Project type and purpose
• This is a full-stack, monolithic web application built on the Django framework.
• Its purpose is to deliver an Online Examination System, with distinct interfaces and workflows for Students, Professors, and Administrators.
File structure
• Top-level “Exam” directory is the Django project root. Under it:
• examProject/ – project settings, URL router, WSGI/ASGI entrypoints, global static files
• Multiple Django apps by domain: admission, course, faculty, questions, resultprocessing, student, studentPreferences, tuition
• templates/ – shared and per-app HTML templates
• media/ – user-uploaded content (profile pictures)
• db.sqlite3 – default database
• manage.py, Pipfile, requirements.txt – build, environment, dependencies
• Each app follows standard Django MVC: models.py, views.py, urls.py, admin.py, migrations/, templates (in some), tests.py.
• Static assets (CSS, JS, images) live under examProject/static and templates/static.
README for additional insights
• Stack: Python, Django, HTML/CSS/JavaScript, SQLite (or configurable RDBMS), Pipenv, Argon2 password hashing.
• Features: auto-submit, focus monitoring with email alert (external SMTP), automatic scoring.
• Actors: Students, Professors, Admins (superuser + Django Groups).
Detail without over-fragmentation
• Domain app as a separate element within the server layer.
• Shared components (template engine, static files).
• User-group logic (Students vs Professors) gating access to specific apps or views.