Project Report

ON

“TEACHER SUBJECT ALLOCATION SYSTEM”

Submitted in partial fulfillment of the requirements for the award of the degree
of

BACHELOROF BUSINESS ADMINISTRATION

(COMPUTERAPPLICATIONS)
BY
MOHAMMED RAJAALI SHAIKH ALIYAWARJANG KHATIK
&
SHAIKH ABU MAVIYA MOHD. GAUS

SEAT.NO: CAS_017 & CAS_029

UNDERTHEGUIDANCEOF

MS. RESHMA SHAIKH MCA

Asst. Professor
 YOUTH EDUCATION & WELFARE SOCIETY’S

NATIONAL SENIOR COLLEGE, Nashik.

(Affiliated to SPPU, Pune & Recognized by Govt. of Maharashtra)

2023-24

YOUTH EDUCATION & WELFARE SOCIETY’S

NATIONAL SENIOR
COLLEGE
AFFILIATED TO SAVITRIBAI PHULE PUNE UNIVERSITY, PUNE

DEPARTMENT OF COMPUTER
APPLICATION

CERTIFICATE

This is to certify that Mr./Miss. MOHAMMAD RAZAALI SHAIKH ALIYAWARJANG

KHATIK & SHAIKH ABU MAVIYA MOHD. GAUS bearing Register Number CAS_017 &
CAS_029 has satisfactorily completed project entitled “TEACHER SUBJECT

ALLOCATION SYSTEM” using PHP/MYSQL as prescribed by the Savitribai Phule Pune

University, Pune, for the B.B.A. (CA) – IV Semester course in the Computer Application

Laboratory of the college during March/April 2024.

Project Guide Head of the Department

Examiners:
1)………………………….

2) …………………………

Examination Center : (0838) NATIONAL SENIOR COLLEGE,

NASHIK.
Seat Number : ……………………………

Date of examination : ……………………………

 DECLARATION

We Mohammed Rajaali Shaikh Aliyawarjang Khatik & Shaikh Abu Maviya

Mohd. Gaus, hereby declare that this project entitled “Teacher Subject

Allocation System” is a record of independent work carried out by us under the

guidance of Ms. Reshma Shaikh.

We further declare that the findings in this project report are based on the

independent study done by us and this project has not formed the basis for the

award of any degree.

Place: Nashik

Date:

Mohammed Rajaali Shaikh Aliyawarjang Khatik

Shaikh Abu Maviya Mohd. Gaus
ACKNOWLEDGET
 We are over whelmed in all humbleness and gratefulness to acknowledge
my depth requital to all those who have helped us to put these ideas, well above
the level of simplicity and into something concrete.

We would like to thank our beloved Dr. S. B. Nahire Principal, National

Senior College, Nashik, for their valuable encouragement to complete this
project.

We express our deepest gratitude to Mrs. Shirin Maniyar, HOD,

Department of Computer Application, National Senior College, Nashik, for
providing the right direction in completing this project.
We would like to express our heartfelt gratitude to Ms. Reshma Shaikh,
Project Guide, Department of Computer Application, National Senior
College, Nashik, for their valuable guidance and suggestions in the phases of
completion of project and making it a successful one.

We would like to thank the Management, the teaching and non-teaching

staff of National Senior College, Nashik, who has served as the major
controllers towards the completion of the project.

We would like to thank our parents for giving encouragement, enthusiasm

and in valuable assistance and best owed upon me their blessings in completion
of project.
 Mohammed Rajaali Shaikh Aliyawarjang Khatik
Shaikh Abu Maviya Mohd. Gaus
CONTENTS
Sr. No Particulars Remark
INTRODUCTION
1.1. Introduction
1 1.2. Objectives and Goals of the System
1.3. Scope and Limitation
SYSTEM ANALYSIS AND DESIGN
2.1. System study
2 2.1.1. Existing system \
2.1.2. Proposed system
2.1.3. Feasibility study
SOFTWARE AND HARDWARE SPECIFICATION
3.1. Operating system
3 3.2. Software Specification
3.3. Hardware Specification
SYSTEM DESIGN
4.1. ER Diagram
4 4.2. Data Flow Diagram
4.3. Table design
SYSTEM TESTING AND IMPLEMENTATION
5.1. System testing
5 5.2. System Implementation
5.3. Maintenance
6 OUTPUT SCREEN AND REPORTS

7 CONCLUSION

8 FUTURE ENHANCEMENT

9 BIBLIOGRAPHY
 INTRODUCTION

1.1 INTRODUCTION

The Teacher Subject Allocation Management System is a comprehensive software solution

designed to streamline and optimize the process of assigning subjects to teachers within an

educational institution. This system aims to enhance the efficiency of academic planning,

improve resource utilization, and ensure that teachers are assigned subjects based on their

expertise and qualifications.

“Teacher Subject Allocation Management System” is web-based application system that

helps to allocate subjects to the teachers. In Teacher Subject Allocation Management System

educational administrators allocate different subjects to the teacher and teacher check that

allotment by their employee id and Name.

1.2 OBJECTIVES AND GOALS OF THE SYSTEM

The main objective of this Teachet Subject Allocation System is to computerize the manual
system & reduce the time consumption. In other words, we can say that our project has the
following objectives: -

➢ Make all the system computerize

➢ Reduce time consumption
➢ Reduce error scope
➢ All system managements are automated
➢ Centralized database management
➢ Easy operations for operator of the system
➢ No paper work requirement
➢ Improve Teachers Satisfaction
➢ Enhance Academic Planning
 1.3 PROJECT SCOPE AND LIMITATION

SCOPE OF THE PROJECT

A teacher subject allocation system developed in PHP has a wide scope and can offer various

functionalities to efficiently manage library operations. Here are some key aspects of the

scope of a teacher subject allocation system in PHP:

➢ Teacher Management: The system allows for the creation and management of

teacher accounts. It provides features like adding and managing teacher.

➢ Subject Management: The system allows for the creation and management of
Subject.

It provides features like adding and managing Subject.

➢ Course Management: The system allows for the creation and management of Course.

It provides features like adding and managing Subject.

➢ Subject Allocation: The system allows for the creation and management of subject

allocation to particular teacher. It provides features like adding and managing Subject

allocation.

➢ Admin Dashboard: The system includes an admin dashboard that allows

administrators to manage system settings, user accounts. The admin can also perform

administrative tasks like adding or removing teacher, subject, course.

LIMITATIONS OF THE PROJECT

While a teacher subject allocation system in PHP can provide significant benefits, it also has

certain limitations. Here are a few limitations to consider:

➢ Scalability: The system may have limitations in handling a large number of teachers,

subjects, or classes efficiently. As the number of users and data increases, the system's

performance may degrade.

➢ Resource Constraints: Depending on the infrastructure and resources available, there

may be limitations in terms of server capacity, storage, or computational power, which

could affect the system's performance under heavy loads.

➢ User Interface Complexity: If the user interface is overly complex or not intuitive

enough, users, particularly those less tech-savvy, may find it challenging to navigate

and use effectively.

➢ Integration with Existing Systems: Integrating the system with existing school

management systems or databases may pose challenges due to compatibility issues or

data migration complexities.

➢ Security Concerns: Ensuring the security of sensitive data such as teacher and student

information is crucial. The system may have limitations in terms of data encryption,

access controls, and vulnerability to cyber threats.

 SYSTEM ANALYSIS
AND DESIGN

2. SYSTEM ANALYSIS AND DESIGN

2.1 SYSTEM STUDY
Analysis is a detailed study of the various operations performed by a system and their

relationships within and outside the system. One aspect of analysis defining the boundaries of

the system and determining whether or not a candidate should consider other related systems.

During analysis, data is collected from the available files, decision points, and transactions

handled by the present system.

2.1.1 EXISTING SYSTEM

➢ In early days, subject scheduling was done manually which takes lot of time and

patients.

➢ It also increases paper work which is difficult to maintain.

➢ Subject was created by a single person or some group involved in thought of managing

time effectively.

➢ Even managing the record is done using the attendance register for staff.

➢ The staff need to submit their leave application manually to respective authorities.

➢ There will be a chance of losing the data.

LIMITATIONS OF EXISTING SYSTEM

➢ Lack of privacy

➢ Risk in the management of the data.

➢ Less Security

➢ Low co-ordination between

➢ Less User-friendly
➢ Accuracy not guaranteed

➢ Not in reach of distant users.

➢ There is no storage and automation if users have some enquiry.

 2.1.2 PROPOSED SYSTEM

“Teacher Subject Allocation Management System” is web-based application system that

helps to allocate subjects to the teachers. In Teacher Subject Allocation Management System

educational administrators allocate different subjects to the teacher and teacher check that

allotment by their employee id and Name.

In this project, we use PHP and MySQL database. It has one module i.e Admin

Admin Module

Admin is the super user of the website who can manage everything on the website. Admin can

log in through the login page

➢ Dashboard: In this section, admin can see all detail in brief like the total course, total

subjects and total teachers.

➢ Course: In this section, admin can manage the course (add/update/delete).

➢ Subject: In this section, admin can manage the subject (add/update/delete).

➢ Teacher: In this section, admin can manage the teacher (add/update).

➢ Subject Allocation: In this section, the admin can allocate subjects to their teachers.

➢ Search: In this section, admin can search uploaded details of subject allotment

Admin can also update his profile, change the password and recover the password.
Brief of Home Page

It is home page of “Teacher Subject Allocation Management System” on this teacher can

view allotment of subject by the help of their employee id.

2.1.3 FEASIBILITY STUDY

After the problem is clearly understood and the solutions are proposed, the next step is to

conduct the feasibility study, which is a part of system analyses well as system design

process. The main objective of the study is to determine whether the proposed system is

feasible or not. Manley there are three types of feasibility study to which the proposed

system subjected as described below. Three key considerations are involved in the

feasibility.

➢ Economic feasibility
➢ Technical feasibility
➢ Behavioral feasibility

The proposed system must be evaluated from a technical view point first and of technical

feasibility, their impact on the organization must be accessed. If compatible, behavioral

system can be devised. Then they must be tested for economic feasibility.

➢ Economic feasibility:
 Justification of any capital outlay is that it will reduce expenditure, improve the

quality of service of goods, which in turn may be expected to provide increased

profits. The technique of cost benefit analysis is often used as a basis for accessing

economic

feasibility.

➢ Technical feasibility:
The assessment of technical feasibility must be based on an outline design of systems

requirements in terms of inputs, output, files, programs and procedures this can be

qualified in terms of volumes of data, trends, frequency of update, cycles of activity

etc, in order to give an introduction of technical system.

➢ Behavioral feasibility:
People are inherently resisted to change and computers have been known to facilitate

change. Since the new proposed system is nothing to do with the ordinary customers,

the worker resistance to the system is very much less. The users might be scared of job

losses and other problems when a new system is introduced

 IMPLEMENTATION DETAILS
(SOFTWARE / HARDWARE
SPECIFICATION)

3.1 ABOUT THE OPERATING SYSTEM

OPERATING SYSTEM (WINDOWS 11)

 Windows 11 provides reliability and scalability. Lower your cost of computing with

powerful, flexible management services, and provides the best foundation for running

business applications. The system information is broken into several main categories and

subcategories.

The components category contains information about the Windows 11 system

configuration including multimedia, display, infrared, input, modems, network, ports, storage,

printing, problem devices, drivers, running tasks and software environment.

These options can be used to troubleshoot display, printing, speed and storage issues and

other Windows related issues such as running out of memory or running tasks that are

causing system problems.

The software environment category is used to display the software that is loaded in

your computer’s memory. This includes any drivers, print jobs, running tasks, loaded

modules, program groups and startup programs. This information is useful for determine

what is being loaded into, and possibly using too much, memory.
3.2 SOFTWARE SPECIFICATION

➢ Operating System : Windows 11

➢ Language Used : PHP5, PHP7

➢ Web Browser : Google Chrome, Mozilla, IE

➢ User interface : HTNL, AJAX, jQuery, JavaScript

➢ Back End : MS SQL Server 2014

➢ Software : Xampp, Wamp

3.3 HARDWARE SPECIFICATION

➢ Microprocessor : Intel i5

➢ RAM : 4 GB

➢ Speed : 3.6 GHz

➢ Monitor : 15” Color

➢ Key Board : 114 Keys

➢ Mouse : Lenovo Mouse

SYSTEM DESIGN
4.1 ENTITY RELATIONSHIP DIAGRAM
4.2 DATA FLOW DIAGRAM
Fig: CONTEXT LEVEL DFD
Fig: FIRSTLEVEL DFD
 Fig: SECOND LEVEL DFD
