System Analysis and Design Lab - Student Management System

Project Report - Submitted in Partial Fulfillment of the requirements

for the Award of the Degree of BSc in Computer Science And Engineering

SUBMITTED BY

Name ID

MD Tousif Zaman Fahim* : 19202103416

Kaiser Mahmud : 19202103427

Nazrul Islam Tareq : 19202103418

Abu Yusuf Sarker : 19202103417

SUBMITTED TO
Humayra Ahmed [ Lecturer (Dept. of CSE), BUBT ]
 INDEX

Topic Page Number

DECLARATION OF AUTHORSHIP—--------------------------------------------------- 3

CERTIFICATE—-------------------------------------------------------------------------------- 4

APPROVAL—----------------------------------------------------------------------------------- 5

ACKNOWLEDGEMENT—------------------------------------------------------------------- 6

1. SYSTEM OVERVIEW--------------------------------------------------------------------- 7-8

1.1 INTRODUCTION—-------------------------------------------------------------- 8

1.2 REASON FOR CHOOSING------------------------------------------------- 8

2. ANALYSIS OF THE SYSTEM---------------------------------------------------------- 9-20

2.1 ORGANIZATIONAL HIERARCHY —-------------------------------------- 10

2.2 MANAGEMENT INFORMATION------------------------------------------ 10

2.2.1 STRATEGIC INFORMATION—------------------------------------- 10

2.2.2 TACTICAL INFORMATION–—------------------------------------ 10

2.2.3 OPERATIONAL INFORMATION—-------------------------------- 11

2.3 DATA FLOW DIAGRAM—----------------------------------------------------- 11

2.4 USE CASE DIAGRAM——---------------------------------------------------- 12

2.5 ACTIVITY DIAGRAM----------------------------------------------------------- 14

2.6 FEATURES OF CURRENT SYSTEM—----------------------------------- 14

2.7 SCREENSHOT OF THE SYSTEM—--------------------------------------- 15

3. ALTERNATIVE PROPOSALS---------------------------------------------------------- 22-23

3.1 PROBLEMS —--------------------------—--------------------------------------- 23

3.2 SOLUTION—--------------------------------------------------------------------- 23

1
4. FEASIBILITY—------------------------------------------------------------------------------ 23-25

4.1 FEASIBILITY ANALYSIS-------------—--------------------------------------- 24

4.2 FEASIBILITY ANALYSIS OF SOLUTION—------------------------------ 24

4.2.1 TECHNICAL FEASIBILITY—----------------------------------------- 24

4.2.2 ECONOMIC FEASIBILITY—---------------------------------------- 24

4.2.3 OPERATIONAL FEASIBILITY—------------------------------------ 25

4.3 PAYBACK PERIOD—----------------------------------------------------------- 25

5. LIMITATIONS & CONCLUSION—---------------------------------------------------- 26-27

LIMITATIONS—--------------------------------------------------------------------------------- 27

CONCLUSION—-------------------------------------------------------------------------------- 27

REFERENCES—--------------------------------------------------------------------------------- 27

2
 DECLARATION OF AUTHORSHIP

We declare that this project entitled "Student Management System" and the works
presented in it are our own. We confirm that:

● This work was done wholly or mainly while in candidature for a B.Sc. Engineering
in CSE degree at this University.
● Where any part of this software development project has previously been
submitted for a degree or any other qualification at this University or any other
institution, this has been clearly stated.
● Where we have consulted the published work of others, this is always clearly
attributed.
● Where we have quoted from the work of others, the source is always given. With
the exception of such quotations, this thesis is entirely our own work.
● We have acknowledged all main sources of help.
● Where the thesis is based on work done by ourselves jointly with others, we have
made clear exactly what was done by others and what we have contributed
ourselves.

3
 CERTIFICATE

This is to certify that the project entitled, “Student Management System” and submitted
by,

MD Tousif Zaman Fahim* : 19202103416

Kaiser Mahmud : 19202103427

Nazrul Islam Tareq : 19202103418

Abu Yusuf Sarker : 19202103417

In partial fulfillment of the requirements of embodies the work done by them under my
supervisor,

Humayra Ahmed

Lecturer

Department of CSE

Bangladesh University of Business and Technology (BUBT)

