ONLINE BLOOD BANK MANAGEMENT

A Major Project Report

Submitted in Partial fulfillment for the award of
Bachelor of Technology in Computer Science & Engineering

Submitted to
RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA BHOPAL (M.P)

Submitted by
Neelesh Singh Thakur [0157CS181099] Palak Chandak [0157CS181105]
Parul Hardikar [0157CS181108] Mani Pratap Singh [0157CS181091]

Under the Guidance of

Dr. Ashish Khare Sir
Head of the Department

DEPARTMENT OF COMPUTER SCIENCE& ENGINEERING

LAKSHMI NARAIN COLLEGE OF TECHNOLOGY & SCIENCE, BHOPAL (M.P.)
SESSION 2021-22
 LAKSHMI NARAIN COLLEGE OF TECHNOLOGY &SCIENCE
BHOPAL (M.P.)
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

CERTIFICATE
This is to certify that the work embodied in this report entitled “Online Blood
Bank Management” has been satisfactorily completed by Mani Pratap Singh
(0157CS181091) , Neelesh Singh Thakur (0157CS181099) , Palak Chandak
(0157CS181105) , Parul Hardikar (0157CS181108) of 4th year. It is bonafied
piece of work carried out under guidance in the department of Computer
Science & Engineering, Lakshmi Narain College of Technology & Science,
Bhopal (M.P.). for partial fulfillment of the Bachelor of Technology Degree in
Computer Science & Engineering, during the academic year 2021-22.
Under Guidance of
Dr. Ashish Khare Sir
Head of the Department

Approved by
Dr. Ashish Khare Sir
Head of the Department

Forwarded by
Dr. A.K. Sachan sir
Principal
 LAKSHMI NARAIN COLLEGE OF TECHNOLOGY &SCIENCE
BHOPAL (M.P.)
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

CERTIFICATE OF APPROVAL

This foregoing project work is hereby approved as a creditable study of

Engineering carried out and presented in a manner satisfactory to
warranty its acceptance as a prerequisite to the degree for which it has
been submitted. It is understood that by this approval the undersigned
do not necessarily endorse or approve any statement made, opinion
expressed or conclusion drawn there in, but approve the project only
for the purpose for which it has been submitted.

(Internal Examiner) (External Examiner)

Date: Date:
 LAKSHMI NARAIN COLLEGE OF TECHNOLOGY & SCIENCE
BHOPAL (M.P.)
DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

DECLARATION

We, Neelesh Singh Thakur (0157CS181099) , Palak Chandak

(0157CS181105) , Parul Hardikar (0157CS181108), Mani Pratap Singh
(0157CS181091) student of “Bachelor of Technology” in Computer Science
& Engineering”, session: 2021 -22, Lakshmi Narain College of Technology
& Science Bhopal (M.P.), hereby declare that the work presented in this
Synopsis Report for Major Project entitled “Online Blood Bank
Management” is the outcome of my own work, is bonafide and correct to the
best of our knowledge and this work has been carried out taking care of
Engineering Ethics. The work presented does not infringe any patented work
and has not been submitted to any other University or anywhere else for the
award of any degree or any professional diploma.

Neelesh Singh [0157CS181099] Palak Chandak [0157CS181105]

Parul Hardikar [0157CS181108] Mani Pratap Singh [0157CS181091]

Date :
index
Abstract

Yelpcamp is a system that gives you the facility of viewing various types of tourist places.
This system is made so that the tourists can visit different tourist places and plan their trip.
The project ‘Yelpcamp’ is developed so that people can view places, comment and also
give review about them. In the present era where “time” proves to be the most important
asset for an individual by replacing the current register system to fully computerize, it not
only saves the precious asset that is time, but also accuracy, reliability and uniformity can
be maintained. This project helps to search the data faster than existing system, to get
records easily per requirement.

Keywords :-
 Chapter – 1
Introduction

1.1 Introduction :-
1.2 Objective :-
1.3 Motivation :-

The motivation behind this project is due to India's rich history, its cultural and geographical
diversity, makes it international tourism. We present heritage and cultural tourism along with
transportation, packages, and various events of India via our websites. Our website provides
best travelling services to the customers and travel agents, provides a search platform where
a tourist can find their tour places according to their choices, promotes responsible and
interesting tourism so that people can enjoy their holidays at their favourable places, develop
tourism with different cultures so that they enrich the tourism experience and build pride.

1.4 Scope :-
The web-based classification of applications is considered, which maintains a centralized
repository of all related information. The system allows one to easily access the relevant
information and make necessary travel arrangements. Users can decide about places they
want to visit and make bookings online for travel and accommodation. It is a fast and light
weight code project which is ultimately very beneficial for dealing with huge users
database and thus increasing the scalability. In our future research, we intend to extend the
initial results obtained to include additional performance metrics.
 Chapter – 2
LITERATURE SURVEY
This chapter provides the literature review of the work that has previously done on predicting the
chances of student’s enrollment in universities. There have been several project and studies performed
on topics related to student’s admission into universities.

2.1 Literature Survey:-

1. Travel System Faith Motors :-

Online Travel Management system is a web-based application that allows travellers check for bus
ticket availability, book a ticket, book a hotel and also hire a car. At Faith Motors, the traditional
method of travel management system is presently in use which involved the use of papers for storing
traveller’s information. With this method there is always long queue, loss of data, incomplete
traveller’s information and inaccuracy. An online Travel management system was implemented for
Faith Motors to solve the existing problems. Tools such as MySQL, PHP and WAMP server were
used to develop the online travel management system.

2. Online Tours Ticketing Asp.NET :-

Online Tours and Travels Management is a software web application to book multiple types of
tickets online. Presently this web site will offer Trip booking, Air Ticket Booking and Bus Ticket
Booking. So, for all type of travellers this website provides a solution to book their tickets online and
make the payment online. The site is also providing the communication between user and the
administration. This project has two modules, one admin module and the client module. In admin
module all the master entries, ticket pricing, trip details, flight details, bus details, and their schedule
etc can be entered. So, admin complete control on the site. Apart from this in each section proper
reports are provided to know how many tickets are booked in each section. In case of user module,
user can sign up after that they can able login into the site, they can search for the different trips,
flight details, bus details etc, after searching they can able to book the tickets. The main objective of
the application is to automate the existing system of issuing tickets at only at select outlets to make
available online, so each customer can book their tickets online by sitting at his or her place.

2.2 Related Work:-

 Chapter – 3
PROBLEM STATEMENTS

3.1 Problem Statement :-

3.2 Existing System :-

In the present system a customer has to approach various agencies to find details of places and to
book tickets. This often requires a lot of time and effort. A customer may not get the desired
information from these offices and often the customer may be misguided. It is tedious for a
customer to plan a particular journey and have it executed properly.
3.3 Proposed System:-
The proposed system is a web based application and maintains a centralized repository of all
related information. The system allows one to easily access the relevant information and make
necessary travel arrangements. Users can decide about places they want to visit. To provide
flexibility to the users, the interfaces have been developed that are accessible through a browser.
 Chapter – 4
Hardware and Software Requirements

4.1 Software Requirements :-

 HTML :-
Hypertext Markup Language (HTML) is the standard markup language for creating web
pages and web applications. With Cascading Style Sheets (CSS) and JavaScript, it forms a
triad of cornerstone technologies for the World Wide Web.
Web browsers receive HTML documents from a web server or from local storage and render
the documents into multimedia web pages. HTML describes the structure of a web page
semantically and originally included cues for the appearance of the document.

 CSS :-
Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation
of a document written in a markup language like HTML. CSS is a cornerstone technology of
the World Wide Web, alongside HTML and JavaScript.

 Node.js :-
