COLLEGE MANAGEMENT SYSTEM

A PROJECT REPORT

Submitted By
MD. SHAKAWAT HOSSAIN SUNY
ID No: 11508046

In partial fulfillment for the award of the degree

of
BACHELOR OF ENGINEERING
in
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

COMILLA UNIVERSITY:: CUMILLA-3506

NOVEMBER 2021
 COMILLA UNIVERSITY:: CUMILLA-3506

BONAFIDE CERTIFICATE

Certified that this project report “COLLEGE MANAGEMENT

SYSTEM” is the bona-fide work of “MD. SHAKAWAT HOSSAIN

SUNY” who carried out the project work under my supervision.

MD. HASAN HAFIZUR RAHMAN MD. MOHIBULLAH

CHAIRMAN, EXAM COMMITTEE SUPERVISOR
Assistant Professor Assistant Professor
Department of Computer Science Department of Computer Science
and Engineering and Engineering
Comilla University, Cumilla Comilla University, Cumilla
 Abstract

This project is aimed to developing an online College Management Information. The entire

project has been developed keeping in view of the distributed client server computing

technology, in mind. The project entitled \College Management System" is a web application.

It is developed using PHP and MySQL. This project has tried to incorporate all the advanced

features of PHP such as to ful ll the aim of the project. The application has been designed such

that it encompasses the managerial as well as public functionalities. Among the managerial

functionalities are the task performed by the various. The public features are exercised by the

users and outsiders according to the permissions level availed to them.

 Acknowledgements
At first, I want to express gratitude to the Almighty Allah for His endless kindness for keeping
us mentally and physically t to complete this project.

This project would not get its own shape without the support of the Comilla University which
provided us the chance for Bachelor’s Program in computer science and engineering. This
project is an aggregate of co-operation of many person.

Foremost, I would like to express my deepest gratitude to my honorable supervisor,

MD.MOHIBULLAH. His vast knowledge, attitude, behavior and wisdom are have given
myself the strength to work harder everyday. His directions and guidelines of preparing
manuscripts, reports, presentations made us more dynamic and well-organized throughout the
whole project. He gave us enough time from the beginning of the project, though he has a
tough schedule of his own task.

I also like to thank to all of my honorable teachers in department for giving me the proper
guideline throughout entire semester.

I want to thank all of my class mates who always inspired, helped and motivated me. I also
wish to thank all of my seniors for their utmost supports.

iii
Contents

Certificate i
Abstract ii

Acknowledgements iii

Contents iv

List of Figures vi

Abbreviations vii

1 Introduction 1

1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Purpose of CIMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Project Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 Literature Review 3

2.1
Perspective of System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2
Proposed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.3
Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.4
Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.5
Used Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.5.1 Software Requirement . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.5.2 Hardware Requirement . . . . . . . . . . . . . . . . . . . . . . . . . 5
3 Methodology and Design 6

3.1 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3.2 System Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Data Flow Diagram (DFD) . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3.1 Level 0 DFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

iv
Contents v
3.3.2 Level 1 DFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3.4 E-R Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.5 Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5.1 Sign In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5.2 Save Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5.3 Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.6 User Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4 Implementation and Result 13

4.1 Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.2 Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3 Input View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3.1 Student Data Enty . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3.2 Teacher Data Enty . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3.3 Subject Data Enty . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.4 Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4.1 Student View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4.2 Teacher View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4.3 Faculties View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.4.4 Subject View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.4.5 Score View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4.6 Article View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5 Conclusion and Future Directions 19

5.1 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.2 Future Scopes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

REFERENCES 21
List of Figures

3.1 Proposed System Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.2 Data Flow Diagram (DFD) . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3 Data Flow Diagram (DFD) . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.4 ER Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.5 Sign In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.6 Send Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.7 Blood Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.8 User Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1 login Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.2 Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.3 Student Request Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4 Teacher Request Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.5 Subject Request Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.6 Student View Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.7 Teacher View Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.8 Faculties View Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.9 Subject View Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.10 Score View Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.11 Article View Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

vi
Abbreviations

XML eXtensible Markup Language

ERD Entity Relationship Diagram
IDE Integrated Development Environment

vii
Chapter 1

Introduction

1.1 Introduction

This project is aimed at developing an online application for the College Management System
Dept. of the college. The system is an online application that can be accessed throughout the
organization and outside as well with proper login provided. The college management and sta
logging should be able to upload their information in the form of a CV and student record and
college department record uploaded. Visitor’s college sta representatives logging in may also
access/search any information put up by Students.

1.2 Purpose of CIMS

The purpose of College Information Management System is to allow the administrator of any
organization to edit and nd out the personal details of a student and allows the student to keep
up to date his pro le .It’ll also facilitate keeping all the records of students, such as their id,
name, mailing address, phone number, DOB etc. So all the information about a student will be
available in a few seconds.

Overall, it’ll make Student Information Management an easier job for the administrator and
the student of any organization.

1
Chapter 1. Introduction 2

The main purpose of this SRS document is to illustrate the requirements of the project
College Information Management System and is intended to help any organization to
maintain and manage its student’s personal data.

The main purpose of the project College Information Management System, is to reduce the
consumption of time during maintaining the records of college. Separate logins are provide to
maintain the records of teachers, students, and admin.

1.3 Scope

The CIMS will permit process impact gathering information about students from admission
cell and give it to sta . And another very important impact is taking classes, conducting
exams, maintaining fee details and examination etc., this is important features of college
information system

1.4 Project Outline

This project report will be structured as follows:

Chapter 2 introduces the Literature Review containing background knowledge and related
works in this eld.

In Chapter 3, we presents an overall interpretation of the methodology and design of the

project work.

In Chapter 4, we discussed about the results and how we implemented the College
management system.

Finally in Chapter 5, we conclude this project report with the future objectives for our system
and an overall epilogue.
Chapter 2

Literature Review

2.1 Perspective of System

The CIMS is a system that can help to maintaining student and sta information easily and it
will maintain the student records, library, schedules, important events and many other
important information related to college management. The website is aimed towards
recording a considerable number of student records and need assistance for managing their
data. Website is user-friendly, quick to learn and reliable. CIMS is a stand-alone product and
doesn’t depend upon the availability of any other websites. The system will have an
administrator who has full- edged rights with regards to performing all actions related to
control and management of the website and all relevant data.

2.2 Proposed System

There are two different users who will be using this product:

Admin who can view and edit the details of any students.

Faculty who can view their schedules, library, their pro le information as well as they can
edit their information

3
Chapter 2. Literature Review 4

The features that are available to administrator are:

An administrator can login into the system and perform any of the available operations

can delete user

can accept/decline user registration request

can edit user information records into database

can access all details

The features that are available to faculty are:

A faculty can login into the system and perform any of the available operations

can view his/her information

can edit their details

can access library records

can view their schedule

2.3 Characteristics

User should be aware of internet.

User should have a valid login ID and password.

Admin, faculty and student can access

Guest user send their registration request

2.4 Constraints

Every user must be comfortable using computer

All operations are in English so user must have basic knowledge of English.
Chapter 2. Literature Review 5

2.5 Used Technology

The CIMS systems is an web application. To run this application a device is required that on runs
on from any broswer. These are technologies used to implement the application.

2.5.1 Software Requirement

1. Operating System : Microsoft Windows 10

2. Data Base Server : Mysql

3. Front-End : HTML, CSS

4. Back-End : PHP

5. IDE : VS Code, Notepad etc.

2.5.2 Hardware Requirement

1. RAM 8 GB

2. Hard Disk 10 GB
Chapter 3

Methodology and Design

In this chapter we will present an overall interpretation of the methodology and design of our
proposed system .

3.1 System Architecture

The system is decomposed into the following processing steps:

1. Data collection and input.

2. Processing

3. Tentative output.

3.2 System Model

There are two types of User in our \College Management". Teacher and Student.

When a user will register to system then he/she will be a donor. Then he/she can update his
blood donating info and also can update their pro le info. Admin can update donors pro le
info and also their donating info.

6
Chapter 3. Methodology and Design 7

Figure 3.1: Proposed System Model

3.3 Data Flow Diagram (DFD)

CMS data ow diagram is often as preliminary step to create an overview of news portal without
going into great detail, which can be later elaborated. It generally consists of overall application
data ow and process. All of the below diagrams are used to visualize of data processing and
structured design of the blood management system.[1]

3.3.1 Level 0 DFD

Figure 3.2: Data Flow Diagram (DFD) level0

Chapter 3. Methodology and Design 8

3.3.2 Level 1 DFD

Figure 3.3: Data Flow Diagram (DFD) level1

Chapter 3. Methodology and Design 9

3.4 E-R Diagram

