1

Chapter 1
Introduction

1.1 Aim
Student Management System is software which is helpful for students as well as the
school authorities. In the current system all the activities are done manually. It is very time
consuming and costly. Our Student Management System deals with the various activities
related to the students.
There are mainly 3 modules in this software
User module
Student Module
Mark management
In the Software we can register as a user and user has of two types, student and
administrator. Administrator has the power to add new user and can edit and delete a user. A
student can register as user and can add edit and delete his profile. The administrator can add
edit and delete marks for the student. All the users can see the marks.

1.2 Purpose
Computerized Student Management System is developed to facilitate the general administration
system to manage the various information of the students and the processes involved in an
university. So, that university can access accurate information quickly and easily as and when
required, thereby improving its operational efficiency & effectiveness.

1.3 Objective and Scope
This is Java Projects on Student Information Management System, which provided a lot of
facility to their user.The objective and scope of my Project Student Information Management
System is to record the details various activities of user. It will simplifies the task and reduce the
paper work. During implementation every user will be given appropriate training to suit their
specific needs. Specific support will also be provided at key points within the academic
calendar. Training will be provided on a timely basis, and you will be trained as the new is
2

Student Information Management System rolled out to your area of responsibility.At the
moment we are in the very early stages, so it is difficult to put a specific time on the training, but
we will keep people informed as plans are developed.The system is very user friendly and it is
anticipated that functions of the system will be easily accessed by administrators, academics,
students and applicants.Hence the management system for the College management has been
designed to remove all the deficiency from which the present system is suffering and to ensure.


















3

Chapter 2
Software Requirement Specification
The term specification means different things to different people. It includes analysis of
data describing the system to determine how well it is performing, what requirements must
be met, and strategies for fulfilling them.
Following activities are important and must be performed correctly.
Analysis of actual data:
(i) The data collected during the fact finding study and included in data flow and
decision analysis documentation are examined to determine how well the
system is performing and whether it will.
(ii) Meet the organizations demand.
Identification of essential requirements:
(i) Features that must be included in the new system, ranging from operational
details to performance criteria, are specified.
Requirement Analysis:
The requirements gathering process is intensified and focused specifically on software.
Software requirements analysis encompasses understanding the information domain for the
software as well as required function, performance, behavior and interfacing. Requirements
for both the system and the software are documented and reviewed with the customer.





4

Design
Software design is a multi-step process that focuses on four distinct attributes of a program:
data structure, software architecture, interface representation, and procedural details. The
design process translates requirements into a representation of the software that can be
assessed for quality before code generation begins. The design is documented and becomes
part of the software configuration.

Code Generation
The design is translated into a machine readable form. If design is performed in a detailed
manner, code generation can be accomplished mechanistically.

Testing
The testing process focuses on the logical internals of the software, assuring that all
statements have been tested, and on the functional externals i.e. conducting tests to uncover
errors and ensure that defined input will produce actual results that agree with required
results.

Maintenance
Software maintenance applies to following phases in the existing program:

Change in software due to errors.

Change in software because the software must be adapted to accommodate changes in its
environment.

Change in software when the customer requires functional or performance enhancements.





5

Cost
It is desirable to aim for a system with a minimum cost subject to the condition that it must
satisfy all the requirements.
2.1 Hardware and Software Requirements

Hardware Specification:-

Processor: Dual Core or higher
RAM: 256GB or higher
HDD: 20GB Hard Disk (For Best Performance) or higher

Software Specification:-

Operating System: Windows XP, Windows 7
Database specification: MS Access

2.2 Constraints
Constraints of the project include certain requirements and concerns needed for the project.

2.2.1 Regulatory Policies
We have decided regularities policies asperrequirement of our project development. We have
done project work from Monday to Saturday and 2 hours per day. We have prepared project
plan and we maintained the plan throughout the project. Every day we had a discussion with
our project guide and every alternative Sunday we had a reporting of the project work.
2.2.2 Hardware Limitations
There are no major hardware limitations but minimum 128 MB RAM and 20 GB Hard Disk
are required.

6

2.2.3 Interfaces to Other Applications
In our Project there is no need to have any sort of interface with other applications
2.2.4 Parallel Operations
We can run more than One Application or instances of our system by putting the currently
not running instances in the system tray.
2.2.5 Reliability Requirements
The system is almost reliable and ensures that correct output is being delivered to the user.
2.2.6 Safety and Security Consideration
In the system there are login and password facility for security of database. We also take
Backup of our project and databases regularly.
2.2.7 Introduction to Database:
A database is a collection of interrelated data. The collection of data must be logically coherent
with some inherent meaning. A database is designed and built for a specific purpose, keeping in
mind the needs of the applications that are going to use it and end users of those applications. It
is managed by a software package known a database management system (DBMS).
A DBMS is a software system that enables users to record and maintain database. It provides an
environment where in data can be stored and retrieved from database easily and must efficiently.
The data can be any thing that is deemed to be of significant to the organization, the system is
serving.

2.3 What is java?
A high-level programming language developed by Sun Microsystems. Java was
originally called OAK, and was designed for handheld devices and set-top boxes. Oak was
unsuccessful so in 1995 Sun changed the name to Java and modified the language to take
advantage of the burgeoning World Wide Web.
7

Java is an object-oriented language similar to C++, but simplified to eliminate language features
that cause common programming errors. Java source code files (files with a .java extension)
are compiled into a format calledbytecode (files with a .class extension), which can then be
executed by a Javainterpreter. Compiled Java code can run on most computers because Java
interpreters and runtime environments, known as Java Virtual Machines (VMs), exist for
most operating systems, including UNIX, the Macintosh OS, and Windows. Bytecode can also
be converted directly into machine languageinstructions by a just-in-time compiler (JIT).
Java is a general purpose programming language with a number of features that make the
language well suited for use on the World Wide Web. Small Java applications are called
Java applets and can be downloaded from a Web server and run on your computer by a Java-
compatible Web browser, such asNetscape Navigator or Microsoft Internet Explorer.

2.3.1 MS access:
In recent years, Database Management System (DBMS) have established themselves as primary
means of data storage for information system ranging from large commercial transaction to PC
desktop application. At the heart of todays most of the information system is Relational
Database System (RDBMS).
Have been the workhouse for data management operation for over a decade and continue to
evolve and mature, providing sophisticated storage, retrieval and distribution function to
enterprise wide data processing and management system compared to the file system, RDBMS
provides organization with capability to easily integrate and leverage the massive amount of
operational data into meaningful data.
The evolution of high-powered database engine such as MS access has faster the development of
advance enabling technology including client/server ,data warehousing and online processing ,all
of which comprise the core todays state of art information system. A database is an organized
collection of related information. Any meaningful data is called information. A database
management system is a collection of interrelated data a set of programs to access that data
The MS access architecture in this section is generic architecture that applies all platforms on
which ACCESS run. These may be different platform, but the fundamentals are same.
8

Physically in its simplest form, an access database is nothing more than a set of files on the disk.
The physical relation of these files is irrelevant to the function of the database. Logically the
database is divided into a set of user account, each of which is identified by username and
password unique to the database. Tables and objects are owned one by one of these. MS access
maintains its own list of authorized user and their associated privileged, manages memory cache
paging; control locking for concurrent resource usage; dispatch and schedules users request ;
manages space usage within its table space structure.
2.3.2 Memory:
MS access uses the memory of the system to turn the user process and to cache data objects.
There are major areas used by MS access : memory that is shared by all process against the data
and the database memory that is local to each individual user process.
2.3.3 System Memory :
MS access database wide system memory is known as the SGA (System Global ACCESS Area).
The data and control structures in SGA are sharable and all ACCESS Server background process
uses them.













9

Chapter 3
System Analysis & Design

Requirements analysis is a software engineering task that bridges the gap between system level
requirements engineering and software design. Requirements engineering activities result in the
specification of softwares operational characteristics (function, data and behavior), indicate
softwares interface with other system elements, and establish constraints that software must
meet. The most commonly used requirements technique is to conduct a meeting or interview.
The first meeting between a software engineer (the analyst) and the customer can be likened to
the awkwardness of a first date between two adolescents. Neither person knows what to say or
ask; both are worried that they do say will be misinterpreted; both are thinking about where it
might lead (both likely have radically different expectations here); both want to get the thing
over with, but at the same time, both want it to be a success.
Gause and Weinberg suggest that the analyst start by asking CONTEXT-FREE QUESTIONS.
That is, a set of questions that will lead to a basic understanding of the problem, the people who
want a solution, the nature of the solution that is desired, and the effectiveness of the first
encounter itself.
The goal of the requirements gathering activity is to collect all relevant information from the
customer regarding the product to be developed with a view to clearly understanding the
customer requirements and weeding out the incompleteness and inconsistencies in these
requirements. The requirements analysis activity is begun by collecting all relevant data
regarding the product to be developed from the users of the product and from the customer
through interviews and discussions. Data collection is done by taking the copies of the
documents involved in its working from the organization.

3.1 Project Development Approach and Justification
The Requirements provided by the users are converted into Users Requirement Specification
as described above. The URS documents are then revised, validated, authorized and
approved by the users. The development commences after the approval phase i.e. after the
10

signing off of the URS documents. Thus, the URS is concerned to be the most important
document from user and developer prospective. The Developer will try to adhere to the
requirements specified in the URS documents in order to develop the required application.
We have used Waterfall model as a development model.

Fig3.1: Waterfall Model
3.2 The Waterfall Model
As the process model for our project we use Waterfall model .The definition of business
requirements, design, build and test are undertaken in a linear fashion. Provided the desired
project outcomes can be clearly defined from the outset, this approach is swift and effective.
Difficulties arise when unforeseen risks are encountered in later stages, requiring an
unwinding of the process and the generation of significant project rework.
The waterfall model is well understood and time tested but generally considered to be less
useful than it once was due to the increasing complexity of systems. It works well for
automating the tasks of clerks and accountants, less well for knowledge works such as
experts trying to solve problems (Information Center Quarterly article, Larry Runge).
11

Another problem is that in the waterfall model users only input is in specifying requirements
and that all requirements must be specified at one point before production begins. However,
requirements typically change through the process and require more feedback.
We use waterfall model because:
It is easy for managers to understand, plan by and to test progress against as it has very
clear sequential milestones.
It encourages good design practices such as early clarification of system goals, which in
turn save time and money (the earlier a bug is caught, the less harm it can cause)
Due to lots of up front design planning, should the project be stopped and taken up at a
later date, or should project members change, implementation can continue far easier
than with more agile development models where there is considerably less design
documentation.
It is compatible with a wide range of design strategies
In sense of 10% customization in this model, users may change requirements often, at
stages beyond the requirements stage.
In sense of testing, constant verification of each stage is required to ensure that the next
phase can start on a correct base Technology may change during development.

3.3 Project Plan
Areas, which would be considered during the planning and analysis, would be:
Ensure that the information flow is process driven.
Reduce the manual efforts to the maximum extent for all activities.
Ensure validation at each and every level.
Act as an effective tool in decision support.
Provide user friendly system.
12


Fig. 3.2 Project Planning and Management Approach


3.3.1 DATA FLOW DIAGRAM
The DFD also known as the Bubble Chart is a simple graphical formalism that can be used to
represent a system in terms of the input data to the system. Various processing carried out on
these data, and the output data generated by the system. The main reason why the DFD technique
is so popular is probably because of the fact that DFD is a very simple formalism-it is simple to
understand and use. A DFD uses a very limited number of primitive symbols to represent the
functions performed by a system and the data flow among these functions. Starting with a set of
high-level functions that a system performs, a DFD model hierarchically represents various sub
functions. The five different types of primitive symbols used for constructing DFDs are:

SYMBOLS USED:

PROCESS:






A function is represented using a circle. This symbol is called a process or a bubble. Bubbles are
annotated with the names of the corresponding functions.


13




EXTERNAL ENTITY:




An external entity such as a librarian, a library member, etc. is represented by a rectangle. The
external entities are essentially those physical entities external to the software system that
interact with the system by inputting data to the system or by consuming the data produced by
the system. In addition to the human users, the external entity symbols can be used to represent
external hardware and software such as application software.


DATA FLOW:

A directed arc or an arrow is used as a data flow symbol. A data flow symbol represents the data
flow occurring between two processes, or between an external entity and a process, in the
direction of the data flow arrow. Data flow symbols are usually annotated with the corresponding
data names.

DATA STORE:


A data store represents a logical file. It is represented using two parallel lines. A logical file can
represent either a data store symbol, which can represent either a data structure, or a physical file
on disk. Each data store is connected to a process by means of a data flow symbol. The direction
14

of the data flow arrow shows whether data is being read from or written into a data store. A
arrow flowing in or out of a data store implicitly represents the entire data of the data store and
hence connecting to a data store need not be annotated with the name of the corresponding data
items.



OUTPUT SYMBOL:



The output symbol is used when a hard copy is produced and the user of the copies
cannot be clearly specified or there are several users of the output.

LEVEL-0 DATAFLOW DIAGRAM:
Fig.3.3 LEVEL-0 DFD


LEVAL-1 DATAFLOW DIAGRAM:
15



Fig.3.4 LEVEL-1 DFD















16

LEVAL-2 DATAFLOW DIAGRAM:





Fig.3.6 LEVEL 2 DATA FLOW DIAGRAM

17



3.3.2 Use Case Diagrams:

Fig.3.7.USE CASE DIAGRAM



18

Chapter 4
Data Dictionary

4.1 ER-Diagram




ADMINISTRATER
Admin Name Password Admin
ADDS
ENTER
Student Course
HANDLS
COURSE_ID
Course
name
Qualification
Experiance
Roll no.
Student
Name
Address
Contect
no.
DEPARTMENT
ENROLLS
CONDUCT
Dept_id
Department
HAS
MAINTAINS
Exam
Roll no.
Course
Student
name
Marks
SECTION
Section_ID Name
ATTENDANCE
Roll no.
Student
name
Course
percentage
19

Chapter 5
Snapshots




20




21










22







23






24








25










26








27





28






29






30

Chapter 6
Conclusion & Scope for future work

CONCLUSION:
The project has been of great help in more ways than one.It helped us gain valuable insight into
the principles of GUI designing and user interface handling.The Student Management has been
designed in such a manner that it will fulfill all the requisite information. The advantage is that
non-technical user can operate it. The user manual is also produced in this project for ready
information. The Student Management System is capable of handling all the information about
branch and course management. Also, in order to generate final reports an additional report
generating applications using data reports was added. Though the system still contains lot of
scope of improvement in it. But its overall looks rough picture of on existing automation
system.The system has been developed with much care that it is free of errors and at the same time it is
efficient and less time consuming. The important thing is that the system is robust. Avoid malfunction
from outsiders .It goes through all phases of software development cycle. So product is accurate. Also
provision is provided for future developments in the system.

Future Scope:
We can make future changes to the project, so that it will not obsolete, as the future requirement.
We can make changes in project according to users future requirement.
1. Network
2. Database Security
3. User Rights
4. Can include a comprehensive query generation capable of performing ad-hoc queries.
5. Additional reports listing flights costs and passenger categories could have been added



31



Chapter 7
Bibliography

Bibliography:
The Language JAVA
Introduction to JAVA
Practical JAVA programming
JAVA Documentation
References:
www.google.com
www.w3schools.com
www.wikipedia.com