College PRO
College PRO
Date: -
This document specially mentions the details of the project how it was developed, the
primary requirement, as well as various features and functionalities of the project and the
procedures followed in achieving these objectives.
College Management forms the lifeline of the business institute to manage the
Employee and its salary ,Student and its Fee etc. It is very essential for an Institute to handle
the Salary, Fee and other expenses and their scale. It is very useful for an Institute to test its
employee, Student and other Staff continuously for their mutual development.
With the effective use, any Institute can apply the “College Management System” for
conducting quick attendance ,Payroll Management and Fee collection and getting better results
in less time.
Table of Contents
SR.NO Topic
1 Introduction to Organization
2 Introduction to System
4 Project Profile
5 System Overview
6 Objective
7 Scope
8 System Analysis
10 Feasibility Study
System design- Data Flow Diagram, System Flow Diagram, E-R Diagram,
12
Database Design, Coding, Screen Layouts
13 Conclusion
14 Summary
15 Bibliography
COLLEGE PROFILE
Necessity is the mother of invention, but it is not necessary that every invention is perfect. So
to make invention better and better, we need some amendments, and amendments should be
according to latest technology and most importantly they should we very easy to use.
Have you ever thought how difficult it is to maintain records? It’s not that easy as it
seems. It’s a collection of huge data base which should be maintained properly. This is a
common problem faced by universities, colleges, and other private institutes as few years
back all work was manually done which was a hectic work for record maintainer. So, to
solve this problem almost all universities and college wished to have software which could
be capable of maintaining records very easily and with less manual work. Some of the
universities and colleges have spent too much in developing or purchasing such software.
There is another case of those institutes who have such software, but these
software are not either functioning well, or fulfilling their requirements.
This system provides the detail structure of the college campus and its departments.
College Management System synchronizes the working of all the departments. It
looks on all aspects of a college, its students, faculties, Departments, marks and other
co – curricular activities.
1. Project Developer :
➢ Hardware:
• PENTIUM 4 or later.
• 80 GB HARD DISK DRIVE (FREE SPACE MEMORY).
• 512 MB RAM or more.
➢ Software:
➢ Development Tools:
➢ Time Management :-
The benefits of using a time and College management solution at your colleges
can not be underestimated. With thousands and thousands of employees, students,
teachers working in many institutions around the world, the need of an efficient
organizational system or programs are getting more and more vital. Therefore, there are
many colleges implementing College management solutions in order to improve
productivity.
➢ Create a Window application to be used in place of old paper based user Employee Salary
manage process.
➢ Use window and Microsoft Server technology to create strong and secured database
connectivity.
➢ Incorporate the server software within the code.
➢ Runtime package and deployment instructions are given.
In simple term we can say that Main aim in developing College Management System
is to provide an easy way not only to automate all functionalities of a college, but also to
provide full functional reports to top management of college with the finest of details about any
aspect of college.
College Management System is software has the perspective of attaining attraction of those
colleges which don’t have one good performing software for keeping their information secure
and make their management easier. College Management System provides one attractive environment
where you can manipulate data and information about students and staff easily. So we can say the
Core purpose of designing “College Management System” is to manage the task related to
the college students/employees and to reduce time to searching of appropriate candidates in
college view.
Scope
The scope of the project is the system on which the software is installed, i.e. the project
is developed as a desktop application, and it will work for a particular institute or organization.
But later on the project can be modified to operate it online.
This system will be used in one User Modules which are Administrator. As all of these
have different requirements the modules are designed to meet their needs and avoid any type of
confusion. The Uses of all three User Modules have been described below.
Hardware:
➢ Pentium IV.
➢ 80 GB Hard Disk Space.
➢ 512 MB RAM.
Software:
➢ Operating System: Windows XP or later.
➢ Front End: VB 6.0 .
➢ Back End: MS ACCESS.
System Analysis
Study & Weaknesses of Current System
Current System
In the present system all work is done on paper. The whole session data is stored in
register and at the end of the session the reports are generated. We are not interested in
generating report in the middle of the session or as per the requirement because it takes more
time in calculation. So, We are not able to get employees, students and teachers regularity
report and take necessary action on employees, students and Teachers whenever we want
because of having very time consuming process.
5. Time consuming:
Every work is done manually so we cannot Generate report in the middle of the
session or as per the requirement because it is very time consuming.
Requirements of New System
User Requirements.
The User requirements for the new system are to make the system fast, flexible, less
prone to errors and reduce expenses and save time.
➢ Time can be saved in scheduling the salary if it were available to make question
banks to store questions for different Employee in advance and can be used as per
required.
➢ A system that can automate the checking of answers which are pre-stored so that
results can be generated as soon as the Employee/student gives the reason.
➢ A facility that can generate result charts as per required without manual interference
for providing how a task is to be done instead only asking what is to be done.
➢ The system should have Employee/Student & its records on hand which can be used
as per required only by authorized personnel.
➢ The New system should be more secure in managing Employee records and reliable
enough to be used in any condition.
Feasibility Study:
A key part of the preliminary investigation that reviews anticipated costs and
benefits and recommends a course of action based on operational, technical, economic,
and time factors. The purpose of the study is to determine if the systems request should
proceed further.
➢ Economically Feasibility:
➢ Technical feasibility:
The technical requirement for the system is economic and it does not use any
other additional Hardware and software.
➢ Behavioral Feasibility:
The system working is quite easy to use and learn due to its simple but attractive
interface. user requires no special training for operating the system.
Features of the New System
The new system has been designed as per the user requirements so as to fulfill
almost all them.
1. User Friendly: -
The proposed system is user friendly because the retrieval and storing of
data is fast and data is maintained efficiently. Moreover the graphical user
interface is provided in the proposed system, which provides user to deal with
the system very easily.
Reports can be easily generated in the proposed system so user can generate
the report as per the requirement (monthly) or in the middle of the session. User
can give the notice to the employees ,students and Teachers to be regular.
The proposed system requires very less paper work. All the data is feted into
the computer immediately and reports can be generated through computers.
Moreover work becomes very easy because there is no need to keep data on
papers.
CONTEXT DIAGRAM:
The context diagram is a top-level view of an information system that shows the
boundaries and scope. It describes the main objective of the system and the entities involved.
Level 0:
Invalid
Request Response
Data Base
➢ DATA FLOW DIAGRAM (Level 1)
Employee Entry
Employee
Employee
Entry
Employee info
Working days
Entry
Working Working
Days Days
Days Info
Attendance Entry
Attendance
Attendance
Entry
Attendance Info
Salary Entry
Salary
Salary
Calculation
Salary Info
Paysilp
Start
Login
Check id
&
NO
Password
YES
Check login
Type
Admin
A
E-R Diagram
DATABASE DESIGN
MDI FORM
Form2.Show
End Sub
Form17.Show
End Sub
Shell "l:\windows\system32\calc.exe"
End Sub
Form7.Show
End Sub
Form10.Show
End Sub
Form9.Show
End Sub
End
End Sub
Form19.Show
End Sub
DataReport3.Show
End Sub
Form3.Show
End Sub
Form15.Show
End Sub
Form16.Show
End Sub
Form14.Show
End Sub
Form12.Show
End Sub
Form13.Show
End Sub
DataReport1.Show
End Sub
Form5.Show
End Sub
Form8.Show
End Sub
FORM 1-Login
MDIForm1.Show
Unload Me
Else
Text1.SetFocus
End If
End Sub
End
End Sub
Static A As Integer
If A <= 15 Then
Label3.ForeColor = QBColor(A)
A=A+1
Else
A=0
End If
End Sub
FORM 2
If Adodc1.Recordset.BOF Then
Adodc1.Recordset.MoveFirst
Else
Adodc1.Recordset.MovePrevious
End If
End Sub
Unload Me
MDIForm1.Show
End Sub
If Adodc1.Recordset.EOF Then
Adodc1.Recordset.MoveLast
Else
Adodc1.Recordset.MoveNext
End If
End Sub
Adodc1.Recordset.AddNew
Text1.SetFocus
End Sub
Dim A As Integer
If A = vbYes Then
Adodc1.Recordset.Update
End If
End Sub
FORM 3
Private Sub Command1_Click()
If Adodc1.Recordset.BOF Then
Adodc1.Recordset.MoveFirst
Else
Adodc1.Recordset.MovePrevious
End If
End Sub
If Adodc1.Recordset.EOF Then
Adodc1.Recordset.MoveLast
Else
Adodc1.Recordset.MoveNext
End If
End Sub
Unload Me
MDIForm1.Show
End Sub
Dim A As Integer
If A = vbYes Then
Adodc1.Recordset.Update
Else
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
Text9.Text = ""
Text10.Text = ""
Text12.Text = ""
Text1.SetFocus
End If
End Sub
Adodc1.Recordset.AddNew
Text3.SetFocus
End Sub
FORM - 4
Dim A As Integer
If A = vbYes Then
Adodc1.Recordset.Delete
End If
End Sub
If Adodc1.Recordset.BOF Then
Adodc1.Recordset.MoveFirst
Else
Adodc1.Recordset.MovePrevious
End If
End Sub
MDIForm1.Show
End Sub
If Adodc1.Recordset.EOF Then
Adodc1.Recordset.MoveLast
Else
Adodc1.Recordset.MoveNext
End If
End Sub
FORM-5
Private Sub Command1_Click()
Unload Me
MDIForm1.Show
End Sub
Text1.Text = Now
End Sub
FORM-8
Dim A As Integer
If A = vbYes Then
Adodc1.Recordset.Delete
End If
End Sub
If Adodc1.Recordset.BOF Then
Adodc1.Recordset.MoveFirst
Else
Adodc1.Recordset.MovePrevious
End If
End Sub
Unload Me
MDIForm1.Show
End Sub
If Adodc1.Recordset.EOF Then
Adodc1.Recordset.MoveLast
Else
Adodc1.Recordset.MoveNext
End If
End Sub
FORM-9
Private Sub Command1_Click()
If Adodc1.Recordset.BOF Then
Adodc1.Recordset.MoveFirst
Else
Adodc1.Recordset.MovePrevious
End If
End Sub
If Adodc1.Recordset.EOF Then
Adodc1.Recordset.MoveLast
Else
Adodc1.Recordset.MoveNext
End If
End Sub
Unload Me
MDIForm1.Show
End Sub
Dim A As Integer
If A = vbYes Then
Adodc1.Recordset.Update
End If
End Sub
FORM-10
Private Sub Command1_Click()
If Adodc1.Recordset.BOF Then
Adodc1.Recordset.MoveFirst
Else
Adodc1.Recordset.MovePrevious
End If
End Sub
If Adodc1.Recordset.EOF Then
Adodc1.Recordset.MoveLast
Else
Adodc1.Recordset.MoveNext
End If
End Sub
Unload Me
MDIForm1.Show
End Sub
Dim A As Integer
If A = vbYes Then
Adodc1.Recordset.Delete
End If
end Sub
Screen Layout
LOGIN FORM
MDI FORM
ADMISSION FORM
STUDENT DETAILS
LEAVE FORM
PROFESSOR ENTRY FORM
CLERK ENTRY FORM
PEON ENTRY FORM
EXAMINATION FORM
FEE RECORD FORM
CANTEEN BILL FORM
REPORTS
Conclusion
The main aim of this system was to put what we learnt in our software engineering
class into practice. The College management system designated to our team allowed us to
fully exercise the techniques of XP.
We were able to attain our set objectives, and this helped us again confidence in
writing our own code and our own applications. In addition, the use of serialization was an
experimentation to cut down the time taken in designing.
The front-ends and back-ends of applications separately. With our OOP approach
and serialization, we only concentrated on designing the objects/classes, and then just
serialized them on disk. So we did not spend any time on designing how to store data.
There is always room for improvement, and the software we created can also be
improved. This is especially because we had to create it within a limited time. With more
time, the software can be improved to include security and different types of users. This
would be the first step in marking the software network-enabled, and eventually web-
enabled.
This was our original after-thought to programming the software, and we had
chosen VB 6.0 . In addition, the software can also be improved in terms of the calculations
it addition, the software can also be improved in terms of the calculations it can do, and
more flexibility in the rates used in calculations per employee/student.
Bibliography
Reference:
➢ http://www.microsoft.com
➢ http://projectabstracts.com
➢ http://www.wikipedia.org
To bring the system of the verge of completion, the following books are being
referred: -
################