INTERNATIONAL INSTITUTE OF PROFESSIONAL STUDIES

DEVI AHILYA VISHWA VIDHYALAYA

INDORE M.P.

Project Report

On

Study and Evaluation of Effectiveness of

College Management System

Dissertation Submitted in Partial fulfillment of the

Requirement for the Award of the Degree of

Master of Computer Application (6 Yrs.) IV Semester

Session - Jan-May, 2021

Under the guidance of: Submitted by:

Dr. Shaligram Prajapat Samriddhi Jariya

IC-2K19-76

Pradhumn Chourey

IC-2K19-60
COLLEGE MANAGEMENT SYSTEM

BONAFIDE CERTIFICATE

This is to certify that the project report entitled “College Management System”
submitted to Devi Ahilya Vishwavidyalaya in partial fulfillment of the
requirement for the award of degree of BACHELORS OF COMPUTER
APPLICATION (BCA), is an authentic and original work carried out by
Samriddhi Jariya (IC-2K19-76), Pradhumn Chourey (IC-2K19-60) under my
guidance.

The matter embodied in the project is genuine work done by the students and
has not been submitted whether to this or any other university/ institute for the
fulfillment of the requirement of any course of study.

Internal examiner: External examiner:

1
COLLEGE MANAGEMENT SYSTEM

RECOMMENDATION

The work entitled “College Management System” submitted by Ms.

Samriddhi Jariya and Mr. Pradhumn Chourey is satisfactory account of the
bonafide work under my supervision and is recommended towards the end of
their IV semester of MCA, Masters of Computer Application (6 Years).

Guided by:

Dr. Shaligram Prajapat

2
COLLEGE MANAGEMENT SYSTEM

ACKNOWLEDGEMENT

We acknowledge our sincere thanks to those who have contributed

significantly to this project. It is a pleasure to extend our deep gratitude to the
project guide Dr. Shaligram Prajapat, IIPS, for his valuable guidance and
support and to continuously prompt us for the progress of the project. We
thank him for his valuable suggestion towards our project, which helped us in
making this project more efficient and user friendly.

We thank and acknowledge each and everyone’s efforts that helped us in

some or the other way for small and significant things.

3
COLLEGE MANAGEMENT SYSTEM

ABSTRACT

College Management System (CMS) provides a simple interface for

maintenance of student information. It can be used by educational institutes
or colleges to maintain the records of students easily. The creation and
management of accurate, up-to-date information regarding a students’
academic career is critically important in the university as well as colleges.
Student information system deals with all kind of student details, academic
related reports, college details, course details, curriculum, batch details,
placement details and other resource related details too. It will also have
faculty details, batch execution details, students’ details in all aspects, the
various academic notifications to the staff and students updated by the
college administration. It also facilitates us to explore all the activities
happening in the college. Different reports and Queries can be generated
based on vast options related to students, batch, course, faculty, exams,
semesters, certification and even for the entire college. The placement officer
is responsible for updating the placement related information like eligibility
criteria for a particular company, arriving date for the company which is
coming for recruitment, the list of students who are eligible for attending the
recruitment process.

4
COLLEGE MANAGEMENT SYSTEM

TABLE OF CONTENTS

[Link]. TOPIC PG NO.

i. BONAFIDE CERTIFICATE 2.

ii. RECOMMENDATION 3.

iii. ACKNOWLEDGEMENT 4.

iv. ABSTRACT 5.

1. INTRODUCTION 8.
OVERVIEW

1.1 EXISTING SYSTEM 10.

1.2 PURPOSE 10.

1.3 SCOPE 11.

1.4 METHODOLOGY 12.

2. AIM AND OBJECTIVE 13

2.1 GOALS OF THE PROJECT 13..

2.2 OBJECTIVE 14

3. SYSTEM DEVELOPMENT LIFE CYCLE 15.

SDLC

3.1 FEASIBILITY STUDY 17.

3.3.1 TECHNICAL ECONOMICAL AND
OPERATION FEASIBILITY

3.2 ANALYSIS 20.

● INTRODUCTION
● USER REQUIREMENT

3.2.1 EXISTING SYSTEM 22.

5
COLLEGE MANAGEMENT SYSTEM

3.2.2 PROPOSED SYSTEM 23.

(DIAGRAM) 24.

3.2.3 DATA FLOW DIAGRAM 25.

1. 0 LEVEL 26.
2. 1 LEVEL 27.
3. 2 LEVEL 28.

3.3 PLANNING 29.

3.3.1 FUNCTIONAL REQUIREMENT
3.3.2 NON-FUNCTIONAL REQUIREMENT

3.3.3 ARCHITECTURE OF THE PROPOSED 30.

SYSTEM
3.3.4 HARDWARE REQUIREMENT
3.3.5 SOFTWARE REQUIREMENT
3.3.6 FUNCTIONAL REQUIREMENT

3.4 DESIGN 32.

3.4.1 DATABASE DESIGN 33

3.4.2 ENTITY RELATIONSHIP DIAGRAM 36.

● DIAGRAM 38.

3.4.3 GANTT CHART 39.

3.4.4 USE CASE DIAGRAM 42.

3.5 IMPLEMENTATION 44.

3.6 TESTING 45.

3.7 MAINTENANCE 48.

4. SCREENSHOTS 49.

5. FUTURE ENHANCEMENT 57.

6. CONCLUSION 58.

7. BIBLIOGRAPHY 59.

6
COLLEGE MANAGEMENT SYSTEM

INTRODUCTION:

➢ Overview

➢ Existing System

➢ Purpose

➢ Scope

➢ Methodology

7
COLLEGE MANAGEMENT SYSTEM

1. OVERVIEW:

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.

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 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 turn 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 has identity, state, and behavior.

8
COLLEGE MANAGEMENT SYSTEM

The design and implementation of a comprehensive Online

College Management System and user interface is to replace the
current paper records. College Staff are able to directly access all
aspects of a student’s academic progress through a secure, online
interface embedded in the college’s website.

The system utilizes user authentication, displaying only

information necessary for an individual’s duties. Additionally, each sub-
system has authentication allowing authorized users to create or update
information in that subsystem. In addition to a staff user interface, the
system plans for student user interface, allowing users to access
information and submit requests online, thus reducing processing time.
The system features a complex logging system to track all users’ access
and ensure conformity to data access guidelines and is expected to
increase the efficiency of the college’s record management thereby
decreasing the work hours needed to access and deliver student
records to the user.

9
COLLEGE MANAGEMENT SYSTEM

1.1 EXISTING SYSTEM:

Previously the college management primary focus was on managing

students and account sections and rest are going besides them. But this
is not the actual scenario of today’s environment. Apart from these,
there are other modules which exist in a particular college, which the
management will have to look after. Existing system was not paying
attention for managing their working employees, integration of library
management was not possible, thus another software has to be used
which requires extra investment and effort. If the college provided
boarding facility, hostel management and store management was not
available in the existing system.

1.2 PURPOSE:

⮚ Facilitates hassle-free management of the whole administrative

process.

⮚ Allows keeping relevant information about all the students, guardians,

teachers, and staff members so that it can be accessed by the
concerned authority anytime, as and when required.

⮚ It aids in enhancing the standard of an educational institution by

reducing the monotony and difficulty of dealing with routine tasks.

⮚ By eliminating loads of manual work and repetitive tasks, the software

helps in saving their time, money and resources.

10
COLLEGE MANAGEMENT SYSTEM

1.3 SCOPE:

⮚ This project deals with the various functioning in college management

process. The main idea is to implement a proper process to system. Our
existing system contains an operations registration, student search,
fees, attendance, exam records, performance of the student etc. All
these activities are performed manually by administrator.
⮚ In our model, it deals with the operations in system. For example, when
students fill the registration form the record is stored in the database.
And details of student are displayed by retrieving information from
database table.

Our project aims at business automation process i.e., we have tried to