4
 APPROVAL

This project “Student Management System” Submitted by MD Tousif Zaman Fahim* (ID -
19202103416); Kaiser Mahmud (ID - 19202103427); Nazrul Islam Tareq (ID - 19202103418);
Abu Yusuf Sarker (ID - 19202103417) Department of Computer Science and Engineering
(CSE), Bangladesh University of Business and Technology (BUBT) under the supervision
of Humayra Ahmed; Lecturer, Department of Computer Science and Engineering has
been accepted as satisfactory for the partial fulfillment of the requirement for the degree
of Bachelor of Science (B.Sc. Eng.) in Computer Science and Engineering and approved
as to its style and contents.

Supervisor
Humayra Ahmed

Lecturer (Dept. of CSE), BUBT

5
 ACKNOWLEDGEMENT

Our main focus is to design a unique Student Management system that will
improve Data Management in Institutes experience for Students. The system is
based on JAVA and MySQL. This project helps us a lot to learn java properly. We
use databases for the first time in our project. That was quite interesting for us. So,
in future we will do much better projects by adding databases in our projects.

Again, one more challenging problem is about our system hardware. We will need
a good requirement in the hardware section. Otherwise we will feel lag issues and
the development process will hamper.

6
 CHAPTER 1
SYSTEM OVERVIEW

7
1.1 INTRODUCTION
The project School Management System includes registration of students, storing their
details into the system. The software has the facility to give a unique id for every student
and stores the details of every student automatically. It includes a search facility to know
the current status of students.

Here the data can be retrieved easily. The interface is very user-friendly. The data is well
protected for personal use and makes the data processing very fast.

The School Management System is powerful, flexible, and easy to use and is designed
and developed to deliver real conceivable benefits to schools.

The School Management System is designed for multispeciality schools, to cover a wide
range of school administration and management processes. It is an integrated
end-to-end School Management System that provides relevant information across the
school to support effective decision making for student care and school administration, in
a seamless flow.

School Management System is a software product suite designed to improve the quality
and management of school management in the areas of clinical process analysis and
activity-based costing.

1.2 REASON FOR CHOOSING

The reason for making the school management system project is to make all the
management processes like students registration, teachers course etc. To find out the
students and teacher history, the user has to go through various registers. This results in
wastage of time. So, by this system it will become easy to manage all processes. So now
by taking the motivation of this scenario which was regularly done in schools we are
designing this system which can be beneficial for the students and school staff. So, we'd
like to possess this system which helps schools to do work fast and effectively.

8
 CHAPTER 2
ANALYSIS OF THE SYSTEM

9
2.1 ORGANIZATIONAL HIERARCHY

Fig-1 : Student management system hierarchy

2.2 MANAGEMENT INFORMATION

The informations of the system are discussed below -

2.2.1 STRATEGIC INFORMATION

Using a manual system to manage the students which records all information and in the
book or paper was causing the job of the teachers to become more and more
troublesome. The record has a possibility of missing or destroyed in any accident. Now
the school can use the computer to manage the student information.

2.2.2 TACTICAL INFORMATION

External interface requirements

● User interfaces The software provides a good graphical interface for the front end
which is self explanatory.

10
Hardware interfaces

● Memory minimum of 4GB RAM

● Hard disk of 30 GB
● Monitor
● Mouse
● Keyboard

Software interfaces

● Operating System Windows 10.

● Language JAVA
● MySQL

2.2.3 OPERATIONAL INFORMATION

Planning One Week

Define Requirements One Week

Design and Prototyping One Week

Software Development Four Weeks

Testing Deployment Two Weeks

Operations and Maintenance One Week

2.3 DATA FLOW DIAGRAM

11
2.4 USE CASE DIAGRAM

Fig : 3.0 Student management use case diagram

12
2.5 ACTIVITY DIAGRAM

Fig : 4.0 Student management system activity diagram

13
2.6 FEATURES OF CURRENT SYSTEM

You can do using this system:

● Add Student Information – In this feature the user can add the information
of the students.
● Update Student Information – In this feature the user can update the
information of the students inside the database.
● Delete Student Information – In this feature the user can delete any
information of the students inside the database.
● Print Student Information – In this feature the user can print the report or the
record of the students inside the database.

14
2.7 SCREENSHOTS OF THE SYSTEM

15
16
17
18
19
20
 CHAPTER 3
ALTERNATIVE PROPOSALS

21
3.1 PROBLEMS
By observing and conducting student management analysis; we find out some problems
from the beginning of the student that cause student management system as whole is
very weak and complexity in systematic orderly as following:

1. Weak on an administration management system

2. Student financial recording system
3. Student report management system
4. Student enrollment system
5. Student go by bus report
6. Student payment report
7. Student new session system
8. Staff management system
9. Inventory management system
10. Institution Asset management system
11. Waste time on controlling report
12. Use too many resources in the one problem function
13. Easy to lose the record
14. Difficult for gaining the report for use in effectively

3.2 SOLUTION
There are two different users who will be using this product:

1. Admin who can view and edit the details of any students/teachers.
2. Students and teachers who can view their details as well as they can edit their
details.

An Administrator can login into the system and perform any of the available operations:

● Can enable/disable student.

● Can edit student information to the database.
● Can make search for a specific student.
● Can access all the details of the student.

The features that are available to the student and teacher are:

● Students/teachers can login into the system and can perform any of the available
options.
● Can view his/her personal details,course,routine.
● Teachers can upload students' results.

22
CHAPTER 4
FEASIBILITY

23
4.1 FEASIBILITY ANALYSIS

The project topic of the student management system was put forward by the
project team after investigation, and then this topic formulated a questionnaire for
the project and conducted related surveys in some areas. During the investigation,
the project team conducted in-depth exchanges and statistics with teachers,
students, etc. and found that they had many concerns about the functions of the
existing system. Therefore, after the questionnaire survey, the project team
promptly summarized the needs of the respondents, put forward the project's
structural analysis of the student status management system, and finally
determined the solution to be solved.

4.2 FEASIBILITY ANALYSIS OF SOLUTION

Through the Student Management System project carried out a series of detailed
research, defined the feasibility of implementing the system project in terms of technical,
economical and operational factors to explain rationally to achieve the project objectives
implementation report, Carry out feasibility analysis of the problems to be faced in
software development.

4.2.1 TECHNICAL FEASIBILITY

We can strongly say that it is technically feasible, since there will not be much difficulty in
getting required resources for the development and maintaining the system as
well. All the resources needed for the development of the software as well as the
maintenance of the same are available in the organization where we are utilizing the
resources which are available already.

4.2.2 ECONOMIC FEASIBILITY

Development of this application is highly economically feasible. The organization needed

not spend much money for the development of the system already available. The only
thing to be done is making an environment for development with effective supervision. If
we are doing so, we can attain the maximum usability of the corresponding resources.
Even after the development, the organization will not be in condition to invest
more in the organization. Therefore, the system is economically feasible.
.

24
4.2.3 OPERATIONAL FEASIBILITY

This assessment involves undertaking a study to analyze and determine whether—and

how well—the organization’s needs can be met by completing the project. Operational
feasibility studies also examine how a project plan satisfies the requirements identified in
the requirements analysis phase of system development.

4.3 PAYBACK PERIOD

The payback period may be computed by the following formula:

Overall cost outlay/ Annual cash return = (A*B)+ (C*D)/ (5+2)=

Years + Installation time (G) / Years to recover

We are considering the costs of making this project 50,000 Tk and which will generate
10,000 Tk per year of net cash flow. The payback period for this capital investment is 5.0
years. We are also considering updating the project for 36,000 Tk, which will increase
the income of the project by 12,000 Tk per year. The payback period for this capital
investment is 3.0 years. If we only have sufficient funds to invest in one of these projects,
and if it were only using the payback method as the basis for its investment decision, It
has a shorter payback period.

25
 CHAPTER 5
LIMITATIONS & CONCLUSION

26
LIMITATIONS

The system does not cover the computation of students' grades and paying of
fees. Not accepting any online payments. It can only operate for student
enrollment purposes. It can’t show the schedule of the course at the per year
level.

CONCLUSION

After completing this project, it will be helpful to maintain all data of a school. And
admins can show data of their choice at any time.

REFERENCES
● IT Source Code
● W3School
● Existek
● CodeAstro

–Thank You-

27