Planning System For Educators

A major project report submitted in partial fulfillment of the requirement

for the award of degree of

Bachelor of Technology
in
Computer Science & Engineering

Submitted by
Yuvika Dhiman 211556

Under the guidance & supervision of

Ms. Seema Rani & Mr. Gaurav Negi

Department of Computer Science & Engineering and

Information Technology
Jaypee University of Information Technology,
Waknaghat, Solan - 173234 (India)
May 2025
 SUPERVISOR’S CERTIFICATE

This is to certify that the major project report entitled ‘Planning System For Educators’,
submitted in partial fulfillment of the requirements for the award of the degree of Bachelor
of Technology in Information Technology, in the Department of Computer Science &
Engineering and Information Technology, Jaypee University of Information Technology,
Waknaghat, is a bona fide project work carried out under my supervision during the period
from July 2024 to May 2025.

I have personally supervised the research work and confirm that it meets the standards
required for submission. The project work has been conducted in accordance with ethical
guidelines, and the matter embodied in the report has not been submitted elsewhere for the
award of any other degree or diploma.

Supervisor Name: Seema Rani Supervisor Name: Mr. Gaurav Negi

Designation: Assistant Professor Designation: Assistant Professor
Department: Dept. of CSE & IT Department: Dept. of CSE & IT

Date: 9 May 2025

Place: JUIT, Waknaghat, Solan

i
 CANDIDATE’S DECLARATION

We hereby declare that the work presented in this major project report entitled ‘Planning
System For Educators’, submitted in partial fulfillment of the requirements for the award
of the degree of Bachelor of Technology in Information Technology, in the Department
of Computer Science & Engineering and Information Technology, Jaypee University of
Information Technology, Waknaghat, is an authentic record of our own work carried out
during the period from July 2024 to May 2025 under the supervision of Ms. Seema Rani &
Mr. Gaurav Negi.

We further declare that the matter embodied in this report has not been submitted for the
award of any other degree or diploma at any other university or institution.

Name: Yuvika Dhiman

Roll No.: 211556
Date: 9 May 2025

This is to certify that the above statement made by the candidates is true to the best of my
knowledge.

Supervisor Name: Seema Rani Supervisor Name: Mr. Gaurav Negi

Designation: Assistant Professor Designation: Assistant Professor
Department: Dept. of CSE & IT Department: Dept. of CSE & IT

Date: 9 May 2025

Place: JUIT, Waknaghat, Solan

ii
ACKNOWLEDGEMENT

Firstly, we express our heartiest thanks and gratefulness to almighty God for His divine
blessing makes it possible for us to complete the project work successfully.

We are really grateful and wish my profound indebtedness to Supervisor Ms. Seema Rani
& Mr. Gaurav Negi, Assistant Professor, Department of CSE Jaypee University of
Information Technology, Wakhnaghat. Deep Knowledge & keen interest of my supervisor
to carry out this project in the field of ‘Web Development’. His endless patience, scholarly
guidance, continual encouragement, constant and energetic supervision, constructive
criticism, valuable advice, reading many inferior drafts and correcting them at all stages have
made it possible to complete this project.

We would like to express our heartiest gratitude to Ms. Seema Rani & Mr. Gaurav Negi,
Associate Professor, Department of CSE, for his kind help to finish this project.

We would also generously welcome each one of those individuals who have helped us
straightforwardly or in a roundabout way in making this project a win. In this unique
situation, we might want to thank the various staff individuals, both educating and non-
instructing, which have developed their convenient help and facilitated our undertaking.

Finally, we must acknowledge with due respect the constant support of our parents.

Yuvika Dhiman
211556

iii
TABLE OF CONTENTS

Supervisor’s Certificate ...................................................................................................... I

Candidate’s Declaration .................................................................................................... II

Acknowledgement .............................................................................................................III

List Of Tables ...................................................................................................................VII

List Of Figures ................................................................................................................VIII

List Of Abbreviations, Symbols Or Nomenclature ........................................................IX

Abstract .............................................................................................................................. X

Chapter 1: Introduction ......................................................................................................1

1.1 Introduction ...................................................................................................................1

1.2 Problem Statement .........................................................................................................2

1.3 Objectives ......................................................................................................................3

1.4 Significance And Motivation Of Our Project ................................................................5

1.5 Organisation Of Project Report .....................................................................................7

Chapter 2: Literature Survey …….....................................................................................9

2.1 Overview Of Relevant Literature ..................................................................................9

2.2 Key Gaps In The Literature .........................................................................................15

Chapter 3: System Development ......................................................................................17

iv
 3.1 Requirements And Analysis ..................................................................................... 17

3.1.1 Functional Requirements .................................................................................. 17

3.1.2 Non-Functional Requirements ....................................................................... .. 19

3.1.3 Analysis Approach .......................................................................................... 20

3.2 Project Design And Architecture ............................................................................... 21

3.2.1 System Architecture .......................................................................................... 22

3.2.2 Tools, Technologies, And Languages ................................................................ 23

3.2.3 Architecture ........................................................................................................24

3.3 Implementation .......................................................................................................... 24

3.4 Key Challenges ............................................................................................................ 27

Chapter 4: Testing .......................................................................................................... .31

4.1 Testing Strategy ......................................................................................................31

4.1.1 Levels Of Testing ......................................................................................... 32

Chapter 5: Results And Evaluation ............................................................................. 34

5.1 Results .................................................................................................................. 34

5.1.1 Performance Analysis ................................................................................ 34

5.1.2 User Experience And Usability Evaluation ……........................................ 40

5.1.3 Comparison With Existing Solutions…………………….………………. 41

Chapter 6: Conclusions And Future Scope …………….........................................….43

6.1 Conclusion ............................................................................................................43

iv
 6.1.1 Key Findings ............................................................................................ .44

6.1.2 Contributions To The Field ...................................................................... 45

6.2 Future Scope ........................................................................................................46

References ....................................................................................................................... 47

Appendix ......................................................................................................................... 51

iv
 LIST OF TABLES

Table No. Title Page No.

Table 2.1 Literature review 9

8
 LIST OF FIGURES

Figure No. Title Page No.

Fig 3.1 Unit Planning in Planning Module Architecture 23

Fig 5.1 Course Structure Teacher Account Navigation Flow 36

Fig 5.2 Teacher dashboard with customized view. 38

Fig 5.3 Interactive Curriculum Course Builder 39

Fig 5.4 Unit Planning Timeline Overview in Planning Module 40

Fig 5.5 Unit Planning Timeline Overview in Planning Module 40

Fig 5.6 Single Page Unit Planner 41

9
LIST OF ABBREVIATIONS, SYMBOLS OR
NOMENCLATURE

Abbreviations Full Form

IB International Baccalaureate

PYP Primary Years Programme (part of the IB continuum)

MYP Middle Years Programme (part of the IB continuum)

DP Diploma Programme (part of the IB continuum)

QA Quality Assurance

10
 ABSTRACT

Effective teaching starts with effective preparation, but teachers often find it challenging to
manage their schedules, lesson plans, and curriculum objectives for multiple courses.
Fragmented technologies make it even harder to work with coworkers, students, and
families. Toddle's Planning Module solves this by providing a simplified one-stop solution
that maximizes planning, improves teamwork, and lessens administrative burden.

The Planning Module accommodates IB curriculum and has further equipped teachers with
all intuitive tools for easy unit formation and easy schedule management. The planning tool
also features the function to form and modify a unit while maintaining permission and its
editing rights among colleagues as needed. Class planner further eases visualization over an
entire school year. Teachers gain flexibility and structure within these features to plan, get
ahead, and deliver well towards curriculum objectives. Moreover, Class Flow tools allow
teachers to easily organize class objectives and transitions so that they do not waste time in
class on executing the lesson.

The Planning Module is an important tool for educators around the world because it allows
them to be responsive to different teaching needs and changing classroom demands. Toddle
gives instructors one platform that combines resource management, planning, and
collaboration to help them increase teaching impact, efficiency, and focus on meaningful
learning experiences.

11
 CHAPTER 1: INTRODUCTION

1.1 INTRODUCTION

The backbone of effective teaching remains effective planning, yet this is one of the most
significant obstructions teachers face worldwide. The demand for planning lessons,
scheduling, and curriculum requirements clashes with the challenge of teaching multiple
classes and the needs of numerous students. The problem is that most of today's standard
planning and organizing tools are fragmented, making it difficult for teachers to work well
with colleagues, students, and families. Such inefficiencies are costly in terms of the time
and effort teachers use to provide relevant, engaging learning experiences.

The Toddle planning module addresses this issue by offering teachers practical, easy-to-
access solutions that help to optimize work streams and enhance instruction. It combines unit
planning, class scheduling, and collaboration into a single interface designed with the
modern educator in mind.

At the core of this module is Unit Planning, a feature that allows teachers to easily plan and
edit curriculum-aligned units to global standards, such as International Baccalaureate (IB)
frameworks. Teachers can share their plans with colleagues, students, and families while
retaining total control over permissions to prevent sensitive information from being accessed
incorrectly.

The Class Planner helps teachers structure their annual calendars visually. This way, they
can be organized while still being flexible with changes that may be required by classroom
needs. Class Flow also enables teachers to organize the lessons so that teaching becomes
smooth due to clear goals and transitions.

Apart from planning, this module creates a collaborative environment since it centralizes all
the available resources, such as assignments, notes, and links. This reduces administrative
workload so that the teachers have ample time to focus on the student's engagement and
learning outcomes.

Intuitively designed and powerful functionality make the Planning Module suitable for the
varied needs of educators worldwide. It has addressed the pain points - fragmented tools and

1
lack of coordination in the workflow - ensuring that Toddle equips teachers to streamline
their planning, enhance collaboration, and focus on what is meaningful for them: impactful
learning experiences for their students. In so doing, not only will the Planning Module
revolutionise teachers' planning and teaching, but it will also elevate the level of education
as a whole.

Successful teaching is founded on careful planning, but teachers everywhere get bogged
down in time-consuming administrative tasks that take away from their primary focus:
creating quality learning. Standard planning practices are usually a juggling act between
several tools - lesson planners, digital calendars, communication tools, and curriculum
blueprints - and result in inefficiency and frustration. Teachers need to balance curriculum
demands, student needs, and institutional requirements with flexibility for improvisation.
The absence of an integrated system removes these issues, which forces teachers to spend
precious time on coordination instead of teaching.

Toddle’s Planning Module emerges as a transformative solution, integrating unit planning,

scheduling, and collaboration into a single, intuitive platform. Designed with modern
pedagogical demands in mind, it eliminates the need for fragmented tools by offering
curriculum-aligned unit planning, visual class scheduling, and centralized collaboration.
Teachers can design, modify, and share units compliant with global standards like the
International Baccalaureate (IB), while an interactive planner helps structure the academic
year with real-time adaptability. By consolidating resources, assignments, and feedback, the
module reduces redundancy and improves communication among teachers, students, and
parents. Ultimately, what our tools does is empowering educators to focus on student
engagement rather than focusing on the administrative overhead, addressing the critical pain
points of disorganized planning tools and fostering a more efficient educational ecosystem.

1.2 PROBLEM STATEMENT

Teachers across the globe are seriously challenged with developing and implementing
effective lessons.Scheduling lessons, aligning schedules with those of other classes, and
achieving curriculum objectives are often complicated because many educators have to
juggle numerous classes, diverse students with different needs, and administration demands.

2
These processes become even more challenging because such educators lack a holistic
system that can help them easily accomplish their workflows.

Current educational planning tools typically are isolated. Teachers have to employ multiple
systems to create lesson plans, schedule lessons, and collaborate with other teachers,
students, and families. This isolation results in inefficiencies, miscommunications, and more
administrative burden. For example, one tool may be used for lesson planning, another for
scheduling, and yet another facilitates communication between parents and students. These
transitions waste the limited time and energy that could otherwise be channeled toward the
intended goal: creating meaningful learning experiences.

Another significant problem that teachers encounter is collaboration. Teachers' ability to

collaborate and provide constructive criticism might be impaired by silos created by
inadequate means for exchanging plans and resources. Similar to this, poor channels of
communication with families and kids often create a gap between the goals of the classroom
and outside help, which eventually impacts the students.

However, with the trend that goes towards curriculum frameworks, for instance,
International Baccalaureate, other inquiry-based approaches that include curricula, it's gotten
so much more complex and the process of planning, too, which now requires that in the
course of designing units and lessons according to the frameworks, one would ensure it is
flexible for learners with diverse needs and changeable classroom environments. Most
existing tools are ineffective in aligning the teaching strategy to the developed international
standards. Thus, most teachers will be forced to independently sort out such issues.

Mostly, resource management and the follow-up on progress will become another
administrative task added to the burden of a teacher. Most of them spend a lot of time
managing such issues because no integrated systems have been implemented in handling
administrative duties.

The lack of all-in-one solutions that can handle such challenges comprehensively creates a
big barrier to an effective teaching process. Educators need streamlined, intuitive platforms,
which include unit planning, scheduling, resource management, and collaborative functions.
This would allow teachers to spend less time on administrative tasks, increase their capacity
to work in teams, and spend more time on quality education delivery, which consequently
will enhance outcomes for students while fostering a more efficient teaching environment.

3
Also there is problem with the teachers is that they cannot plan their day. The students should
also be able to see what they will be doing today. Collaboration can make learning so much
easier and better. There is no tool that can do these things. The teachers can manage the
homework of students at one place, monitor and track their performance. These are still
missing one software.

Instructors carry a triple load: creating engaging lessons, conforming to strict curricula, and
teaching complex classrooms—all while operating with isolated tools that stifle productivity.
The majority of educators use a collection of apps, including Google Classroom, Excel, and
paper calendars, for lesson planning, attendance, and communication with parents. This
fragmentation creates data silos, redundant efforts, and miscommunication. While no shared
space where teachers cannot collaborate on unit planning or offer on-time feedback, and
parents and students have no visibility into the lesson objectives, leading to lacunae in
homework support at home.

The intricacy of modern curricula, such as the IB's inquiry-driven curriculum, further
complicates planning. Most resources do not accommodate customization for these
standards, requiring instructors to do manual mapping of lessons to competencies—a waste
of hours on formatting instead of pedagogy.

Administrative overload in keeping track of assignments, grading, and resource deployment

across multiple classes further increases the load. Schools then compound this by purchasing
single subscriptions for planning, learning management systems (LMS), and
communication, rendering it more expensive and IT-savvy.

One platform must be able to automate day-to-day work, support global curricula with
editable templates, enable real-time collaboration, and reduce the cost of institutions by
integrating multiple tools into one. Toddle's Planning Module addresses these limitations
directly, offering an extensible, one-stop system for modern education.

1.3 OBJECTIVES

Toddle's Planning Module was created with the very specific aim of providing teachers with
an intuitive, user-friendly, and thorough system that addresses the grand challenges of lesson
planning, planning, and collaboration. A combined solution is anticipated to result in

4
increased productivity, reduced administrative inconvenience, and unfettered time for
instructors to concentrate on imparting meaningful and memorable learning experiences.

The Planning Module’s goals align with teacher empowerment and student success. First, it
streamlines unit planning by providing inquiry-based design templates for IB and other
curricula, allowing teachers to focus on pedagogy rather than formatting. Dynamic editing
features enable mid-term adjustments to accommodate student needs, while controlled
sharing ensures privacy—for instance, excluding draft units from parent view.

Second, the module streamlines class scheduling by utilizing a drag-and-drop layout to

graphically organize lessons between weeks or months and flagging conflict or pacing
concerns. Adaptive accommodations enable instructors to move whole units with the push
of a button when unexpected disruptions, such as assemblies or holiday events, take place.

Third, the module informs about the collaboration through a shared workspaces in which
teachers work together on units, comment on plans, and share resources. A parent and student
portal provides secure access to upcoming lessons and assignments, creating a bridge
between classroom and home learning.

Fourth, it aggregates resources into a single source where rubrics, worksheets, and videos
can be linked to units and accessed quickly. Automatic tracking permits student submissions,
grades, and feedback to be tracked in a single place and reduced manual recording.

Finally, the module supports global flexibility, accommodating hybrid learning (in-person
and online) and varied curricula, such as the U.S. Common Core or U.K. National
Curriculum. By addressing these objectives, the Planning Module redefines educational
planning as efficient, collaborative, and student-centered.

The following describes the four major outputs of the Planning Module:

1.3.1. STREAMLINE UNIT PLANNING

Simplification and streamlining of unit planning is among the fundamental objectives of the
Planning Module. It will enable teachers to come up with inquiry-based units which will
satisfy students with diverse learning abilities in compliance with curriculum specifications
due to user-friendly tools that teachers have for building, modifying, and managing

5
curriculum-based units for the IB and other international standards. Teachers can share the
unit plan with colleagues, students and families, for total management of access control
permissions in order to fully utilize available time and save energy towards reducing the
redundancy that could go into planning in a similar class.

1.3.2. STREAMLINE CLASS PLANNING

Collaboration is one of the cornerstones of good teaching, yet many traditional tools fail to
do this smoothly. The Planning Module helps in collaboration since educators can work
together on unit plans, share insights, and give constructive feedback. It also improves
communication with students and families since there is a central location to get lesson plans,
schedules, and resources. It creates a well-connected learning community where one can
learn from all participating parties - the educator, the student, and the family. Better channels
of communication improve ways in which teachers, parents, and students can focus on
achieving the same goals for the same thing.

1.3.3. FOSTER SEAMLESS COLLABORATION

The second critical objective of the Planning Module is to centralize all the learning
resources, including notes, assignments, links, and progress reports, into one location. In
doing this, the module minimizes the amount of labor that educators have to spend to
manually organize resources or use several different platforms. In addition to minimizing
administrative tasks, it also ensures that the efforts of teachers are focused on innovative and
creative strategies of teaching. Automated features and easy-to-use interface have also
regained the important time of educators, and resourced management is also made easier.

1.3.4. CONSOLIDATE RESOURCES AND REDUCE ADMINISTRATIVE BURDEN

The second critical objective of the Planning Module is to centralize all the learning
resources, including notes, assignments, links, and progress reports, into one location. In
doing this, the module minimizes the amount of labor that educators have to spend to
manually organize resources or use several different platforms. In addition to minimizing

6
administrative tasks, it also ensures that the efforts of teachers are focused on innovative and
creative strategies of teaching. Automated features and easy-to-use interface have also
regained the important time of educators, and resourced management is also made easier.

1.3.5. GLOBAL AND DIVERSE EDUCATIONAL NEEDS

It is flexible as its planning module adapts diverse and dynamic needs of the educators all
over the globe. This module, whether teaching is taken online or in a traditional setting, or
any mix of both, allows for flexibility and scalability on varied ground. Its alignment with
worldwide frameworks such as the IB curriculum makes it relevant, while being flexible
allows teachers to look into unique classroom dynamics and needs of students. By achieving
the objectives, the Planning Module changes how teachers plan, organize, and collaborate.
And finally making the education better and giving educators with the ability to design
meaningful, impactful learning experiences.

1.4 SIGNIFICANCE AND MOTIVATION OF THE PROJECT WORK

The importance of this project is in its ability to tackle significant education issues. Teacher
turnover is increasingly an issue, with burnout from administrative work pushing teachers
out of the field. Efficiency in workflows can increase job satisfaction and retain experienced
teachers in classrooms. Schools in low-resource areas also appreciate the low-cost, combined
tools that minimize the necessity for multiple subscriptions. Above all, transparent planning
is associated with greater student engagement and improved performance, so this module is
a driving force for better learning results.

The motivation behind the Planning Module stems from direct teacher feedback. Educators
frequently express frustration with juggling multiple apps just to plan a single week or lament
the lack of parent understanding about unit goals, which leaves students unprepared. By
merging planning, communication, and curriculum management into one platform, Toddle
addresses these pain points and redefines what teaching tools should be—efficient,
collaborative, and student-centered.

7
1.4.1 SIGNIFICANCE

Education is the important thing for social development, but teaching is its heart.
Nonetheless, teachers around the globe face increasingly difficult challenges related to
managing lesson plans and coordinating schedules and teamwork. This is further
complicated by splintered tools that hinder starting up workflows, add administrative
burdens, and hijack the amount of time that teachers can actually spend on learning moments.

The Toddle Planning Module has been designed so that it can remove the agony points and
provide teachers with a smooth, consolidated solution that makes them more efficient,
collaborative, and effective as teachers. Through its capacity to consolidate key functions
like unit planning, scheduling, and resource management into one instrument, the module
simplifies and optimizes teachers' daily practices. Moreover, by aligning with international
standards of education levels such as the International Baccalaureate syllabus, it prepares
teachers to create lesson plans that incorporate inquiry-based classes that are aligned with
academic performance expectations. It improves teaching and adds to the richness of the
learning experience of the students. All activities, notes, and timetables are provided so that
extra aids are not needed and save teachers time to concentrate more on generating
innovative lesson plans and engage face-to-face with students. Second, it helps effective
communication between families, educators, and pupils to encourage mutual respect and
encouraging learning atmosphere.

1.4.2 MOTIVATION

This project was undertaken chiefly in light of the difficulties teachers have with finding
balance between curriculum requirements and the construction of compelling teaching
experiences. With the increasing popularity of international curricula like the IB, there is an
absolute need for managing complexity without overwhelming teachers, and existing tools
lack flexibility, integration, and ease of use, hence the need for innovation. The driver for
the Planning Module is the need to bridge these gaps through an offering that addresses the
varying needs of teachers around the world. Teachers need flexible resources that can suit
their unique teaching situations, whether standard, blended, or online. By enabling teachers
to better cope with their everyday issues, the Planning Module helps enhance the quality of
instruction and educational levels across the world. Above all, its ability to deliver actual

8
change to teaching practices, alleviate administrative stresses, and allow teachers to dedicate
more time to effective student interactions is what necessitates and makes this project
important.

1.5 ORGANIZATION OF PROJECT REPORT

1.5.1 CHAPTER 1: INTRODUCTION

This chapter introduces the reader about the project with emphasis placed on how hard it is
for teachers to plan and organize lessons. It brings into the limelight the Planning Module in
Toddle as the solution to the problem with its features and goals set out. It then identifies the
significance and necessity of the project and how it may rationalize the flow of educational
activity, foster collaboration, and assist in improving teaching outcomes. The introduction
thus portrays the scope, relevance, and significance of the project to teachers and the wider
education community by laying the ground for the following chapters.

1.5.2 CHAPTER 2: LITERATURE SURVEY

This chapter discusses all the existing research work and softwares used by the teachers like
google classroom. It summarizes fragmented solutions already offered to teachers and their
shortcomings in terms of integration, ease of use, and flexibility. The chapter also researches
global curricula like the International Baccalaureate (IB) and what they require, presenting
the need for a unified solution like the Planning Module. This survey places the project
context, outlines why innovation is needed, and provides a glimpse at best practice which
has informed the module.

1.5.3 CHAPTER 3: SYSTEM DEVELOPMENT

The System Development chapter describes the technical and functional elements of the
Planning Module. It describes the system architecture, functionality, and workflow
components, including Unit Planning, Class Planner, and Class Flow features.

9
The chapter defines the technology of development, such as database administration for
resource centralization and design interfaces user-friendly. Apart from guaranteeing user
needs by means of collaboration features and management of resources, it also accounts for
how the system is compatible with international frameworks of curriculum. It provides an
overall understanding of implementation in the module.

1.5.4 CHAPTER 4: TESTING

The chapter on Testing would discuss the process and methods that have been employed to
guarantee that the Planning Module is functional, usable, and reliable. It would discuss
various phases of testing,like manual testing, unit testing, integration testing, and finally user
acceptance testing, along with key results and iterations of the system. The chapter deals
with test cases, detection of errors, and methods for resolution in achieving the desired goals
for the module. This chapter confirms the functioning of the module after new features are
introduced with the help of different testing.

1.5.5 CHAPTER 5: RESULTS AND EVALUATION

The Results and Evaluation chapter provides the outcomes of the project, showing how the
Planning Module meets the challenges identified. The module is evaluated in terms of
efficiency, usability, and alignment with curriculum frameworks. Feedback from educators,
students, and families is analyzed to assess its impact on teaching workflows and
collaboration. The chapter shows that the module's success is achieved throught the
objectives and value that the module provides as an innovative educational tool by
comparing initial goals and final outcomes. This module

1.5.6 CHAPTER 6: CONCLUSIONS AND FUTURE SCOPE

This chapter emphasizes scalability and further opportunities to improve the module. Chapter
Conclusion and Future Scope of summarize the contribution made by this project toward
educational planning and collaboration. Reflect on whether objectives have been achieved,
which barriers were overcome, and to what extent the Planning Module influences teaching

10
practices. Outlining the future improvements which will help us to integrate further
curriculum framework and analytics supporting enhanced insights for teaching. Finally,
using our solution, we can support hybrid models of online learning. Toddle’s Planning
Module represents a paradigm shift in educational planning. By addressing different parts,
collaboration barriers, and curriculum complexity, our tool frees teachers to focus on what
they do best that is inspire learners. The subsequent chapters delve deeper into its design,
validation, and transformative potential for schools worldwide.

11
 CHAPTER 2: LITERATURE SURVEY

Literature survey is an necessary process in any project development. This is because of the
fact that it gives an extensive insight into current knowledge, technology, and loopholes in
the area of study. Prior to initiating a new project or conduct an existing project, it is critical
to look at existing work to avoid duplication, learn from best practices, and make sure the
intended solution has meaningful innovation. Unless they conduct a serious literature review,
researchers and developers run the risk of reinventing the wheel or missing important issues
that others have previously solved. By examining scholarly articles, business case studies,
and available tools, researchers and developers can benefit from established methods without
repeating mistakes of the past.

One of the primary benefits of a literature survey is that it helps in validating the feasibility
of a project. For instance, if previous studies have demonstrated that a particular technology
(such as React.js for front-end development or Node.js for back-end scalability) works well
in similar applications, it provides confidence in adopting those technologies. On the other
hand, if research indicates limitations—such as GraphQL security weaknesses or learning
curve issues for some frameworks—the project team can anticipate and tackle these issues
ahead of time. For Toddle's Planning Module, literature reviews of educational technology
tools showed that most current solutions are disjointed, supporting the necessity for a
comprehensive platform.

Additionally, a literature survey aids in identifying gaps that the new project can fill. Many
studies focus on isolated aspects of a problem—such as optimizing database queries or
improving UI responsiveness—but few provide holistic solutions. For instance, whereas
other papers cover real-time collaboration capabilities within education apps, others
highlight curriculum alignment, but none of them has both in a coherent manner. Through
the integration of these results, the Planning Module aimed to fill all these gaps, providing
one coherent system for lesson planning, scheduling, and stakeholder collaboration.

In addition, a literature review assists in narrowing the project objectives and scope. Through
an understanding of how others approached the same issues, the team can establish
achievable goals and feature priorities that maximize value delivery. For example, a study of

12
teacher workflows found administrative burden to be a significant pain area, from which the
module's focus on automation and resource concentration was born. Likewise, cloud-based
deployment studies guided scalability decision-making, providing the platform's ability to
adapt to changing school sizes and mixed learning models.

Finally, an effective literature survey which adds credibility to the project. By reading well-
established research identifies that not just answer on beliefs but facts. It also supports
benchmarking against existing tools proposed in the available resources, reflecting its unique
features. For Toddle, it was placing the Planning Module in a position, not just another
learning application but as an evidence-based, instructor-centered platform aimed at solving
real-world inefficiencies.

In short, a literature survey is a must since it makes sure that a project is informed, innovative,
and impactful. It avoids duplication of effort, reveals avenues for improvement, and offers a
solid ground for development. By taking cue from the achievements and failures of past
work, the Toddle team was able to come up with a solution that really serves the needs of
educators, students, and institutions. Without this important step, the possibility of making
an ineffective or redundant system would be much greater.

2.1 OVERVIEW OF RELEVANT LITERATURE

P. Keshari et al., [1] explore the use of ReactJS in contemporary web development. Their
work details React’s component-based architecture and Virtual DOM, which supports high-
performance UI updates and one-way data flow. The paper surveys essential features such
as reusable components, lifecycle methods, and React Hooks to illustrate how developers
can efficiently build interactive single-page applications. Findings highlight React’s ability
to accelerate rendering and developer productivity, though the authors note some constraints
(e.g. a learning curve and ecosystem complexity) despite React’s broad adoption.

A. Yaris et al., [2] present a cloud-based crowd monitoring system using Node.js and Redis.
The project builds a web dashboard for visualizing crowd movement data from IoT sensors,
leveraging Redis (using the RediSolar framework) for real-time processing. Deployment on

13
Google Cloud Platform’s IaaS offers scalable hosting. Implementation results confirm that
the system successfully integrates sensor inputs and provides public web access to analytics.
The authors demonstrate that cloud deployment and in-memory data handling yield a
responsive monitoring interface, though practical performance would depend on sensor
throughput and cloud configuration.

S. K. Satapathy et al., [3] examine integrating SocialPilot (a social-media management

platform) with Node.js optimizations to enhance marketing workflows. They develop a
Node.js application that leverages SocialPilot’s APIs for scheduling and analytics, and apply
non-blocking I/O, caching, and concurrency techniques to improve throughput. The results
show significantly faster processing of social-media tasks (e.g. batch posting, metrics
aggregation) compared to a naive implementation. The authors conclude that Node.js
optimizations can materially accelerate campaign operations, though gains are bounded by
external API rate limits.

Vinayak Iswalkar et al., [4] examine integrating GraphQL with reactjs makes it more flexible
to use. No overfetching is done while using GraphQL. React’s ability to accelerate rendering
and developer productivity, though the authors note some constraints (e.g. a learning curve
and ecosystem complexity) despite React’s broad adoption. There are still some security
issues related to GraphQL API.

N. Vohra et al., [5] compare REST and GraphQL implementations in microservice

architectures. They develop example services (e.g. an authorization service with GraphQL
and a user-profile service with REST) and design “API Provider Factories” to interface with
each. Using GraphQL Code Generator for the GraphQL side and Swagger/OpenAPI for
REST clients, the study illustrates how both paradigms can be automated. The authors
highlight GraphQL’s single-endpoint advantage (federating data across microservices) and
note integration via an API gateway. Limitations include increased complexity in managing
public/private API routing and reliance on specific code-generation tooling.

14
M. N. Alzamzami et al., [6] introduce a GraphQL-based tool to scaffold backend services
with built-in CRUD operations, authentication, and authorization. The tool uses schema-
driven code generation to automate resolver creation and security wiring, reducing manual
coding. It generates GraphQL schema and resolvers and integrates attribute-based access
control policies directly into the queries. A key contribution is streamlining GraphQL API
development by encapsulating common patterns (user roles, resource permissions). The
authors claim the tool significantly reduces boilerplate for CRUD and auth, though details
on limitations are sparse.

G. Mavroudeas et al., [7] propose a machine-learning approach to estimate GraphQL query

cost. They extract query features (field counts, nesting, and graph embeddings) and train an
ensemble of regressors. The framework is evaluated on real GraphQL logs (e.g. GitHub and
Yelp APIs) to predict execution cost. Results show that the ML model achieves high
accuracy, substantially outperforming prior static worst-case estimators. This enables
providers to better gauge query complexity before runtime. The authors note, however, that
training requires representative query-response data and that the model may need retraining
for different schemas.

C. M. Novac et al., [8] perform a comparative study of front-end applications built with the
Vue.js versus React.js frameworks. They developed similar demo apps in both frameworks
tso that they can access the differences in performance and developer effort. Metrics such as
rendering speed, code complexity, and bundle size are compared. The findings suggest that
React’s virtual-DOM approach offers marginally better runtime efficiency, while Vue’s
lightweight design eases development and reduces initial load. The authors note trade-offs
but emphasize that both frameworks serve modern web needs, with choice often depending
on project context. The study is limited by its narrow scope of examples.

A. Javeed et al., [9] investigate performance optimization techniques for ReactJS

applications. The paper identifies common pitfalls such as unnecessary re-renders and heavy
component updates, and examines techniques like memoization (React.memo/useCallback),
lazy loading, and code-splitting to mitigate them. Using benchmarks and literature review,
15
Javeed demonstrates that applying such optimizations can significantly reduce rendering
time and improve responsiveness. The study reports enhanced application performance
under load, but also cautions that benefits depend on profiling and specific use cases, as
optimization effects may vary across scenarios.

L. Liang et al., [10] describe an “Express Supervision System” built with AngularJS on the
front end, Node.js/Express on the back end, and MongoDB for data storage. The system
targets logistics tracking (e.g. express delivery) with real-time data visualization. The
approach leverages Node.js’s asynchronous model and MongoDB’s document store to
handle high-throughput data. The authors report efficient performance for their prototype
and note that using a full JavaScript stack simplified development. The study’s scope is
limited to this specific implementation and does not evaluate scalability under large user
loads.

2.1.1 Table Stating Objectives Of Various Research Papers Analysed During Our Research
On This Project

Table 2.1 Literature review

S. No. Paper Title Journal/ Tools/ Results Limitations

[Cite] Conference Techniques
(Year)

1. Web ICAC3N ReactJS Faster, Hard to learn,

Development (2023) efficient, needs extras.
Using ReactJS reusable, user-
friendly.

16
2. Crowd ICWT Node.js, Real-time Data
Monitoring (2023) Redis, IaaS, monitoring, consistency,
System Using WebSockets scalable, reliability
Nodejs efficient, under load
responsive

3. Full-Stack IEEE (2023) React, Integrates Personal blog,

Web GraphQL, headless CMS lacks peer
Development Apollo with GraphQL review.
with GraphQL Client, Full- in React.
and React: Stack
Taking React Development
from frontend
to full-stack
with GraphQL
and Apollo .

4. Vulnerability IJISRT GraphQL, Identifies Focuses on

Analysis of (2023) React.js, security issues security,
GraphQL APIs Security in GraphQL- limited
After Tools, React performance
Integration integration. benchmarks
with React.js

5. Implementatio ICIMTech RESTful GraphQL is Complex;

n of REST API (2022) APIs, flexible and REST can
vs GraphQL in GraphQL, efficient; REST over-fetch
Microservice Microservice is simple and and require
Architecture Architecture, widely used. many
API Gateway endpoints.

17
6. GraphQL- ICoDSE GraphQL Efficient Customizatio
based (2022) backend service n for complex
Development with auth auth
Tool for CRUD
Operations,
Authentication,
and
Authorization

7. Learning ASE (2021) GraphQL Optimized Limited to

GraphQL GraphQL query query
Query Cost cost estimation complexity
analysis

8. Comparative EMES Vue.js , Reactjs uses Vuejs

study of some (2021) React.js virtual DOM application
applications while Vuejs cannot scale
made in the uses under load
Vue.js and lightweight
React.js method
frameworks

9. Performance ICECCT JavaScript, Faster ReactJS Requires

Optimization (2019) React, JSX, performance expertise,
Techniques for State complex
ReactJS Management setup.
, Lifecycle
Methods

10. Express ICIS React, Scalable Handles up to

Supervision (2017) Node.js, ,efficient data 100
System Based Express.js,

18
 on NodeJS and GraphQL, storage and concurrent
GraphQ React Hooks analysis users

2.2 KEY GAPS IN LITERATURE

2.2.1 FRAGMENTATION IN EXISTING TOOLS

A recurring theme in the literature is the fragmentation of tools to support educators. Most
of these systems do not offer a solution encompassing all aspects but tend to focus on one
single facet of teaching, like lesson planning, grade administration, or communication with
parents. It obliges teachers to operate different systems, which is inefficient and makes
teachers' work more challenging. A significant proportion of works have recognized the
problem at hand that several studies have not been made on how to integrate these
multifaceted technologies into an encompassing system that would rationalize workflows
and meet the diversities of instructional demands; however, educators are struggling to find
ways to better streamline their work and maximize collaborative efforts without having to
use extra effort because there lacks a centralized platform.

2.2.2 LIMITED FOCUS ON GLOBAL CURRICULUM ALIGNMENT

An another gap in the literature which emerges is that of lack of focus on resources that
actually support international curricula in terms of national frameworks and for instance,
Cambridge International and The International Baccalaureau. Most of today's research
focuses on curricular alignment regarding specific educational systems or places where
geographical boundaries blur the fact that tools needed an adaptation flexibility to fit
divergent standards around the globe.

19
This would remove from the concerns of educators and schools the global focus in
multicultural or multinational settings. What is needed to learn about how the tools can
support multiple curricula implementation without compromising the usability or flexibility
is further research projects to be developed.

2.2.3 CHALLENGES IN COLLABORATION AND COMMUNICATION

While most tools and platforms may lack the simplicity to help the educators, learners, and
families communicate with one another even though cooperation among these people is what
makes education effective, there is research that shows the majority of the platforms provide
only one of the two main areas: teacher-teacher cooperation or parent-student
communication. In addition, there is a lack of information in the literature on real-time
collaboration capabilities, such as sharing resources, co-editing lesson plans, and receiving
immediate feedback. The following gap thus emerges in this context: the need to provide all
process participants with user-friendly, permission-based collaborative tools.

2.2.4 USABILITY AND ADOPTION BARRIERS

A big challenge related to educational technology usage and often mentioned in research has
been the difficulty of acquiring user adoption. Most the tools either lack depth to keep up
with experienced teachers' needs or are too advanced for an educator not computer-savvy.
Balancing usability and usefulness interfaces in the literature are often overlooked and not
given attention to. This is highly critical, especially for teachers who might not have too
much time or confidence when handling new technologies. The teacher-centric approach has
received very little attention about this approach, and with the end result, there are hardly
any solutions regarding how to provide a friendly, accessible multiuser platform.

2.2.5 OVERLOOKING TEACHER WELL-BEING

Administrative workload is the last area with regard to which little is paid for the impact it
has on the wellbeing of teachers. Rare research address the potentiality of planning tools to
reduce the emotional stress of educators in improving work-life balance though most studies

20
suggest being productive and efficient. Human elements of teaching are often not addressed
but instead, more technical fixes are suggested without bearing much to mental or emotional
wellbeing.

21
 CHAPTER 3: SYSTEM DEVELOPMENT

3.1 REQUIREMENTS AND ANALYSIS

An intensive requirement analysis is essential to the success of the Toddle Planning Module
because it guarantees that the end product will meet user expectations, institutional
objectives, and technical possibilities. It fills the gap between overall project objectives and
in-depth design, leading the development process through concrete, usable knowledge.
Through a study of the needs of all the main stakeholders - teachers, administrators, students,
and families - the project lays a sound foundation for the development of a solution that is
practical, user-friendly, secure, and flexible to meet different educational environments.

3.1.1. FUNCTIONAL REQUIREMENTS

The core functionality of the module is enhancing the learning and teaching process through
effective planning, management, and teamwork features.

1. UNIT PLANNING

a. Creation and Management Tools Offer easy-to-use tools for creating, editing,
and managing curriculum-mapped teaching units, allowing teachers to easily
create thorough learning experiences.

b. Global Framework Compatibility: Support globally recognized frameworks

like the International Baccalaureate (IB) to provide relevance and adaptability
of the system in different learning environments.

c. Collaboration and Permissions: Provide support for teachers, students, and

families to share units and set permissions securely to provide collaborative
planning with privacy and security.

22
2. CLASS PLANNER

a. Calendar-Based Scheduling: Provide an adaptable, calendar-based system to

facilitate educators in scheduling and planning their teaching calendar
throughout the academic year.

b. Responsive Schedule Allocations: Facilitate the capacity to alter and adapt

schedules promptly in response to shifting classroom dynamics, celebrations,
or unforeseen events.

c. Curriculum Alignment: Seamlessly integrate with unit planning, such that

class calendars coordinate with the overall curriculum goals and objectives

3. CLASS FLOW MANAGEMENT

a. Objective and Transition Management: Provide tools for charting and

tracking daily class objectives to enable transitions among subjects to be
efficient and significant.

b. Activity Planning: Support daily planning of activities against long-term

education goals, promoting meaningful teaching activity and alignment of
teaching activities within the overall learning plan.

4. RESOURCE CENTRALIZATION

a. Centralized Storage: Provide a centralized space for storing and keeping track
of resources such as assignments, notes, and links, which are available to
teachers, students, and families.

b. Effective Access: Enable resources to be easy to locate and access,

minimizing the time it takes to locate appropriate teaching materials.

23
 5. COLLABORATION TOOLS

a. Real-Time Communication: Allow instructors to communicate and give

feedback in real time, improving collaboration and idea exchange.

b. Family and Student Engagement: Make it easy for families and students to
get engaged, enabling them to engage with plans, resources, and progress,
ensuring an integrated approach to education.

3.1.2 NON-FUNCTIONAL REQUIREMENTS

In addition to functional capabilities, the system must meet certain non-functional criteria to
ensure usability, performance, security, and scalability.

1. USABILITY

a. Simple User Interface: The system should have a user-friendly interface,

easy and intuitive, with minimal learning curve for the teachers and other
users. it should not need a lot of training to use.

b. Device Accessibility: Make sure the platform can be accessed by a variety

of devices, desktops, tablets, and smartphones, so the teachers and students
can access the system anywhere.

2. PERFORMANCE

a. High Concurrent User Support: The platform should be able to support

several users at the same time without any compromise on performance and
efficiency, so the system operates smoothly at peak usage times.

b. Fast Response Time: The platform should support fast response times for
operations such as plan creation, editing, and data retrieval to increase
efficiency and user satisfaction.

24
 3. SECURITY

a. Strong Permission Control: Enforce solid permission controls to protect

sensitive educational information and lesson plans, enabling the assignment
of who is able to access or edit given content.

b. Data Encryption: Make all data, such as communication and stored assets,
encrypted to keep user information private and untouched.

4. SCALABILITY

a. Future-Proof Integrations: Design the system extremely integratable with

future frameworks, tools, or functionalities such that it is extremely flexible
to evolving educational requirements.

b. Flexibility to Educational Models: The system must be flexible enough to

accommodate different educational models, including traditional
classrooms, distance learning, and blended models, with flexibility for
different teaching environments.

3.1.3 USER ANALYSIS

1. PRIMARY USER

a. Teachers: Teachers need a set of tools that allow them to plan lessons, share
ideas with other instructors, and effectively schedule their classrooms.
These tools should allow them to stay organized, save time, and focus more
on the quality of education.

b. School Administrators: Administrators require tools through which they can

observe and manage the curriculum, checking that all goes well. Such tools
must be able to check whether all the lessons align with the objectives of the
school and whether the process of teaching is efficient and effective.

25
 2. SECONDARY USER

a. Students: Students have an advantage of being able to have all of their work,
schedules, and study materials on a single centralized platform where they
can retrieve all of them at ease. This becomes simpler for them to manage
since they can do it all from one location.

b. Families: Families wish to remain updated and engaged with their child's
learning. They require an option for monitoring their child's progress,
checking assignments, and interacting with instructional content.

3.2 PROJECT DESIGN AND ARCHITECTURE

The Planning Module's design revolves around an easy-to-use and straightforward flow to
improve the efficiency of educators and ease their planning process. The architecture of the
project is hierarchical and modular, with ease of movement from one functionality to another
while preserving clarity and ease of access. A step-by-step description of the design
according to the given diagram follows:

Fig 3.1: Unit Planning in Planning Module Architecture

26
In the Fig 3.1 The image shows the users' flow diagram of the Educational Platform, which
begins from the "Login." After successful "login," the user receives the "Dashboard" wherein
to select a class, later the "Class Overview page," which is considered central hub. From the
Central hub, users can use further Class Units, Planners, Timeline, Calendars, Assignments,
Progress reports, and More Features. All these areas provide unique features such as
maintaining class material, scheduling activities, monitoring timelines, viewing assignments,
and tracking progress reports, guaranteeing a unified and well-planned experience for the
students as well as educators.

3.2.1 HIGH-LEVEL FLOW

The system begins with the Login module to give secure and authenticated access to the
users. Teachers log in using their credentials and are able to view their respective dashboards.
The Dashboard has been utilized as the highest level for all the navigation that offers an
overview of classes, tasks, and other key features. This single portal allows teachers to
quickly choose a class and become immersed in its particular planning and management
features.

After a class is chosen, the user is brought to the Class Overview page, the portal to all class
features. The Class Overview provides users with an overview of the class with links to
important modules like unit planning, timelines, and progress tracking. This hierarchical
sequence from login to class tools is simple and convenient for the user.

3.2.2 CORE MODULES

Following class, users are offered the Class Overview page. The Class Overview page serves
as a summation of all the essential pieces related to that class. The page connects to several
crucial modules that allow granular management of unit planning, resource organization, and
monitoring progress.

The Planning Module is designed around seven core features that address various critical
aspects of teaching and class management:

27
1. CLASS UNITS : This module empowers the teacher to create, edit, and manage
curriculum-compliant units. It is quite specifically attuned to frameworks like IB,
thus ensuring curriculum adherence to international standards. Teachers may share
their plans with colleagues, students, and families without compromising on security
while having very granular control over permissions; therefore, collaboration is
fostered.

2. PLANNERS : The Planner module is based on a calendar view for the planning of
yearly and weekly schedules. Teachers can link their lesson plans to unit objectives,
tweak them, and ensure that they are on track with their plans. It helps link long-term
goals with everyday activities in the classroom, but maintains structure and
flexibility.

3. TIMELINE :The module helps in visualizing activities and transitions through

objectives on the timeline. This helps a teacher to view how they progress with
lessons, follow milestones, and make any adjustments so that lessons could be
presented coherently.

4. CALENDARS :This is centralized scheduling that provides the key dates and
deadlines of what is done, and all of these, by one glance, will offer a shared view to
teachers, students, and families alike.

5. ASSIGNMENTS : This is the Assignments module that allows the teacher to create,
manage, and track homework, assessments, and other tasks. This feature streamlines
the process of assigning and monitoring work, ensures deadlines are met, and reduces
administrative overhead.

6. PROGRESS REPORTS :A student's performance and what is taking place in the

classroom are revealed by a progress report. This module generates detailed analytics

28
 and visualizations that can be shared with students and families for learning and
participation.

7. MORE FEATURES : The system is designed to be extensible, and this is a holding

place for future extensions. Advanced analytics, notification, and integration are
features which are possible to add later as the system continues to develop.

3.2.3 MODULAR AND SCALABLE DESIGN

Its design is modular in nature, so that every feature is independent and can operate in
isolation. Because it is modular, it becomes scalable as it can have additional features or new
improvements added to it without harming the existing capabilities of the system. For
example, additional curriculum frameworks, analytic tools, or third-party platform
integrations can be added into the system without harming its existing capabilities.

3.2.4 USER-CENTRIC NAVIGATION

The system possesses user-focused hierarchical flow. With room for overview and rapid
access to the most important features, the Dashboard will serve as a pivot. Users can then
drill down into specific classes from the dashboard in order to find complete resources
according to their requirements. Even for users not very proficient in technology, the
intelligent layout of the system makes it easy and simple to use.

3.3 IMPLEMENTATION

The project's implementation makes for a solid and efficient application using the latest
scalable tech stack. Frontend development, which is component architecture-based, employs
ReactJS [1] for providing the ability of reuse for UI design. Redux is employed for state
management for creating centrally controlled and predictable application state. To improve
performance and eliminate unnecessary network requests, Apollo Client is also brought to
the frontend to fetch, cache, and handle data from the backend GraphQL API. The backend

29
is driven by Apollo Server, which simplifies data querying and mutation operations.
Structured data is cached in a PostgreSQL [5,7] relational database. SASS [2] handles the
styles so that one can leverage advanced CSS features and assure reusability and
maintainability of the design. In combination, these technologies generate a streamlined
architecture in which the database takes on complicated relationships and queries and
frontend and backend interact in the right way to produce an application that is both scalable
as well as easy to use.

The frontend structure of Toddle Planning Module is developed over ReactJS, a

contemporary JavaScript library that provides the ability to create dynamic, responsive user
interfaces using its component-based structure. This makes it possible for the developers to
split complex UI parts into smaller ones, which are reusable, having their own presentation
and logic within them. Through this modular design of the application, the codebase is more
scalable and maintainable, thus it is simpler to add or modify features without affecting the
whole system. The virtual DOM implementation in React ensures efficient rendering by
minimizing direct manipulations of the browser's DOM, resulting in smoother performance
even when dealing with data-intensive operations like calendar scheduling or resource
management.

State management is handled through Redux, which provides a predictable state container
for JavaScript applications. Redux maintains the application state in a centralized store,
making it accessible to all components while ensuring consistency across different parts of
the interface. This becomes increasingly relevant in an educational planning system where
various perspectives may require access to the same information. For instance, student
progress or lesson plans. Application of Redux middleware such as redux-thunk allows the
frontend to manage asynchronous operations without any issues, e.g., backend GraphQL
server API calls. This structure ensures the state updates are managed in a predictable and
controlled way, allowing race conditions to be avoided and application behavior to be more
predictable.

Data fetching and handling are maximized by Apollo Client, which acts as a mediator
between the React client and GraphQL server. It offers smart caching feature, storing query
results in local cache and refetching only the data which is soon to be updated.This reduces
network load significantly and makes the application feel snappier. The client also gracefully
manages error states by rendering fallback UI in the case of request failures and

30
automatically retrying queries upon improvements in the network. The integration of Apollo
Client and React's context API enables effective prop drilling, reducing unnecessary re-
renders while components remain decoupled and manageable.

The user interface is structured with accessibility and cross-device support in mind as the
key considerations. Semantic HTML attributes and ARIA roles are employed consistently
throughout to make the application accessible with assistive technology. Responsive design
guidelines are practiced through a blend of CSS Grid and Flexbox, enabling the interface to
seamlessly respond across various screen sizes from desktop monitors to mobile phones.
Media queries allow layout changes to occur at suitable breakpoints, and touch-friendly
controls enable the application to be used on tablets and smartphones. Performance
optimizations such as code splitting and lazy loading are utilized to minimize initial load
times, particularly valuable for users with slower network connections.

Styling is managed through SASS, a CSS preprocessor that brings powerful features like
variables, mixins, and nested rules to the stylesheet architecture. This enables the creation of
a consistent design system where colors, spacing, and typography can be defined once and
reused throughout the application. SASS's modular structure is similar to React's component-
based structure, with each big component having its own style files that can be compiled into
optimised CSS during the build phase. CSS-in-JS methods used for dynamic styling
guarantee that components are self-contained, and their styles get properly scoped to avoid
leakage and conflicts.

The frontend build takes advantage of cutting-edge tooling such as Webpack and Babel to
build production bundles that are optimized. Tree shaking removes unused code, and
minification and compression shrink bundle sizes.The development environment includes
hot module replacement for faster iteration, along with comprehensive linting and type
checking (using TypeScript) to catch potential issues early. End-to-end testing with tools like
Cypress verifies critical user flows, while Jest and React Testing Library provide unit and
integration test coverage for individual components.

Authentication flows are implemented using industry-standard practices, with JSON Web
Tokens (JWT) for session management and secure HTTP-only cookies for token storage.
The frontend integrates with Auth0 for identity management, providing features like multi-
factor authentication and social login while abstracting away the complexity of secure
credential handling. Permission checks are performed both client-side (for UX
31
responsiveness) and server-side (for security), ensuring users only see and can interact with
features appropriate to their roles.

Real-time features, such as collaborative editing of lesson plans, are enabled through
WebSocket connections that push updates to all connected clients. Conflict resolution
strategies ensure data consistency when multiple users edit the same resource
simultaneously. The frontend employs optimistic UI updates to make interactions feel
instantaneous, with reconciliation logic to handle cases where the backend rejects changes.

Error handling and logging are done thoroughly, with friendly error messages shown when
operations go wrong. Sentry integration gives real-time error monitoring in production, while
thorough logging assists in diagnosing issues during development. Performance metrics are
gathered and analyzed through tools such as Lighthouse, with ongoing monitoring to spot
and fix bottlenecks.

The development workflow emphasizes code quality and consistency. Pre-commit hooks run
linters and tests automatically, while pull request reviews ensure changes meet project
standards. Documentation is generated from code comments using tools like Storybook,
which also serves as a living style guide and component library. This rigorous approach to
frontend engineering results in an application that is not only functional and performant but
also maintainable and adaptable to future requirements.

3.3.1 FRONTEND

It's built using ReactJS. This is a library that is well regarded, again because of its architecture
on components and virtual DOM efficiency. Using ReactJS, developers can break up the UI
into reusable pieces in order to create highly interactive and dynamic user interfaces [1]. This
modular approach both simplifies the development process but also ensures that it will
remain maintainable as well as scalable enough to ensure future enhancements. Clean
separation of concerns; It encloses each feature functionality into its own component such as
navigation bars forms, and data tables.

With Redux, application-wide states are centralized and managed using a centralized store,
so that everything stays consistent in all the components. With the usage of Redux
middleware like redux-thunk, asynchronous operations like API calls are efficiently handled
by the frontend so that interaction with the GraphQL [3] backend is seamless. Data fetching,
32
caching, and error handling are also optimized by the use of Apollo Client so that the
application is both performant and responsive.

The application is compatibility for desktop, tablet, and smartphone. It provide users with
great user experience. Using the ARIA roles and semantic HTML, we enhanced accessibility
and assistive support for diverse user needs. High quality and ease of use are assured by this
solid frontend implementation. Accessibility forms a fundamental consideration throughout
the interface design. Semantic HTML provides meaningful structure for assistive
technologies, while comprehensive ARIA attributes communicate dynamic interface
changes to screen readers. Keyboard navigation follows logical patterns that mirror visual
flow, with careful focus management ensuring users always understand their position within
the application. Color contrast ratios exceed WCAG standards, and interactive elements
include visible states for hover, focus, and active interactions. The application is
continuously tested for accessibility using automated tools and manual testing with assistive
technologies.

Performance optimization seeps into every aspect of the frontend implementation. React's
memoization strategies avoid unnecessary re-renders, and code splitting means users only
download the JavaScript needed for their current task. Critical rendering paths are optimized
by prioritizing resources carefully - loading critical interface elements first, followed by
gradually adding more features. The build process employs advanced techniques like tree
shaking and module concatenation to minimize bundle sizes, with differential serving
delivering optimized code based on browser capabilities.

Real-time collaboration features represent one of the frontend's most advanced capabilities.
Operational transformation algorithms enable concurrent editing of lesson plans, with
conflict resolution preserving user intent when multiple educators make simultaneous
changes. Presence indicators show who else is viewing or editing documents, while live
cursors and selection highlights facilitate visual collaboration. These aspects blend
harmoniously with the application's state management so that all participants experience
uniform updates irrespective of their connection quality.

Error recovery and resilience features produce a strong user experience even in less than
optimal situations. The interface uses optimistic updates to keep responsiveness even in
network activities, with extensive reconciliation logic resolving possible conflicts. Graceful
degradation makes core functionality available during service disruptions, with operations
33
queuing up and synchronizing automatically when connectivity comes back. User-facing
error messages provide clear, actionable information without technical jargon, while detailed
error reports help developers identify and resolve issues quickly.

Authentication and authorization flows integrate tightly with the frontend architecture. Role-
based access control determines interface visibility and capabilities, with permissions
evaluated both client-side for immediate feedback and server-side for security. The
authentication mechanism is capable of supporting various credential types, such as
institution-level single sign-on and two-factor authentication, both of which are done with
best-security practices. Session management keeps user context between browsing sessions
and guards against cross-platform weaknesses.

Analytics instrumentation provides valuable insights into usage patterns without violating
user privacy. Carefully calibrated event tracking records valuable interactions without
personal data, allowing institutions to discover how teachers utilize the planning tools.
Performance metrics also monitor real user experience which indicating where optimization
is required. These analytics feed continuous improvement cycles, with the application
evolving to meet changing needs.

3.3.2 GRAPHQL

GraphQL is the spine of data communication in this project, replacing REST APIs with a
more efficient and flexible querying system. With REST, one usually suffers from over-
fetching or under-fetching. GraphQL [3], on the other hand, enables the clients to request
only specific fields of data. Performance is enhanced and network overhead is decreased.

The backend utilizes GraphQL queries and modifications are done through the utilization of
Apollo Server [4,6]. With the utilization of system design skills, and efficient processes like
filtering, sorting, and pagination. Resolvers are utilized in the execution of these queries and
to access the database for ensuring proper and efficient retrieval of data. The utilization of
Apollo's built-in caching system also adds efficiency, as it reduces redundant requests [6].

Apollo Server forms the backbone of our GraphQL implementation, providing a production-
ready framework for building and deploying the GraphQL API. The server implementation
follows best practices for schema design, organizing types into logical domains while

34
avoiding common anti-patterns like overly nested structures. Resolver functions hold the
business logic for retrieving and converting data and are the intermediary between GraphQL
operations and different data sources. Resolver functions apply effective data loading
patterns like batching and caching to avoid performance bottlenecks when resolving complex
queries.

The other advantage is that when there are changes on the back-end, real-time data updates
in dashboards and other front-end updates are possible using GraphQL, as its capabilities of
subscription allow it to provide real-time updates. GraphQL is an extremely efficient tool in
the development of modern applications since it simplifies procedures in managing and
debugging APIs using a single endpoint for all actions.

Mutation operations exhibit a predictable pattern intended to guarantee data integrity for all
modifications. Every mutation takes explicit input types that validate parameters prior to
processing, and delivers explicit payload types that contain the altered data along with any
appropriate metadata. The pattern ensures it is simple for clients to know and process results
of their changes. Mutations also coordinate with the system's authorization layer, checking
permissions prior to processing any modifications to sensitive education data.

Performance optimization is a key consideration throughout the GraphQL implementation.

The query execution engine includes several layers of caching, from memoization of resolver
functions to a persisted query cache that stores optimized execution plans. Query complexity
analysis blocks overly costly operations from overwhelming the server, and depth limiting
guards against abusive queries. Intelligent query whitelisting is also deployed in production
environments by the system to boost security and performance.

The GraphQL API is connected to a range of different data sources via a modular data access
layer. Master data exists in PostgreSQL, with the GraphQL resolvers taking advantage of the
database's sophisticated features such as JSON columns and full-text search where
necessary. For certain high-read, low-write data like curriculum standards, the system
employs Redis as a secondary cache to reduce database load. The data access layer also
manages connection pooling and transaction management to ensure optimal resource usage
in all GraphQL operations.

Error handling also follows predictable patterns across the GraphQL implementation. Instead
of using HTTP status codes, the API exposes errors via a uniform error format in GraphQL

35
responses. This entails rich error classifications that enable clients to respond appropriately
- whether a validation error should be presented to the user or a system error needs
administrative review. The error format also includes machine-readable codes that enable
sophisticated client-side handling of common scenarios.

Security forms a critical aspect of the GraphQL implementation. The API implements
multiple layers of protection, beginning with thorough input validation against the schema.
Authentication integrates with the system's identity provider, with JSON Web Tokens
carrying authorization context through the request pipeline. Permission checking occurs at
both the operation level and the individual field level, ensuring users can only access data
appropriate to their roles. The implementation also includes safeguards against common
GraphQL-specific vulnerabilities like introspection attacks and query depth exploits.

3.3.3 SASS

The project uses SASS (Syntactically Awesome Stylesheets) for the creation of a scalable
and maintainable styling architecture. SASS is the CSS preprocessor. SASS provides
variables, nested rules, mixins, and inheritance capabilities on top of the current CSS. SASS
is new way of writing css.

We have defined global variables for colors, fonts, and spacing, which helps in creating a
design system. For example: the primary and secondary colors used in buttons, headers, and
links are reused across the application, thus making it look and feel similar. Nested rules
enable the styles to be scoped for specific components, avoiding conflicts and improving
readability.

Mixins are used to declutter the reusable pieces of code, for example, to define responsive
breakpoints or buttons styles which can be commonly applied on multiple components
thereby reducing duplication and speeding development. Finally, SASS partials are used by
organizing the styles into little manageable files that corresponded to every component or
feature. It improves maintainability and ease of collaboration within developers.

By using SASS, the project is looks very professional. The user interface is responsive which
fits very well on any device resolution.

36
3.4 KEY CHALLENGES

The evolution and application of the Planning Module in Toddle are accompanied by a set
of challenges that have to be faced to make the system efficient, effective, and responsive to
teachers' needs. These challenges cross technical, functional, and user experience domains
and need innovative responses to provide an effective and smooth planning platform to
teachers and schools. Below are some of the key challenges faced during the project:

1. INTEGRATION WITH EXISTING SYSTEMS AND DATA SOURCES

a. One of the most significant challenges in designing the Planning Module is

integrating it with existing school management systems, curriculums, and
educational tools. Learning management systems (LMS), administrative
software, and student information management are some of the numerous
systems that most schools use for different purposes. Proper preparation and
robust API interaction are required to ensure that the preparation Module can
interact with these systems without creating data fragmentation or duplication
of effort.

b. A further degree of complexity is introduced when the module has alignment

with international educational schemes such as the International
Baccalaureate (IB). The module will need to be adaptable and versatile
enough to satisfy different educational standards globally since the system
will have to accommodate numerous curricula and their respective structures.

2. ENSURING SEAMLESS COLLABORATION

a. The Planning Module's main objective is to encourage the cooperation

between teachers, students, and families. But establishing a smooth climate
for collaboration has its own set of difficulties. Teachers need to work
together on curriculum design, lesson planning, and assessment strategies, but
they must also control what information is shared and with whom. Balancing
this level of collaboration - while maintaining privacy, security, and control

37
 over sensitive data - requires the development of a highly customizable and
robust permissions system.

b. In addition, the balance between ease of use and usefulness is difficult to

achieve while providing basic communications tools and ensuring parents and
children are able to communicate with the system without experiencing
unnecessary complexity.

3. USER EXPERIENCE AND ADOPTION

a. Although technical function of the Planning Module is ease of use by teachers

are even more essential to adoption. Teachers do not have enough time, and
therefore they will only embrace new technology if it's simple and easy to
operate. The challenge lies in creating a system that's simple to use but not
at the expense of functional breadth to facilitate effective planning.

b. A good onboarding, teamed with a simple, uncluttered design, is the solution

to this issue. The system needs to be accessible to users with varying levels
of technological proficiency, so a smooth and engaging user experience is
paramount. Additionally, providing ongoing support, training resources, and
user feedback channels will be necessary to ensure the system is continuously
improved and adapted to user needs.

4. SCALABILITY AND FLEXIBILITY

a. Schools everywhere have differing classroom arrangements, curriculum

requirements, and procedures, and educational needs are extremely varied.
Perhaps the largest challenge is making the Planning Module both scalable
and flexible enough to serve so many disparate needs.

b. New modules, features or integration will need to be supported by the system

without breaking existing workflows. For example, the system will need to
remain flexible enough to accommodate changes in curriculum designs or
pedagogical practices. Another key issue that will have to be solved is

38
 achieving a balance between scalability and performance so that the module
can efficiently process large datasets and large user volumes with fast
response times.

5. DATA PRIVACY AND SECURITY

a. Data privacy and security are important because of the information that is
being handled which includes students, teachers and academic data. Schools
must be governed by strict data privacy laws, including the General Data
privacy Regulation (GDPR) and the Family Educational Rights and Privacy
Act (FERPA).

b. Implementing strong security features and maintaining usability is the tricky

part. Most important design aspects include encrypting sensitive data,
implementing multi-factor authentication. We have also added secure data
storage and securing transmission using the latest tech. The instructors can
manage the user data and user permissions.

6. REAL-TIME UPDATES AND SYNCHRONIZATION

a. Another challenge is providing real-time updates and synchronization across

multiple users. Teachers may collaborate on unit planning, schedules, and
assignments, and any changes made by one user should immediately reflect
for all others. Ensuring seamless real-time synchronization of data across
different platforms (desktop, tablet, mobile) without performance lag is
another technical challenge. Our users are working across different devices
and time zones which makes it more difficult to handle.

b. This requires an efficient backend system capable of handling concurrent

updates without losing data integrity or introducing errors.

39
7. CUSTOMIZATION AND PERSONALIZATION

a. Each teacher is different in their lesson planning and organization needs.

Some teachers like it when there is more detail in their lesson planning while
others prefer simple and flexible plans. This is very difficult to achieve as it
will make the entire system complicated.

b. Offering editable templates, variable calendar views, and permission to

customize features to individual preferences will enable users to customize
the system to their particular teaching styles. Too much choice, however,
creates confusion and increases the complexity of the user interface, and
balancing flexibility and simplicity is thus crucial.

40
 CHAPTER 4: TESTING

4.1 TESTING STRATEGY

The Planning module testing in Toddle ensures there is a secure, bugless user experience.
Post-development phase, dev testing is performed as an initial layer of validation. During
this, developers assure that the module functions as one would expect using the unit tests and
manual tests which will run on key functionality. Testing has to be done before deployment.
All the features should be tested so that it is working as expected.

The testing strategy for the Toddle Planning Module follows a comprehensive, phased
approach to ensure the system meets all functional requirements while delivering a seamless
user experience. Beginning with developer testing, the process starts immediately after the
development phase as an initial validation layer. Developers conduct unit testing to examine
individual components in isolation, using frameworks like Jest for frontend React
components and Mocha/Chai for backend Node.js services. These tests verify core
functionality including lesson plan creation workflows, calendar scheduling algorithms,
permission management for resource sharing, and data validation for curriculum standards.
Alongside automated unit tests, developers perform manual smoke testing on key user flows
to validate basic functionality before proceeding to more rigorous testing phases.

After the unit testing has been successfully conducted, the system is subjected to yet another
testing, which is integration testing to confirm how various modules communicate with one
another. The API endpoints between the frontend and backend are here focused on in order
to enable smooth data passing throughout the application. Integration tests validate critical
interactions such as how lesson plan updates propagate to student dashboards and how
calendar changes affect resource availability. The testing team uses tools like Postman and
Supertest to simulate various scenarios and edge cases, paying particular attention to data
consistency and error handling across integrated components. This phase helps identify and
resolve issues that might emerge when individual units are combined into a complete system.

System testing represents the next critical phase, where the complete application is evaluated
against all specified requirements. Testers execute end-to-end scenarios that mimic real-
world usage patterns, covering all user roles including teachers, students, and administrators.

41
Performance testing forms a crucial part of this phase, where the system is subjected to load
testing to verify it can handle expected concurrent users without degradation in response
times. Security testing is conducted concurrently, examining authentication flows, data
encryption, and role-based access controls to ensure compliance with educational data
protection standards. The system testing phase also includes compatibility testing across
different browsers and devices to guarantee consistent user experience.

User acceptance testing (UAT) serves as the final validation before deployment, involving
actual end-users from the target audience. Selected teachers and administrators work with
the system in a controlled environment, performing their typical workflows while providing
feedback on usability and functionality. This stage not only confirms whether the system has
technical specifications but also whether it complies with actual educational workflows and
expectations. UAT sessions are well-documented, with all the issues found categorized by
severity and resolved based on their potential effect on user experience.

Regression testing is done continuously throughout the development process. It is important

to perform it particularly after any significant changes or bug fixes. Automated regression
test suites guarantee a new updates do not introduce any unexpected side effects or disable
existing functionality. These tests are run as part of the continuous integration pipeline,
which provides feedback to developers in real time. The testing strategy which also includes
continuous testing and monitoring post-deployment to immediately the identify and correct
any issues that occur in the production environment. This comprehensive approach ensures
the Toddle Planning Module delivers a stable, high-quality solution that addresses the
diverse needs of educational institutions with high performance and security features.

4.1.1 MANUAL TESTING

Manual testing plays an important role in ensuring the Planning module in Toddle in which
each feature is tested manually. The process begins during the staging environment, where
the QA team conducts detailed functional testing. QA engineers manually test all key
features, such as task tracking, calendar integrations, and centralized resource organization,
verifying they align with requirements. Exploratory testing is also employed to uncover edge
cases or unexpected behaviors that might not be covered by predefined test cases.

42
Usability testing is a significant aspect of manual testing. To ensure the module is easy to
use and easy to understand, QA engineers here emulate real user behavior. Also, manual
accessibility testing is performed, focusing on WCAG guidelines, ensuring functionality can
be accessed using only a keyboard, and checking readability of the content for everyone.

To ensure that the new module will not bring bugs into the existing functionalities, regression
testing is done. Our QA confirms that the system is stable. A smoke test is done after
releasing the feature. It checks the basic functionality of the application. It provides
assurance to the team that the feature is working as expected.

Data integrity testing is also a critical aspect of manual verification. Testers verify that data
entered into the interface correctly saves to the database and renders correctly in all relevant
views. This involves verifying that complex data relationships (e.g., lesson plans tied to
specific curriculum standards) maintain their relationships through all application states.
Individual test cases verify data synchronizing across multiple devices and browser
windows, maintaining consistency within collaborative environments.

Workflow testing investigates end-to-end flows that involve numerous features. Testers may
simulate a teacher's complete planning process, like creating a new unit, constructing lesson
schedules over weeks, adding resources, sharing with colleagues, and then finally publishing
to students. These sets of scenarios reveal integration problems between parts of the system
that might not be uncovered by using isolated feature tests.

Localization testing verifies the application's behavior with different language settings and
regional preferences. Testers check not only for proper text translation but also for correct
date/number formatting, text direction in right-to-left languages, and proper handling of
locale-specific educational terminology. This testing ensures the Planning Module meets the
needs of global educational institutions.

Performance evaluation during manual testing focuses on perceived responsiveness. Testers

assess whether the interface remains snappy during complex operations like loading large
lesson plans or searching through extensive resource libraries. While automated tests
measure technical performance metrics, manual testing captures the human experience of
using the application under realistic conditions.

The manual testing process concludes with a final sign-off procedure where senior QA
members verify that all critical issues have been resolved and the feature meets quality
43
standards for release. This includes confirming that all test cases have been executed, defects
have been properly triaged, and the release documentation is complete. Only after this
comprehensive validation does the feature progress to production deployment.

4.1.2 AUTOMATED TESTING

Automated testing is done so that it can cover all the test cases which might be missed in
manual testing. Also automated testing works faster than manual testing, so it can be done
faster. It all starts by using tools like Jest to check all the individual components. Jest is a
unit testing tool.

Once the module passes unit tests, integration tests are automated to verify that various
components work together seamlessly. These tests focus on interactions between the
Planning module, existing features, and external APIs, such as calendar integrations or
shared resources.

Cypress and Selenium frameworks are commonly used to automate testing. Automated
testing is helpful because it allows you to run tests on features that were previously working,
using the test cases which were written earlier. As all the application grows, testing every
feature manually becomes very hard for humans. It’s difficult to keep track of everything,
but automated testing can do this easily.

Integration testing builds upon unit tests by verifying how different parts of the system work
together. Automated integration tests will validate critical interactions between the frontend
components and the GraphQL API, ensuring that queries return the expected data structures
and mutations properly update the application state. These type of tests employ a
combination of mocking for external services and real connections to development
databases, striking a balance between test reliability and execution speed. Special attention
is given to testing the data transformation layer where GraphQL responses are converted into
the format expected by Redux stores.

End-to-end testing represents the most comprehensive automated testing layer, using
Cypress to simulate real user interactions with the complete application. These tests automate
browser interactions to validate complete user flows, such as creating a new lesson plan,
attaching resources, and publishing it to students. The Cypress tests run against a fully

44
deployed test environment, including all backend services and databases, providing
confidence that all system components integrate correctly. Visual regression capabilities
within Cypress automatically detect unintended UI changes by comparing screenshots
against baseline images.

The automated test suite includes specialized tests for performance-critical paths through the
application. These tests measure and assert acceptable response times for key operations like
loading a teacher's weekly schedule or searching through curriculum resources. Performance
tests run as part of the nightly build process, tracking metrics over time to detect gradual
degradation before it impacts users.

Accessibility testing automation complements manual accessibility reviews using tools that
scan rendered components for WCAG compliance issues. These kinds of tests check for
correct use of ARIA attributes, color contrast ratios, and support for keyboard navigation,
and marking issues related to accessibility early in the development process. These
automated checks do not substitute human review but ensure consistent standards for
accessibility across the application.

Test data management is an important aspect of the automated testing strategy. A special test
data generation system produces realistic data sets for different scenarios of testing, ranging
from small classroom to large-scale school rollouts. This has the effect of getting the tests
run through the application under conditions that are more real-world-like while delivering
predictable results.

The testing is done with extensive reporting capabilities that track test coverage, test time,
and pass/fail percentages over time. These metrics offer hints on flaky tests, performance
bottlenecks in the test suite itself, and areas of the application that need additional test
coverage. Integration with the team's project management tools automatically generates
tickets for newly found issues, thereby making the bug-fixing process streamlined.

Keeping the automated test suite is considered a first-class development task. The team
spends time refactoring tests as the application changes so that they remain stable and
maintainable. Test code is kept upto the same quality as production code, such as code
reviews and style enforcement. This rigorous process avoids test suite degradation and keeps
automated tests delivering value throughout the application's lifetime.

45
4.2 TEST CASES AND OUTCOMES

For the Planning module, testing begins with a single feature. There are several features such
as creating tasks, calendar integration, updating timelines, and resource management. For
instance, test cases involve whether tasks can be created and edited, testing drag-and-drop
functionality in the calendar, and ensuring unit plans can be shared securely.

To make sure everything works well, we also test edge cases like overlapping tasks, handling
wrong inputs, and multiple users updating things at the same time. Each test case is done
either manually or automatically. We already have the final result in advance. If anything
fails, it is send to the developer again for fixing the bug. For example, when a task is marked
as complete, all views should update to reflect the progress and send notifications as needed.

Resource testing targets the entire process of uploading, structuring, and sharing learning
material. Test cases ensure resources are uploaded with valid type checking and size limits,
tagged with proper metadata, and properly categorized. Sharing features are tested
extensively to ensure that permission controls function as expected - ensuring only
authorized users can access resources while keeping version control in check when updates
are made.

Collaboration features are tested with expert validation to ensure real-time synchronisation
for multiple users. Test scenarios involve having several teachers editing the same lesson
plan or changing the schedule at the same time to ensure that conflict resolution is
functioning correctly. The system is put under simulated different network conditions to
affirm graceful recovery from connectivity problems, and changes synchronise correctly
when connections are regained.

Error recovery and input validation are an important for test cases. They check that the
system correctly recovers from and handles invalid inputs, out-of-range values, and
malformed requests. The tests confirm that appropriate error messages are displayed to users
while preventing invalid data from persisting in the system. Security-focused test cases
validate that authentication and authorization controls are enforced consistently across all
operations.

Performance test cases measure system behavior under various load conditions. These
include tests for rendering large sets of data, handling multiple concurrent users, and

46
processing complex operations within acceptable time limits. The results are compared
against established performance benchmarks to identify any degradation in responsiveness.

Accessibility test cases check for conformance to WCAG guidelines through automated
scans as well as manual checks. They include keyboard navigation tests, screen reader
compatibility tests, and color contrast checks. The tests check that all interactive elements
are labeled correctly and that the interface is accessible with different assistive technologies.

Every test case that is run produces rich artifacts such as screenshots, network traces, and
performance statistics. These are saved along with the test outcomes to give full
documentation of the testing process. Failed test cases automatically generate bug reports
with all relevant diagnostic information, streamlining the debugging process for developers.

The test case repository is continuously updated to reflect new features and edge cases
discovered during testing. This living documentation serves as both a quality assurance tool
and a detailed specification of system behavior, helping to maintain consistency as the
application evolves. Regular reviews of test results identify patterns that may indicate
systemic issues or areas needing additional test coverage.

The results are carefully recorded. If a test case fails, it shows where there are issues or
mistakes, while successful test cases confirm that the features are working as expected. These
results help developers know what needs to be fixed and what should be tested further.

4.3 TEST RESULTS AND ANALYSIS

We carefully reviewed the test results to check if the Planning module is ready to be
released. During testing, we tracked important things like how many tests passed or failed,
how many bugs were found, and how serious those bugs were.

We prioritized the critical issues - particularly those that would make the system crash or
result in loss of important data. These types of issues were addressed first and resolved
immediately. Fixing issues early on prevents more complicated issues when the module is
implemented in real situations.

47
We were able to determine where parts of the module are still lacking due to the research.
For instance, if a feature did not act as expected, or resulted in unforeseen outcomes, we
noted that. This process is important in order to ensure everything functions according to
plan and meets the criteria.

We also considered the overall quality of the module. This meant considering whether
bugs had been successfully resolved and how quickly they had been done so. It is a good
sign that the module is stable if there were just minor issues and all of the major bugs had
been resolved.

The module can finally be approved for production if there are no major defects anymore
and the features work as planned. This means that it is ready for use in real-world
applications. A successful test outcome tells us that the Planning module is reliable and
meets the requirements since there are no major problems left.

48
 CHAPTER 5: RESULTS AND EVALUATION

5.1 RESULTS

The deployment of this project effectively offers a user-friendly, efficient platform that
combines a seamless frontend and a strong backend to meet the desired requirements. The
system performs high data fetching and display using GraphQL with low latency and
efficient data management. Redux state management, responsive user interface built using
ReactJS, and well-organized PostgreSQL database structure assist in delivering a scalable
and reliable solution[12,25]. The use of Apollo Client supports hassle-free data and SASS
communication that enhances the beauty of the user interface. Overall, the solution meets
users' needs with an effortless, scalable, and current application that can be easily supported
and extended.

Fig 5.1: Course Structure Teacher Account Navigation Flow

49
In fig 5.1 The image shows an organized Teacher Account Navigation Flow, starting with a
general Login Screen for all users of the system. Once they have logged in, users go to a
User Selection phase, during which they select their type: Teacher, Student, or Parent. The
choice sets the path that the user will take through the application. The drawing concentrates
directly on the teacher's navigation flow, which is specifically designed to facilitate course
and class management.

Once the user selects the teacher role, the user is in the Teacher Account interface. The.
instructor can. see All Courses they are currently working with or taking. here. From this
point, they can choose to. Select a Course in. order to learn more about particular. teaching
materials or course layouts. This is. an. access. to. more. detailed. course. information. and.
customization.

Once a course is chosen, the instructor is directed to the Course Details page. This page gives
access to the Course Flow, which describes the organization and sequence of course material.
In addition to this, the Associated Classes feature lets the instructor see and arrange the
groups of students assigned to the course. These features allow teachers to tailor their
instructional method to class-specific demands.

To even more effectively enable course management, the interface includes a sequence of
Course Flow Views. These include a default Course Flow View, a Card View to show
content in bite-sized cards, a Timeline View to organize content in chronological sequence,
and a Table View for a more data-centric presentation. These varied points of view allow
instructors to engage with the content in the manner best suited for their instructional and
organizational approach, and the platform becomes versatile as well as accessible.

In fig 5.2 This image displays my Teacher Account homepage on the course planning
platform, designed to help me manage both academic content and classroom operations. At
the top, I have access to key tools such as Announcements, Attendance Dashboard,
Assignments Manager, Calendar, Family Messaging, Progress Reports, School Policies,
School Library, and the Timetable.

Below these tools, I see a table listing all my courses, each showing details like Course Name,
Associated Classes, Grade, Subject, and Status. I have highlighted the course "PCM", which
is listed as Active and falls under the Parent Toddler grade with the subject tagged as Arts.

50
This highlighted selection allows me to focus on a specific course for more in-depth actions,
such as editing the course flow, managing linked classes, or reviewing student progress.

Fig 5.2: Teacher dashboard with customized view.

There is also switch between "My courses" and "My classes" using the segmented control
above the table, depending on whether I want to organize my view by subject or classroom.
In addition, I have a filter option to narrow down the list based on my criteria, and a column
configuration feature that lets me choose which information to display in the table - such as
grades, subjects, status, or associated classes - so I can customize the interface to suit my
workflow and teaching preferences.

In fig 5.3 This image shows a Course Flow interface for the subject "Advance Mathematics"
in a digital learning platform. On the left panel is an outline view listing subjects and units
such as "Unit 1: Differential Equations" and "Derivative." These items are organized
hierarchically and can be expanded or collapsed for easy navigation.

The right panel displays accordion-style units that can be expanded to show content like
notes or learning elements (LEs). Units can be reordered via drag-and-drop, and new content
can be added inline using the "+" button. For example, under "Unit 1," there's a sub-item
called "First Order Differential Equations."

51
Each unit has a dropdown menu (three-dot icon) with options like Edit unit title, Edit unit,
Duplicate, Collapse all sections, and Delete. This setup allows educators to build, modify,
and manage course content efficiently.

Fig 5.3: Interactive Curriculum Course Builder

In fig 5.4 This image displays a course planning timeline in a subject-based grading system,
specifically under the “Unit timeline” view. The timeline spans from April 2025 to March
2026 and shows when different course units are scheduled. Each unit (Discrete Mathematics,
Solving Linear and Quadratic Equations, Differential Equations, and Derivatives) has a
visual block indicating its duration and overlap.

52
 Fig 5.4: Unit Planning Timeline Overview in Planning Module

Fig 5.5: Unit Planning Unit Card View in Planning Module

In fig 5.5 This image presents the same course content in a card layout view, showing the
details of each unit (title, stream, duration, and team size). Each card includes a colorful
image representing the unit, providing a quick visual summary of the course structure. Each
card has different courses.

53
 Fig 5.6: Single Page Unit Planner

In fig 5.6 This image displays a unit planning page for a course titled "Unit 1: Differential
Equations" within a digital learning or curriculum design platform. This interface is likely
used by educators to structure and organize unit content, assessments, and learning
outcomes. The unit is set to run from 16 April 2025 to 28 May 2025, and although it is
mathematically focused, the subject is mistakenly marked as "Arts." A visually engaging
image of colorful mathematical blocks is used, possibly to represent mathematical operations
in a playful and approachable manner.

The platform uses a tabbed menu at the top with sections like Planner, Unit Flow,
Evidencing, and Reflections. Each tab helps teachers through different steps of planning
lessons. On the left side, there’s a sidebar divided into three main parts: Desired Results,
Evidence, and Learning Plan. This setup follows a backward design model, where teachers
start by setting learning goals, then decide how to assess them, and finally plan the lessons.

The site has spaces like "Standards," "Skills," and "Essential Questions." The site also help
teachers remember what students are intended to know long-term. There are also spaces, like
"Performance Tasks" and "Learning Experiences." These can actually help bridge these
goals to what is happening in the classroom. Overall, the site help teachers develop well-
structured lessons with particular goals. It also offer multiple means of measurement of how
54
well students are learning and offer detailed teaching plans. Teachers are also able to track
student progress, which help them see how students are doing.

5.1.2 USER EXPERIENCE AND USABILITY EVALUATION

The platform looks modern and clean and its really easy to use which makes experience
better. The use of clear typography, organized tabs, and a consistent visual layout ensures
that users can navigate the platform with ease. Features such as labeled sections (e.g., “Unit
Summary,” “Standards,” “Skills”) and structured stages (Desired Results, Evidence,
Learning Plan) help educators follow a logical flow in curriculum design. The aesthetic
design - including colorful visuals and balanced spacing - adds an engaging element to what
is typically a content-heavy planning task.

From a usability perspective, the system supports efficiency by breaking down unit planning
into manageable sections. Users can easily locate and input relevant information due to the
sidebar and tabbed navigation at the top. Interactive elements such as dropdowns and editable
text boxes suggest a user-centered design [21]. Some small issues - like calling a math unit
“Arts” by mistake - could make the data less accurate and reduce user trust. Also, even
though the layout is clear, beginners might need help like tooltips or hints to understand the
more advanced planning parts.

The platform supports good teaching practices, helping users plan by starting with learning
goals and then working backwards to plan lessons. This educational logic reinforces positive
user behavior and makes the platform valuable for structured lesson planning.[21,16] The
separation of stages allows teachers to track progress and maintain focus. While the system
seems to be primarily desktop-oriented, the responsiveness and integration with reflection
and evidence tools show promise for continuous instructional improvement. Overall, the
platform is supported with a streamlined, user-friendly planning process. The process can be
further enhance usability with more contextual help and automated suggestions.

55
5.1.3 COMPARISON WITH EXISTING SOLUTIONS

The solution was developed under this project, has been found to have several more
advantages in efficiency, scalability, and user experience in comparison with existing
systems. Traditional implementations of similar systems often depend on REST APIs, which
are functional in nature but suffer from such inherent flaws as over-fetching or under-
fetching data. This project eliminates the same inefficiency by using GraphQL and thereby
enables the fetching of the exact data. GraphQL permits the client to request only necessary
fields, thus giving much faster responses and lesser overhead in the network as against the
solutions based on REST [8].

It also comes with Redux for state management. The above techniques are mostly being
based upon local component states and using alternative libraries that end in a scattered state
management approach and inconsistency. Reducers centralize states thus making predictable
data flows by way of debugging and easier scales as the application grow on. The middle
integration available with Redux, can use asynchronous actions to better carry out its job
much of which is not seamless or even possible to old solutions.

From a frontend perspective, this solution has more maintainability and customization edges
due to the use of ReactJS with SASS on styling [2]. Most older platforms base their styling
on vanilla CSS or less advanced frameworks without the modularity and features that are
present in SASS. Having reusable components and variables using SASS gives the solution
design consistency and faster updating of the UI compared to less structured approaches.

On the backend, using Apollo Server offers a more powerful GraphQL implementation with
much easier schema definition, query processing, and mutation processing. The existing
solutions, based on REST APIs, are mostly verbose and redundant in endpoint definitions.
With Apollo Server and PostgreSQL, there is a more streamlined and efficient backend
architecture. PostgreSQL indexing and query optimization can better outperform non-
relational or less feature-rich databases that struggle with complex relational queries [7,12].

In a nutshell, using modern tools and frameworks that incorporate the use of an ecosystem
like Apollo offers improved developer experience as well as quicker development cycles,
better than legacy systems offer. Development time will take off a lot as Apollo Client
reduces it greatly while maintaining good performance compared to what has been found.
Unlike the existing system, it uses modern technology [14].

56
 CHAPTER 6: CONCLUSIONS AND FUTURE
SCOPE

6.1 CONCLUSIONS

The first step in effective teaching is planning and Toddle's Planning Module makes teaching
planning different. This module helps address the biggest problems educators face when
scheduling, planning lessons, and aligning the curriculum. It gives instructors one cohesive,
user-friendly system that unifies organization, collaboration, and unit development. This is
a life-changing experience as educators navigate the dynamic classrooms of today.

A high-point feature of the Planning Module is its rich feature, in which it supports and
facilitates the effectiveness and impact on teaching. Teachers can start changing, editing, or
creating the planning by using the Unit Planning feature with international curricula-the IB
curriculum. It makes collaboration convenient between teammates to coworkers, students
and families while maintaining strict management of who can and who cannot view the
plans-keeping the atmosphere of education safe and cooperative.

Class Planner system makes it easier to manage complexities of yearly timetables. Teachers
can transition from lesson to lesson and activity to activity more easily through their capacity
to visualize and plan their class movement with ease. It provides workflows with more
guidance and direction, enabling teachers to be ahead of curriculum objectives to concentrate
on delivering engaging and effective lessons.

One of the strengths of the Planning Module is that it is adaptable to fit various teaching
requirements. Whether for various pedagogies or for the individual needs of evolving
classrooms, this module is adaptable in a way that none other is. It integrates assignments,
notes, and links for students and teachers. It is low in administrative load but makes resources
easily searchable and accessible.

In addition, the Planning Module is all about collaboration. It makes communication between
teachers, students, and families easier and more efficient, hence bringing everyone together
towards education. For an effective interdisciplinary learning environment for students,
educators can collaborate with one another to achieve common goals and tactics.
57
It is revolutionary for teachers across the globe. It redefines the planning process and points
out the inconsistency of the tools currently on the market. It enables the teacher to
concentrate on what counts the most : giving students engaging, relevant learning
experiences. In light of its cutting-edge attributes and dedication to satisfaction of the
evolving demands in education, the Planning Module is a key partner to establish the new
path that effective teaching will follow in the future.

6.1.1 KEY FINDINGS

Toddle review confirms that through the provision of a collaborative, organized, and simple-
to-use configuration, it significantly enhances the general learning process. Efficiently
planned workflows that assist with lesson planning, curriculum mapping, and team
development are preferable to educators. The interface for the module aims at simplifying
planning activities and giving educators an all-in-one kit that eliminates their effort with a
focus on keeping learning targets on track.

The capacity of the module to encourage collaboration among teachers, students, and even
families is one of the most profound findings. With the provision of controlled visibility and
mutual access, the tool avails an open and transparent planning space. By collaborating in
preparing units, ensuring they are well documented, and ensuring they are in compliance
with global standards such as the IB curriculum, teachers can generate a homogenized and
globalized learning process.

Educators can plan activities, annual schedules, and class motions with such ease due to the
curriculum mapping and visual learning capabilities in Toddle's Planning Module, enabled
by features such as the Class Planner. This feature provides for the fulfillment of learning
targets without any kind of problem and allows for the continuity of lessons while making
otherwise cumbersome processes run smoothly. Together, these characteristics represent a
revolutionary departure from the planning approach employed in education today.

58
6.1.2 CONTRIBUTIONS TO THE FIELD

Toddler's Planning Module significantly supports the use of instructional technology by

solving the fundamental issue of planning and teaching integration in the classroom.

By combining lesson planning, collaboration, and information sharing into one package, it
provides an integrated system of pedagogy management within the grasp of most schools.

This innovation sets the standard for subsequent resources that enable teacher independence
and pedagogical convenience.

Not only does the module facilitate systematic preparation, but also adaptive adjustment,
allowing teachers to quickly react to the changing needs of classrooms today. This is
particularly important for inquiry-based or multilingual curriculum, as with the IB, where
success is contingent upon continuous reflection and adjustment. Toddle fills the gap
between set plans and changing classroom needs by offering one place where learning
materials are to be organized, made available, and stored.

Lastly, the design of the platform adds into wider educational practice which encourage
reflective teaching and collaborative professionalism. Through the built-in evidencing and
reflection tools, teachers are not merely planning but continually refining their practice based
on feedback and outcomes. This promotes a culture of iterative growth, data-informed
instruction, and peer-supported development - strengthening both individual and institutional
teaching quality.

6.2 FUTURE SCOPE

There will be much scope in the future to develop Course Structure Development and fine-
tune Roles and Permissions in the Toddle platform, thus adhering to institutional
requirements, revenue growth, and also furthering user engagement. With these
developments, there will be more freedom to act for teachers, while the institutions will have
effective systems that can adapt themselves to a wide range of requirements.

59
6.2.1 FUTURE SCOPE FOR COURSE STRUCTURE DEVELOPMENT

In the future, Toddle could grow into a flexible and adaptable course structure. By making
frameworks that can support all kinds of curriculum, such as those offered by the IB,
Cambridge, and national educational boards, Toddle may strive to be the number one choice
for educational institutions worldwide. Customizable course templates could be introduced,
allowing educators to adapt content to specific teaching goals and institutional standards.

Course development can also be enhanced with integrated advanced analytics that offer
insights into the behavior of the users and completion rates as well as weaknesses. Data-
driven refinement in the continuous adjustment of the courses will make sure the courses
meet expectations of both users and education. Finally, integrating multimedia-rich content,
interactive features, and AI-driven personalization can develop immersive learning
experiences to enhance user engagement.

Course sharing marketplace is another exciting option. Teachers and schools would be able
to add or buy pre-designed courses thus creating a collaborative community for themselves
while also adding income streams for Toddle. Integration of third-party tools and LMS would
solidify Toddle's hold as an all-round education platform.

6.2.2 FUTURE SCOPE FOR STUDENT-END COURSE STRUCTURE

This upgrade will establish the entire planner view and student access rights within the site.
It will provide students with a clear, organized view of their learning path, including access
to applicable units, calendars, and assignments specific to their grade level and registration.
Access rights will be tightly made to restrict what students can see or engage with -
maintaining focus, clarity, and data security. This customized experience seeks to enhance
student accountability, planning effectiveness, and general learning participation.

60
 REFERENCES
[1] A. Williams, "Understanding the Event-Driven Architecture in Node.js," Journal of
Computer Science and Technology, vol. 34, no. 4, pp. 456-467, Oct. 2023.

[2] R. Thompson, "Building Scalable Microservices with React, Node.js, and GraphQL,"
Proceedings of the International Conference on Web Development, New York, USA, 2023,
pp. 89-98.

[3] D. Brown, "Integrating PostgreSQL with NoSQL Databases: A Comparative Study,"

International Journal of Database Management Systems, vol. 39, no. 6, pp. 200-215, Nov.
2023.

[4] A. Richards, "Exploring Full-Stack JavaScript Frameworks for Web Development,"

IEEE Access, vol. 9, pp. 1763-1778, Feb. 2024.

[5] P. Johnson, "Advanced Techniques in GraphQL Query Optimization," ACM

Transactions on Web Development, vol. 31, no. 1, pp. 1-14, Mar. 2024.

[6] S. Martinez, "PostgreSQL Performance Tuning and Optimization for High-Volume

Applications," IEEE Transactions on Big Data, vol. 6, no. 4, pp. 489-502, Dec. 2023.

[7] J. Williams, "Serverless GraphQL with Apollo Server and AWS Lambda," International
Journal of Web Services Research, vol. 27, no. 2, pp. 112-126, Apr. 2024.

[8] L. Davis and M. Garcia, "Node.js vs. Django: A Comparative Analysis for Modern Web
Development," Journal of Software Engineering, vol. 15, no. 3, pp. 340-355, Jan. 2024.

[9] M. Brown, "Building a Real-Time Data Processing Pipeline with Node.js and
PostgreSQL," Proceedings of the 2024 International Conference on Database Engineering,
San Francisco, CA, USA, pp. 102-110.

[10] B. Clark, "Managing Asynchronous Operations in JavaScript with Promises and

Async/Await," Journal of Software Architecture, vol. 11, no. 5, pp. 77-89, May 2023

61
[11] H. Green, "A Deep Dive into React Suspense for Data Fetching," IEEE Software, vol.
40, no. 1, pp. 98-107, Jan. 2024.

[12] T. Roberts and C. Martinez, "Building Enterprise-Scale GraphQL APIs with Apollo
Server," IEEE Transactions on Cloud Computing, vol. 10, no. 4, pp. 1245-1258, Nov. 2023.

[13] P. Williams, "GraphQL Error Handling and Resilience," Journal of Web and Cloud
Computing, vol. 27, no. 2, pp. 302-315, Feb. 2024.

[14] K. James, "Scaling Node.js Applications with Docker and Kubernetes," IEEE
Transactions on Software Engineering, vol. 50, no. 2, pp. 251-263, Mar. 2024.

[15] L. Thomas, "A Survey of Database Integration Techniques for Modern Web
Applications," ACM Computing Surveys, vol. 56, no. 5, pp. 1-20, May 2024.

[16] R. Green, "Managing State with Redux and React Context API," IEEE Transactions on
Computer Science, vol. 25, no. 3, pp. 315-328, Mar. 2024.

[17] B. Lewis, "The Power of SASS Mixins in Web Development," Smashing Magazine,
Jun. 23, 2023.

[18] M. Davis, "How to Manage Database Transactions in PostgreSQL," PostgreSQL

Documentation, Feb. 10, 2024.

[19] C. Miller, "Creating Scalable REST APIs with Node.js and Express," Rising
Developers, Sep. 18, 2023.

[20] H. Patel, "Implementing JWT Authentication in Node.js," Auth0 Blog, Dec. 1, 2023.

[21] J. Collins and R. Kim, "Designing Scalable Microservices Architecture Using GraphQL
and Node.js," IEEE Transactions on Cloud Computing, vol. 11, no. 6, pp. 1032-1045, Jun.
2024.

[22] A. Zhang and Y. Lee, "Optimizing PostgreSQL for High-Volume OLAP Workloads,"
IEEE Transactions on Big Data, vol. 7, no. 3, pp. 654-667, Mar. 2024.

[23] R. Gupta, "Improving Front-End Performance with React and Webpack," IEEE
Software, vol. 41, no. 2, pp. 75-86, Apr. 2024.

62
[24] T. Johnson and K. Lee, "Building Full-Stack Applications with Node.js and Express,"
IEEE Transactions on Software Engineering, vol. 51, no. 1, pp. 112-124, Jan. 2024.

[25] L. Turner and B. Roberts, "Introduction to Real-Time Data Streaming with Node.js and
Apache Kafka," IEEE Transactions on Distributed and Parallel Systems, vol. 35, no. 4, pp.
567-578, Apr. 2024.

63
Appendix

A.1 Project Plan

A.1.1 Phase 1: Planning and Design

● Define project scope and objectives

● Design system architecture

● Develop user stories

A.1.2 Phase 2: Development

● Building frontend with ReactJs.

● Integrating backend with frontend.

A.1.3 Phase 3: Testing

● Manually testing on the website.

● Testing done by QA.

64