Department Of

Computer Science

A Project Report
On

Submitted To
Savitribai Phule Pune University in Partial Fulfillment of
Degree of BSC (Computer Science) for the Academic Year
2024-25

Submitted By
Ms. Ghodechor Prachi Navnath
(Roll No: Exam Seat No: )

Project Guide : Jawale M.V. Sir

1
 JIJAMATA COLLEGE OF SCIENCE AND ARTS,
Dnyaneshwar Nagar, Bhende
Tal-Newasa Dist.-Ahmednagar PIN-414605
-------------------------------------------------------------
Roll No- 08 Exam Seat No-

CERTIFICATE
DEPARTMENT OF Computer
This is to certify that Ms.Ghodechor Prachi Navnath has
satisfactorily carried out the required Project work, prescribed by
the Savitribai Phule University of Pune for the TYBCS(Computer
science) course in Computer Project and this file represents her
bonafide work in the year 2024-2025

IN Charge
H.O.D
Prof.Jawale.M.V. Sir
Prof.Jawale.M.V. Sir

Internal Examiner
External Examiner

2
Prof M.V INDEX
Sr.no Title Remark

1 Introduction
2 Acknowledgement
3 Project profile
4 Existing system
5 Limitation of existing system
6 Analysis
7 Hardware and software
Requirement
8 Designs(Diagram)
9 Data Dictionary
10 Testing
11 Project Screenshot
12 Conclusion
13 Bibliography

3
 INTRODUCTION
Blood Bank, with some little changes in the medical
terms, database etc.
Still to encourage such Blood banks to use computers for
generating useful information to run the organization
efficiently, we provide the following Software from which
one can choose according to their requirement. It is a
system which will help Doctor to keep track of Blood
Bank, from time to time. The data regarding the patient
blood information will help the patient in order to be used
for the future. By implementing a robust Blood Bank
Management System, organizations can significantly
enhance their operations, improve patient care, and save
lives.
Blood Bank Management System aims to improve
efficiency, accuracy, and transparency in managing blood
donations, inventory, and distribution.

Acknowledgement

4
 We take an opportunity to present this work entitled
as
“BLOOD BANK MANAGEMENT SYSTEM”
This work would not be possible without the valuable
support & encouragement froms those who helped
turning out this project into a success.

1. We must express our sincere thanks to Prof. Jawale

M.V. our project guide, whose ideas &knowledge
helped our project to go in a fluent manner.
2. We must also express our regards to the entire staff
of the computer science department of Jijamata
college bhende
- Prof.Jawale sir

Project Profile
Project Title: Blood Bank Management System
Objective: The main purpose of the Blood Bank
Management System is to manage details about
blood donation, blood donor, blood receiver, blood
availability, and give dyanamic result of blood
donation ,received stock everyday.
Internal Guide: Prof. Jawale M.V.

5
Submitted to: Department of Computer Science,
Jijamata College of Science And Art’s Bhende , pune
University.
Developed By: Deshmukh Vaishnavi Pandit

EXISTING SYSTEM
Existing system refers to the system
that is being followed till now. Presently
all the clinics functionalities are done
manually. That is if a patient want to
consult a doctor he can visit their till his
chance called. This is make the person
very difficult. An Appointment are
distributed directly. The main
disadvantage is time consuming.
Limitation of existing system is if sum
one patient loses his receipt, difficulties
to find out patient has assign tickets. To

6
defect this limitation we do computer
system.
The current system works as the
following:
 In the old system, the user was
maintaining the records like number
of books, CD’s, DVD’s and
subscribers. Fees Detail and bill
(Receipt) in the paper sheets.
 Hence it was very difficult for him to
keep track which Customer has been
taken which cd or did, what is the Bill
no, etc.
 The manpower required for this kind
of transaction and maintenance of
data is higher than the actual
requirement.

LIMITATIONS OF EXISTING SYSTEM

No system can be referred as complete system in all aspec

ts. In spite ofsuccessful executions of testing plan .The
problem arises, when the system is input in the real
working environment, the problem that will arise cannot
7
be visualized and their solution cannot be predetermined
to be rectified.

 the designed product is standalone system.

 it works on current basis.

 On-line booking, transaction etc. are not possible.

 Lack of security of data.

 Time consuming.

 Consumes large volume of paper work.

 Manual work

 No direct role for the higher officials.

 to avoid all these limitations and make the system working

more accurately it needs to be computerized.

ANALYSIS
It is necessary to analyze the needs and availability before
designing any application. This analysis includes study of the
existing system and the availability of the resources. The study

8
is conducted on each and every aspect which is necessary to
design any enterprise solution
METHODOLOGY ADOPTED:-
PROCESS MODEL:
In the development of software we have used Waterfall Model,
the linear sequential mode. This model encompasses the
following activities:
a) Analysis Phase:
This refers to the gathering of requirements, with the goal of
determining how these requirements will be accommodated in
the system.
b) System Design Phase:
This is actually a multistep process. In this we tried to focus on
some distinct attributes of a program like data structure,
software architecture, interface representations and
algorithmic detail. In this we tried to translate requirement into
representation of the software which can be assessed for
quality before coding begins. In the verifications, I have tried to
ensure that the design is satisfying the
Requirements and is of good quality. I have tried to find out if
there is any misinterpretation of specified any requirements.
c) Code Generation Phase:

9
In this phase, we translated design of a system into code which
can be compiled and executed. In this phase we have done
actual coding for all forms. In this we tried to produce simple
program which are clear to understanding and modify We have
used dynamic method to verify the code. We have executed
program on some test data and output of the program
examined to determine if there are any error present. I have
read the code carefully to detect any discrepancies between
the design specification and the actual implementation.
d) Testing:
Testing plays a critical role in quality assurance for software.
Due to limitations of the verification methods for the previous
phase, design and requirement faults also appear in the code.
Testing is used to detect these errors, in addition to the errors
introduced during the coding phase.

Hardware and software requirements

In the proposed system we have used:

HARDWARE
10
 Processor Any Generation

RAM Min 2 GB

Hard Disk Min 32GB

Monitor VGA/SVGA

SOFTWARE

11
 Front-end HTML,CSS,BOOTSTRAP

Back-end Php

o.s Windows X

FEASIBILITY STUDY
A feasibility study is conducted to select the
best system. That meets performance
requirement. A system required performance is
defined by a statement of constraints the
identification of specific system objectives &
adscription of outputs. All projects are feasible-
given unlimited time.
12
  All projects are feasible-given unlimited time.
 Feasibility and risks analysis are related in
many ways, if project risk is great the
Feasibility of providing quality software is
reduced.

ECONOMICAL ANALYSIS:-

A system is expected to provide benefits.

Identification of each benefit and assignment
of monetary value to it is required for cost
benefit analysis. Benefits can be tangible and
intangible, direct or indirect. As assessment of
the economic justification for a computer
based system project is cost benefit. Cost
benefit analysis is complicated by criteria that
vary with the characteristics of the system to
be developed, the relative size of the project
and the respected return on investment
derived as part of the strategic plan.
TECHNICAL ANALYSIS:-
During the technical analysis the analyst
evaluates the technical merits of the system
concept, at the same time collecting additional
information about performance, reliability and
maintainability. In some cases, this step also
includes the limited amount of research and

13
design. Technical analysis begins with an
assessment of the technical ability of the proposed
system.
 Technically this project is very sophisticated
and has faster execution comparatively used in
project.
 During the technical analysis the analyst
evaluates the technical merits of the system
concept, at the same time collecting additional
information about performance, reliability and
maintainability. In some cases, this step also
includes the limited amount of research and
design.
 Technical analysis begins with an assessment
of the technical ability of the proposed system.
 The tools available for technical analysis are
derived from mathematical modelling,
probability and statistic, queering theory and
control theory.

DESIGNS
14
  USE CASE DIAGRAM

ACTIVITY DIAGRAM

15
DATA FLOW DIAGRAM

16
Class Diagram

17
ENTITY RELATIONSHIP DIAGRAM

18
DATA DICTIONARY
19
1] Table Name : table_Patient
Field Type DESCRIPTION
Patient_id Varchar( 50) Patient Id
Patient_Name Varchar( 50) Patient NAME
Patient_Age Varchar( 50) Patient age
Patient_Gender Varchar( 50) Patient gender
Patient_Address Varchar(MAX) Patient Address
Patient_Contact Varchar( 50) Patient contact
Patient_Bloodgroup Varchar( 50) Paitent blood group
Patient_Dob Smalldatetime Patient dateof birth
Patient_Healthproblem Varchar(Max) Health problem
2) Table Name: table_doctor
Filed Type Decription
Doctor_id Varchar( 50) Doctor Id
Doctor_Name Varchar( 50) Doctor name
Doctor_age Varchar( 50) Doctor age
Doctor_Gender Varchar( 50) Doctor gender
Doctor_Adress Varchar(Max) DOCTOR address
Doctor_Contact Varchar( 50) Doctor contact
Doctor_Bloodgroup Varchar( 50) Doctor bloodgroup
Doctor_Dob Smalldatetime Date of birth

3) Table Name: Table_bill

Field Type Description
20
Bill-ID Varchar(50) Bill id
Doctor-id Varchar(50) Doctor id
Doctor_Name Varchar(50) Docter name
Bill_date Smalldatetime Date
Patient_id Varchar(50) Patient id
Patient_name Varchar(50) Patient name
Bill_total Varchar(50) Total amount

4) Table Name:table_billdetails
filed Type Description
Bill_id Varchar(50) Bill id
Bill_service Varchar(50) Service name
Bill_Amount Varchar(50) Amount

5) Table name:table_services
Filed Type Description
Services_id Varchar(50) Services id
Services_name Varchar(50) Services name
Services_amount Varchar(50) Anount to be changed

6) Table Name:table_Appointment

21
 Filed Type Description
Appointment_id Varchar(50) Appointment id

Patient_id Varchar(50) Patient id

Patient_name Varchar(50) Patient name

Appointment_date smalldatetime Date of

appointment
Appontment_time Varchar(50) Time of
appointment
Appointment_service Varchar(50) Services name
s
Appointment_Doctor Varchar(50) Doctor name

TESTING
22
TESTING:-
Testing is the most vital phase in completing a project. Testing mainly
aims at checking the modularity, data flow and code thereby
scrutinizing the intricacies of the system being developed. A through
testing has been carried out for this website. At all the required places
appropriate validation has been done. User involvement at every stage
has been propounded in the system. Testing is the crucial part of the
system development to assure quality of the services, design and
coding.
TESTING OBJECTIVES:
Testing objective is the guideline that helps in carrying out proper
testing of the system. The guidelines stated below are followed to carry
out proper testing on the system. Testing is the process of executing a
program with a goal to uncover the errors within the system. A
successful test needs to be carried out in order to find undetected
errors. The main objective is to design the tests that systematically
uncover different types of errors with minimum amount of time and
errors. Testing demonstrates that the system functions appear to be
working in a proper manner and that the performance requirements
are met.

FORMAL TECHNICAL REVIEW:

A formal technical review is a form of a peer review in which a team of
qualified personnel examines the suitability of the software product for
its intended use and identifies discrepancies from specifications and
standards. The purpose of technical reviews is to arrive at a technically
superior version of the product reviewed, by correction of defects.

23
There are various responsibilities assigned to the team members
regarding the project.
 User participation is important for performing administrative tasks
relative to the review, ensuring orderly conduct and ensuring that
the reviews meet its objectives.
 One of the team members documents anomalies, action items,
decisions and recommendations made by the review team.
 Technical experts are the active participants in the review and
evaluation of the software product.

TEST PLAN:-
Test plan provides a road map for instituting software testing. This
describes the overall testing strategy and the project management
issues that are required to properly execute effective tests. Testing
plan contains various test phases, start and end dates for each
phase is described. Testing is the process of analysing a software
item to detect the differences between existing and required
conditions and to evaluate the features of the software item.
Software Test Plan (STP) is designed to prescribe the scope,
approach, resource and schedule of all testing activities. The plan
must identify the items to be tested, the features to be tested, the
types of testing to be performed, the personnel responsibilities for
testing, the resources and schedule required to complete testing,
and the risks associated with the test plan.

TESTING METHODOLOGY:-
Black box testing:

24
 The first type of testing was at user level where all the applications
were tested for the users.
White Box Testing:
The second level of testing was at functional level where each
module of all the applications was tested. This testing continued
throughout the entire project, evolving from component level (or
unit) testing to integration testing.
Unit Testing:
This testing focuses effort on the smallest part of software design-
the module or software component. After the code has been
developed, reviewed and verified for correspondence to
component level design, unit testing case design begins.
Integration Testing:
Unit testing ensures that all the modules are working fine
independently but now we have to test the system as awhile; we
have to develop a strategy, which sees that the system is
functioning properly as a whole system. Integration testing is
systematic testing for constructing the program structure while at the same time
conducting tests to uncover errors associated with interfacing. We will use bottom up
integration testing where we will integrate the modules by starting with the lower
individual modules and moving upward through the control hierarchy.
MODULES TO BE TESTED:
1) Login Module
2) Registration Module
1) Log-in module:

Test Test case Expected result Actual result

case no

1 Check for User will be User

valid authenticate authenticated
25
 username d successfully
and successfully
password.
Check for Alert invalid Alert invalid
2 invalid username username and
username and password is
and password will displayed
password. be displayed

2) Registration module
Test Test case Expected result Actual result
case
no
1 Check for User will be authenticated User
successfully authenticated
only successfully
character
2 Check for Alert invalid Alert invalid
username and
numeric username password is
password will be displayed

displayed

Screenshot

1) Home page:

26
2) Services

3) Gallery

27
4) Doctors

28
5) Registration form

6) Fill registration:
29
7) ADD value

8) Patient Report
30
CONCLUSION
31
 Dental Management System is a system which is
a first step to change the medical industry
methodology of keeping the data of patients as well
as the other important information. This system will
help the users to manage the dental information
and make sure that all the important data are able
to be use in the future time. This includes
information for the future treatment, as well as to
do research from the data that had been captured.
As this system will be used for the dental
management, the dental industry will soon be a
high standard industry, which all the process will be
done through the computer and specified system. I
actually learnt what exactly coding is when I did this
project in html , css ,bootstrap &php. It was
different from what you read in books. It was a
great learning process.

BIBLOGRAPHY
32
 Text-Book References: References:-
 Software Engineering , Fifth Edition by
Roger S. Pressman , Nirali Publication
 Web Technology Nirali Publication.

 Web references:
 www.w3schools.com
 www.google.co.in
 http://library.utem.edu.my/index2.php?
option=com_docman&task=doc_view&g
id=4098&Itemid=342

33
THANK YOU!

34