TEACHERS RECORD MANAGEMENT SYSTEM

A PROJECT REPORT

Submitted to:

HIMACHAL PRADESH TECHNICAL UNIVERSITY,

HAMIRPUR
by
SHIVALI (21020203006)
in partial fulfillment for the award of the degree
of
BACHELOR OF TECHNOLOGY
in
COMPUTER SCIENCE & ENGINEERING

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

ATAL BIHARI VAJPAYEE GOVT. INSTITUTE OF

ENGINEERING & TECHNOLOGY
PRAGATINAGAR, SHIMLA, HIMACHAL PRADESH
DECEMBER 2023

1
 ACKNOWLEDGEMENT
I am very grateful to my Industrial Training Project guide Ms. Aashna Sharma for
giving her valuable time and constructive guidance in preparing the Synopsis/Project
Work I. It would not have been possible to complete this Synopsis/Project Work- I in
short period of time without his/her kind encouragement and valuable guidance.

Date: 4/10/2023 Signature

Shivali
21020203006

2
 CERTIFICATE
I hereby certify that the work which is being presented in the B.Tech. Project Work- I
Report entitled “TEACHER RECORD MANAGEMENT SYSTEM”, in partial
fulfillment of the requirements for the award of the Bachelor of Technology in
Computer Science & Engineering and submitted to the Department of Computer
Science & Engineering of Atal Bihari Vajpayee Govt. Institute of Engineering &
Technology, Pragatinagar, Shimla, HP is an authentic record of my own work carried
out during a period from August 2023 to November 2023 under the supervision of Er.
Navdeep Sharma, Assistant Professor, CSE Department.

Signature
SHIVALI
21020203006

This is to certify that the above statement made by the candidate is correct to the best
of my knowledge.

Date:04/10/2023 Signature of Supervisor

Er. Navdeep Sharma
Assistant Prof. (CSE)

Head
Computer Science & Engineering Department
Atal Bihari Vajpayee Govt. Institute of Engineering & Technology, Pragatinagar

3
4
 ABSTRACT
The Teachers Record Management System (TRMS) is a web-based application aimed
at efficient organization and management of teacher records in educational
institutions. It comprises two main modules: Admin and Users, each serving distinct
functionalities to meet diverse stakeholder needs. Teacher Record Management
System contains data and information of teacher. The main purpose of TRMS is to
systematically record, store and update the teacher's records.

The information from TRMS is used to search teachers online. With the help of this
software person can easily search teacher according to his/her requirement.

The Admin module is the system's cornerstone, empowering administrators with

robust control. It includes features like subject and teacher management, a powerful
search engine, reporting functions, profile management, secure login, and password
change. Administrators can efficiently organize subjects and teacher records,
benefiting from a robust search engine and insightful reporting capabilities. Profile
management ensures accurate representation within the system while secure login and
password change features bolster system security.

The Users module prioritizes a user-centric experience, serving students, parents, and
other stakeholders. It offers user-friendly functionalities such as teacher search and
query submission. Users can easily search for teachers based on subjects and raise
queries, promoting effective engagement and inquiries related to education.

The Teacher Module caters to educators, offering a welcoming Dashboard for quick
information access. The Queries Section centralizes communication, allowing
teachers to efficiently review user queries, fostering seamless engagement. Profile
management enables teachers to maintain accurate personal and professional
information.

5
 TABLE OF CONTENTS

Chapter No. Contents Page No.

1 Introduction 1-3

2 S/w and H/w Requirement Specification 4-5

3 System analysis 6-9

3.1 Identification of Need
3.2 Preliminary Investigation

4 Feasibility Study 10-14

4.1 Technical Feasibility
4.2 Economic Feasibility
4.3 Operational Feasibility

5 Analysis and Design 15-25

5.1 Analysis
5.2 Design Introduction
5.2.1 UML Diagrams
5.2.2 Use case Diagrams
5.2.3 Class Diagram
5.2.4 ER Diagram
5.2.5 Data Flow Diagram
5.2.6 Data Tables

6 Software Engineering paradigm applied 26-27

7 Implementation and System Testing 28

8 Project Screenshots 29-41

9 Future Scope of the project 42

6
 LIST OF FIGURES
Figure No. Figure Name Page No.

1 Use Case Diagram for Admin 17

2 Use Case Diagram for Users 18

3 Use Case Diagram for Teachers 18

4 Class Diagram 19

