1

INDUSTRIAL TRAINING REPORT

ON
STUDENT MANAGEMENT SYSTEM USING JAVA

Submitted by
Neelendra Dhar
B.Voc (SD & e-G)
Student id: 718629

Department of IT & Software

Deen Dayal Upadhyay Kaushal Kendra
National P. G. College Lucknow
2

CERTIFICATE

This is to certify that the project report entitled “Student Management System
Using Java ” is the bonafide work of Neelendra Dhar , Student Id. – 718629
BACHELOR OF VOCATION (SD&EG) from National P.G. College Lucknow

Place: Lucknow
Date: (Guide Name)
3

DECLARATION BY THE STUDENT

I Neelendra Dhar , hereby declare this Industrial Training Report entitled

“Student Management System Using Java”. In portfolio management submitted
in the partial fulfilment of the requirements for The Degree in Bachelor of
Vocation (SD&EG of National P.G. College Lucknow.

Date: Candidate Signature:

Place: (Neelendra Dhar )
4

ACKNOWLEDGEMENT

I acknowledge the sincere assistance provided to me from several rather

unexpected quarters during the course of execution of this study. It would be a
mammoth task to place on record my gratitude to each and every one of them
but a whole hearted attempt would be made nevertheless, least I be branded
ungrateful.

Neelendra Dhar
B.Voc (SD & e-G)
Student id:
718629
5

TABLE OF CONTENTS
1. INTRODUCTION

2. SYSTEM ANALYSIS

3. FEASIBILITY ANALYSIS

4. HARDWARE CONFIGURATION

5. SOFTWARE CONFIGURATION

6. SYSTEM REQUIREMENTS

7. DATA FLOW DIAGRAM

8. SOFTWARE INTERFACE

9. SYSTEM DESIGN

10.TABLES USED

11.SYSTEM IMPLEMENTATION

12.SOFTWARE TESTING

13.CONCLUSION

14.BIBLIOGRAPHY
6

INTRODUCTION
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.
7

SYSTEM ANALYSIS
EXISTING SYSTEM:

System Analysis is a detailed study of the various operations performed

by a system and their relationships within and outside of the system. Here the
key question is- what all problems exist in the present system? What must be
done to solve the problem? Analysis begins when a user or manager begins a
study of the program using existing system.

During analysis, data collected on the various files, decision points and
transactions handled by the present system. The commonly used tools in the
system are Data Flow Diagram, interviews, etc. Training, experience and
common sense are required for collection of relevant information needed to
develop the system. The success of the system depends largely on how clearly
the problem is defined, thoroughly investigated and properly carried out through
the choice of solution. A good analysis model should provide not only the
mechanisms of problem understanding but also the frame work of the solution.
Thus it should be studied thoroughly by collecting data about the system. Then
the proposed system should be analyzed thoroughly in accordance with the
needs.

System analysis can be categorized into four parts.

 System planning and initial investigation

 Information Gathering
 Applying analysis tools for structured analysis
 Feasibility study
 Cost/ Benefit analysis.
8

In the current system we need to keep a number of records related to the

student and want to enter the details of the student and the marks manually. In
this system only the teacher or the school authority views the mark of the
student and they want to enter the details of the student. This is time consuming
and has much cost.

PROPOSED SYSTEM

In our proposed system we have the provision for adding the details
of the students by themselves. So the overhead of the school authorities and the
teachers is become less. Another advantage of the system is that it is very easy
to edit the details of the student and delete a student when it found unnecessary.
The marks of the student are added in the database and so students can also
view the marks whenever they want.

Our proposed system has several advantages

 User friendly interface

 Fast access to database
 Less error
 More Storage Capacity
 Search facility
 Look and Feel Environment
 Quick transaction

All the manual difficulties in managing the student details in a school

or college have been rectified by implementing computerization.
9

FEASIBILITY ANALYSIS
Whatever we think need not be feasible .It is wise to think about the
feasibility of any problem we undertake. Feasibility is the study of impact,
which happens in the organization by the development of a system. The impact
can be either positive or negative. When the positives nominate the negatives,
then the system is considered feasible. Here the feasibility study can be
performed in two ways such as technical feasibility and Economical Feasibility.

Technical Feasibility:

We can strongly says 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 is available in the
organization here we are utilizing the resources which are available already.

Economical Feasibility

Development of this application is highly economically feasible .The

organization needed not spend much money for the development of t he system
already available. The only thing is to be done is making an environment for the
development with an effective supervision. I f 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 t he
organization .There fore , the system is economically feasible.
10

HARDWARE CONFIGURATION

Processor : Pentium III 630MHz

RAM : 128 MB

Hard Disk : 20GB

Monitor : 15” Color monitor

Key Board : 122 Keys

11

SOFTWARE CONFIGURATION

Operating System : Windows NT,

Windows 98,

Windows XP.

Language : Java 2 Runtime

Environment

Database : MS Access2007.
12

SYSTEM REQUIREMENTS

This management system can be used in windows 98, Windows2000,

Windows XP and Windows NT, supported for other platform such as Applet,
Macintosh and UNIX.

The system must be running Windows 98, Windows 98 or Windows NT4.0

operating system and must meet the following hardware requirements.

 For Windows 95 based computers , a 486 / 66 MHz or

higher processor with 8MB
 For Windows 98 based computers , a 500/88MHz or
higher processor with 32 Mb of RAM
 For Windows NT based computers , a 488 / 66 MHz
or higher processor with 16 MB of RAM
 For Windows 200 based computers , a 700/850 MHz
or higher processor with 512 MB of Ram
13

DATA FLOW DIAGRAM

Context Diagram
14
15

SOFTWARE INTERFACE
Login

Add New User

16

Edit User Type

Delete User
17

Student Registration
18

Edit Student Details

19

Delete Student details

20

Add/Edit Mark Details

21

View Marks
22

View User details

23

View Student Details

24

Add New Subjects

25

Edit Subject details

26

Delete Subject details

27

Subject Allocation
28

CODING

Main
<?xml version="1.0" encoding="UTF-8"?>

<project xmlns="http://www.netbeans.org/ns/project/1">

<type>org.netbeans.modules.java.j2seproject</type>

<configuration>

<data xmlns="http://www.netbeans.org/ns/j2se-project/3">

<name>StudentManagementSystem</name>

<minimum-ant-version>1.6.5</minimum-ant-version>

<source-roots>

<root id="src.dir"/>

</source-roots>

<test-roots>

<root id="test.src.dir"/>

</test-roots>

</data>

</configuration>

</project>
29

Code 2
build.classes.dir=${build.dir}/classes

build.classes.excludes=**/*.java,**/*.form

# This directory is removed when the project is cleaned:

build.dir=build

build.generated.dir=${build.dir}/generated

# Only compile against the classpath explicitly listed here:

build.sysclasspath=ignore

build.test.classes.dir=${build.dir}/test/classes

build.test.results.dir=${build.dir}/test/results

debug.classpath=\

${run.classpath}

debug.test.classpath=\

${run.test.classpath}

# This directory is removed when the project is cleaned:

dist.dir=dist

dist.jar=${dist.dir}/StudentManagementSystem.jar

dist.javadoc.dir=${dist.dir}/javadoc

excludes=

includes=**
30

jar.compress=false

javac.classpath=

# Space-separated list of extra javac options

javac.compilerargs=

javac.deprecation=false

javac.source=1.5

javac.target=1.5

javac.test.classpath=\

${javac.classpath}:\

${build.classes.dir}:\

${libs.junit.classpath}:\

${libs.junit_4.classpath}

javadoc.additionalparam=

javadoc.author=false

javadoc.encoding=${source.encoding}

javadoc.noindex=false

javadoc.nonavbar=false

javadoc.notree=false

javadoc.private=false

javadoc.splitindex=true
31

javadoc.use=true

javadoc.version=false

javadoc.windowtitle=

main.class=Login

manifest.file=manifest.mf

meta.inf.dir=${src.dir}/META-INF

platform.active=default_platform

run.classpath=\

${javac.classpath}:\

${build.classes.dir}

# Space-separated list of JVM arguments used when running the project

# (you may also define separate properties like run-sys-prop.name=value

instead of -Dname=value

# or test-sys-prop.name=value to set system properties for unit tests):

run.jvmargs=

run.test.classpath=\

${javac.test.classpath}:\

${build.test.classes.dir}

source.encoding=UTF-8

src.dir=src

test.src.dir=test
32

Code 3

<?xml version="1.0" encoding="UTF-8"?>

<!--

*** GENERATED FROM project.xml - DO NOT EDIT ***

*** EDIT ../build.xml INSTEAD ***

For the purpose of easier reading the script

is divided into following sections:

- initialization

- compilation

- jar

- execution

- debugging

- javadoc

- junit compilation

- junit execution

- junit debugging

- applet

- cleanup
33

-->

<project xmlns:j2seproject1="http://www.netbeans.org/ns/j2se-project/1"
xmlns:j2seproject3="http://www.netbeans.org/ns/j2se-project/3"
xmlns:jaxrpc="http://www.netbeans.org/ns/j2se-project/jax-rpc" basedir=".."
default="default" name="StudentManagementSystem-impl">

<target depends="test,jar,javadoc" description="Build and test whole

project." name="default"/>

<!--

======================

INITIALIZATION SECTION

======================

-->

<target name="-pre-init">

<!-- Empty placeholder for easier customization. -->

<!-- You can override this target in the ../build.xml file. -->

</target>

<target depends="-pre-init" name="-init-private">

<property file="nbproject/private/config.properties"/>

<property file="nbproject/private/configs/${config}.properties"/>

<property file="nbproject/private/private.properties"/>

</target>
34

<target depends="-pre-init,-init-private" name="-init-user">

<property file="${user.properties.file}"/>

<!-- The two properties below are usually overridden -->

<!-- by the active platform. Just a fallback. -->

<property name="default.javac.source" value="1.4"/>

<property name="default.javac.target" value="1.4"/>

</target>

<target depends="-pre-init,-init-private,-init-user" name="-init-project">

<property file="nbproject/configs/${config}.properties"/>

<property file="nbproject/project.properties"/>

</target>

<target depends="-pre-init,-init-private,-init-user,-init-project,-init-macrodef-
property" name="-do-init">

<available file="${manifest.file}" property="manifest.available"/>

<condition property="manifest.available+main.class">

<and>

<isset property="manifest.available"/>

<isset property="main.class"/>

<not>

<equals arg1="${main.class}" arg2="" trim="true"/>

</not>
35

</and>

</condition>

<condition property="manifest.available+main.class+mkdist.available">

<and>

<istrue value="${manifest.available+main.class}"/>

<isset property="libs.CopyLibs.classpath"/>

</and>

</condition>

<condition property="have.tests">

<or>

<available file="${test.src.dir}"/>

</or>

</condition>

<condition property="have.sources">

<or>

<available file="${src.dir}"/>

</or>

</condition>

<condition property="netbeans.home+have.tests">

<and>
36

<isset property="netbeans.home"/>

<isset property="have.tests"/>

</and>

</condition>

<condition property="no.javadoc.preview">

<and>

<isset property="javadoc.preview"/>

<isfalse value="${javadoc.preview}"/>

</and>

</condition>

<property name="run.jvmargs" value=""/>

<property name="javac.compilerargs" value=""/>

<property name="work.dir" value="${basedir}"/>

<condition property="no.deps">

<and>

<istrue value="${no.dependencies}"/>

</and>

</condition>

<property name="javac.debug" value="true"/>

<property name="javadoc.preview" value="true"/>

37

<property name="application.args" value=""/>

<property name="source.encoding" value="${file.encoding}"/>

<condition property="javadoc.encoding.used" value="$

{javadoc.encoding}">

<and>

<isset property="javadoc.encoding"/>

<not>

<equals arg1="${javadoc.encoding}" arg2=""/>

</not>

</and>

</condition>

<property name="javadoc.encoding.used" value="${source.encoding}"/>

<property name="includes" value="**"/>

<property name="excludes" value=""/>

<property name="do.depend" value="false"/>

<condition property="do.depend.true">

<istrue value="${do.depend}"/>

</condition>

<condition else="" property="javac.compilerargs.jaxws" value="-

Djava.endorsed.dirs='${jaxws.endorsed.dir}'">

<and>
38

<isset property="jaxws.endorsed.dir"/>

<available file="nbproject/jaxws-build.xml"/>

</and>

</condition>

</target>

<target name="-post-init">

<!-- Empty placeholder for easier customization. -->

<!-- You can override this target in the ../build.xml file. -->

</target>

<target depends="-pre-init,-init-private,-init-user,-init-project,-do-init"
name="-init-check">

<fail unless="src.dir">Must set src.dir</fail>

<fail unless="test.src.dir">Must set test.src.dir</fail>

<fail unless="build.dir">Must set build.dir</fail>

<fail unless="dist.dir">Must set dist.dir</fail>

<fail unless="build.classes.dir">Must set build.classes.dir</fail>

<fail unless="dist.javadoc.dir">Must set dist.javadoc.dir</fail>

<fail unless="build.test.classes.dir">Must set build.test.classes.dir</fail>

<fail unless="build.test.results.dir">Must set build.test.results.dir</fail>

<fail unless="build.classes.excludes">Must set

build.classes.excludes</fail>
39

<fail unless="dist.jar">Must set dist.jar</fail>

</target>

<target name="-init-macrodef-property">

<macrodef name="property" uri="http://www.netbeans.org/ns/j2se-

project/1">

<attribute name="name"/>

<attribute name="value"/>

<sequential>

<property name="@{name}" value="${@{value}}"/>

</sequential>

</macrodef>

</target>

<target name="-init-macrodef-javac">

<macrodef name="javac" uri="http://www.netbeans.org/ns/j2se-

project/3">

<attribute default="${src.dir}" name="srcdir"/>

<attribute default="${build.classes.dir}" name="destdir"/>

<attribute default="${javac.classpath}" name="classpath"/>

<attribute default="${includes}" name="includes"/>

<attribute default="${excludes}" name="excludes"/>

<attribute default="${javac.debug}" name="debug"/>

40

<attribute default="/does/not/exist" name="sourcepath"/>

<element name="customize" optional="true"/>

<sequential>

<javac debug="@{debug}" deprecation="${javac.deprecation}"

destdir="@{destdir}" encoding="${source.encoding}"
excludes="@{excludes}" includeantruntime="false" includes="@{includes}"
source="${javac.source}" sourcepath="@{sourcepath}" srcdir="@{srcdir}"
target="${javac.target}">

<classpath>

<path path="@{classpath}"/>

</classpath>

<compilerarg line="${javac.compilerargs} $
{javac.compilerargs.jaxws}"/>

<customize/>

</javac>

</sequential>

</macrodef>

<macrodef name="depend" uri="http://www.netbeans.org/ns/j2se-

project/3">

<attribute default="${src.dir}" name="srcdir"/>

<attribute default="${build.classes.dir}" name="destdir"/>

<attribute default="${javac.classpath}" name="classpath"/>

41

<sequential>

<depend cache="${build.dir}/depcache" destdir="@{destdir}"

excludes="${excludes}" includes="${includes}" srcdir="@{srcdir}">

<classpath>

<path path="@{classpath}"/>

</classpath>

</depend>

</sequential>

</macrodef>

<macrodef name="force-recompile" uri="http://www.netbeans.org/ns/j2se-

project/3">

<attribute default="${build.classes.dir}" name="destdir"/>

<sequential>

<fail unless="javac.includes">Must set javac.includes</fail>

<pathconvert pathsep="," property="javac.includes.binary">

<path>

<filelist dir="@{destdir}" files="${javac.includes}"/>

</path>

<globmapper from="*.java" to="*.class"/>

</pathconvert>

<delete>
42

<files includes="${javac.includes.binary}"/>

</delete>

</sequential>

</macrodef>

</target>

<target name="-init-macrodef-junit">

<macrodef name="junit" uri="http://www.netbeans.org/ns/j2se-project/3">

<attribute default="${includes}" name="includes"/>

<attribute default="${excludes}" name="excludes"/>

<attribute default="**" name="testincludes"/>

<sequential>

<junit dir="${work.dir}" errorproperty="tests.failed"

failureproperty="tests.failed" fork="true" showoutput="true">

<batchtest todir="${build.test.results.dir}">

<fileset dir="${test.src.dir}" excludes="@{excludes},$

{excludes}" includes="@{includes}">

<filename name="@{testincludes}"/>

</fileset>

</batchtest>

<classpath>

<path path="${run.test.classpath}"/>
43

</classpath>

<syspropertyset>

<propertyref prefix="test-sys-prop."/>

<mapper from="test-sys-prop.*" to="*" type="glob"/>

</syspropertyset>

<formatter type="brief" usefile="false"/>

<formatter type="xml"/>

<jvmarg line="${run.jvmargs}"/>

</junit>

</sequential>

</macrodef>

</target>

<target depends="-init-debug-args" name="-init-macrodef-nbjpda">

<macrodef name="nbjpdastart" uri="http://www.netbeans.org/ns/j2se-

project/1">

<attribute default="${main.class}" name="name"/>

<attribute default="${debug.classpath}" name="classpath"/>

<attribute default="" name="stopclassname"/>

<sequential>

<nbjpdastart addressproperty="jpda.address" name="@{name}"

stopclassname="@{stopclassname}" transport="${debug-transport}">
44

<classpath>

<path path="@{classpath}"/>

</classpath>

</nbjpdastart>

</sequential>

</macrodef>

<macrodef name="nbjpdareload" uri="http://www.netbeans.org/ns/j2se-

project/1">

<attribute default="${build.classes.dir}" name="dir"/>

<sequential>

<nbjpdareload>

<fileset dir="@{dir}" includes="${fix.classes}">

<include name="${fix.includes}*.class"/>

</fileset>

</nbjpdareload>

</sequential>

</macrodef>

</target>

<target name="-init-debug-args">

<property name="version-output" value="java version &quot;$

{ant.java.version}"/>
45

<condition property="have-jdk-older-than-1.4">

<or>

<contains string="${version-output}" substring="java version

&quot;1.0"/>

<contains string="${version-output}" substring="java version

&quot;1.1"/>

<contains string="${version-output}" substring="java version

&quot;1.2"/>

<contains string="${version-output}" substring="java version

&quot;1.3"/>

</or>

</condition>

<condition else="-Xdebug" property="debug-args-line" value="-Xdebug

-Xnoagent -Djava.compiler=none">

<istrue value="${have-jdk-older-than-1.4}"/>

</condition>

<condition else="dt_socket" property="debug-transport-by-os"

value="dt_shmem">

<os family="windows"/>

</condition>

<condition else="${debug-transport-by-os}" property="debug-transport"

value="${debug.transport}">

<isset property="debug.transport"/>
46

</condition>

</target>

<target depends="-init-debug-args" name="-init-macrodef-debug">

<macrodef name="debug" uri="http://www.netbeans.org/ns/j2se-

project/3">

<attribute default="${main.class}" name="classname"/>

<attribute default="${debug.classpath}" name="classpath"/>

<element name="customize" optional="true"/>

<sequential>

<java classname="@{classname}" dir="${work.dir}" fork="true">

<jvmarg line="${debug-args-line}"/>

<jvmarg value="-Xrunjdwp:transport=${debug-
transport},address=${jpda.address}"/>

