How eshwargit2/java_placement_training_app works
This is a Java placement-preparation portal with a 41-day learning roadmap, daily assessments, student progress tracking, and batch analytics. The main flow is learners accessing the portal, retrieving day-based questions, submitting answers for grading, and having results and progress stored for later review; administrators manage students and question banks and review reports. The sampled routes and models support these backend links. Frontend-to-API calls and the compile route’s execution details were not shown, so those connections are left unverified or omitted.
Main entry points: server.js HTTP server · assessments.js Assessment workflow · User.js User records · stats.js Batch analytics
Components 23
Portal screens
- Learner portal
frontend/student.html - Assessment screen
frontend/assessment.html - Admin dashboard
frontend/admin.html - Student management
frontend/students.html - Reports and results
frontend/reports.html - Result details
frontend/results.html - Browser API client
frontend/api.js - Portal interactions
frontend/script.js
API workflows
- Authentication
backend/routes/auth.js - Student profiles
backend/routes/students.js - Question bank
backend/routes/questions.js - Assessment workflow
backend/routes/assessments.js - Answer evaluation
backend/utils/evaluator.js - Batch analytics
backend/routes/stats.js - Code compilation
backend/routes/compile.js
Assessment data
- User records
backend/models/User.js - Question records
backend/models/Question.js - Submission history
backend/models/Submission.js
Service runtime
- HTTP server
backend/server.js - MongoDB connection
backend/config/db.js - Initial data seeding
backend/utils/seeder.js
Other components
- Student
- Administrator
Connections 29
- HTTP server → MongoDB connection: connects
backend/server.js - HTTP server → Initial data seeding: seeds data
backend/server.js - HTTP server → Authentication: mounts route
backend/server.js - HTTP server → Student profiles: mounts route
backend/server.js - HTTP server → Question bank: mounts route
backend/server.js - HTTP server → Assessment workflow: mounts route
backend/server.js - HTTP server → Batch analytics: mounts route
backend/server.js - HTTP server → Code compilation: mounts route
backend/server.js - HTTP server → Learner portal: serves static files
backend/server.js - Student → Learner portal: uses
README.md - Administrator → Admin dashboard: uses
README.md - Browser API client → HTTP server: requests API
- Authentication → User records: reads
backend/routes/auth.js - Student profiles → User records: manages
backend/routes/students.js - Student profiles → Submission history: reads and deletes
backend/routes/students.js - Question bank → Question records: queries and imports
backend/routes/questions.js - Assessment workflow → Question records: loads questions
backend/routes/assessments.js - Assessment workflow → Answer evaluation: evaluates answers
backend/routes/assessments.js - Assessment workflow → User records: reads and updates
backend/routes/assessments.js - Assessment workflow → Submission history: saves submissions
backend/routes/assessments.js - Batch analytics → User records: counts students
backend/routes/stats.js - Batch analytics → Question records: counts questions
backend/routes/stats.js - Batch analytics → Submission history: aggregates scores
backend/routes/stats.js - Initial data seeding → User records: seeds accounts
backend/utils/seeder.js - Initial data seeding → Question records: imports questions
backend/utils/seeder.js - Learner portal → Assessment screen: takes assessments
README.md - Admin dashboard → Student management: manages students
README.md - Admin dashboard → Reports and results: reviews analytics
README.md - Assessment screen → Result details: reviews scores
README.md