ACKNOWLEDGMENT
The enduring pages of the work are the cumulative sequence of extensive guidance and
arduous work. We wish to acknowledge and express our gratitude to all those without
whom our thesis could not have been a reality. We feel very delighted to get this rare
opportunity to show our profound senses of reverence and indebtedness to our thesis
supervisor Ms. Rosina Surovi Khan for the information she provided to us through the
lecture sittings and her invaluable timely advice and guidance. We would like to extend our
sincere thanks to her for giving us her precious time and for being always available to us in
order to clarify our doubts regarding the thesis. This thesis is dedicated to our parents who
have given us the opportunities of education from the best institutions and support
throughout our lives. The last but not the least we would like to thank all those who have
directly or indirectly helped and cooperated in accomplishing this thesis.
Abstract
A database is the single most useful environment in which to store data and an ideal tool to
manage and manipulate that data. The benefits of a well-structured database are infinite,
with increased efficiency and time-saving benefits. Our team’s interest is centered around
this area. At the very start, we create a database on blood-bank management system. We
use Microsoft SQL Server for this purpose. We determine attributes and entities and figure
out relationships among entities. Then we draw the entity-relationship diagram, convert it to
a relational model (relational tables) and normalize the tables. We implement the design,
create tables and insert values inside the tables using sql server. We execute sample queries
on the system and verify that our system contains all required information making retrieval
of the information fast and efficient. In part II of the thesis, we convert the database tables
of the system to text files. Using exact and approximate string matching algorithms, we
match a string in question with the strings in text files and get the index of exactly matched
strings for the former and obtain approximately matched strings displaying edit distances
between the two for the latter.
DATABASE DESIGN
2.1
The Entity-Relationship Model The entity-relationship (E-R) model was developed to
facilitate database design by allowing specification of an enterprise schema that represents
the overall logical structure of a database. The E-R data model is one of the several
semantics data models; the semantic aspect of the model lies in its representation of the
meaning of the data. The E-R model is very useful in mapping the meanings and interactions
of real-world enterprises onto conceptual schema. The E-R data model has three basic
notions: entity-sets, relationship sets and attributes. Entity sets: An entity is a thing or object
in the real world that is distinguishable from all other objects. It has a set of properties, and
the values for some set of properties may uniquely identify an entity. It is also a set of
entities of the same type that share the same properties. Relationship sets: A relationship is
an association among several entities. It is a set of relationships of the same type. The
association between entity sets is referred to as participation. The function that an entity
plays in a relationship is called that entity’s role. Attributes: An entity is represented by a set
of attributes. Attributes are descriptive properties possessed by each member of an entity
set. The designation of an attribute for an entity set expresses that the database stores
similar information concerning each entity in the entity set; however, each entity may have
its own value for each attribute. [1]
Our E-R diagram represents the Blood-Bank Management system. It has eight entity sets.
They are— a) Donor: (Attributes- dName, dId, sex, age, dreg_date, db_grp).
b) District: (Attributes- dis_id, dis_name).
c) Registration_Staff: (Attributes- rs_id, rs_name, sex).
d) Blood_Recipient: (Attributes- rId, sex, age, r_regdate, rName, b_qnty, rb_grp).
e) Blood_Sample: (Attributes- b_group, sample_no, status).
f) Disease_Recognizer: (Attributes- drecog_id, drecog_name, sex).
g) Blood_Processing_Manager: (Attributes-bm_id, bm_name, sex).
h) Hospital: (Attributes- hId, hName, hb_grp, hb_qnty).
Abbreviations of all attributes are given in relational schema. Some notes about entity sets,
their attributes and cardinalities among them----
Donor- Who donates blood. When a donor will donate, an id(a serial number will be given
for a specific identification (primary key)); age, sex, name, registration date (dreg_date) and
blood group will be stored in the database under entity Donor.
District- Every district’s/location’s id is different (primary key).
Registration_Staff- Registration staffs will register the information of donors and the
recipients.
Disease_Recognizer-Disease recognizer will test blood samples whether the samples are
contaminated or okay.
Blood_Processing_Manager- They will take orders from the hospitals and fulfill their needed
requirements of blood samples.
Blood_Sample- The quantities of blood that the Blood_bank has. Their group, sample_no,
status will be stored.
Hospital- Hospitals of each district, where blood samples are needed, also included in the
database.
Blood_Recipient- Who needs blood. A recipient’s id, name, age, sex, the blood sample’s
group information will be stored in database.
