INDUSTARY ORIENTED PROJECT

TRAINING REPORT

COLLEGE MANAGEMENT SYSTEM

Submitted in partial fulfilment of the requirements for the award of

Degree of Bachelor of Technology in Information Technology

Submitted By

Name: Sabin Mudvari

University Roll No: 1507052

Submitted to

Department of IT
GLOBAL INSTITUTE OF MANAGEMENT AND EMERGINGTECHNOLOGIES
 DECLARATION
This is to certify that the work reported in the present project entitled “College Management
System” is a record of work done by me in the department of Information Technology. The reports
are based upon the project work done by me and not copied from any other source.

Sabin Mudvari

1507052

Date: 19 May 2019

Certified that the above statement made by the student is correct to the best of our knowledge
and belief.

Signatures
Examined by:

Head of Department

i
CERTIFICATE

ii
 ACKNOWLEDGEMENT

While presenting this report I would like to express my deep sense of gratitude to entire Broadway

Infosys Nepal. staff that were indispensable part of my training giving me unending guidance,

inspiration, encouragement and providing me excellent environment throughout my training at

BROADWAY INFOSYS NEPAL. The training was an extremely productive & enriching

experience, not only technically but also from providing practical skills.

I am extremely thankful to Mr. SAGUN SIWAKOTI who had devoted a lot of time in guiding

and supervising me during my training.

I must place my gratitude towards Prof. MEENAKSHI SHARMA (H.O.D. of IT Dept.) for their

valuable advice and guidance in carrying out this enjoyable and productive experience, which

provided me a great opportunity to search new horizons.

Signature of Student:

Sabin Mudvari (1507052)

iii
 ABOUT BROADWAY INFOSYS NEPAL PVT. LTD.

Broadway Infosys Nepal is one of the best inclusive computer training institutes in Kathmandu,
Nepal. Established in 2008, our professional IT Training and Development centre has been
employing experts in this field to impart professional education to trainees. We offer well-
structured complete professional training in various Programming Languages, Graphics &
Multimedia, Web Designing as well as Development Training that is based upon the current
recruitment needs in the IT market.

To summarize, Broadway Infosys is a complete learning institute that not only provides training
on various IT courses but also prepares students to smartly handle the real working environment.
We are dedicated and committed towards:

• Providing quality IT training to the aspiring IT professionals

• Availability of highly qualified and experienced instructors

• Assigning project works as per the nature of the courses

• Conducting regular project work evaluation sessions

• Identifying trainees' skills and knowledge gaps

• Taking corrective actions to enhance trainees' skills

• Providing internship and job placement facilities to the trainees

• Building long-term trustful relationship with the trainees

Since establishment, we have successfully established and maintained network with more than
fifty IT and other companies which has made us able to offer and provide our students with
internship and job opportunities.

iv
 Table of contentents
1. Introduction .................................................................................................................................... 1
1.1 Introduction ............................................................................................................................ 1
1.2 Purpose ................................................................................................................................... 1
1.3 Scope ....................................................................................................................................... 1
1.4 Technologies ........................................................................................................................... 2
2. Basic Concept and Definitions ........................................................................................................ 2
2.1 Product Perspective ................................................................................................................ 2
2.2 Functions ................................................................................................................................. 2
2.3 Characteristics ......................................................................................................................... 3
2.4 Constraints .............................................................................................................................. 3
2.5 USE CASE MODEL: ................................................................................................................... 3
2.5.1 ADMIN ............................................................................................................................. 3
2.5.2 FACULTY .......................................................................................................................... 3
2.5.3 STUDENTS ....................................................................................................................... 4
2.6 Assumptions & dependencies................................................................................................. 4
3. Requirements .................................................................................................................................. 4
3.1 Specific Functions.................................................................................................................... 4
3.2 Functional Requirements ...................................................................................................... 10
3.3 Non-Functional Requirements .............................................................................................. 10
4. Design............................................................................................................................................ 10
4.1 Objectives.............................................................................................................................. 10
4.2 System Architecture .............................................................................................................. 10
4.3 Data Design ........................................................................................................................... 11
4.4 Functional Design .................................................................................................................. 12
5. Technological Description ............................................................................................................. 13
5.1 HTML ..................................................................................................................................... 13
5.2 CSS ......................................................................................................................................... 13
5.3 JAVASCRIPT ........................................................................................................................... 13
5.4 MySQL ................................................................................................................................... 13
5.5 PHP ........................................................................................................................................ 14
6. Project Description........................................................................................................................ 15

v
 6.1 Introduction .......................................................................................................................... 15
6.2 Structure of the Database: .................................................................................................... 16
7. Snapshots ...................................................................................................................................... 17
8. Scope of the Project: ..................................................................................................................... 25
9. Bibliography .................................................................................................................................. 25
10. Conclusion ………..……………………………………………………………………………………………………………………. 25

List of figures
Figure 1: Use case - display user details ................................................................................................. 5
Figure 1: Use case - display user details ................................................................................................. 5
Figure 1: Use case - display user details ................................................................................................. 5
Figure 1: Use case - display user details ................................................................................................. 5
Figure 2: Use case - edit user details ...................................................................................................... 6
Figure 2: Use case - edit user details ...................................................................................................... 6
Figure 2: Use case - edit user details ...................................................................................................... 6
Figure 2: Use case - edit user details ...................................................................................................... 6
Figure 3: Use case - user registration...................................................................................................... 7
Figure 4: Use case - login into the website ............................................................................................. 8
Figure 5: Use case - edit user registration .............................................................................................. 9
Figure 6: Use case - entity relationship diagram .................................................................................. 11
Figure 7: Use case - data flow diagram ................................................................................................. 12
Figure 8: Database schema ................................................................................................................... 16
Figure 9: Home page - snapshot ........................................................................................................... 17
Figure 10: Programs - snapshot ............................................................................................................ 18
Figure 11: Notices - snapshot................................................................................................................ 19
Figure 12: Apply for admission - snapshot............................................................................................ 19
Figure 13: About us - snapshot ............................................................................................................. 20
Figure 14: Admin login - snapshot ........................................................................................................ 20
Figure 15: Applied for admission - snapshot ........................................................................................ 21
Figure 16: Albums - snapshot................................................................................................................ 21
Figure 17: Events - snapshot ................................................................................................................. 21
Figure 18: Notices - snapshot................................................................................................................ 22
Figure 19: Messages - snapshot ............................................................................................................ 22
Figure 20: Pages - snapshot .................................................................................................................. 22
Figure 22: Photos - snapshot ................................................................................................................ 23
Figure 23: Socials - snapshot ................................................................................................................. 23
Figure 21: Programs - snapshot ............................................................................................................ 23
Figure 24: Testimonials - snapshot ....................................................................................................... 24
Figure 25: Videos - snapshot ................................................................................................................. 24
Figure 26: Change password - snapshot ............................................................................................... 24

vi
1. Introduction
1.1 Introduction

The objective of College Management System is to allow the administrator of any

organization to edit and find out the personal details of a student and allows the student
to keep up to date his profile. 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 an easier job for the administrator and the student of any organization. The
main purpose of this project is to illustrate the requirements of the project College
Management System and is intended to help any organization to maintain and manage
personal data.
It is a comprehensive project developed from the ground up to full fill the needs of
colleges as they guide their students. This education edge integrated information
management system connects daily operations in the college environment ranging from
registration to finance, faculty, and library. This reduces data error and ensures that
information is always up-to-date throughout the college.
It provides a single source of data repository for streamlining your business processes
and for all reporting purposes.
It has a simple user interface and is intuitive. This insures that the users spend less time
in learning the system and hence, increase their productivity. Efficient security features
provide data privacy and hence; increase their productivity.

1.2 Purpose

The purpose of College Management System is to allow the administrator of any

organization to edit and find out the personal details of a student and allows the student
to keep up to date his profile. 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.
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 Management System is to reduce the
consumption of time during maintaining the records of college. Separate logins are
providing 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 staff. 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
1.4 Technologies

• HTML (Hyper Text Mark-up Language)

• CSS (Cascading Style Sheet)
• BOOTSTRAP
• Advanced Java (JSP)
• JAVASCRIPT
• MySQL

2. Basic Concept and Definitions

2.1 Product Perspective

The CIMS is a system that can help to maintaining student and staff 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-fledged rights with
regards to performing all actions related to control and management of the website and
all relevant data.

2.2 Functions

There are three 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 profile information as well
as they can edit their information
• Students who can view their details, library, course material, as well as they can
edit their information.

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

2
 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

The features that are available to faculty are:

▪ A student 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 course detail and related material

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.

2.5 USE CASE MODEL:

2.5.1 ADMIN

Responsible for managing user records.

• Login into the website

• Update the information

• Accept/Decline user request

• View user details

2.5.2 FACULTY

Rights to view and edit their personal details.

3
 • Login into the website
• View their details
• Edit their details
• View schedule information

2.5.3 STUDENTS

Rights to view and edit their personal details.

• Login into the website

• Edit their details
• View their details
• View course details

2.6 Assumptions & dependencies

• Administrator is created in the system already.

• Roles and tasks are predefined.
• Guest’s users can view college details.
• Guest can send application request.

3. Requirements
3.1 Specific Functions

Administrator: Responsible for managing student details.

Use-case: Login into the website

Goal: Gain access into the website

Brief: This use case is when the administrator wants to access the website to
accept/decline/update details of the student.

Perquisites: The admin must be logged onto the website for this se case to begin.

Basic Flow: The application asks the admin for the username and password the administrator
enter his/her details.
• The website validates and then verifies the details and send it to admin page.
• The administrator now given access to the website to perform their tasks.

Alternative Flow: The administrator enters invalidate username and password, then not
allowed to do any operations.

Use-case: Display user details

Goal: View user details

4
Brief: This use case is when the administrator wants to view the personal details of
users that are already existing in the database.

Perquisites:

• The admin must be logged onto the website for this se case to begin.
• The details of the users must pre-exist in the database.
• The student id must be entered correctly.

Basic Flow:

• The administrator logs onto the system.

• The administrator searches the user by
o Email
o Name

The system views the user detail.

Alternative Flow: User not found

If in the display, a user with the specific Id does not exist, system generates an error
message. The administrator can then enter a different Id or cancel the operation, when
error occurred.

Figure 1: Use case - display user details

5
Figure 2: Use case - display user details
Use-case: Edit user details
Goal: Edit the details of user

Brief: This use case is when the administrator wants to edit the personal details of
users that are already existing in the database.

Perquisites:

• The admin must be logged onto the website for this se case to begin.
• The details of the users must pre-exist in the database.

Basic Flow:

• The administrator logs onto the system.

• The administrator edits the user details
o Email
o First Name/Last name
o DOB
o Qualification
o City
o Contact No
o Address

The website updates the database according to the edited details.

Alternative Flow: No alternative flow for this use case.

Figure 5: Use case - edit user details

Figure 6: Use case - edit user details

Figure 7: Use case - edit user details

Figure 8: Use case - edit user details

6
 User: Student

Use-case: User registration

Goal: Registration of user

Brief: This use case is when the user send registration request himself/herself in the
database online.

Perquisites:

• The student must access the website for this use case to start.
• The input must be entered correctly.

Basic Flow:

• The student enters the website.

• The student fills his/her details from the following:
o Email
o Password
o First name/Last name
o Gender
o DOB
o Contact No
o Qualification
o Address

Alternative Flow: Validates all the user

Figure 9: Use case - user registration

7
User: Student

Use-case: Login into the website

Goal: Gain Access to the website

Brief: This use case is when the user wants to access the website.

Perquisites:

• The student must access the website for this use case to start.
• User input valid credentials.

Basic Flow:

• The website prompt user for details.

• The user enters the username and password.
• The websites verify the password.
• The user is given access to the website to form his tasks.

Alternative Flow:
The student enters invalid credentials then he will not be allowed to enter the website.

Figure 10: Use case - login into the website

8
 Use-case: Edit user registration

Goal: details of user registration

Brief: This use case is when the user wants to edit their details of himself/herself
already existing in the database.

Perquisites:

• The user must be logged into the system for this use case to start
• The details of the user must pre-exist into the database.
• The user must be enabled by administrator.

Basic Flow:

• The user logs onto the system.

• The user can edit the following keys:
o Address
o Contact No
o DOB
o Qualification

Alternative Flow:

There is no alternative for this diagram.

Figure 11: Use case - edit user registration

9
3.2 Functional Requirements

▪ The Administrator will be given more powers (accept/decline/update) than

other users.
▪ It ensures that the information entered is of correct format. For example, name
field cannot contain numbers. In case if incorrect information is given, the user
will be asked to fill the information again.
▪ The applications can be accessed any time.

3.3 Non-Functional Requirements

▪ The database may get crashed at any certain time due to virus of operating
system failure. Therefore, it is required to take the database backup.
▪ The proposed system we are going to develop will be used as the major
performance system for providing help to the organization in managing the
whole database of the student studying in the organization.

4. Design
4.1 Objectives

The overall design objective is to provide an efficient, modular design that will reduce
the system’s complexity, facilitate change and result in an easy implementation. This
will be accomplished by designing strongly cohesion system with minimal coupling. In
addition, this document will provide interface design models that are consistent user
friendly and will provide straight forward transition through the various system
functions.
The purpose of the design phase is to develop a clear understanding of what the
developer wants people to gain from his/her project. As you the developer work on the
project, the test for every design decision should be "Does this feature fulfil the ultimate
purpose of the project?" The Design Document will verify that the current design meets
all the explicit requirements contained in the system model as well as the implicit
requirements desired.

4.2 System Architecture

The CIMS is a system which contain major part which include: user detail, user records
and other options. The user selects one of the available options as an input to the system.
According to the input by the user the system acts, and the rest of the functions are
performed accordingly. The administrator can operate on any user details. But the
normal users can only access their details of all the functionalities.

10
 4.3 Data Design

Entity-Relationship Diagram

Figure 12: Use case - entity relationship diagram

11
 4.4 Functional Design

Data-Flow Diagram

Figure 13: Use case - data flow diagram

12
5. Technological Description
The technology selected for implementing College Management System is
JSP/MySQL. Glassfish is used as the HTTP server. The development was done in a
‘windows operating system’ using Net Beans IDE.

5.1 HTML

HTML (Hypertext Mark-up Language) is the most basic building block of the Web. It
describes and defines the content of a webpage. Other technologies besides HTML are
generally used to describe a webpage's appearance.
"Hypertext" refers to links that connect webpages to one another, either within a single
website or between websites. Links are a fundamental aspect of the Web. By uploading
content to the Internet and linking it to pages created by other people, you become an
active participant in the World Wide Web.

5.2 CSS

Cascading Style Sheets (CSS) are a stylesheet language used to describe the
presentation of a document written in HTML or XML (including XML dialects like
SVG or XHTML). CSS describes how elements should be rendered on screen, on
paper, in speech, or on other media. CSS is one of the core languages of the open web
and has a standardized W3C. Developed in levels, CSS1 is now obsolete, CSS2.1 is a
recommendation, and CSS3, now split into smaller modules, is progressing on the
standardization track.

5.3 JAVASCRIPT

JavaScript is a lightweight, interpreted programming language. It is designed for

creating network-centric applications. It is complimentary to and integrated with Java.
JavaScript is very easy to implement because it is integrated with HTML. It is open
and cross-platform.

5.4 MySQL

MySQL is a relational database management system (RDBMS) that runs as a server

providing multi-user access to several databases. MySQL is a popular choice of
database for use in web applications and is an open source product. The process of
setting up a MySQL database varies from host to host; however, we will end up with a
database name, a user name and a password. Before using our database, we must create
a table. A table is a section of the database for storing related information. In a table we
will set up the different fields which will be used in that table. Creating a table in
MySQL is simple, we just type the name, select the number of fields and click the ‘go’
button. we will then be taken to a setup screen where you must create the fields for the
database. Another way of creating databases and tables in MySQL is by executing
simple SQL statements. We have used this method to create our database and tables.

13
5.5 PHP

PHP (recursive acronym for PHP: Hypertext Pre-processor) is a widely-used open

source general-purpose scripting language that is especially suited for web development
and can be embedded into HTML.
• PHP is an acronym for "PHP: Hypertext Pre-processor"
• PHP is a widely-used, open source scripting language
• PHP scripts are executed on the server
• PHP is free to download and use

Why PHP:

• PHP runs on various platforms (Windows, Linux, Unix, Mac OS X, etc.)

• PHP is compatible with almost all servers used today (Apache, IIS, etc.)
• PHP supports a wide range of databases
• PHP is free. Download it from the official PHP resource: www.php.net
• PHP is easy to learn and runs efficiently on the server side

What Can PHP Do:

• PHP can generate dynamic page content

• PHP can create, open, read, write, delete, and close files on the server
• PHP can collect form data
• PHP can send and receive cookies
• PHP can add, delete, modify data in your database
• PHP can be used to control user-access

With PHP you are not limited to output HTML. You can output images, PDF files, and
even Flash movies. You can also output any text, such as XHTML and XML.

An introductory example

<!DOCTYPE HTML>
<html>
<head>
<title>Example</title>
</head>
<body>

<?php
echo "Hi, I'm a PHP script!";
?>

</body>
</html>

14
6. Project Description
6.1 Introduction

Student Management System can be used by education institutes to maintain the records
of students easily. Achieving this objective is difficult using a manual system as the
information is scattered, can be redundant and collecting relevant information may be
very time consuming. All these problems are solved using this project.
The directory structure of the project is as follows:

15
 6.2 Structure of the Database:

Figure 14: Database schema

16
 7. Snapshots

Figure 15: Home page - snapshot

17
Figure 16: Programs - snapshot

18
Figure 17: Notices - snapshot

Figure 18: Apply for admission - snapshot

19
Figure 19: About us - snapshot

Figure 20: Admin login - snapshot

20
Figure 21: Applied for admission - snapshot

Figure 22: Albums - snapshot

Figure 23: Events - snapshot

21
Figure 25: Messages - snapshot

Figure 24: Notices - snapshot

Figure 26: Pages - snapshot

22
Figure 27: Photos - snapshot

Figure 29: Socials - snapshot

Figure 28: Programs - snapshot

23
Figure 30: Testimonials - snapshot

Figure 31: Videos - snapshot

Figure 32: Change password - snapshot

24
8. Scope of the Project:
• The College Management System (CIMS) can be enhanced to include some
other functionality like marks, attendance management.
• Talent management of students based on their performance evaluation can be
added. Social networking can also be added wherein students can interact with
each other.
• Online class functionality can be added.
• Can evolve as an online institution.
• Functionality of chat and messages can be added.
• Online exam functionality can be added.

9. Bibliography
• The Complete reference on PHP
• www.google.com.
• www.wikipedia.com
• www.tutorialspoint.com
• www.getbootstrap.com
• www.studytonight.com
• www.stackoverflow.com
• www.roseindia.net

10.Conclusion
• 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 faculty.

25