4.3 TABLE DESIGN
Table Name: tblAdmin

Sr
Field name Constraint Description
No
int (10)
1 ID ID of the Admin
primary Key
varchar (200)
2 AdminName Name of the Admin
Not Null
varchar (200)
3 UserName User name for the admin
Not Null
bigint(10) Not
4 MobileNumber Mobile no of the admin
Null
varchar (200)
5 Email Email id of the admin
Not Null
varchar (200 )
6 Password Password of the admin
Not Null
Timestamp
7 AdminRegdate Admin registration date
Not Null

Table Name: tblCourse

Sr
Field name Constraint Description
No
int (10)
1 ID ID of the Course
primary Key
2 BranchName varchar (200) Name of the Branch
 Not Null
varchar (200)
3 CourseName Name of the Course
Not Null
Timestamp
4 CreationDate Creation Date of the Course
Not Null

Table Name: tblSubAllocation

Sr
Field Name Constrain Description
No
int (5) primary
1 ID ID of the subject allocation
key
int (5)
2 CourseID
Not Null
ID of the course
varchar (100) Not
3 Teacherempid EmpID of the teacher
Null
int (5)
4 Subid
Not Null
ID of the subject
Timestamp Not
5 AllocationDate Date of the Assigning Allocation
Null

Table Name: tblsubject

Sr
Field name Constrain Description
No
Int (5)
1 ID Id of the subject
Primary key
Int (5)
2 CourseID ID of the course
Not Null
Varchar (200) Not
3 SubjectFullname Full name of subject
Null
 4 SubjectShortname Varchar (200) Not Short name of subject
Null
Varchar (200) Not
5 SubjectCode Code of subject
Null
Varchar (200) Not
6 CreationData Data of creation
Null

Table Name: tblteacher

Sr
Field Name Constrain Description
No
int (10)
1 ID ID of teacher
Primary key
Varchar (50) Not
2 EmpID ID of employee
Null
Varchar (200) Not
3 FirstName First name of teacher
Null
Varchar (200) Not
4 LastName Last name of teacher
Null
Bigint(10) Not
5 MobileNumber Mobile number of teachers
Null
Varchar (200) Not
6 Email Email ID of teacher
Null
Varchar (200) Not
7 Gender Gender of teacher
Null
Varchar (200) Not
8 DOB DOB of teacher
Null
int (5)
9 CourseID Course ID of teacher
Not Null
10 Religion Varchar (200) Not Religion of teacher
Null
Mediumtext Not
11 Address Address of teacher
Null
Varchar (200) Not
12 Password Password of teacher
Null
Varchar (200) Not
13 ProfilePic Profile Picture of teacher
Null
Timestamp Not
14 JoiningDate Joining date of teacher
Null
 SYSTEM TESTING AND
IMPLEMENTATION
5.1 SYSTEM TESTING
System testing is the stage of implementation, which is aimed at ensuring that the system

works accurately and efficiently before live operation commence. Testing is vital to the

success of the system. An elaborate testing of data is prepared and the system is tested using

this test data. While testing errors are noted and corrections are made. The users are trained to

operate the developed system. Both hardware and software securities are made to run the

developed system successfully in future.

Testing is a process of executing a program with the interest of finding an error. A good test is

one that has high probability of finding the yet undiscovered error. Testing should

systematically uncover different classes of errors in a minimum amount of time with a

minimum number of efforts. Two classes of inputs are provided to test the process
 1. A software configuration that includes a software requirement specification, a design

specification and source code.

2. A software configuration that includes a test plan and procedure, any testing tool and

test cases and their expected results.

Testing is divided into several distinct operations:

1. UNIT TESTING
Unit test comprises of a set test performed by an individual program prior to the integration

of the unit into large system. A program unit is usually the smallest free functioning part of

the whole system. Module unit testing should be as exhaustive as possible to ensure that each

representation handled by each module has been tested. All the units that makeup the system

must be tested independently to ensure that they work as required. During unit testing some

errors were raised and all of them were rectified and handled well. The result was quite

satisfactory and it worked well.

2. INTEGRATION TESTING

Integration testing is a system technique for constructing the program structure while at the

same time conducting tests to uncover errors associated with interfacing. The objective is to

take unit tested modules and build a program structure that has been dictated by design.

Bottom-up integration is the traditional strategy used to integrate the components of a

software system into functioning whole. Bottom-up integration consists of unit test followed

by testing of the entire system. A sub-system consists of several modules that communicated

with other defined interface.

The system was done the integration testing. All the modules were tested for their

Compatibility with other modules. They test was almost successful. All the modules

coexisted very well, with almost no bugs. All the modules were encapsulated very well so as

to not hamper the execution of other modules.

3. VALIDATION TESTING
After validation testing, software is completely assembled as a package, interfacing errors

that have been uncovered and corrected and the final series of software test; the validation

test begins. Steps taken during software design and testing can greatly improve the

probability of successful integration in the larger system. System testing is actually a series

of different tests whose primary purpose is to fully exercise the compute –based system.

4. RECOVERY TESTING
It is a system that forces the software to fail in a variety of ways and verifies that the recovery

is properly performed.

5. SECURITY TESTING
It attempts to verify that protection mechanisms built into a system will in fact protect it

from improper penetration. The system’s security must of course be tested from in

vulnerability form frontal attack.

6. STRESS TESTING

Stress tools are designed to confront programs with abnormal situations. Stress testing executes

a system in a manner that demands resources in abnormal quantity and volume.

7. BLACK BOX

Testing Black box testing is done to find out the following information as shown in below:

➢ Incorrect or missing functions.

➢ Interface errors.

➢ Errors or database access.

➢ Performance error.

➢ Termination error.

The mentioned testing is carried out successfully for this application according to the user’s

requirement specification.

8. TEST DATA OUTPUT

 After preparing test data, the system under study is tested using the test data. While testing

the system using test data, errors are again uncovered and corrected by using above testing

and corrections are also noted for future use.

5.2 SYSTEM IMPLEMENTATION

This is the part that puts a planned system into action and examine in details the analysis and

design of Teacher Subject Allocation System. The point discussed the implementation of the

system, highlighting the testing exercise and describing some of the main components of the

system’s Graphical User Interface. It will give an output from programming language and other

tools used to develop our system. According to this plan, the activities are to be carried out,

discussions made regarding the component and resources and the additional equipment has to be

acquired to implement the new system.

5.3 SYSTEM MENTAINANCE

The Program may be maintained on the ground that the system requires an upgrade when

there is a new field to be added or a new form to be added in other to serve users well. Though
it is compiled as a standalone software the database can be tempered with but it’s advisable

that the admin put a password on the file to secure the database from instruction.
OUTPUT SCREENS
 I/O SCREENS

FIG: ADMIN LOGIN

FIG: ADMIN DASHBOARD
FIG: ADD COURSE
FIG: ADD SUBJECT
FIG: ADD TEACHER
FIG: MANAGE TEACHER
FIG: SUBJECT ALLOCATION

FIG: ADMIN PROFILE

FIG: CHANGE PASSWORD
FIG: INDEX PAGE
CONCLUSION
 7.1 CONCLUSION

It has been a great pleasure for me to work on this exciting and challenging project. This

project proved good for me as it provided practical knowledge of not only programming in

PHP web-based application but also about all handling procedure related with “Teacher

Subject Allocation System”. It also provides knowledge about the latest technology used

in developing web enabled application and client server technology that will be great

demand in future. This will provide better opportunities and guidance in future in

developing projects independently. Since we have created the website of teacher subject

allocation system, it will become easier for admin to assign subject to teachers which has

access to the internet.

FUTURE ENHANCEMENT
 8.1 FUTURE ENHANCEMENT

Future enhancements for subject teacher allocation management systems include:

➢ Cloud-based online teacher subject allocation system

➢ Multi-channel, on-the-go access

➢ No software installations and updates

➢ Scanner
 BIBLIOGRAPHY AND

REFERENCES
9.1 BIBLIOGRAPHY

➢ php.net

➢ www.hotscripts.com/category/php/

➢ www.apache.org

➢ www.mysql.com/click.php?e=35050

➢ SOFTWARE ENGINEERING- Roger’s. Pressman

➢ COMPLETE HTML-Steven Holzner

➢ SQL FOR PROFESSIONALS-Jain