Blood Bank Management System
Blood Bank Management System
Blood Bank Management System
INTRODUCTION
Data is the code word of the computer industry. Data refers to a collection of facts
usually collected as a result of observation and experiment or processes within a
computer system. This may consist of numbers, words or images or observations
of a set of variables. Data are often viewed as a lowest level of abstraction from
which information and knowledge are derived.
SYNOPSIS
This system is mainly based on collection, storage and usage of blood in needy
situations. City life is turning hectic as we move in 21st century. Day by day all the
newspapers that were filled with motivating articles and some important news is
now filled with either Bollywood stuffs or some kinds of crime, bomb blasts
becoming one of the main events. Hence the need of blood is the crucial subject of
consideration. Also many diseases are seen to be creped in our day to day life. One
of which can be instanced as Thallesmania. One that is affected by this disease also
needs the transmission of the blood week by week. Hence blood bank is the most
suitable option then.
PROJECT
OBJECTIVE
The main objective of this application is to automate the complete operations of the
blood bank. They need maintain hundreds of thousands of records. Also searching
should be very faster so they can find required details instantly.
SCOPE
This application is built such a way that it should suits for all type of blood banks
in future. So every effort is taken to implement this project in this blood bank, on
successful implementation in this blood bank, we can target other blood banks in
the city.
This project has the following modules, to manage all the requirements of the
blood bank.
1. Employee Details
2. Employee Salary Payment
3. Reports
TOOLS INFORMATION
Hardware Requirement
Software Requirement
TOOLS USED
VISUAL BASIC is a high level programming language which evolved from the
earlier Dos version called BASIC.BASIC means Beginner’s All – Purpose
Symbolic Instruction Code. It is a very easy Programming language to learn.
The code looks a lot like English Language. Different software companies
produced different versions of BASIC, such as Microsoft QBASIC,
QUICKBASIC, GWBASIC, IBM BASIC and so on. However, people prefer to
use Microsoft Visual Basic today, as it is a well developed programming language
and supporting resources are available anywhere. Now there are many versions of
VB exist in the market, the most popular one and still widely used by many VB
programmers is none other than Visual Basic 6.We also have VB.net, VB2005,
VB2008 and the latest VB2010.Both Vb2008 and VB2010 are fully object oriented
programming (OOP) language.
What it Does
Access can store data in specific format for sorting, querying, and reporting.
Sorting is pretty straightforward; data is simply presented to you in particular
orders. An example might be presenting your customer data (customer number,
name, address, city, state, zip, and total purchases) in last name order.
Querying means that as a user of this database, you can ask Access for a collection
of information relating to location such as state or country, price as it might relate
to how much a customer spent, and date as it might relat4 to when items were
purchased.
Querying can include sorting as well. For example if you wanted to see the top
spending customers in the state of Florida querying would be a way to do that. A
Query on data typically returns a sub-set of the collection of data, but can return all
of it in a different order as well.
Reporting is simply query results in printable or viewable form.
In order for Access to perform these functions data has to be stored in the smallest
possible units. These units are called fields. A field might contain a first name, a
last name, a middle name, a street address, and so on. Notice that I do not propose
that the entire name be placed in one field. If that were done sorting one could
perform would end up being presented by the first name. But if a separate field is
used for the last name, another foe first, and so on, much more useful sorting can
be accomplished.
Fields are also defined as a type of data (number, text, date, date-time, dollar, etc.).
By storing data in its own specific field type, Access (or any RDBMS for that
matter) can sort that data in very tightly controlled as long as Access knows what
type of sort to apply to that data.
SYSTEM ANALYSIS
This project has been developed to automate data handling in Blood Bank
Management. The different forms have been used to input data, make changes to
the existing data, delete some records according to the requirements. The different
reports give the user a Firth and knowledge about various details.
This project opens with a splash screen clicking on which takes the user to the
screen having login form by clicking on it, the respective password entry form
opens. On entering the correct password the main MDI form is invoked, where the
user can select the desired form or report from the menu.
The Cancel button associated with every form cancels the currently
performed operation and not the form.
To exit from the form click the “x” button available on the top corner of
every Form.
It has not been possible to cater to all the possible quires and the project can
be upgraded according to the requirements.
There are some important modules in the purpose system, which are:
Login for admin: This module will allow the administrator to enter their
respective forms.
Donor details: This module will enable admin to add new donor and to
change their details.
Hospital details: This module will enable the Administrator to add new
Hospital details, modify their details. The Hospital ID is generated
automatically. He can also generate Hospital transaction and allows printing.
EXISTING SYSTEM
In the manual system, firstly the Blood bank and its staff have to manage
information regarding the donor details of all the donors manually. Doing this
manual transaction was really tedious job. Secondly information regarding
Hospital transactions, employee details was to be maintained. This process is time
consuming and it requires a great manual effort.
Disadvantages:
More time is consumed.
More hard work to maintain all records.
Bulk of paper is to be searched for a single search.
PROPOSED SYSTEM
Today one cannot afford to rely on the fallible human beings to stand against the
Merciless competition where it is not wise to say “to err is human” no longer valid.
It is outdated to rationalize your mistake. So, to keep pace with time, to bring about
The best result without malfunctioning and greater efficiency we have to replace
the unending heaps of files with a much sophisticated hard disk of the computer.
One has to use the data management software. Software has been an ascent in
automation of various organizations. Many software products working are now in
markets, which have helped in making the organizations work easier and efficient.
Data management initially had to maintain a lot of ledgers and a lot of paperwork
has to be done but now software production, this organization has made their work
faster and easier. Now only this software has to be loaded on the computer and
work can be done. This prevents a time and money. The work becomes fully
automated and any information regarding the organization can be obtained by
clicking the button. Moreover, now it’s age of computers and automating such an
organization gives the better look.
FEASIBILITY STUDY
Technical feasibility
Economic feasibility
Operational feasibility
TECHNICAL FEASIBILITY
This is considered with specifying equipment and software that will successfully
satisfy the user requirement. It involves determining whether or not a system can
actually be constructed or upgraded to solve the problem at hand. The technical
needs of a system may vary considerably, but might include and following:
The necessary technology of both hardware and software existed and also
could be acquired for the new system.
As the improvement in storage technology has developed over the recent
years, data storage is becoming easier and safer.
The new system with powerful database technology has the capability to hold
the proposed data.
ECONOMICAL FEASIBILITY
Economic feasibility involves estimating benefits and costs. These benefits and
costs may be tangible or intangible. It is seen whether the expenditure incurred for
developing the new system will be cost effective or not. Because of the confusion
between the types of costs, it is sometimes very difficult to decide if the benefits
outweigh the costs. The basically involves top-level management of the company
who are the decision makers. Some key fin dings from the study are listed below.
OPERATIONAL FEASIBILITY
Operational feasibility deals with the human aspect of the organization, proposed
projects are beneficial only if they can be turned into information systems that will
meet the organization’s operating requirements. This feasibility test asks whether
the system will work when developed and installed, the users need to be convinced
about the advantages of the new system.
Unless this done effectively, the system would not be implemented even after its
development and the old system would continue to be used.
PROBLEM SPECIFICATION
For the present fashion in the shopping system premises there is no solution as
such to provide the convenience of supporting multiple platforms and technologies
as there are no three tier based solution. The present solution is using web
technologies for the user. Any changes in the business logic requires lot of system
studies in terms coding and in terms of new hardware and software specifications
and the possibilities of integrating the web services is zero. For any small changes
requires the understanding of the business logic of the entire organization. There is
no job classification such as:
In the present scenario of the most of the responsibilities like coding and
integration of business logic is done by the software engineers. There is no
segregation of tasks. So it is very difficult to manage the enhancements of the
solutions.
SYSTEM DESIGN
DESIGN TOOLS
Various tools are being used by a system analysis to specify computer procedures.
Not all of them are used here to design this project.
E-R diagram
Input design
Output design
E-R DIAGRAM
Gender
Donor Name Blood Group
Age
Collection Date
DID
BBID
Expiry Date
Blood Group
Status
Address Donates
Donor Blood
Ph No Address
Ph No
Name
Orders
Works
Blood Group
Receptionist Blood Bank
No of Bags
Ph No
Emp ID
Issues
Address
Name
Transaction No Amount
Blood Bag
Registered Donor
Date
Hospital
Outsiders Blood Group No of Bags
Donor Details
Field Name Data Type
Donor_ID Text
Name Text
Address Text
Gender Text
Age Number
MaritalStatus Text
Phone_No Number
BloodGroup Text
Occupation Text
Email_ID Text
LastDonateDate Date/Time
Hospital Details
Field Name Data Type
Hospital_ID Text
Hospital_Name Text
Address Text
City Text
Pin_Code Number
Phone_No Number
Outsider Details
Field Name Data Type
Outsider_ID Text
Outsider_Name Text
Address Text
Age Number
Gender Text
Phone_No Number
Hospital_Name Text
BloodGroup Text
Camp Schedule
Field Name Data Type
Code Text
Name Text
Address1 Text
Address2 Text
Address3 Text
PinCode Number
Contact_Person Date/Time
Phone_No Number
Scheduled_Date Date/Time
No_Of_Beds Number
Stock Details
Field Name Data Type
BloodGroup Text
NoOfBags_Available Number
Employee Details
Employee Salary
SCREEN SHOTS
Login Form:
MDI Form:
Donor Details
Hospital Details
Outsider Information
Equipment Details
Employee Details
Camp Details
Transaction Details
REPORTS
Donor Report
CODING
Login Form:
If IsNumeric(Trim(txtUsername.Text)) Then
MsgBox "Please Enter Characters Only", vbInformation
txtUsername.Text = ""
txtUsername.SetFocus
Exit Sub
End If
BCA V SEM-BLOOD BANK MANAGEMENT SYSTEM
P a g e | 32
On Error GoTo e1
e1:
If err.Number = 3709 Then
ElseIf Not dbrec.EOF Then
USER_NAME = txtUsername.Text
MsgBox "!!! Login Done Successfully !!! " & vbCrLf & vbCrLf & "User
Name:- " & USER_NAME & vbCrLf & vbCrLf & "Time :-" & Time, vbOKOnly
+ vbInformation, "Login"
MDIForm1.Show
Unload Me
BCA V SEM-BLOOD BANK MANAGEMENT SYSTEM
P a g e | 33
Else
Call login
End If
dbrec.Close
dbcon.Close
End Sub
End Sub
MDI Form
Form1.Show
End Sub
End Sub
Outsidertransaction.Show
End Sub
Donor Transaction
Exit Sub
End If
If dtpTo.Value > Date Then
MsgBox "select 2nd Date as Todays Date"
Exit Sub
End If
DonorTransReport
End Sub
Function DonorTransReport()
Dim rs As New ADODB.Recordset
Dim strsql As String
Module1.Connect
rs.Open "select * from Trans where Recipient_Type=1", cnn, adOpenDynamic,
adLockOptimistic
If rs.RecordCount < 1 Then
MsgBox "Record not present", vbInformation
Exit Function
Else
Set DRDonorTrans.DataSource = rs
With DRDonorTrans
.Sections("Section2").Controls.Item("lblFrom").Caption =
Format(dtpFrom.Value, "dd-MMM-yyyy")
.Sections("section2").Controls.Item("lblTo").Caption = Format(dtpTo.Value,
"dd-MMM-yyyy")
BCA V SEM-BLOOD BANK MANAGEMENT SYSTEM
P a g e | 40
End With
With DRDonorTrans.Sections("Section1").Controls
.Item("txtDate").DataField = "Date"
.Item("txtTransNo").DataField = "Transaction_ID"
.Item("txtID").DataField = "Recipient_ID"
.Item("txtDonorName").DataField = "Recipient_Name"
.Item("txtBloodGroup").DataField = "BloodGroup"
.Item("txtNOB").DataField = "NoOfBags"
End With
DRDonorTrans.Refresh
DRDonorTrans.Show
End If
rs.Close
End Function
Hospital Transaction
Exit Sub
End If
If dtpTo.Value > Date Then
MsgBox "select 2nd Date as Todays Date"
Exit Sub
End If
HospitalTransReport
End Sub
Function HospitalTransReport()
Dim rs As New ADODB.Recordset
Dim strsql As String
Module1.Connect
rs.Open "select * from Trans where Recipient_Type=2", cnn, adOpenDynamic,
adLockOptimistic
If rs.RecordCount < 1 Then
MsgBox "Record not present", vbInformation
Exit Function
Else
Set DRHospitalTrans.DataSource = rs
With DRHospitalTrans
.Sections("Section2").Controls.Item("lblFrom").Caption =
Format(dtpFrom.Value, "dd-MMM-yyyy")
.Sections("section2").Controls.Item("lblTo").Caption = Format(dtpTo.Value,
"dd-MMM-yyyy")
BCA V SEM-BLOOD BANK MANAGEMENT SYSTEM
P a g e | 42
End With
With DRHospitalTrans.Sections("Section1").Controls
.Item("txtDate").DataField = "Date"
.Item("txtTransNo").DataField = "Transaction_ID"
.Item("txtID").DataField = "Recipient_ID"
.Item("txtHospitalName").DataField = "Recipient_Name"
.Item("txtBloodGroup").DataField = "BloodGroup"
.Item("txtNOB").DataField = "NoOfBags"
.Item("txtAmount").DataField = "Amount"
End With
DRHospitalTrans.Sections("Section5").Controls.Item("funTotal").DataField =
"Amount"
DRHospitalTrans.Refresh
DRHospitalTrans.Show
rs.Close
End If
End Function
Module1.Connect
BCA V SEM-BLOOD BANK MANAGEMENT SYSTEM
P a g e | 45
Camp Schedule
BCA V SEM-BLOOD BANK MANAGEMENT SYSTEM
P a g e | 46
Case vbNo:
Exit Sub
End Select
End Sub
sql = "update CampSchedule set Name='" & txtName.Text & "',Address1='" &
txtAdd1.Text & "',Address2='" & txtAdd2.Text & "',Address3='" & txtAdd3.Text
& "',PinCode='" & txtPinCode.Text _
& "',Contact_Person='" & txtPerson.Text & "',Phone_No='" & txtPhNo.Text &
"',Scheduled_Date='" & dtpDate.Value & "',No_Of_Beds='" & txtBeds.Text & "'
where Code='" & txtCode.Text & "'"
cnn.Execute sql
ListCampSchedule
MsgBox "Camp schedule Record Modified", vbInformation, "Camp Schedule"
End Sub
rs.MoveNext
Next
txtCode.Text = nn
rs.Close
cmdNew.Enabled = False
cmdSave.Enabled = True
cmdScancel.Enabled = True
cmdModify.Enabled = False
cmdSearch.Enabled = False
cmdDelete.Enabled = False
cmdClear.Enabled = False
End Sub
cmdSave.Enabled = False
cmdScancel.Enabled = False
cmdModify.Enabled = True
cmdSearch.Enabled = True
cmdDelete.Enabled = True
cmdClear.Enabled = True
End Sub
msfCamp.TextMatrix(slno, 7) = rs("Phone_No")
msfCamp.TextMatrix(slno, 8) = rs("Scheduled_Date")
msfCamp.TextMatrix(slno, 9) = rs("No_Of_Beds")
slno = slno + 1
If msfCamp.Rows = slno Then
msfCamp.Rows = msfCamp.Rows + 1
End If
rs.MoveNext
Next
rs.Close
End Function
rs.Close
End Sub
Next
rs.Close
End Function
ValidateIndividual = False
Exit Function
End If
SOFTWARE TESTING
White box testing is a test case design method that uses the control structure of the
procedural designs to derive test cases. As we are using a non procedural language,
there is very small scope for the white box testing. Whenever it is necessary, there
the control structures are tested and successfully passed all the control structures
with a very minimum error.
Black box testing focuses on the functional requirements of the software. It enables
to derive sets of input conditions that will fully exercise all functional requirements
for a program. The black box testing finds almost all errors, if finds some interface
errors and errors in accessing the database and some performance errors in b lack
box testing we use mainly two techniques: equivalence partitioning the boundary
volume analysis technique.
Equivalence partitioning:
In this method we divide input domain of program into classes of data from
which test cases are derived. An Equivalence class represents a set of valid or
invalid or a set of related values or a Boolean conditions. The equivalence for
these is:
Input condition requires a range – in the range or out of range two classes
Input condition specifies a member of set-belongs to a set or not belongs to
the set of two classes.
Input condition id Boolean- valid or invalid Boolean condition two classes.
System Testing:
System testing is designated to uncover weakness that was not detected in
the earlier tests. The total system is tested for recovery and fallback after various
major failures to ensure that no data are lost. An acceptance test is done for the
validity and reliability of the system. The philosophy behind the testing is to find
error in project. There are many test cases designed with this in mind.
Code Testing:
This strategy examines the logic of the program. Here only syntax of the code
is tested. In code testing syntax error are corrected, to ensure that the code is
perfect.
In our project, logic is complex but a very interesting one. The syntax and the
statements are all tested line by line by line for error correction. During
compilation each line has to be checked for errors. This is done by code testing.
Unit Testing:
The first level of testing is called unit testing. Here different modules are
tested against the specifications produced during the design of the modules. Unit
testing is done to test the working of individual modules with test oracles.
System Testing:
The next level of testing is system testing and acceptance testing. This
testing is done to check if the system has met its requirements and to find the
external behavior of the system.
Integration testing
Acceptance testing
Integration Testing:
The next level of testing is called the Integration Testing. In this many
tested modules are combined into subsystems, which were then tested.
Test case data is prepared to check the control flow of all the modules and to
exhaust all possible inputs to the program. Situations like treating the modules
when there is no data entered in the test box is also tested.
are tested and combined together or integrated together to form a bigger module or
sometimes a whole system. This is done by integration testing.
In our project, even though the coding is divided into many parts. At the
end, it is all integrated into one big module and tested.
Acceptance Testing:
This testing is performed finally by user to demonstrate that the
implemented system satisfies its requirements. The user gives various inputs to get
required outputs.
In our project, we have designed it in a way where any form of people can
understand and use it.
It is user friendly
It can be implemented everywhere
It can hold any number of records
The flow of the project is easy and understanding
Specification Testing:
Specification testing is done to check if the program does what it should do
and how it should behave under various conditions or combination and submitted
for processing in the system and it is checked if any overlaps occur during the
processing.
In our project, the main aim is to specify the needs of maintaining the data base
correctly and efficiently. This specification is done by testing it according to
various conditions.
The total system is tested for recovery and fallback after various major failures
to ensure that no data are lost during an emergency. An acceptance test is done to
the user about the validity and reliability of the system.
In our project, we have assigned specific time limit to certain parts, which is
very much important. The time taken to load and unload the forms and progress
bar and time interval everything must be fast and within the time limit.
Performance time testing takes care of all this.
IMPLEMENTATION
The final and important phase in system life cycle is the installation of the new
system. The term installation has different meaning, ranging from the conversion
of basic application a complete replacement of a computer system. The procedure,
however are virtually the same. Installation is the process of converting a new
system into an operational one. It involves user training and successful running of
the developed system.
In the installation phase the user and the system manuals are prepared handed over
to the user to operate the developed system. The objective of each manual is the
same but the target customers may be different.
The user manual is aimed at those who would be using the system but not
interested in technical information about the insides of the system, or
implementation of login within the system.
Security measures
Input’s and output’s formats
Do’s and don’ts
The system manual is aimed at those persons who would ne maintain, changing
and enhancing system and also the people who are interested in the implementation
of the logic within the system.
FUTURE ENHANCEMENTS
The system has been developed under the given conditions and is found to
work effectively and efficiently. We should make the possible use of the
techniques. The basic purpose of all the innovations in the technology is for our
betterment.
The system has been tested with sample covering .All possible options and
their performances are good. Since this system is flexible and modular, further
modifications of this package can be easily incorporated. The system can be easily
placed on the office so that best work efficiently.
CONCLUSION
The main focus of this project is to less in human efforts. The maintenance of the
record is made efficient, as all the records are stored in the SQL database.
It is user interactive and effective than the existing system. The flexibility of visual
basic helps to maintain the “BLOOD BANK MANAGEMENT SYSTEM” more
efficiently.
Finally, we are thankful to all the people who have given us their hearty support in
this endeavour.
BIBILOGRAPHY
The following are the books that have been referred for the successful completion
of our project work: