A

Project
Presentation
On
Student Management
System
Submitted to

Project Guide: Mr Ajai Kumar Submitted by: Akhil Saroha

Dept CSE Aryan Malik
Aryan Kuchhal
Badal Chaudhary
 CONTENTS

1. Technology used in project and other compatible technologies

2. Project Undertaken
3. Introduction to project
4. Project Analysis
(a) Project Planning
(b) Division of time of work
(c) Project requirement & specification
5. Project design
(a) Dataflow diagram
(b) Database design
(c) Snapshots of Forms with some coding.
6. Project Testing
7. Maintenance
8. Project security
9. Project implementation
10. Conclusion
References
 Technology Used in the
Project

Introduction

When the chronicle of computer languages is written, the following will be said: B led to C,
C evolved into C++, and C++ set the stage for Java. To understand Java is to understand the
reasons that drove its creation, the forces that shaped it, and the legacy that it inherits. Like the
successful computer languages that came before, Java is a blend of the best elements of its rich
heritage combined with the innovative concepts required by its unique environment.

Although Java has become inseparably linked with the online environment of the Internet, it is
important to remember that Java is first and foremost a programming language. Computer
language innovation and development occurs for two fundamental reasons:

o To adapt to changing environments and uses

o To implement refinements and improvements in the art of programming
As you will see, the creation of Java was driven by both elements in nearly equal measure.

History

Java was conceived by James Gosling, Patrick Naughton, Chris Warth, Ed Frank, and Mike
Sheridan at Sun Microsystems, Inc. in 1991. It took 18 months to develop the first working
version. This language was initially called “Oak” but was renamed “Java” in 1995. Between
the initial implementation of Oak in the fall of 1992 and the public announcement of Java in
the spring of 1995, many more people contributed to the design and evolution of the language.
Bill Joy, Arthur van Hoff, Jonathan Payne, Frank Yellin, and Tim Lindholm were key
contributors to the maturing of the original prototype.
Somewhat surprisingly, the original impetus for Java was not the Internet! Instead, the primary
motivation was the need for a platform-independent (that is, architectureneutral) language that
could be used to create software to be embedded in various consumer electronic devices, such
as microwave ovens and remote controls. As you can probably guess, many different types of
CPUs
are used as controllers. The trouble with C and C++ (and most other languages) is that they
are designed to be compiled for a specific target. Although it is possible to compile a C++
program for just about any type of CPU, to do so requires a full C++ compiler targeted for
that CPU. The problem is that compilers are expensive and time-consuming to create. An
easier— and more cost-efficient—solution was needed. In an attempt to find such a solution,
Gosling and others began work on a portable, platform-independent language that could be
used to produce code that would run on a variety of CPUs under differing environments. This
effort ultimately led to the creation of Java.

Feature

Although the fundamental forces that necessitated the invention of Java are portability
and security, other factors also played an important role in molding the final form of
the language. These features are as follows:
o Simple : Java was designed to be easy for the professional programmer to
learn and use effectively. Assuming that you have some programming
experience, you will not find Java hard to master. If you already understand the
basic concepts of object-oriented programming, learning Java will be even
easier.
o Secure: As you are likely aware, every time that you download a “normal”
program, you are risking a viral infection. Prior to Java, most users did not
download executable programs frequently, and those who did scanned them for
viruses prior to execution. Even so, most users still worried about the
possibility of infecting their systems with a virus. In addition to viruses,
another type of malicious program exists that must be guarded against. This
type of program can gather private information, such as credit card numbers,
bank account balances, and passwords, by searching the contents of your
computer’s local file system. Java answers both of these concerns by providing
a “firewall” between a networked application and your computer. When you
use a Java-compatible Web browser, you can safely download Java applets
without fear of viral infection or malicious intent.
o Object-oriented: Although influenced by its predecessors, Java was not
designed to be source-code compatible with any other language. This allowed
the Java
 team the freedom to design with a blank slate. One outcome of this was a clean,
usable, pragmatic approach to objects. Borrowing liberally from many seminal
object-software environments of the last few decades, Java manages to strike a
balance between the purist’s “everything is an object” paradigm and the
pragmatist’s “stay out of my way” model. The object model in Java is simple
and easy to extend, while simple types, such as integers, are kept as high-
performance nonobjects.
o Robust: The multiplatformed environment of the Web places extraordinary
demands on a program, because the program must execute reliably in a variety
of systems. Thus, the ability to create robust programs was given a high
priority in the design of Java. To gain reliability, Java restricts you in a few key
areas, to force you to find your mistakes early in program development.
o Multithreaded: Java was designed to meet the real-world requirement of
creating interactive, networked programs. To accomplish this, Java supports
multithreaded programming, which allows you to write programs that do
many things simultaneously.
o Architecture-neutral: A central issue for the Java designers was that of code
longevity and portability. One of the main problems facing programmers is that
no guarantee exists that if you write a program today, it will run tomorrow—
even on the same machine. Operating system upgrades, processor upgrades, and
changes in core system resources can all combine to make a program
malfunction. The Java designers made several hard decisions in the Java
language and the Java Virtual Machine in an attempt to alter this situation.
Their
Goal was “write once; run anywhere, any time, forever.” To a great extent, this
goal was accomplished.
o Interpreted & High performance: Java enables the creation of cross-platform
programs by compiling into an intermediate representation called Java byte
code. This code can be interpreted on any system that provides a Java Virtual
Machine. Most previous attempts at cross platform solutions have done so at
the expense of performance. Other interpreted systems, such as BASIC, Tcl,
and PERL, suffer from almost insurmountable performance deficits. Java,
however, was designed
 to perform well on very low-power CPUs. As explained earlier, while it is true
that Java was engineered for interpretation, the Java byte code was carefully
designed so that it would be easy to translate directly into native machine code
for very high performance by using a just-in-time compiler. Java run-time
systems that provide this feature lose none of the benefits of the platform-
independent code. “High-performance cross-platform” is no longer an
oxymoron.
o Distributed: Java is designed for the distributed environment of the
Internet, because it handles TCP/IP protocols.
o Dynamic: Java programs carry with them substantial amounts of run-time type
information that is used to verify and resolve accesses to objects at run time.
This makes it possible to dynamically link code in a safe and expedient manner.
This is crucial to the robustness of the applet environment, in which small
fragments of bytecode may be dynamically updated on a running system.

Tools & Technologies:

The JDK comes with a collection of tools that are used for developing and running Java
programs which includes:
Appletviewer :
Enables us to run Java applets(without having a compatible browser)
Javac:
Java Compiler ,which translates Java source code to bytecode files that the
interpreter can understand.
Java:
Java Interpreter, which runs applets and applications by reading
and interpreting byte code files.
Javah:
Produces header files for use with native methods.

Javadoc:
Creates HTML format documentation from Java source code files.
 Jdb:
Java debugger, which finds errors in programs.

Package & Interface:

Packages and interfaces are two of the basic components of a Java program. Packages are
containers for classes that are used to keep the class name space compartmentalized. For
example, a package allows you to create a class named List, which you can store in your own
package without concern that it will collide with some other class named List stored elsewhere.
Packages are stored in a hierarchical manner and are explicitly imported into new class
definitions.
The use of the interface keyword, Java allows you to fully abstract the Interface from its
implementation. Using interface, you can specify a set of methods which can be implemented
by one or more classes. The interface, itself, does not actually define any implementation.
Although they are similar to abstract classes, interfaces have an additional capability: A class
can implement more than one interface.

AWT classes & its Controls:

All applets must import java.applet. Applets must also import java.awt. Recall that AWT
stands for the Abstract Window Toolkit. Since all applets run in a window, it is necessary to
include support for that window. Controls are components that allow a user to interact with
your application in various ways—for example, a commonly used control is the push button. A
layout manager automatically positions components within a container. Thus, the appearance
of a window is determined by a combination of the controls that it contains and the layout
manager used to position them. In addition to the controls, a frame window can also include a
standard- style menu bar. Each entry in a menu bar activates a drop-down menu of options
from which the user can choose. A menu bar is always positioned at the top of a window.
Although different in appearance, menu bars are handled in much the same way as are the other
controls.
 Applets:
The Applet class is contained in the java.applet package. Applet contains several
methods that give you detailed control over the execution of your applet. In addition,
java.applet also defines three interfaces: AppletContext, AudioClip, and AppletStub.

Swings:
Unlike AWT components, Swing components are not implemented by Platform-specific code.
Instead, they are written entirely in Java and, therefore, are Platform-independent. The term
lightweight is used to describe such elements. Swing is a set of classes that provides more
powerful and flexible components than are possible with the AWT. In addition to the familiar
components, such as buttons, check boxes, and labels, Swing supplies several exciting
additions, including tabbed panes, scroll panes, trees, and tables.

RMI:
Remote Method Invocation (RMI) allows a Java object that executes on one machine to invoke
a method of a Java object that executes on another machine. This is an important feature,
because it allows you to build distributed applications.
 Project Undertaken

1. Administrative cell in the Meerut Institute of Engineering and Technology has been
doing a yeoman service in managing students records and their personal information. The
broad functions of Administrative cell are: -
a) Manages personal Information of Students.
b) Manages past Records of Students.
c) Manages Enquiry from students regarding their courses.

2. Presently, the entire process is done manually using MS-Office & is being repeated semester
after semester. It requires huge amount of data to be collected from time to time.
It is felt that in this IT era, the manual process is time consuming, complex & error prone. In
order to streamline the entire process, it has been decided to assign the project to the student of
semester 5th CSE as minor project.

3. The terms of reference for the project are as below.

a) Identify student database to be maintained & updated on the regular basis.

b) Analyze the existing system.
c) The software will be developed using core Java & Database (My-SQL).

4. The project will commence from 1st Dec 2024 and Completed by Jan , 2025.

5. This project will work under the strict guidance of Dr Satendra Kumar

6. The project report will be submitted at the end of Jan 2025.

All the concerned departmental heads and the other staff are requested to extend full support in
completion of the project.
 Introduction To PROJECT

At present the Administrative officers have to manage the records of the every students
of this college manually on paper . They have to search from a large number of various
files ,the required file of the student. This project will solve this problem and is capable of
following:

➢ Maintaining the data of students

➢ Maintaining sessional details of students,
➢ Searching students on the basis of Student ID.,
➢ Collect records of various Programs and Courses..

“SMS” Student Management System software will automate the operations of the
Administrative office of the college.
 PROJECT ANALYSIS

A complete understanding of the software requirements is necessary for successful software. It

is therefore the Requirements analysis is done. The Requirement analysis is a process of
understanding of user requirements, study of existing system, disadvantage of existing system,
objectives of proposed system, and the various constraints that are to be applied to proposed
system.

Requirement analysis is software –engineering task that bridges the gap between user
specification and software design. User’s Requirements are taken as a written document and
verified at the same time. This makes sure that the software Engineer properly understands the
problem. Both the developer and the customer take an active role in the requirement analysis.
The customer tries to put into words, his requirements from the software and the developer acts
as an interrogator, consultant and a problem solver. It enables a S/W Engineer to specify
software functions and performance, indicate software’s interface with other system elements
and establish constraints that the software must meet.

This phase must achieve three primary objectives:

(i) To describe the customer Requirements
(ii) To establish the basis for the creation of the software
(iii) To define the set of requirements

Requirement Analysis of “SMS”

Before the start of the process following analysis was done for the system

What is the system aimed for?

“SMS” Student Management System software will automate the operations of the
Administrative office of the college. Main operations of the Administrative office are:
Maintaining the data of students, maintaining academic structure details of students, Searching
students on the basis of student ID , or enrollment number, Collect records of various Programs
and Courses for “Student Management System”:
Module: 1 (Authority Controller)

➢ In this process, the software will ask for the data of Authorities.
➢ It will ask A_mail,A_name,A_role & A_contact.

Module Description (View, Update, & deletion of Authority Details)

➢ The software manages data of authorities..

➢ It asks A_mail.
➢ The software then provides a view to the data of Authorities.
➢ In this module, a user can update data and can delete data.

Module: 2 (Classroom Controller)

➢ In this process, data of classrooms are seen and updated.
➢ It will ask Cl_roomno,Cl_name & Cl_time.

Module Description : (view, update, & deletion of Classroom Details)

➢ The software manages data of Classrooms.
➢ It asks Cl_roomno.
➢ The software then provides a view to the data of classrooms.
➢ In this module, a user can update data and can delete data.
Module: 3 (Course Controller)

➢ In this process, the software will ask for data of course.

➢ It will ask C_ID,C_name,C_duration & C_credit.

Module Description (View, Update, & deletion of Course Details)

➢ The software manages data of courses.

➢ It asksC_ID.
➢ The software then provides a view to the data of courses.
➢ In this module, a user can update data and can delete data.

Module: 4 (Department Controller)

➢ In this process, data of department are seen.
➢ It will ask D_ID,D_name & D_head.

Module Description : (view, update, & deletion of Department Details)

➢ The software manages data of departments.
➢ It asks D_ID.
➢ The software then provides a view to the data of department..
➢ In this module, a user can update data and can delete data.

Module: 5 (Exam Controller)

➢ In this process, the software will ask for the data of exams..
➢ It will ask E_ID, E_date,, E_type, E_roomno & Mark

.
Module Description (View, Update, & deletion of Exams Details)
 ➢ The software manages data for exams.
➢ It asks E_ID..
➢ The software then provides a view to the data of exams.
➢ In this module, a user can update data and can delete data.

Module: 6 (Faculty Controller)

➢ In this process, data of students regarding their held in DB whose Roll no
in Basic detail Table.
➢ It will ask F_ID,F_name,F_contact & F_mail..

Module Description : (view, update, & deletion of Faculties Details)

➢ The software manages data of faculties..
➢ It asks F_ID.
➢ The software then provides a view to the data of the Faculty..
➢ In this module, a user can update data and can delete data.

Module: 7 (Grade Controller)

➢ In this process, the software will ask for the data of grades..
➢ It will ask G_Id,CGPA,Semester & Sem_Year.

Module Description (View, Update, & deletion of Grade Details)

➢ The software manages data of Grades..

➢ It asks G_ID.
➢ The software then provides a view to the basic Details of the Grading system.
 ➢ In this module, a user can update data and can delete data.

Module: 8 (Program Controller)

➢ In this process, the software will ask for the basic details of students.
➢ It will ask P_ID, P_name, P_duration & P_type.

➢
Module Description (View, Update, & deletion of Program Details)

➢ The software manages data of Programs.

➢ It asks P_ID.
➢ The software then provides a view to the basic Details of the Program..
➢ In this module, a user can update data and can delete data.

Module: 9 (Student Controller)

➢ In this process, data of students regarding their held in DB whose
S_ID in Basic detail Table.
➢ It will ask S_ID,S_name,S_mail,S_contact & Enroll year of all students.

Module Description : (view, update, & deletion of Student Details)

➢ The software manages data of Students..
➢ It asks S_ID.
➢ The software then provides a view to the details of the student.
➢ In this module, a user can update data and can delete data.

PROJECT REQUIREMENT SPECIFICATION

Requirement specifies capabilities that system must provide in order to solve the problem.
Requirement includes functional requirement of hardware, software and user interface. The
system must be able to integrate the following facilities.
 ➢ Interactive menus for selecting operation to be performed.

➢ The record must have all the essential fields, roll number, name etc.

ENVIRONMENTAL REQUIREMENTS

HARDWARE REQUIREMENTS

1. PC-Pentium III or above

2. 128 MB RAM
3. 10 GB Hard Disk

SOFTWARE REQUIREMENTS

1. JDK 2.3
2. JDBC/ODBC
3. My-SQL
3. PERFORMANCE REQUIREMENTS

The performance requirements of the system are that it should have fast response and
correct retrieval of information. The language used should be very easy and clear to
understand for the user or the operator for feeding the data or the records etc. The main
memory should be large enough to handle large data and store it well. The system should
maintain the complete integrity.

SYSTEM ACCEPTANCE CRITERIA

The system should be able to create data files, retrieve, update and format by information
form the system file. It should be able to recognize invalid entries and corresponding error
message should be generated. The system must be able to perform all the function viz.
maintenance of master files, temporary files, calculating data, able to handle and process the
data, should generate the necessary reports etc. While performing these above functions the
data integrity must be maintained. It should have the space for storage of the full records and
the data.
 Project Design

Software design is the process of applying various techniques and principles for the purpose
of the designing a system in sufficient details to present its physical relation.
The software is built in three stages:-
1. External Design
2. Architectural Design
3. Detailed Design

External design in software involves conceiving, planning out and specifying the external
observable characteristics of a software product. These characteristics include user display and
report format, external data sources and sinks and functional characteristics, performance
requirement and high level process structure for the product. In other words we can say that
external design is the transitional step form the requirement definition.
Architectural design is concerned with refining the conceptual view of the system, identifying
internal processing functions decomposing higher level functions into sub functions, defining
external data streams and data structures and establishing relationships and interconnections
among functions.
Detailed design includes specification of algorithms that implements the functions, concrete
data structures that implements the data structure, the actual interconnections among functions
data structures and packing schemes for the system.

1. External Design
External Design consideration is to perform the Authority details through
the unique field i.e. the Authority ID, perform structure classification of various
Classes,Courses,Departments,Exams,Faculties,Grades, Programs & assigning students to their
respective course,program and assign faculties to them.. Filling of all the forms should be
automatic i.e. viz. either diagrams or flow charts, algorithms.

2. Architectural Design
In architectural design, describe the structure of a system. There are standard
design representation techniques such a data flow diagrams structure charts, algorithms.
 Dataflow Diagram

Student Database Input from Authority

ODBC Calls

DB
Connection
M
a
Queries & Update to DB i
n

F
o
r
m

Modify Student info

Delete Student info/Add
Student
 DATABASE DESIGN

Table Structure Used in “Student Management System”

1. Student

Primary Key: S_ID

Description: This table is used to store basic details of students.

Field Name Field Size Description

Type
S-ID Int Default ID of student
S_name Varchar 100 Name of Student
S_mail Varchar 255 Student email id
S_contact Varchar 20 Contact no of student
Enroll year Int default Enrollment year of student

2. Program
Primary Key: P_ID
Description: This table is used to store details of programs.

Field Name Field Size Description

Type
P_ID Int Default Program ID
P_name Varchar 100 Program Name
P_duration Int Default Duration of the program
P_type Varchar 50 Program Type
`
3. Grade
Primary Key: grade_id
Description: This table is used to store details of Grades

Field Name Field Size Description

Type
grade_id Int Default ID of grade
S_ID Int Default ID of Student
C_ID Int Default ID of Course
E_ID Int Default ID of Exam
Grade Varchar 2 Grade of student

4. Faculty
Primary Key: F_ID
Description: This table is used to store details of Faculties.

Field Name Field Size Description

Type
F_ID Int Default ID of faculty
F_name Varchar 50 Name of Student
F_contact Varchar 20 Contact details of Faculty
F_mail Varchar 255 Email id of faculty

5. Exam
Primary Key: E_ID
Description: This table is used to store details of Exams.

Field Name Field Size Description

Type
E_ID Int Default ID of exams
E_date Date NA Date of exam
E_type Varchar 50 Type of exam
E-roomnol Varchar 10 Room No of exam
Mark Int Default Marks obtained by the student
6. Dept
Primary Key: D_ID
Description: This table is used to store details of departments.

Field Name Field Size Description

7. Type
D_ID Int Default ID of dept
D_name Varchar 100 Name of dept
D_head Varchar 100 Head of dept
Course
Primary Key: C_ID
Description: This table is used to store details of Courses.

Field Name Field Size Description

Type
C_ID Int Default ID of courses
C_name Varchar 100 Name of course
C_duration Int Default Duration of the course
C_credit Int Default Credit of the course

8. Classroom
Primary Key: Cl_roomno
Description: This table is used to store details of Classrooms.

Field Name Field Size Description

Type
Cl_roomno Varchar 10 Classroom no
Cl_name Varchar 100 Name of the classroom
Cl_time Varchar 50 Time of classroom

9. Authority
 Primary Key: A_mail
Description: This table is used to store details of Authority.

Field Name Field Size Description

Type
A_mail Varchar 255 Email id of authority
A_name Varchar 100 Name of authority
A_role Varchar 50 Role of authority
A_contact Varchar 20 Contact details of authority

PROJECT TESTING
Testing is the process of exercising software with the intent of finding and ultimately
correcting the errors. Testing demonstrates that software functions appear to be working
according to specification, that performance requirements appear to have been met. Data
collected as testing is conducted provide a good indication of software reliability and some
indication of software reliability and some indication of software quality as a whole.

Testing objectives:

➢ Testing is process of executing a program with the intent of finding an error.

➢ A good test case is one of that has high probability of finding a yet
undiscovered error.
➢ A successful test is the one that uncovers a yet undiscovered error.

Type of Testing:

➢ White Box Testing: White Box Testing is a test case design that uses the
control structure of the procedural design to derive test cases.
White Box Testing basically looks for:
(a) Logical Errors
(b) Loop Testing
(c) Typographical Errors
(d) Testing of all independent paths
(e) Tests all the internal data structure
(f) Condition Testing
White Box Testing is done on individual modules as well as the complete program.
➢ Black Box Testing: The basic objective of the Black Box Testing is to check the
functional requirements of the system. Black Box Testing is done to find test cases. The
tests done proved to be satisfactory after a few minor changes. The database
updating,deletion, modifications were perfect. The validation and checks were put in
every page to prevent user from entering wrong data.

Testing methods:
Software testing states a number of methods to ensure complete testing, which are:-
➢ Unit testing: The developer according to the design tests each individual
function/program individually. This is done before the function is released for final
Integration and System testing. It is the responsibility of the individual developer to
ensure that the individual units are working as per the requirements. Selected
processing components are unit tested- Selection Data module was having an error
in selecting eligible students for a drive. There was a problem in the query used for
that purpose.
● Integration testing: The integrated system is tested against the Test Scripts and
functional specification. The project team is involved in testing the integrated
software.
● System testing: Once the final integration testing is over all the known faults are
fixed, the application is tested on the basis of the Test Scripts and Functional
Specification. The project team is involved in system testing. The application is
implemented in a variety of different environmental Configurations and is tested for
compatibility with each configuration.

Test Strategies:

Test cases are designed with the intent of finding errors in the way the system will process it.
There are two general strategies for testing software. They are:

● Code Testing: The code testing strategy examines the logic of the program. To
follow this testing method, the analyst develops test cases that result in executing
every instruction in the program or module; i.e. every path through the program is
tested. A path is a specific combination of conditions that is handled by the
program.On the surface, code testing seems to be an ideal method for testing
software. This testing strategy does not indicate whether all aspects are even
implemented. Code testing also does not check the range of the data that the
program will accept, even though, when software failures in actual case, it is
frequently because users submitted data out of expected ranges.
● Specification Testing: To perform specification testing, specification is examined
 stating what the program should do and how it should perform under various
conditions. Then test cases are developed for each condition or combination of
conditions and submitted for processing. By examining the results, we can
determine whether the program performs according to its specified
requirements.MAINTENANCE

This phase start when software system is released for production work and it continue during
all the lifetime. It is the largest and the most important phase. Maintenance activities include:
➢ Enhancement of capabilities

➢ Error correction
➢ Deletion of obsolete features

We have three types of maintenance:

➢ Preventive
For the software to prevent from any type of technological or requirement change, we
will work on the project after its submission to TPO cell.
➢ Corrective

The coding is implemented again and again to check the faults and it is checked at
different levels.
➢ Adaptive

JAVA can adapt itself to any operating system environment. So there is no need for this
type of maintenance scheme.PROJECT SECURITY

Security is concerned with making sure that unauthorized people cannot access the
software. Even no one can change the entered information of students.

Security requirements are particularly significantly in many database systems. Security

requirements lace restrictions on the use of certain commands, control access to data, provide

different kinds of access requirements for different people, require the use of password.
 We have provided a login facility which asks for user name and password. We have
given all the authority to a user but in future enhancements; we are planning to make to classes
of users.
 PROJECT IMPLEMENTATION

In this phase, the system or system modifications are installed and made
operational in a production environment. The phase is initiated after the system has been tested
and accepted by the user and Project Manager. Activities in this phase include notification of
implementation to end users, execution of the previously defined training plan, data entry or
conversion, and post implementation review. This phase continues until the system is operating
in production in accordance with the defined user requirements.
The new system can fall into three categories, replacement of a manual process,
replacement of a legacy system, or upgrade to an existing system. Regardless of the type of
system, all aspects of the implementation phase should be followed.

Steps of Implementation:

● Notify users of new implementation: The implementation notice should be sent to

all users and organizations affected by the implementation. Additionally, it is good
policy to make internal organizations not directly affected by the implementation
aware of the schedule so that allowances can be made for a disruption in the normal
activities of that section.
● Execute training plan: It is always a good business practice to provide training
before the end user uses the new system. Because there has been a previously
designed training plan established, complete with the system user manual, the
execution of the plan should be relatively simple.
● Perform data entry or conversion: With the implementation of any system,
typically there is old data which is to be included in the new system. This data can
be in a manual or an automated form. Regardless of the format of the data, the tasks
in this section are two fold, data input and data verification. When replacing a
manual system, hard copy data will need to be entered into the automated system.
Some sort of verification that the data is being entered correctly should be
conducted throughout
 this process. This is also the case in data transfer, where data fields in the old
system may have been entered inconsistently and therefore affect the integrity of the
new database. Verification of the old data becomes imperative to a useful computer
system.
the operation can proceed on the old system while the bugs are worked out.
● Install System: To ensure that the system is fully operational, install the system in
a production environment.
● Conduct post-implementation review: After the system has been fielded a post-
implementation review is conducted to determine the success of the project through
its implementation phase. The purpose of this review is to document
implementation experiences to recommend system enhancements and provide
guidance for future projects.
In addition, change implementation notices will be utilized to
document user requests for fixes to problems that may have been recognized
during this phase. It is important to document any user request for a change
to a system to limit misunderstandings between the end user and the system
programmers.

After the Implementation Phase Review and Approval Certification is signed by the
Project Manager and the System Proponent representatives, the system – including the
production version of the data repository – is delivered to the customer for the Operations and
Maintenance Phase.
The review is conducted at the end of the Implementation Phase. A post-implementation
review shall be conducted to ensure that the system functions as planned and expected; to
verify that the system cost is within the estimated amount; and to verify that the intended
benefits are derived as projected.
 CONCLUSION
We have earnestly Endeavour to carry out the given project study to the best of our capacities.
However due to time constraints, this project could not be carried out as per the initial set
objectives. This would include the following:

➢ Record adding facility.

➢ Record viewing Facility.
 REFERENCES

1. The Complete Reference to Java by Herbert Schdilt.

2. Teach Yourself Java in 21 Days.
3. Gateway to SCJP by Keyur Shah.
4. A programmer’s guide to JAVA 2 by Ivor Harton.
5. OOPS with JAVA by E. Balagurusamy.