2. 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.
3. Scope and Objectives:
The specification builds on the experience of users of IT technology in blood
transfusion that is currently available and informs both Connecting for Health (CfH)
and commercial companies producing both hardware and software.
The main objective of this 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.
4. Problem Definition of Existing system:
Entering the details about the blood groups, members, addresses etc. And
tracking the database is complicated when the details are maintained
manually. This makes the maintenance of schedule erroneous.
Limitation of manual system:
It is time consuming.
It leads to error prone results.
It consumes lot of men power to better results.
It lacks of data security.
Retrieval of data takes lots of time.
Percentage of accuracy is less.
Reports takes time to produce.
5. Proposed System:
This system is used for maintain whole information about campus.
In this project mainly 3 modules are there.
Admin
Donors
Acceptors
6. Action Plan:
Literature survey 2 Days
Analysis/Design 3 Days
Coding 6 Days
Review of coding 2 Days
Documentation 2 Days
Total 2 Weeks
7. System requirements:
Operating system : Window XP & higher.
IDE : visual studio.net 2005 / 2010.
Front end : ASP.NET.
Language : C#.NET.
Database : SQL server 2000/2005.
Hardware Requirement:
Intel P4 1.5GHz or above.
512MB ram.
80GB HDD Minimum.
8. BENEFITS
1. Blood donation management.
2. Blood procurement.
3. Blood safety.
4. Blood and blood component production.
5. Blood and blood component storage and distribution.
6. Blood transfusion management.
7. Routine blood transfusion.
8. Emergency issue of blood.
9. Management of returned and unused blood units.
10 .To provide online information flow for the management
Of blood donors and recipients.
9. Functional requirements:
Login of admin.
Blood Donor
Change the login password of admin.
Register the donor by himself.
Register the donor by system admin.
Login of the donor
Change the login password of the donor.
Change personal, contact details by the donor himself.
Change personal, contact details by system admin.
Withdraw reg. details by the donor.
Withdraw reg. details by the admin.
Send blood donation details to the relevant donors.
Send blood testing details.
10. Other non functional requirements:
A characteristic of a quality SRS is that in addition to describing the
functional requirements of a system, it will also provide detailed coverage of
the non-functional requirements. In practice, this would entail detailed
analysis of issues such as availability, security, usability and maintainability.
However, as this document is only an outline specification, it does not
contain the same degree of rig our that would normally be expected in a
formal SRS. Therefore, the sections below should be seen as indicative rather
than providing specific (i.e. testable) requirements.
11. Capacity, scalability and availability
Maintainability
Other Requirements
Security
Performance requirements
Should run on 500 GHz, 64MB machine
Should have a proper internet connection.
The response time for occurs a change will be no more than
4 seconds.
The response time for access the database will be no more
than 5 Seconds.
12. FUNCTIONAL REQUIREMENTS
Use case diagrams are used to describe functional requirements of the
system. The diagrams are draw below.
26. Admin Donor
Official
website
Login Admin
Change the login password
of admin
Register the donor by
himself
Login Donor
Change the login password of
donor
Change personal contact
detail by donor
Change the personal contact
details by admin
Withdraw registration details
by donor
Withdraw registration details
by admin
Send blood testing
details
Send blood donation details to
relevant donor
Display Result
Send registration detail of
donor
27. Official Website
Registered donor
by himself
Login Admin
Send details to
admin
Withdraw detail
of donor
Login donor
Start
End
If not
eligible
If not
eligible
28. user
-User name
-Password
-Database ID
+login()
+Change password
+Donor registration
+Change details
+Withdraw donor()
Report
-Report Name
-Report duration
+Print report()
+Display report
Donor
-Registration Number
-Blood group
-ID Number
-Email ID
+Future-donation-detail()
+Donation-contribution-detail()
+Edit-Profile()
System Administrator
-Database ID
+Print Report()
+Search Donor()
+Inform blood testing details()
Database Access
Database ID
+Access database()
+Store details()
+Remove details()
Donation
Test Detail
Alert
SMS Alert
Email Alert-Mobile Phone number
-Database ID
+Send SMS & Save()
+Read SMS & Save()
-Donor registration number
-Donor ID number
-Database ID
+Send blood testing details()
-Blood group
-Donation date
-Donation venue
+Future donation details()
+Clarify Alert()
+Display Alert Details()
-Alert Type
-Email address
-Database ID
+Send Email & Save()
+Read Email & Save()
29. Login admin
Register the donor by himself
Change login password of donor
Login of the donor
Register the donor by Admin
Change the login password Of
admin
Send blood details to relevant
donor
Withdraw reg. Details by the
Admin
Withdraw reg. Details by the
donor
Send blood testing details
Change personal contact details
by donor himself
Change personal contact detail
by system Admin