Blood bank management system Essay
Blood bank management system
BLOOD BANK MANAGEMENT is a software application to maintain day to day transactions in a blood bank. This software help to register all the donors, Blood collection details, blood issued details etc. Blood banks collect, store, and provide blood. Typically, these banks collect blood from voluntary blood donors. The banks then sort blood by type, check blood to make sure it is free of disease and then store it for future use. The main mission of a blood bank is to provide life-saving blood to hospitals and other health care facilities. Blood cannot be created by any means, it can only be collected from the Humans i.e. donors. A blood bank is a bank of blood or blood components, gathered as a result of blood donation, stored and preserved for later use in blood transfusion..to satisfy blood necessity, to buy, sale and stock.
Online Blood Bank is aims serving for human welfare. We have all the information, you will ever need. Many people are here for you, to help you, willing to donate blood for you anytime. We have done the entire job, rest is yours. Search the blood group you need. You can help us by registering on Online Blood Bank if you are willing to donate your blood when needed. As a proud member of Blood Bank and a responsible human being, you can help someone in need. So donate blood in online.
Blood Bank is aims serving for human welfare. We have all the information, you will ever need. Many people are here for you, to help you, willing to donate blood for you anytime. We have done the entire job, rest is yours. Search the blood group you need. You can help us by registering on Online Blood Bank if you are willing to donate your blood when needed. As a proud member of Online Blood Bank and a responsible human being, you can help someone in need. So donate blood in bank. In this project mainly 3 modules are there.
This module focuses on the both donors & acceptors. Each member in a donor & acceptor is given a user id and password, which identifies him uniquely. The member is given a login form. he enters the login details user id and password. .. The options given to
• Maintain donor details
• Maintain referral once
• Update donor details
• View Experiences
Whenever a user wants to change his / her password he can select the change password option. The system displays the form, which asks him for his old password and new password. The system then compares the old password with the existing password in the database…
Each member in a Donor is given a user id and password, which identifies him uniquely. The member is given a login form. he enters the login details user id and password. .. The options given to a each member in a staff are Change password
Find a Blood group
Why donate blood
who needs blood
Find a Donor
Refer a friend
In this you can store the information about Acceptors.
Find a blood group.
Who needs blood
Operating System: Windows XP
Front End: NET (Active Server Pages, Visual basic ,Java Script) Back end :
Hardware requirements :
MINIMUM P-IV SYSTEM
40 GB HDD
The person who donate the blood
The person who accepts the blood
An act of transfusing donated blood, blood products, or other fluid into the circulatory system of a person or animal.
The first section tells about introduction of blood bank management system and its scope. The remaining sections of this document provide a general description, including characteristics of the users of this project, the product’s hardware, and the functional and data requirements of the product. General description of the project is discussed in section 2 of this document. Section 3 gives the functional requirements, data requirements and constraints and assumptions made while designing the E-Store. It also gives the user viewpoint of product. Section 3 also gives the specific requirements of the product. Section 3 also discusses the external interface requirements and gives detailed description of functional requirements. Section 4 is for supporting information.
Now the description of SRS is follow:-
2.1 Product Perspective
2.2 Product Functions
2.3 User Characteristics
3. Specific Requirements
3.1 External Interfaces
3.3 Performance Requirements
3.4 Logical Database Requirements
3.5 Design Constraints
3.6 Assumptions and Dependencies