5 ER Diagram 21

6 Zero Level DFD 22

7 First Level DFD 23

8 Two Level DFD 23

9 Teacher Module 24

10 Admin Table 24

11 Subject Table 25

12 Admin Table 25

13 Query table 25

14 Agile Software Development 26

7
 CHAPTER-1

INTRODUCTION

The Teachers Record Management System (TRMS) is a sophisticated and intuitive

web-based application designed to facilitate the efficient organization and
management of teacher records within educational institutions. This system comprises
two primary modules: the Admin module and the Users module. The Admin module
empowers administrators with comprehensive control over system functionalities,
enabling effective oversight, data management, and reporting. In contrast, the Users
module caters to the needs of students, parents, and various stakeholders by offering
user-friendly features for searching teachers and raising queries.

1.1 OBJECTIVES

 Efficient Organization of Teacher Records:

The primary objective of TRMS is to streamline the organization of teacher
records within educational institutions. By providing a centralized and structured
repository, the system aims to facilitate easy access, management, and
maintenance of vital teacher-related information.
 Enhanced Administrative Control:
Through the Admin module, includes efficient management of subjects, teachers,
and related data. The objective is to equip administrators with tools to oversee and
regulate the system effectively.
 Facilitating Informed Decision-Making:
TRMS endeavors to aid administrators in making informed decisions by providing
reporting functionalities. This offer insights into the number of teachers, their
distribution, and changes over specified periods.
 User-Centric Experience:
The Users module is designed to prioritize the user experience, catering to
students, parents, and stakeholders. The system aims to provide a seamless and
intuitive interface for users to search for teachers based on subjects and

1.2 SCOPE

8
The project's scope encompasses the design, development, and implementation of the
TRMS. This involves creating the essential modules - Admin, Users, and Teacher -
each serving specific purposes within the system. The project will utilize PHP for the
backend and MySQL for the database, ensuring a secure and scalable application.

1.3 METHODOLOGY

The development of TRMS will follow an agile methodology, enabling iterative

development and continuous feedback integration. The project will proceed through
stages of requirements gathering, system design, implementation, testing, and
deployment. Regular sprints and feedback loops will ensure that the system meets the
defined objectives and remains aligned with stakeholders' expectations.

1.4 SIGNIFICANCE

Efficient management of teacher records is critical for educational institutions to

ensure smooth operations, timely communication, and informed decision-making. The
TRMS project addresses this need by introducing a modernized approach to record-
keeping. It is expected to significantly reduce administrative burden, enhance data
accessibility, and promote a more transparent and organized educational environment.

In the subsequent sections of this report, we delve deeper into the project's
architecture, functionalities, implementation details, and the outcomes achieved. We
present an in-depth analysis of each module, illustrating their features and advantages.
Additionally, we discuss challenges faced during development and provide
recommendations for future enhancements. The culmination of this report is a
comprehensive understanding of the Teachers Record Management System and its
potential to transform how educational institutions handle teacher-related data.

Admin Module

Dashboard: In this section admin can briefly view total number of subjects and total
number of teachers.

Subjects: In this section, admin can manage the Subjects (add/update).

Teachers: In this section, admin can add new teachers and manage the details of old
teachers.

9
Search: In this section, admin can search teachers by using teacher name.

Report: In this section, admin can view number of teachers added in particular
periods.

Profile: In this section admin can update his/her profile.

Change Password: In this section admin can change his/her own passwords

Logout: Through this button admin can logout.

Forgot Password: In this section, admin can reset his/her password by using registered
email id and contact number.

Teacher Module

Dashboard: It is the welcome page for a teacher.

Queries: In this section, teacher view the queries which is raised by users.

Profile: In this section teacher can update his/her profile.

Change Password: In this section teacher can change his/her own passwords

Logout: Through this button teacher can logout.

Note: In this project MD5 encryption method used.

Users:

Users can search the teachers by entering the subject name and raised the queries
which is seen by teacher.

10
 CHAPTER-2
SOFTWARE AND HARDWARE SPECIFICATION

2.1 HARDWARE SPECIFICATION:

Table 2.2: H/w Requirement

Item Description
Server/Hosting A dedicated server with sufficient power, RAM and
storage capacity.
Workstations Faculty computers with RAM:4GB or higher,
SSD: 256GB or higher,
Storage:256GB or higher
Internet Connectivity High Speed internet connection for online access
Processor Brand AMD Quad-Core Processor A6-7310

2.2 SOFTWARE SPECIFICATION:

Table 2.1: S/w Requirement

Client Side:

Web Browser Google Chrome or any compatible

browser
Operating System
Windows or any equivalent OS

Server Side:

Web Server APACHE

Server side Language PHP5.6 or above version

Database Server MYSQL

11
 Google Chrome or any compatible
Web Browser browser

Operating System Windows or any equivalent OS

APACHE
The Apache HTTP Server Project is an effort to develop and maintain an open-source
HTTP server for modern operating systems including UNIX and Windows. The goal
of this project is to provide a secure, efficient and extensible server that provides
HTTP services in sync with the current HTTP standards.
The Apache HTTP Server ("httpd") was launched in 1995 and it has been the most
popular web server on the Internet since April 1996. It has celebrated its 20th birthday
as a project in February 2015.
PHP
• PHP stands for PHP: Hypertext Preprocessor.
• PHP is a server-side scripting language, like ASP.
• PHP scripts are executed on the server.
• PHP supports many databases (MYSQL, Informix, Oracle, Sybase, Solid,
Generic ODBC, etc.).

• PHP is an open source software.

• PHP is free to download and use.

MYSQL
• MYSQL is a database server.
• MYSQL is ideal for both small and large applications.
• MYSQL supports standard SQL.
• MYSQL compiles on a number of platforms.
• MYSQL is free to download and use.
• How to access MySQL: http://localhost/phpmyadmin.

12
 CHAPTER-3

SYSTEM ANALYSIS
System analysis for the Teachers Record Management System (TRMS) project
involves a comprehensive and structured approach to understanding, defining, and

designing the system to ensure it meets its objectives effectively.

 Understanding User Requirements
Conducted in-depth interviews and discussions with educational institution
stakeholders, including administrators, teachers, students, and parents, to gather
comprehensive requirements for the system.
 Identifying Functional Requirements
Compiled a detailed list of functionalities required in the Admin, Users, and
Teacher modules based on the gathered requirements.
 Defining Non-Functional Requirements
Defined non-functional requirements such as system performance, security,
scalability, usability, and data privacy to ensure the system meets desired
standards.
 Defining Data Models
Created entity-relationship diagrams (ERDs) to depict the relationships between
various data entities like teachers, subjects, users, profiles, and queries.
 Analyzing Data Flow
Mapped the flow of data within the system, identifying inputs, processes, and
outputs at different stages of system usage.
 Security and Access Control Analysis
Conducted a thorough analysis to identify potential security threats and risks, and
formulated strategies to mitigate them, including the use of encryption methods
and secure login mechanisms.
 Performance Analysis

13
 Evaluated the system's performance requirements, including response times,
concurrent user handling, and database optimization to ensure optimal
performance under varying load conditions.

3.1 IDENTIFICATION OF NEED

The identification of needs revolves around understanding the specific
requirements and pain points within educational institutions related to teacher
record management. Here's a breakdown of the identified needs:
 Efficient Organization of Teacher Records:
Educational institutions need a systematic and organized approach to store and
manage teacher records, including personal information, qualifications, teaching
experience, and subjects taught.
 Centralized Repository for Teacher Information:
Institutions require a centralized system to consolidate and manage
comprehensive teacher-related data, ensuring easy access and retrieval when
needed.
 Comprehensive Administrative Control:
Administrators need tools and features to efficiently manage and oversee teacher
records, subjects, and system functionality to ensure smooth operations and
informed decision-making.
 User-Centric Experience for Various Stakeholders:
Students, parents, and other stakeholders need a user-friendly interface to search
for teachers based on specific criteria and raise queries related to education for
effective engagement and communication.
 Data-Driven Decision Making:
The need for reporting functionalities that empower administrators to generate and
view reports on teacher additions and other relevant data during specific time
periods, aiding in data-driven decision-making.
 Enhanced Communication Channels:

14
 Establishing effective communication channels between teachers and stakeholders
is crucial to facilitate inquiries, address concerns, and maintain a seamless flow of
information.
 Data Security and Privacy:
Educational institutions need assurance that the teacher record management
system maintains the security and privacy of sensitive data through secure login,
password change features, and robust data encryption methods.
 Quick Information Access for Educators:
Educators require a dedicated dashboard for quick access to essential information,
including queries from users, to effectively manage their responsibilities and
engage with stakeholders.
 Accurate and Up-to-Date Teacher Profiles:
It is essential to ensure that teacher profiles within the system are accurate and up-
to-date, providing an authentic representation of the educators within the
educational institution.

3.2 PRELIMINARY INVESTIGATION

Preliminary investigation for the Teachers Record Management System (TRMS)
involves gathering essential information to understand the project's context
objectives, and initial requirements. Here's a structured approach for conducting a
preliminary investigation:
 Project Overview:
Understand the project's purpose, which is to develop a web-based application for
efficient organization and management of teacher records in educational
institutions. Familiarize yourself with the core modules: Admin, Users, and
Teacher, and their respective functionalities.
 Identify Stakeholders:
List and identify the primary stakeholders involved, such as administrators,
teachers, students, parents, and any other relevant parties. Understand their roles,
needs, and expectations regarding the system.
 Meet with Stakeholders:

15
 Schedule meetings or interviews with stakeholders to discuss the objectives,
expectations, and requirements they have for the TRMS. Document their feedback
and insights.
 Current System Assessment:
Evaluate any existing systems or processes currently in use for managing teacher
records. Identify the strengths, weaknesses, and limitations of the current
approach.
 Business Process Analysis:
Analyze the current business processes related to teacher record management.
Understand how information is currently collected, stored, accessed, and
managed.
 Needs Assessment:
Gather information on the needs and pain points of administrators, users, and
teachers. Identify what functionalities are lacking in the existing systems and
processes.
 Technology Assessment:
Research and assess the technology landscape to identify suitable platforms,
frameworks, and tools that can be utilized to develop the TRMS. Consider factors
like scalability, security, and compatibility.
 Regulatory and Compliance Requirements:
Investigate any legal requirements relevant to teacher record management in
educational institutions. Ensure that the TRMS complies with necessary
regulations.
 Budget and Resource Constraints:
Determine the budget constraints and resource availability for the project.
Understand the limitations in terms of funding, time, and human resources.
 Risk Assessment:
Identify potential risks and challenges that may arise during the development and
implementation of the TRMS. Assess their impact and likelihood.
 Project Objectives and Scope:
Define the high-level objectives and scope of the project based on the gathered
information. Ensure that the objectives align with the needs of the stakeholders
and the goals of the educational institution.

16
 CHAPTER-4
FEASIBILITY STUDY
A feasibility study for the Teachers Record Management System (TRMS) project
is essential to determine its viability and potential success. The study assesses
various aspects to ensure the project is feasible and aligns with organizational
goals and resources. It involves a comprehensive assessment of various factors to
ensure that the project is feasible and aligned with the organization's goals and
resources.

4.1 TECHNICAL FEASIBILITY

The Technical Feasibility analysis for the Teachers Record Management System
(TRMS) involves assessing the technological aspects to ensure that the project can
be successfully developed, implemented, and maintained. It evaluates whether the
proposed Teachers Record Management System (TRMS) can be developed and
implemented using available technology and within specified constraints . Analyze
the volume and types of data that TRMS will handle, and propose an appropriate
data storage and retrieval mechanism.
 Technology Assessment:
Evaluate the appropriate technologies and frameworks for developing a robust
web-based application for TRMS. Consider factors like scalability, compatibility,
security, and performance in selecting the technology stack.

17
 Hardware and Software Requirements:
Define the hardware and software infrastructure needed to support the
application's development, deployment, and ongoing operation. Specify server
configurations, database requirements, and other hardware components.
 Integration Capabilities:
Analyze the integration points of TRMS with external systems, if any, and ensure
smooth data exchange and interaction. Evaluate the compatibility and ease of
integration with existing school management systems or other educational tools.
 Database Management:
Identify the appropriate database management system (DBMS) that can efficiently
handle the volume and complexity of teacher records and related data.
Consider database design, indexing strategies, and data retrieval mechanisms for
optimal performance.
 Scalability and Performance:
Evaluate the system's ability to scale to handle an increasing number of users,
data, and transactions over time. Perform load testing and assess the system's
performance under different usage scenarios to ensure responsiveness and
reliability.
 Security Measures:
Define robust security measures to safeguard sensitive information, such as user
credentials, teacher records, and communication channels. Implement encryption,
secure login mechanisms, role-based access control, and data privacy protocols.
 Software Development Lifecycle (SDLC):
