A PROJECT REPORT

ON
“HOSPITAL MANAGEMENT SYSTEM”
SUBMITTED IN THE PARTIAL FULFILLMENT OF THE REQUIREMENTS

FOR THE AWARD OF THE DEGREE

OF

BACHELOR OF COMPUTER APPLICATION

CHAUDHARY CHARAN SINGH UNIVERSITY, MEERUT

Session (2018-2021)

SUBMITTED TO : SUBMITTED BY:

Mr. PUNIT KUMAR SHARMA SANDHYA RAWAT

Assistant Professor BCA VI SEM
FIT, MEERUT ROLL NO. (180942106138)

FORTE INSTITUTE OF TECHNOLOGY,

MAWANA ROAD MEERUT
 A PROJECT REPORT
ON
“HOSPITAL MANAGEMENT SYSTEM”
SUBMITTED IN THE PARTIAL FULFILLMENT OF THE REQUIREMENTS

FOR THE AWARD OF THE DEGREE

OF

BACHELOR OF COMPUTER APPLICATION

CHAUDHARY CHARAN SINGH UNIVERSITY, MEERUT

Session (2018-2021)

SUBMITTED TO : SUBMITTED BY:

Mr. PUNIT KUMAR SHARMA SANDHYA RAWAT

Assistant Professor BCA VI SEM
FIT, MEERUT ROLL NO. (180942106138)

FORTE INSTITUTE OF TECHNOLOGY,

MAWANA ROAD MEERUT
 ACKNOWLEDGEMENT
The satisfaction that accompanies successful completion of any work would be incomplete without the

mention of the people who made it possible.

Primarily, I would like to thank my faculty members for giving me the opportunity to fulfill my

aspiration. With deep sense and regards, I am obliged to Mr. PUNIT KUMAR SHARMA , Project

Guide and project coordinator, as he had a direct influence, some way, in my motivation and

gratefulness for being part of the responsible project guide of the institute. I am very thankful to him

for his valuable guidance and remarkable patience in guiding my work to its fulfillment.

I wish to thank my parents for their constant encouragement which is like snow, so after when it falls

and longer when it falls and longer when it dwells upon, the deeper it sinks in mind.

I will be failing in my mission if I do not thank other people who directly or indirectly helped me in the

successful completion of this project.

So, my heart full thanks to all friends mainly who supported and encouraged me in preparing this

project report as best as possible.

SANDHYA RAWAT
BCA VITH SEM
ROLL NO. 180942106138
 CERTIFICATE

This is to be certify that this Project Report entitled “HOSPITAL MANAGEMENT SYSTEM” which is

submitted by SANDHYA RAWAT (180942106138), in the partial fulfillment, for the award of degree of

Bachelor of Computer Application in Department of Computer Application, of FORTE INSTITUTE OF

TECHNOLOGY, Meerut, affiliated to CHAUDHARY CHARAN SINGH UNIVERSITY, MEERUT

(U.P.); is carried out by him/her under my supervision.

The matter embodied in this Project Work has not been submitted earlier for award of any degree or diploma in

any university/institution to the best of our knowledge and belief.

(Mr. Punit Kumar Sharma) (Mr. Rajiv Kumar) (Mrs. Shweta Batra)
Project Guide Head of the Department Director

Date: __/__/____
 ABSTRACT

The purpose of the project entitled as “HOSPITAL MANAGEMENT SYSTEM” is to computerize the Front

Office Management of Hospital to develop software which is user friendly simple, fast, and cost – effective. It

deals with the collection of patient’s information, diagnosis details, etc. Traditionally, it was done manually.

The main function of the system is register and store patient details and doctor details and retrieves these details

as and when required, and also to manipulate these details meaningfully System input contains patient details,

diagnosis details, while system output is to get these details on to the screen. The Hospital Management System

can be entered using a username and password. It is accessible either by an administrator or receptionist. Only

they can add data into the database. The data can be retrieved easily. The data are well protected for personal

use and makes the data processing very fast.

 INDEX

1. INTRODUCTION
1.1 Introduction

1.2 Problem introduction

1.3 Modules in the project

2. REQUIREMENTS SPECIFICATION
2.1 Introduction

2.2 Hardware requirements

2.3 Software requirements

3. ANALYSIS
3.1 Existing System

3.2 Proposed System

3.3 Feasibility study

3.4 Software specification

4. DESIGN
4.1 System Design

4.1.1 Introduction to UML

4.1.2 UML Diagrams of our project

5. SYSTEM IMPLEMENTATION
5.1 Introduction

5.2 Sample code

6. TESTING
 6.1 Introduction

6.2 testing methods

7. SAMPLE SCREENSHOTS

8. CONCLUSION

9. BIBLOGRAPHY
 CHAPTER 1
INTRODUCTION
The title of the project is “Hospital Management System”. Hospital Management System has most of the

facilities that a modern Hospital requires to computerize its day-to-day jobs. It provides facilities to keep the

records of Hospital, Doctors, Patient, fees, staff with all their required details along with all required transaction

handling. It has facilities to generate various types of reports, which are required by the management during

normal Hospital operations to operate the effectively.

This project is based on the RDBMS technology; the main objective of this project is to computerize the manual

system & reduce the time consumption. In other words we can say that our project has the following objectives:

 Make all the system computerize

 Reduce time consumption

 Reduce error scope

 All system managements are automated

 Centralized database management

 Easy operations for operator of the system

 No paper work requirement

1.1 Scope:

The different areas where we can use this application are:

 Any Hospital can make use of it for providing information about Doctor and Patient.
 It can be used in offices and modifications can be easily done according to requirements.
 Only admin can update, create, and delete the record of doctor and patient as per requirement.
 This application is used to convert the manual application to the online application.
 Customized data will be used in this application.
 User does not have right to enter information about Hospital.
1.2 Hardware and Software Requirements:

Hardware requirements:

 Pentium-II processor or above

 Processor Speed 533 MHZ
 Color monitor
 Keyboard
 10-GB Hard Disk Drive or above
 32 MB RAM or above

Software Requirements:

 Microsoft Windows-95 or above

 Java 6.0 or above
 Microsoft Access
 CHAPTER 2

MODULES AND THEIR DESCRIPTION

2.1Modules:

In this project, we divide overall program in five modules. These are as follows:

 Splash Form
 Login Form
 Main Form
 Application Form For Patient
 Application Form For Doctor
 Modification Form For Patient
 Modification Form For Doctors
 Report Form

2.2Modules Description:

2.1 Splash Form

 This is a first form that displays the welcome screen for the user and also shows the information of
developer or version etc.

2.2 Login Form

 This form shows the Login name and password when users enter a valid user name and password then
he/she can operate the application.

2.3Main Form

 This form is a menu-based form that displays the menu for operation of the application. It includes
various options for Hospital staff, fees and report related option.

2.4 Application Form (both Doctors and Patient)

 This form provides the option to insert all the details of the Hospital at the administrator side.
2.5 Administrator Form

 This form provides the option to add, delete, search and delete the information of staff that is working in
the Hospital.

2.6 Billing Form (not provide the write access to the Staff)

 This form provides the option to the user of the system to add, delete, modify and search the information
of the fee deposited by the Patient.

2.7 Report Form

 With the help of this option from menu user of the system can see or take the print out of various reports
provided by the system.
 CHAPTER 3

Problem Analysis
One of the most difficult tasks of system analysis is developing a clear, in-depth understanding of the problem
being investigated, without which it becomes impossible to specify the requirements for a new project with any
accuracy. Several questions should be posed for this. Some of those may be:

 What is the problem?

 How complex is it?
 What are its likely causes?
 Why is it important that the problem be solved?
 What are possible solutions to the problem?
 What types of benefits can be expected once the problem is solved?

It takes considerable skill to determine the true cause of a system problem. A systems analyst might begin to
define the problem by determining if the problem can be classified ac-cording to one or more common types of
systems problems. With knowledge of the common types of systems problems, the analyst can diagnose a
problem by examining its characteristics.

Organizations usually face problems or have opportunity due to the following facts:

 A new product or plant or branch

 A new market or new process
 Failure of an existing system
 Inefficiency of an existing system
 Structural error in the existing system etc

For identifying problems/opportunities, we scan the following:

 The performance of the system

 The information being supplied and its form
 The economy of processing
 The control of the information processing
 The efficiency of the existing system
 The security of the data and software
 The security of the equipment and personnel etc
After identification of the problem, it is defined and a general direction or method for solving this problem is
also determined. The management establishes the term of reference as well as the resources to be provided for
the project. System development is an iterative process and the first identifiable stage of it is problem definition,
whose final output is terms of reference.

Careful analysis of this system suggests a number of different problems:

1. Problem of reliability: Current system is not reliable. It seems to vary in quality and result from
one month to the next. Some items it gives good output, but sometimes the output is worst.
2. Problem of accuracy: There are too many mistakes in reports and calculations.

3. Problem of timeliness: In the current system the reports and output produced is mostly late and in
most of the cases it is useless because it is not on time.
4. Problem of validity: The output and reports mostly contains misleading information. The
transactions and calculations are sometimes not valid.
5. Problem of economy: The current system is very costly. We have to spend lots of money in manual
filing, calculations and remembering the information, but still not get the desired results.
6. Problem of capacity: The current system is suffering from problem of capacity also. The workload
is too much. Few peoples cannot handle all the working.
 CHAPTER 4

FEASIBILITY STUDY
4.1 Steps in feasibility analysis:

Eight steps involved in the feasibility analysis are:

1. From a project team and appoint a project leader.

2. Prepare system flowcharts.
3. Enumerate potential proposed systems.
4. Define and identify characteristics of proposed system.
5. Determine and evaluate performance and cost effectiveness of each proposed system.
6. Weight system performance and cost data.
7. Select the best proposed system.
8. Prepare and report final project directive to management.

4.2 Type of feasibilities:

4.2.1 Economic Feasibility:

Economic analysis is the most frequently used technique for calculating the effectiveness of a proposed system.
More commonly known as cost/benefit analysis; in this procedure we determine the benefits and savings that
are expected from a proposed system and compare them with costs. We found the benefits outweigh the costs;
we take a decision to design and implement the new proposed system.

4.2.2 Technical Feasibility:

This is concerned with specifying equipment and software that will successfully satisfy the user requirement.
The technical needed of the system may vary considerable, but might include:

 The facility to produce outputs in a given time.

 Response time under certain conditions.
 Ability to process a certain volume of transaction at a particular speed.
 Facility to communicate data to distant location.
After examining technical feasibility, we give more importance to the configuration of the system then the
actual make of hardware. The configuration gives the complete picture about the system’s requirements.

Ten to twelve workstations are required, these units should be interconnected through LAN so that could
operate and communicate smoothly. They should have enough speeds of input and output to achieve a particular
quality of printing.

4.2.3 Operational Feasibility:

It is mainly related to human organizational and political aspects. The points to be considered are:

 What changes will be brought with the system?

 What organizational structures are disturbed?
 What news skills will required?
 Do the existing staff members have these skills?
 If not, can they be trained in due course of time?

Generally project will not be rejected simply because of operational infeasibility but such considerations are
likely to critically affect the nature and scope of the eventual recommendations.

For operational feasibility study we appointed a small group of people who are familiar with information system
techniques, who understand the of the business that are relevant to the project and skilled in system analysis and
design process.

4.2.4 Social Feasibility:

Social feasibility is a determination of whether a proposed project will be acceptable to the people or not. This
determination typically examines the probability of the project being accepted by the group directly affected by
the proposed system change.

4.2.5 Management Feasibility:

It is a determination of whether a proposed project will be acceptable to management. If management does not
accept a project or gives a negligible support to it, the analyst will tend to view the project as a non-feasible one.

4.2.6 Legal Feasibility:

Legal feasibility is a determination of whether a proposed project infringes on known Acts, Statutes, as well as
any pending legislation. Although in some instances the project might appear sound, on closer investigation it
may be found to infringe on several legal areas.

4.2.7 Time Feasibility:

Time feasibility is a determination of whether a proposed project can be implemented fully within a stipulated
time frame. If a project takes too much time it is likely to be rejected.
 CHAPTER 5

SYSTEM ANALYSIS
System analysis and design refers to the process of examining a business situation with the intent of improving
it through better procedures and methods. Systems development can generally be through of having two major
components: System Analysis and System Design. System design is the process of planning a new system or
replace or complement an existing system. But before this planning can be done, we must thoroughly
understand the existing system and determine how computers can best be used to make its operation more
effective. System analysis, then, is the process of gathering and interpreting facts, diagnosing problems and
using the information to recommend improvement to the system. In brief, we can say that analysis specifies
what the system should do. Design states hew to accomplish the objective.

In this project we have used Rapid Application Development (RAD) model; RAD is an incremental software
development process model that emphasizes an extremely short development cycle. The following phases are
encompassed:

Business modeling: All the information about the business functioning of the gateway development is
collected, how the data and information is flow from one end to another end using the following questions:
What information drives the department process? What information is generated? Who generates it? Where
does the information go? Who process it?

Data modeling: The information collected in business modeling phase is refined into a set of data objects
that are needed to support the project. The attributes of each object are identified and the relationship between
these objects defined.

Process modeling: Processing descriptions and functions like adding, modifying, deleting student records,
assigning marks, generating mark sheet, printing reports, providing information, file handling etc. are created.

Application generation: The fourth generation techniques are used to generate application, like reusing the
predefined functions or creating reusable components.

Testing: Most of the functions are already tested, as they are predefined functions. However, new components
or functions are also tested after application generation.
 CHAPTER 6

SYSTEM DESIGN
6.1 Introduction:

The system objectives outlined during the feasibility study serve as the basis from which the work of the system
design is initiated. Much of the activities involved at this stage is of technical nature requiring a certain degree
of experience in designing systems, sound knowledge of computer related technology and through
understanding of computers available in the market and the various facilities provided by the vendors.
Nevertheless, a system cannot be designed in isolation without the active involvement of the user. The user has
a vital role to play at this stage too. As we know that data collected during feasibility study will be utilized
systematically during the system design. It should, however, be kept in mind that detailed study of existing the
system is not necessarily over with the completion of the feasibility study. Depending on the plan of feasibility
study, the level of detailed study will vary and the system design stage will also vary in the amount of
investigation that still needs to be done. This investigation is generally an urgent activity during the system
design as the designer needs to study minute’s details in all aspects of the system. Sometimes, but rarely, this
investigation may from a separate stage between feasibility study and computer system design. Designing a new
system is a creative process, which calls for logical as well as lateral thinking. The logical approach involves
systematic moves towards the end product keeping in mind the capabilities of the personnel and the equipment
at each decision making step. Lateral thought implies encompassing of ideas beyond the usual functions and
equipment. This is to ensure that no efforts are being made to fit previous solutions into new situations.

6.2 System Design Considerations:

The system design process is not a step-by-step adherence of clear procedures and guidelines. Though, certain
clear procedures and guidelines have emerged in recent days, but still much of design work depends on
knowledge and experience of the designer.

When designer starts working on system design, he will face different type of problems. Many of these will be
due to constraints imposed by the user or limitations of the hardware and software available in the market.
Sometimes, it is difficult to enumerate the complexity of the problems and solutions thereof since the variety of
likely problems is so great and no solutions are exactly similar. However, following considerations should be
kept in mind during the system–designing phase:

The primary objective of the design: Of course, is to deliver the requirements as specified in the feasibility
report. In general, the following design objectives should be kept in mind:
a. Practicality: The system must be stable and can be operated by people with average +.

b. Efficiency: This involves accuracy, timeliness and comprehensiveness of the system output.

c. Cost: It is desirable to aim for a system with a minimum cost subject to the condition that it must satisfy all
the requirements.

d. Flexibility: The system should be modifiable depending on the changing needs of the user. Such
modifications should not be entail extensive reconstructing or recreation of software. It should also be portable
to different computer systems.

e. Security: This is very important aspect of the design and should cover areas of hardware reliability, fall
back procedures, physical security of data and provision for detection of fraud and abuse.

System design involves first logical design and then physical construction of the system. The logical design
describes the structure and characteristics of features, like the outputs, inputs, files, databases and procedures.
The physical construction, which follows the logical design, produces actual program software, files and a
working system.

6.3 The designer constraints:

6.3.1 Hardware: The existing hardware will obviously affect the system design.

6.3.2 Software: The available software (operating system, utilities, language etc.) in the market will
constraint the design.

6.3.3 Budget: The budget allocated for the project will affect the scope and depth of design.

6.3.4 Time-scale: The new system may be required by a particular time (e.g. the start of a financial
year).This may put a constraint on the designer to find the best design.

6.3.5 Interface with other systems: The new system may required some data from another computerized
system or may provide data to another system in which case the files must be compatible in format and the
system must operate with a certain processing cycle.

6.4 Processing Techniques:

The options available to the designer are:

 Batch processing
  Real-time processing
 Online processing
 A combination of all the above

You are already aware of these techniques. It is quite interesting to note, however that a combination of these is
often found to be ideal in traditional data processing applications. This increases throughput of the system as
also brings down the response time of on-line activities. In most of die business applications, 24-hour data is
acceptable enough and hence it is possible to update voluminous data after office-hours in batch mode.

6.5 Design Methodologies:

The scope of the system design is guided by the framework for the new system developed during analysis. More
clearly defined logical method for developing system that meets user requirements has led to new techniques
and methodologies that fundamentally attempt to do the following:

 Improve productivity of analysts and programmers.

 Improve documentation and subsequent maintenance and enhancements.
 Cut down drastically on cost overruns and delays.
 Improve communication among the user, analyst designer, and programmer.
 Standardize the approach to analysis and design.
 Simplify design by segmentation.
 CHAPTER 7

STRUCTURE DESIGN
7.1 Introduction:

Structure design is a data flow based methodology. The approach begins with a system specification that
identifies inputs and outputs and describes the functional aspects of the system. The specifications then are used
as a basis for the graphics representation. The step is the definition of the modules and their relationship to one
another in a form called a structure chart, using a data dictionary and other structure tools.

Logical design proceeds from the top down. General features such as reports and inputs are identified first.
Then each is satisfied individually and in more detail. Hence, the structure design partitions a program into
small, independent modules. They are arranged in a hierarchy that approximates a model of the business area
and is organized in a top-down manner. Thus, structured design is an attempt to minimize the complexity and
make a problem manageable by subdividing it into smaller segments which is called modularization or
decomposition. In this way, structuring minimizes intuitive reasoning and promotes maintainable provable
systems.

A design is said to be top-down if it consists of a hierarchy of modules. with each module having a single entry
and a single exit subroutine. The primary advantages of this design are as follows:

 Critical interfaces are tested first.

 Early versions of the design, through incomplete, are useful enough to resemble the real system.
 Structuring the design, parse, provides control and improves morale.
 The procedural characteristics define the order that determines processing.

7.2 Major System Design Activities:

Several development activities are carried out during structured design. They are data base design,
implementation planning, system test preparation, system interface specification, and user documentation.

a. Data base design: This activity deals with the design of the physical database. A key is to determine how
the access paths art to be implemented.

b. Program design: In conjunction with database design is a decision on the programming language to be
used and the flowcharting, coding, and debugging procedure prior to conversion. The operating system limits
the programming languages that will run of the system.
c. System and program test preparation: Each aspect of the system has a separate test requirement.
System testing is done after all programming and testing completed. The test cases cover every aspect of the
proposed system, actual operations, and user interface and so on. System program test requirements become a
part of design specification–a pre requisite to implementation.

In contrast to the system testing is acceptance testing. Which puts the system through a procedure design to
convince the user that the proposed system will meet the started and requirements. Acceptance testing is
technically similar to system testing but politically it is different. Acceptance testing is conducted in the
presence of the user, audit representatives, or the entire staff.

CHAPTER 8
 PROCESS MODELING
8.1 Data Flow Diagram:

Graphical description of a system`s data and how the processes transform the data is known as Data Flow
Diagram (or DFD).

Unlike detail flowcharts. DFDs do not supply detailed descriptions of modules but graphically describe a
system`s data and how the data interact with the system.

To construct data flow diagrams, we use:

 Arrows
 Circles
 Open–ended boxes
 Squares

An arrow identifies data flow–data in motion. It is a pipeline through which information flows. Like the
rectangle in flowcharts, circles stand for a process that converts data/into in–formation. An open–ended box
represents a data store data at rest, or a temporary repository of data. A square defines a source (originator) or
destination of system data.

The following seven rules govern construction of data flow diagrams (DFD).

 Arrows should not cross each other.

 Squares, circles, and files must bear names.
 Decomposed data flows must be balanced (all data flows on the decomposed diagram must reflect flows
in the original diagram).
 No two data flows, squares, or circles can have the same name.
 Draw all data flows around the outside of the diagram.
 Choose meaningful names for data flows, processes, and data stores.
 Use strong verbs followed by nouns.
 Control information such as record counts, passwords, and validation requirements are not pertinent to a
data-flow diagram.

If too many events seem to be occurring at a given point, an analyst can decompose a data conversion (circle).
The new data conversions from a parent-child relationship with the original data conversion : the child circle.
Fig.8.1: Level 0 DFD for Hospital Management System

Fig.8.2: Level 1 DFD for Hospital Management System

 Login

Admin User

Add New Account Only View All

Records

Delete Record Create Login ID

or Password
Modify Record

View All Transaction

Fig. 8.3: DFD for Login Process

Fig. 8.4 DFD for Admin Process

8.2 Entity-Relationship Diagram:

 Fig.8.5: Doctor and Patient attributes

Fig. 8.6: Administrator attributes

 Fig.8.7: Relationship between admin and user

8.3 Coding:

importjava.awt.*;
importjava.awt.event.*;
importjavax.swing.*;
class login implements ActionListener
{
JFramefr;
JLabel l1,l2,l3,l4,l5,limg;
JPanel panel;
Choice chrt;
JButton b1,b2;
JTextField t1,t2,t3;
JPasswordFieldpf;
ImageIconig,fimg;
public static void main(String[] args)
{
new login();
}
public login()
{
fr = new JFrame("Login SMS");
fr.setLayout(null);
fimg = new ImageIcon("c:\\stdmgtsys\\images\\student.png");
fr.setIconImage(fimg.getImage());
limg = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\login\\login22.jpg"));
fr.setContentPane(limg);
l1 = new JLabel("User Name");
l2 = new JLabel("Password");
l1.setForeground(Color.white);
l2.setForeground(Color.white);
ig = new ImageIcon("c:\\stdmgtsys\\images\\student.png");
l5 = new JLabel(ig);
l1.setBounds(130,180,80,30);
l2.setBounds(130,220,100,30);
l5.setBounds(5,5,150,150);
fr.add(l1);
fr.add(l2);
fr.add(l5);
chrt=new Choice();
chrt.setBounds(215,180,150,30);
chrt.addItem("Admin");
chrt.addItem("Student");
fr.add(chrt);
pf = new JPasswordField();
pf.setBounds(215,220,150,30);
fr.add(pf);
b1 = new JButton("Login");
b1.setBounds(155,285,80,35);
b1.setBackground(Color.white);
b1.setForeground(Color.black);
b1.addActionListener(this);
fr.add(b1);
b2 = new JButton("Cancel");
b2.setBounds(260,285,80,35);
b2.setBackground(Color.white);
b2.setForeground(Color.black);
b2.addActionListener(this);
fr.add(b2);
Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize();
int height = screenSize.height;
int width = screenSize.width;
fr.setUndecorated(true);
//fr.getRootPane().setWindowDecorationStyle(JRootPane.PLAIN_DIALOG);
//fr.getContentPane().add(new JPanel());
fr.setResizable(false);
fr.setBounds((width-500)/2,(height-500)/2,500,500);
fr.setVisible(true);
fr.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
}
public void actionPerformed(ActionEventae)
{
if(ae.getSource()==b1)
{
String user,pass;
user=chrt.getSelectedItem();
pass=pf.getText();
if(pass.equals("student") &&user.equals("Student") )
{
newsearchlogin();
//setvisible(false);
fr.dispose();
}
if(pass.equals("Admin") &&user.equals("Admin") )
{
newawelcome();
//setvisible(false);
fr.dispose();
}
/*else{
JOptionPane.showMessageDialog(null,"Invaild User name and password");
pf.setText("");
}*/
}
 if(ae.getSource()==b2)
{
fr.dispose();
}
}
}
//***********************//

importjava.awt.*;
importjava.awt.event.*;
importjavax.swing.*;
importjava.sql.*;
classsearchlogin implements ActionListener
{
public static String sid;
JFramefr;
JLabel l1,limg;
JButton b1,b2;
publicsearchlogin()
{
fr = new JFrame("SEARCH RECORDS");
fr.getContentPane().setBackground(Color.pink);
fr.setSize(400,300);
fr.setLayout(null);
limg = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\login\\login1.jpg"));
fr.setContentPane(limg);
l1 = new JLabel("ARE YOU REGISTERED USER ?");
l1.setFont(new Font("comic sans ms",Font.BOLD,22));
l1.setForeground(Color.blue);
l1.setBounds(30,90,350,30);
 fr.add(l1);
b1 = new JButton("YES");
b1.setBounds(90,180,100,30);
b1.addActionListener(this);
b2 = new JButton("NO");
b2.setBounds(200,180,100,30);
b2.addActionListener(this);
fr.add(b1);
fr.add(b2);
Dimension screen = Toolkit.getDefaultToolkit().getScreenSize();
fr.setLocation((screen.width - 500)/2,((screen.height-350)/2));
fr.setUndecorated(true);
fr.setVisible(true);
fr.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
}
public void actionPerformed(ActionEventae)
{
if(ae.getSource()==b1)
{
newuserlogin();
fr.dispose();
}
if(ae.getSource()==b2)
{
new register();
fr.dispose();
}
}
public static void main(String args[])
{
 newsearchlogin();
}
}
//*********************************//
importjava.awt.*;
importjava.awt.event.*;
importjavax.swing.*;
classawelcome implements ActionListener
{
JFramefr;
JLabel l1,limg,l2,l3;
JButton b1,b2;
publicawelcome()
{
fr = new JFrame();
//fr.getContentPane().setBackground(Color.pink);
fr.setSize(400,300);
fr.setLayout(null);
limg = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\back\\smile2.jpg"));
fr.setContentPane(limg);
l1 = new JLabel(" WELCOME ");
l1.setFont(new Font("comic sans ms",Font.BOLD,30));
l1.setForeground(Color.yellow);
l1.setBounds(110,130,250,40);
fr.add(l1);
b1 = new JButton(" OK ");
b1.setBounds(150,230,100,30);
b1.setBackground(Color.yellow);
b1.addActionListener(this);
fr.add(b1);
 Dimension screen = Toolkit.getDefaultToolkit().getScreenSize();
fr.setLocation((screen.width - 500)/2,((screen.height-350)/2));
fr.setUndecorated(true);
fr.setVisible(true);
fr.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
}
public void actionPerformed(ActionEventae)
{
if(ae.getSource()==b1)
{
newmainform();
fr.dispose();
}
}
public static void main(String args[])
{
newawelcome();
}
}
//********************************************//
importjava.awt.*;
importjava.awt.event.*;
importjavax.swing.*;
importjava.sql.*;
classuserlogin implements ActionListener
{
Connection con = null;
Statement stmt = null;
ResultSetrs = null;
JFramefr;
JLabel l1,limg,l2,l3;
JTextField t1,t2;
JPasswordField t3;
JButton b1,b2;
static String name;
publicuserlogin()
{
fr = new JFrame("REGISTER USER LOGIN");
fr.getContentPane().setBackground(Color.pink);
fr.setSize(400,300);
fr.setLayout(null);
limg = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\login\\login1.jpg"));
fr.setContentPane(limg);
t1 = new JTextField();
t1.setBounds(200,70,150,30);
l1 = new JLabel("USER NAME ");
l1.setFont(new Font("comic sans ms",Font.BOLD,18));
l1.setForeground(Color.blue);
l1.setBounds(40,70,150,30);
fr.add(l1);
l2 = new JLabel("Enter ID ");
l2.setFont(new Font("comic sans ms",Font.BOLD,18));
l2.setForeground(Color.blue);
l2.setBounds(40,120,150,30);
fr.add(l2);
t2 = new JTextField();
t2.setBounds(200,120,150,30);
fr.add(t2);
l3 = new JLabel("PASSWORD ");
l3.setFont(new Font("comic sans ms",Font.BOLD,18));
 l3.setForeground(Color.blue);
l3.setBounds(40,170,150,30);
fr.add(l3);
t3 = new JPasswordField();
t3.setBounds(200,170,150,30);
fr.add(t3);
b1 = new JButton("LOGIN");
b1.setBounds(90,230,100,30);
b1.addActionListener(this);
b2 = new JButton("CANCLE");
b2.setBounds(200,230,100,30);
b2.addActionListener(this);
fr.add(b1);
fr.add(t1);
fr.add(b2);
Dimension screen = Toolkit.getDefaultToolkit().getScreenSize();
fr.setLocation((screen.width - 500)/2,((screen.height-350)/2));
fr.setUndecorated(true);
fr.setVisible(true);
fr.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
}
public void actionPerformed(ActionEventae)
{
if(ae.getSource()==b1)
{
String s1 = t2.getText();
String s2 = t1.getText();
String s3 = t3.getText();
String s4,s5;
name = s2;
 try
{
makeconnection();
stmt = con.createStatement();
rs = stmt.executeQuery("select Name,Password1 from record where id="+s1);
rs.next();
s4 = rs.getString("Name");
s5 = rs.getString("Password1");
if(s4.equals(s2) && s5.equals(s3))
{
newswelcome();
//new mainform();
fr.dispose();
}
con.close();
}
catch(Exception e)
{
System.out.println("error"+e);
}
}
if(ae.getSource()==b2)
{
//new mainform();
fr.dispose();
}
}
public void makeconnection()
{
try
 {
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
con = DriverManager.getConnection("JDBC:ODBC:Driver={Microsoft Access Driver (*.mdb,
*.accdb)};DBQ=c:\\stdmgtsys\\source code\\database\\login.accdb");
System.out.println("Connection established...");
}
catch(Exception e)
{
System.out.println("Connection not established...");
}
}
public static void main(String args[])
{
newuserlogin();
}
}
//********************************************//
importjava.awt.*;
importjava.awt.event.*;
importjavax.swing.*;
classswelcome extends userlogin implements ActionListener
{
JFramefr;
JLabel l1,limg,l2,l3;
JButton b1,b2;
publicswelcome()
{
fr = new JFrame();
fr.getContentPane().setBackground(Color.yellow);
fr.setSize(400,300);
fr.setLayout(null);
 limg = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\back\\smile1.jpg"));
fr.setContentPane(limg);
l1 = new JLabel(" WELCOME ");
l1.setFont(new Font("comic sans ms",Font.BOLD,30));
l1.setForeground(Color.black);
l1.setBounds(110,130,250,40);
fr.add(l1);
l2 = new JLabel( name );
l2.setFont(new Font("comic sans ms",Font.BOLD,20));
l2.setForeground(Color.red);
l2.setBounds(160,180,250,30);
fr.add(l2);
b1 = new JButton(" OK ");
b1.setBounds(150,230,100,30);
b1.setBackground(Color.yellow);
b1.addActionListener(this);
fr.add(b1);
Dimension screen = Toolkit.getDefaultToolkit().getScreenSize();
fr.setLocation((screen.width - 500)/2,((screen.height-350)/2));
fr.setUndecorated(true);
fr.setVisible(true);
fr.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
}
public void actionPerformed(ActionEventae)
{
if(ae.getSource()==b1)
{
newmainform();
fr.dispose();
}
 }
public static void main(String args[])
{
newswelcome();
}
}
//**********************************************//
importjava.awt.*;
importjava.awt.event.*;
importjavax.swing.*;
importjava.sql.*;
class register implements ActionListener
{
public static String sid;
JFramefr;
JLabel l1,limg,l2;
JTextField t1,t2,t3;
JButton b1,b2;
public register()
{
fr = new JFrame("REGISTER NEW USER LOGIN");
fr.getContentPane().setBackground(Color.pink);
fr.setSize(400,300);
fr.setLayout(null);
limg = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\login\\login1.jpg"));
fr.setContentPane(limg);
l1 = new JLabel("DO YOU WANT TO CREATE NEW");
l2 = new JLabel(" REGISTRATION ? ");
l1.setFont(new Font("comic sans ms",Font.BOLD,18));
l1.setForeground(Color.blue);
 l1.setBounds(40,100,350,30);
fr.add(l1);
l2.setFont(new Font("comic sans ms",Font.BOLD,18));
l2.setForeground(Color.blue);
l2.setBounds(40,140,350,30);
fr.add(l2);
b1 = new JButton("YES");
b1.setBounds(90,205,100,30);
b1.addActionListener(this);
b2 = new JButton("NO");
b2.setBounds(200,205,100,30);
b2.addActionListener(this);

fr.add(b1);
fr.add(b2);
Dimension screen = Toolkit.getDefaultToolkit().getScreenSize();
fr.setLocation((screen.width - 500)/2,((screen.height-350)/2));
fr.setUndecorated(true);
fr.setVisible(true);
fr.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
}
public void actionPerformed(ActionEventae)
{
if(ae.getSource()==b1)
{
newloginregister();
fr.dispose();
}
if(ae.getSource()==b2)
{
 newsearchlogin();
fr.setVisible(false);
}
}
public static void main(String args[])
{
new register();
}
}
//************************************************//
importjava.awt.*;
importjava.awt.event.*;
importjavax.swing.*;
importjava.sql.*;
classloginregister implements ActionListener
{
Connection con = null;
Statement stmt = null;
ResultSetrs = null;
String str[]={"Student ID","UserName","Father'sName","Class/Branch","ContactNo","Date Of
Birth","Emailid","Password","Retype Password"};
JFramefr;
JLabellb[],limg;
JTextFieldtxt1[];
JPasswordField t1,t2;
staticint y1=130,y2=130,y3=100;
JButton b1,b2,b3;
JLabel l1;
publicloginregister()
{
fr = new JFrame("NEW USER REGISTRATION");
//fr.getContentPane().setBackground(Color.pink);
fr.setSize(1366,768);
fr.setLayout(null);
limg = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\back\\wood9.jpg"));
fr.setContentPane(limg);
lb = new JLabel[str.length];
for(int i=0 ; i<9 ; i++)
{
lb[i] = new JLabel(str[i]);
lb[i].setBounds(150,y1,160,30);
lb[i].setForeground(Color.red);
y1=y1+50;
fr.add(lb[i]);
lb[i].setFont(new Font("lucida console",Font.BOLD,18));
}
txt1 = new JTextField[7];
for(int i=0 ; i<7 ; i++)
{
txt1[i] = new JTextField();
txt1[i].setBounds(340,y2,180,30);
y2=y2+50;
fr.add(txt1[i]);
txt1[i].setFont(new Font("lucida console",Font.BOLD,16));
}
t1 = new JPasswordField();
t1.setBounds(340,y2,180,30);
y2=y2+50;
fr.add(t1);
t2 = new JPasswordField();
t2.setBounds(340,y2,180,30);
 y2=y2+50;
fr.add(t2);
b1 = new JButton("SUBMIT");
b1.setBounds(305,630,105,30);
b1.addActionListener(this);
fr.add(b1);
b2 = new JButton("Login");
b2.setBounds(420,630,105,30);
b2.addActionListener(this);
fr.add(b2);
fr.setVisible(true);
fr.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
}
public void actionPerformed(ActionEventae)
{
if(ae.getSource()==b1)
{
String s1 = txt1[0].getText();
String s2 = txt1[1].getText();
String s3 = txt1[2].getText();
String s4 = txt1[3].getText();
String s5 = txt1[4].getText();
String s6 = txt1[5].getText();
String s7 = txt1[6].getText();
String s8 = t1.getText();
String s9 = t2.getText();
String s10;
/*try
{
makeconnection1();
 stmt = con.createStatement();
rs = stmt.executeQuery("select name from record where id="+s1);
rs.next();
System.out.println(rs.getString("name"));
con.close();
}
catch(Exception e)
{
System.out.println("error"+e);
}*/
try
{
makeconnection();
if(s8.equals(s9))
{
stmt = con.createStatement();
System.out.println("i m here");
String str ="insert into record values(" + s1 + ",'" + s2 + "','" + s3 +"','" + s4 + "','" + s5 +
"','" + s6 + "','" + s7 + "','" + s8 + "','" + s9 + "')";
System.out.println("i m here"+str);
stmt.executeUpdate(str);
System.out.println("i m here");
newSuccessDialog();
}
else
{
JOptionPane.showMessageDialog(null, "Please re enter Password", "Done!",
JOptionPane.INFORMATION_MESSAGE);
}
con.close();
}
 catch(Exception e)
{
System.out.println("Error in Inserting Record...."+e);
}
}
if(ae.getSource()==b2)
{
newuserlogin();
fr.dispose();
}
}
public void makeconnection()
{
try
{
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
con = DriverManager.getConnection("JDBC:ODBC:Driver={Microsoft Access Driver (*.mdb,
*.accdb)};DBQ=c:\\stdmgtsys\\source code\\database\\login.accdb");
System.out.println("Connection established...");
}
catch(Exception e)
{
System.out.println("Connection not established...");
}
}
/*public void makeconnection1()
{
try
{
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
con = DriverManager.getConnection("JDBC:ODBC:Driver={Microsoft Access Driver (*.mdb,
*.accdb)};DBQ=c:\\stdmgtsys\\source code\\database\\student.accdb");
System.out.println("Connection established...");
}
catch(Exception e)
{
System.out.println("Connection not established...");
}
}*/
public static void main(String args[])
{
newloginregister();
}
}
//************************************************//
importjavax.swing.JFrame;
importjavax.swing.JOptionPane;
public class SuccessDialog
{
SuccessDialog()
{
String message = "Data added successfully!";
JOptionPane.showMessageDialog(new JFrame(), message, "Done!",
JOptionPane.INFORMATION_MESSAGE);
}
public static void main(String argv[])
{
newSuccessDialog();
}
}
//************************************************//
importjava.awt.*;
importjava.awt.event.*;
importjavax.swing.*;
importjava.sql.*;
classsearchlogin implements ActionListener
{
public static String sid;
JFramefr;
JLabel l1,limg;
JButton b1,b2;
publicsearchlogin()
{
fr = new JFrame("SEARCH RECORDS");
fr.getContentPane().setBackground(Color.pink);
fr.setSize(400,300);
fr.setLayout(null);
limg = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\login\\login1.jpg"));
fr.setContentPane(limg);
l1 = new JLabel("ARE YOU REGISTERED USER ?");
l1.setFont(new Font("comic sans ms",Font.BOLD,22));
l1.setForeground(Color.blue);
l1.setBounds(30,90,350,30);
fr.add(l1);
b1 = new JButton("YES");
b1.setBounds(90,180,100,30);
b1.addActionListener(this);
b2 = new JButton("NO");
b2.setBounds(200,180,100,30);
b2.addActionListener(this);
fr.add(b1);
 fr.add(b2);
Dimension screen = Toolkit.getDefaultToolkit().getScreenSize();
fr.setLocation((screen.width - 500)/2,((screen.height-350)/2));
fr.setUndecorated(true);
fr.setVisible(true);
fr.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
}
public void actionPerformed(ActionEventae)
{
if(ae.getSource()==b1)
{
newuserlogin();
fr.dispose();
}
if(ae.getSource()==b2)
{
new register();
fr.dispose();
}
}
public static void main(String args[])
{
newsearchlogin();
}
}
//***************************************************//
importjava.awt.*;
importjavax.swing.*;
importjava.awt.event.*;
classmainform extends Thread implements ActionListener
{
//Thread th;
JFramefr;
JMenuBarmb;
JMenu op;
JMenuItemar,dr,sr,mr,dsr,ext,fee,mar;
JPopupMenu pm;
JMenu op1,op2;
JMenuItem ar1,dr1,sr1,mr1,dsr1,ext1,m1,m2,m3,m4,m5,m6;
ImageIcon fimg,img1,img2,img3,img4,img5,img6;
JLabel limg,limg1,l1;
JToolBartoolBar;
JButton btn1,btn2,btn3,btn4,btn5,btn6;
intwidth,height;
staticintfx=1,fy=50,x=10,z=0;
publicmainform()
{
fr = new JFrame("Student Management System Ver(1.0)");
fr.setBackground(Color.black);
limg = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\back\\student.jpg"));
fr.setContentPane(limg);
String str="Student Management System";
l1 = new JLabel(str);
l1.setVisible(true);
l1.setFont(new Font("Times New Roman",Font.BOLD,80));
l1.setForeground(Color.red);
l1.setBounds(fx,fy,1050,85);
fr.add(l1);
if(z==0)
{
 start();
z=1;
}
Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize();
height = screenSize.height;
width = screenSize.width;
fr.setBounds(0,0,width,height);
mb = new JMenuBar();
mb.setBackground(Color.red);
op = new JMenu("Operations");
op.setFont(new Font("comic sans ms",Font.BOLD,18));
op.setMnemonic('O');
img1 = new ImageIcon("c:/stdmgtsys/images/save.png");
ar = new JMenuItem(" Insert Record");
ar.setIcon(img1);
ar.setFont(new Font("comic sans ms",Font.BOLD,18));
ar.setAccelerator(KeyStroke.getKeyStroke(KeyEvent.VK_I, Event.CTRL_MASK));
ar.setMnemonic((int)'I');
ar.addActionListener(this);
img2 = new ImageIcon("c:/stdmgtsys/images/delete.png");
dr = new JMenuItem(" Remove Record");
dr.setIcon(img2);
dr.setFont(new Font("comic sans ms",Font.BOLD,18));
dr.setAccelerator(KeyStroke.getKeyStroke(KeyEvent.VK_R,Event.CTRL_MASK));
dr.setMnemonic((int)'R');
dr.addActionListener(this);
img3 = new ImageIcon("c:/stdmgtsys/images/search3.png");
sr = new JMenuItem(" Search Record");
sr.setIcon(img3);
sr.setFont(new Font("comic sans ms",Font.BOLD,18));
sr.setAccelerator(KeyStroke.getKeyStroke(KeyEvent.VK_S,Event.CTRL_MASK));
sr.setMnemonic((int)'S');
sr.addActionListener(this);
img4 = new ImageIcon("c:/stdmgtsys/images/modify1.png");
mr = new JMenuItem(" Modify Record");
mr.setIcon(img4);
mr.setFont(new Font("comic sans ms",Font.BOLD,18));
mr.setAccelerator(KeyStroke.getKeyStroke(KeyEvent.VK_M,Event.CTRL_MASK));
mr.setMnemonic((int)'M');
img5 = new ImageIcon("c:/stdmgtsys/images/monitor2.png");
dsr = new JMenuItem(" Marks Record ");
dsr.setIcon(img5);
dsr.setFont(new Font("comic sans ms",Font.BOLD,18));
dsr.setAccelerator(KeyStroke.getKeyStroke(KeyEvent.VK_D,Event.CTRL_MASK));
dsr.setMnemonic((int)'D');
img6 = new ImageIcon("c:/stdmgtsys/images/close.png");
ext = new JMenuItem(" Quit SMS ");
ext.setIcon(img6);
ext.setFont(new Font("comic sans ms",Font.BOLD,18));
ext.setAccelerator(KeyStroke.getKeyStroke(KeyEvent.VK_Q,Event.CTRL_MASK));
ext.setMnemonic((int)'Q');
op.add(ar);
op.addSeparator();
op.add(dr);
op.addSeparator();
op.add(sr);
op.addSeparator();
op.add(mr);
op.addSeparator();
op.add(dsr);
op.addSeparator();
op.add(ext);
mb.add(op);
fr.setJMenuBar(mb);
pm = new JPopupMenu();
op1 = new JMenu("Operations ");
op1.setFont(new Font("comic sans ms",Font.BOLD,14));
ar1 = new JMenuItem(" Add New Record");
ar1.setIcon(img1);
ar1.setFont(new Font("comic sans ms",Font.BOLD,14));
dr1 = new JMenuItem(" Remove Record");
dr1.setIcon(img2);
dr1.setFont(new Font("comic sans ms",Font.BOLD,14));
sr1 = new JMenuItem(" Search Record");
sr1.setIcon(img3);
sr1.setFont(new Font("comic sans ms",Font.BOLD,14));
mr1 = new JMenuItem(" Modify Record");
mr1.setIcon(img4);
mr1.setFont(new Font("comic sans ms",Font.BOLD,14));
dsr1 = new JMenuItem(" Marks Record ");
dsr1.setIcon(img5);
dsr1.setFont(new Font("comic sans ms",Font.BOLD,14));
ext1 = new JMenuItem(" Exit ");
ext1.setIcon(img6);
ext1.setFont(new Font("comic sans ms",Font.BOLD,14));
ar1.addActionListener(this);
dr1.addActionListener(this);
sr1.addActionListener(this);
mr1.addActionListener(this);
dsr1.addActionListener(this);
ext1.addActionListener(this);
op1.add(ar1);
op1.add(dr1);
op1.add(sr1);
op1.add(mr1);
op1.add(dsr1);
op1.add(ext1);
op2 = new JMenu("Change Background ");
op2.setFont(new Font("comic sans ms",Font.BOLD,14));
m1 = new JMenuItem(" Cobra Skin");
m2 = new JMenuItem(" Green Latern");
m3 = new JMenuItem(" Sun Set");
m4 = new JMenuItem(" Texture");
m5 = new JMenuItem(" Greynite");
m6 = new JMenuItem(" Set Default");
m1.setFont(new Font("comic sans ms",Font.BOLD,14));
m2.setFont(new Font("comic sans ms",Font.BOLD,14));
m3.setFont(new Font("comic sans ms",Font.BOLD,14));
m4.setFont(new Font("comic sans ms",Font.BOLD,14));
m5.setFont(new Font("comic sans ms",Font.BOLD,14));
m6.setFont(new Font("comic sans ms",Font.BOLD,14));
m1.addActionListener(this);
m2.addActionListener(this);
m3.addActionListener(this);
m4.addActionListener(this);
m5.addActionListener(this);
m6.addActionListener(this);
op2.add(m1);
op2.add(m2);
op2.add(m3);
op2.add(m4);
op2.add(m5);
op2.add(m6);
pm.add(op1);
pm.add(op2);
//fr.setUndecorated(true);
btn1 = new JButton(img1);
btn2 = new JButton(img2);
btn3 = new JButton(img3);
btn4 = new JButton(img4);
btn5 = new JButton(img5);
btn6 = new JButton(img6);
btn1.setToolTipText("Registration");
btn2.setToolTipText("Remove Record");
btn3.setToolTipText("Search Record");
btn4.setToolTipText("Modify Record");
btn5.setToolTipText("Marks Record");
btn6.setToolTipText(" Exit ");
btn1.addActionListener(this);
btn2.addActionListener(this);
btn3.addActionListener(this);
btn4.addActionListener(this);
btn5.addActionListener(this);
btn6.addActionListener(this);
toolBar = new JToolBar();
toolBar.setBackground(Color.pink);
addtool();
fr.setVisible(true);
fr.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
fr.addMouseListener (new MouseAdapter () {
 public void mousePressed (MouseEvent me) { checkMouseTrigger (me); }
public void mouseReleased (MouseEvent me) { checkMouseTrigger (me); }
private void checkMouseTrigger (MouseEvent me) {
if (me.isPopupTrigger ())
pm.show (me.getComponent (), me.getX (), me.getY ());
}
}
);
}
public void actionPerformed(ActionEventae)
{
if((ae.getSource()==ar) || (ae.getSource()== btn1) || (ae.getSource()== ar1))
{
fr.setTitle("Student Management System [Insert Record]");
fr.setEnabled(false);
newaddrecord();
}
if((ae.getSource()==dr) || (ae.getSource()== btn2) || (ae.getSource()== dr1))
{
fr.setTitle("Student Management System [Remove Record]");
fr.setEnabled(false);
newdeleterecord();
}
if((ae.getSource()==sr) || (ae.getSource()== btn3) || (ae.getSource()== sr1))
{
fr.setTitle("Student Management System [Search Record]");
fr.setEnabled(false);
new search();
}
if((ae.getSource()==mr) || (ae.getSource()== btn4) || (ae.getSource()== mr1))
{
fr.setTitle("Student Management System [Modify Record]");
fr.setEnabled(false);
newsearchmodify();
}
if((ae.getSource()==dsr) || (ae.getSource()== btn5) || (ae.getSource()== dsr1))
{
fr.setTitle("Student Management System [Marks Record]");
fr.setEnabled(false);
newsearchmarks();
}
if((ae.getSource()==ext) || (ae.getSource()== btn6) || (ae.getSource()== ext1))
{
//fr.setTitle("Student Management System [Marks Record]");
//fr.setEnabled(false);
fr.dispose();
new login();
}
if(ae.getSource()==m1)
{
limg1 = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\back\\wood2.jpg"));
fr.setContentPane(limg1);
fr.invalidate();
fr.validate();
fr.repaint();
addtool();
}
if(ae.getSource()==m2)
{
limg1 = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\back\\wood3.jpg"));
fr.setContentPane(limg1);
fr.invalidate();
fr.validate();
fr.repaint();
addtool();
}
if(ae.getSource()==m3)
{
limg1 = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\back\\img..jpg"));
fr.setContentPane(limg1);
fr.invalidate();
fr.validate();
fr.repaint();
addtool();
}
if(ae.getSource()==m4)
{
limg1 = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\back\\img.png"));
fr.setContentPane(limg1);
fr.invalidate();
fr.validate();
fr.repaint();
addtool();
}
if(ae.getSource()==m5)
{
limg1 = new JLabel(new ImageIcon("c:\\stdmgtsys\\images\\back\\sm.jpg"));
fr.setContentPane(limg1);
fr.invalidate();
fr.validate();
 fr.repaint();
addtool();
}
if(ae.getSource()==m6)
{
fr.setContentPane(limg);
fr.invalidate();
fr.validate();
fr.repaint();
addtool();
}
}

public void addtool()

{
toolBar.add (btn1);
toolBar.addSeparator ();
toolBar.add (btn2);
toolBar.addSeparator ();
toolBar.add (btn3);
toolBar.addSeparator ();
toolBar.add (btn4);
toolBar.addSeparator ();
toolBar.add (btn5);
toolBar.addSeparator ();
toolBar.add (btn6);
toolBar.setBounds(0,0,width,50);
fr.add(toolBar);
}
public void run()
 {
while(true)
{
try
{
sleep(80);
}
catch(Exception e)
{
}
fx = fx + x;
l1.setBounds(fx,fy,1050,85);
if(fx<= 1366)
{
x = x * +1;
}
if(fx> 1366)
{
fx = 0;
}
}
}
public static void main(String args[])
{
newmainform();
}
}
//*****************************************//
 CHAPTER 9

SNAPSHOTS
Snapshots 1: For admin login

Snapshots 2: Welcome page for admin login

Snapshots 3: Main form

Snapshots4: Select operations (Patient)

Snapshots 5: Add patient information form

Snapshots 6: Registration successfully

Snapshots 7: Modify operation

Snapshots 8: View Patient Information

Snapshots 9: Doctors Information form

Snapshots 10: Add Doctor Information

Snapshots 11: Modify Doctors Information

Snapshots 12: View Doctor’s Information

Snapshots 13: Billing Information

Snapshots 14: Display All Users

Snapshots 15: Show all patient’s

Snapshots 16: Show all Doctor’s
 CHAPTER 10

CONCLUSION
10.1 Introduction:
The decision to acquire hardware or software must be handled in the same way as any other information
decision, the variety of sizes and types of computing resources available puts a burden on the analyst who must
select hardware, software and advise the top management accordingly.

Today, selecting a system is a serious and time-consuming. The time spent on the selection process is a function
of the applications and whether the system is a basic microcomputer or a mainframe. In either case, planning
system selection and acquiring experienced help where necessary pay off in the long run.

There are various important factors, which should be considered prior to system selection. They are:

 Define system capabilities that make sense for the Hospital.

 Specify the magnitudes of the problem; that is, clarify section entails a few peripherals or a major
decision concerning the mainframe.
 Hardware and software should be considered as a package.
 Develop a time frame for the selection process.
 Provide user indoctrination. This is crucial, especially for first time users. Selling the system to the user
staff, provide adequate training and creating an environment conductive to implementation are
prerequisites for system acquisition.

The selection process should be viewed as a project and a project team should be formed with the help of
management. The selection process consists of several steps, which are discussed below:

10.1.1 Requirements analysis: The first step in selection is understanding the user`s requirements within
the framework of the organization`s objectives and the environment in which the system is being installed.

10.1.2 System specifications: System specification must be clearly defined. These specifications must
reflect the actual applications to be handled by the system and include system objectives, Flowcharts, input-
output requirements, file structure and cost.

10.1.3 Request for proposal: After the requirement analysis and system specifications have been defined,
a request for proposal is prepared and sent to selected vendors for bidding.

10.1.4 Evaluation and validation: The evaluation phase ranks various vendor proposal and determines
the one best suited to the user`s requirements. It looks into items such as price, availability and technical
support. System validation ensures that the vendor can, in fact, match his/her claims, especially system
performance.
10.1.5 Vendor selection: This step determines the vendor with the best combination of reputation,
reliability, service record, training, delivery time, lease/finance terms. The System chosen goes though contract
negotiation before implementation.

10.2 Conclusion and future scope:

This project as title “Student management system” is comes under the Relational Database Management

System (RDBMS). This application is developed with the help of java 6.0 and Microsoft Access. This

application can also be run on the network environment so it can be said as network application.

From a proper analysis of positive points and constraints on the component it can be safely concluded that the
product is a highly efficient GUI based component. This application is working properly and meeting to all user
requirements. This component can be easily plugged in many other systems.

Nothing is perfect in this world. So, we are also no exception. Although, we have tried our best to present the
information effectively, yet, there can be further enhancement in the Application. We have taken care of all the
critical aspects, which need to take care of during the development of the Project. Like the things this project
also has some limitations and can further be enhances by someone, because there are certain drawbacks that do
not permit the system to be 100% accurate.

The different areas where we can use this application are:

 Any Hospital can make use of it for providing information about Hospital.
 It can be used in offices and modifications can be easily done according to requirements.
 This application can work on the full web based environment.

REFERENCES

Books:

 Beginning Java Objects: From Concepts to Code , Jacquie Barker,2009

 Introduction to Java Programming: NIIIT publication , John Wiley,1998
 The Complete Reference Java, McGrawhill: Herbert Schildth- reprint, 2008

Web Sites:

 www.apache.org
 www.wikipedia.com