Professional Documents
Culture Documents
Documented by:
Honorable mentions:
GHADEER MOHAMMED
YOUSEF SHAWQI
Supervision:
i
DEDICATION
We are pleased to extend our sincere thanks to our partners who helped us and
worked with us to make this project and hopefully it will also fit to your liking
ii
ACKNOWLEDGMENTS
iii
ABSTRACT
Digitalizing the process would make it much easier to store and retrieve data
whenever needed. A system must be built to keep the data safe and neat.
Using the help of some data experts, A database would be made available for
storing different data that the bank needs, like the donations and the available blood
and the types and etc…
iv
TABLE OF CONTENTS
Dedication …………..…………………………………………………..…………… ii
Abstract …………………...…………………..…...…..……………….……….…... iv
GLOSSARY……………………………………………..………………….………... v
List of notations……………………………………………………………………… vi
List of Abbreviations ………………………………………………………………. vii
Project overview………………………………………………………..……..…… viii
Chapter 1: ……………………………………………………………………………1
1.1: Introduction …………………………………………………………………………… 1
Chapter 2: …………………………………………………………………………... 2
Chapter 3: ….……………………………………………….……………………… 3
Conclusion …...………………………………………………………………….….12
***
GLOSSARY
Abbreviation Definition
ERD Entity Relationship Diagram
DBMS Database Management System
v
LIST OF NOTATIONS
Symbol Meaning
Entity
Attributes
Relationship
Arrow
Primary key
vi
LIST OF ABBREVIATIONS
vii
PROJECT OVERVIEW
This project is a database for an Blood Bank System , and we have used
MS Access to create this database. This project was built based on the data
given by the client and the purpose of this database.
viii
CHAPTER1
1.1: INTRODUCTION
Definition of Database:
MS Access:
1
CHAPTER 2
2.1: Methodology:
We will speak about this project in three points:
C: Taking information from the client and then converting it to ERD and schema .
D: Create reports and forms and queries According to the customer's desire.
In this project, we designed a database for a Blood Bank System based on the
information that the client gave us. We made the relationships between the tables, based
on ERD, Schema, which is related to the work.
2
CHAPTER 3
We want to develop a Blood Bank System using MS Access. Hospitals have a blood
bank and there are also separate blood banks. This system works according to the
following:
There are 4 main blood groups (types of blood): A, B, AB and O. Donors donate a
specific blood type . This system is supposed to make it a much simpler and easier
process for the doctors to insert the donors’ data and also have access to blood supply
requests that patients need in the hospital.
3.1.1: Tables:
A table is an object that is used to define and store data. When you create a new table,
Access asks you to define fields which is also known as column headings. Each field
must have a unique name, and data type.
Tables contain fields or columns that store different kinds of data, such as a name or
an address, and records or rows that collect all the information about a particular
instance of the subject, such as all the information about a customer or employee etc.
You can define a primary key, one or more fields that have a unique value for each
record, and one or more indexes on each table to help retrieve your data more quickly.
3
These two tables show each donor’s personal data (like name, ID, SNS, etc..) as
well as their donation data (their blood type, chronic diseases, donated units, etc..).
This table shows the doctor’s data so they can use the login form (down below) to
get access to the database. Their names, IDs, SNSs and of course passwords are stored
in this table so they can check into the database.
And the table right here is supposed to show the patients, as this system is designed
for a hospital. Their data is all stored here like their names, IDs and of course blood
type in case of emergencies, as well as other data about them. 4
And lastly, the requests table which they can use to insert if there’s any shortage in
a specific blood type that might be needed for a specific patient.
3.1.2: Relationships:
A connection between a parent table and the child table exists by referencing the
parent's primary key. The reference's behavior defines the relationship type between
two database tables.
1. One-to-one (1:1)
2. One-to-many (1:N)
3. Many-to-many (N:N)
A line connecting two tables represents a relationship, while the symbols on the line's
end represent the exact relationship type.
5
The relationships between the tables in the blood bank database.
3.1.3: Queries:
A query is an object that provides a custom view of data from one or more tables.
Queries are a way of searching for and compiling data from one or more tables. Running
a query is like asking a detailed question of your database.
You can define queries to Select, Update, Insert, or Delete data. You can also define
queries that create new tables from data in one or more existing tables.
6
On the left: query of the amount of blood available of each blood type.
Query of the requested blood and the amount and the patient its requested for.
7
3.1.4: Forms:
A form is an object in a desktop database designed primarily for data input or display
or for control of application execution. You use forms to customize the presentation of
data that your application extracts from queries or tables.
Login form that doctors use to get to the Main Screen. (Next form)
The main form that holds all the functions of the database accessed by doctors.
8
On the left: The form used for donor’s data entry.
On the right: The form used for donation’s data entry, which opens right after entering
and saving donor’s data.
------------------------------------------------
9
3.1.5: Reports:
Anything you plan to print deserves a report, whether it is a list of names and
addresses, a financial summary for a period, or a set of mailing labels.
Reports are useful because they allow you to present components of your database
in an easy-to-read format. You can even customize a report's appearance to make it
visually appealing.
10
A report expressing the data in the donors’ chronic diseases query.
11
CONCLUSION
After everything has been digitalized, processes has been quite faster.
Communication, data collection and organization, international transactions and many
more.
The project that has been displayed previously should make dealing with the process
of blood bank management much easier. Not the perfect system, but good enough to
help keep the data neat and safe.
12