Download the screens and check how the LMS works: Download

 

Background: Nachiketa Tapovan, a school dedicated to underprivileged children in Hyderabad, operates with transparency and a mission to provide quality education. Recognizing the need for efficiency and transparency, a decision was made to implement a Learning Management System (LMS) across its two campuses. 

 

My Responsibilities: As the driving force behind this product, I undertook the responsibility of understanding requirements,decide the user flows, creating wireframes, Highlevel system design, Selection of database  and onboarding a developer committed to the cause. After a meticulous search, Hemant Raut, an exceptionally talented team member, joined the project, becoming a crucial contributor to the LMS development. 

 

Functional Requirements: 

The LMS was designed to cater to different users: 

1. Student Profiles and Login: Enables students to track documents and monitor their performance across classes. 

2. Teachers Login: Facilitates mark entry, student performance monitoring, and access to student profiles. 

3. Sponsor Login: Allows sponsors to monitor their sponsored students' performance and ensures complete transparency on fund usage. 

4. Admin Login: Provides administrators with the capability to monitor students, teachers, sponsors, and maintain essential master data. 

5. Teacher Attendance Monitoring: A crucial feature to keep track of teacher attendance. 

 

Non-Functional Requirements: 

 

According to the CAP(Consistency, Availability & Partial failure) for any system there is a constraint that we can select two out of three from CAP. 

 

1. Consistency: System should be consistent across and there should not be any data discrepancies within different modules as main aim for LMS was to build transparency 

1. Avaliability: Sponsor can login at any time system should be consistent and available for all the request that are sent

2. Performance: The latency should be in the medium range as we were also focused on cost and used only one server that can perform both storage and processing.

 

High-Level System Design: 

 

Efficiency and cost-effectiveness were prioritized: Database Selection: A 16GB AWS database was chosen, serving both as a processing unit and storage, balancing functionality and cost.

 

We used SQL database as described above in CAP for us it was more important to have Consistency & Availability rather than to handle a partial failure scenario.

 

The LMS architecture comprised several key components: 

1. User Authentication: Secure logins for students, teachers, sponsors, and administrators, ensuring data privacy. 

2. Database Management: The AWS database acted as the backbone, handling data storage and processing efficiently. 

3. Student Performance Tracking: Through a user-friendly interface, students could access documents and monitor their academic progress. 

4. Teacher Functions: Teachers could log in to input marks, monitor student performance, and manage profiles. 

5. Sponsor Transparency: Sponsors had a dedicated portal for real-time tracking of their sponsored students' progress and fund utilization. ​

6. Admin Oversight: Administrators had comprehensive control, overseeing all aspects, including master data maintenance and teacher attendance monitoring. 

How the LMS Works: The LMS functions as a cohesive platform where students, teachers, sponsors, and administrators engage: 

1. User Authentication: Each user logs in securely, accessing their personalized dashboard. 

2. Task-Specific Portals: Tailored interfaces for students, teachers, sponsors, and administrators, catering to their specific responsibilities. 

3. Real-Time Updates: The LMS provides real-time updates on student performance, fund utilization, and overall system health. 

4. Efficient Communication: The platform facilitates seamless communication between stakeholders, fostering transparency and collaboration.