Patients

Records
Monitoring
System

WHO Norms

B.Madhavai
[Prime Multi Specialty Hospital is an ISO 9001-2000
accredited, 400 bed multi-specialty hospitals located in
Hyderabad. Patients Record Monitoring System is a
DC
Java application which automates the Receptionist
[Prime module, Doctors Module and Lab Module.]
Multispecialty
Hospitals]

[9348455007]

0 4 0 - 32993007

[05-Jan-2009]
Project name: Patients Record Monitoring System (WHO)
Client: Prime Hospitals, Hyderabad
About Client

Prime Hospitals are one of the most trustworthy hospitals in the twin cities.
Prime Multi Specialty Hospital is an ISO 9001-2000 accredited, 400 bed multi-specialty hospital
located in Hyderabad. The Hospital is spread in an area of about 20 acres with roads on all 4
sides. Every room is airy and sunlit. The landscaped lush gardens make the ambience peaceful
and relaxing, not only for the patients but for attendants too. The Hospital prides itself on
offering qualitative Intensive Care Unit (I.C.U), Out Patient Department (O.P.D), In Patient
Department, Two Operation Theatres, Separate Labor Room, a well equipped Diagnostic Center
and In-house Pharmacy etc. The O.P.D and diagnostic center is housed in a separate building
within the same campus. 80 cars free parking, a food court; ATM etc. are all available in-house.

Scope

The project assigned to the project team is real time project. The project is developed in Web
based screens and connected with Oracle Database connectivity. To develop this project the
project team has used web logic server as an application server and oracle database server as
backend. There are basically two types of modules are developed by the front end programmers.
These are input modules and out put modules. The module which helps the user to input the data,
modify the data and delete the data will be called the input modules. The modules which enables
the user to view the data from the database and no manipulations and modifications can be done
through this will be called out put modules. In this project the project team has to generate
hundreds of reports from the data stored in the database through the out put modules. This
reports can be generated from different tables with multiple where clauses. There are lots of
manipulations and calculations have to be defined in between the tables and the relative tables
from different departments have to be integrated with certain calculations. The retrieved data will
be exhibited through output screens or reporting screens. These calculations and manipulations
have to be generated automatically. The output data has to be generated in compatible mode. The
compatible reports are shown in the HTML Tables or Crystal reports. These reports should be
generated and cover all the user requirements and replicate the minute details of the company
transactions.

The Deliverables of this project: The project team has to integrate all the departments. All
modules in each and every department have to be automated and should replicate the data
manipulations in other departments. The screens defined for the project are divided in to
deferent modules. The screens should be user-friendly and with attractive pictures which
replicate the symbolism of the department. The screens developed in this project should help
the user to navigate the further screens and options. The screens have to be developed with
required fields. There should be radio buttons, dropdown boxes or scroll bars or interactive
buttons have to be incorporated in accordance with the project automation requirements. The
linking of the screens and content management of the screen should be built aptly.

Functionality of the project

Prime Multi Specialty Hospital is an ISO 9001-2000 accredited, 400 bed multi-specialty
hospitals located in Hyderabad. Patients Record Monitoring System is a Java application
which automates the Receptionist module, Doctors Module and Lab Module. Receptionist
Module is meant for record the primary information about the patient. According to the
patients choice the receptionist will guide the patient to the specific doctor specialized in the
treatment required for the patient. The details of the patient and the doctor suggested by the
receptionist will be entered in the database. The data will be retrieved by all departments with
the primary key i.e patients ID given and generated at receptionist module. As soon as the
patient reaches the doctor with patient ID, doctor will get all the primary details of the patient
and examine the patient if it is need he will suggest some lab examinations and enter the
same in the patients screen available in doctors module. The patient will go to receptionist
and pay for the examinations and then go for the examination at lab or diagnostic center. The
incharge of the diagnostic center will open the module and enter the patient ID. Then he can
understand the reports needed by the doctor for better diagnosis of the disease. The lab
assistant will do the examinations required by the patient and enter the examination reports in
his module. This will be updated in the database of patients record. At last the patient will go
to the doctor. Doctor will open the module and understand the reports of the patients which
were entered by lab assistant. Finally doctor diagnosis the disease and prescribe the
medicines. The prescription of the medicines will be entered in the patients records as well as
a copy of the record will be given to the patient for taking the medication. In this project all
the departments with their sections have to be integrated separately in one main screen. The
user will have an option to choose the particular department. Once any department is chosen
the login screen will be pop up and ask for the user name and password. This mechanism is
to give entry to relevant user to operate the particular section. This will stop the intrusion of
unauthorized user. Once the username and password is authenticated the user will have an
option to choose the relevant section main page. This page consists of three options to
manage the data. One is to enter new entry, second one is to modify the existing entry and the
third one is to delete the entry. Every user page is connected to the reports. These reports will
give comprehensive information about the user data available in the department database.
Each reporting screen will have not less than 20 options to view the data from the database
pertaining to the department.

Technical Design of the Project:

Patients Record Monitoring
System

Receptionist User or Patient

Doctor Laboratory

Doctor Lab
Receptionist

Patients Records
 Business Processes: In this project the web application is going to serve the
same locations as follows:

1. Receptionist

2. Doctor

3. Laboratory

Business Areas: By implementing this project the following areas will be

affected.

1. Receptionist

2. Doctors in Different specializations

3. Blood and Urin Lab

4. X-Ray Lab

5. Pathology

6. Scanning

7. CT Scanning

8. 64 Slice Scanning

9. Operation Theater

Business Data that will be changed:

This is the project with full automation mechanism. The project team has to develop
the internal coding to transmit the data to other tables where ever it has
relationship. The data which will be inserted from one department that will be
automatically affects the relevant departments. The data which stored in one
department might be changed automatically time to time because of the other data
entered in other department. For example there is a data entered in Receptionist
system will definitely transmitted to al the departments. If any data is updated in
any Department that will be automatically updated in the patients records. In this
manner the relative departments will be interchanging the data and activate the
manipulations with the other data.

Technologies Required: Patients records monitoring Systems is a complete

Automation of different departments. It is a web application
which integrate different departments in different locations.
To construct this application the web based technologies are
essentially used. This application can be developed in Java,
 J2EE and HTML pages with JSP Serve lets. The database can be
oracle 9i used.

Existing System: The existing system is developed with VB Technologies

backed with Oracle 8i database. This is stand alone application
which caters the services of each and every department
severally.

The proposed System:

1. The proposed system should support all departments.

2. This should integrate with all the modules in every section.

3. This application should automate the data within different sections.

4. This application should automate the different departments located

in different Locations.

5. This application should be maintained with remote database and

support IES server.

6. This application is an embodiment of the integrated and automated

solution between all departments in accordance with the purchase
orders generated from the customers.

7. This application should exhibit the minute reports of the data

available in database.

Milestone of the project work:

1. Requirements gathering of the client

2. Requirements specifications Document Preparation

3. Functional Specifications of the project.

4. Design Document ( Macro level )

5. Design Documentation ( Micro Level )

6. Database Design ( Macro Level )

7. Database Design ( Micro Level )

8. Coding specifications
9. Coding Metrics Finalization.

10. Coding execution

11. Database Creation – database – Table space – table

12. Data integration design

13. Data manipulation design

14. Procedures and functions design

15. Integration between Screens and database

16. Synchronization of front end and back end.

17. Testing
18. Review – Coding

19. Documentation – Business process Documentation

20. Documentation – Business process Re-engineering

21. People management -

22. Preparation of Training Material

23. Project management and administration

24. Hardware Installation – Servers - Clients

25. Deployment of the Software at clients place

26. Data preparation for transfer

27. System Documentation

28. Process flow documentation

 As a front end programmer my Role

• Developed JSP pages, Servlets and HTML pages as per requirement

• Understand the Module specifications of the project and developed the code for inter-
module relationship along with the Oracle Developers.
• Module de composition is perfectly followed in this project.
• Developed reports for Management specific requirements.
• Developed the User screens and connectivity to the tables in accordance with the
Oracle programmers.
• Used extensively HTML and JSP to develop the screens and run with Web logic server
• Used Java beans extensively to connect, retrieve and insert the data into the
database.
• Java script used to display the date and time and other calculations of the
applications.
• Developed JSP pages, Servlets and HTML pages as per requirement
• Understand the Module specifications of the project and developed the code for inter-
module relationship along with the Oracle Developers.
• Module de composition is perfectly followed in this project.
• Developed reports for Management specific requirements.
• Developed the User screens connectivity to the tables in accordance with the Oracle
programmers.
• Used extensively HTML and JSP to develop the screens and run with Web logic server
• Used Java beans extensively to connect, retrieve and insert the data into the
database.
• Java script used to display the date and time and other calculations of the
applications.
• Developed the Inter Module auto updates with the help of Oracle Primary Key and
Foreign Key concepts.
Business Requirements
Client: Prime Hospitals, Hyderabad.
 Modules of the Project
1. Receptionist

2. Doctor

3. Laboratory

Distribution or Deployment

Prime Hospitals are one of the most trustworthy hospitals in the twin cities.
Prime Multi Specialty Hospital is an ISO 9001-2000 accredited, 400 bed multi-specialty hospital
located in Hyderabad. The Hospital is spread in an area of about 20 acres with roads on all 4
sides. Every room is airy and sunlit. The landscaped lush gardens make the ambience peaceful
and relaxing, not only for the patients but for attendants too. The Hospital prides itself on
offering qualitative Intensive Care Unit (I.C.U), Out Patient Department (O.P.D), In Patient
Department, Two Operation Theatres, Separate Labor Room, a well equipped Diagnostic Center
and In-house Pharmacy etc. The O.P.D and diagnostic center is housed in a separate building
within the same campus. 80 cars free parking, a food court; ATM etc. are all available in-house.

This application enables the hospital management to maintain the records of the patients visited
to the hospital with their case study and their medical history. When eve the patient comet to the
hospital the patient No what is allocated by the system will get the complete previous history.
The application enables the doctor to view the history of the patient as soon as he come and tell
his Patient ID. The patient Id is one which gives time to time details as soon as he enters into the
hospital.

The Laboratory also gets the details of the patient and the suggestions given by the doctor to
undergo the specific test. As soon as he get the details of the test he will do it and update the
same into the system. The details will be again viewed by the doctor and prescribe the medicines.

Mission profile or scenario

The Mission profile of the project is obviously revealed by the modules. In this project the
stand alone application is going to serve the different locations as follows:

1. Receptionist
 2. Doctor

3. Lab

Performance and related parameters

The project should perform the following parameters.

1. This project is a stand alone application to automate and integrate different departments.

2. The doctor will view the details of the patient entered by the receiptionist.

3. The tests suggested by the doctor and entered in the system will be viewed by the lab
technicians.

4. The lab technicians will perform the tests and enter the details of the reports into the
system.

5. The doctor will again view the details of the tests and prescribe the patient with
appropriate medicine.

Utilization environments

The application should work on any platform. Hence the application should be
developed in java Technologies. For this the project team has to develop the application
using jsp servlet with Oracle 9i database.

• Developed HTML pages with JSP code and Servlet validations as per requirement
• Understand the Module specifications of the project and developed the code for inter-
module relationship along with the Oracle Server Developers.
• Module de composition is perfectly followed in this project.
• Developed reports for user specific requirements.
• Developed the User screens and connectivity to the tables in accordance with the SQL
Server developers.
 • Used extensively HTML to develop the screens and run with Oracle server
• Used Java beans extensively to connect, retrieve and insert the data into the database.
• Java script used to display the date and time and other calculations of the applications.

Effectiveness requirements

The effectiveness of the project will be highlighted by the following points;

1. The project is meant for preserving the records of the patients in accordance with
WHO Norms and conditions.

2. Different modules are meant for entering the details of the patients in different stages.

3. To view the reports different modules are accessing the database for
different purposes.

4. The updated information should be bifurcated in two main categories .

5. These are Patients history and what the disease and diagnosis.

Operational life cycle

The life span of the project is for 10 years

The project should support all the data of the delayed timings in the database.

The project should be feasible for up gradation of further technologies.

The project should consist of data consistency.

The project should be developed with Module de composition.

The project should maintain the inter module relation-ship.

The project should be supported with latest versions of internet explorer.

 Environment
Hard ware Specification

Processor : Intel P-IV based system

Processor Speed : Core 2 Deo 2.4 MHz

RAM : 512MB

Hard Disk : 80GB

Software Specification

Technologies : Java, JSP, Servelets, HTML pages and HTML Tables

Database : Oracle 9i

Operating System : Windows NT/2000/XP

 System Analysis
All User requirements.

The system should have all the user requirement as specified below:

1. The system should enable the hr manager to access the different modules of
the project in a easy identification buttons or hyperlink sentences. The HR
manager should have a superseded password which can enable to access
any module.
2. The receptionist, doctor and lab should access different activities of the
modules with easy to use interface screens. All the screens should have easy
to use navigational interface mode.

3. The user is not a computer knowledge specialist. so the user interface

screens should be designed in accordance with the general English language
and help the user to navigate to the next level screens.

4. The Receiptionist will have access the patients records and assign the patient
Id to the new patients coming to the hospitals.

5. The doctor module will specify the user name and password to access his
module and look for the details of the patient.

6. The user interface screens should consist comprehensive information about

the project and help the user to choose the particular activity what he is
intended to do.
7. The user interface screens which make the user to input the information
should guide the user to input the relevant information into the database.

8. The input module screens should guide with pop up menus if the
information is wrongly typed.

9. The user should view the reports about the data entered into the system.

10.The user should have a facility to modify the data what entered wrongly.

11.The user should also have a facility in the system to delete the wrong and
unnecessary records from the database.

12.The user should not get any eye stress because of the color of the screens.

13.The transaction no should consist of year, day, month and auto sequence no.

14.The user should have user access to the screens by password authentication
system.

15.User name should be unique and the user should have a facility to change
the password of his own.
16.If the user forget the password the screen should have an option to retrieve
the password from the company administrator by giving his date of birth and
maidens name option.

17.The screens should not allow the unauthorized user into the system.

18.The user should access the different options of his choice by one mouse click
on the buttons. The buttons should be interactive mode and give specific
option navigation to the user. In the next level screen the options should be
defined with accurate hyperlinks with relevant screens.

Modules specification diagram:

Patients Record
Human Monitoring
Capital
System
Management

Receptionist User or Patient

Doctor Laboratory
 Doctor Lab
Receptionist

Patients Records

System Architecture

Patients
Records
User Monitoring
User will interact the system and
enter the details of his activity
System
The data entered by the user will
be stored in the database

Database

Interface

Patients Records
Monitoring
System

Receptionist Laboratory
Doctor
Patients Tests and
personal prescriptions Tests and
History reports

Database
System Design
 List of Modules

4. Receptionist

5. Doctor

6. Laboratory

Description of the Modules

1. Receptionist: Receptionist is responsible for entering the details of

the patients. From this module only the patient ID will be generated.
Once the patient pays the fee then the module will store the details
into the database. This first hand details will be used by the other
modules.

2. Doctor: Doctor is responsible for entering the tests and view the
tests reports from lab. Through this module only the diagnosis of
disease will be revealed. This module is responsible for entering the
prescription of the patients.

3. Laboratory: This module is responsible for entering the reports for the
tests suggested by the doctor.

Functionality of Modules

Prime Multi Specialty Hospital is an ISO 9001-2000 accredited, 400 bed multi-specialty
hospitals located in Hyderabad. Patients Record Monitoring System is a Java application
which automates the Receptionist module, Doctors Module and Lab Module.

Receptionist Module is meant for record the primary information about the patient.
According to the patients choice the receptionist will guide the patient to the specific doctor
specialized in the treatment required for the patient. The details of the patient and the doctor
suggested by the receptionist will be entered in the database. The data will be retrieved by all
departments with the primary key i.e patients ID given and generated at receptionist module.
Doctor Module: As soon as the patient reaches the doctor with patient ID, doctor will get
all the primary details of the patient and examine the patient if it is need he will suggest some
lab examinations and enter the same in the patients screen available in doctors module. The
patient will go to receptionist and pay for the examinations and then go for the examination
at lab or diagnostic center. The incharge of the diagnostic center will open the module and
enter the patient ID. Then he can understand the reports needed by the doctor for better
diagnosis of the disease.

The Lab: The lab assistant will do the examinations required by the patient and enter the
examination reports in his module. This will be updated in the database of patients record.

At last the patient will go to the doctor. Doctor will open the module and understand the
reports of the patients which were entered by lab assistant. Finally doctor diagnosis the
disease and prescribe the medicines. The prescription of the medicines will be entered in the
patients records as well as a copy of the record will be given to the patient for taking the
medication. In this project all the departments with their sections have to be integrated
separately in one main screen. The user will have an option to choose the particular
department. Once any department is chosen the login screen will be pop up and ask for the
user name and password. This mechanism is to give entry to relevant user to operate the
particular section. This will stop the intrusion of unauthorized user. Once the username and
password is authenticated the user will have an option to choose the relevant section main
page. This page consists of three options to manage the data. One is to enter new entry,
second one is to modify the existing entry and the third one is to delete the entry. Every user
page is connected to the reports. These reports will give comprehensive information about
the user data available in the department database. Each reporting screen will have not less
than 20 options to view the data from the database pertaining to the department.
Interface relationship among the module ER Diagram
 Class diagram

Sequence Diagram
 1. The details of the Patient will be retrieved by the Patient table. The
Patient ID will be automatically generated.

Designing of database tables with key elements

Patient Details Table

SL No Description Size Data type constraint

1. Patient ID 10 Varchar 2 Primary Key
2. Patient Name 20 Varchar 2
3. DOB Date
4. Age 2 Num
5. Address 50 Varchar2
6. Contact No 10 Numb
7. Blood Group 5 Varchar2
8. Problem 200 Varchar2
9. Doctor Name 30 Varchar 2

Doctor Table

SL No Description Size Data type constraint

1. Patient ID 10 Varchar2 Foreign Key
2. Patient Name 20 Varchar2
3. Age 3 Num
4. Tests 50 Varchar2
5. Prescription 200 Varchar 2

Attendance Table

SL No Description Size Data type constraint

 1. Patient ID 10 Varchar 2 Foreign Key
2. Patient Name 20 Varchar 2
3. Tests 50 Varchar2
4. Reports 200 Varchar2

Detailed Functionality and Logic of

the Modules

Input and out put of the modules

The outcome of the project is to get the details of the candidates who upload through the web
site. The uploaded details will be stored in the database. The details will be updated in different
stages of the candidates examinations, personal round of interview results etc. The Candidates
details will be updated in different stages and shortlisted by the HR manager for offer letter,

Input

The candidate will input the details and the different stages of recruitment will automatically
input the details of the examination resuls.

The output

The Patient details will be stored in the database.

Dependencies Issues

The Lab module is depended on the details of the tests given by the doctor.

The doctor module is also depended on the receptionist module which is entering the details of
the patient.
 Error Message Listing

1. The PatientID should be unique. This will be generated by the system only.

2. If the user enter the wrong detsils into the employee name it should generate the error
message to enter only alphabets only.

3. If the user enter the unwanted information into the dob field it should generate an error
message to guide the user to insert the appropriate format into the system.

4. The unwanted data entered by the user should be corrected by the error message of the
system appropriately to guide the user.
Company Profile
Fore C Software Ltd
 WELCOME TO Fore C Software

We recruit top-notch people and encourage them to grow as

individuals and as members of our team. We promote within an
approach that takes a long-term view of career development,
minimizes employee turnover, and helps retain multi-skilled and
experienced consultants. We invest in the ever-growing knowledge
of our consultants, allowing the continually enhance their skills and
experience.

ABOUT US

SekharSoft Started in 1999 with a focus to provide quality

recruitment service to clients, we have evolved into a Total
Solutions Company Spanning IT.

During the last 6 years of operation, Fore C Software consulting and

IT services has created benchmarks in areas of Recruitment and
Staffing Progressed to become a Total Solutions Company Spanning
IT.

Delivering What Business Demands

Fore C Software Ltd. is a leading consulting and IT services