<jvmarg line="${run.jvmargs}"/>

<classpath>

<path path="@{classpath}"/>

</classpath>

<syspropertyset>

<propertyref prefix="run-sys-prop."/>

<mapper from="run-sys-prop.*" to="*" type="glob"/>

</syspropertyset>
47

<customize/>

</java>

</sequential>

</macrodef>

</target>

<target name="-init-macrodef-java">

<macrodef name="java" uri="http://www.netbeans.org/ns/j2se-project/1">

<attribute default="${main.class}" name="classname"/>

<element name="customize" optional="true"/>

<sequential>

<java classname="@{classname}" dir="${work.dir}" fork="true">

<jvmarg line="${run.jvmargs}"/>

<classpath>

<path path="${run.classpath}"/>

</classpath>

<syspropertyset>

<propertyref prefix="run-sys-prop."/>

<mapper from="run-sys-prop.*" to="*" type="glob"/>

</syspropertyset>

<customize/>
48

</java>

</sequential>

</macrodef>

</target>

<target name="-init-presetdef-jar">

<presetdef name="jar" uri="http://www.netbeans.org/ns/j2se-project/1">

<jar compress="${jar.compress}" jarfile="${dist.jar}">

<j2seproject1:fileset dir="${build.classes.dir}"/>

</jar>

</presetdef>

</target>

<target depends="-pre-init,-init-private,-init-user,-init-project,-do-init,-post-
init,-init-check,-init-macrodef-property,-init-macrodef-javac,-init-macrodef-
junit,-init-macrodef-nbjpda,-init-macrodef-debug,-init-macrodef-java,-init-
presetdef-jar" name="init"/>

<!--

===================

COMPILATION SECTION

===================

-->

<target depends="init" name="deps-jar" unless="no.deps"/>

49

<target depends="init,-check-automatic-build,-clean-after-automatic-build"
name="-verify-automatic-build"/>

<target depends="init" name="-check-automatic-build">

<available file="${build.classes.dir}/.netbeans_automatic_build"
property="netbeans.automatic.build"/>

</target>

<target depends="init" if="netbeans.automatic.build" name="-clean-after-

automatic-build">

<antcall target="clean"/>

</target>

<target depends="init,deps-jar" name="-pre-pre-compile">

<mkdir dir="${build.classes.dir}"/>

</target>

<target name="-pre-compile">

<!-- Empty placeholder for easier customization. -->

<!-- You can override this target in the ../build.xml file. -->

</target>

<target if="do.depend.true" name="-compile-depend">

<j2seproject3:depend/>

</target>

<target depends="init,deps-jar,-pre-pre-compile,-pre-compile,-compile-
depend" if="have.sources" name="-do-compile">
50

<j2seproject3:javac/>

<copy todir="${build.classes.dir}">

<fileset dir="${src.dir}" excludes="${build.classes.excludes},$

{excludes}" includes="${includes}"/>

</copy>

</target>

<target name="-post-compile">

<!-- Empty placeholder for easier customization. -->

<!-- You can override this target in the ../build.xml file. -->

</target>

<target depends="init,deps-jar,-verify-automatic-build,-pre-pre-compile,-pre-
compile,-do-compile,-post-compile" description="Compile project."
name="compile"/>

<target name="-pre-compile-single">

<!-- Empty placeholder for easier customization. -->

<!-- You can override this target in the ../build.xml file. -->

</target>

<target depends="init,deps-jar,-pre-pre-compile" name="-do-compile-

single">

<fail unless="javac.includes">Must select some files in the IDE or set

javac.includes</fail>

<j2seproject3:force-recompile/>
51

<j2seproject3:javac excludes="" includes="${javac.includes}"

sourcepath="${src.dir}"/>

</target>

<target name="-post-compile-single">

<!-- Empty placeholder for easier customization. -->

<!-- You can override this target in the ../build.xml file. -->

</target>

<target depends="init,deps-jar,-verify-automatic-build,-pre-pre-compile,-pre-
compile-single,-do-compile-single,-post-compile-single" name="compile-
single"/>

<!--

====================

JAR BUILDING SECTION

====================

-->

<target depends="init" name="-pre-pre-jar">

<dirname file="${dist.jar}" property="dist.jar.dir"/>

<mkdir dir="${dist.jar.dir}"/>

</target>

<target name="-pre-jar">

<!-- Empty placeholder for easier customization. -->

52

<!-- You can override this target in the ../build.xml file. -->

</target>

<target depends="init,compile,-pre-pre-jar,-pre-jar" name="-do-jar-without-

manifest" unless="manifest.available">

<j2seproject1:jar/>

</target>

<target depends="init,compile,-pre-pre-jar,-pre-jar" if="manifest.available"

name="-do-jar-with-manifest" unless="manifest.available+main.class">

<j2seproject1:jar manifest="${manifest.file}"/>

</target>

<target depends="init,compile,-pre-pre-jar,-pre-jar"
if="manifest.available+main.class" name="-do-jar-with-mainclass"
unless="manifest.available+main.class+mkdist.available">

<j2seproject1:jar manifest="${manifest.file}">

<j2seproject1:manifest>

<j2seproject1:attribute name="Main-Class" value="${main.class}"/>

</j2seproject1:manifest>

</j2seproject1:jar>

<echo>To run this application from the command line without Ant,
try:</echo>

<property location="${build.classes.dir}"
name="build.classes.dir.resolved"/>
53

<property location="${dist.jar}" name="dist.jar.resolved"/>

<pathconvert property="run.classpath.with.dist.jar">

<path path="${run.classpath}"/>

<map from="${build.classes.dir.resolved}" to="${dist.jar.resolved}"/>

</pathconvert>

<echo>java -cp "${run.classpath.with.dist.jar}" ${main.class}</echo>

</target>

<target depends="init,compile,-pre-pre-jar,-pre-jar"
if="manifest.available+main.class+mkdist.available" name="-do-jar-with-
libraries">

<property location="${build.classes.dir}"
name="build.classes.dir.resolved"/>

<pathconvert property="run.classpath.without.build.classes.dir">

<path path="${run.classpath}"/>

<map from="${build.classes.dir.resolved}" to=""/>

</pathconvert>

<pathconvert pathsep=" " property="jar.classpath">

<path path="${run.classpath.without.build.classes.dir}"/>

<chainedmapper>

<flattenmapper/>

<globmapper from="*" to="lib/*"/>

54

</chainedmapper>

</pathconvert>

<taskdef
classname="org.netbeans.modules.java.j2seproject.copylibstask.CopyLibs"
classpath="${libs.CopyLibs.classpath}" name="copylibs"/>

<copylibs compress="${jar.compress}" jarfile="${dist.jar}" manifest="$

{manifest.file}" runtimeclasspath="${run.classpath.without.build.classes.dir}">

<fileset dir="${build.classes.dir}"/>

<manifest>

<attribute name="Main-Class" value="${main.class}"/>

<attribute name="Class-Path" value="${jar.classpath}"/>

</manifest>

</copylibs>

<echo>To run this application from the command line without Ant,
try:</echo>

<property location="${dist.jar}" name="dist.jar.resolved"/>

<echo>java -jar "${dist.jar.resolved}"</echo>

</target>

<target name="-post-jar">

<!-- Empty placeholder for easier customization. -->

<!-- You can override this target in the ../build.xml file. -->

</target>
55

<target depends="init,compile,-pre-jar,-do-jar-with-manifest,-do-jar-without-
manifest,-do-jar-with-mainclass,-do-jar-with-libraries,-post-jar"
description="Build JAR." name="jar"/>

<!--

=================

EXECUTION SECTION

=================

-->

<target depends="init,compile" description="Run a main class."

name="run">

<j2seproject1:java>

<customize>

<arg line="${application.args}"/>

</customize>

</j2seproject1:java>

</target>

<target name="-do-not-recompile">

<property name="javac.includes.binary" value=""/>

</target>

<target depends="init,-do-not-recompile,compile-single" name="run-single">

<fail unless="run.class">Must select one file in the IDE or set

run.class</fail>
56

<j2seproject1:java classname="${run.class}"/>

</target>

<!--

=================

DEBUGGING SECTION

=================

-->

<target depends="init" if="netbeans.home" name="-debug-start-debugger">

<j2seproject1:nbjpdastart name="${debug.class}"/>

</target>

<target depends="init,compile" name="-debug-start-debuggee">

<j2seproject3:debug>

<customize>

<arg line="${application.args}"/>

</customize>

</j2seproject3:debug>

</target>

<target depends="init,compile,-debug-start-debugger,-debug-start-debuggee"
description="Debug project in IDE." if="netbeans.home" name="debug"/>

<target depends="init" if="netbeans.home" name="-debug-start-debugger-

stepinto">
57

<j2seproject1:nbjpdastart stopclassname="${main.class}"/>

</target>

<target depends="init,compile,-debug-start-debugger-stepinto,-debug-start-
debuggee" if="netbeans.home" name="debug-stepinto"/>

<target depends="init,compile-single" if="netbeans.home" name="-debug-

start-debuggee-single">

<fail unless="debug.class">Must select one file in the IDE or set

debug.class</fail>

<j2seproject3:debug classname="${debug.class}"/>

</target>

<target depends="init,-do-not-recompile,compile-single,-debug-start-
debugger,-debug-start-debuggee-single" if="netbeans.home" name="debug-
single"/>

<target depends="init" name="-pre-debug-fix">

<fail unless="fix.includes">Must set fix.includes</fail>

<property name="javac.includes" value="${fix.includes}.java"/>

</target>

<target depends="init,-pre-debug-fix,compile-single" if="netbeans.home"

name="-do-debug-fix">

<j2seproject1:nbjpdareload/>

</target>

<target depends="init,-pre-debug-fix,-do-debug-fix" if="netbeans.home"

name="debug-fix"/>
58

<!--

===============

JAVADOC SECTION

===============

-->

<target depends="init" name="-javadoc-build">

<mkdir dir="${dist.javadoc.dir}"/>

<javadoc additionalparam="${javadoc.additionalparam}" author="$

{javadoc.author}" charset="UTF-8" destdir="${dist.javadoc.dir}"
docencoding="UTF-8" encoding="${javadoc.encoding.used}"
failonerror="true" noindex="${javadoc.noindex}" nonavbar="$
{javadoc.nonavbar}" notree="${javadoc.notree}" private="${javadoc.private}"
source="${javac.source}" splitindex="${javadoc.splitindex}" use="$
{javadoc.use}" useexternalfile="true" version="${javadoc.version}"
windowtitle="${javadoc.windowtitle}">

<classpath>

<path path="${javac.classpath}"/>

</classpath>

<fileset dir="${src.dir}" excludes="${excludes}" includes="$

{includes}">

<filename name="**/*.java"/>

</fileset>

</javadoc>
59

</target>

<target depends="init,-javadoc-build" if="netbeans.home" name="-javadoc-

browse" unless="no.javadoc.preview">

<nbbrowse file="${dist.javadoc.dir}/index.html"/>

</target>

<target depends="init,-javadoc-build,-javadoc-browse" description="Build

Javadoc." name="javadoc"/>

<!--

=========================

JUNIT COMPILATION SECTION

=========================

-->

<target depends="init,compile" if="have.tests" name="-pre-pre-compile-

test">

<mkdir dir="${build.test.classes.dir}"/>

</target>

<target name="-pre-compile-test">

<!-- Empty placeholder for easier customization. -->

<!-- You can override this target in the ../build.xml file. -->

</target>

<target if="do.depend.true" name="-compile-test-depend">

60

<j2seproject3:depend classpath="${javac.test.classpath}" destdir="$

{build.test.classes.dir}" srcdir="${test.src.dir}"/>

</target>

<target depends="init,compile,-pre-pre-compile-test,-pre-compile-test,-
compile-test-depend" if="have.tests" name="-do-compile-test">

<j2seproject3:javac classpath="${javac.test.classpath}" debug="true"

destdir="${build.test.classes.dir}" srcdir="${test.src.dir}"/>

<copy todir="${build.test.classes.dir}">

<fileset dir="${test.src.dir}" excludes="${build.classes.excludes},$

{excludes}" includes="${includes}"/>

</copy>

</target>

<target name="-post-compile-test">

<!-- Empty placeholder for easier customization. -->

<!-- You can override this target in the ../build.xml file. -->

</target>

<target depends="init,compile,-pre-pre-compile-test,-pre-compile-test,-do-
compile-test,-post-compile-test" name="compile-test"/>

<target name="-pre-compile-test-single">

<!-- Empty placeholder for easier customization. -->

<!-- You can override this target in the ../build.xml file. -->

</target>
61

<target depends="init,compile,-pre-pre-compile-test,-pre-compile-test-single"
if="have.tests" name="-do-compile-test-single">

<fail unless="javac.includes">Must select some files in the IDE or set

javac.includes</fail>

<j2seproject3:force-recompile destdir="${build.test.classes.dir}"/>

<j2seproject3:javac classpath="${javac.test.classpath}" debug="true"

destdir="${build.test.classes.dir}" excludes="" includes="${javac.includes}"
sourcepath="${test.src.dir}" srcdir="${test.src.dir}"/>

<copy todir="${build.test.classes.dir}">

<fileset dir="${test.src.dir}" excludes="${build.classes.excludes},$

{excludes}" includes="${includes}"/>

</copy>

</target>

<target name="-post-compile-test-single">

<!-- Empty placeholder for easier customization. -->

<!-- You can override this target in the ../build.xml file. -->

</target>

<target depends="init,compile,-pre-pre-compile-test,-pre-compile-test-
single,-do-compile-test-single,-post-compile-test-single" name="compile-test-
single"/>

<!--

=======================

JUNIT EXECUTION SECTION

62

=======================

-->

<target depends="init" if="have.tests" name="-pre-test-run">

<mkdir dir="${build.test.results.dir}"/>

</target>

<target depends="init,compile-test,-pre-test-run" if="have.tests" name="-do-

test-run">

<j2seproject3:junit testincludes="**/*Test.java"/>

</target>

<target depends="init,compile-test,-pre-test-run,-do-test-run" if="have.tests"

name="-post-test-run">

<fail if="tests.failed">Some tests failed; see details above.</fail>

</target>

<target depends="init" if="have.tests" name="test-report"/>

<target depends="init" if="netbeans.home+have.tests" name="-test-

browse"/>

<target depends="init,compile-test,-pre-test-run,-do-test-run,test-report,-post-
test-run,-test-browse" description="Run unit tests." name="test"/>

<target depends="init" if="have.tests" name="-pre-test-run-single">

<mkdir dir="${build.test.results.dir}"/>

</target>
63

<target depends="init,compile-test-single,-pre-test-run-single" if="have.tests"

name="-do-test-run-single">

<fail unless="test.includes">Must select some files in the IDE or set

test.includes</fail>

