Complete Information About Blood Bank Management Software With Sequence, Class,and Use Case Diagram

1. Introduction
This project is developed to manage the blood stock in the "BLOOD
BANK" and the blood prices are maintained in the database. New blood details are entered in to
the project to manage blood details. Blood donor details are entered and maintained in the
database.
Blood sales and blood purchase are entered and maintained in this project. Blood stock
reports, sales reports and blood purchase reports are managed in this project.
Characteristics
The main objective of specification is to support the automated tracking of blood products from
the initial ordering of a blood transfusion for a patient, through to the taking of a blood sample
for cross matching, to administration of a blood transfusion and subsequent updates to care
records. The scope of the specification includes the following scenarios:
• Routine blood transfusion.
• Transfusion for special requirements (for example, cytomegalovirus (CMV) seronegative
blood, irradiated blood or antigen negative blood).
• Emergency issue of blood.
• Management of returned and unused blood units.
Functional Requirements
• Login of admin: System should allow to login as an administrator.
• Blood Donor: System should be able to hold details of blood donors.
• Change the login password of admin: System should allow administrator to change the
admin password.
• Register the donor by himself: System should allow that the donor can register himself.
• Register the donor by system admin: System should allow the administrator to register
the blood donor.
• Login of the donor: There should be facility of donor login.
Hasham

2. • Change details by system admin: System should allow the admin to change the personal,
contact details of the blood donor.
• Withdraw reg. details by the donor: System should allow the donor to withdraw his own
registration details.
• Withdraw reg. details by the admin: System should allow the admin to withdraw the
registration details of the donor.
• Send details to donors: System should allow the admin to send the blood donation details
to the relevant donors.
• Send blood testing details: System should allow to send blood testing details to the
doctor.
Non-functional Requirements:
• System Performance: This section describes the performance requirements of the system
from the customers’ perspective.
• System Capacity: This section describes the size of the system from the customers’
perspective.
• Security: This section outlines the security requirements for any new systems design.
• Business Continuity & Disaster Recovery: This section outlines the security requirements
for any new systems design. Each requirement is listed below with a brief description.
• Client: NHSBT support a number of clients but is committed deploying applications
via Windows Terminal Services with Citrix Presentation Server to Windows Based
Terminals wherever possible. Each type of client required for this system is specified
below.
Hasham

3. Sequence Diagram
Hasham

4. Class Diagram
Hasham

5. Use Case Diagram
Hasham