Final Project Report
Final Project Report
Final Project Report
1
To whom so ever it may concern
I, Laksh Patra, 12207745, hereby declare that the work done by me on “University
Management System” from 10-06-2023 to 30-07-2023, is a record of original work for the
partial fulfillment of the requirements for the award of the degree, Masters of Computer
Applications.
20-08-2023
2
CERTIFICATE
3
LIST OF FIGURES
1.1 Introduction 6
4.1 ER Diagram 11
4
CHAPTER 1
INTRODUCTION
1.1 Overview:
• Fee Department
• Examination Department
• Attendance
• Faculty information portal
• Student information portal
1.2 Purpose:
• Drive operational efficiency.
• Self-service systems with simple to use with little or no training.
• Elimination of duplicate data entry processes.
• Integrated with Online Application workflow with unified data model.
• Monitoring and decision support system.
• Automation of all the Academic / Examination / Administration operations.
• Ease and accuracy of reporting.
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. In our existing system contains a many
operations registration, student search, fees, attendance, exam records, performance of the
student etc. All these activity takeout manually by administrator.
5
CHAPTER 2
REQUIREMENT SPECIFICATIONS
Processor Count :1
RAM Size : 2 GB
6
CHAPTER 3
TOOL DESCRIPTION
An important issue for the development of a project is the selection of suitable front-
end and back-end. When we decided to develop the project we went through an extensive
study to determine the most suitable platform that suits the needs of the organization as well
as helps in development of the project.
The aspects of our study included the following factors.
Front-end selection:
1. It must have a graphical user interface that assists employees that are not from IT
background.
2. Scalability and extensibility.
3. Flexibility.
4. Robustness.
5. According to the organization requirement and the culture.
6. Must provide excellent reporting features with good printing support.
7. Platform independent.
8. Easy to debug and maintain.
9. Event driven programming facility.
10. Front end must support some popular back end like MySQL.
According to the above stated features we selected PHP and CSS as the front-end for
developing.
7
Here are some important Java applications:
8
SQL is the standard language for Relational Database System. All the Relational
Database Management Systems (RDMS) like MySQL, MS Access, Oracle, Sybase, Informix,
Postgres and SQL Server use SQL as their standard database language.
MySQL is a fast, easy-to-use RDBMS being used for many small and big
businesses. MySQL is developed, marketed and supported by MySQL AB, which is a
Swedish company. MySQL is becoming so popular because of many good reasons.[1]
MySQL works very quickly and works well even with large data sets. MySQL is
very friendly to PHP, the most appreciated language for web development. MySQL
supports large databases, up to 50 million rows or more in a table. The default file size
limit for a table is 4GB, but you can increase this (if your operating system can handle it)
to a theoretical limit of 8 million terabytes (TB).
9
CHAPTER 4
REQUIREMENT ANALYSIS
10
4.2 SCHEMA DIAGRAM:
Schema diagram A schema diagram is the skeleton structure that represents the logical view
of the entire database. It contains a descriptive detail of the database.
11
CHAPTER 5
TABLE DESCRIPTION
ACCOUNT TABLE
Account Table: Account table consists of five attributes which are Username, Name,
Password, Sec_ques, Sec_ans.Username is used as Primary key.
Desc account;
Student table :Student table is used to add the details of new student like
Name,phoneno.,DoB,course,Branch etc...Phoneno. ,E-mail and Aadhar are used as Primary
key.
Desc student;
12
TEACHER TABLE
Teacher table: Teacher table is used to add the details of new student like Name,
phoneno.,DoB, course,Branch etc...Phoneno. ,E-mail and Aadhar are used as Primary key.
Desc teacher;
ATTENDANCE_STUDENT TABLE
Desc attendance_student;
13
ATTENDANCE_TEACHER TABLE
Desc attendance_teacher;
SUBJECT TABLE
Subject table :Subject table is used to add the subjects of the student in that particular sem
with the attributes like rollno and five subjects.
Desc Subject;
14
MARKS TABLE
Marks table :Marks table is used to add the marks of the particular subjects of the student in
a particular sem and the attributes used are rollno and five subject marks.
Desc Marks;
FEE TABLE
Fee table:fee table is used to pay the fee dues of the student for that particular sem and the
attributes used like rollno, name, fathersname, course, branch, sem and fee_paid.
Desc Fee;
15
CHAPTER 6
Account table :Account table consists of five attributes which will be retrived from user when
the user signsup/logs in.
Student table: Student table is used to add the details of new student like
Name,phoneno.,DoB,course,Branch etc...Phoneno.E-mail and Aadhar are used as Primary key.
16
Teacher table :Teacher table is used to add the details of new student like
Name,phoneno.,DoB,course,Branch etc...Phoneno. ,E-mail and Aadhar are used as Primary
key.
17
Attendance_Teacher table :Attendance_Teachertable is used to mark the attendance of the
teacher day to day which as attributes like emp_id,name,first and second half.
Select * fromattendance_teacher;
Subject table : Subject table is used to add thesubjects of the student in that particular sem
with the attributes like rollno and five subjects.
18
Marks table :Markstable is used to add the marks of the particular subjects of the student in
a particular sem and the attributes used are rollno and five subject marks.
Fee table :fee table is used to pay the fee dues of the student for that particular sem and the
attributes used like rollno, name, fathersname, course, branch, sem and fee_paid.
19
CHAPTER 7
IMPLEMENTATION
Sample code :
Package institution.management.system;
importjava.awt.*;
importjavax.swing.*;
importjava.awt.event.*;
importjava.sql.*;
importinstitution.management.system.Signup;
privateJPanel panel;
privateJTextFieldtextField;
privateJPasswordFieldpasswordField;
privateJButton b1,b2,b3;
public Login() {
setContentPane(panel);
panel.setLayout(null);
20
panel.add(l1);
panel.add(l2);
panel.add(textField);
panel.add(passwordField);
panel.add(l3);
panel.add(l3);
b1 = new JButton("Login");
b1.addActionListener(this);
panel.add(b1);
b2 = new JButton("SignUp");
b2.addActionListener(this);
21
b2.setForeground(new Color(139, 69, 19));
panel.add(b2);
b3.addActionListener(this);
panel.add(b3);
panel.add(l5);
panel.add(panel2);
if(ae.getSource() == b1){
try {
22
conn con = new conn();
PreparedStatementst = con.c.prepareStatement(sql);
st.setString(1, textField.getText());
st.setString(2, passwordField.getText());
ResultSetrs = st.executeQuery();
if (rs.next()) {
this.setVisible(false);
new Loading().setVisible(true);
} else
e2.printStackTrace();} }
if(ae.getSource() == b2){
setVisible(false);
su.setVisible(true);}
if(ae.getSource() == b3){
setVisible(false);
forgot.setVisible(true);}
new Login().setVisible(true); } }
23
CHAPTER 8
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 the
process of executing the program with the intent of finding errors and missing operations and
also a complete verification to determine whether the objectives are met and the user
requirements are satisfied. The ultimate aim is quality assurance.
The software units in a system are modules and routines that are assembled and
integrated to perform a specific function. Unit testing focuses first on modules, independently
of one another, to locate errors. This enables, to detect errors in coding and logic that are
contained within each module. This testing includes entering data and ascertaining if the value
matches to the type and size supported by java. The various controls are tested to ensure that
each performs its action as required.
Data can be lost across any interface, one module can have an adverse effect on another,
sub functions when combined, may not produce the desired major functions. Integration testing
is a systematic testing to discover errors associated within the interface. The objective is to take
unit tested modules and build a program structure. All the modules are combined and tested as
a whole. Here the Server module and Client module options are integrated and tested. This
testing provides the assurance that the application is well integrated functional unit with smooth
transition of data.
Testing User acceptance of a system is the key factor for the success of any system.
The system under consideration is tested for user acceptance by constantly keeping in touch
with the system users at time of developing and making changes whenever required.
24
8.4 Test Cases:
Actual Expected
Test No. Test Name input Status
output output
User is User is
Username and
1 successfully successfully
Login password Pass
Authenticated Authenticated
Wrong Invalid Invalid
2 username and username or username or
Login Pass
password password password
User details Account Account
3 and successfully successfully
Signup Pass
passsword created created
Details of the Student Student
4 student inserted inserted
Student Pass
required. successfully successfully
Details of the Teacher Teacher
5 teacher inserted inserted
Teacher Pass
required successfully successfully
Enter the
subject names
Subjects Subjects
6 and marks
Subject entered entered Pass
along with
successfully successfully
rollno
Details and Paid Paid
7
Fee fee_paid successfully successfully Pass
Enter rollno
Remove Removed Removed
8 and click on
Student successfully successfully Pass
remove
Remove Enter emp_id Teacher Teacher
9 Teacher and click on removed removed
Pass
remove successfully successfully
Logout Logout
10 Exit Click on Exit
successfully successfully Pass
25
CHAPTER 9
SNAPSHOTS
1. Login form: This page represents the first thing about our website. It leads on to the login
point for its personnel; it takes up the username,password and signup.
2. Signup page: This page represents signing up to website. It leads to registering to website
making username and password, it takes the up username, name, password and security
question. These information are mandatory.
26
3. Home page user : This page shows us what user can see and access. He can add,
remove,update and upload the data. He can logout from the website in homepage.
4. Student form : In this we can add the new student details which will be stored in back end
of user.This details further can updated in the update page.
27
5. Teacher form: In this we can add the new teacher details which will be stored in back end
of user.This details further can updated in the update page.
6. Marks and Subject page : In this page we can enter the subjects and marks scored in that
particular subject along the rollno.
28
7. Fee payment page : In this page we can the pay the fee dues of the particular student which
uses rollno,course,branch and sem to pay the fee.
29
CONCLUSION
The project entitled as University 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 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.
30
REFERENCES
31