Define the software development methodology (e.g., Agile, Scrum) that aligns
with the project's goals and requirements. Establish a structured SDLC process to
ensure efficient development, testing, deployment, and maintenance of TRMS.
 Technical Expertise and Skills:
Assess the availability of skilled developers and technical expertise required for
building and maintaining the TRMS. Plan for training and skill development
programs to ensure the team is equipped to work with the chosen technologies.

4.2 ECONOMIC FEASIBILITY

18
 Economic feasibility analysis for the Teachers Record Management System
(TRMS) involves evaluating whether the project is financially viable and cost-
effective. It helps in determining whether the benefits outweigh the costs
associated with development, implementation, and maintenance. It assesses
whether the project is financially viable and if the benefits outweigh the costs. It
include initial development costs, maintenance costs, and potential cost savings or
revenue generation resulting from system implementation.Here are the key aspects
of economic feasibility for TRMS:

 Cost Estimation:
Identify and estimate all costs associated with the project, including development,
hardware, software, training, maintenance, support, and any other expenses related
to the project lifecycle.
 Development Costs:
Estimate the costs involved in developing the TRMS, including software
development, database design, user interface development, integration, testing,
and quality assurance.
 Hardware and Software Costs:
Calculate the expenses associated with procuring and setting up the required
hardware and software components for the application to function optimally.
 Operational Costs:
Assess ongoing operational costs, such as hosting, maintenance, updates, support,
and licensing fees for third-party tools or software.
 Training and Support Costs:
Estimate the costs associated with training the users, administrators, and support
staff for effective utilization of the TRMS.
 Benefits and Savings:
Identify and quantify the benefits and savings that the TRMS will bring to the
educational institution, including time saved, efficiency gains, reduced paperwork,
improved decision-making, and resource optimization.
 Sensitivity Analysis:

19
 Conduct sensitivity analysis to assess how changes in key parameters, such as user
adoption rates or operational costs, affect the economic feasibility of the project.
Identify the critical parameters that significantly influence the project, such as cost
of development, maintenance costs, user adoption rates, or technological
advancements.
 Comparison with Alternatives:
Compare the economic feasibility of developing TRMS with potential
alternatives, such as using existing systems or outsourcing the development, to
make an informed decision. List and describe alternative solutions that could
potentially address the need for efficient organization and management of teacher
records in educational institutions.
4.3 OPERATIONAL FEASIBILITY
Operational feasibility for the Teachers Record Management System (TRMS)
assesses whether the proposed system can be effectively implemented and
integrated into the existing educational environment. It focuses on evaluating the
practicality of implementing TRMS from an operational standpoint. Describe how
the TRMS will be integrated into the existing operations. Explain any changes or
enhancements needed in the current processes to accommodate the new system.
Assess if the existing workforce possesses the necessary skills or if additional
training is needed. Here are the key aspects of operational feasibility for TRMS:
 User Acceptance and Training:
Assess the willingness and readiness of users, including administrators, teachers,
students, and parents, to accept and adapt to the new system. Evaluate the need for
training and determine the ease of use for various user roles.
 Ease of Use and Navigation:
Evaluate the system's user interface and navigation to ensure that users can easily
perform tasks and access functionalities without encountering significant
difficulties.
 Integration with Existing Systems:
Determine how seamlessly TRMS can integrate with any existing systems,
databases, or software solutions used within the educational institution to avoid
disruptions and ensure smooth operations.
 Data Migration and Compatibility:

20
 Assess the feasibility of migrating existing teacher records and data into TRMS,
ensuring compatibility and data integrity during the transition.
 Impact on Current Processes:
Analyze how TRMS will impact current administrative and record-keeping
processes, and identify any necessary adjustments or improvements needed for
efficient implementation.
 Risk Assessment:
Identify potential risks related to system implementation, integration, and
operation, and develop risk mitigation strategies to address them effectively.
 Scalability and Flexibility:
Evaluate the system's ability to accommodate growth in the number of users, and
additional features, ensuring it remains flexible and scalable to meet future
requirements.
 Availability of Resources:
Determine if there are sufficient resources, including hardware, software, skilled
personnel, and technical support, available to successfully implement and
maintain TRMS.
 Security and Privacy Compliance:
Ensure that TRMS complies with legal and regulatory requirements related to data
privacy and security, considering the sensitive nature of educational and personal
information.
 Feedback and Stakeholder Involvement:
Engage stakeholders to gather feedback and suggestions regarding the system's
design, functionalities, and potential improvements, ensuring that their needs and
concerns are adequately addressed.
 Operational Impact Analysis:
Conduct an analysis to predict the operational impact of TRMS on daily activities,
workload, and efficiency, both during the transition phase and in the long run.

21
 CHAPTER-5
ANALYSIS AND DESIGN
5.1 ANALYSIS
In present all teacher record work done on the paper. The whole year teacher
record is stored in the registers. We can’t generate reports as per our requirements
because its take more time to calculate the teacher record report.
Disadvantage of present system:
• Not user friendly: The present system not user friendly because data is not
stored in structure and proper format.
• Manual Control: All report calculation is done manually so there is a chance of
error.
• Lots of paper work: Teacher record maintain in the register so lots of paper
require storing details.
• Time consuming.

5.2 DESIGN INTRODUCTION

Design is the first step in the development phase for any techniques and principles
for the purpose of defining a device, a process or system in sufficient detail to
permit its physical realization.
Once the software requirements have been analyzed and specified the software
design involves three technical activities - design, coding, implementation and
testing that are required to build and verify the software.
The design activities are of main importance in this phase, because in this activity,
decisions ultimately affecting the success of the software implementation and its
ease of maintenance are made. These decisions have the final bearing upon

22
reliability and maintainability of the system. Design is the only way to accurately
translate the customer’s requirements into finished software or a system.
Design is the place where quality is fostered in development. Software design is a
process through which requirements are translated into a representation of
software. Software design is conducted in two steps. Preliminary design is
concerned with the transformation of requirements into data

5.2.1 UML Diagrams:

Actor: A coherent set of roles that users of use cases play when interacting with
the use cases.

Use case: A description of sequence of actions, including variants, that a system

performs that yields an observable result of value of an actor.

UML stands for Unified Modeling Language. UML is a language for specifying,
visualizing and documenting the system. This is the step while developing any
product after analysis. The goal from this is to produce a model of the entities
involved in the project which later need to be built. The representation of the
entities that are to be used in the product being developed need to be designed.

5.2.2 Use case Diagrams:

Use case diagrams model behavior within a system and helps the developers
understand of what the user require. The stick man represents what’s called an
actor.
Use case diagram can be useful for getting an overall view of the system and
clarifying who can do and more importantly what they can’t do.
Use case diagram consists of use cases and actors and shows the interaction
between the use case and actors.

23
 • The purpose is to show the interactions between the use case and actor.
• To represent the system requirements from user’s perspective.
• An actor could be the end-user of the system or an external system.

Use case Diagrams: A Use case is a description of set of sequence of actions.

Graphically it is rendered as an ellipse with solid line including only its name.
Use case diagram is a behavioral diagram that shows a set of use cases and actors
and their relationship. It is an association between the use cases and actors. An
actor represents a real-world object. Primary Actor – Sender, Secondary Actor
Receiver.

Use Case Diagrams:

Dashboard
Admin

Add Subject

Manage Subject (Update

Details)

Add Teacher

Manage Teacher (Update

Details)

Search(Teacher)

Generate Reports

Update Profile

Change Password

24
 Password Recovery

Fig.1- Use Case Diagram for Admin

Users:

Visit Website

Search (Teacher)

Fig.2- Use Case Diagram for Users

Teachers:

Signup

Login

Dashboard

View Queries

Update Profile

Change Password

Fig.3- Use Case Diagram for Teacher

25
5.2.3 Class Diagram:
A description of set of objects that share the same attributes operations, relationships,
and semantics.

Fig.4- Class Diagram

5.2.4 ER Diagram:
The Entity-Relationship (ER) model was originally proposed by Peter in 1976
[Chen76] as a way to unify the network and relational database views. Simply
stated the ER model is a conceptual data model that views the real world as
entities and relationships. A basic component of the model is the Entity-
Relationship diagram which is used to visually represent data objects. Since Chen

26
wrote his paper the model has been extended and today it is commonly used for
database design for the database designer, the utility of the ER model is:
• It maps well to the relational model. The constructs used in the ER model can
easily
be transformed into relational tables.
• It is simple and easy to understand with a minimum of training. Therefore, the
model can be used by the database designer to communicate the design to the end
user.
• In addition, the model can be used as a design plan by the database developer to
implement a data model in specific database management software.

ER Notation:
There is no standard for representing data objects in ER diagrams. Each modeling
methodology uses its own notation. The original notation used by Chen is widely
used in academics texts and journals but rarely seen in either CASE tools or
publications by non-academics. Today, there are a number of notations used;
among the more common are Bachman, crow's foot, and IDEFIX.
All notational styles represent entities as rectangular boxes and relationships as
lines connecting boxes. Each style uses a special set of symbols to represent the
cardinality of a connection. The notation used in this document is from Martin.
The symbols used for the basic ER constructs are:
• Entities are represented by labeled rectangles. The label is the name of the
entity. Entity names should be singular nouns.
• Relationships are represented by a solid line connecting two entities. The
name of the relationship is written above the line. Relationship names should be
verbs
• Attributes, when included, are listed inside the entity rectangle. Attributes
which are identifiers are underlined. Attribute names should be singular nouns.
• Cardinality of many is represented by a line ending in a crow's foot. If the
crow's foot is omitted, the cardinality is one.
Existence is represented by placing a circle or a perpendicular bar on the line.
Mandatory existence is shown by the bar (looks like a 1) next to the entity for an
instance is required. Optional existence is shown by placing a circle next to the
entity that is optional.
27
 Fig.5-ER Diagram
5.2.5 Data Flow Diagram
DFD graphically representing the functions, or processes, which capture,
manipulate, store, and distribute data between a system and its environment and
between components of a system. The visual representation makes it a good
communication tool between User and System designer. Structure of DFD allows

28
 starting from a broad overview and expand it to a hierarchy of detailed diagrams.
DFD has often been used due to the following reasons:
• Logical information flow of the system.
• Determination of physical system construction requirements.
• Simplicity of notation.
• Establishment of manual and automated systems requirements.

Zero Level DFD:

User
Management
Teacher Registration Teacher
Management Management

Subject
Management
TRMS
Report
Management

Query
Management

Login
Management

Fig.6-Zero Level DFD

First Level DFD:

Subject Management

Generate Report

Teacher
Management 29
Query TRMS Check Query
Management Details

Teacher
Check Teacher
Registration
Login Details
Management

Login Management Check Admin

Login Details

Fig.7-First Level DFD

Second Level DFD:

Admin Login to Check Manage

system Roles of Subjects
access

Manage
Teacher

Search
Forgot Check Teacher
Password Credential
Generate
Manage Report
Modules

Update
Profile
Fig.8-Two Level DFD

Change
Teacher Module: Password

Teacher Signup/ Check

ihuji
Login to Roles of
system access

30
 Check
Forgot Credential View Queries
Password

Change Profile
Manage
Modules
Change
Password
Fig.9-Teacher Module

5.2.6 Data Tables

Admin Table :(Table name is admin)
This store admin personal and login details.

Fig.10-Admin Table
Subject Table: (Table name is tblsubjects)

Fig.11-Subject Table

31
 Teacher Table: (Table name is tblteacher)

Fig.12-Teacher Table

Query Table: (Table name is tblquery)

Fig.13-Query Table

CHAPTER-6
SOFTWARE ENGINEERING PARADIGM APPLIED
The one software engineering paradigm applied to the Teachers Record
Management System (TRMS) is the Agile Development Methodology.
Agile Development Methodology:
In TRMS, the Agile Development Methodology is employed to enhance
collaboration, flexibility, and responsiveness throughout the software
development process. Agile emphasizes iterative and incremental development,

allowing for continuous feedback and adaptation to changing requirements.

32
 Fig14:-Agile Software development

Key characteristics of Agile in Teacher Record Management System are:

 Iterative Development:
TRMS follows an iterative development process, breaking the project into small,
manageable iterations called sprints. Each sprint has a specific duration (e.g., 2-4
weeks) and results in a potentially shippable product increment. Feedback from
users and stakeholders is collected at the end of each iteration, allowing for
continuous improvement and refinement of the product in subsequent sprints.
 Adaptability:
Agile allows TRMS to be flexible and adaptable to changing requirements and
priorities. As educational needs evolve or new functionalities are identified, the
project team can easily incorporate these changes in the upcoming iterations. The
development team can reprioritize features based on the feedback received during
the iterations, ensuring the product remains aligned with the evolving needs of
users.
 Collaborative Approach:
Cross-functional teams in TRMS, including developers, designers, testers, and
product owners, work collaboratively throughout the development process.
Regular meetings like daily stand-ups and sprint reviews foster collaboration and
provide a platform for team members to share progress, challenges, and solutions.

33
 Stakeholders' involvement and feedback are encouraged and incorporated to
enhance the product.
 Customer-Centric Focus:
Agile places a strong emphasis on understanding and meeting customer needs. In
TRMS, regular reviews and demonstrations of the product increment are
conducted to gather feedback from stakeholders, including administrators,
teachers, students, and parents. This feedback is utilized to prioritize features and
make necessary adjustments, ensuring TRMS is tailored to address the specific
requirements and preferences of its users.
 Continuous Improvement:
Agile promotes a culture of continuous improvement within the development
team. At the end of each iteration, a retrospective meeting is held to reflect on
what went well, what didn't, and what can be improved. The retrospective
outcomes are utilized to implement process improvements in subsequent
iterations, leading to a more efficient and effective development process for
TRMS.

CHAPTER-7
IMPLEMENTATION AND SYSTEM TESTING
After all phase have been perfectly done, the system will be implemented to the server
and the system can be used.

SYSTEM TESTING:

The goal of the system testing process was to determine all faults in our project .The
program was subjected to a set of test inputs and many explanations were made and
based on these explanations it will be decided whether the program behaves as
expected or not. Our Project went through two levels of testing.

34
 Unit Testing: Unit testing is commenced when a unit has been created and
effectively reviewed .In order to test a single module we need to provide a
complete environment i.e. besides the section we would require

• The procedures belonging to other units that the unit under test calls
• Non local data structures that module accesses
• A procedure to call the functions of the unit under test with
appropriate parameters

Test for the admin module

• Testing admin login form: This form is used for log in of administrator of
the system. In this form we enter the username and password if both are
correct administration page will open otherwise if any of data is wrong it will
get redirected back to the login page and again ask the details.
• Report Generation: admin can generate report from the main database.

 Integration Testing: In the Integration testing we test various combination of the

project module by providing the input.

The primary objective is to test the module interfaces in order to confirm that no
errors are occurring when one module invokes the other module.

CHAPTER-8
PROJECT SCREENSHOTS
Home Page:

35
About Us:

36
Contact Us

Listed Teachers::

37
Teacher Detail:

Admin Login:

38
Dashboard:

Admin Profile

39
Change Password:

Add Subjects

40
Manage Subjects

Update Subjects:

41
Add Teachers:

Manage Teachers:

42
Update Teachers Information:

View Queries:

43
View details of queries:

Search Teachers:

Between Dates Reports:

44
View Between dates reports:

Forgot Password:

:
Teacher Panel:
Signup:

45
Login

Dashboard:

Manage Queries:

46
View Queries

Profile:

Change Password:

47
Forgot Password:

CHAPTER-9
FUTURE SCOPE OF THE PROJECT
CONCLUSION

48
 This Application provides an online version of Teacher Record Management
System which will benefit the school who want to maintain records of teacher and
also help to person who search teacher according to his/her requirement.
It makes entire process online and can generate reports. The Application was
designed in such a way that future changes can be done easily. The following
conclusions can be deduced from the development of the project.
• Automation of the entire system improves the productivity.
• It gives appropriate access to the authorized users depending on their
permissions.
• It effectively overcomes the delay in communications.
• Updating of information becomes so easier.
• System security, data security and reliability are the striking features.
• The System has adequate scope for modification in future if it is necessary.

FUTURE SCOPE OF THE PROJECT

The future scope of a Teacher Record Management System (TRMS) holds
immense potential for revolutionizing educational administrative processes and
improving educational outcomes. As education continues to evolve and embrace
digital transformation, TRMS can incorporate cutting-edge technologies such as
artificial intelligence (AI) and machine learning to provide predictive analytics for
optimizing teacher-student interactions and resource allocation. Furthermore, the
utilization of big data analytics can offer valuable insights into teaching
methodologies and student performance trends, enabling data-driven decision-
making for educators and administrators. The system could also expand to include
features like automated lesson planning, smart scheduling, and real-time
collaboration tools, transforming the teaching and learning experience. Ultimately,
the future of TRMS lies in leveraging innovative technologies to enhance
efficiency, effectiveness, and overall quality in the realm of education.

REFERENCES
For PHP
•https://www.w3schools.com/php/default.asp
•https://www.sitepoint.com/php/

49
•https://www.php.net/

For MySQL
•https://www.mysql.com/
•http://www.mysqltutorial.org

For XAMPP
•https://www.apachefriends.org/download.html

50