<j2seproject3:junit excludes="" includes="${test.includes}"/>

</target>

<target depends="init,compile-test-single,-pre-test-run-single,-do-test-run-
single" if="have.tests" name="-post-test-run-single">

<fail if="tests.failed">Some tests failed; see details above.</fail>

</target>

<target depends="init,-do-not-recompile,compile-test-single,-pre-test-run-
single,-do-test-run-single,-post-test-run-single" description="Run single unit
test." name="test-single"/>

<!--

=======================

JUNIT DEBUGGING SECTION

=======================

-->

<target depends="init,compile-test" if="have.tests" name="-debug-start-

debuggee-test">

<fail unless="test.class">Must select one file in the IDE or set

test.class</fail>
64

<property location="${build.test.results.dir}/TEST-${test.class}.xml"
name="test.report.file"/>

<delete file="${test.report.file}"/>

<mkdir dir="${build.test.results.dir}"/>

<j2seproject3:debug
classname="org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner"
classpath="${ant.home}/lib/ant.jar:${ant.home}/lib/ant-junit.jar:$
{debug.test.classpath}">

<customize>

<syspropertyset>

<propertyref prefix="test-sys-prop."/>

<mapper from="test-sys-prop.*" to="*" type="glob"/>

</syspropertyset>

<arg value="${test.class}"/>

<arg value="showoutput=true"/>

<arg
value="formatter=org.apache.tools.ant.taskdefs.optional.junit.BriefJUnitResultF
ormatter"/>

<arg
value="formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResult
Formatter,${test.report.file}"/>

</customize>

</j2seproject3:debug>
65

</target>

<target depends="init,compile-test" if="netbeans.home+have.tests" name="-

debug-start-debugger-test">

<j2seproject1:nbjpdastart classpath="${debug.test.classpath}" name="$

{test.class}"/>

</target>

<target depends="init,-do-not-recompile,compile-test-single,-debug-start-
debugger-test,-debug-start-debuggee-test" name="debug-test"/>

<target depends="init,-pre-debug-fix,compile-test-single"
if="netbeans.home" name="-do-debug-fix-test">

<j2seproject1:nbjpdareload dir="${build.test.classes.dir}"/>

</target>

<target depends="init,-pre-debug-fix,-do-debug-fix-test" if="netbeans.home"

name="debug-fix-test"/>

<!--

=========================

APPLET EXECUTION SECTION

=========================

-->

<target depends="init,compile-single" name="run-applet">

<fail unless="applet.url">Must select one file in the IDE or set

applet.url</fail>
66

<j2seproject1:java classname="sun.applet.AppletViewer">

<customize>

<arg value="${applet.url}"/>

</customize>

</j2seproject1:java>

</target>

<!--

=========================

APPLET DEBUGGING SECTION

=========================

-->

<target depends="init,compile-single" if="netbeans.home" name="-debug-

start-debuggee-applet">

<fail unless="applet.url">Must select one file in the IDE or set

applet.url</fail>

<j2seproject3:debug classname="sun.applet.AppletViewer">

<customize>

<arg value="${applet.url}"/>

</customize>

</j2seproject3:debug>

</target>
67

<target depends="init,compile-single,-debug-start-debugger,-debug-start-
debuggee-applet" if="netbeans.home" name="debug-applet"/>

<!--

===============

CLEANUP SECTION

===============

-->

<target depends="init" name="deps-clean" unless="no.deps"/>

<target depends="init" name="-do-clean">

<delete dir="${build.dir}"/>

<delete dir="${dist.dir}"/>

</target>

<target name="-post-clean">

<!-- Empty placeholder for easier customization. -->

<!-- You can override this target in the ../build.xml file. -->

</target>

<target depends="init,deps-clean,-do-clean,-post-clean" description="Clean

build products." name="clean"/>

</project>
68

SYSTEM DESIGN
INPUT DESIGN

Input design is the process of converting user-oriented input to a

computer based format. Input design is a part of overall system design, which
requires very careful attention .Often the collection of input data is the most
expensive part of the system. The main objectives of the input design are …

1. Produce cost effective method of input

2. Achieve highest possible level of accuracy

3. Ensure that the input is acceptable to and understood by the staff.

Input Data

The goal of designing input data is to make entry easy, logical and free
from errors as possible. The entering data entry operators need to know the
allocated space for each field; field sequence and which must match with that in
the source document. The format in which the data fields are entered should be
given in the input form .Here data entry is online; it makes use of processor that
accepts commands and data from the operator through a key board. The input
required is analyzed by the processor. It is then accepted or rejected. Input
stages include the following processes

 Data Recording
 Data Transcription
 Data Conversion
 Data Verification
 Data Control
 Data Transmission
69

 Data Correction

One of the aims of the system analyst must be to select data capture
method and devices, which reduce the number of stages so as to reduce both the
changes of errors and the cost .Input types, can be characterized as.

 External
 Internal
 Operational
 Computerized
 Interactive

Input files can exist in document form before being input to the computer.
Input design is rather complex since it involves procedures for capturing data as
well as inputting it to the computer.

OUTPUT DESIGN

Outputs from computer systems are required primarily to communicate

the results of processing to users. They are also used to provide a permanent
copy of these result for latter consultation .Computer output is the most
important and direct source of information to the users. Designing computer
output should proceed in an organized well through out the manner. The right
output must be available for the people who find the system easy o use. The
outputs have been defined during the logical design stage. If not, they should
defined at the beginning of the output designing terms of types of output
connect, format, response etc,
70

Various types of outputs are

 External outputs
 Internal outputs
 Operational outputs
 Interactive outputs
 Turn around outputs

All screens are informative and interactive in such a way that the user can
full fill his requirements through asking queries.
71

DATABASE DESIGN

The general theme behind a database is to handle information as an

