BCA MINOR PROJECT CERTIFICATE

“ISSUED FROM PROJECT GUIDE”

This is to certify that the Project/Dissertation entitled, Unique Identification

Project is a bonafide work done by Mr. Manish Pratap Singh (Roll No:
1802675011001) in partial fulfillment of the requirement for the award of the
degree of BACHELOR OF COMPUTER APPLICATION from DR. BHIM RAO
AMBEDKAR UNIVERSITY, AGRA and has been carried out under my direct
supervision and guidance. This report or a similar report on the topic has not been
submitted for any other examination and does not form a part of any other
course undergone by the candidate.

____________________

Signature of Guide/Supervisor

Place: __________ Name: ____________________

Date: __________ Designation: ____________________

1|Page
 DECLARATION

I hereby declare that the project titled “Student Information Management

System” submitted for the B.C.A degree of DR. BHIM RAO AMBEDKAR
UNIVERSITY, AGRA.

This is my original work and the project has not formed the basis for the award of
any degree, association ship or fellowship or any similar titles.

Date: ________________ _____________________

Place: ________________ Name: MANISH PRATAP SINGH

B.C.A 5th Semester

Roll No: 1802675011001

Enroll No: A-18250779

2|Page
 ACKNOWLEDGEMENT

This report acknowledges the intense drive and technical competence of all the
individuals who have contributed to its success.

Any work of this nature would not have possible without the support and the
guidance of others around me. Hence, I feel to be my first and foremost duty to
express my deep sense of gratitude and pay my genuine and thanks to Mr. VIKAS
CHANDRA SHARMA (H.O.D - I.T.) and all I.T. faculty for giving me this
opportunity to work on this challenging project.

Whenever a complex and complicated problem confronted me, the spontaneous

guidance of all my team members was ever at hand to solve any difficulty.

Last but not least; I would like to express my thanks to Mr. C P GUPTA (Director,
Dr. MPS Memorial College of Business Studies, Agra) who has been a huge
support thought.

Manish Pratap Singh

B.C.A 5th Semester

Roll No: 1802675011001

Enroll No: A-18250779

3|Page
 TABLE OF CONTENTS

S.No. Description Page No.

1 Project Abstract 5-6
 Project Title
 Project Description

2 Objective 7-8

3 System Requirement Specification (SRS) 9 - 11

 Introduction
 Software and Hardware Requirements
 Design and Implementation Constraints
 Software Development Methodology
4 System Analysis 12 - 13
 Existing System
 Proposed System
5 Design Document 14 - 22
 Introduction
 Data Flow Diagram
 Sequence Diagram
 E-R Diagram
6 Input/output Screens 23 - 34
7 Future Scope 35
8 Conclusion 36

9 Bibliography 37

4|Page
PROJECT ABSTRACT

5|Page
Project Title : STUDENT INFORMATION MANAGEMENT SYSTEM

Students form a main part of any institution that concerns with. But the
institutions find it difficult to keep details of so many students of the organization
just in one stretch. It will involve a lot of pen paper work. Sometimes there will be
some huge heap of files bundled up and kept together in some corner of the
office. If you want any information regarding the particular student then it can be
obtained by just entering the roll number or the name of the student to be
searched. This student management system will make the work of storing the
data in an organized way.

The student management system application will help in managing the student’s
information will become easier with one such system. It will also help in saving
time and effort. The user interface of this system is user friendly and easy to
understand. The information of the particular student will be obtained in just one
mouse click.

6|Page
OBJECTIVES

7|Page
 Enable self-service for students to perform basic administrative functions
and tasks in a “one-stop” service and access environment.

 Support the retention and recruitment of students and encourage a strong

and positive relationship with the university, alumni, donors, and other
constituencies.

 Integrate and support new learning and teaching opportunities and

technologies for students and faculty.

 Support open interfaces and integration with other campus applications

and database systems.

 Ensure data integrity, privacy, and security in an open-access environment.

 Support faculty and staff who perform both basic and complex functions
through simplified work processes and procedures.

 Enable ongoing, flexible reconfiguration of the application to extend its life

cycle and to meet the changing business processes of the university.

 Include implementation and support services that meet institution needs.

8|Page
SYSTEM REQUIREMENT
SPECIFICATION (SRS)

9|Page
 INTRODUCTION
Purpose
Students Management System (also known as a student information system or
SIS) helps a school manage data, communications, and scheduling. A
school system generates and uses a large amount of data. This data must be
communicated appropriately to students, faculty, and parents.

Scope

 Languages
Front-End : Java
Back-End : Oracle Database 11g Express

Project Scope
 This management system is supported by all operating systems.
 This management system is platform independent.
 This management system is designed in such a manner so that every user of
this management system can use very efficiently and easily.

Requirements
 RAM 256 MB or higher
 Hard disk (of minimum storage 100GB)
 Operating System - Windows 7 or any other higher.

10 | P a g e
Software Development Methodology:

 Project Planning, Feasibility Study: Establishes a high-level view of

intended project and determines its goals.
 Systems Analysis, Requirements Definition: Refines project goals into
defined functions and operation of the intended application. Analyzes end-
user information needs.
 System Design: Describes desired features and operations in detail,
including screen layouts, business rules, process diagrams, pseudo code
and other documentation.
 Implementation: The real code is written here.
 Integration and Testing: Brings all the pieces together into a special testing
environment, then checks for errors, bugs interoperability.
 Acceptance, Installation, Deployment: The final stage of initial
development, where the software is put into production and runs actual
business.
 Maintenance: What happens during the rest of the software’s life: changes,
correction, additions, and moves to a different computing platform and
more.

11 | P a g e
SYSTEM ANALYSIS

12 | P a g e
Existing System:

 All operating system are supporting the management system.

 Management System is platform independent.
 The user is mandatory to have a user id and password.
 The management system is multi-user or a one user can use this system at
a time.

Proposed System:

 The graphics of the management system can be improved.

 The management system can be multiuser.
 The management system can be more secured.
 The options can be increased.
 The management system can be comprised of multilevel.

13 | P a g e
SYSTEM DESIGN

14 | P a g e
INTRODUCTION
Software design sits at the technical kernel of the software engineering
process and it’s applied regardless of the development paradigm and is of
application. Design is the first step in the development phase for any engineered
product or system. The designer’s goal is to produce a model or representation of
an entity that will later be built. Beginning, once system requirement have been
specified and analyzed, system design is the first of the three technical activities-
design, code and test that is required to build and verify software.

The importance can be stated with a single word “Quality”. Design is the
place where quality is fostered in software development. Design provides us with
representations of software that can assess for quality. Design is the only way
that we can accurately translate a customer’s view into a finished software
product or system. Software design serves as a foundation for all the software
engineering steps that follow. Without a strong design we risk building an
unstable system- one that will be difficult to test, one whose quality cannot be
assessed until the last stage.

DATA FLOW DIAGRAMS

The development of DFD’s is done in several levels. Each process in lower
level diagrams can be broken down into a more detailed DFD in the next level.
The top-level diagram is often called context diagram. It consists a data flow
diagram is graphical tool used to describe and analyze movement of data through
a system. These are the central tool and the basis from which the other
components are developed. The transformation of data from input to output,
through processes, may be described logically and independently of physical
components associated with the system. These are known as the logical data flow
diagrams. The physical data flow diagram shows the actual implements and
movement of the data between people, departments and workstations. A full
description of a system actually consists of a set of data flow diagrams. Using two
familiar notations Yourdon, Gane and Sarson notation develops the data flow

15 | P a g e
diagrams. Each component in a DFD is labeled with a descriptive name. Process is
further identified with a number that will be used for identification purpose single
process bit, which plays vital role in studying the current system. The process in
the context level diagram is exploded into other process at the first level DFD.

The idea behind the explosion of a process into more process is that
understanding at one level of detail is exploded into greater detail at the next
level. This is done until further explosion is necessary and an adequate amount of
detail is described for analyst to understand the process. Larry Constantine first
developed the DFD as a way of expressing system requirements in a graphical
form, this lead to the modular design.

A DFD is also known as ‘Bubble Chart’ has the purpose of clarifying system
requirements and identifying major transformation that will become programs in
system design. So it is the starting point of the design to the lowest level of detail.
A DFD consists of a series of bubbles joined by data flows in the system.

16 | P a g e
DFD SYMBOLS:
In the DFD, there are four symbols

1. A square defines a source (originator) or destination of system data.

2. An arrow identifies data flow. It is the pipeline through which the
information flows.
3. A circle or a bubble represents a process that transforms incoming data
flow into outgoing data flows.
4. An open rectangle is a data store, data at rest or a temporary repository of
data.

Process that transform data flow

Source or Destination of Data

Data Flow

Data Store

17 | P a g e
CONSTRUCTING A DFD:
Several rules of thumb are used in drawing DFD’s:

1. Process should be named and numbered for an easy reference. Each name
should be representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data
traditionally flow from source to destination although they may flow back
to the source. One way to indicate this is to draw long flow line back to a
source. An alternative way is to repeat the source symbol as a destination.
Since it is used more than once in the DFD it is marked with a short
diagonal.
3. When a process is exploded into lower level details, they are numbered.
4. The names of data stores and destinations are written in capital letters.
Process and dataflow names have the first letter of each work capitalized.

A DFD typically shows the minimum contents of data store. Each data store
should contain all the data elements that flow in and out. Questionnaires should
contain all the data elements that flow in and out. Missing interfaces
redundancies and like is then accounted for often through interviews.

SAILENT FEATURES OF DFD’s

1. The DFD shows flow of data, not of control loops and decisions are
controlled considerations do not appear on a DFD.
2. The DFD does not indicate the time factor involved in any process whether
the dataflow take place daily, weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.

18 | P a g e
DATA FLOW DIAGRAM

 0(Zero) Level DFD

USER

Request for LogIn

Response

SIMS

Check Details

Send Response

Database

19 | P a g e
 1 (One) Level DFD

LogIn failed

LogIn successful LogIn

USER

Response

Request
Request

DATABASE
SIMS
Response

Request
Response

Provide
student
support
services

20 | P a g e
SEQUENCE DIAGRAM:
UML sequence diagrams model the flow of logic within your system in a visual
manner, enabling you both to document and validate your logic, and are
commonly used for both analysis and design purposes. Sequence diagrams are
the most popular UML artifact for dynamic modeling, which focuses on
identifying the behavior within your system.

A sequence diagram is a two dimensional in nature. On the horizontal

access, it shows the life of the object that it represents, while on the vertical axis,
it shows the sequence of the creation or invocation of these objects.

USER USER TERMINAL DATABASE

Login
Confirm User

Register student

Register Successful

View info
Send request
View Student Info

Update Student Info

Update Student Info
Display Updated Successful

Delete Student Info

Send Request for deleting

Deleted successful

21 | P a g e
 ENTITY RELATIONSHIP DIAGRAM:

MOBILE NUMBER LOGIN PASSWORD DATE OF BIRTH

EMAIL ID NAME
USER
1
GENDER
PHOTO

have

SIMS

DATE OF BIRTH

ID

IMAGE FEES DETAILS

NAME

22 | P a g e
INPUT/OUTPUT SCREENS

23 | P a g e
This is the first window when we will run the software.

24 | P a g e
When a new user want to login in the software, he/she have to have an account
for use this software.

When he/she click on the “DON’T HAVE ACCOUNT? CLICK HERE TO CREATE
ONE!!!” this window will open and they will insert their details for create login.

25 | P a g e
Now they will insert their details for new login.

After that when they click “Register”, a popup window open on the screen.

26 | P a g e
As you can see in the bottom photo a popup window is open which is telling us
that “Registration Successful”.

After the successfully registration, we will click on the “CLICK HERE TO LOGIN/
SIGN IN (TO CLOSE REGISTRATION FORM)” and a LOGIN window will open.

27 | P a g e
As you can see when they will insert their credential details a popup window will
also open on that LOGIN window.

And then when they click “OK”, student’s registration form will open for fill
details.

28 | P a g e
On first this window will be clear, so user have to insert details for adding the
students.

When they filled the details of the students a popup window will open that shows
us that “Student inserted into DataBase”.

29 | P a g e
When user want to search the student from many students then it can easily do
by inserting Name in the “Search Student Name:” , when user insert name of
student in that search bar student details will present in below table in the front
of user. As you can see below –

30 | P a g e
When student found in below table, user can update the details of the student as
you can see below in the image –

As you can see user changed his photo and a popup window opened that telling
us “Student Update Successfully”.

31 | P a g e
If user wants to delete student from the database, this can also achieve easily by
clicking the delete button.

First user have to find the student and then he/she will click on the delete button
and as you can see in the below image, data of “Manish” has been deleted. And a
popup opened with “Student Deleted Successfully…” and also you can see in the
below table student Manish is not present. So that means that student deleted.

32 | P a g e
The Database image below –
 For LogIn Window –

33 | P a g e
 For Students Details Window –

34 | P a g e
 Future Scope

 In the future, students can also be able to upload or download notes.

 In future our system can include online accounting system, good backup
and restore facility.
 System is so much flexible so in future it can increase easily and new
modules can be added easily.
 You can add online student admission as well pay online fees.
 The Student Information Management System(SIMS) can be enhanced to
include some other functionality like marks, attendance management.
 Talent management of students based on their performance evaluation can
be added.
 Social networking can also be added wherein students can interact with
each other.
 Online examination module would be introduced to conduct online
examination.
 Further, the faculty can upload the videos of their lectures on this site and
students who had missed those classes can view those videos.

35 | P a g e
 CONCLUSION

 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
school.
 Deployment of our application will certainly help the school to reduce
unnecessary wastage of time in personally going to each department for
some information.
 Awareness and right information about any school is essential for both the
development of student as well as faculty.
 Helpful to perform paperless work and manage all data
 Provides easy, accurate, unambiguous and faster data access.
 This software is very easy to use so all educational institute can use this
frequently.
 It was a wonderful and learning experience for us while working on this
project.

36 | P a g e
 BIBLIOGRAPHY

 www.geeksforgeeks.org
 www.javatpoint.com
 www.oracle.com
 www.stackoverflow.com
 www.w3schools.com

37 | P a g e