1.1 About Project

Main Live Project Report Blood Bank Data Base for IRCS
zz
1. INTRODUCTION
1.1 About project:
The main aim of this project is to create Database for Blood Bank system, so that the
user can maintain all the details of the Donor, Donor test details, Stock details, Recipient
details, Discard details.
We have done our main project on Database for Blood Bank System inorder to
maintain the data in the database. And mentioned the complete details in the database.
The project is computerizing the School database system, which is designed and developed
in JAVA and Oracle 10g express edition. This project is developed to reduce the complexity
involved in maintaining large amount of data and frequent complex operations manually in
large school. This project comprises the modules like Student, Staff, Accounts and
Transportation.
The following are major activities that take place in Blood bank database:
Donor details.
Donor Test details.
Stock details.
Account details.
Recipient details.
Discard details.
Camp details.
Aizza College of Engineering & Technology Page 1

zz
1.2 Existing system with drawbacks:
At present the hospital maintaining all information in records, registers and papers.
Drawbacks
Difficult in database maintenance.

Time consuming process
Huge human resource.
1.3 Proposed system with features:
In our project we are providing a user friendly interface through which an

authenticated user can interact with the Database.
Features
The information regarding Blood Bank can be retrieved easily and takes less time.
Increases the efficiency in storing the information there by reducing risk.
This application provides security.

zz
2. SYSTEM ANALYSIS
2.1 Functional Requirements:

Hardware Requirements (Preferable):
Processor : Intel Pentium-IV
Hard disk : 20GB
RAM : 512 MB
Software Requirements (Preferable):
Front End : JAVA/J2EE
Back end :Oracle10g Expression
IDES : Net Beans6.8
Operating System : Windows XP
Framework : C#(3.5 version)

zz
2.2 Non-Functional Requirements:
Cost
Size
Maintainability
Robust
Reliability:
Cost:
It is Feasable
Size:
It occupies lessthan 2MB
Maintainability:
Maintainability is used to make future maintenance easier, meet new requirements.
Robustness:
Robustness is the quality of being able to withstand stress, pressures, or changes in
Procedure or circumstance.
Reliability:
Reliability is a ability of a person or system to perform and maintain its functions
in circumstances.

zz
2.3 Technology Used:
The Technology used in the development of this software is JAVA/J2EE.JAVA [3]

represents an advanced new generation of software that will drive the Next Generation
Internet. Its purpose is to make information available any time, any place, and on any
device.JAVA is an initiative to integrate all Microsoft products with the Next Generation
web.
2.4 Module Description

Donor details.
Master
Stock details.
Discard & Issues details.
.
Donor:
In this module all the donor details are provided. They are like donor add and view.
Master:
In this module we are providing Master details. It is a combination of Donation test
details and Recipient details.
Stock Details:
In this module we are providing Stock details. They are like Stock view by bag , view
by expiry ,view by Blood group , view by gender.
Discard & Issue details:

In this module we are providing the details of discard. They are like discard add,
view, update, delete.

zz
3. SYSTEM DESIGN
3.1 Block Diagram

zz

zz
F igure: 3.1(a ) Block Diagram
3.2 Data Flow Diagrams:
A data flow diagram[2] is graphical tool used to describe and analyze movement of
data through a system. These are the central tool and the basis from which the other
components are developed.
The transformation of data from input to output, through processed, may be described
logically and independently of physical components associated with the system. These
are known as the logical data flow diagrams.
The physical data flow diagrams show the actual implements and movement of data
between people, departments and workstations.
DFD is also known as a Bubble Chart has the purpose of clarifying system
requirements and identifying major transformations that will become programs in
system design. So it is the starting point of the design to the lowest level of detail.
DFD symbols:
Element References Symbols

Data Flow Process
Process
Data Store
Source & Destination

Description:
Process:
No process can have only outputs

zz
No process can have only inputs. If an object has only inputs than it must be a sink.
A process has a verb phrase libels.
Data Store:
Data cannot move directly from one data store to another data store, a process must
move data.
Data cannot move directly from an outside source to a data store, a process, which
receives, must move data from the source and place the data into data store.
A data store has a noun phrase label.
Source or Sink:
The origin and/or destination of data
Data cannot move directly from a source to sink it must be moved by a process
Source and/or sink has a noun phrase

zz
3.2.1Context Level DFD
Login Insert and update details

1.0
Admin # Database
Logout Blood
bank Retrives the data
Figure: 3.2.1 Context Level DFD

zz
3.2.2 Top Level DFD
# Database
Admin 1.0
2.0
Login Donor
# Donor table
3.0
Donor # Donor test
test table
4.0 # Stock table

Stock
5.0 # Issue table

Issue
6.0
Recipie # Recipient table
nt
7.0
Discar # Discard table
Blood bank for d
IRCS
Figure: 3.2.2 Context Level DFD

zz
3.2.3 Detail Level DFD

zz

zz
F igure 3.2.3 detail level D FD

zz
3.3 Entity- Relationship Diagrams:

In E-R diagram[5] basic objects are.
Entity
Attribute
Relationship
Entity:
An entity is a logical object that represents a person, place, or thing about which an
organization maintains information.
Attributes:
Attribute collect information about an entity. Logical attribute usually corresponds to

physical columns in a table.
Relationships:
A very important object in a data model is the relationship, which is represented by the
solid or dashed line that connects two entities or tables. A relationship line connects parent to
child entities or tables.
Ellipses: Represent attribute

zz
Diamonds: Represent relationship sets.
Lines: Link attribute to entity sets and entity sets to relationship sets.
Double Ellipse: Represent multi-valued attributes.
Dashed Ellipse: It denotes derived attributes.
Double Lines: Indicate total participation of an entity in a relationship set.

zz
E-R DIAGRAM
F igure 3.3 ER D iagra m

zz
3.4 Unified Modeling Language (UML) Diagrams

The Unified Modeling Language (UML)[1] is a Graphical Language for
Visualizing, Specifying, Constructing, and Documenting .The Artifacts of a Software
Intensive System. UML provides Blue Prints for Business process, System Function,
Programming Language statements, Database Schemas and Reusable Components.
There are 8 Types of Diagrams:
Class diagram
Object diagram
Use case diagram
Sequence diagram
Collaboration diagram
State diagram
Component diagram
Deployment diagram

zz
3.4.1 Class Diagram:
Classes are the most important building of any obi-oriented languages. A class is
a description of a set of obis that share the same attributes, operations, relationships and
semantics. A class is an abstraction of things that are a part of a vocabulary. A class is not an
individual obj, but rather represents a whole set of obis.
SHAPE Name Name
Attributes:
ORIGIN
MOVE() O perations
Resize()
Name:
A name is a textual string. The name alone is called as simple name; a path name is a
class name prefixed by the name of the package in which the class lives.
Attribute:
An attribute is a named property of a class that describes a range of values that
instances of the property may hold. An attribute represents some property of the thing u are
modeling that is shared by all objs of that class.
Operation:
An operation is the implementation of a service that can be requested from any
obj of the class to effect behavior. class may have any number of operation or no operation at
all.

zz
Class Diagram:
Donor Donation
dname bagno
daddress year sno
did month sno
dbloodgroup
view()
add() * update()
view() delete()
* update()
Stock
1 kitid
Admin kit name
user name 1 date of expiry
...
password *
1 view()
retrieve information()
... update()
1 delete()
update database()
1 1
Recipient
name
* id
* Issue
Discard
bagno view()
donorname
donation date recipient no
reason * quantity
crossmatch id
add()
view() add()
update() view()
update()
delete()
Figure 3 . 4 . 1 C l a s s D i a g r a m

zz
3.4.2 Use Case Diagram:
Early stages of the design process to collect the intention requirements of a project.
The first diagram to look at a project is the Use Case diagram[1]. The main ingredients for
this type of diagram are use cases and actors. They are associated to the tasks, or use cases,
they are involved in. it is often used in
ACTORS - also referred to as roles. Name and stereotype of an actor can

be changed in its properties tab.
INHERITANCE - refinement relations between actors. This relation can
carry a name and a stereotype.
USE CASES - these can have extension points.
ASSOCIATIONS - between roles and use cases. It is useful to give

associations speaking names.
DEPENDENCIES - between use cases. Dependencies often have a

stereotype to better define the role of the dependency. There are two special
kinds of dependencies: <<extend>> and <<include>>.
EXTEND RELATIONSHIP - a unit-directional relationship between two

use cases. An extend relationship between use case b and use case a means
that the behavior of b can be included in a.
INCLUDE RELATIONSHIP - a unit-directional relationship between

two use cases. Such a relationship between use cases a and b means, that the
behavior of b is always included in a.
SYSTEM BORDER -. You can simply draw a rectangle; use it as system

border by putting all corresponding use cases inside the rectangle.

zz
Use Case Diagram
Figure: 3.4.2 Use case Diagram

zz
3.4.3 Sequence Diagram:
A Sequence diagram[1] is an easily comprehensible visualization of single

scenarios in time. The diagram essentially includes a timeline that flows from the top to the
bottom of the diagram and is displayed as a dotted line. The interaction between objects is
described by specifying the different kinds of messages sent between them. Messages are
called stimuli.
Diagram Elements:
OBJECTS - elements responsible for sending and receiving messages.

CALL STIMULI - represents a synchronous message, which means that it is
regarded as a procedure call.
SEND STIMULI - illustrates an asynchronous message, which means that it is

regarded as a signal. As such, the sender doesn't wait for an answer from the receiver.
RETURN STIMULI - represents the return statement of a call stimulus.
CREATE STIMULI - used to create a new object at a certain point in the

sequence. The created object will then be placed at this specific point and not at the
top of the diagram pane
DESTROY STIMULI - used to destroy an object at a specific point in the

sequence. the lifeline of the destroyed object will then end with a cross at this point
and not at the bottom of the diagram pane

zz
Sequence Diagram
Figure: 3.4.3(e) Sequence diagram

zz
3.4.4 Collaboration Diagram:
A Collaboration diagram[1] emphasizes the organization of the objects that

participates in interaction. It addresses the dynamic view of the system. It consists of a path
and sequence number. A path is used to indicate how one object is linked to another; you can
attach a path stereotype to the far end of a link. The sequence diagram used to indicate the
time-ordering of message; we prefix the message with a number.
Diagram Elements:
Objects- in Collaborations, objects represent different roles these are specified as

classifier roles in Poseidon for UML.
Association- Associations illustrate the connections between collaborating
objects. Messages are then placed along them.
Messages- Messages just like in Sequence diagrams, messages are used to
describe the interaction between objects. The numbers in front of the given names.

zz
Collaboration diagram
Figure: 3.4.4 Collaboration diagram

zz
3.4.5 Activity Diagrams:
Activity diagrams[1] are often used to model business processes. They simply and
quite plainly show how things work, and so function as a good aid to discussions of aspects
of the workflow with the domain experts.
Diagram Elements:
Initial States And Final States - indicate the beginning and end of the observed
process.
Action States - specific activities which comprise the process. They must be executed
in a specified chronological order. Sometimes you may want to split the sequence;
therefore, you have two different possibilities: branches (choice) and forks
(concurrency).
Branches - these divide the sequence into several alternatives specified by different
conditions (guards).
Forks And Joins - forks divide the sequence into concurrent sub-sequences. Joins
merge the sub-sequences.
Synchronization States - used in concurrent sub-sequences to synchronize producer-

consumer relations.
Transitions - the ingredient that keep states active and the model elements together.
Each transition can be given guards, triggers, and actions as properties to describe its
behavioral details.
Object Flow States - objects are inputs or outputs of activities and are accordingly
connected by transitions to them.
Dependencies - always possible between any model elements.

zz
Activity diagram

zz
Figure: 3.4.5 Activity diagram
4. DATA DICTIONARY
Data dictionary[5] is a catalog-a repository-of the elements in the system. It stores

details and description of the data flow, process and data stores. It is intended to be used to
understand the system by analysis, which retrieve the details and descriptions it stores and
during system design, when information about such concern as data length, alternative names
and data used for specific process must be available.
A Data Dictionary has many advantages the most obvious is documentation. It is
valuable reference in any organization. Another advantage is improving analyst/user
communication by establishing consistent definitions of various elements, terms and
procedures. During implementation it serves as a common their data descriptions. Also
control information for each data element is cross data element is cross-referenced in Data
Dictionary.
Once the system is developed the system analyst checks the required data elements
against the organizations central data dictionary. This saves a great deal of work to the
analyst. Finally DD is important step in building a database. Most data base management
system has a DD as standard features.
The most important aspect of the system is data design. The data must be organized
according to the system requirements.
The database approach is used to store and organize the data in developing the
system. The database is an integrated collection of data stored in different types of tables.
Some general objectives in establishing a database are as follows:
Integrating all data
Incorporate updating easily
Provide data security from unauthorized users

zz
Table Datatype Details:

zz

zz

zz

zz

zz

zz

zz
4. SAMPLE CODING
Welcome page :
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
/*
* modules.java
*
* Created on 20 Mar, 2012, 8:23:13 PM
*/
package source;
import java.io.FileInputStream;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.Statement;
import java.util.Properties;
import javax.swing.JOptionPane;
import javax.swing.JPanel;
/**
*
* @author GAYATHRI
*/
public class modules extends javax.swing.JFrame {
/** Creates new form modules */

public modules() {
initComponents();
}
/** This method is called from within the constructor to

* initialize the form.
* WARNING: Do NOT modify this code. The content of this method is
* always regenerated by the Form Editor.
*/
@SuppressWarnings("unchecked")
// <editor-fold defaultstate="collapsed" desc="Generated Code">
private void initComponents() {
jPanel1 = new javax.swing.JPanel();


zz
jLabel2 = new javax.swing.JLabel();

jComboBox1 = new javax.swing.JComboBox();
jTextField1 = new javax.swing.JTextField();
jButton1 = new javax.swing.JButton();
jMenuBar1 = new javax.swing.JMenuBar();
jMenu1 = new javax.swing.JMenu();
jMenuItem8 = new javax.swing.JMenuItem();

zz
jSeparator1 = new javax.swing.JPopupMenu.Separator();

setDefaultCloseOperation(javax.swing.WindowConstants.DISPOSE_ON_CLOSE);
addWindowListener(new java.awt.event.WindowAdapter() {
public void windowActivated(java.awt.event.WindowEvent evt) {
formWindowActivated(evt);
}
public void windowOpened(java.awt.event.WindowEvent evt) {
formWindowOpened(evt);
}
});
jPanel3.setBackground(new java.awt.Color(255, 255, 255));
jLabel2.setText("Blood Group");
jComboBox1.setModel(new javax.swing.DefaultComboBoxModel(new String[]

{ "Select", "A+", "B+", "AB+", "O+", "A-", "B-", "AB-", "O-" }));
jLabel3.setText("Threshold");
jButton1.setText("Update");
jButton1.addActionListener(new java.awt.event.ActionListener() {
public void actionPerformed(java.awt.event.ActionEvent evt) {
jButton1ActionPerformed(evt);
}
});
javax.swing.GroupLayout jPanel3Layout = new javax.swing.GroupLayout(jPanel3);

jPanel3.setLayout(jPanel3Layout);
jPanel3Layout.setHorizontalGroup(

zz
jPanel3Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addGroup(jPanel3Layout.createSequentialGroup()
.addGap(27, 27, 27)
.addGroup(jPanel3Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADI
NG, false)
.addComponent(jLabel2)
.addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.UNRELATED)
.addComponent(jComboBox1,
javax.swing.GroupLayout.PREFERRED_SIZE, 121,
javax.swing.GroupLayout.PREFERRED_SIZE))
.addGap(18, 18, 18)
NG)
.addComponent(jButton1)
.addComponent(jTextField1))))
.addContainerGap(88, Short.MAX_VALUE))
);
jPanel3Layout.setVerticalGroup(
.addGap(21, 21, 21)
.addGroup(jPanel3Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.BASEL
INE)
.addComponent(jComboBox1, javax.swing.GroupLayout.PREFERRED_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE,
.addGap(31, 31, 31)
INE)
.addComponent(jTextField1, javax.swing.GroupLayout.PREFERRED_SIZE,
.addGap(43, 43, 43)
.addComponent(jButton1)
);
jLabel4.setText("A+");

zz
jLabel6.setText("B+");
jLabel8.setText("AB+");
jLabel10.setText("O+");
jLabel12.setText("A-");
jLabel14.setText("B-");
jLabel16.setText("AB-");
jLabel18.setText("O-");
jLabel20.setText("Kits");

.addGap(24, 24, 24)
NG)
.addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED)
.addComponent(jLabel21))

zz
.addGap(18, 18, 18)
.addGap(31, 31, 31)
NG)
.addComponent(jLabel9))))
.addContainerGap(javax.swing.GroupLayout.DEFAULT_SIZE,
Short.MAX_VALUE))
);
.addGap(26, 26, 26)
INE)
.addGap(18, 18, 18)
INE)
.addGap(18, 18, 18)
INE)
.addGap(29, 29, 29)
INE)
.addGap(18, 18, 18)
INE)

zz
.addGap(18, 18, 18)
INE)
.addGap(18, 18, 18)
INE)
.addGap(18, 18, 18)
INE)
.addGap(18, 18, 18)
INE)
);
jLabel22.setFont(new java.awt.Font("Times New Roman", 3, 24)); // NOI18N

jLabel22.setForeground(java.awt.Color.red);
jLabel22.setText("WELCOME TO THE BLOOD BANK");

.addGroup(javax.swing.GroupLayout.Alignment.TRAILING,
jPanel1Layout.createSequentialGroup()
.addGap(191, 191, 191)
.addComponent(jLabel22, javax.swing.GroupLayout.PREFERRED_SIZE, 490,
javax.swing.GroupLayout.PREFERRED_SIZE)
.addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED, 170,
Short.MAX_VALUE)
.addComponent(jPanel4, javax.swing.GroupLayout.PREFERRED_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE, javax.swing.GroupLayout.PREFERRED_SIZE)
);

zz
NG)
.addGroup(jPanel1Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.TRAILI
NG, false)
.addComponent(jPanel4, javax.swing.GroupLayout.Alignment.LEADING,
javax.swing.GroupLayout.DEFAULT_SIZE, javax.swing.GroupLayout.DEFAULT_SIZE,
Short.MAX_VALUE)
.addComponent(jPanel3, javax.swing.GroupLayout.Alignment.LEADING,
javax.swing.GroupLayout.DEFAULT_SIZE, javax.swing.GroupLayout.DEFAULT_SIZE,
Short.MAX_VALUE))
.addGap(89, 89, 89)
.addComponent(jLabel22, javax.swing.GroupLayout.PREFERRED_SIZE,
147, javax.swing.GroupLayout.PREFERRED_SIZE)))
);

.addGap(0, 657, Short.MAX_VALUE)
);
.addGap(0, 95, Short.MAX_VALUE)
);
jLabel1.setText("jLabel1");
jMenu1.setIcon(new javax.swing.ImageIcon(getClass().getResource("/ICON/images
(15).jpg"))); // NOI18N
jMenu1.setText("Donor");
jMenu1.setFont(new java.awt.Font("Times New Roman", 1, 14));
jMenuItem8.setText("Add");
jMenuItem8.addActionListener(new java.awt.event.ActionListener() {
jMenuItem8ActionPerformed(evt);
}
});
jMenu1.add(jMenuItem8);
jMenuItem2.setFont(new java.awt.Font("Times New Roman", 0, 14));

jMenuItem2.setText("Update");

zz

}
});

jMenuItem1.setText("View");
}
});
jMenuBar1.add(jMenu1);
jMenu2.setIcon(new
javax.swing.ImageIcon(getClass().getResource("/ICON/IIII.jpg"))); // NOI18N
jMenu2.setText("Donation");
jMenuItem28.setText("Add Techncians");
}
});
}
});

}
});

zz
(17).jpg"))); // NOI18N
jMenu3.setText("Stock");
jMenu3.addActionListener(new java.awt.event.ActionListener() {
jMenu3ActionPerformed(evt);
}
});

jMenuItem6.setText("View by Blood group");
}
});

jMenuItem9.setText("View by Gender");
}
});

jMenuItem10.setText("View by bag");
}
});
jMenuItem7.setText("View by expiry");
}
});
jMenuItem23.setText("View By Receipient");
}

zz
});

jMenuItem29.setText("DailyStock");
jMenuItem29ActionPerformed1(evt);
}
});

}
});

}
});

}
});
jMenu6.setText("Discard Details");
jMenu6.addActionListener(new java.awt.event.ActionListener() {
jMenu6ActionPerformed(evt);

zz
}
});

}
});
}
});
jMenu6.add(jSeparator1);

}
});
(14).jpg"))); // NOI18N
jMenu7.setText("Test");

}
});

jMenuItem21.setText("Updatae");

zz
}
});
jMenu8.setIcon(new javax.swing.ImageIcon(getClass().getResource("/ICON/kit.jpg")));
// NOI18N
jMenu8.setText("Kits");
}
});

}
});

}
});
jMenu9.setIcon(new
javax.swing.ImageIcon(getClass().getResource("/ICON/report.jpg"))); // NOI18N
jMenu9.setText("Reports");
jMenuItem22.setText("Complete Report");
}
});

zz
jMenu10.setIcon(new
javax.swing.ImageIcon(getClass().getResource("/ICON/camp.jpg"))); // NOI18N
jMenu10.setText("Camp Details");
}
});
}
});
jMenu4.setText("Accounts");
jMenuItem11.setText("View Daily Report");

}
});
jMenuItem24.setText("Monthly Report");
}
});
}
});

zz
jMenu11.setText("Receipient Details");

}
});
setJMenuBar(jMenuBar1);
javax.swing.GroupLayout layout = new javax.swing.GroupLayout(getContentPane());

getContentPane().setLayout(layout);
layout.setHorizontalGroup(
layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addGroup(javax.swing.GroupLayout.Alignment.TRAILING,
layout.createSequentialGroup()
.addGap(408, 408, 408)
.addComponent(jPanel2, javax.swing.GroupLayout.DEFAULT_SIZE,
javax.swing.GroupLayout.DEFAULT_SIZE, Short.MAX_VALUE)
.addGap(196, 196, 196))
.addGroup(layout.createSequentialGroup()
.addContainerGap()
.addContainerGap())
);
layout.setVerticalGroup(
layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)
.addGroup(layout.createSequentialGroup()
.addContainerGap()
javax.swing.GroupLayout.DEFAULT_SIZE, javax.swing.GroupLayout.PREFERRED_SIZE)
.addContainerGap())
);
pack();
}// </editor-fold>
private void jMenuItem1ActionPerformed(java.awt.event.ActionEvent evt) {

// TODO add your handling code here:

zz
DonorView v=new DonorView();

v.setSize(800,550);
v.setVisible(true);
//this.dispose();
// JPanel jp = (JPanel)v.getContentPane();
//this.setContentPane(jp);
//this.validate();
//this.repaint();

DonorUpdates u=new DonorUpdates();
u.setSize(800,600);
u.setVisible(true);
//this.dispose();
//JPanel jp = (JPanel)u.getContentPane();
//this.validate();
//this.repaint();

Donation a=new Donation();
//JPanel jp = (JPanel)a.getContentPane();
//this.validate();
//this.repaint();
a.setSize(1000,600);
a.setVisible(true);
//this.dispose();

Donationview v=new Donationview();
v.setSize(1300,550);
v.setVisible(true);
// this.dispose();
//JPanel jp = (JPanel)v.getContentPane();
// this.setContentPane(jp);

zz
// this.validate();
// this.repaint();

StockViewBG v=new StockViewBG();
v.setSize(1000,600);
v.setVisible(true);
//this.dispose();
// this.validate();
// this.repaint();
private void jMenu3ActionPerformed(java.awt.event.ActionEvent evt) {

StockViewexpiry e=new StockViewexpiry();
e.setSize(800,800);
e.setVisible(true);
//JPanel jp = (JPanel)e.getContentPane();
//this.validate();
//this.repaint();

Stockviewgender g=new Stockviewgender();
g.setSize(1000,600);
g.setVisible(true);
//this.dispose();
// JPanel jp = (JPanel)g.getContentPane();
//this.validate();
//this.repaint();

Stockviewbag b=new Stockviewbag();
b.setSize(1300,600);
b.setVisible(true);
//this.dispose();

zz
//JPanel jp = (JPanel)b.getContentPane();
//this.validate();
//this.repaint();

IssueAdd a=new IssueAdd();
a.setSize(800,600);
a.setVisible(true);
// JPanel jp = (JPanel)a.getContentPane();
// this.validate();
// this.repaint();
//this.dispose();
}

IssueView i=new IssueView();
i.setSize(800,600);
//JPanel jp = (JPanel)i.getContentPane();
//this.validate();
//this.repaint();
i.setVisible(true);
//this.dispose();
}

IssueUpdate u=new IssueUpdate();
u.setSize(800,500);
//this.validate();
//this.repaint();
u.setVisible(true);
//this.dispose();
}

KitsAdd k=new KitsAdd();

zz
k.setSize(800,500);
k.setVisible(true);
//JPanel jp = (JPanel)k.getContentPane();
//this.validate();
// this.repaint();

KitsView v=new KitsView();
v.setSize(800,500);
v.setVisible(true);
//this.validate();
//this.repaint();

KitsUpdate u=new KitsUpdate();
//this.validate();
//this.repaint();
u.setSize(800,500);
u.setVisible(true);
}

//KitsDelete d=new KitsDelete();
//d.setSize(800,500);
//d.setVisible(true);
}

ReceipientView v=new ReceipientView();
//this.validate();
//this.repaint();

zz
v.setSize(850,550);
v.setVisible(true);
//this.dispose();
}

Reportsviewbygroup g=new Reportsviewbygroup();
g.setSize(800,500);
this.validate();
g.setVisible(true);
// JPanel jp = (JPanel)g.getContentPane();
//this.validate();
//this.repaint();
AddDonor g=new AddDonor();
//JPanel jp = (JPanel)g.getContentPane();
//this.validate();
//this.repaint();
g.setSize(800,600);
g.setVisible(true);

}

TestUpdate u=new TestUpdate();
// JPanel jp = (JPanel)u.getContentPane();
// this.validate();
// this.repaint();
u.setSize(900,550);
u.setVisible(true);
// this.dispose();
}

zz

TestAdd a=new TestAdd();
//this.validate();
// this.repaint();
a.setSize(800,500);
a.setVisible(true);
// this.dispose();
}

// TODO add your handling code here
NewTechnician nt = new NewTechnician();
nt.setVisible(true);
nt.setSize(800, 500);
//JPanel jp = (JPanel)nt.getContentPane();
//this.validate();
//this.repaint();

CampAdd cd = new CampAdd();

cd.setVisible(true);
cd.setSize(800, 500);
//JPanel jp = (JPanel)cd.getContentPane();
//this.validate();
//this.repaint();

CampView cv = new CampView();

zz
cv.setSize(1000, 500);
cv.setVisible(true);
// JPanel jp = (JPanel)cv.getContentPane();
//this.validate();
//this.repaint();

StockViewexpiry sv = new StockViewexpiry();

sv.setSize(900,500);
// JPanel jp = (JPanel)sv.getContentPane();
// this.validate();
//this.repaint();
sv.setVisible(true);
private void jMenuItem22ActionPerformed1(java.awt.event.ActionEvent evt) {

CompleteReport cr = new CompleteReport();

cr.setSize(1200,700);
cr.setVisible(true);
//JPanel jp = (JPanel)cr.getContentPane();
// this.validate();
// this.repaint();

}

zz
CampAdd ca=new CampAdd();

ca.setVisible(true);
ca.setSize(1000, 600);

}

ViewMonthlyAccountReport va=new ViewMonthlyAccountReport();
va.setVisible(true);
va.setSize(1000,600);

}

ViewDailyAccountReport va=new ViewDailyAccountReport();
va.setVisible(true);
va.setSize(1000,600);

}

ViewThalasaima vt=new ViewThalasaima();
vt.setVisible(true);
vt.setSize(1000, 700);
}

CampView v=new CampView();
v.setVisible(true);
v.setSize(1000, 600);
}

DailyStock s=new DailyStock();
s.setVisible(true);
s.setSize(1000, 600);
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {

zz
if(jTextField1.getText().equals(""))
{
JOptionPane.showMessageDialog(this,"please enter the Threshold value");
}
else
{
try{
FileInputStream fs=new FileInputStream("D:/dbconn.properties");
Properties p1=new Properties();
p1.load(fs);
String driver=p1.getProperty("driver");
String url=p1.getProperty("url");
String un=p1.getProperty("username");
String pwd=p1.getProperty("password");
Class.forName(driver);
Connection con=DriverManager.getConnection(url,un,pwd);
Statement st=con.createStatement();
String val=jComboBox1.getSelectedItem().toString();
ResultSet rs=st.executeQuery("select * from CRITICALVIEWDETAILS where
bg='"+val+"'");
if(rs.next())
{
PreparedStatement pst=con.prepareStatement("update CRITICALVIEWDETAILS set
thrhold=?,chage_date=? where bg=?");
pst.setInt(1, Integer.parseInt(jTextField1.getText()));
pst.setDate(2, new java.sql.Date(System.currentTimeMillis()));
pst.setString(3,jComboBox1.getSelectedItem().toString());
pst.executeUpdate();
JOptionPane.showMessageDialog(this,"Updated Successfully");
}
else
{
PreparedStatement pst=con.prepareStatement("insert into criticalviewdetails
values(?,?,?)");
pst.setInt(2, Integer.parseInt(jTextField1.getText()));
pst.setDate(3, new java.sql.Date(System.currentTimeMillis()));
pst.setString(1,jComboBox1.getSelectedItem().toString());
pst.executeUpdate();
JOptionPane.showMessageDialog(this,"Detals Uploaded Successfully");
}
}
catch(Exception e)
{
JOptionPane.showMessageDialog(this, e);
}
}
}

zz
private void formWindowActivated(java.awt.event.WindowEvent evt) {

}
private void formWindowOpened(java.awt.event.WindowEvent evt) {

}
private void jMenu6ActionPerformed(java.awt.event.ActionEvent evt) {

//this.dispose();
}

DiscardUpdate dsup = new DiscardUpdate();

dsup.setSize(800, 500);
dsup.setVisible(true);
//JPanel jp = (JPanel)dsup.getContentPane();
// this.validate();
// this.repaint();

DiscardView v=new DiscardView();
v.setSize(800,500);
//this.validate();
//this.repaint();
v.setVisible(true);
//this.dispose();
}

DiscardAdd a=new DiscardAdd();

zz
//this.validate();
//this.repaint();
a.setSize(800,500);
a.setVisible(true);
//this.dispose();
}
/**
* @param args the command line arguments
*/
public static void main(String args[]) {
java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {
new modules().setVisible(true);
}
});
}
// Variables declaration - do not modify

private javax.swing.JButton jButton1;
private javax.swing.JComboBox jComboBox1;
private javax.swing.JLabel jLabel1;

zz
private javax.swing.JMenu jMenu1;

private javax.swing.JMenuBar jMenuBar1;
private javax.swing.JMenuItem jMenuItem1;
private javax.swing.JPanel jPanel1;
private javax.swing.JPopupMenu.Separator jSeparator1;
private javax.swing.JTextField jTextField1;
// End of variables declaration }
Login Page:

zz
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
/*
* Title.java
*
* Created on 20 Mar, 2012, 3:49:04 PM
*/
package source;
import java.awt.Color;
import java.io.FileInputStream;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.util.Properties;
import javax.swing.JOptionPane;
/**
*
* @author GAYATHRI
*/
public class Title extends javax.swing.JFrame {
/** Creates new form Title */

public Title() {
initComponents();
}
/** This method is called from within the constructor to

* initialize the form.
* WARNING: Do NOT modify this code. The content of this method is
* always regenerated by the Form Editor.
*/
@SuppressWarnings("unchecked")
// <editor-fold defaultstate="collapsed" desc="Generated Code">
private void initComponents() {

jTextField1 = new javax.swing.JTextField();
jPasswordField1 = new javax.swing.JPasswordField();

zz

setDefaultCloseOperation(javax.swing.WindowConstants.EXIT_ON_CLOSE);
addWindowListener(new java.awt.event.WindowAdapter() {
public void windowOpened(java.awt.event.WindowEvent evt) {
formWindowOpened(evt);
}
});
getContentPane().setLayout(null);

jPanel1.setLayout(null);
jLabel1.setFont(new java.awt.Font("Times New Roman", 1, 20));

jLabel1.setForeground(new java.awt.Color(249, 12, 12));
jLabel1.setText("BLOOD BANK DATABASE MANAGEMENT SYSTEMFOR
IRCS(mncl)");
jPanel1.add(jLabel1);
jLabel1.setBounds(150, 60, 730, 22);

jLabel2.setForeground(new java.awt.Color(102, 0, 255));
jLabel2.setText(" Login");

jLabel3.setText("User name");

jLabel4.setText("Password");
jTextField1.addFocusListener(new java.awt.event.FocusAdapter() {
public void focusLost(java.awt.event.FocusEvent evt) {
jTextField1FocusLost(evt);
}
});
jPanel1.add(jTextField1);
jTextField1.setBounds(375, 155, 119, 20);
jPasswordField1.addFocusListener(new java.awt.event.FocusAdapter() {
public void focusLost(java.awt.event.FocusEvent evt) {

zz
jPasswordField1FocusLost(evt);
}
});
jPanel1.add(jPasswordField1);
jPasswordField1.setBounds(375, 202, 119, 20);
jButton1.setText("submit");
}
});
jPanel1.add(jButton1);
jButton1.setBounds(294, 289, 90, 23);
jButton2.setText("cancel");
}
});
jButton3.setText("forgot password?");
}
});
jLabel5.setText("*");
jLabel6.setText("*");
jLabel7.setIcon(new
javax.swing.ImageIcon("C:\\Users\\GAYATHRI\\Documents\\NetBeansProjects\\Source\\src\
\ICON\\IRCSLOGO.jpg")); // NOI18N
jLabel7.setText("jLabel7");
getContentPane().add(jPanel1);
jPanel1.setBounds(0, 10, 800, 560);

zz
pack();
}// </editor-fold>

jTextField1.setText("");
jPasswordField1.setText("");

}

try {
// JOptionPane.showMessageDialog(this," user name:"+jTextField1.getText()

+"password:"+jPasswordField1.getText());
String u=jTextField1.getText();
String p=jPasswordField1.getText();
FileInputStream fs=new FileInputStream("D:/dbconn.properties");
Properties p1=new Properties();
p1.load(fs);
String driver=p1.getProperty("driver");
String url=p1.getProperty("url");
String un=p1.getProperty("username");
String pwd=p1.getProperty("password");
Class.forName(driver);
Connection con=DriverManager.getConnection(url,un,pwd);
PreparedStatement ps=con.prepareStatement("select * from login where username=?
and password=?");
ps.setString(1,u);
ps.setString(2,p);
ResultSet rs=ps.executeQuery();
if(rs.next())
{
JOptionPane.showMessageDialog(this,"valid user");
modules m=new modules();
m.setSize(800,500);
m.setVisible(true);
this.dispose();
}
else
{
JOptionPane.showMessageDialog(this,"Invalid
user","alert",JOptionPane.ERROR_MESSAGE);
}
} catch (Exception e) {

zz
JOptionPane.showMessageDialog(this,e);
}

}

Forgot fg=new Forgot();
fg.setSize(800,500);
fg.setVisible(true);
this.dispose();
}
private void jTextField1FocusLost(java.awt.event.FocusEvent evt) {

if(jTextField1.getText().equals(""))
{
// JOptionPane.showMessageDialog(this,"enter username");
jLabel5.setForeground(Color.red);
jLabel5.setText("enter username");
}
else
{
jLabel5.setText("");
}
}
private void jPasswordField1FocusLost(java.awt.event.FocusEvent evt) {

if(jPasswordField1.getText().equals(""))
{
// JOptionPane.showMessageDialog(this,"enter password");
jLabel6.setForeground(Color.red);
jLabel6.setText("enter password");
}
else
{
jLabel6.setText("");
}
}
private void formWindowOpened(java.awt.event.WindowEvent evt) {

this.setSize(800, 500);
}
/**
* @param args the command line arguments

zz
*/
public static void main(String args[]) {
java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {
new Title().setVisible(true);
}
});
}
// Variables declaration - do not modify

private javax.swing.JPasswordField jPasswordField1;
private javax.swing.JTextField jTextField1;
// End of variables declaration
5. RESULTS

zz
Login page:
Forgot password form:

zz
Modules Form:

zz
Homepage:

zz
Donor Updates Form:

zz
Donor View Form:

zz
New Technician Form:

zz
Donor Test Details Form:

zz
Donor Test View Form:

zz
Stock View by Blood Group Form:

zz
Stock View by Gender Form:

zz
Stock View By Bag Form:

zz
Stock View By Expiry Form:

zz
Recipient View Form:

zz
Daily Stock Form:

zz
Discard Add Form:

zz
Discard Update Form:

zz
Test Add Form:

zz
Test Update Form:

zz
Kit Add Form:

zz
Account Purchase Form:

zz
Complete Report Form:

zz
Camp Add Form:

zz
Camp View Form:

zz
View Thalasamia Form:

zz
6. SYSTEM TESTING

zz
The purpose of this project is for security testing to ensure the robustness of a system
at the face of malicious attacks or regular software failure. A process of executing a program
with explicit intension of finding errors that is that is making the program fails. A primary
purpose for testing is to detect software failures so that defects may be uncovered and
corrected. The scope testing often includes examination of code as execution of that code in
various environments and conditions.
Software testing:
It is process of testing the functionality and it is the process of executing a program
with the intent of finding an error.
Black box Testing:

The base of the black box testing[4] strategy lies in the selection of appropriate data
as per functionality and testing it against the functional specifications in order to check for
normal and abnormal behavior of system. Now a days, it is becoming to route the testing
work to a third party as the developer of the system knows too much of the internal logic and
coding of system, Which makes it unfit to test application by the developer.
Test case:
In our project, we have used the validation such that only required details to be entered.
Validation control is applied [Regular expression validation] for all the fields of mail
address such that the mail address is to be entered with format. @.
Calendar control is used such that format of date/month and year are correctly
inserted.
White box testing:

White box testing requires access to the source code. Though White box testing can
be performed any time in the life cycle after the code is developed, it is a good practice white
box testing during the unit testing phase.
Test cases:

zz
According to our project, we have performed testing to check the correctness of

process.
Testing is performed to check the errors and to debug those errors, such that the forms
or modules are executed. I have done the unit testing by checking each line of code and found
that the code is error free.
8.SCOPE & EXPANSION

zz
Scope:
The Administrator can maintain all the details such Donor , Donor test, Stock , Issue ,
Recipient and Disposed details.
Expansion:
We can search the required blood group by using mobile system.
9. LIMITATION AND CONCLUSION

zz
Limitation:
We have done the project successfully according to the clients requirements. So there
are no limitations in the project.
Conclusion:
We are successfully completed the Data base project for Blood Bank Managent
System For IRCS.
On our project basis using JAVA technology we have developed database for
Blood bank database Management system For IRCS.
There application is user friendly.
GLOSSARY

zz
DFD - Data Flow Diagram

UML - Unified Modeling Language
ER - Entity Relationship
IDE Integrated Development Environment
J2SE Java 2.0 Standard Editon

zz
BIBLIOGRAPHY
Text Books:
[1] Grady Booch, James Rumbaugh, Ivar Jacobson, The Unified Modeling
Language User, Lower price Edition, 1997, 81-7808-169-5, 91.
[2] Roger.S.Pressman, Software Engineering, A Practitioners Approach, 7th

Edition, 2010, 13:978-007-126782-3, 482.
[3] Herbert schildt, TMHl, Java Programming Language, 6th Edition, 2006, 92-
7005-23-7, 345.
[4] Boris Beizer, Software Testing Techniques, Dreamtech, 2nd Edition, 2009,
10:81-7722-260-0, 145.
[5] Raghu Ramakrishnan / Johannes Gehrke, Data base Management Systems,

McGraw Hill, 2rd Edition, 2000, 0-07-116898-2, 24.

1.1 About Project

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1.1 About Project

Uploaded by

Copyright:

Available Formats

Main Live Project Report Blood Bank Data Base for IRCS

Aizza College of Engineering & Technology Page 1

1.2 Existing system with drawbacks:

Difficult in database maintenance.

1.3 Proposed system with features:

In our project we are providing a user friendly interface through which an

Aizza College of Engineering & Technology Page 2

2.1 Functional Requirements:

Processor : Intel Pentium-IV

Hard disk : 20GB

Software Requirements (Preferable):

Front End : JAVA/J2EE

Back end :Oracle10g Expression

IDES : Net Beans6.8

Operating System : Windows XP

Framework : C#(3.5 version)

Aizza College of Engineering & Technology Page 3

2.2 Non-Functional Requirements:

Aizza College of Engineering & Technology Page 4

2.3 Technology Used:

The Technology used in the development of this software is JAVA/J2EE.JAVA [3]

2.4 Module Description

Discard & Issue details:

Aizza College of Engineering & Technology Page 5

3.1 Block Diagram

Aizza College of Engineering & Technology Page 6

Aizza College of Engineering & Technology Page 7

F igure: 3.1(a ) Block Diagram

3.2 Data Flow Diagrams:

Element References Symbols

Source & Destination

Aizza College of Engineering & Technology Page 8

Aizza College of Engineering & Technology Page 9

3.2.1Context Level DFD

Login Insert and update details

Figure: 3.2.1 Context Level DFD

Aizza College of Engineering & Technology Page 10

3.2.2 Top Level DFD

4.0 # Stock table

5.0 # Issue table

Aizza College of Engineering & Technology Page 11

3.2.3 Detail Level DFD

Aizza College of Engineering & Technology Page 12

Aizza College of Engineering & Technology Page 13

F igure 3.2.3 detail level D FD

Aizza College of Engineering & Technology Page 14

3.3 Entity- Relationship Diagrams:

Attribute collect information about an entity. Logical attribute usually corresponds to

Ellipses: Represent attribute

Aizza College of Engineering & Technology Page 15

Diamonds: Represent relationship sets.

Double Ellipse: Represent multi-valued attributes.

Dashed Ellipse: It denotes derived attributes.

Double Lines: Indicate total participation of an entity in a relationship set.

Aizza College of Engineering & Technology Page 16

F igure 3.3 ER D iagra m

Aizza College of Engineering & Technology Page 17

3.4 Unified Modeling Language (UML) Diagrams

There are 8 Types of Diagrams:

Aizza College of Engineering & Technology Page 18

3.4.1 Class Diagram:

SHAPE Name Name