company, offering a wide array of solutions customized for a range
of key verticals and horizontals. From strategy consulting right
through to implementing IT solutions for customers in the entire IT
space. It has excellent competencies in ERP, CRM, Web Designing,
Data Warehousing, Manufacturing, Health Care, Application Tuning
and Database Tuning. As a diverse end-to-end IT solutions provider,
Fore C Software offers a range of expertise aimed at helping
customers re-engineer and re-invent their businesses to compete
successfully in an ever-changing marketplace.

Our Vision

"Development Through Dedication" is a naked fact in the eyes of

management the object of operations from day one is
multidimensional integration in tune with the global requirements
adopting the best possible/suitable technologies. We have derived
our own methodology to achieve the objective. We strongly believe
not just in customer satisfaction but also social responsibility and
commitments. We place a great deal of importance on training and
education, To serve our clients by recruiting, screening and
recommending who will improve our client's organization. Our goal
is to provide business solutions to our clients with minimum
overheads and maximum effect.

As a first step to provide best possible training, to make the

trainees fit to the competitive global market.

As a second step in the integration process we provide the

potential persons to our clients in the areas of Oracle, Visual Basic,
Java, J2EE , System & Network Administration, DBA, Data
Warehousing, Testing Tools.

As a third step in the process of integration we provide software

solutions to organizations of every description.

Fore C Software Ltd was formed by a group of extremely well

qualified technical experts to provide high quality professional
services in the fields of:
Consulting and Software Development.

Professional Education.

CONSULTING SERVICES
Fore C Software Ltd's placement division was formed with the aim
of providing a quality service to clients and candidates alike. And
distinguishes itself from other agencies by dealing exclusively with
technology experienced professionals with proven track records of
success. We set out to achieve this by building long-term
partnerships with our clients and endeavoring to give a high
standard of personal service both to clients and candidates.

Our service includes the recruitment of permanent and contract staff

across a range of disciplines.

With recruitment consultants who have experience not only in

recruitment but also commercial experience, we can work very
closely with our clients to understand their requirements. Our
services cover both the requirement for permanent and contract
staff.

We understand that you may have short-term as well as long -term

goals. Our services are flexible to meet those goals and we offer

Permanent Placement

Contract Services

CAPABILITIES

Fore C Software Ltd can provide contract consultants with

expertise in the following areas; E-Commerce Technologies, Java,
Oracle (all Products), Data Warehousing, C, C++, Visual C++,
PowerBuilder, Visual Basic, ColdFusion, IBM Web-Sphere, NetObjects,
SAP, PeopleSoft, , Siebel, UNIX, Windows NT, Sybase, SQL Server,
COM/DCOM, Testing/Analysis. We use our best endeavors to satisfy
any contract service requirement, with no restriction on discipline,
market sector or geographical area.

Development
can take complete projects off your hands and ensure prompt
delivery within budget. Here are just a few examples of the types of
projects that we can handle:

Development and/or implementation of a long term, strategic

technology plans.
Development of an Internet Presence.

Development of an Intranet and extended enterprises solutions·

Development and/or implementation of document management

solution
Development of a Paperless office environment

Electronic Commerce Initiatives

Strategic Network Planning and implementation

Sales Force Automation

Customer Application Development:

Fore C Software can build any application that you require. You tell
us what you would like to do, and well spec it, build it, implement it,
and train your people on how to use it. Have you ever said, "If we
just had an app that would?". Then call Sekhar Soft. We will turn
your idea into a reality. Fore C Software has unique resources that
allow us to develop and deliver custom applications very rapidly and
inexpensively.

Maintenance

Fore C Software is known to be the best for Database

Administration. Fore C Software has talented certified DBA's to
support relational database remotely. Why do you need a full time
DBA to manage a database that needs only 10 hours of maintenance
time? Many organizations need assistance in installation,
maintenance, and operations of their relational database, due to a
lack of necessary expertise or experience to efficiently accomplish
their objectives. Furthermore, recruiting and retaining people with
this background is an expensive venture. Fore C Software can
provide remote DBA services in number of relational database like
Oracle, Microsoft and SQL Server.

Fore C Software can perform following tasks

Database Backups at regular intervals.

Troubleshooting of any minor problems with the application.

Tuning the database.

Server set up and disk configuration.

Database Capacity Planning.

Upgrading of Oracle software to required/supported levels.

Configuration of Oracle networking software.

Providing technical services to assist in the day to day

management of Oracle database systems.

METHODOLOGY:

Out of our past experience and keeping in view, available human

resources, equipment, time factor, client specifications, cost,
training requirements, technology adoption, user environment, we
have developed methodologies for different applications. The major
methodologies includes .

Training methodology for individuals and corporate

Implementation methodology for applications

 Development methodology for made-to-order solutions

Methodology for user manuals · Methodology for pricing

Methodology for vendor selection

Technology evaluation criteria

CLIENT LIST

Following are our Valued Customers to whome we served to

meet their ends
Our Valued Customers

Priyadarshini Cements Ltd.

Sharanya Teltronics

Medwin Hospitals

Kakatiya cements and Sugars LimiteD

Four Soft Pvt. Lt

APSRTC (Through IDS Technologies)

EPFO (Employes Provident Fund Organisation)

Penna Cements

Samkerg Pistons

Veljion
Makson

Testing
Testing
Testing is the process of detecting errors. Testing performs a very critical
role for quality assurance and for ensuring the reliability of software.
The results of testing are used later on during maintenance also. In the
test phase various test cases intended to find the bugs and loop holes
exist in the software will be designed. During testing, the program to be
tested is executed with a set of test cases and the output of the
program is performing as it is expected to.

Often when we test our program, the test cases are treated as “
throw away” cases. After testing is complete, test cases and their outcomes
are thrown away. The main objective of testing is to find errors if any,
especially the error uncovered till the moment. Testing cannot show the
absence of defects it can only show the defects that are a set of interesting
test cases along with their expected output for future use.

Software testing is crucial element and it represents at the

ultimate review of specification design and coding. There are black box
testing and glass box testing. When the complete software testing is
considered Back box attitudes to the tests. That is concluded predicted on a
close examination of procedural detail.

The software is tested using control structures testing method

under white box testing techniques. The two tests done under this approach.
One condition testing to check the Boolean operator errors, Boolean variable
errors, Boolean parenthesis errors etc. Loop testing to check simple loops
and tested loops.
Faults can be occurred during any phase in the software development
cycle. Verification is performed on the output in each phase but still some fault. We
likely to remain undetected by these methods. These faults will be eventually
reflected in the code. Testing is usually relied upon to detect these defaults in
addition to the fault introduced during the code phase .For this, different levels of
testing are which perform different tasks and aim to test different aspects of the
system.
Psychology of Testing

The aim of testing is often to demonstrate that a program works by showing that it
has no errors. The basic purpose of testing phase is to detect the errors that may be
present in the program. Hence one should not start testing with the intent of
showing that a program works, but the intent should be to show that a program
doesn’t work. Testing is the process of executing a program with the intent of
finding errors.

Testing Objectives

The main objective of testing is to uncover a host of errors, systematically

and with minimum effort and time. Stating formally, we can say,
 Testing is a process of executing a program with the intent of finding an
error.
 A successful test is one that uncovers an as yet undiscovered error.
 A good test case is one that has a high probability of finding error, if it
exists.
 The tests are inadequate to detect possibly present errors.
 The software more or less confirms to the quality and reliable standards.

Levels of Testing

In order to uncover the errors present in different phases we have the

concept of levels of testing. The basic levels of testing are as shown below…

Acceptance
Testing

Client Needs

System Testing
Requirements

Integration Testing

Unit Testing
 Design

Code

System Testing

The philosophy behind testing is to find errors. Test cases are devised with
this in mind. A strategy employed for system testing is code testing.

Code Testing:

This strategy examines the logic of the program. To follow this method we
developed some test data that resulted in executing every instruction in the
program and module i.e. every path is tested. Systems are not designed as
entire nor are they tested as single systems. To ensure that the coding is
perfect two types of testing is performed or for that matter is performed or
that matter is performed or for that matter is performed on all systems.

Types Of Testing

 Unit Testing
 Link Testing

Unit Testing

Unit testing focuses verification effort on the smallest unit of software i.e. the
module. Using the detailed design and the process specifications testing is
done to uncover errors within the boundary of the module. All modules must
be successful in the unit test before the start of the integration testing
begins.

In this project each service can be thought of a module. There are so many
modules like Login, HWAdmin, MasterAdmin, Normal User, and PManager.
Giving different sets of inputs has tested each module. When developing the
module as well as finishing the development so that each module works
without any error. The inputs are validated when accepting from the user.

In this application developer tests the programs up as system. Software units

in a system are the modules and routines that are assembled and
integrated to form a specific function. Unit testing is first done on
modules, independent of one another to locate errors. This enables to
detect errors. Through this errors resulting from interaction between
modules initially avoided.

Unit testing focuses verification effort on the smallest

unit of software design module. Using the detail design description as an
important control path is tested to uncover errors with in the boundary of the
modules unit. Testing has many important results for the next generation is
to be easy. The unit testing considers the following condition of a program
module while testing.

Interface

Logical data structure

Boundary data structures

Independent path

Error handling path

Testing
In the project Budget Analysis System we have done the unit testing. The table
applied out the modules or interface test to answer that information properly flows
into and out of the program unit under test. The local data structure is examine to
ensure that data stores temporary monitors its integrity during all steps in algorithm
execution. Boundary conditions are tested to ensure that the module operates
properly at boundaries, establish to limit on restrict proclaim.

Link Testing

Link testing does not test software but rather the integration of each module
in system. The primary concern is the compatibility of each module. The
Programmer tests where modules are designed with different parameters,
length, type etc.

Integration Testing

After the unit testing we have to perform integration testing. The goal here is
to see if modules can be integrated proprerly, the emphasis being on testing
interfaces between modules. This testing activity can be considered as
testing the design and hence the emphasis on testing module interactions.

In this project integrating all the modules forms the main system. When
integrating all the modules I have checked whether the integration effects
working of any of the services by giving different combinations of inputs with
which the two services run perfectly before Integration.

System Testing

Here the entire software system is tested. The reference document for this
process is the requirements document, and the goal os to see if software
meets its requirements.

Here entire ‘ATM’ has been tested against requirements of project and it is
checked whether all requirements of project have been satisfied or not.
Acceptance Testing

Acceptance Test is performed with realistic data of the client to demonstrate

that the software is working satisfactorily. Testing here is focused on
external behavior of the system; the internal logic of program is not
emphasized.

In this project ‘Network Management Of Database System’ I have collected

some data and tested whether project is working correctly or not.

Test cases should be selected so that the largest number of attributes of an

equivalence class is exercised at once. The testing phase is an important
part of software development. It is the process of finding errors and missing
operations and also a complete verification to determine whether the
objectives are met and the user requirements are satisfied.

White Box Testing

This is a unit testing method where a unit will be taken at a time and tested
thoroughly at a statement level to find the maximum possible errors. I tested step
wise every piece of code, taking care that every statement in the code is executed
at least once. The white box testing is also called Glass Box Testing.

I have generated a list of test cases, sample data, which is used to check all
possible combinations of execution paths through the code at every module level.

Black Box Testing

This testing method considers a module as a single unit and checks the unit at
interface and communication with other modules rather getting into details at
statement level. Here the module will be treated as a block box that will take some
input and generate output. Output for a given set of input combinations are
forwarded to other modules.
Criteria Satisfied by Test Cases

1) Test cases that reduced by a count that is greater than one, the number
of additional test cases that much be designed to achieve reasonable
testing.

2) Test cases that tell us something about the presence or absence of

classes of errors, rather than an error associated only with the specific
test at hand.

Implementation
A product software implementation method is a systematically structured
approach to effectively integrate a software based service or component into
the workflow of an organizational structure or an individual end-user.
This entry focuses on the process modeling (Process Modeling) side of the
implementation of “large” (explained in complexity differences) product
software, using the implementation of Enterprise Resource Planning systems
as the main example to elaborate on.

Overview
A product software implementation method is a blueprint to get users and/or
organizations running with a specific software product. The method is a set
of rules and views to cope with the most common issues that occur when
implementing a software product: business alignment from the
organizational view and acceptance from the human view.
The implementation of product software, as the final link in the deployment
chain of software production, is in a financial perspective of a major issue. It
is stated that the implementation of (product) software consumes up to 1/3
of the budget of a software purchase
Implementation complexity differences
The complexity of implementing product software differs on several issues.
Examples are: the number of end users that will use the product software,
the effects that the implementation has on changes of tasks and
responsibilities for the end user, the culture and the integrity of the
organization where the software is going to be used and the budget available
for acquiring product software.
In general, differences are identified on a scale of size (bigger, smaller, more,
less). An example of the “smaller” product software is the implementation of
an office package. However there could be a lot of end users in an
organization, the impact on the tasks and responsibilities of the end users
will not be too intense, as the daily workflow of the end user is not changing
significantly. An example of “larger” product software is the implementation
of an Enterprise Resource Planning system. The implementation requires in-
depth insights on the architecture of the organization as well as of the
product itself, before it can be aligned. Next, the usage of an ERP system
involves much more dedication of the end users as new tasks and
responsibilities will never be created or will be shifted.
Software customization and Business Process Redesign
Process modeling, used to align product software and organizational
structures, involves a major issue, when the conclusion is drawn that the
product software and the organizational structure do not align well enough
for the software to be implemented. In this case, two alternatives are
possible: the customization of the software or the redesign of the
organizational structure, thus the business processes.

Customizing the software actually transforms the product software in tailor-

made software, as the idea of standardized software no longer applies. This
may result in loss of support on the software and the need to acquire
consultancy when issues arise in the usage of the software. Customizing
however results in a situation where the organizational integrity is not
adjusted, which puts less pressure on the end users, as less changes or shifts
in workflows are required. This fact may positively add to the acceptance of
any new (product) software application used and may thus decrease the
implementation time and budget on the soft side of the implementation
budget.
Redesigning business processes is more sensible for causing resistance in
the usage of product software, as altered business processes will alter tasks
and responsibilities for the end users of the product software. However, while
the product software is not altered, better support, training and service
levels are possible, because the support was created for the specific integrity
of the software.

Implementation Frameworks
The guiding principle versus the profession
Another issue on the implementation process of product software is the
choice, or actually the question, to what extent an implementation method
should be used.
Implementation methods can on the one hand be used as a guiding principle,
indicating that the method serves as a global idea about how the
implementation phase of any project should run. This choice leaves more
room for situational factors that are not taken into account in the chosen
method, but will result in ambiguity when questions arise in the execution of
the implementation process.
On the other hand methods can be used as a profession, meaning that the
method should be taken strict and the usage of the method should be a
profession, instead of a guiding principle. This view is very useful if the
implementation process is very complex and is very dependent on exact and
precise acting. Organizational and quality management will embrace this
view, as a strict usage of any method results in more clarity on
organizational level. Change management however might indicate that more
flexibility in an implementation method leaves more room for the soft side of
implementation processes.
Implementation frameworks
Apart from implementation methods serving as the set of rules to implement
a specific product or service, implementation frameworks serve as the
project managed structure to define the implementation phase in time,
budget and quality.
Several project management methods can serve as a basis to perform the
implementation method. Since this entry focuses on the implementation of
product software, the best project management methods suitable for
supporting the implementation phase are project management methods that
focus on software and information systems itself as well. The applicability of
using a framework for implementation methods is clarified by the examples
of using DSDM and Prince2 as project management method frameworks.rony
DSDM
The power of DSDM is that the method uses the principles of iteration and
incremental value, meaning that projects are carried out in repeating phases
where each phase adds value to the project. In this way implementation
phases can be carried out incrementally, adding value to for example the
degree of acceptance, awareness and skills within every increment [F. Von
Meyenfeldt, Basiskennis projectmanagement, Academic Service 1999].
Besides in the management of chance scope, increments are also usable in
the process modeling scope of implementation phases. Using increments can
align process models of business architectures and product software as
adding more detail in every increment of the phase draws both models
closer. The DSDM also has room for phased training, documentation and
reviewing.
The image below illustrates how implementation phases are supported by
the usage of DSDM, focusing on management of change, process modeling
and support.
Prince2
As DSDM does, the Prince2 method acknowledges implementation as a
phase within the method. Prince2 consists of a set of processes, of which 3
processes are especially meant for implementation. The processes of
controlling a stage, managing product delivery and managing stage
boundaries enable an implementation process to be detailed in with factors
as time and quality. The Prince2 method can be carried out iteratively but is
also suitable for a straight execution of the processes.

The profits for any implementation process being framed in a project

management framework are:
Clarity
An implementation framework offers the process to be detailed in with
factors such as time, quality, budget and feasibility.
Iterative, incremental approach
As explained, the possibility to execute different phases of the
implementation process iteratively enables the process to be executed by
incrementally aligning the product to be implemented with the end-user
(organization).
Assessments
Using an embedded method brings the power that the method is designed to
implement the software product that the method comes with. This suggests
a less complicated usage of the method and more support possibilities. The
negative aspect of an embedded method obviously is that it can only be
used for specific product software. Engineers and consultants, operating with
several software products, could have more use of a general method, to
have just one way of working.
Using a generic method like ERP modeling has the power that the method
can be used for several ERP systems. Unlike embedded methods, the usage
of generic methods enables engineers and consultants that operate in a
company where several ERP systems are implemented in customer
organizations, to adapt to one specific working method, instead of having to
acquire skills for several embedded models. Generic methods have however
the lack that implementation projects could become too situational, resulting
in difficulties and complexity in the execution of the modeling process, as
less support will be available.
Managing project delivery is essential to avoid the common problems of the
software solution not working as expected or crashing out due to multiple
users accessing the system at the same time. The keys to project delivery
are: successful implementation of the software, managing the business
change and scaling up the business use quickly.
Successful Implementation
Successful implementation of the software must be planned carefully. In
short there are two key options for delivering the software -- big bang or
phased release:
A "big bang" deployment or release software to all users at the same time
Phased deployment or release software to users over a period of time for
example by department or by geographical location. The project needs to
make a considered decision on the best way to release a software solution to
the business. Business will often choose a phased deployment, consequently
reducing project risk because if there is some problem the business impact is
reduced. In addition, the project deployment of software includes:
Cleanup of the "test" environment following successful completion of testing
Preparation of project deployment to the business such as setting up user
accounts to access the system and ensuring any lists of values have valid
values Deploying the software to the "production" environment ready for
normal business use. Plan and mechanism to back out of production
software deployment if the process goes wrong for some unexpected reason,
restoring the business to its pre-deployment state. Some of these ideas
have developed from IT Service Management and its discipline of Release
Management - for more background read: Release Management: Where to
Start? Project management should borrow and evolve good ideas whenever
needed.
Managing the Business Change of Project Delivery
Project deployment of the software to the business units such that they are
able to use it from a specified date/time is not enough by itself. Managing
the business change is an essential part of project delivery and that needs to
include:
Building awareness within the business of the software solution through
communication
Developing business support and momentum to use the solution through
stakeholder engagement Planning and executing the training plan for
business users and administrators
Business plan to exploit the use of the solution and to scale up the numbers
of users Setting up and operating a customer board to manage the evolution
of the solution
Software Maintenance
Software maintenance: Software maintenance in software engineering is
the modification of a software product after delivery to correct faults, to improve
performance or other attributes, or to adapt the product to a modified environment

Overview

This international standard describes the 6 software maintenance processes as:

The implementation processes contains software preparation and transition

activities, such as the conception and creation of the maintenance plan, the
preparation for handling problems identified during development, and the follow-up
on product configuration management.

The problem and modification analysis process, which is executed once the
application has become the responsibility of the maintenance group. The
maintenance programmer must analyze each request, confirm it (by reproducing
the situation) and check its validity, investigate it and propose a solution, document
the request and the solution proposal, and, finally, obtain all the required
authorizations to apply the modifications.

The process considering the implementation of the modification itself is classified

below.

The process acceptance of the modification, by checking it with the individual who
submitted the request in order to make sure the modification provided a solution.
The migration process (platform migration, for example) is exceptional, and is not
part of daily maintenance tasks. If the software must be ported to another platform
without any change in functionality, this process will be used and a maintenance
project team is likely to be assigned to this task. Finally, the last maintenance
process, also an event which does not occur on a daily basis, is the retirement of a
piece of software.

There are a number of processes, activities and practices that are unique to
maintainers, for example:

Transition: a controlled and coordinated sequence of activities during which a

system is transferred progressively from the developer to the maintainer;
Service Level Agreements (SLAs) and specialized (domain-specific) maintenance
contracts negotiated by maintainers;

Modification Request and Problem Report Help Desk: a problem-handling process

used by maintainers to prioritize, documents and route the requests they receive;

Modification Request acceptance/rejection: modification request work over a certain

size/effort/complexity may be rejected by maintainers and rerouted to a developer.

A common perception of maintenance is that it is merely fixing bugs. However,

studies and surveys over the years have indicated that the majority, over 80%, of
the maintenance effort is used for non-corrective actions (Pigosky 1997). This
perception is perpetuated by users submitting problem reports that in reality are
functionality enhancements to the system.

Software maintenance and evolution of systems was first addressed by Meir M.

Lehman in 1969. Over a period of twenty years, his research led to the formulation
of eight Laws of Evolution (Lehman 1997). Key findings of his research include that
maintenance is really evolutionary developments and that maintenance decisions
are aided by understanding what happens to systems (and software) over time.
Lehman demonstrated that systems continue to evolve over time. As they evolve,
they grow more complex unless some action such as code refactoring is taken to
reduce the complexity.

The key software maintenance issues are both managerial and technical. Key
management issues are: alignment with customer priorities, staffing, which
organization does maintenance, estimating costs. Key technical issues are: limited
understanding, impact analysis, testing, maintainability measurement.

Categories of maintenance in ISO/IEC 14764

E.B. Swanson initially identified three categories of maintenance: corrective,

adaptive, and perfective. These have since been updated and ISO/IEC 14764
presents:
Corrective maintenance: Reactive modification of a software product performed
after delivery to correct discovered problems.

Adaptive maintenance: Modification of a software product performed after

delivery to keep a software product usable in a changed or changing environment.

Perfective maintenance: Modification of a software product after delivery to

improve performance or maintainability. A type of maintenance that includes
reengineering, and is sometimes applied more broadly to include enhancement

Preventive maintenance: Modification of a software product after delivery to

detect and correct latent faults in the software product before they become
effective faults.Preventative Maintenance module. When combined, the two
modules work seamlessly to schedule, time release, and track preventative
maintenance and reoccurring work orders. Through a simple Windows interface,
you can inventory equipment, link specific tasks, and then schedule your
preventative maintenance tasks daily, weekly, monthly, quarterly, semi-annually,
and yearly. Preventative maintenance work orders are automatically printed out x
days prior to the due date for advance notice. Coherent Preventative Maintenance
is delivered with many standard reports, which allow you to accurately track your
preventative maintenance efforts.

Using corrective maintenance work plans to improve plant reliability

Preventive maintenance is generally considered to include both condition-

monitoring and life-extending tasks which are scheduled at regular intervals. Some
tasks, such as temperature and vibration measurements, must be done while the
equipment is operating and others, such as internal cleaning, must be done while
the equipment is shut down.

There is another, often overlooked, type of preventive maintenance inspection

which can not be scheduled at regular intervals. These inspections can and should
be done in conjunction with corrective maintenance.

Corrective maintenance is defined as maintenance work which involves the

repair or replacement of components which have failed or broken down. For failure
modes which lend themselves to condition monitoring, corrective maintenance
should be the result of a regular inspection which identifies the failure in time for
corrective maintenance to be planned and scheduled, then performed during a
routine plant outage.

When corrective maintenance is done, the equipment should be inspected to

identify the reason for the failure and to allow action to be taken to eliminate or
reduce the frequency of future similar failures. These inspections should be included
in the work plan.

A good example is the failure of packing in a process pump. Packing can be

monitored by checking leakage and the location of the gland follower, so repacking
should not normally be a fixed-time maintenance task. It should be done at
frequencies which depend on the operating context.

During the process of repacking the pump, there are a number of simple inspections
related to packing life which can be performed. These include:

Many of these inspections would not normally be done on a regular scheduled basis
and can only be done during repacking. In a well-managed maintenance system,
inspections that should be done during corrective maintenance for a specific failure
mode (such as packing failures) should be listed, recorded and used. So for any
work order to repack a pump, the above check list should be attached to or included
in the work order as a standard procedure. The standard should include
measurements appropriate to the specific equipment, such as the allowable sleeve
wear and the impeller clearance in the case of the process pump packing. A check
list similar to the one for pump packing can be developed for many failure modes
for common components, such as mechanical drives and hydraulic systems.
Integrating inspections that directly relate to failures into corrective maintenance
work plans is a powerful tool to improve plant reliability.

SOFTWARE MAINTENANCE

The process of modifying a software system or component. There are three classes.

Perfective maintenance incorporates changes demanded by the user; these may,

for example, be due to changes in requirements or legislation, or be for embedded
applications in response to changes in the surrounding system. Adaptive
maintenance incorporates changes made necessary by modifications in the
software or hardware (operational) environment of the program, including changes
in the ...

Preventive Maintenance

Preventive maintenance is a schedule of planned maintenance actions aimed at the prevention of

breakdowns and failures. The primary goal of preventive maintenance is to prevent the failure of
equipment before it actually occurs. It is designed to preserve and enhance equipment reliability by
replacing worn components before they actually fail. Preventive maintenance activities include equipment
checks, partial or complete overhauls at specified periods, oil changes, lubrication and so on. In addition,
workers can record equipment deterioration so they know to replace or repair worn parts before they
cause system failure. Recent technological advances in tools for inspection and diagnosis have enabled
even more accurate and effective equipment maintenance. The ideal preventive maintenance program
would prevent all equipment failure before it occurs.

Value of Preventive Maintenance

There are multiple misconceptions about preventive maintenance. One such misconception is that PM is
unduly costly. This logic dictates that it would cost more for regularly scheduled downtime and
maintenance than it would normally cost to operate equipment until repair is absolutely necessary. This
may be true for some components; however, one should compare not only the costs but the long-term
benefits and savings associated with preventive maintenance. Without preventive maintenance, for
example, costs for lost production time from unscheduled equipment breakdown will be incurred. Also,
preventive maintenance will result in savings due to an increase of effective system service life.

Long-term benefits of preventive maintenance include:

• Improved system reliability.

• Decreased cost of replacement.
• Decreased system downtime.
• Better spares inventory management.

Long-term effects and cost comparisons usually favor preventive maintenance over performing
maintenance actions only when the system fails.
When Does Preventive Maintenance Make Sense

Preventive maintenance is a logical choice if, and only if, the following two conditions are met:

• Condition #1: The component in question has an increasing failure rate. In other words, the failure
rate of the component increases with time, thus implying wear-out. Preventive maintenance of a
component that is assumed to have an exponential distribution (which implies a constant failure
rate) does not make sense!
• Condition #2: The overall cost of the preventive maintenance action must be less than the overall
cost of a corrective action. (Note: In the overall cost for a corrective action, one should include
ancillary tangible and/or intangible costs, such as downtime costs, loss of production costs,
lawsuits over the failure of a safety-critical item, loss of goodwill, etc.)

If both of these conditions are met, then preventive maintenance makes sense. Additionally, based on the
costs ratios, an optimum time for such action can be easily computed for a single component. This is
detailed in later sections.

Literature Survey
1. INTRODUCTION

Java is an Object-Oriented, multi-threaded programming language developed

by Sun Microsystems in 1991. It is designed to be small, simple and portable.
The popularity of the Java is due to 3 key elements powerful programming
language, applets and rich set of significant object classes.

Adv of Java

1. Simple
2. Secure
3. Portable
4. Object Oriented
5. Robust
6. Multithreaded
7. Interpreted
8. High Performance
9. Distributed
10. Dynamic

Components of JVM

In Java development environment, there are two parts, a Java compiler and
Java interpreter. Java compiler generates byte code and interpreter executes
the Java program. Eventhough the bytecode is slow, it gives platform
independent application.
Java program is typed in and saved in a file with extension .java. This file is
compiled by javac. It creates a file with .class extension. This is executed by
Java file without extension. A simple example for a Java program is

Type casting:

When one type of data is assigned to be another type of variable, an

automatic type conversion will take place. For example

byte a=10; int c = a + 10;

Here, a is converted to int automatically.

To manually convert a type use (type) value

For example float f = (float) a/ float(b) ; if a, b are integers.

Operators

1) Arithmetic - + - * / %

2) Relational - < > <= >= !=

3) Logical - && || !=

4) Assignment - =

5) Comparision - = =

6) Incre/Decrement - ++ --

7) Bitwise operator - ~ & | ^ >> >>> << &= != ^=

8) Conditional - ? :

2. PROGRAM CONSTRUCST

They are divided into

i. Sequence
 ii. Selection - if, switch
iii. Iteration - while, do..while, for

Misc - break, exit, continue, and return

e) break, continue and exit

break will transfer the control out of the loop, in continue , the rest of the
lines are ignored and loop continue after the next iteration. The exit function
will stop the program execution.

3. CLASSES AND METHODS

Classes

The most important feature of the OOP is classes. A class defines the shape
and behavior of an object and is a template for multiple object with similar
features. It is a logical construct upon which the entire java language is built
because it defines the shape and nature of the object.

To create a class, a source file with the class keyword in it, followed by a
name and pair of curly braces for the body.

Once class is created, an instance of class is created by new keyword. The

instance of class is used to access the variables and methods that form part
of the class. The dot operator is used to get the value of the class variable
(object.variable).

Instance Variable : Data is encapsulated in a class by declaring varables

inside the class declaration. Variables declared in this scope are called as
Instance variables.

Class Variable : Class variables are global to class and all the instances of the
class. To declare class variable static keyword is used.

The access of class may be public, private, abstract or final.

Methods

Methods are functions that operate on instances of classes in which they are
defined. Method definition has four parts. They are name of the method,
return type , list of parameters and body of the method.
Access Specifiers:

Public : If any method or variable is declared as public, it is

visible to all

classes.

Private : If any method or variable is declared as private , it is visible to

classes in which it is declared.

Protected : It is visible in class and all its subclasses.

Package : It is indicated by the lack of any access modifier in a declaration.

It has an increased protection and narrowed visibility.

Final : It can not overridden by subclass

Abstract : in abstract class without body, must be overridden by subclass.

Static : It is automatically called when creating instance of class.

this:

The this keyword is used inside any instance method to the current object.

Constructor

A constructor method is a special kind of method that determines how

an object is initialized when created. They have the same name as the
class but do not have any return type. Consturctor can also be
overloaded.

Garbage collection

When no reference to object exits, the object no longer needed, the memory
occupied by the object is reclaimed. This is called garbage collection. Java
periodically does garbage collection.

Finalizer :

Finalizer method is the exact opposite of constructor method. They are called
just before the object is garbage collected and its memory is reclaimed. All
cleanup operations are performed in this method.
protected void finalize( )

{}

Methods overloading

Methods overloading is creating different methods with same name but with
different parameters. This is the one type of creating polymorphism in Java

Example for method overloading and constructor overloading

Method Overriding

Method overriding is creating a method in the derived class that has the
same name arguments as in the superclass. This new method hides the
superclass method.

Recursion

Recursion is the process of defining something in terms of itself. A method

that calls itself is said to be recursive.

Nested Class

It is possible to nest a class definition within another and treat the nested
class like any other method of that class. An inner class is a nested class
whose instance exists within an instance of its enclosing class and has direct
access to the instance members of its enclosing instance.

4. Inheritance

Inheritance is the method of creating new class based on the already

existing class. The new class derived is called as sub class or derived class
which has all features of the existing class and its own. The existing class is
called as super class or base class.

Adv : reusability of code, accessibility of variables and methods of the base

class

by the derived class.

If the class is derived from more than one class , then it is called as multiple
inheritance. This is not available in Java. To overcome this problem use
interface.

Method Overriding

Whenever there are methods of the same name both in the base class as
well as in the derived class and if that method is called by main, the method
in the derived class is always executed. This is called overriding. See
example11.

Super

Super has two forms. First it calls the superclass’s constructor. The second is
used to access a member of the superclass that has been hidden by a
member of a subclass.

Final

a. final variables - to create constant

final float pi =3.14f;

final int a = 40

final is used to create constant variable.

b) final modifiers - to prevent overriding

Final modifiers are those to which no further alteration can be made. We can
not override the method using final

Abstract

Sometimes we will want to create a superclass that only defines a

generalized form that will be shared by all of its subclasses, leaving it to
each subclass to fill in the details. To declare abstract class

abstract type name(parameters);

We must override the abstract method. An abstract class cannot be directly

instantiated with the new operator. We cannot declare abstract constructors
or abstract static methods.
5. Exception

An exception is an abnormal condition or error that occurs during the

execution of the program. Exception in java is handled by five keywords –
try, catch, finally, throw and throws.

The object class has a subclass called Throwable to handle exception and
errors, which has two subclasses Exception and Error.The classes of
exception are IOException and RuntimeExveption

The try and catch fixes the error and prevents the program from terminating
abruptly. The finally block will be executed if no catch matches it and always
executed. If you use try block, finnaly block or atleast one catch block should
be used.

If you don't want to use try and catch statements then use throws clause.
The throws class is responsible to handle the different types of exceptions
generated by the program. This clause usually contains a list of types of
exceptions that are likely to occur in that program.

The throw clause is used to call exception explicitly. User defined exception
can be called by throw clause. User defined exception is created by
extending the class Exception.

6. Package

Package contains set of classes in order to ensure that class names are
unique. Packages are container of classes used to keep the class name space
compartmentalized.

1. Create a subdirectory, which has the same name as package.

2. Include package command, along with the package name, as first
statement in the program.
3. Write class declaration
4. Save file in this directory as "name of class.java"
5. Compile this file using javac.
6. To use this program set the CLASSPATH or change to previous
directory and use java packname.classname

If Java source file contain package, interface, classes then the order should
be

a. A single package statement (optional)

b. Any number of import statements (optional)
 c. A single public class declaration (required)
d. Any number of classes private to the package (optional)

6. Interfaces :

An interface is a collection of abstract behavior that individual classes can

implement. An interface consists of set of method collections. Using
interface, you can specify what a class must do but not how it does it. All
methods and final variables in interface must be public.

Multithreading is not available in Java. To overcome this problem, interface is

introduced.

8. Multhithreading in Java

Thread

A process is a program in a execution. A thread is a line of execution. Two or

more processes running concurrently in a computer is called multitasking.
The process can contain multiple threads to execute its different sections.
This is called multhreading. Using this, we can run different parts of the
programs at a time.

States of thread

There are four states of thread. They are new, runnable, blocked and dead
The fig shows the states of the thread.

Adv of thread:

• Can be created faster

• Maximum use CPU time
• Requires less overhead
• Interprocess communication is faster
• Context switching is faster
Thread is created by

a) the class Thread which has the interface Runnable.

b) creating the objects of the class Thread

a) Using runnable interface

class c1 implements Runnable

To create a thread

Thread t = new Thread(this) ;

Thread t = new Thread(this,"Demo thread’);

Where this referes the Applet object.

After thread is created , it will first execute start( ) method then

run( ) method is automaticall called.

b) Creating Thread Class Objects

Runnable abstracts a unit of executable code. We can construct a thread on

any object that implements Runnable.

The thread methods are start( ), resume( ), sleep( ), suspend( ) , join( ) and
toString( )

.Synchronization

Two or more threads accessing the same data simultaneously may lead to
loss of data integrity. Java uses the concept of monitor. A monitor is an
object, used as a mutually exclusive lock.

Java offers interprocess communication through the use of wait( ), notify( )

and notifyall( ) methods of Object class and all are synchronized methods.

Thread Priorities
The usage of setPriority( ) and getPriority( ) methods are used to set and get
the priorities of thread respectively. The yield( ) method enables provision of
CPU’s time to threads with equal priority and prevents monopolization of a
single thread. The Thread has final variables declared line – NORM_PRIORITY
(5), MINIMUM_PRIORITY (1) and MAXIMUM_PRIORITY (10).

9. APPLET

Applet

An applet is a dynamic and interactive program that can run inside Web
page displayed by a Java-capable browser or applet viewer.

All applets are subclasses of Applet. You should import java.applet and
java.awt since all applets run in a window. Applet defines three interfaces
Appletcontext, AppletStub and AudioClip.

Applet extends java AWT class Panel, Panel extends Container which extends
Component.

The init( ) Method

This method gets called as soon an applet is started. Initialization of all

variables, creation of objects, setting of parameters, etc. can be done in this
method.

The start( ) method

This method is executed after the init mehod. Also used to restart the applet
that was stoped.

The stop( ) method

This method is used to halt the running of an applet. This method is called
when a web browser leaves the HTML document containing the applet.

The destroy( ) method

This method is used to free the memory occupied by the variables and
objects initialized in the applet. Called by the browser just before the applet
is terminated.

The paint( ) method

This method helps in drawing, writing and creating a colored background or
an image on to the applet. This method is called each time your applet’s
output must be redrawn. It has one parameter called Graphics.

The repaint( ) method

This method is used in case an applet is to be repainted. The repaint method

calls update( ) method to clear screen and paint( ) method to redraw the
contents of the current frame.

resize (width, height)

Resize the applet window

showStatus (str)

Displays the string in the status window of the applet

When starting the applet init, start, paint methods and when terminating
stop and destroy methods are called.

9.a. The Graphics Class in java.awt package

drawString(message,x,y);

9.b. Font Class in java.awt package

Font f = new Font ("fontname", format, size);

Formats are Font.BOLD, Font.ITALIC, and Font.PLAIN

g.setFont(f)

9.c. Color Class in java.awt package

Color.grey, Color.green, Color.yellow, Color.pink, Color.red, Color.blue,

Color.magenta, Color.cyan

9.d. Images

Clipping

A technique by which the drawing area can be restricted to a small portion of

the screen.

Method is clipRect( )
clipRect(x1,y1,x2,y2);

Animation

Animation is technique by the object is moved on the screen In which the

original image is clreared and placed in another place.

9.e. Events

Mouse Events methods

boolean mouseDown(event , x, y)

boolean mouseDrag(event , x, y)

boolean mouseEnter(event , x, y)

boolean mouseExit(event , x, y)

boolean mouseMove(event , x, y)

boolean mouseUp(event , x, y)

boolean mouseDown(event , x, y)

boolean mouseDown(event , x, y)

KeyBoard Events

boolean keyDown(event , x, y)

boolean keyUp(event , x, y)

Types of Event handling

a)Low Level event

Low level classes Low level event Listener

ComponentEvent ComponentListener

FocusEvent FocusListener
KeyEvent KeyListener

ContainerEvent ContainerListener

MouseEvent MouseListener

MouseMotionListener

WindowEvent WindowListener

InputEvent

b) Semantic Events

Low level classes Low level event Listener

ActionEvent ActionListener

AdjustmentEvent AdjustmentListener

ItemEvent ItemListener

TextEvent TextListener

Each component class in the AWT has one addXXXListener( ) method for
each event type.

9.f. ABSTRACT WINDOW TOOLKIT (AWT)

Component Contructor Methods

Button

Button( ) setLabel(String)

Button("label") getLabel( )

Label

Label( ) getText( )

Label(String) setText(String)

Label(String, int) getAlignment( )

SetAlignment(int)
where Int is alignment. It may be Label.LEFT, Label.RIGHT, Label.CENTER

Checkbox

Checkbox( ) setLabel(string)

Checkbox(String) getLabel( )

Checkbox(String,grp,boolean) setState(boolean)

getLabel( )

Choice

Choice( ) getItem(int)

addItem(String) getItemcount( )

getSelectedItem( )

getSelectedIndex( )

TextComponent

TextField( ) getText( )

TextField(String, int) setText(String)

TextArea( )

TextArea(String, int, int) int represents rows and columns

List

List( ) getItem(int) int starts from 0

List(int,boolean) getItemCount( )

AddItem(String) select(int)

getSelectedItem( )

Scrollbar

Scrollbar( ) setValue(int)
Scrollbar(orient, value, visible, min, max) getValue( )

Layout Manger

A set of classes used to position the components in a container.

a. FlowLayout
b. BorderLayout
c. GridLayout

First create instantiate a layout manager class and use setLayout( ) method

Flow Layout

Lays components linewise from left to right

FlowLayout( )

FlowLayout(align, hgap, vgap)

Align – FlowLayout.LEFT, FlowLayout.RIGHT, FlowLayout..CENTER

Grid Layout

Position the components in the cellf of the grid.

GridLayout(int rwo, int col)

GridLayout( int rwo, int col, int hgap, int vgap)

Border Layout

Lays components relative to the edges of the container

BorderLayout( )

BorderLayout(int hgap, int vgap)

add("direction",item);

direction may be NORTH, SOUTH,EAST , WEST or CENTER

Insets(int, int, int, int)

Used to give spacing around the container

Panel

A panel class is a non-abstract, recursively nestable container.

Panel( )

9.g. Frames, Menus and Dialogs

Frame

11. Networking in Java

Java.net package

The objectives are

Network Datagram

Protocol DatagramPacket

Socket DatagramSocket

Client/Server TCP/IP

Internet (IP) Address Socket

Domain Name Service ServerSocket

InetAddress URL

Network is a set of computers physically connected together. It enables the

sharing of computer pheriperals and resources by different computers.

The communication between the computers requires certain set of rules

called protocols. Some important protocols are TCP/IP, HTTP, FTP, SMTP and
NNTP. Port no 21 is for FTP, 23 is for Telnet, 25 is for e-mail and 80 is for
HTTP.

IP is a low-level routing protocol that breaks data into small packets and
sends them to an address across a network. TCP is a higher level protocol
that manages string together these packets, sorting and retransmitting them
to reliably transmit your data. UDP (user Datagram Protocol) can be used to
support fast, connectionless, unreliable transport of packets.
Socket is the place used to plug in just like electric sockets, from the socket
the communication starts.

Client is the machine, which sends some request to another computer. The
computer that does the request is called the Server.

A proxy server speaks the client side of protocol to another server. A client
would connect to a proxy server, which have no restrictions, and the proxy
server would in turn communicate for the client.

Every computer connected to the network has unique address it contains

four numbers between 0 and 255 separated by period. Ex is 80.0.0.50

It is very difficult to remember the IP of the computer. To overcome this

problem domain name service (DNS) is used. It maps the IP address by string
of characters. Ex is www.microsoft.com

InetAddress is a class, which is used to encapsulate IP address and DNS.

InetAddress getLoaclHost( ) throws unknowHostException

InetAddress getByName (String hostName)

InetAddress getAllByName (String hostName)

URL

Uniform Resource Locater. It contains four parts protocol, separated by :

and //, host name of IP address, port number, file path.

For ex http://www.starwave.com/index.html

Constructors of URL throws MalformedURLException

URL (String urlspecifier)

URL (String protocolName, String hostName, int port,String path)

URL (String protocolName, String hostName, String path)

getPort( ), getHost( ),getFile( ) and toExternalForm( )

To access content information of a URL, use url.openConnection( ) method.

Datagrams

Datagrams are bundles of information passed between machines. It contains

two classes

DatagramPacket for container of data

DatagramSocket for send or receive the DatagramPacket

DatagramPacket constructors are

DatagramPacket (byte data[ ], int size);

DatagramPacket (byte data[ ], int size, ipAddress, int port);

Methods of DatagramPacket are

InetAddress getAddress( ), int getPort( ) , byte( ) , getData( ) and

int getLength( )

DatagramSocket constructors are

DatagramSocket.send (DatagramPacket d);

DatagramSocket.receive (DatagramPacket p);

client.java

import java.net.*;

class client

public static DatagramSocket ds;

public static byte buffer[] = new byte[1024];

public static void main(String arg[]) throws Exception

ds = new DatagramSocket(6);

while(true)
{

String a;

DatagramPacket p = new DatagramPacket(buffer,buffer.length);

ds.receive(p);

a=new String(p.getData(),p.getLength(),1);

if (a.equals("q"))

System.out.println("Server response is shut off now");

return;

System.out.println(new String(p.getData(),0,p.getLength()));

server.java

import java.net.*;

class server

public static DatagramSocket ds;

public static byte buffer[] = new byte[1024];

public static void main(String a[]) throws Exception

InetAddress ia = InetAddress.getByName("rad-tm-04");
System.out.println(ia);

ds = new DatagramSocket(123);

int pos=0;

while(true)

int c = System.in.read();

switch(c)

case 'q':

System.out.println("Server quits");

return;

case '\r':

break;

case '\n':

ds.send(new DatagramPacket(buffer,pos,ia,456));

pos=0;

break;

default:

buffer[pos++] = (byte) c;

}
TCP/IP

TCP/IP sockets are used to implement reliable, bidirectional, persistent, point

to point, stream based connection between hosts on the Internet.

It contains two classes. They are Socket and ServerSocket. ServerSocket

class is designed to wait for clients to connect and Socket class is used to
connect to ServerSocket.

ServerSocket (int port)

ServerSocket (int port, int maxqu)

ServerSocket (int port, int maxqu, InetAddress localAddress)

ServerSocket has a method accept( ) that waits for client to initiate

communication.

Socket (String hostName, int port)

Socket (InetAddress ipAddress, int port)

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

12. JDBC-ODBC

JDBC is a set of Java API for executing SQL statements.

Two-Tier Model

Client Machine
DBMS propictary protocol

Database server

Three-Tier Model

Client Machine(GUI)

HTTP, RMI, CORBA

Server Machine

DBMS-proprictary protocol

Database Server

Two-Tier Model

In Two-Tier Model, a Java applet or application talks directly to the database.

This requires a JDBC driver that can communicate with the particular
database management systems accessed. Users SQL statement is delivered
to the database and the results of those statements are sent to the user.
This is referred to as client/server configuration.

Three-Tier Model

In this a middle tier is introduced for fast performance. It sends the SQL
statements to the databases. The results of the query are send to middle
tier, which sends them to user.

1. getConnection( ) of DriverManager class is used to get connection

object.
2. It prepares Statement Object to prepare SQL statement
3. The method executeQuery( ) is used to obtain ResultSet and the
method executeUpdate( ) is used to for deleting, updating or inserting
records.
4. rollback( ) and commit( ) are used to undo or permanent save the
changes.
Example :

a) Create a data base students in Ms-Access with table student containing

the following fields studid number, sname text, course text and marks
number.

a. Create a datasource studentdsn in ODBC for the above database

b. Write the source file , compile and execute it.

import java.sql.*;

class dbappn

static connection con;

public static void main(String a[ ]) throws Exception

class.forName("sun.jdbc.odbc.JdbcOdbcdriver");

open( );

select( );

insert( );

delete( );

update( );

select( );

close( );

static void open( ) throws SQLException

/*con = DriverManger.getConnection("dsn","username","pwd"); */
con = DriverManager.getConnection("jdbc:odbc:student","palani","kumar");

con.setAutoCommit(false);

static void close( ) throws SQLException

con.commit( );

con.close( );

static void select( ) throws SQLException

Statement stmt = con.createStatement( );

ResultSet rs = stmt.executeQuery("Select * from student");

Boolean more = rs.next( );

If (!more)

System.out.println("No rows found");

Return ;

while(more)

System.out.println("ID " : " + rs.getString("studid"));

System.out.println("Name : " + rs.getString("sname"));

System.out.println("Course : " + rs.getstring("course"));

System.out.println("Marks : " + rs.getString("marks"));

more = rs.next( );

rs.close( );

stmt.close( );

static void insert( )

try{

Statement stmt = con.createStatement( );

int rows = stmt.executeUpdate("Insert

into student

values(100, ‘Subash’,’Java’,80)");

con.commit( );

stmt.close( );

System.out.println(rows + " row added");

} catch(SQLException s) { System.out.println("Error"); }

static void delete( )

try{

Statement stmt = con.createStatement( );

int rows = stmt.executeUpdate("Delete

from student
 where id = 100;

con.commit( );

stmt.close( );

System.out.println(rows + " row deleted");

} catch(SQLException s) { System.out.println("Error"); }

static void update( )

try{

Statement stmt = con.createStatement( );

int rows = stmt.executeUpdate("Update

student

set marks = 90 where id =100 ;

con.commit( );

stmt.close( );

System.out.println(rows + " row added");

} catch(SQLException s) { System.out.println("Error"); }

13. Remote Method Invocation (RMI)

RMI allows java object that executes on one machine to invoke a method
that executes on another machine. This is the one method of creating
distributed application.

Steps to create client/server application using RMI

 1. Write source code for interface, server and client program and compile
them.
2. Generate Stubs and Skeletons classes by compiling server program
using RMI compiler
3. Install files on client and server machines.
4. start rmiregistry on server machine to map server name to object
reference
5. Execute the server program by java server.
6. Execute the client program on client machine by java client localhost
args

inter.java

import java.rmi.*;

public interface inter extends Remote

public void getdata(int m,int n) throws RemoteException;

int adddata() throws RemoteException;

client.java

import java.rmi.*;

public class client

public static void main(String arg[])

try

{
int a = Integer.parseInt(arg[1]);

int b = Integer.parseInt(arg[2]);

int result;

inter i = (inter) Naming.lookup("rmi://" + arg[0] + "/Addserver");

System.out.println("client");

i.getdata(a,b);k

result = i.adddata();

System.out.println(result);

}catch(Exception e)

System.out.println("error " + e);

server.java

vbnm,import java.rmi.*;

import java.rmi.server.*;

public class server extends UnicastRemoteObject implements inter

int x,y;

public server() throws RemoteException

{
}

public int adddata() throws RemoteException

return x+y;

public void getdata(int m, int n) throws RemoteException

x=m; y=n;

public static void main(String arg[])

try

server s = new server();

Naming.rebind("Addserver",s);

catch(Exception e)

System.out.println("Exception e");

}
Comp Constructor Methods

JLabel(Icon I) Icon getIcon( )

JLabel(String s) String getText( )

label
JLable(String s, Icon I, int align) void setIcon(Icon I)

void setText(String
s)

JTextField( )

JTextField(int cols)
Text Field
JTextField(String s)

JTextField(String s, int cols)

JButton(Icon i)

Buttons JButton(String s)

JButton(String s, Icon I)

JCheckBox(Icon I)

JCheckBox(String s)

CheckBox JCheckBox(Icon I, boolean)

JChcekBox(String s, boolean)

JCheckBox(String s, Icon I, boolean)

JRadioButton(Icon I)

JRadioButton(String s)
Radio
Buttons
JRadioButton(String s, boolean)

JRadioButton(s, I, boolean)

Combo JComboBox( )
Box
 JComboBox(Vector v)

Tabbed JTabbedPane( ) addTab(title,

Panes comp)

JScrollPane(comp)
Scroll
JScrollPane(int vsb, int hsb)
Panes
JScrollPane(comp, vsb, hsb)

JTree(HashTable h)

JTree(Object ob[])
Trees
JTree(TreeNode t)

JTree(Vector v)

JTable(Obect data[][], Object

Tables
colheads[])

Icons

Method

Int getIconHeight( )

int getIconWidth( )

void paintIcon(comp, Graphics, x, y)

void setDisabledIcon(icon)

void setPressedIcon(icon)

void setSelectedIcon(icon)

void setRolloverIcon(icon)
Scroll Panes

JScrollPane(comp, vsb, hsb)

The vsb, hsb constants are

ScrollPaneConstants.HORIZONTAL_SCROLLBAR_ALWAYS

ScrollPaneConstants.HORIZONTAL_SCROLLBAR_AS_NEEDED

ScrollPaneConstants.VERTICAL_SCROLLBAR_ALWAYS

ScrollPaneConstants.VERTICAL_SCROLLBAR_AS_NEEDED

Example :

import javax.swsing.*;

import java.awt.*;

public class Jlabel extends JApplet

public void init( )

Container cp = getContentPane( );

ImageIcon ii = new ImageIcon("Birds");

JLabel jl = new JLabel("Birds",ii,JLabel.Center);

Cp.add(jl);

}
}

Example :

import javax.swing.*;

import java.awt.*;

public class jscroll extends JApplet

public void init( )

Container CP = getContentPane( );

Jpanel jp = new Jpanel( );

jp.setLayout(new GridLayout(20,20));

int b = 0;

for(int ii = 0; I<20; I++)

for(k=0;k<20;k++)

jp.add(new JButton("Button " + b));

b++;

}
 int v = ScrollPaneConstants.VERTICAL_SCROLLBAR_AS_NEEDED

int
h=ScrollPaneConstants.HORIZONTAL_SCROLLBAR_AS_NEEDED;

JScrollPane jsp = new JscrolPane(jp, v, h) ;

CP.add(jsp, BorderLayout.CENTER);

Example :

Servlets

Servlets are small programs that execute on the server side of a Web
connection, used to extend the functionality of a Web Server.

JSDK

Java Servlet Development Kit (JSDK) contains class libraries to create

servlets. It contains the utility servletrunner to test the servlets. The basic
life cycles of servlets are init( ), service( ) and destroy( ). The steps to create
a servlets are

1. Create and compile the servlet source code.

2. Start the servletrunner utility.
3. Start a Web browser and reuest the servlet.

Adv of servlets over CGI :

o Performance is better. Creating a separate process to handle

each client reuest isn't necessry.
o Servlets are platform-independent, because they are written in
Java.
o The Java Security Manager on the server enforces a set of
restrictions to protect the resources on a server machine.
o The full functionality of Java class is available to the servlet. It
can communicate with applets, databases or other software via
sockets and RMI.
The javax.servlet package

Interfaces Class Methods

Servlet GenericServlet Init(ServletConfig sc )

Service(ServeltRequest
ServletRequest ServletInputStream
req, ServletResponse res

ServletResponse ServletOutputStream void destroy( )

ServletConfig
ServletConfig ServletException
getServletConfig( )

ServletContext UnavailableException

SingleThreadModel

The first two methods throws SerlvelException

The javax.servlet.http Package

Interface Class

HttpServletRequest Cookie

HttpServletResponse HttpServlet

HttpSession HttpSessionBindingEvent

HttpSessionBindingListener HttpUtils

HttpSessionContext

Example :
Step 1 : colorGet.html

<html>

<body>

<center>

<form name ="form1" method ="get"

action=<http://localhost:8080/servlet/colorGetServlet">

<B> color : </B>

<Select name="color" size="1">

<option value = "Red"> Red </option>

<option value="Blue"> Blue </option>

</select>

<br> <br>

<input type = submit value="submit">

</form>

</body>

</html>

Step 2 : colorGetSelvlet.java

import java.io.* ;

import javax.servlet.*;

import javax.servlet.http.*;

public class colorGetServlet extends HttpServlet

{
public void doGet (HttpServlet request, HttpServletResponse response)

throws ServletException, IOException

String color = request.getParameter("color");

response.setContentType("text/html");

PrintWriter pw = response.getWriter( );

pw.println("<B> The selected color is : " );

pw.println(color);

pw.close( );

Step 3: compile the above program colorGetServlet.java

Step 4 : start servlet runner by c:\javawebbrowser2.0\jserv

Step 5: Display the web page in the browser. Select a color and submit.

ORACLE:

Structured Query Language (SQL) is the language used to manipulate

relational databases. SQL is tied very closely with the relational model.

In the relational model, data is stored in structures called relations or tables.

SQL statements are issued for the purpose of:

• Data definition:
 Defining tables and structures in the database (DDL used to create,

alter and drop schema objects such as tables and indexes).

• Data manipulation:

Used to manipulate the data within those schema objects (DML

Inserting, Updating, Deleting the data, and Querying the Database).

A schema is a collection of database objects that can include: tables, views,

indexes and sequences

List of SQL statements that can be issued against an Oracle database schema

are:

• ALTER - Change an existing table, view or index definition (DDL)

• AUDIT - Track the changes made to a table (DDL)

• COMMENT - Add a comment to a table or column in a table (DDL)

• COMMIT - Make all recent changes permanent (DML - transactional)

• CREATE - Create new database objects such as tables or views (DDL)

• DELETE - Delete rows from a database table (DML)

 • DROP - Drop a database object such as a table, view or index (DDL)

• GRANT - Allow another user to access database objects such as tables

or views (DDL)

• INSERT - Insert new data into a database table (DML)

• No AUDIT - Turn off the auditing function (DDL)

• REVOKE - Disallow a user access to database objects such as tables

and views (DDL)

• ROLLBACK - Undo any recent changes to the database (DML -

Transactional)

• SELECT - Retrieve data from a database table (DML)

• TRUNCATE - Delete all rows from a database table (can not be rolled

back) (DML)

• UPDATE - Change the values of some data items in a database table

(DML)

4.9.1 Oracle Installation:

1. In the Oracle CD double click on the setup.exe program to get the

installation process started.

The following Welcome window will appear:

2. Click on the Next button to move to the File Locations.

3. In this the Source and Destination locations must be selected.

For the Destination, leave the Oracle Home named OraHome81 as the

default.

Choose a hard disk drive that has at least 2 gigabytes of free space. In

the example here, we are using the C: drive.

Leave the \Oracle\Ora81 path as it is (the default).

Click on the Next button to load the Product information. This may

take up to 2 minutes (depending on the speed of the machine).

4. Once the product information has been read, the following 3 "Available

Products" options are presented:

• Oracle 8I Typical Installation.

• Oracle 8I Minimal Installation.

• Oracle 8I Custom Installation.

 Make sure the "Oracle8i Typical Installation" is selected and click on

the Next button.

5. The "Type of Starter Database" screen will appear next

Make sure the "Standard Starter Database" option is selected and click

on the Next button to continue.

6. The next step is to identify the database using the Global database

name.

Leave this as the default. Make a note of the following:

Oracle SID is ORCL

Global Database Name is oracle

7. Click on the Next button to continue to the "Location of

Documentation" screen. In this step, you need to select where the

Oracle documentation will reside. If we have the extra free space on

our hard disk (140MB or so), then choose the "Hard Disk" option.

Otherwise, choose the "CD-ROM" option and links will be made to the

Oracle 8i CD-ROM for documentation support. This means that in order

to view Oracle documentation, we need to have the CD in the CD-ROM

drive.

8. Click on the Next button to move to the "Summary" screen:

In this, the products and files that will be installed are summarized.

Click on the Install button to begin the installation.

9. Once the installation is completed, the last step is to exit the

installation and then reboot the computer.

Administratorlogin
ADMINISTRATION.ASPX
DOCTOR REGISTRATION FORM
RECEPTIONIST REGISTRATION FORM
LABORATOR REGISTRATION FORM
EMPLOYEE REGISTRATION FORM
RECEPTIONIST LOGIN
PATIENT ADMIT FORM
LABORATOR LOGIN
LABORATOR PAGE
DOCTOR LOGIN
DOCTOR’S PAGE
Conclusion
Conclusion:

Patient Records Monitoring system is a stand alone application which

enables the management to store the patient’s records effectively. The
application is not only storing the records but also keep the history of the
patient. In developing this project I established 3 modules which are inter
related each other. To develop this project the project team has used web logic server as an
application server and oracle database server as backend. There are basically two types of
modules are developed by the front end programmers. These are input modules and out put
modules. The module which helps the user to input the data, modify the data and delete the data
will be called the input modules.

• The project has been appreciated by all the users.

• It is easy to use, since it uses the GUI provided in the user dialog.

• User friendly screens are provided.

• The usage of software increases the efficiency, decreases the effort.

• It has been efficiently employed as a Site management mechanism.

• It has been thoroughly tested and implemented.

BIBLIOGRAPHY
Title of Book Author

name

 “Java the Complete Reference

 “Thinking in c# Bruce Eckel

 “Software Engineering Concepts”

Pessman

 “Object Oriented Analysis and Design” Ram

Baugh

Websites
 www.datagridgirl.com

 www.dotnetuncle.com

 www.Codeproject.com