Entity Relationship Diagram, also known as ERD, ER Diagram or ER model, is a type of

structural diagram for use in database design. An ERD contains different symbols and
connectors that visualize two important information: The major entities within the system
scope, and the inter-relationships among these entities. And that’s why it’s called "Entity"
"Relationship" diagram. The E-R diagram of Blood bank management system shows all the
visual instrument of database tables and relation between contents. The main entities of the
proposed system are User and Blood.[2]

Figure 3.4: ER Diagram

Chapter 3. Methodology and Design 10

3.5 Activity Diagram

3.5.1 Sign In

Users provided must be match with database to sign in.

Figure 3.5: Sign In

3.5.2 Save Info

Users need to provide all information to store data.

Figure 3.6: Send Request

Chapter 3. Methodology and Design 11

3.5.3 Search

All users can search if the search by providing correct search value.

Figure 3.7: Blood Search

Chapter 3. Methodology and Design 12

3.6 User Case Diagram

Blood bank data ow diagram is often as preliminary step to create an overview of news portal
without going into great detail, which can be later elaborated. It generally consists of overall
application data ow and process. All of the below diagrams are used to visualize of data
processing and structured design of the news portal design.

Figure 3.8: User Case Diagram

Chapter 4

Implementation and Result

Implementation is the stage in the project where the theoretical design is turned into a
working system. The implementation phase constructs, installs and operates the new system.
The most crucial stage in achieving a new successful system is that it will work efficiently
and e effectively.

4.1 Login

This is the index of the web application. This is a login form

Figure 4.1: login Page

13
Chapter 4. Results 14

4.2 Home

This is the starting of the web application. All functionality can be accessed from the home.

Figure 4.2: Home Page

4.3 Input View

4.3.1 Student Data Entry

At the time of admission students information like personal details, contact details and education
details are saved in the database and the student id is generated by the system.

Figure 4.3: Student Data Entry Page

Chapter 4. Results 15

4.3.2 Teacher Data Entry

Figure 4.4: Teacher Data Entry Page

4.3.3 Subject Data Entry

Figure 4.5: Subject Data Entry Page

Chapter 4. Results 16

4.4 Result

4.4.1 Student View

Figure 4.6: Student View Page

4.4.2 Teacher View

Figure 4.7: Teacher View Page

Chapter 4. Results 17

4.4.3 Faculties View

Figure 4.8: Faculties View Page

4.4.4 Subject View

Figure 4.9: Subject View Page

Chapter 4. Results 18

4.4.5 Score View

Figure 4.10: Score View Page

4.4.6 Article View

Figure 4.11: Article View Page

Chapter 5

Conclusion and Future Directions

Thanks to almighty ALLAH WHO blessed us to understand and carry out this work within my
expected time-frame. By this project I am trying to help our country. All phases of this project
are important because any kind of mistake can damage the whole system. And this
documentation is the note of whole process of this college management system. The project
from a personal point of view helped us in understanding the following aspects of project
development:

The planning that goes into implementing a project.

The importance of proper planning and an organized methodology.

The key element of team spirit and co-ordination in a successful project.

The project also provided us the opportunity of interacting with our teachers and to gain from
their best experience We think that all kind of people of our country will get a great bene t
from this project.

5.1 Limitations

The part of the system can be implemented using the current technology although some modi
cations had to be done at various places. At various places some alterations with

19
Chapter 5. Conclusion and Future Directions 20

the prototypes and functionalities would be done in order to work out the cost constraints and
to cope with the scheduling constraints.

In this system we have don’t have facility for attendance management of student.

In this application search is limited to String or by number. Cannot do search by photo and
gure prints.

5.2 Future Scopes

The CIMS has been developed with a main aim of making work easier and time saving for
the human capital. The whole system is bi-lingual at present and can be extended to other
languages too with minor changes (not in coded).

The coding pattern is kept as dynamic as possible with minimum amount of static values to
make it easier for future extensions. As the current system is expected to add more
functionality and dependency according to requirement changes and technology, proper
coding standards and working platform have been kept in mind to produce a quality product.

One enhancement is that we can make this application in more than 1 language as well.
Adding attendance management is also one option for enhancement.
REFERENCES

[1] Data- ow diagram. . URL https://en.wikipedia.org/wiki/Data-flow_diagram.

[2] Entity{relationship model. . URL https://en.wikipedia.org/wiki/Entity%E2%

80%93relationship_model.

21