Minor Project Aman
Minor Project Aman
On
Bachelor of Computer
Applications
To
(HOD Signature)
Session
2022-23
Certificate
Certified that the Minor Project (507) submitted in partial fulfillment of the
requirements for the award of the degree of Bachelor of Computer Applications (BCA)
to Chaudhary Charan Singh University, Meerut by Aman Tripathy, Roll No
200992106011 has been completed under my
The matter embodied in this project work has not been submitted earlier for award of
any degree to the best of my knowledge and belief.
[Roll No.]
ACKNOWLEDGEMENT
With candor and pleasure I take opportunity to express my sincere thanks and obligation
to my esteemed guide __________________________________________________________________ It
is because of his/her able and mature guidance and co-operation without which it would
not have been possible for me to complete my project.
[Roll No.]
1. INTRODUCTION
The ONLINE BLOOD DONATION MANAGEMENT SYSTEM is great project. this project
is designed for successful completion of project on Online Blood Donation management
System. the basic building aim is to provide blood donation service to the city recently.
Online Blood Donation management System (BBMS) is a browser based system that is
designed to store, process, retrieve and analyze information concerned with the
administrative and inventory management within a blood bank. This project aims at
maintaining all the information pertaining to blood donors, different blood groups available
in each blood bank and help them manage in a better way. Aim is to provide transparency in
this field, make the process of obtaining blood from a blood bank hassle free and corruption
free and make the system of blood bank management effective.
The Blood bank system project report contain information related to blood like
•Blood type
•validity of Blood s
Bank blood donation system in java is planned to collect blood from many donators in
short from various sources and distribute that blood to needy people who require blood.
To do all this we require high quality software to manage those jobs. The government
spending lot of money to
develop high quality “Online Blood Donation management System project”. For do all
those kinds of need Online Blood Donation management System project in java contain
modules which are include the detail of following areas:
•Blood Donor
•Equipment’s
•Stick
•Blood Recipient
•Blood collection
•Camp
•Stock details
•blood bank system project Reports
•Blood issued
•Blood bank system project
1.2 Scope
The scope for this system is divided into four which are administrator, blood bank staff,
and donor.
1. Admin
• Manage Profile
• Manage Blood Bank .
• Add/View Camp
• Add/View User
• View Requirements
2. Blood Donor.
• Manage registration and profile.
• View blood donation record
• View Information about blood donation
1.3 Objective
There are the objectives in this project to be achieve to make this project successfully
complete:
• To design an application for publicize and advertise the advantage of blood donation to
encourage people to donate blood.
• To develop an application that can manage blood bank using mobile phone and
records blood donation as the alternative to replace the traditional way of
recording Red Book Certificate.
• To test the functionality of the developed application to meet the user requirement.
Software Development Life Cycle (SDLC) methodologies are a set of frameworks that
are used to guide the development of software products. The following are the commonly
used SDLC methodologies:
Waterfall Methodology: This is a linear, sequential approach where each stage of the
software development process must be completed before moving onto the next.
Requirements are defined at the start of the project and then development, testing,
deployment, and maintenance are completed sequentially.
Agile Methodology: This is an iterative, incremental approach where the development
process is broken down into smaller stages or sprints. Agile methodology emphasizes
collaboration, flexibility, and adaptability, and involves frequent testing and feedback
cycles.
Scrum Methodology: This is a subset of Agile methodology that emphasizes teamwork,
accountability, and iterative progress. The Scrum process involves a set of roles, events,
and artifacts that help guide the development process.
Lean Methodology: This is a process improvement approach that emphasizes reducing
waste and increasing efficiency. Lean methodology involves identifying value streams,
mapping processes, and continuous improvement.
Spiral Methodology: This is a risk-driven approach that involves continuous iteration
and evaluation throughout the software development process. The spiral methodology
emphasizes risk management and involves multiple cycles of planning, design,
development, and testing.
Rapid Application Development (RAD) Methodology: This is an iterative approach
that emphasizes rapid prototyping and testing. The RAD methodology involves frequent
user feedback and the use of tools and technologies to accelerate the development
process.
The choice of SDLC methodology depends on the specific needs and requirements of the
project as well as the preferences of the development team. Each methodology has its
own advantages and disadvantages and the decision should be based on factors such as
project complexity, budget, and timeline.
I select waterfall because it is easy to use and it is very useful for small project
Waterfall Model
1. Requirement Gathering and analysis: All possible requirements of the system to
Be developed are captured in this phase and documented in requirement specification
document.
2. System Design: The requirement specifications form first phase are studied in this
phase and the system design is prepared. This system design helps in specifying hardware
and system requirements and help in defining the overall system architecture.
3. Implementation: With inputs from the system design ,the system is first developed
In small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality, which is referred to as Unit Testing.
4. Integration and Testing: All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is
tested for any faults and failures.
5. Deployment of system: Once the functional and non-functional testing is done; the
product is deployed in the customer environment or released into the market
6. Maintenance: There are some issues which come up in the client environment. To fix
those issues, patches are released. Also to enhance the product some better versions are
released. Maintenance is done to deliver these changes in the customer environment.
2. SYSTEM ANALYSIS STUDY
2.1 Introduction
2.1.1. Project Description
The Blood Donation Agent is to create an e-Information about the donor that are related to
donating the blood. Through this application any person who is interested in donating the
blood can register. Moreover if any general consumer wants to make request blood online he
can also take the help of this site. Admin is the main authority who can do addition, deletion,
and modification if required. The application for the storage of the data has been planned.
Using the constructs of MySQL and all the user interfaces have been designed using the PHP
technologies.
The database connectivity is planned using the “SQL Connection” methodology. The
standards of security and data protective mechanism have been given a big choice for proper
usage.
• Less Security.
Disadvantages
2. The system makes the overall project management much easier and flexible.
3. Readily upload the latest updates, allows user to download the alerts by clicking the
URL.
4. There is no risk of data mismanagement at any level while the project development is
under process.
A blood donation system is a critical application that requires a reliable and efficient database
to manage information about blood donors, blood banks, and blood donation events. The
database should be designed to ensure the confidentiality and integrity of donor information
and ensure the efficient management of blood inventory. Here are some requirements for a
database for a blood donation system:
Donor information: The database should be able to store detailed information about the
donors, such as their name, address, age, gender, blood type, and contact information. This
information should be securely stored and easily retrievable when required.
Blood bank information: The database should also store information about the blood banks,
such as their location, contact information, and inventory status. This information should be
easily accessible to the blood donation system.
Blood inventory: The database should track the availability of different types of blood in the
blood banks, such as A+, B+, O+, and so on. It should also track the expiration dates of the
blood units.
Donation history: The database should maintain a record of all blood donations made by the
donors, including the date, blood type, and quantity of blood donated. This information can
help identify regular donors and ensure that blood banks have a regular supply of blood.
Security: The database should be secure and designed to protect donor information. Access to
the database should be restricted to authorized personnel only, and the database should be
backed up regularly to prevent data loss.
Reporting: The database should generate reports on the blood inventory, blood donation
events, and donor history. Reports can help blood banks identify trends and plan blood
donation events.
Integration: The database should be easily integrated with other systems used by the blood
donation system, such as donor registration and scheduling software, to ensure that all
systems are working together efficiently.
Overall, a database for a blood donation system should be designed to ensure the efficient and
effective management of blood inventory, maintain the privacy and confidentiality of donor
information, and provide the necessary reports and analytics to support the blood donation
system.
I have used MySQL for Database
MySQL
MySQL is a relational database management system
MySQL is open-source and free
MySQL is ideal for both small and large applications
MySQL is very fast, reliable, scalable, and easy to use
MySQL is cross-platform
MySQL is compliant with the ANSI SQL standard
MySQL was first released in 1995
MySQL is developed, distributed, and supported by Oracle Corporation
MySQL is named after co-founder Monty Widenius's daughter: My
Donor registration: The user interface should allow donors to easily register their personal
and medical information, such as name, contact information, and blood type. It should also
allow them to update their information as needed.
Appointment scheduling: The user interface should allow donors to schedule appointments to
donate blood. It should provide a calendar view that shows available dates and times, and
allow donors to select a time that is convenient for them.
Donation history: The user interface should provide donors with access to their donation
history, including the date of their last donation, the type of blood donated, and the blood
bank where the donation was made.
Donor education: The user interface should provide educational resources to help donors
understand the blood donation process, including eligibility criteria, the donation process, and
the benefits of blood donation.
Blood donation events: The user interface should provide information about upcoming blood
donation events, including the location, date, and time of the event.
Messaging: The user interface should allow donors to receive messages from the blood
donation system, such as reminders about upcoming appointments, notifications about blood
donation events, and updates about the status of their donations.
Mobile responsiveness: The user interface should be optimized for mobile devices, allowing
donors to access the system from their smartphones or tablets.
Overall, a user interface for a blood donation system should be designed to make it easy for
donors to schedule appointments, track their donation history, and receive educational
resources about blood donation. It should be user-friendly, intuitive, and optimized for
mobile devices, and designed to be accessible to people with disabilities.
3. SYSTEM DESIGN
3.1 Introduction
The front end is an interface between the user and the back end. The front and back ends may
be distributed amongst one or more systems front end can refer to any hardware that
optimizes or protects network traffic Network traffic passes through the front-end hardware
before entering the network. In compilers, the front end translates a computer programming
source code into an intermediate representation, and the back end works with the intermediate
representation to produce code in a computer output language. The back end usually
optimizes to produce code that runs faster. The front-end/back-end distinction can separate
the parser section that deals with source code and the back end that generates code and
Optimizes.
1.Administration:
User Account:
AccountID
Username
Password
UserDesc
HintQuestion
Answer
RoleID
Active
UserRole:
RoleID
RoleName
RoleDesc
Active
BDAState:
StateID
StateName
StateCode
StateDesc
CountryID
Active
Country:
CountryID
CountryName
CountryDesc
CountryCode
BDACity
CityID
CityName
CityDesc
CityCode
StateID
Active
BDALocation:
LocationID
LocationName
LocationDesc
LocationCode
CityID
Pin code
Active
Blood Group:
BloodGroupID
BloodGroup
Description
Active
Blood Type:
BloodTypeID
TypeName
TypeDesc
Active
PersonalDetails:
UserAccountID
FirstName
MiddleName
LastName
Email
DOB
Weight
Gender
ImageURL
BloodGroupID
BloodType
BloodType
AddressID
ContactNo_Office
ContactNo_Residence
MobileNo
Active
EmployeeDetail:
EmpId
Name
Address
Phone
Email
Active
DonationFrequencies:
FrequencyID
Frequency
Description
Active
UserAcountID
OrganisationID
Active
Organisation:
OrgID
OrgName
OrgType
Email
OrgAddrID
OrgImageURL
OrgDescription
ContactNo
MobileNo
Active
Comment
OrganisationType:
TypeID
TypeName
TypeDescription
OrgImage
Active
3.2.1 System Flow Chart
3.2.2 Use Case Diagram
Use case diagrams are valuable for visualizing the functional requirements of a system that
will translate into design choices and development priorities. They also help identify any
internal or external factors that may influence the system and should be taken into
consideration. They provide a good high-level analysis from outside the system. Use case
diagrams specify how the system interacts with actors without worrying about the details of
how that functionality is implemented. While a use case itself might drill into a lot of detail
(such as, flow of events and scenarios) about every possibility, a use-case diagram can help
provide a higher-level view of the system, providing the simplified and graphical
representation of what the system must actually do. Use cases define interactions between
external actors and the system to attain particular goals.
3.2.3 Data Flow Diagram
Admin
Login data
login
Value Abilities
Table View of value
Abilities details
Level 1 DFD: For Users Module
Call Center
Login
Value Abilities
Table updating and
editing
3.2.4 Any Other Applicable Diagram
An entity relationship diagram (ERD) shows the relationships of entity sets stored in a
database. An entity in this context is an object, a component of data. An entity set is a
collection of similar entities. These entities can have attributes that define its properties. By
defining the entities, their attributes, and showing the relationships between them, an ER
diagram illustrates the logical structure of databases.ER diagrams are used to sketch out the
design of a database.
Constraints enforce limits to the data or type of data that can be inserted/updated/deleted from
a table. The whole purpose of constraints is to maintain the data integrity during an
update/delete/insert into a table. In this tutorial we will learn several types of constraints that
can be created in RDBMS.
Types of constraints
NOT NULL
UNIQUE
DEFAULT
CHECK
Domain constraints
Mapping constraints
NOT NULL:
NOT NULL constraint makes sure that a column does not hold NULL value. When we don’t
provide value for a particular column while inserting a record into a table, it takes NULL
value by default. By specifying NULL constraint, we can be sure that a particular column(s)
cannot have NULL values.
UNIQUE:
UNIQUE Constraint enforces a column or set of columns to have unique values. If a column
has a unique constraint, it means that particular column cannot have duplicate values in a
table.
DEFAULT:
The DEFAULT constraint provides a default value to a column when there is no value
provided while inserting a record into a table.
CHECK:
This constraint is used for specifying range of values for a particular column of a table. When
this constraint is being set on a column, it ensures that the specified column must have the
value falling in the specified range.
Key constraints:
PRIMARY KEY:
Primary key uniquely identifies each record in a table. It must have unique values and cannot
contain nulls.
FOREIGN KEY:
Foreign keys are the columns of a table that points to the primary key of another table. They
act as a cross-reference between tables.
Domain constraints:
Each table has certain set of columns and each column allows a same type of data, based on
its data type. The column does not accept values of any other data type.
Domain constraints are user defined data type and we can define them like this:
Domain Constraint = data type + Constraints (NOT NULL / UNIQUE / PRIMARY KEY /
FOREIGN KEY / CHECK / DEFAULT).
Mapping Cardinality:
One to One: An entity of entity-set A can be associated with at most one entity of entity-set B
and an entity in entity-set B can be associated with at most one entity of entity-set A.
One to Many: An entity of entity-set A can be associated with any number of entities of
entity-set B and an entity in entity-set B can be associated with at most one entity of entity-
set A.
Many to One: An entity of entity-set A can be associated with at most one entity of entity-set
B and an entity in entity-set B can be associated with any number of entities of entity-set A.
Many to Many: An entity of entity-set A can be associated with any number of entities of
entity-set B and an entity in entity-set B can be associated with any number of entities of
entity-set A.
3.3.3 Database Schema
A database schema is a blueprint or design for organizing and structuring data in a database.
In a Blood Donation Management project, the database schema is an important component
that defines the structure and relationships between the different data entities. Here is an
example of a database schema that can be used in a Blood Donation Management project:-
Login
Register User
Admin
Blood Request
Registration Form
Camps
View
Contact
3.4. USER INTERFACE DESIGN
The user interface design is an important aspect of a Blood Donation Management system as
it directly affects the user experience. Here are some considerations for the user interface
design of a Blood Donation Management system:
Home Page
About
Register Donor
Contact
3.4.2 Reports Layout Design
Dashboard
Register Donor
Camps
Requirements
BIBLIOGRAPHY
https://www.php.net/
https://www.w3schools.com/
https://blooddonation.co.in/
https://www.blood.co.uk/
https://getbootstrap.com/
https://fontawesome.com/
https://jquery.com/