Node.js is an open-source, cross-platform JavaScript run-time environment that executes
JavaScript code outside of a browser, Node.js lets developers use JavaScript to write
Command Line tools and for server-side scripting—running scripts server-side to produce
dynamic web page content before the page is sent to the user's web browser.
As an asynchronous event driven JavaScript runtime, Node is designed to build scalable
network applications.

 MongoDB :-
MongoDB is a free and open-source cross-platform document-oriented database
program. Classified as a NoSQL database program, MongoDB uses JSON-like
documents with schemata. MongoDB is developed by MongoDB Inc., and is
published under a combination of the GNU Affero General Public License and the
Apache License.

 Express Framework :-
 Express.js, or simply Express, is a web application framework for Node.js, released as free
and open-source software under the MIT License. It is designed for building web applications
and APIs. It has been called the de facto standard server framework for Node.js.
The original author, TJ Holowaychuk, described it as a Sinatra-inspired server, meaning that
it is relatively minimal with many features available as plugins. Express is the backend part
of the MEAN stack, together with MongoDB database and AngularJS frontend framework.

4.2 Hardware Requirements :-

 Processor : Intel or high.
 RAM : 4 GB or above.
 Space on disk : Minimum 100 MB for running the application.
 Device : Laptop or computer compatible to the above-mentioned software specifications.
 Minimum space to execute : 20 MB
 Chapter – 5
Method Used

5.1 Methodologies Used :-

 Prototype Model :-
The prototype model requires that before carrying out the development of actual software, a
working prototype of the system should be built. A prototype is a toy implementation of the
system. A prototype usually turns out to be a very crude version of the actual system, possible
exhibiting limited functional capabilities, low reliability, and inefficient performance as
compared to actual software. In many instances, the client only has a general view of what is
expected from the software product. In such a scenario where there is an absence of detailed
information regarding the input to the system, the processing needs, and the output requirement,
the prototyping model may be employed.

Steps of Prototype Model :-

Step 1 :- Requirements gathering and analysis

A prototyping model starts with requirement analysis. In this phase, the requirements of the system
are defined in detail. During the process, the users of the system are interviewed to know what is
their expectation from the system.

Step 2 :- Quick design

The second phase is a preliminary design or a quick design. In this stage, a simple design of the
system is created. However, it is not a complete design. It gives a brief idea of the system to the
user. The quick design helps in developing the prototype.

Step 3 :- Build a Prototype

In this phase, an actual prototype is designed based on the information gathered from quick design.
It is a small working model of the required system.
 Step 4 :- Initial user evaluation

In this stage, the proposed system is presented to the client for an initial evaluation. It helps to find
out the strength and weakness of the working model. Comment and suggestion are collected from
the customer and provided to the developer.

Step 5 :- Refining prototype

If the user is not happy with the current prototype, you need to refine the prototype according to the
user’s feedback and suggestions. This phase will not over until all the requirements specified by the
user are met. Once the user is satisfied with the developed prototype, a final system is developed
based on the approved final prototype.

Step 6 :- Implement Product and Maintain

Once the final system is developed based on the final prototype, it is thoroughly tested and
deployed to production. The system undergoes routine maintenance for minimizing downtime and
prevent large-scale failures.

The description of above steps in this project is as follows :-

 Feasibility Study :-

A feasibility analysis usually involves a thorough assessment of the operation, financial

and technical aspects of a proposal. Feasibility study is the test of the system proposal
made to identify whether the user needs may be satisfied using the current software and
hardware technologies.

Five Areas of Project Feasibility Study :-

1. Technical Feasibility :-
This project is the web application so it requires only web browser environment to run on. The
language which is used in development is Node.js and we take help of Express Framework to
implement the predefined methods so it is understandable by developer therefore we can state that
our project is technically feasible.
 2. Economic Feasibility:
As in this project the all resources are open source and user participation is
spontaneous, so we can say that this project is economically feasible.

i. Operational Feasibility:

