Professional Documents
Culture Documents
S.No
Contents
1.
Introduction
2.
Project Objective
3.
System Specification
System Configuration
Software Specification
4.
System Analysis
Existing System
Proposed System
5.
System Design
Input Design
Output Design
6.
Database Design
7.
Dataflow Diagram
8.
System Testing
9.
Sample Codings
10.
Screenshots
11.
Bibiliography
12.
Webiliography
INTRODUCTION
This project will automate the daily operations of LIFE LINE hospital.
The project keeps track of the staff and patient (in-patient, out-patient) details. It
also takes care of the ward, medical, invoice and the doctors appointment
details. The system generates the daily ward availability, the status of the
operation theatres and ICU.
HOSPITAL MANAGEMENT is an integrated Hospital Information
System, which addresses all the major functional areas of multi-specialty
hospitals. The HOSPITAL MANAGEMENT enables better patient care, patient
safety, patient confidentiality, efficiency, reduced costs and better management
information system. It provides easy access to critical information thus enabling
the management to take better decisions on time.
This project deals with processing of each and every department in the
hospital. This project sincerely aims to reduce the manual processing of each
department.
The Scope of the project takes care of the details of each and every
department. These details gives the doctor, staffs, specialists and patient details
including their salary,
system. The details of Doctor and staff help the hospital to maintain the record
of every person. Their attendance details help them to know about their attentive
presence while salary is calculated. The billing system provides an efficient way
for calculating bill details of the patients.
PROJECT OBJECTIVE
MODULES REQUIRED
public class Hello extends JFrame {
public Hello() {
super("hello");
super.setDefaultCloseOperation(WindowConstants.EXIT_ON_CLO
SE);
super.add(new JLabel("Hello, world!"));
super.pack();
super.setVisible(true);
}
The Hello() constructor initializes the frame by first calling the superclass
constructor, passing the parameter "hello", which is used as the window's title. It
then calls the setDefaultCloseOperation(int) method inherited from JFrame to
set the default operation when the close control on the title bar is selected to
WindowConstants.EXIT_ON_CLOSE this causes the JFrame to be disposed
of when the frame is closed (as opposed to merely hidden), which allows the
Java virtual machine to exit and the program to terminate. Next, a JLabel is
created for the string "Hello, world!" and the add(Component) method inherited
from the Container superclass is called to add the label to the frame. The pack()
method inherited from the Window superclass is called to size the window and
lay out its contents.
The main() method is called by the Java virtual machine when the
program starts. It instantiates a new Hello frame and causes it to be displayed by
calling the setVisible(boolean) method inherited from the Component superclass
with the boolean parameter true. Once the frame is displayed, exiting the main
method does not cause the program to terminate because the AWT event
dispatching thread remains active until all of the Swing top-level windows have
been disposed.
Generics[edit]
Main article: Generics in Java
In 2004, generics were added to the Java language, as part of J2SE 5.0.
Prior to the introduction of generics, each variable declaration had to be of a
specific type. For container classes, for example, this is a problem because there
is no easy way to create a container that accepts only specific types of objects.
Either the container operates on all subtypes of a class or interface, usually
Object, or a different container class has to be created for each contained class.
Generics allow compile-time type checking without having to create a large
written largely in C, the Android SDK uses the Java language as the basis for
Android applications. However, Android does not use the Java virtual machine,
instead using Java bytecode as an intermediate step and ultimately targeting
Android's own Dalvik virtual machine.
Android also does not provide the full Java SE standard library, although
the Android class library does include an independent implementation of a large
subset of it. This led to a legal dispute between Oracle and Google. On May 7,
2012, a San Francisco jury found that if APIs could be copyrighted, then Google
had infringed Oracle's copyrights by the use of Java in Android devices.[42]
District Judge William Haskell Alsup ruled on May 31, 2012, that APIs cannot
be copyrighted,[43] but this was reversed by the Ninth Circuit Court of Appeals
in May 2014.[44][45]
Class libraries[edit]
Question book-new.svg
This section does not cite any references or sources. Please help improve
this section by adding citations to reliable sources. Unsourced material may be
challenged and removed. (May 2013)
Main article: Java Class Library
The Java Class Library is the standard library, developed to support
application development in Java. The class library contains features such as:
The core libraries, which include:
Many low level, GUI, Integration, Deployment and Tools Java Platform
Standard Edition 7 Documentation