integrated whole. A database is a collection of interrelated data stored with
minimum redundancy to serve many users quickly and effectively. After
designing input and output, the analyst must concentrate on database design
or how data should be organized around user requirements. The general
objective is to make information access, easy quick, inexpensive and flexible
for other users. During database design the following objectives are
concerned:-

 Controlled Redundancy
 Data independence
 Accurate and integrating
 More information at low cost
 Recovery from failure
 Privacy and security
 Performance
 Ease of learning and use
72

TABLES USED
Student

Field Name Data Type Description

RollNo Number Primary Key
SName Text(50) -
Phno Text(15) -
Sex Text(10) -
FName Text(50) -
Occupation Text(50) -
MName Text(50) -
DOB Date/Time -
Age Number -
Caste Text(25) -
Religion Text(30) -
Hname Text(50) -
City Text(50) -
District Text(50) -
State Text(50) -
Pin Text(10) -
Year Number -
Qualification Text(25) -

UAD

Field Name Data Type Description

Username Text(25) Primary Key
Password Text(15) -
Type Text(15) -
73

Subjects

Field Name Data Type Description

Subjectcode Text(10) Primary Key
Subjectname Text(50) -
Creditmark Number -
MaxMark Number -
Type Text(25) -

SubjectAllocation

Field Name Data Type Description

Subjectname Text(50) -
Semester Number -
Batch Text(15) -

SSLC1

Field Name Data Type Description

RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
74

SSLC2

Field Name Data Type Description

RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -

SSLC3

Field Name Data Type Description

RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -

SSLC4

Field Name Data Type Description

RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
75

SSLC5

Field Name Data Type Description

RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -

SSLC6

Field Name Data Type Description

RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
76

PLUSTWO1

Field Name Data Type Description

RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -

PLUSTWO2

Field Name Data Type Description

RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -

PLUSTWO3

Field Name Data Type Description

RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
77

PLUSTWO4

Field Name Data Type Description

RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
78

PLUSTWO5

Field Name Data Type Description

RollNo Number -
SubjectName Text(50) -
Subjectcode Text(15) -
Internal Number -
Theory Number -
Practical Number -
Total Number -
79

SYSTEM IMPLEMENTATION

Implementation is the stage in the project where the theoretical design is

turned into a working system. The implementation phase constructs, installs and
operates the new system. The most crucial stage in achieving a new successful
system is that it will work efficiently and effectively.

There are several activities involved while implementing a new project. They
are

 End user training

 End user Education
 Training on the application software
 System Design
 Parallel Run and To New System
 Post implementation Review

End user Training:

The successful implementation of the new system will purely upon the
involvement of the officers working in that department. The officers will be
imparted the necessary training on the new technology

End User Education:

The education of the end user start after the implementation and testing is
over. When the system is found to be more difficult to under stand and complex,
more effort is put to educate the end used to make them aware of the system,
giving them lectures about the new system and providing them necessary
documents and materials about how the system can do this.
80

Training of application software:

After providing the necessary basic training on the computer awareness,

the users will have to be trained upon the new system such as the screen flows
and screen design type of help on the screen, type of errors while entering the
data, the corresponding validation check at each entry and the way to correct the
data entered. It should then cover information needed by the specific user or
group to use the system.

Post Implementation View:

The department is planning a method to know the states of t he past

implementation process. For that regular meeting will be arranged by the
concerned officers about the implementation problem and success
81

SOFTWARE TESTING
Is the menu bar displayed in the appropriate contested some system
related features included either in menus or tools? Do pull –Down menu
operation and Tool-bars work properly? Are all menu function and pull down
sub function properly listed ?; Is it possible to invoke each menu function using
a logical assumptions that if all parts of the system are correct, the goal will be
successfully achieved .? In adequate testing or non-testing will leads to errors
that may appear few months later.

This create two problem

1. Time delay between the cause and appearance of the problem.

2. The effect of the system errors on files and records within the system

The purpose of the system testing is to consider all the likely variations to
which it will be suggested and push the systems to limits.

The testing process focuses on the logical intervals of the software

ensuring that all statements have been tested and on functional interval is
conducting tests to uncover errors and ensure that defined input will produce
actual results that agree with the required results. Program level testing,
modules level testing integrated and carried out.

There are two major type of testing they are

1) White Box Testing.

2) Black Box Testing.

White Box Testing

White box some times called “Glass box testing” is a test case design
uses the control structure of the procedural design to drive test case.
82

Using white box testing methods, the following tests where made on the system

a) All independent paths within a module have been exercised once. In our
system, ensuring that case was selected and executed checked all case
structures. The bugs that were prevailing in some part of the code where fixed

b) All logical decisions were checked for the truth and falsity of the values.

Black box Testing

Black box testing focuses on the functional requirements of the software. This is
black box testing enables the software engineering to derive a set of input
conditions that will fully exercise all functional requirements for a program.
Black box testing is not an alternative to white box testing rather it is
complementary approach that is likely to uncover a different class of errors that
white box methods like..

1) Interface errors

2) Performance in data structure

3) Performance errors

4) Initializing and termination errors

83

CONCLUSION

Our project is only a humble venture to satisfy the needs in an

Institution. Several user friendly coding have also adopted. This package
shall prove to be a powerful package in satisfying all the requirements of the
organization.

The objective of software planning is to provide a frame work that

enables the manger to make reasonable estimates made within a limited time
frame at the beginning of the software project and should be updated
regularly as the project progresses. Last but not least it is no the work that
played the ways to success but ALMIGHTY
84

BIBLIOGRAPHY

1) http://www.javaworld.com/javaworld/jw-01-1998/jw-01-bookreview.html
2) Database Programming with JDBC and Java by O'Reilly
3) Head First Java 2nd Edition
4) http://www.jdbc-tutorial.com/
5) Java and Software Design Concepts by APress