A

PROJECT REPORT

COLLEGE MANAGEMENT SYSTEM

Subject : SEN
(“Software Engineering” )
SUBMITTED BY

Mr. Lad Abhay .V [107]

Mr. Lakare Rohit .R [108]

Mr. Mahanor Shubham .C [115]

Mr.Nawale Sai .B [126]
Mr. Rajput Pruthavi .G [141]

Under the Guidance of

MS.M.B.CHARMAL
Lecturer

Department of Computer Technology

DEPARTMENT OF COMPUTER TECHNOLOGY,

SANJIVANI K.B.P POLYTECHNIC, KOPARGAON
 (2022-2023)

Sanjivani Rural Education Society’s

SANJIVANI K. B. P. POLYTECHNIC, KOPARGAON

CERTIFICATE
This is to certify that the Project report entitled
“COLLEGE MANAGEMENT SYSTEM”
SUBMITTED BY :

Mr. Lad Abhay .V [107]

Mr. Lakare Rohit .R [108]

Mr. Mahanor Shubham .C [115]

Mr.Nawale Sai .B [126]
Mr. Rajput Pruthavi .G [141]

Under our supervision and guidance for partial fulfilment of the requirement for
Diploma in Computer Technology affiliated to
Maharashtra State Board of Technical Education, Mumbai
For academic year
2022-2023
 Ms.M.B.Charmal Prof.G.N.Jorvekar

Project Guide H.O.D

Acknowledgement
First and the foremost we, express me deep sense of gratitude, sincere thanks and deep sense
of appreciation to Project Guide Ms.M.B.Charmal , Department of Computer Technology,
Sanjivani K.B.P. Polytechnic, Kopargaon. Your availability at any time throughout the year,
valuable guidance, opinion, view, comments, critics, encouragement, and support
tremendously boosted this project work. Lots of thanks to Head, Computer Technology
Department, Mr. G. N. Jorvekar for providing me the best support we ever had. We like to
express my sincere gratitude to Prof. A.R. Mirikar Principal, Sanjivani K. B. P. polytechnic,
kopargaon for providing a great platform to complete the project within the scheduled time.

We are also thankful to all the faculty member, Computer Technology Department, Sanjivani
K. B. P. Polytechnic, Kopargaon for giving comments for improvement of work,
encouragment and help during completion of the Project.

Last but not the least; we should say thanks from my bottom of heart to my family and friend
for their neverending love, help, and support in so many ways through all this time.

Thank you so much.

Mr. Lad Abhay .V

Mr. Lakare Rohit .R

Mr. Mahanor Shubham .C

Mr.Nawale Sai .B
Mr. Rajput Pruthavi .G [141]

Diploma in Computer Technology.

Sanjivani K. B. P. Polytechnic
Kopargaon. .
 INTRODUCTION OF THE COLLEGE MANAGEMENT SYSTEM

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’II 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’II make Student Information an easier job for the
administrator and the student of any Organizatiion.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
integrted information management system connects daily operation 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.


 INDEX
Sr.NO Contents Page No

1 Management
control

2 Waterfall Model

3 V Model

4 Incremental model

5 Iterative Model

6 RAD model

7 Spiral model

8 ER Diagram…
 Management control:-
 What is a Software Process Model?

Software Processes is a coherent set of activities for specifying, designing,

implementing and testing software systems. A software process model is an
abstract representation of a process that presents a description of a process
from some particular perspective. There are many different software
processes but all involve:

 Specification – defining what the system should do;

 Design and implementation – defining the organization of the system and
implementing the system;
 Validation – checking that it does what the customer wants;
 Evolution – changing the system in response to changing customer
needs.

 Types of Software Process Model :-

Software processes, methodologies and frameworks range from specific

prescriptive steps that can be used directly by an organization in day-to-day
work, to flexible frameworks that an organization uses to generate a custom
set of steps tailored to the needs of a specific project or group. In some
cases a “sponsor” or “maintenance” organization distributes an official set of
documents that describe the process.

 Waterfall model
 V model
 Incremental model
 RAD model
 Agile model
 Iterative model
  Spiral model

 Prototype model

 Waterfall Model

The waterfall model is a breakdown of project activities into linear

sequential phases, where each phase depends on the deliverables of the
previous one and corresponds to a specialisation of tasks. The approach is
typical for certain areas of engineering design.

 V Model
The V-model represents a development process that may be
considered an extension of the waterfall model and is an example of the more
general V-model. Instead of moving down in a linear way, the process steps are
bent upwards after the coding phase, to form the typical V shape. The V-Model
demonstrates the relationships between each phase of the development life cycle
and its associated phase of testing. The horizontal and vertical axes represent time
or project completeness (left-to-right) and level of abstraction (coarsest-grain
abstraction uppermost), respectively.
 Incremental model
The incremental build model is a method of software development
where the model is designed, implemented and tested incrementally (a little more is
added each time) until the product is finished. It involves both development and
maintenance. The product is defined as finished when it satisfies all of its
requirements. Each iteration passes through the requirements, design, coding and
testing phases. And each subsequent release of the system adds function to the
previous release until all designed functionally has been implemented. This model
combines the elements of the waterfall model with the iterative philosophy of
prototyping.
.
 Iterative Model
An iterative life cycle model does not attempt to start with a full
specification of requirements by first focusing on an initial, simplified set user
features, which then progressively gains more complexity and a broader set of
features until the targeted system is complete. When adopting the iterative
approach, the philosophy of incremental development will also often be used
liberally and interchangeably.
In other words, the iterative approach begins by specifying and implementing
just part of the software, which can then be reviewed and prioritized in order to
identify further requirements. This iterative process is then repeated by delivering a
new version of the software for each iteration. In a light-weight iterative project the
code may represent the major source of documentation of the system; however, in
a critical iterative project a formal software specification may also be required.

 RAD model
 Rapid application development was a response to plan-driven waterfall
processes, developed in the 1970s and 1980s, such as the Structured Systems
Analysis and Design Method (SSADM). Rapid application development (RAD) is
often referred as the adaptive software development. RAD is an incremental
prototyping approach to software development that end users can produce better
feedback when examining a live system, as opposed to working strictly with
documentation. It puts less emphasis on planning and more emphasis on an
adaptive process.
RAD may resulted in a lower level of rejection when the application is placed
into production, but this success most often comes at the expense of a dramatic
overruns in project costs and schedule. RAD approach is especially well suited for
developing software that is driven by user interface requirements. Thus, some GUI
builders are often called rapid application development tools.

 Spiral model
The spiral model, first described by Barry Boehm in 1986, is a risk-driven
software development process model which was introduced for dealing with the
shortcomings in the traditional waterfall model. A spiral model looks like a spiral
with many loops. The exact number of loops of the spiral is unknown and can vary
from project to project. This model supports risk handling, and the project is
delivered in loops. Each loop of the spiral is called a Phase of the software
development process.
 The initial phase of the spiral model in the early stages of Waterfall Life
Cycle that is needed to develop a software product. The exact number of phases
needed to develop the product can be varied by the project manager depending
upon the project risks. As the project manager dynamically determines the number
of phases, so the project manager has an important role to develop a product using
a spiral model.
 ER Diagram…
Conclusion: