Professional Documents
Culture Documents
Ste Microproject
Ste Microproject
MICRO PROJECT
Name: Ritu Rajendra Kamble, Nilakshi Naresh Kudu, Jagruti Mahesh Chavan
Certificate
This is to certify that Mr. /Ms. Ritu Rajendra Kamble, Nilakshi Naresh
Kudu, Jagruti Mahesh Chavan of FIFTH Semester of Diploma in
Computer Engineering.
SEAL OF
INSTITUTE
Part A: Micro Project Proposal
Rationale: The project's purpose is to develop and execute a set of test cases for
the Blood Bank Management System. This is essential to ensure the system's
reliability, functionality, and adherence to regulatory standards, ultimately
enhancing patient safety and the efficiency of blood bank operations.
Course Outcomes Integrated:
2. Literature
Survey/Information
Collection
3. Project Proposal
6. Quality of Prototype/Model
7. Report Preparation
8. Presentation
9. Viva
6
Micro-Project Evaluation Sheet
Title: BLOOD BANK MANAGEMENT SYSTEM
Institute Code: 0093 Academic year:2023
Program: Computer Engineering Course & Code: STE (22518)
Name of Candidate: Roll No:
Semester: Fifth Name of Faculty: Mrs. Seema Kaimal
7 Presentation .
8 Viva
7
WEEKLY ACTIVITY SHEET
Title: BLOOD BANK MANAGEMENT SYSTEM
Institute Code: 0093 Academic year: 2022
Program: Computer Engineering Course & Code: STE (22518)
Name of Candidate: Roll No:
Semester: Fifth Name of Faculty: Mrs. Seema Kaimal
SR.
WEEK ACTIVITY PERFORMED
NO
8
Index
Sr. No. Content Page no.
1. Introduction 10
5. Conclusion 20
6. References 20
9
Introduction to Blood Bank Management System
A Blood Bank Management System is a sophisticated software solution
designed to streamline the core processes of blood banks and transfusion
centers. It serves as a critical tool in managing the lifecycle of blood units,
from donor registration to blood collection, testing, inventory
management, and distribution. This system plays a pivotal role in
ensuring the availability of safe and compatible blood products,
optimizing the use of resources, and maintaining high standards of
patient safety and care. By centralizing and automating these operations,
a Blood Bank Management System not only improves efficiency but also
contributes significantly to the well-being of patients in need of blood
transfusions.
Blood Bank Management Systems are engineered to orchestrate the
entire journey of blood - from the altruistic act of donation to the critical
moment of transfusion. These systems offer a systematic approach to
donor registration, blood collection, rigorous testing, secure inventory
management, and the expeditious processing of blood requests from
healthcare facilities. Moreover, the system emphasizes stringent security
measures and regulatory compliance to protect sensitive patient data and
ensure the integrity of the blood supply.
By amalgamating technology, adherence to best practices, and a
commitment to patient well-being, Blood Bank Management Systems
represent an indispensable resource in the modern healthcare landscape.
These systems not only improve operational efficiency but also play a
pivotal role in saving lives by guaranteeing the availability of safe and
compatible blood products whenever and wherever they are needed.
10
Blood Bank Management System Test Plan
1. Introduction
1.1 Purpose
The purpose of this test plan is to define the testing approach, objectives,
and strategy for the Blood Bank Management System to ensure it meets
quality standards, security requirements, and functionality expectations.
1.2 Scope
This test plan covers testing for the key modules of the Blood Bank
Management System, including Donor Management, Inventory
Management, Blood Request Processing, User Authentication, Access
Control, Reporting, and Analytics.
1.3 Objectives
The main objectives of this testing effort are to:
Verify the functionality of the Blood Bank Management System.
Ensure data accuracy and integrity.
Validate the system's performance, security, and scalability.
Confirm compliance with relevant regulatory standards (e.g., HIPAA).
2.1 Testing Approach
The testing approach will include a combination of manual and
automated testing to cover functional, non-functional, and security
aspects. Testers will follow a risk-based approach, prioritizing testing
based on the criticality of modules and features.
2.2 Test Levels
Unit Testing: For individual modules and components.
Integration Testing: To verify interactions between modules.
System Testing: To validate the system as a whole.
User Acceptance Testing (UAT): Conducted by end-users.
11
2.3 Test Types
Functional Testing
Non-functional Testing (Performance, Security)
Regression Testing
User Acceptance Testing
Security Testing
2.4 Test Environment
Hardware: Specify the hardware requirements.
Software: List the software components required for testing.
Test Data: Define the data required for testing and any tools used for data
generation.
3. Test Scenarios
Define test scenarios for key functionalities:
3.1 Donor Management
Verify donor registration and record management.
Test donor eligibility checks.
3.2 Inventory Management
Validate blood inventory updates and tracking.
Test blood storage conditions and expiry checks.
3.3 Blood Request Processing
Verify blood request submission and approval.
Test emergency blood requests.
3.4 User Authentication and Access Control
Test user authentication and authorization.
Verify access control to sensitive data.
3.5 Reporting and Analytics
12
Validate reporting and analytics features.
Verify report generation and data accuracy.
4. Test Case Design
4.1 Test Case Identification
Create test cases for each test scenario, specifying input data, expected
outcomes, and pass/fail criteria.
4.2 Test Data Setup
Define procedures for setting up test data, including creating sample
donor records and blood inventory.
4.3 Test Execution Steps
Outline the steps to execute each test case, including prerequisites.
4.4 Expected Results
Specify the expected results for each test case.
5. Test Execution
5.1 Test Schedule
Create a testing schedule, including milestones and deadlines.
5.2 Test Environment Setup
Detail the steps for setting up the test environment.
5.3 Test Case Execution
Define the procedure for executing test cases, including any tools or
scripts used.
5.4 Defect Reporting
Explain the process for reporting defects, including severity and priority
assignment.
6. Defect Management
6.1 Defect Reporting
13
Detail how defects should be reported, including templates and required
information.
6.2 Defect Prioritization
Explain the criteria for prioritizing defects based on severity and impact.
6.3 Defect Resolution
Outline the procedure for defect resolution, retesting, and verification.
14
Test Cases for Blood Bank Management
System
15
2. Test case for login Page
TC2 Validate the 1. Enter an invalid N/A User should User will not Pass
required username not log in and log in and
fields by not 2. Enter the correct should show will show
filling in any password proper error proper error
data. 3. Click on Login message message
Button
TC3 Validate the 1. Enter a valid N/A User should User will not Pass
required username not log in and log in and
fields by 2. Enter an incorrect should show will show
filling password proper error proper error
correct 3. Click on Login message message
username Button
and invalid
password
TC4 Check when 1. Enter a valid N/A User should User is Pass
pass correct username log in logged in
email and 2. Enter a valid
password password
3. Click on Login
Button
16
3. Test the search, donate and request option
17
Images of System
18
19
Conclusion:
In conclusion, the development and execution of these test cases
underline the paramount importance of the Blood Bank Management
System in the healthcare landscape. As a guardian of human lives, this
system is not just a technological marvel but a beacon of hope for
patients and a testament to the tireless dedication of healthcare
professionals and blood donors. Our testing efforts serve as a crucial
step in upholding this commitment to quality care, reinforcing the
system's role as a lifeline in the healthcare ecosystem.
References:
https://chat.openai.com/
https://www.emizentech.com/
https://www.geeksforgeeks.org/test-cases-for-registration-and-login-
page/
20