computerize the various processes of college management system:

● In computer system a person has to fill various forms and number of

copies of the form can be easily generated.
● It is not necessary to create manifest but we can directly print it which
saves our time.
● To assist the staff in capturing the effort spent on their respective work
areas.
● To utilize resources in an efficient manner by increasing their
productivity through automation.
● The system generates different types of information, which can be
utilized for various purposes.
● It satisfies user’s requirement.
● It is easy to understand by user as well as operator.
● It is easy to operate.

11
COLLEGE MANAGEMENT SYSTEM

1.4 METHODOLOGY:

A methodology is a model, which is employed for the design, planning,

implementation and achievement of the project objectives. Methodology
has many research dimension and methods. Methodology is the
underlying principles and rules that governs the system method, on the
other hand it is a systematic procedure for a set of activities.

The system of collecting data for research project is known as research

methodology. The data may be collected for either theoretical or
practical research. For any project to be completed, it has to go through
many stages of System Development Life Cycle (SDLC).

12
COLLEGE MANAGEMENT SYSTEM

2. AIM AND OBJECTIVE:

2.1 AIM:
The application - ‘College Management System’, aims for the
automation of the existing manual College record system.

Aims and Goals to be achieved:

• Provide Accuracy.
• Reduce Redundancy of data.
• Conserve data safely.
• To provide computer-based system to overcome shortfalls in current
manual system.
• Creating a login for administrator, which should be easy to manage.

13
COLLEGE MANAGEMENT SYSTEM

2.2 OBJECTIVES:

Whenever we talk about college management, it doesn’t end with

managing students only. There are lots of sections where the college
management have to focus to run their college smoothly, look after
their administration sections, financial activities and much more. The
CMS is utilized to keep details of various departments and courses
offered by the college, student admission details, faculty details, day-
to-day attendance details, their salary details, end exam marks details,
internal marks details etc.

By building this information, the CMS software system can create

reports that are helpful for office staff, faculty, principal, HOD’s,
and for management within the administration.

Main objective of college management system project is to

record various details of activities of the college. It will simplify
college work. This system can maintain huge number of college
records including student, course, attendance, employee
etc. College management project is designed to remove all the
deficiency of the current system.

14
COLLEGE MANAGEMENT SYSTEM

SYSTEM DEVELOPMENT LIFE CYCLE:

➢ Feasibility Study
• Technical Economical and Operation Feasibility

➢ Analysis
• Existing System
• Proposed System
• Data Flow Diagram

➢ Planning
• Functional Requirement
• Non-Functional Requirement
• Architecture of the proposed system
• Hardware Requirements
• Software Requirements
• Performance Requirements

➢ Design
• Database Design
• E-R Diagram
• Gantt Chart
• Use Case Diagram

➢ Implementation

➢ Testing

➢ Maintenance
15
COLLEGE MANAGEMENT SYSTEM

3. SYSTEM DEVELOPMENT LIFE CYCLE

(SDLC):

The first phase of software project is to gather requirements. Gathering

software requirements begins as a creative brainstorming process in
which the goal is to develop an idea for new modules that no other
software vendor has thought. New software module ideas are normally
developed as a result of analyzing the project.

The main function of requirements gathering

phase is to take an abstract idea that fills a particular need or that solves
a particular problem and create a real-world project with a particular set
of objectives, timeline and team.

Some of the highlights of the requirements gathering phase include:

● Collecting project ideas.

● Gathering customer requirements and proposed solution.
● Justifying the project.
● Submitting the request for proposal
● Getting the team in phase.
● Preparing the requirements document.

Collecting project ideas:

Coming up with project ideas can prove expansion exercise.

Selecting Programming/Coding Language:

C++

16
COLLEGE MANAGEMENT SYSTEM

3.1 FEASIBILITY STUDY:

Whenever a new system (a hardware or software) is to be introduced, there is a

need to study the new system in every aspect or manner before working on it. We
get the idea whether the project is adequate or not.

The feasibility study is based on 3 major questions:

1. Does the candidate system meet the user requirement?

2. Is the problem worth solving?
3. The impact of the system on organization.

3.1.1 Technical, Economically & Operational

Feasibility:

1. Financial feasibility:

Financial feasibility refers to financial support required. It refers to

finance incurred during the development of the project.

2. Technical feasibility:

Technical feasibility refers to technical knowhow and auxiliary devices

required. The criteria for technical feasibility are:

● Easy to use
● Security
● Binary compatibility
● Reliability

3. Behavioral feasibility:

Refers to reaction of the people towards the project.

17
COLLEGE MANAGEMENT SYSTEM

4. Operational feasibility:

Operational feasibility means, is it possible to practically implement the

project. While installing this software, the hardware and software
requirements should be specified.

5. Cost feasibility:

The cost incurred by our system includes only the software cost and the
cost of computer needed to run the project.

6. Maintainability:

It usually comprises of two key factors:

● Updates: As the project is built with keeping in mind all the necessary
functions so no essential update is required.
● Terminals must be updated with antivirus so the proper functioning of
operating system can be maintained.

7. Portability:

As the size of the project is enormous. So, a compact drive can be used
to transfer it from one server to another. If required then data can also
be moved to secondary memory devices. So, it is portable to a large
extent.

8. Extensibility:

The project is easily extensible.

9. Reusability:

The extensibility and portability of the project would make it a reusable

software.

18
COLLEGE MANAGEMENT SYSTEM

3.2 ANALYSIS:

Introduction:
The main function of the analysis phase is to look carefully at the
requested features with an eye towards the issue that each may create
in the actual coding. This phase is the time during which reasonably
deliverable thoughts of each team member can be decided.

User Requirement:
The following requirements are raised during the analysis of the needs
of the users:

• A Person Should be able to login to the system through the first

page of the Application.
• The Administrator can create users as per user requirement.
• A general user will have access to see the status of particular
Student id number.
• Student (user) can use all the facilities, same as which are
provided to him in the college.
• Student can see attendance, notices, grades, report and other
facilities in updated manner.
• There will be a separate page for every student as his account, in
which he/she can get notices, attendance, grades, assignments
etc.
• Faculty can give the attendances and notices for the students.
• The administrator verifies all these reports and generates them
for users to view them.

19
COLLEGE MANAGEMENT SYSTEM

After analyzing the requirements of the task to be performed, the next

step is to analyze the problem and understand its context. The first
activity in the phase is studying the existing system and other is to
understand the requirements and domain of the new system. Both the
activities are equally important, but the first activity serves as a basis of
giving the functional specifications and then successful design of the
proposed system. Understanding the properties and requirements of a
new system is more difficult and requires creative thinking and
understanding of existing running system is also difficult, improper
understanding of present system can lead diversion from solution.

20
COLLEGE MANAGEMENT SYSTEM

3.2.1 EXISTING SYSTEM:

Previously the college management primary focus was on

managing students and account sections and rest are going besides
them. But this is not the actual scenario of today’s environment. Apart
from these, there are other modules which exist in a particular college,
which the management will have to look after. Existing system was not
paying attention for managing their working employees, integration of
library management was not possible, thus another software has to be
used which requires extra investment and effort. If the college provided
boarding facility, hostel management and store management was not
available in the existing system.

Disadvantages Of Existing System:

● Consumes more time

● Is Costly
● More manpower is required
● More work
● Less work results
● Room for errors

21
COLLEGE MANAGEMENT SYSTEM

3.2.2 PROPOSED SYSTEM:

It’s the new complex college management system presented in an interactive

way. Within this new college management system, lots of features have been
added to handle complex environment. Right from managing students, it has
been integrated with hostel management, library management, account
management, store management, employee’s management and bus
management.

Advantages Of Proposed System:

● The application can be accessed through the internet.

● It is a user-friendly application.
● Anyone can visit this application anytime.
● Information about college can be easily accessed and retrieved.

22
COLLEGE MANAGEMENT SYSTEM

Figure 1

