Maharashtra State Board of Technical Education

Micro Project report on

Online Blood Bank Management System

Academic Year: 2023-24 Institute Code: 0563

Program: INFORMATION TECHNOLOGY Semester:IV

Course: SOFTWARE ENGINEERING Course Code: 22413

Group no: 02
 Maharashtra State Board of Technical Education
CERTIFICATE

Enrollment
Roll No Student Name Seat no
No

2205630190
04 SADULKAR MASERA SAMEER

05 MONDAL DISHA SHYAMAL 2205630191

2205630192
06 SATISH ABHISHEK SATISH

This is to certify that, of Fourth Semester of Diploma in Information Technology of

Institute Pravin Patil College of Diploma Engineering and Technology,
Bhayander(E) (Code: 0563) has completed the Micro Project satisfactorily in subject
Software Engineering(2241) for the academic year 2023-24 as prescribed in the
curriculum.

Place: Bhayander (E)

Date:

MR. NILESH VISPUTE MR. NILESH VISPUTE MRS.R.B. PATIL

SUBJECT TEACHER HEAD OF DEPARTMENT PRINCIPAL
 PART A – PLAN MICRO PROJECT PROPOSAL
Online Blood Bank Management System

1.0 Brief Introduction:

At the present there is no software to keep any records in blood bank. It becomes difficult to provide any
record immediately at times of emergency. Required more human efforts in maintaining the branch related
information. Manually to keep the accounts is also tedious & risky job & to maintain those accounts in ledgers
for a long period is also very difficult. Difficult to manage and maintain the files. Chance of damage of files,
if the data is stored in the files for duration of time. Privacy is difficult, Time consuming is retrieving, storing
and updating the data. It is difficult to keep track the record about the donor & receiver he has donated or
received the blood at the last time.
The proposed system (Blood Bank Management System) is designed to help the Blood Bank administrator
to meet the demand of Blood by sending and/or serving the request for Blood as and when required. The
proposed system gives the procedural approach of how to bridge the gap between Recipient, Donor, and Blood
Banks. This Application will provide a common ground for all the three parties (i.e. Recipient, Donor, and
Blood Banks) and will ensure the fulfillment of demand for Blood requested by Recipient and/or Blood Bank.
The features of proposed system are ease of data entry, system should provide user friendly interfaces, no
need to maintain any manual register and form , immediate data retrieval and so on

2.0 Aim of the micro-project

1. Reduce admin work by integrating the details of the person of all

categories into a single database.
2. Manual work for information retrieval on attendance becomes less as work becomes
digitized.
3. It is also time saving because manual work is less.
4. There is less chance of error.
4.0 Action Plan
Sr. Detail of activity Planned Planed Name of
No start date finish date Responsibly
team member
member
1 Discussion and
finalization of ALL
topic
2 Preparation and ALL
submission of
abstract
3 Collection of Data ALL
&Literature
Review
4 Discussion on ALL
Outline of content and
formulating of content
5 Editing and proof ALL
Reading of
Content
6 Compilation of ALL
report and
presentation
7 Viva ALL

8 Final submission ALL

of Micro Project

5.0 Resources Required

Sr. Name of Specifications Qty Remarks
No Resource/Material
1 Open Learning Videos/Websites/ 1 For information
Sources Magazines, Books.
Internet
2 Charts survey Related 1 For report
information purpose
PART A – PLAN MICRO PROJECT PROPOSAL
Online Blood Bank Management System

1.0 Brief Introduction

Blood donation is a life-

saving process that
can help save the lives of
people in need.
Blood banks play a crucial
role in
maintaining a steady supply
of blood for
transfusions. The blood
bank management
system is a web-based
application that
manages the process of blood
donation from
registration to distribution.
The blood bank
Blood donation is a life-
saving process that
can help save the lives of
people in need.
Blood banks play a crucial
role in
maintaining a steady supply
of blood for
transfusions. The blood
bank management
system is a web-based
application that
manages the process of blood
donation from
registration to distribution.
The blood bank
Blood donation is a life-
saving process that
can help save the lives of
people in need.
Blood banks play a crucial
role in
maintaining a steady supply
of blood for
transfusions. The blood
bank management
system is a web-based
application that
manages the process of blood
donation from
registration to distribution.
The blood bank
Blood donation is a life-
saving process that
can help save the lives of
people in need.
Blood banks play a crucial
role in
maintaining a steady supply
of blood for
transfusions. The blood
bank management
system is a web-based
application that
manages the process of blood
donation from
registration to distribution.
The blood bank
Blood donation is a life-
saving process that
can help save the lives of
people in need.
Blood banks play a crucial
role in
maintaining a steady supply
of blood for
transfusions. The blood
bank management
system is a web-based
application that
manages the process of blood
donation from
registration to distribution.
The blood bank
India suffers from an annual deficit of two million units, as only 1% of the Indian population donates blood as
stated by the World Health Organization (WHO). Due to substandard medical facilities and practices in many
parts of the country, there have been cases of transmission of infectious diseases like AIDS. The need for blood is
increasing along with its importance for treating various medical conditions. There are three main components of
blood; plasma, platelet, and RBC/WBC. Especially during this covid pandemic, we’re seeing a huge spike in the
requirement of blood plasma from the patients who were recovered from covid-19 as their Convalescent Plasma
now contains covid-19 antibodies It becomes difficult to provide any record immediately at times of emergency.
Required more human efforts in maintaining the branch related .
Manually to keep the accounts is also tedious & risky job & to maintain those accounts in ledgers
for a long period is also very difficult. Difficult to manage and maintain the files. Chance of damage of files,
if the data is stored in the files for duration of time. Privacy is difficult, Time consuming is retrieving, storing
and updating the data. It is difficult to keep track the record about the donor & receiver he has donated or
received the blood at the last time.
The proposed system (Blood Bank Management System) is designed to help the Blood Bank administrator
to meet the demand of Blood by sending and/or serving the request for Blood as and when required. The
proposed system gives the procedural approach of how to bridge the gap between Recipient, Donor, and Blood
Banks. This Application will provide a common ground for all the three parties (i.e. Recipient, Donor, and
Blood Banks) and will ensure the fulfillment of demand for Blood requested by Recipient and/or Blood Bank.
The features of proposed system are ease of data entry, system should provide user friendly interfaces, no
need to maintain any manual register and form , immediate data retrieval.

2.0 Aim of Micro Project

a. Reduce admin work by integrating the details of the persons of all
categories into a single database.
b. Manual work for information retrieval on attendance becomes less as work becomes
digitized.
c. It is also time saving because manual work is less.
d. There is less chance of error
e.
3.0 Course outcomes integrated:
a. Understanding of Requirements Analysis:
b. Choose relevant data model to solve a problem
c. System Design Skills.
d. Preparing scheduling.
.
4.0 Actual resources used:

Sr. No Name of Resource/Material Specifications Qty Remarks

1 MS ACCESS 2007 1 For Developing Database

2 MS WORD 2016 1 For Documentation

3 Paint - 1 For Output Images

5.0 Skill Developed/Learning Out Of This Micro-Project:

1. Basic knowledge
2. Experiments and practice..
3. Individual team work
4. Engineering tools.
5. Lifelong learning
6.0Content of our micro-project :

1.0 Problem Definition

the 'ONLINE BLOOD BANK MANAGEMENT SYSTEM' project is to interconnect all the
blood banks, hospitals, donors into a single network, validation, store various data and
information of blood of each individual.

2.0 Requirement Gathering

The requirement gathering process for 'ONLINE BLOOD BANK MANAGEMENT SYSTEM'
system involves systematically identifying, documenting, and analyzing the needs and
expectations of various donor. Here is a step-by-step guide for gathering requirements for
online blood bank management system:

1. Define project scope : providing safe and quality blood.

2. Document Personas: Create user personas for each type of user.

3. Determine Core Functionalities: Identify key features like history tracking, and donation
date.

4. Specify Authentication: Define authentication methods (biometrics, PINs, etc.).

5. Consider Compatibility: Determine platform (iOS, Android) and device compatibility.

6. Address Connectivity: Identify customer requirements and consider offline functionality.

7. Establish Security Measures:Define encryption standards and privacy measures.

8. Design Usability: Ensure a user-friendly interface with accessibility features.

9. Integrate with Existing Systems: Identify systems for integration and define data exchange
protocols.
 10. Ensure Regulatory Compliance: Comply with data protection regulations and address
legal/ethical considerations.

11. Plan for Support and Maintenance: Establish support mechanisms and maintenance
processes.

12. Consider Budgetary Constraints: Define the budget and total cost.

13. Collect Feedback: Implement mechanisms for user feedback.

14. Document Requirements: Compile requirements into a clear document with priorities.

3.0 Selection Of Process Model

Selecting an appropriate process model for the development of a online blood bank management
system depends on factors such as project size, complexity, requirements volatility, and the
level of understanding of the system.

Waterfall Model

While the Waterfall model is known for its linear and sequential approach, it may not be the most
flexible choice for mobile attendance systems, which often involve evolving requirements and
user feedback. However, if the project constraints and requirements are well-defined from the
outset, and changes are expected to be minimal, a Waterfall model can be adapted.

4.0 Design Model

 Use Case Diagram Class & Object

Sequance Diagram

Data
Flow Diagram
ACTIVITY

5.0 Software Requirement Specification

1. Introduction

1.1 Purpose
The purpose of this document is to provide a comprehensive overview of the requirements for
the development of a Online blood bank management System. This system aims to
interconnect all the blood banks, hospitals, donors into a single network, validation, store
various data and information of blood and health of each individual.

1.2 Scope
The Blood Bank Management System (BBMS) is an application that stores, processes,
retrieves, and analyses data about blood bank administration.

1.3 Document Conventions

Bold Text: Represents section headings.
Italic Text: Represents placeholder text or user inputs.
Code font: Represents code snippets or technical terms.
2. Overall Description
2.1 Product Perspective
The Online blood bank management system will be a standalone web application with a
client-server architecture.

2.2 Product Features

User Authentication: Secure login using credentials (username/password) or biometric.
Attendance Tracking: Real-time recording of donors donating blood and assign next
donation date.

2.3 User Classes and Characteristics

Admins: Manage system settings, users, and generate reports..

3.Non-Functional Requirements
3.1Performance
Support 5000+ concurrent
users. Response time < 3
seconds.

3.2Security
Secure credentials, HTTPS, role-based access

3.3Usability
Intuitive mobile-friendly interface.

6.0 RMMM PLAN

This plan outlines the approach to mitigate, monitor, and manage potential risks associated with
developing a online blood bank management system.

Risk Mitigation:

 Technical Risks Mitigation:

Perform thorough testing on different devices and network conditions .
Regularly update the mobile app to address security concerns.
  Operational Risks Mitigation:
Conduct awareness sessions to promote user acceptance.
Develop comprehensive training materials and sessions.

Risk Monitoring:

 Regular System Audits:

Conduct periodic security audits to identify and address vulnerabilities.
Monitor app performance and address any issues promptly.
 User Feedback:
Establish a feedback mechanism for users to report issues.
Act on user feedback to enhance system usability and address concerns.

Risk Management:

 Contingency Plans:
Develop contingency plans for potential system failures.
Establish a rapid response team to address critical issues.

 Regular Updates:
Regularly update the system to incorporate new security measures.
Keep users informed about updates and system improvements

7.0 Cost Estimation Using COCOMO

COCOMO (Constructive Cost Model) can be used to estimate the effort (person-
months) required to develop the mobile attendance system. To estimate the cost of a project
like a mobile attendance system using the COCOMO (Constructive Cost Model), we need to
consider various factors such as the size of the project, the development mode, and the
complexity of the system.

Project was estimated to be 1.2 KLOC. Calculate effort & time.

Also we know that ,
Effort = a(KLOC)^b
Time = c(E)^d
Person = E/T
  Organic:
 Effort = 2.4(1.2)^1.05 =3.314 person
 Time = 2.5(2.214)^0.38 = 3 months
 Person = 3.314 /3 = 3 person

8.0 prepare schedule using scheduling technique/ Timeline Chart

Creating a schedule for a blood bank Management System involves identifying tasks,
dependencies, and allocating resources efficiently.

1. Project Initiation (Week 1-2):

Define project scope and objectives.
Identify keys.

2. Requirements Gathering (Week 3-4):

Collect and document system requirements.
Conduct user feedback sessions.
Review existing systems for integration needs.

3. System Design (Week 5-8):

Architectural design of the blood bank management
system.
User interface design.
Database design and schema development.

4. Development (Week 9-16):

Mobile app development.
Backend system development.
Integration of mobile and backend components.

5. Testing (Week 17-20):

Unit testing for mobile app and backend components.
Integration testing for the entire system.
User acceptance testing.

6. Deployment (Week 21-22):

Prepare for system deployment.
Implement the mobile management system.
Conduct final testing in the production
environment.
 7. Training (Week 23-24):
Develop training materials.
Conduct training sessions for end-users.

8. Maintenance and Support (Week 25 onwards):

Establish a maintenance plan.
Address post-deployment issues and feedback.

Chart :
Creating a timeline chart for tracking the process of developing a blood bank management project on
Medium would typically involve writing an article or blog post with a visual representation of the
timeline. Here's a brief outline of how you could structure such an article

TASK JAN FEB MARCH

Planning

Requirement
Gathering

Design

Coding

Testing

Deploymen
t

