'�

it
-

-, VISVESVARA YA TECHNOLOGICAL UNIVERSITY

BELAGAV1 -590018
--. i �
--
4
'l
••
·- A DBMS Mini Project Report On

-.
-- "COLLEGE MANAGEMENT SYSTEM"
-�

---� Submitted in the partial fulfilment of the requirements for the award of the Degree of
Bachelor of Engineering in Computer Science and
� Engineering
....::.-,
-_ "'l Submitted by

ARATHIKL (1OX17CS014)
BRINDA NAGARAJ POOJARY (1OXl 7CS022)

Under the guidance

of

Prof. Seema Patil

Project Guide

Department of Computer Science and Engineering

-1-I The Oxford College of Engineering
r• Hosur Road, Bommanahalli, Bengaluru-560068

--=- •
201
9-
202
0
 TIIE OXFOIU) COLLl <.,I : OF EN(;INEERING
I losur Rond. Bommnnuhulli, Ren •11luru 560068
(Af'flllnh'cl to Vlsws,•111·11)'11T,1ch11olo"knl lJnlvorNlly, Hcln nvl)

Dcparhncnf·of Computer Science and Engineering

CERTIFICATE
ertificd that the project work entitled "COLLl GE MANAGEMENT SYSTEM" carried
out by ARATHI KL (IOX17CS0l4), BRINDA NAGARAJ POOJARY (1OX17CS022),
bonafied students of The Oxford College of Engineering, Bengaluru in partial fulfilment for
the award of the Degree of Bachelor of l ngineering in Computer Science and
Engineering of the Visvesvan1ya Technological University, Belagavi during the year
2019-2020. It is certified that all corrections/suggestions indicated for Internal Assessment
have been incorporated in the report deposited in the deparhnental library. The project report
has been approved as it satisfies the academic requirements in respect of project work
prescribed for the said Degree.

p 0I ( �, (� �(/ � .d,A,.vm --;

.
Pr . Seema Patil 1
HP/o·�} �-�� lfl NT
Project Guide DEPARTMiif0r tDtlb iit:StiENGINEERING Princijfill (;) L
THE OXFORDCOLLEGEOFENGINEE"ING
T,h ,o_,f o r I
Colll•� d
. IIENtA1 i t! Ri8v1v11 Engineering
Bon1mr-111ahall1, Ho ur R =i
1
B ngciluru-s o OGS.
Name of Che Examiners Signature with Date
 DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
THE OXFORD COLLEGE OF ENGINEERING

Hosur Road, Bommanahalli, Bangalore-560068

(Approved by AICTE, New Delhi, Accredited by NBA, NAAC, New Delhi & Affiliated to VTU, Belagavi)

Department Vision

To establish the department as a renowned Centre of excellence in the area

of scientific education, research with industrial guidance, and exploration of
the latest advances in the rapidly changing field of computer science.

Department Mission

To produce technocrats with creative technical knowledge and

intellectual skills to sustain and excel in highly demanding world with
confidence.
 THE OXFORD COLLEGE OF ENGINEERING
Hosur Road, Bommanahalli, Bengaluru - 560068
(Affiliated to Visvesvaraya Technological University, Belagavi)

Department of Computer Science and

Engineering

DECLARATION

We, the students of fifth semester B.E, in the Department of Computer Science and
Engineering, The Oxford College of Engineering, Bengaluru declare that the Project work
entitled COLLEGE MANAGEMENT SYSTEM" has been carried out by us and
submitted in partial fulfilment of the course requirements for the award of degree in Bachelor
of Engineering in Computer Science and Engineering discipline of Visvesvaraya
Technological University, Belagavi during the academic year 2019-20. Further, the matter
embodied in the dissertation has not been submitted previously by anybody for the award of
any degree or diploma to any other university.
�dK•L £ /II I tq
ARATIDKL

\\\\\\
BRINDA NAGARAJ POOJARY

Place: Bengaluru

Date:c2.8 I\ l \c2D\

9
 ABSTRACT
The College Management System is a computerized management system. This project has

GUI based system that will help in storing, updating and retrieving information through

various user-friendly menu driven models. College Management System Project is based on

carrying out various tasks which goes under college management. College Management

System Project will control all activities for a particular college. To handle all the tasks,

system has been divided into different modules and presented on a single window, so that its

user can handle it in eco-friendly manner. Time is money for all students and student does not

have to face any difficulty if the staff members can track all the problems related to their

students. So that they can solve students problems on time and without wasting time.

•
 ACKNOWLEDGEMENT

A project is a job of great enormity and it can't be accomplished by an individual

all by them. Eventually, we are grateful to a number of individuals whose professional
guidance, assistance and encouragement have made it a pleasant endeavour to undertake this
project.

It gives us great pleasure in expressing our deep sense of gratitude to our respected
Founder Chairman Late. Sri S. Narasa Raju, and to our respected Chairman Sri S.N.V.L
Narasimha Raju, for having provided us with great infrastructure and well-furnished labs.

We take this opportunity to express our profound gratitude to our respected

Principal Dr. A. S. Aravind for his support.

We are grateful to the Head of the Department Dr. R.Ch. A Naidu, for his unfailing
encouragement and suggestion given to us in the course of our project work.

Guidance and deadlines play a very important role in successful completion of the
project on time. We also convey our gratitude to our internal project guide, Prof. Seema
Patil ,Associate Professor for having constantly guided and monitored the development of
the project.

Finally, a note of thanks to the Department of Computer Science Engineering, both

teaching and non-teaching staff for their co-operation extended to us.

We thank our parents for their constant support and encouragement. Last, but not the
least, we would like to thank our peers and friends.

ARATHI KL

BRINDA NAGARAJ POOJARY

ii
 TABLE OF CONTENTS
Abstract
Acknowledgment II
Table of Contents Ill
List of Figures Ill

1
Introduction
1.1 Preamble
1.2 Problem statement 2

1.3 Proposed solution 2

2 Analysis and System Requirements

2.1 Existing System 3

2.2 Hardware & Software Requirements 3

3
System Design and Modelling
3.1 Preliminary Design 4

3.1. lE R diagram 4

3.1.2 Database Schema diagram 6

3.2 Normalization 8

3.2.1 First Normal Form 8

3.2.2 Second Normal Form 8

3.2.3 Third Normal Form 9

4 Implementation
4.1 Implementation 10

4.2 Algorithm of implementation

4.2.1 Log into system 12
4.2.2 Adding student 12
4.2.3 Adding staff 12
4.2.4 Updating staff 12
4.2.5 Deleting student 13

5 Testing
5.1 Testing Objective 14
5.2 Testing Process 14

5.3 Level of Testing 14

5.3.1 Unit Testing 14
5.3.2 Integration Testing 16
5.3.3 System Testing 16
 tJ
-'FL
.

•
·"i 6 Conclusion 18

-.
� 7 References 19
8 Appendix A: Snapshots
�

� ;.
• �
LIST OF FIGURES
Figure 3. J: Schema diagram of college management System 7

••• . •
Figure 3.2: ER diagram of hotel management System 5

Figure A. J : Snapshot of login page 20

Figure A.2: Snapshot of home page 20

.
Figure A.3: Snapshot of students page 21

Figure A.4: Snapshot of staff page 21

Figure A.5: Snapshot of examination page 22

Figure A.6: Snapshot of finance page 22

�
• Figure A.7: Snapshot of hostel page 23

-• • 4-

�
• LIST OF TABLES
Table 5.1: Negative test case for adding student 15
�
� Table 5.2: Positive test case for adding student 15

'• •
�- Table 5.3: Positive test case for adding student 15
Table 5.4: Positive test case for input phone number 15
�
• Table 5.5: Test case on basics of generation of student
Table 5.6: Test cases for the project
16

17
�--
•
- - -•
�-

. •.,
«- -

.,
. •
• ·-
-..
·.
•
·
· -
.. ..
�

iii

..· -•
_

•
,-

·� r.
·-
 . ,'ij

-�
-�

i,
� -�

---
-

..
��

� ll
_
CHAPTER 1

INTRODUCTION
 w

,r..,,"

.•·,. CoHege Management System

. CHAPTER!
INTRODUCTION

..
�
- -
-. �

-..
�
� .

�
For accomplishing big projects , the number of developers work collectively on different
modules . Their efforts when combined together gives the final outcome .However ,a member
working on one module may encounter the need to understand other modules . Hence , he
may feel the need of telling the concerned member to explain his module . It may be time
consuming and troublesome for the concerned member to explain the entire code of the
� --�
module .Therefore,there arises a need for a tool like CLASS BROWSER which gives the
�---� class diagram of the entire module(project) . It is quite reliable and easy to understand.It also
-:, helps in debugging large projects.

fl::::_-:it The traditional view of software development takes an algorithmic

perspective. In this approach, the main building block of all software is the procedure or
� function. This view leads developers to focus on issues of control and the decomposition of
1.1 larger algorithms into smaller ones. There is nothing inherently evil about such a point of
view except that it tends to yield brittle systems. As requirements change and the system
grows, systems built on algorithmic focus tum out to be very hard to maintain.
The contemporary view of software development takes an object-oriented

.,
· :
.
perspective.In this approach , the main building block of all software systems is the object or
class.Simply put, an object is a thing, generally drawn from the vocabulary of the problem
space or the solution space ; a class is a description of a set of common objects. Every object

.
i f
has identity, state ,and behavior.

�
1.1 Preamble

-
�

,.
-. -;-.
 . - TJI College database management system keeps track of student details and depru1ment details

-�
and other facilities. A database management system is necessary in order to reach and
manage the data easily.it holds the vital information about status of the college where student
.1.

facilities and services.. The student and faculty can enjoy all the facilities that are offered by
-�
the college management

1.2 Problem Statement

Department of Computer Science and Engineering Page 1

 College Management System

A problem statement will outline the negative points of the correct situation and explain why
this matters. It also serves as a great communication tool helping to get buy-in and support
from others. One of the most important goals of any problem statement is to define the
problem being addressed in a way that is clear and precise. Its aim is to focus the process
improvement of the team's activities and steer the scope of the project.

1. In college management system, the administrator feels difficult in recording

each and every details of every student manually.
2. The student also feel difficult in checking the proper facilities offered by the
college.

1.3 Proposed Solution

The solution to the first problem addressed in this college management system is to provide a
computerized way of recording the details of student in order to make the task of
administrator to go on easier.

The second issue has been addressed by providing a separate page by listing out all the
facilities offered by the college.

Department of Computer Science and Engineering Page 2

 4-..
�-�
fr;.--.�
:.

�. -
=- . CHAPTER 2

--, ANALYSIS AND SYSTEM

. - .. REQUIREMENTS

._. �

�- �
-
--..
•
,-

.
••

···•
(1"-·
:c....
-·
)--
;,,,;;:-4t
<'f:r,;,---
r=f'
 College Mant.1gcmcnt System

CIIAPTER2
ANALYSIS AND SYSTEM REQUIREMENT
2.1 Existing System
Manual Process of this require a lot many of records to maintain College

..iuthorities need lo take care to store each and every student details and also there

examination details. Manunl process requires man power. Existing System is manual

process. Data Security is not provided in this system .Integrating duta is also a problem inthis

system .It is not User friendly system.

2.2 1-Iardware & Software Requirements

Hardware requirements:
• A minimum hard disk space of 20 Gigabytes(GJ3).

• RAM size of I GB
• Intel core i3 processor and AMO processor

• Keyboard

• Mouse

Software requirements:
• Windows operating system such as Windows 2000, Windows XP, Windows Vista,

Windows 7, Windows IO

... •
• Software: Xampp or Wamp
Front end: PI-JP (Hypertext Preprocessor)

• • Back end: MySQL

•
4
•
•
•
•
ff
•
·•
Page 3

I'.' ..
 CHAPTER3

SYSTEM DESIGN
AND MODELLING
 College Management System

CHAPTER3
SYSTEM DESIGN AND MODELLING
3.1 Preliminary design
System design is an abstract representation of a system component and their
relationship and which describe the aggregated functionally and performance of the system.
It is also the overal1 plan or blueprint for how to obtain answer to the question being asked.
The design specifies various type of approach.

Database design is one of the most important factors to keep in mind if you are
concerned with application performance management. By designing your database to be
efficient in each call it makes and to effectively create rows of data in the database, you can
reduce the amount of CPU needed by the server to complete your request, thereby ensuring a
faster application.

3.1.1 ER diagram
Entity-relationship diagram: This depicts relationship between data objects. The
attribute of each data objects noted in the entity-relationship diagram can be described using
a data object description.

Relationship: Data objects are connected to one another in a variety of different ways. We
can define set of object relationship pairs that define the relevant relationships.

Cardinality ratio: The data model must be capable of representing the number of
occurrences of objects in a given relationship. The cardinality of an object relationship pair is

1:N, 1:1,N:N,N:l.

Figure 3.1.I describes the ER diagram of College Management System. It has 5 entities
namely Student, Staff, Hostel, Examination and Finance. The entities have attributes which

are pn·mary, fioreign and composite attributes. The primary attributes are underlined.

Computer Science and Engineering Page 4

Departme11t Of
 College Management System

3.1.1 ER DIAGRAM

student_nam1

• Examination

0 I�
•

Figure 3.1. l ER diagram of College Management System

Department of Computer Science and Engineering Page 5

 College Management System

3.1.2 Schema Diagram

Database schema is described as database connections and constraints. It contains

attributes.

Every database has a state instances represent current set of database with values. There are
different types of keys in a database schema.

A primary key is a table column that can be used to uniquely identify every row of the
table. Any column that has this property, these columns are called candidate key. A
composite primary key is a primary key consisting of more than one column. A foreign is a
column or combination of columns that contains values that are found in the primary key of
some table.

All the attributes of each table are interconnected by foreign key which is primary key in
another column and composite key. Primary key cannot be null. The fact that many foreign
key values repeat simply reflects the fact that its one-to-many relationship. In one-to-many
relationship the primary key has the one value and foreign key has many values.

Figure 3.1.2 is a Schema diagram of College Management System which has five tables
i.e., Student, Staff, Examination, Hostel, Finance where each table contain attributes some
with primary key, foreign key. In the Student table there are 8 attributes- 'sid'(p1imary key),
'sname','student_image', 'father_name', 'coursel', 'batch','student_mob','address'. The staff
table has 7 attributes- 'staff_id'(primary key), 'staff_name', 'designation', 'phone', 'address',
'age', 'salary'. The hostel table has 7 attributes- 'r_no'(primary key), 'sid', 'sname',
'stu_mob', 'address', 'staff_id','warden_name','sid' (foreign key that references the primary
key of the student table- sid), 'staff_id'( foreign key that references the primary key of the
staff table- staff_id). The finance table has 5 attributes- 'staff_id'(primary key),
'designation','salary','sid','student_fee','staff_id'( foreign key that references the primary
key of the staff table- staff_id), 'sid'(foreign key that references the primary key of the
student table- sid). The examination table contains 4 attributes- 'sid'(primary key),'seat_ no,,'
subject','subcode' 'sid '(foreign key that references the primary key of the student table- sid).

•
Department of Computer Science and Engineering Page 6
 College Management System

3.1.2 SCHEMA DIAGRAlVI

Student
\V

sid sname stu_image father name course batch stud_mob add

I�

Staff J
staff id staff_name designation phone add age salary

Hostel
r no sid sname · Stumob add staff id warden name

I
Finance
I
staff id designation salary sid student- fee
I
Examination

[ &!![ seat_no [ subject subcodeI

•
•
•
•
'
••
Figure 3.J.2 Schema diagram of College Management System

Department of Computer Science and Engineering Page 7

t
 College Management System

3.2 Normalization
Nonnalization is a process of organizing the data in database to avoid data redundancy,
insertion anomaly, update anomaly & deletion anomaly. Let's discuss about anomalies first
then we will discuss normal forms with examples.

Anomalies in DBMS

There are three types of anomalies that occur when the database is not nomrnlized. These are
- Insertion, update and deletion anomaly.

3.2.1 First normal form (INF)

As per the rule of first normal form, an attribute (column) of a table cannot hold multiple
values. It should hold only atomic values

sid sname father name course batch phone

t
i
3.2.2 Second normal form (2NF)

table is said to be in 2NF if both the following conditions hold:

• Table is in INF (First normal form)

• No non-prime attribute is dependent on the proper subset of any candidate key of
table.

•
•
An attribute that is not part of any candidate key is known as non-prime attribute.

•
FuncHonaldcpenclency:

• sidsname, fathcr_namc, course, balch, phone

t

• Department of Computer Science and Engineering Page 8

 -;I College Management System

FDl
.,,

{
f
"' sid sname
-..I
f
t
FD2
-<Ill

r ....
I father_name I course I batch I phone
.:;J
t t t
..... t
�

-4 3.2.3 Third Normal form (3NF)

A table design is said to be in 3NF if both the following conditions hold:

--'
-4 • Table must be in 2NF

... • Transitive functional dependency of non-prime attribute on any super key should

be removed.
�
• An attribute that is not part of any candidate key is known as non-prime
-4
attribute.
_..
:I father_name course batch phone
sid sname
.
.._. l i
A l

•
�

...

Department ofComputer Science and Engineering

Page -
9
 CHAPTER 4
IMPLEMENTATION
 College Management System

CHAPTER4
IMPLEMENTATION
4.1 Implementation
Operations:

View student: This is for the students and staff in College Management System. ff the
student wants to view his profile, first he has to login and then go to the student icon by
clicking on that icon he can view his table. ff there is any changes to be done he can click on
the update button to update and if they want to delete whole table they can click on the delete
button.

Adding student: Here user adds the new student details by clicking on student from there by
clicking on student form and saves that is added to the st11dent table.

• Adding faculty: Here user adds the new staff details by clicking on faculty from there by
clicking on faculty fonn and saves that is added to the staff table.

.Updating student: If user wants to update any student in the student table, he can simply
update the student by clicking on that student blocks update button and can update the
information which he wants.

Deleting student: User can delete the student information if he does not want a particular
detail by just simply by clicking on the delete button, the student entire details will be
deleted.

SOL statements:
Insert statement: The INSERT INTO statement is used to insert new records in a table. The
INSERT INTO syntax would be as follows:
INSERT INTO table_nameVALUES (valuel, value2, value3, ...);
The following SQL statement insert's a new record in the "student" table:lnsert into
student VALUES(' l ','Dhanusha' ,'noimage,'malc','ChennappaGowda','BE','Mechanical'

,'9987656 3','singasandra Bangalore');

Update statement : An SQL UPDATE statement changes the data of one or more records in
a table. Either all the rows can be updated, or a subset may be chosen using a condition.
The UPDATE syntax would be as follows: UPDATE table_name SET colttmn_name==valtte
[ column_name==va/ue ... ] [WHERE condition].
The following updates a record in the "finance" table:

• UPDATE
Delete finance SET
statement : Thestaf(_id,
DELETE designation,
statement salary,
is usedsid, student_lee;
to delete existing records in a table.The

Department of Computer Science and Engineering Page 10

 ""
�

4 .. College Management System

DELETE syntax wouId be as fioIIows : DELETE FROM table name WHERE condition;

The following SQL statement delete's a record in the "student' table:

•
�
delete from student where sid=2·

.
'
Create statement :The CREATE TABLE Statement is used to create tables to student data.

• Integrity Constraints like primary key, unique key, foreign key can be defined for the
columns while creating the table. The CREATE syntax would be as follows:
CREATETABLE table_name(columnl datatype,column2 datatype,colurnn3

.. datatype,....columnN datatype,PRIMARY KEY( one or more colwnns ));

The following SQL statement creates a table "amount":

.... Create table student (sid int(5), snarne varchar(20), student_image varchar(20), father

.....
varchar(l O}, course varcbar(l 0), batch varchar(l O),student_mob varchar(l O),address
4
( varcbar(50), primary key(sid));

.._.
• Trigger statement: A trigger is a special kind of stored procedure that automatically

� executes when an event occurs in the database server. The trigger syntax would be as
( follows:

._.
t • Create trigger trigger_name before insert or update of <parameters> on <table_name> for
each row set <condition>;
• The following SQL statement triggers records in the "hostel" table:

..•.
• set new.saname=(select student.sname from student where new.sid= student.sid);
-4 • Stored procedure: A stored procedure is a set of SQL statements with an assigned
name, which are stored in a RDBMS as a group, so it can be reused and shared by multiple
programs. The stored procedure syntax would be as follows: Create procedure
'
rocedure name(input parameters, output parameters)as begin <sql statement used in
p -

.
stored procedure>end
• The following SQL statement creates a procedure:

4
,.
• Delimiter//

•
•
... •
•
·d aine ,f·due from students, fees f where s.sid=f.sid and f.due >O
S.S I , S.S11
End//
4_

•
2
Al
go
 rithm of implementation
.Computer Science and Engineering
Departmen t ot

Page 11
 4.-.l Lo-ginto
·-stem:
I. s

5.
6.

8.
9.
IO.I:
11 0
-rec: -- -:r -- :-:er:=_ ge

-t2._ Adding student:

• 1.

•
•
• -t�.3 Adding staff:

• 1.

'
' .2A Cpdating sr.aff:
L c· ::i."e

2.

3. C1
-4. li

-4.2- . Deleting tudent:

 Col1ege Management System

1. Click on the delete student button

2. Enter sid , if sid exits
3. Delete student from table
4. Jf sid does not exist
5. System message: Sorry! Student does not exist

-
JJi:partment (c1f, Cumpuwr Scle:nce:<1nd 1:ngincerlng
' r-===-=--�=-=====---==o...�=�====�=�===-===--==--=-,

•
•

CHAPTER 5
• TESTING

•
•
•
•
•
•
•
•
•
•
• '-==--===-- = ==- -==-= ==
 College Management_System

CHAPTERS

TESTING
This chapter gives the outline of all the testing methods that are carried out to get a bug free
application. Quality can be achieved by testing the product using different techniques at
different phases of the project development.

5.1 Testing process

Testing is an integral part of software development. Testing process, in a way certifies,
whether the product, that is developed, compiles with the standards, that it was designed to.
Testing process involves building of test cases, against which, the product has to be tested. In
some cases, test cases are done based on the system requirements specified for the
1' producUsoftware, which is to be developed.

.a 5.2 Testing objectives

The main objectives of testing process are as follows:
• Testing is a process of executing a program with the intent of finding an error.
• A good test case is one that has high probability of finding an as yet undiscovered
error.
• A successful test is one that uncovers an as yet undiscovered error.

5.3 Levels of Testing

Different levels of testing are used in the testing process; each level of testing aims to test

• different aspects of the system. The basic levels are unit testing, integration testing,

•
system testing and acceptance testing.
5.3.1 Unit Testing
•
•
Unit testing focuses verification effort on the smallest unit of software design the module.

•
The software built, is a collection of individual modules.

•
In this kind of testing exact flow of control for each module was verified. With detailed
desion consideration used as a guide, important control paths are tested to uncover errors

•
b

within the boundary of the module.

'•
• Table 5.1: Ncgati\'e test case for adding student

t
Page 14
 ... College Management System

... •
. I
•
.. •
•
.. •
�

•. .
...
.:.I

....
_..

.
.. .
•
•
•
•
 t
input for name

Function Name Input Expected Error Resolved

T
a Output
b
l
e
Create student Amith as first Expected - -
name output is
5
. seen
2
:

P Table 5.3: Positive test case for adding student

o
s
i Function Name Input Expected Error Resolved
t
i Output
v
e
Input phone number 998601957labc Must take alphabets are consume()
t only being taken as
e
s 9986019571 input for
t
as input phone number
c
a
s Table 5.4: Positive test case for input phone number
e

f
o Function Name Input Expected Error Resolved
r
Output
a
d Input phone number 9986019571 Expected - -
d
output is seen
i
n
g

s
t
u
d
e 5.3.2 Integration testing
n
The second level of testing is called integration testing. In this, many class-testedmodules
• Department of Computer Science and Engineering Page 15
 College Management System

are combined into subsystems. which nre then tested. The gonl here is to sc if nil th
modules can be integrated properly. We hnvc nre identified nnd d ·bug •ed.

Tnblc 5.5: Test cnsc on hnslcs of lmcrnllon of

shuknt

Function Input Expected Error Resolved

Name Output

Negative- Kokila Must display Output not seen Consume()

Checking for that invoice
student using name doesn't
invoice number exist

Positive- Amith Must display

Checking for that name
student using exits - -
invoice number

5.3.3 System testing

Here the entire application is tested. The reference document for this proce ·s 1s the
requirement document, and the goal is to sec JF the application meets its requirements.
Each module and component of ethereal was thoroughly tested to remove bugs through a
system testing strategy. Test cases were generated for all possible input sequences and the
output was verified for its correctness.

'fable 5.6: Tcsl for lhc

l
l'IISl'S 11rojl'l'I

Action _ Exp,'l'tcd output

Department of Computer Science and Engineering Pag • IC,

,, I

College Management System

• Step1: The screen appears when the A page with different tabbed panes

• choice
users runs the program
l.If student logs in
appears.
Student panel opens

,'
2.If staff logs in staff panel opens

Step2: The screen appears when the A window for viewing student detail.

', student logs in and selects

any one of the student from

•
I Selectionl
the click of the mouse
I.view student

• The screen appears when the A window for adding, deleting,

• student or staff logs in and updating, viewing stock and to

•
Step2.1: select any one of the tabbed generate invoice. To add and view
panes from the click of the student details. Student and staff can

'
mouse view his own details

••
1. Student
Selection2 2. Staff
3. Examinatrion
I
• 4. Hostel

• 5. Finance

•
I

•
I

•
•t
t
t
t
t
• Department of Computer Science and Engineering Page 17

•
 CONCLUSION

t
 College Management System

CHAPTER6

CONCLUSION

-, The project entitled as College Management System is the system that deals with the issues
related to a particular institution.

The project is successfully implemented with all the features mentioned in the system
requirements specification.

• The application provides appropriate information to users according to the chosen service.
The project is designed keeping in view the day to day problems faced by a college.

• Deployment of our application will certainly help the college to reduce unnecessary

• wastage of time in personally going to each department for some information.

'• Awareness and right information about any college is essential for both the development
of student as well as staff. So this serves the right purpose in achieving the desired

• requirements of both the communities.

•
'
t

•
•

Page 18
Department of Computer Science and Engineering
J

, College Management System

1 Chapter 7

.' REFERENCES

,
1. bttp://www.w3schools.com/htm1.doc
J
.J 2. http://-w,vw.w3schools.com/pbp.doc

3. http://www.tutorialspoint.com/literaturesurvey.doc

4. http://www.php.net/literaturesurvery.doc

5. Navathe Text Book

J

'
'
'
'•
•
'•
I
I
I
a

Departrn . . · Page 19
ent of Computer Science and Engmeenng
 College Management System

Chapter 8
Appendix: List of figure
Figure A.1: Snapshot of login page

..J toe...,,_.,, 11TOllllt°""9"/ >t rr 1,r&,•r,,.:.r-t111•.tw<1 " +

+- C Ci) 1tx,1tvu 1 ,, •;
- 0 X

e !

COLLEGE MANAGEMENT SYSTEM

I
I Figure A.2: Snapshot of home page

•
• •+

•
• Department of Computer Science and Engineering Page 20
 Figur,! A.3: Snapshot of studt•nts page

'

,'

Figure A.4: Snapshot of staff page

Depart Ill•nt of Computer Science and E· ng·me rl ng

 Management System
college
Snapshot of examination page
figure A.S:

'+

Figure A.6: Snapshot of finance page

De
artrnent of C . . .
omputer Science and Engmeenng Page 22
college ManagementSystem

figure A,.7: Snapshot of hodel page

,..,.r11J11,.,,.,,, ,, � .., ..
- " /

I,,C Q) IV.,-..,.!.

Depa: :, l!l!l!!!-!lll!l!!!l.l.!a-!!ll!!!ll------!l!'ll'll---!!!!m! ---!IIJ!!!!!!!!'8!'!1!1!11!11!!!!11!!1!11!1!!!!!!9

,rtment ofC omputer Science and Engineering Page 23