23
COLLEGE MANAGEMENT SYSTEM

3.2.3 DATA FLOW DIAGRAM:

A data flow diagram (DFD) is a graphical representation of the "flow"

of data through an information system, modelling its process
aspects. A DFD is often used as a preliminary step to create an
overview of the system without going into great detail, DFDs can also
be used for the visualization of data processing (structured design).

A DFD shows what kind of information will be input to and output

from the system, how the data will advance through the system and
where the data will be stored.

The data flow diagram for college management system has following
3 parts:

1. 0 level data flow diagram

2. 1 level data flow diagram
3. 2 level data flow diagram

24
COLLEGE MANAGEMENT SYSTEM

0 LEVEL DFD:

ADMIN USER
DETAILS

GET INFO
MANAGE DATA

CMS

REPORT

25
COLLEGE MANAGEMENT SYSTEM

1 LEVEL DFD:

verified

User id & authen

admin tication Checking id Login info
pw

Deletin editing
g

remove modify

Removing entry Updating entry Updating entry

Students file Removing entry Faculty file

View student View faculty info

info

student
View
faculty
info info info

user Viewing
details
Generate
Getting report
report

Report
generator

report detail
s

26
 COLLEGE MANAGEMENT SYSTEM

2 LEVEL DFD:

View
info

Student info
Faculty info

Checking info

Student View personal info

profile
student faculty

Check performance

View personal info W.D. status

View attendance Check fee detail
details

Student Attend- Fee Faculty Working

performa days
ance details profile
nce
View profile

Details

View fee
View profile View info View info

Student file Faculty file

27
COLLEGE MANAGEMENT SYSTEM

3.3 PLANNING:

Planning is the process of thinking about the activities required to achieve

a desired goal. It involves the creation and maintenance of a plan, such
as psychological aspects that require conceptual skills. There are even
a couple of tests to measure someone’s capability of planning well.

3.3.1 Functional Requirement

● The system shall incorporate mechanism to authenticate its users.

● The system shall verify and validate all user input and should notify
in case of error detection and should help the user in error correction.

3.3.2 Non-Functional Requirements

● The system shall be user friendly and consistent.

● The system shall provide attractive graphical interface for the user.
● The system shall allow developer access to installed environment.
● The system shall target customer base.

28
COLLEGE MANAGEMENT SYSTEM

3.3.3 Architecture of The Proposed System

This process supports existing infrastructure requirements and provides

specific recommendations for hardware and network solutions based on
existing and projected user needs. Application requirements, data
resources, and people within an organization are all important in
determining the optimum hardware solution. It is represented using a
three-tier architecture that comprises of user interface, process
management and Database Management System (DBMS). It shows the
components of the system, the services they provide and the way they
communicate to bring about the system functionality.

3.3.4 Hardware Requirements:

Minimum Hardware Requirements:

✓ Processor: Intel Dual Core or better

✓ RAM: 2GB or more
✓ Processing Speed: 1GHz or more

29
COLLEGE MANAGEMENT SYSTEM

3.3.5 Software Requirements:

Minimum Software Requirements:

✓ Operating System: Windows 7 or above

✓ Integrated Development Environment: Code Blocks IDE
✓ Back End: Mysql Database (Workbench 8.0 CE)
✓ mysql-connector-c++-8.0.25

3.3.6 Performance Requirements:

✓ System should be able handle multiple users.

✓ Database should follow transaction processing to avoid data
inconsistency.

30
COLLEGE MANAGEMENT SYSTEM

3.4 DESIGN:

Design phase is the creation of a plan or convention for the

construction of an object, system or measurable human interaction.

We have mainly three modules:

1. Administrator module
2. Student module
3. Faculty module

Module Description:
I. Administrator:

The administrator can view and edit his own profile. He can register the
new students and faculty into the application. The administrator can
manage the account details and also, he can generate reports related
to fee payment, leaves and academics.

II. Students:

The administrator creates the profile of new students in the application.

After log-in into the application, the student can view, edit and update
his/her profile. The student can apply for leave and view its status. The
student can pay the fee in this application and view his academics.

III. Faculty:

The faculty can view, update or edit his/her profile in the application.
The faculty can search for the student leaves and he/she can approve
the leaves. The faculty can update the student academics.

31
COLLEGE MANAGEMENT SYSTEM

3.4.1 Database Design:

Conceptual design - Requirement analysis - What data is needed?

List of entities

● Admin
● Students
● Faculty
● Department
● Course
● Attendance
● Fees
● Exams

List of attributes

ADMIN:
● admin_id
● password
STUDENTS:
● s_name
● roll_no
● address
● class
FACULTY:

● f_name
● designation
● salary

32
COLLEGE MANAGEMENT SYSTEM

● f_id

DEPARTMENT

● d_name
● d_no

COURSE

● c_name
● c_no
● no_of_credit

EXAMS

● stud_name
● course
● marks

ATTENDANCE

● student_name
● roll_no
● course
● percentage

FEES

● roll_no
● course

33
COLLEGE MANAGEMENT SYSTEM

3.4.2 Entity-Relationship Diagram:

ER Diagram stands for Entity Relationship Diagram, also known as

ERD is a diagram that displays the relationship of entity sets stored in
a database. In other words, ER diagrams help to explain the logical
structure of databases. ER diagrams are created based on three basic
concepts: entities, attributes and relationships.

ER Diagrams contain different symbols that use rectangles to

represent entities, ovals to define attributes and diamond shapes to
represent relationships.

At first look, an ER diagram looks very similar to the flowchart.

However, ER Diagram includes many specialized symbols, and its
meanings make this model unique. The purpose of ER Diagram is to
represent the entity framework infrastructure.

ER Model stands for Entity Relationship Model is a high-level

conceptual data model diagram. ER model helps to systematically
analyze data requirements to produce a well-designed database. The
ER Model represents real-world entities and the relationships between
them. ER model helps you to analyze data requirements
systematically to produce a well-designed database. Creating an ER
Model in DBMS is considered as a best practice before implementing
your database.

Entity Relationship Diagram Symbols & Notations mainly

contains three basic symbols which are diamond, rectangle and oval
to represent relationships between elements, entities and attributes
respectively. There are some sub-elements which are based on
34
COLLEGE MANAGEMENT SYSTEM

main elements in ER Diagram. ER Diagram is a visual

representation of data that describes how data is related to each
other using different ERD Symbols and Notations.

Following are the main components and its symbols in ER

Diagrams:

• Rectangles: This Entity Relationship Diagram symbol represents

entity types.
• Ellipses: Symbol represent attributes. Diamonds: This symbol
represents relationship types.
• Lines: It links attributes to entity types and entity types with other
relationship types.
• Primary key: Attributes are underlined.
• Foreign key: Attributes are underlined by a dotted line.
• Double Ellipses: Represent multi-valued attributes.
• Double Rectangle: Represents weak entity.
• Double Diamond: Represents a weak relation.

Components of the ER Diagram

This model is based on three basic concepts:

● Entities
● Attributes
● Relationships

35
COLLEGE MANAGEMENT SYSTEM

Figure 2 - E-R Diagram

36
COLLEGE MANAGEMENT SYSTEM

3.4.3 GANTT CHART:

A Gantt chart is a project management tool assisting in the planning and

scheduling of projects of all sizes, although they are particularly useful
for simplifying complex projects. Project management timelines and
tasks are converted into a horizontal bar chart, showing start and end
dates, as well as dependencies, scheduling and deadlines, including
how much of the task is completed per stage and who is the task owner.
This is useful to keep tasks on track when there is a large team and
multiple stakeholders when the scope changes.

As it's in a bar chart format it is possible to check on progress with a

quick glance. You can easily see:
● A visual display of the whole project,
● Timelines and deadlines of all tasks,
● Relationships and dependencies between the various activities,
● Project phases.

When you set up a Gantt chart, you need to think through all of the tasks
involved in your project and divide them into manageable components.
Then decide who will be responsible for each task and delegate to the
team. Identify task relationships and decide on the completion date,
sequence for each task, showing the expected time duration of the
whole project and the sub tasks. A Gantt chart will:
• Show the tasks in a sequential order and display task dependencies
(i.e., how one task relates to another).
• Determine and allocate your resources.
• Anticipate the risks and problems you may encounter and create a
contingency plan for potential problems.

37
COLLEGE MANAGEMENT SYSTEM

Yellow: Samriddhi

Red: Pradhumn

Orange: Both

38
COLLEGE MANAGEMENT SYSTEM

3.4.4 USE CASE DIAGRAM:

A UML use case diagram is the primary form of system/software

requirements for a new software program underdeveloped. Use cases
specify the expected behavior (what), and not the exact method of making it
happen (how). Use cases once specified can be denoted by both textual and
visual representation (i.e., use case diagram). A key concept of use case
modeling is that it helps us design a system from the end user's perspective.
It is an effective technique for communicating system behavior in the user's
terms by specifying all externally visible system behavior.

A use case diagram is usually simple. It does not show the detail of the
use cases:

• It only summarizes some of the relationships between use cases,

actors, and systems.

• It does not show the order in which steps are performed to achieve
the goals of each use case.

39
COLLEGE MANAGEMENT SYSTEM

Figure 3 - Use Case Diagram

40
COLLEGE MANAGEMENT SYSTEM

3.5 Implementation:

Implementation is the stage in the project where the theoretical design is

turned into a working system and is giving confidence on the new system for
the users that it will work efficiently and effectively. It involves careful
planning, investigation of the current system and its constraints on
implementation, design of methods to achieve the changeover, an evaluation
of changeover methods. Apart from planning major task of preparing the
implementation are education and training of users. The more complex
system being implemented, the more involved will be the system analysis
and the design effort required just for implementation.

Implementation is the final and important phase. This is the

most critical stage in achieving a successful new system and in giving the
users confidence that the new system will work effectively.

The system can be

implemented only after thorough testing. This method also offers the greatest
security since the old system can takeover if the errors are found or inability
to handle certain type of transactions while using the new system.

There are various types of implementations:

● Implementation of a computer system to replace an old manual system.

● Implementation of a new computer system to replace an existing one.

● Implementation of modified application to replace an existing one.

41
COLLEGE MANAGEMENT SYSTEM

3.6 TESTING:

System testing is the stage of implementation, which is aimed at ensuring

that the system works accurately and efficiently before live operation
commences. Testing is vital to the success of the system. Testing is the
process of executing a program with the explicit intention of finding errors
that is making the program fail.

Different testing methodologies are used:

• Black Box Testing

• White Box Testing

Software testing methods are traditionally divided into black box testing and
white box testing. These two approaches are used to describe the point of
view that a test engineer takes when designing test cases.

Black Box Testing:

Black box testing treats the software as a “black box” without any
knowledge of internal implementation. Black box testing methods include:
equivalence partitioning, boundary value analysis, all-pairs testing, fuzz
testing, model-based testing, traceability matrix, exploratory testing and
specification-based testing.

White Box Testing:

White box testing, by contrast to black box testing, is when the tester has
access to the internal data structures and algorithms (and the code that
implements these). White box testing methods can also be used to evaluate
the completeness of a test suite that was created with black box testing
methods. This allows the software team to examine parts of a system that

42
COLLEGE MANAGEMENT SYSTEM

are rarely tested and ensures that the most important function points have
been tested.

Grey Box Testing

Grey box testing involves having access to internal data structures and
algorithms for purposes of designing the test cases, but testing at the user,
or black-box level. Manipulating input data and formatting output do not
qualify as “grey box” because the input and output are clearly outside of the
“black-box” that we are calling the system under test. This distinction is
particularly important when conducting integration testing between two
modules of code written by two different developers, where only the
interfaces are exposed for test. Grey box testing may also include reverse
engineering to determine, for instance, boundary values or error messages.

Non-Functional Software Testing:

Special methods exist to test non-functional aspects of software.

● Performance testing checks to see if the software can handle large

quantities of data or users. This is generally referred to as software
scalability. This activity of Non-Functional Software Testing is often times
referred to as Load Testing.
● Stability testing checks to see if the software can continuously function
well in or above an acceptable period. This activity of Non-Functional
Software Testing is often times referred to as indurations test.
● Usability testing is needed to check if the user interface is easy to use and
understand.
● Security testing is essential for software which processes confidential data
and to prevent system intrusion by hackers.
● Internationalization and localization are needed to test these aspects of
software, for which a pseudo localization method can be used.
43
COLLEGE MANAGEMENT SYSTEM

3.7 MAINTENANCE:

During the maintenance stage of the SDLC, the system is assessed to ensure
it doesn’t become obsolete. This is also where changes are made to initial
application/ software. It involves continuous evaluation of the system in terms
of its performance.

In the maintenance phase of SDLC we can add-on new content and update
our application according to change in college management system.

44
COLLEGE MANAGEMENT SYSTEM

4. SCREENSHOTS:

Figure 4

45
COLLEGE MANAGEMENT SYSTEM

Figure 5 - Home Page

46
COLLEGE MANAGEMENT SYSTEM

Figure 6 - Entry Menu

Figure 7

47
COLLEGE MANAGEMENT SYSTEM

Figure 8 – Student Details Entry Page

48
COLLEGE MANAGEMENT SYSTEM

Figure 9 - Display Student Details

49
COLLEGE MANAGEMENT SYSTEM

Figure 10 - Enquiry Menu

50
COLLEGE MANAGEMENT SYSTEM

Figure 11 - Modification Menu

51
COLLEGE MANAGEMENT SYSTEM

Figure 12 - Performance Menu

52
COLLEGE MANAGEMENT SYSTEM

Figure 13 - Modify Student Details

53
COLLEGE MANAGEMENT SYSTEM

Figure 14 - Modify College Details

54
COLLEGE MANAGEMENT SYSTEM

5. FUTURE ENHANCEMENT:

➢ Online examination module would be introduced to conduct online

examination.

➢ Scheduling of the staff i.e., time table setting of the staff function would
be introduced.

➢ Class as well as exam time tables i.e., faculty or staff members will
have an added functionality of creating time tables for lecture and exams
to be held.

➢ A feature to provide and accept assignment would also be introduced.

➢ Further, the faculty can upload the videos of their lectures on to this
site and students who missed those classes can view those videos.

55
COLLEGE MANAGEMENT SYSTEM

6. CONCLUSION:

The project entitled as College Management System is the system that

deals with the issues related to a particular institution.

• This project is successfully implemented with all the features

mentioned in 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 faculty. So, this serves the right
purpose in achieving the desired requirements of both the
communities.

56
COLLEGE MANAGEMENT SYSTEM

7. BIBLIOGRAPHY

● [Link]
Activities/academic-projects
● [Link]
iew?usp=drive_web
● [Link]
RvbWFpbnxkcnNoYWxpZ3JhbXByYWphcGF0aW5kaWF8Z3g6M2E2
M2MxNDMzNzFjMmViNw
● [Link]
QnB6V3IwVWFrUQ/view
● [Link]
w&resid=59EE15FA1399FE19!149&parId=59EE15FA1399FE19!117&
authkey=!ADv9ta8NwHIia90&app=Word
● [Link]
● [Link]
● [Link]
software/
● [Link]
● [Link]
● [Link]
management-software/
● [Link]
data-flow-diagram/
● [Link]
● [Link]
project_report

57
COLLEGE MANAGEMENT SYSTEM

● [Link]
information-management-system-on-advanced-java
● [Link]
[Link]
● [Link]
list/college-management-system
● [Link]
● [Link]
● [Link]
● [Link]
management-system/
● [Link]
management-system-55507131
● [Link]
management-system
● [Link]
● [Link]
● [Link]

58