As this project is is all about the recreational camping activities done at the various
tourist places so it fulfills all the qualities of operational feasibility.

ii. Legal Feasibility:

My project fulfills all the legal documentation so it is legally feasible in nature.

iii. Scheduling Feasibility:

This project is completed within my training period so it is completed in scheduled

time so it is feasible on time.

pg. 1
Chapter – 6
pg. 2
 Design Framework

6.1 E-R Diagram :-

The ER model i.e. Entity-Relationship model defines the conceptual view of a database. It
works around real-world entities and the associations among them. At view level, the ER
model is considered a good option for designing databases. ER Model is represented by
means of an ER diagram. Any object, for example, entities, attributes of an entity,
relationship sets, and attributes of relationship sets, can be represented with the help of an
ER diagram.
Entity - An entity can be a real-world object, either animate or inanimate, that can be easily
identifiable. An entity set is a collection of similar types of entities. An entity set may
contain entities with attribute sharing similar values
Attributes - Entities are represented by means of their properties, called attributes. All
attributes have values.
Types of Attributes :
Single-value attribute − Single-value attributes contain single value. These are represented
by ellipse.
Composite attribute - Composite attributes are made of more than one simple attribute.
Derived attribute - Derived attributes are the attributes that do not exist in the physical
database, but their values are derived from other attributes present in the database. These
are represented by dashes ellipse.
Multi-value attribute − Multi-value attributes may contain more than one values. These
are represented by double ellipse.
Relationship :
The association among entities is called a relationship. Different types of relationships are
as:
 One-to-one − One entity from entity set A can be associated with at most one entity
of entity set B and vice versa.
 One-to-many − One entity from entity set A can be associated with more than one
entities of entity set B however an entity from entity set B, can be associated with at
most one entity.

pg. 3
  Many-to-one − More than one entities from entity set A can be associated with at
most one entity of entity set B, however an entity from entity set B can be associated
with more than one entity from entity set A.
 Many-to-many − One entity from A can be associated with more than one entity
from B and vice versa.

6.2 Use - Case Diagram :-

A use case diagram is used to represent the dynamic behaviour of a system. It encapsulates
the system's functionality by incorporating use cases, actors, and their relationships. It
models the tasks, services, and functions required by a system/subsystem of an application.
It depicts the high-level functionality of a system and also tells how the user handles a
system.
The main purpose of a use case diagram is to portray the dynamic aspect of a system. It
accumulates the system's requirement, which includes both internal as well as external
influences. It invokes persons, use cases, and several things that invoke the actors and
elements accountable for the implementation of use case diagrams. It represents how an
entity from the external environment can interact with a part of the system. Following are
the purposes of a use case diagram given below:
 It gathers the system's needs.
 It depicts the external view of the system.
 It recognizes the internal as well as external factors that influence the system.

pg. 4
  It represents the interaction between the actors.

It is essential to analyse the whole system before starting with drawing a use case diagram,
and then the system's functionalities are found. And once every single functionality is
identified, they are then transformed into the use cases to be used in the use case diagram.
After that, we will enlist the actors that will interact with the system. The actors are the
person or a thing that invokes the functionality of a system. It may be a system or a private
entity, such that it requires an entity to be pertinent to the functionalities of the system to
which it is going to interact.
Once both the actors and use cases are enlisted, the relation between the actor and use case/
system is inspected. It identifies the no of times an actor communicates with the system.
Basically, an actor can interact multiple times with a use case or system at a particular
instance of time. Following are some rules that must be followed while drawing a use case
diagram :-
 A pertinent and meaningful name should be assigned to the actor or a use case of a
system.
 The communication of an actor with a use case must be defined in an understandable
way.
 Specified notations to be used as and when required.
 The most significant interactions should be represented among the multiple no of
interactions between the use case and actors.

pg. 5
pg. 6
6.3 Data Flow Diagram :-

pg. 7
pg. 8
pg. 9
pg. 10