WEEKS 1 2 3 4 5 6 7 8 9 10 1 12
1
9.0 Conclusion:
The Blood bank management system (BBMS) developed consists of an Android smart
phone, technology, Wi-Fi access point and a server. The function of the entire
system is very simple.
The system is a possible option for replacing the current methods. From the
implementation, the system has successfully tested in real situation outside the
building.

10.0 References:
https://5.imimg.com/data5/SELLER/Doc/2020/9/UL/AB/AW/2678632/blood
-bank-management-software.pdf
https://nevonprojects.com/online-blood-bank-project/
 Teacher Evaluation Sheet

Name of Student: Sadulkar Maseera Sameer Enrollment: 2205630190 Roll No: 02

Name of Program:- Information Technology Semester: IV

Course Title: Software Engineering Code: 22413

Tile of the project: Mobile Management System
*Course Outcomes Achieved:
a. Understanding of Requirements Analysis.
b. Choose relevant data model to solve a problem.
c. System Design Skills.
d. Prepare scheduling.
Evaluation as per Suggested Rubric for Assessment of Micro-Project
Sr. Poor (1-3)Average Good Excellent Sub
Characteristics to be assessed
No (4-5) (6-8) (9-10) Total
(A) Process and Product Assessment (Convert above total marks out of 6 Marks)

1 Relevance to the course

Literature Review / Information
2
Collection
Completion of the Target as per
3
project proposal
4 Analysis of Data and representation
5 Quality of Prototype / Model
6 Report Presentation
(B) Individual Presentation / Viva (Convert above total marks out of 4 Marks)

7 Presentation
8 Viva

(A) Process and Product Assessment (B) Individual Presentation / Viva

Total Marks (10)
(6 Marks) (4 Marks)

Comments / Suggestions about team work / leadership / inter-personal communication (If any):

Name & Designation of the Faculty Member: Mr. Nilesh Vispute

Dated signature:-------------------------_
 Teacher Evaluation Sheet

Name of Student: Mondal Disha Shyamal Enrollment: 2205630191 Roll No: 05

Name of Program :- Information Technology Semester: IV

Course Title: Software Engineering Code: 22413

Tile of the project: Mobile Management System

*Course Outcomes Achieved:

a. Understanding of Requirements Analysis.
b. Choose relevant data model to solve a problem.
c. System Design Skills.
d. Prepare scheduling.

Evaluation as per Suggested Rubric for Assessment of Micro-Project

Sr. Poor (1-3) Average Good Excellent Sub
Characteristics to be assessed
No (4-5) (6-8) (9-10) Total
(A) Process and Product Assessment (Convert above total marks out of 6 Marks)

1 Relevance to the course

Literature Review / Information
2
Collection
Completion of the Target as
3
per project proposal
Analysis of Data and representation
4
5 Quality of Prototype / Model
6 Report Presentation
(B) Individual Presentation / Viva (Convert above total marks out of 4 Marks)

7 Presentation
8 Viva

(A) Process and Product Assessment (B) Individual Presentation / Viva

Total Marks (10)
(6 Marks) (4 Marks)

Comments / Suggestions about team work / leadership / inter-personal communication (If any):

Name & Designation of the Faculty Member: Mr. Nilesh vispute

Dated signature:-------------------------_
 Teacher Evaluation Sheet

Name of Student: Mishara Abhishek Satish Enrollment: 2205630192 Roll No: 06

Name of Program :- Information Technology Semester: IV

Course Title: Software Engineering Code: 22413

Tile of the project: Mobile Management System

*Course Outcomes Achieved:

a. Understanding of Requirements Analysis.
b. Choose relevant data model to solve a problem.
c. System Design Skills.
d. Prepare scheduling.

Evaluation as per Suggested Rubric for Assessment of Micro-Project

Sr. Poor (1-3) Average Good Excellent Sub
Characteristics to be assessed
No (4-5) (6-8) (9-10) Total
(A) Process and Product Assessment (Convert above total marks out of 6 Marks)

1 Relevance to the course

Literature Review / Information
2
Collection
Completion of the Target as per
3
project proposal
Analysis of Data and representation
4
5 Quality of Prototype / Model
6 Report Presentation
(B) Individual Presentation / Viva (Convert above total marks out of 4 Marks)

7 Presentation
8 Viva

(A) Process and Product Assessment (B) Individual Presentation / Viva

Total Marks (10)
(6 Marks) (4 Marks)

Comments / Suggestions about team work / leadership / inter-personal communication (If any):

Name & Designation of the Faculty Member: Mr. Nilesh vispute

Dated signature: