0% found this document useful (0 votes)
44 views7 pages

Project Proposal

This document discusses developing a website for blood banks to manage donor and blood stock information. The objectives are to allow donors to view their information, maintain centralized donor and donation records, inform donors of results, and enable administrators to search, request, and notify donors and hospitals of blood availability. The goal is to manage donor, blood, blood group, and blood bank details through registration, data input, donation recording, blood requests, and notifications. This improves on existing paper-based systems by making information easily accessible online and maintaining updated records.

Uploaded by

Prachi Rathod
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
44 views7 pages

Project Proposal

This document discusses developing a website for blood banks to manage donor and blood stock information. The objectives are to allow donors to view their information, maintain centralized donor and donation records, inform donors of results, and enable administrators to search, request, and notify donors and hospitals of blood availability. The goal is to manage donor, blood, blood group, and blood bank details through registration, data input, donation recording, blood requests, and notifications. This improves on existing paper-based systems by making information easily accessible online and maintaining updated records.

Uploaded by

Prachi Rathod
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

SHREE SWAMINARAYAN COLLEGE OF COMPUTER SCIENCE

1. INTRODUCTION
1.1 Background
A blood donation is a process whereby a person voluntarily has blood drawn
to be used for future transfusions when in need at hospitals for treatment
procedures that require them. Donation may be of whole blood (blood drawn
directly from the body) or of specific components of the blood; such as red
blood cells, plasma, and platelets. Blood banks often participate in the process
of collecting blood and other procedures such as managing stocks, approving
blood requests and updating donation information. The inspiration of this
project is to improve blood banks and to develop a blood bank information
system which focuses on making an online system that is accessible for both
donors and administrators. Donors can directly receive information regarding
their previous blood donations, including their blood results and donation
history, in order to easily schedule their next donations. They can also update
the personal information through the system, without having to contact the
blood bank registry. The administrator is also responsible for responding to the
blood requests and checking the stocks in the blood bank’s inventory.

1.2 Objective
The goal of the project is to develop a website for blood banks to manage
information about their donors and blood stock. The main objectives of this
website development can be defined as follows:
• To develop a system that provides functions to support donors to view
and manage their information conveniently.
• To maintain records of blood donors, blood donation information and
blood stocks in a centralized database system.
• To inform donors of their blood result after their donation.
• To support searching, matching and requesting for blood convenient
for administrators.
• To provide a function to send a notification directly to the donor for
their user account and the hospital, the availability of the blood bag.

1.3 Purpose and Scope


This project is aimed to developing an online Blood Donation Information.
The entire project has been developed keeping in view of the distributed client
server computing technology, in mind. Through this application any person
who is interested in donating the blood can register himself in the same way if
any organization wants to register itself with this site that can also register.
Admin is the main authority who can do addition, deletion, and
modification if required. The project has been planned to be having the
view of distributed architecture, with centralized storage of the database. The
standards of security and data protective mechanism have been given a big
choice for proper usage.

0120044 DRASHTI SHUKLA


1 SAVE RED
0120025 PRACHI RATHOD
SHREE SWAMINARAYAN COLLEGE OF COMPUTER SCIENCE

1.4 Goal
The goal of the Blood Bank Management System is to manage the details of
Blood, Donor, Blood Group, Blood Bank. The project is totally built at
administrative end and thus only the administrator is guaranteed the access.
The blood donation management system (BDMS) is a 24 × 7 system provides
services to the hospitals and other users. The system is easy to maintain all the
information about the blood donor. Proposed work provides services to
persons who pursue donors who are willing to donate blood.

1.5 Concept of existing system


The system functions and features of existing system are mentioned in the
following:
• Difficult to stay updated for camps and other programs.
• Tedious task is the result for managing data.
• Risk of mismanagement and of data due to paper work dependency.
• Less Security.
• No proper coordination between different Applications and Users.
• Fewer Users – Friendly

1.6 Concept of purposed system


• Registration: This function allows the donor and administrator to register as
a user to interact with the system. The system requires the user to login before
viewing and editing any information.
• Data is input by the Administrators: The donor’s information and donation
records can be stored in database and controlled and update by administrator.
The administrator is responsible for keying the received data into the system.
• Recording donation records: The system can record data of whole blood
which is sent from the hospital.
• Blood requests: The hospital can request blood by contacting and connecting
to the blood bank.
• Notify the viewers: The donor’s account will receive notifications about
camp, volunteering or special achievements. Hospitals can also receive
notification responding to their requested blood whether it is available in our
stock or not.

0120044 DRASHTI SHUKLA


2 SAVE RED
0120025 PRACHI RATHOD
SHREE SWAMINARAYAN COLLEGE OF COMPUTER SCIENCE

1.7 Advantages and Disadvantages of new system


The project is identified by the merits of the system offered to the user.
The merits of this project are as follows:
• It’s a web-enabled project.
• This project offers user to enter the data through simple and interactive
forms. This is very helpful for the client to enter the desired
information through so much simplicity.
• The user is mainly more concerned about the validity of the data,
whatever he is entering. There are checks on every stages of any new
creation, data entry or updation so that the user cannot enter the invalid
data, which can create problems at later date.
• Sometimes the user finds in the later stages of using project that he
needs to update some of the information that he entered earlier. There
are options for him by which he can update the records. Moreover
there is restriction for his that he cannot change the primary data field.
This keeps the validity of the data to longer extent.
• User is provided the option of monitoring the records he entered
earlier. He can see the desired records with the variety of options
provided by him.

The demerits of the new system are as follows:


• The size of the database increases day-by-day, increasing the load on
the database back up and data maintenance activity.
• Training for simple computer operations is necessary for the users
working on the system.

0120044 DRASHTI SHUKLA


3 SAVE RED
0120025 PRACHI RATHOD
SHREE SWAMINARAYAN COLLEGE OF COMPUTER SCIENCE

2. Requirement Analysis
2.1 Problem Defination
• Cannot Upload and Download the latest updates.
• No use of Web Services and Remoting.
• Risk of mismanagement and of data when the project is under
development.
• Less Security.
• No proper coordination between different Applications and Users.
• Fewer Users – Friendly

2.2 Requirement Specification


a) Functional Requirements

Access Website:

Software operator should be capable to access web-application through


either an application browser or similar service on the PC. There
should not be any limitation to access website.

Software operator Registration:

Given that software operator has accessed web-application, then he


software operator should be able to register through the website. The
donor software operator must provide first name ,gender, blood or
plasma group, location, contact , software operator name and
password.

Search result in a list view:

Search result can be viewed in a list. Each element in the list represents
a specific donor. Each element should include first name, gender, blood
or plasma group, contact according to the software operator position.

Request Blood or plasma:

Software operator(Clinic) should be able to request for blood or plasma


at emergency situation, software operator need to define blood or
plasma group, location, required date, contact. The blood or plasma
requested will be sent to blood or plasma bank and then to the
inventory to check the availability. If available, the requested blood or
plasma will be sent to the requested donor(Clinic).

0120044 DRASHTI SHUKLA


4 SAVE RED
0120025 PRACHI RATHOD
SHREE SWAMINARAYAN COLLEGE OF COMPUTER SCIENCE

b) Non-Functional Requirements :
Maintainability:

The Blood bank Management System have must have high level of
Maintainability.

Serviceability

If issue arises in the Blood bank Management System, then the project must be
programmed in such a way that developer can service it again.

Environmental

The Blood bank Management System must be working in latest operating


system environments like windows 7, windows 8, windows 10 and so on.

Data Integrity

All the data in the Blood bank Management System must be accurate and
reliable.

Usability

The Blood bank Management System must have a good looing user friendly
interface.

Interoperability

The Blood bank Management System must work with or use the parts or
equipment of another system.

Capacity

The Blood bank Management System must fulfill on storage requirements,


today and in the future. The Blood bank Management System must be scale up
for increasing volume demands.

Performance

The Blood bank Management System must perform well in different


scenarios.

Security

The Blood bank Management System must be secured with proper user name
and passwords.

Availability

The Blood bank Management System must be available 24 hours a day with
no bandwidth issues.

0120044 DRASHTI SHUKLA


5 SAVE RED
0120025 PRACHI RATHOD
SHREE SWAMINARAYAN COLLEGE OF COMPUTER SCIENCE

2.3 SOFTWARE AND HARDWARE REQUIREMENT:


2.3.1 Software:
Items Version
Browser Chrome, Firefox
Front end Python(django)
Back end Mysql
Software Xammp, Pycharm
Design Html, Css

2.3.2 Hardware:
Item Minimum Recommended
Requirement
RAM 4GB 8GB
Processor Intel i3 Intel i5
Hard disk space 10GB 20GB

2.4 Planning and Scheduling

Activities Days
Analysis 12
Designing 15
Coding 30
Testing 10
Implementation 5

0120044 DRASHTI SHUKLA


6 SAVE RED
0120025 PRACHI RATHOD
SHREE SWAMINARAYAN COLLEGE OF COMPUTER SCIENCE

2.5 Preliminary Production Description


There are two internal users involved in this system. The user requirements are
considered as follows:
• Donor
1. To be able to view their donation records, including where and when they
made donations, and the blood results for each, to learn of their donated blood
quality and schedule their next donations.
2. To be able to view and update their personal information, including name,
contact address, and phone number, to keep their donor’s information record
up to date with the blood bank. (Solving P1)

• Administrator
1. To be able to create, update, delete, and query donor’s records in order to
manage donor information.
2. To be able to create, update, delete, and retrieve donation records to manage
information about donations made.
3. To be able to deposit donated blood into inventory when donations are
made.
4. To be able to withdraw blood from the inventory and keep a record of blood
stocks to always keep count of the blood bags.
5. To be able to create, update, delete, and retrieve request records from
hospitals to manage hospital requests for blood.
6. To be able to create, update, delete, and query hospital’s records in order to
manage hospital information.
7. To be able to send notifications to donors for their user account and blood
results through the system.
8. To be able to communicate for responding to hospitals for their blood
requests through the system.
• Hospital/Clinic
1.To be able to request the three components available in blood bank.
2.To be able to receive the major updates and camps details.
3.To be able to go through information of availability of blood.

3. References
www.google.com
www.w3schools.com
www.learnpython.org

0120044 DRASHTI SHUKLA


7 SAVE RED
0120025 PRACHI RATHOD

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy