Blood bank management

BLOOD BANK MANAGEMENT

A PROJECT REPORT

Submitted in partial fulfilment of the

Requirements for the award of the Degree of

BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)

BY

Mr. SHIVAM MAURYA & Mr. SHUBHAM LOKHANDE

Seat Number: 318 & 317

Under the esteemed guidance of

Prof. KRUNALI PETKAR

DEPARTMENT OF INFORMATION TECHNOLOGY

SMT. PARMESHWARIDEVI DURGADUTT TIBREWALA LIONS

JUHU COLLEGE OF ARTS, COMMERE AND SCIENCE
Affiliated to University of Mumbai
J.B. NAGAR, ANDHERI (E), MUMBAI-400059
Blood bank management

PROFORMA FOR THE APPROVAL PROJECT PROPOSAL

PNR No :…………………………… Roll No :………………………

1. Name of the student :

__________________________________________________

2. Title of the Project :

__________________________________________________

3. Name of the Guide :

__________________________________________________

4. Teaching experience of guide : ______________________

5. Is this your first submission? Yes No

Signature of the student Signature of the Guide

Date :………………………… Date :………………………..

Signature of the Cordinator Date :…………………………

Blood bank management

SMT.PARMESHWAEIDEVI DURGADUTT TIBREWALA LIONS JUHU

COLLEGE OF ARTS,COMMERECE & SCIENCE
Affilated to University of Mumbai

J.B.NAGAR, ANDHERI (E) MUMBAI-59.

DEPARTMENT OF INFROMATION TECHNOLOGY

CERTIFICATE
This is to certify that project entitled "Blood Bank Management" Is bonafied work of
Mr.Shivam Maurya and Shubham Lokhande Bearing Seat No. and seat no. submitted
in partial fulfilment of the requirements for the award of degree of BACHELOR OF SCIENCE
in INFORATION TECHNOLOGY from University of Mumbai. Examination had not been
submitted for any other examination and does not form of any other course undergone by the
candidate. It is further certified that he has completed all required phases of the project.

Internal Examiner External Examiner

Project Guide Coordinator

College Stamp
Blood bank management

ABSTRACT
This project is aimed to developing an online Blood Donation Information. The entire

project has been developed keeping in view of the distributed client server computing

technology, in mind. The Blood Donation Agent is to create an e-Information about the donor

and organization that are related to donating the blood. Through this application any person

who is interested in donating the blood can register himself in the same way if any organization

wants to register itself with this site that can also 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 project has been planned to be having the view of distributed architecture, with

centralized storage of the database. The application for the storage of the data has been planned.

Using the constructs of MS-SQL Server and all the user interfaces have been designed using

the ASP.Net 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. The application takes care of different modules and their associated

reports, which are produced as per the applicable strategies and standards that are put forwarded

by the administrative staff.

The entire project has been developed keeping in view of the technology, in mind.

distributed client server computing specification has been normalized up to 3NF to eliminate

all the anomalies that may arise due to the database transaction that are executed by the general

users and the organizational administration.

Blood bank management

ACKNOWLEDGEMENT

Achievement is finding out what you would be doing rather than what you have to do.

It is not until you undertake such a project that you realize how much effort and hard work it

really is, what are your capabilities and how well you can present yourself or other things. It

tells us how much we rely on the efforts and goodwill of others. It gives me immense pleasure

to present this report towards the fulfilment of my project.

It has been rightly said that we are built on the shoulder of others .For everything I have

achieved, the credit goes to all those who had helped me to complete this project successfully.

I take this opportunity to express my profound gratitude to management of Smt.

PARMESHWARIDEVI DURGADUTT TIBREWALA LIONS JUHU COLLEGE OF

ARTS, COMMERCE & SCIENCE for giving me this opportunity to accomplish this project

work.

A special vote of thanks to” Prof. Krunali petkar” and “principal Dr.(Mrs.) Trisha

Mehta” who is our professors & project guides for their most sincere, useful and encouraging

contribution throughout the project span.

Finally, I would like to thank entire Information Technology department who directly

or indirectly helped me in completion of this project & to my family without whose support,

motivation &encouragement this would not have been possible.

Mr. Shivam S. Maurya

Mr.Shubham Lokhande
Blood bank management

DECLARATION

I "Mr Shivam S. Maurya & Shubham Lokhande hereby declare that I myself

have completed the project under the guidance of Prof. Krunali Petkar. I on my own

have designed the system and have done all the programming required.

It may require some modifications in the future as per the user's requirements.

From practical implementation point of view flexibility in the changes have

incorporated in the package.

I am sure that I can do any kind of modification suggested while practical

implementation by modifying file design or the program code if necessary.

Shivam s. Maurya

Shubham Lokhande
Blood bank management

TABLE OF CONTENTS

PAGE
Sr No Topic
NO
1 CHAPTER1: INTRODUCTION
1.1 Background
1.2 Objectives
1.3 Purpose,Scope,Applicability
1.3.1 Purpose
1.3.2 Scope
1.3.3 Applicability
1.4 Project Overview
1.5 Project Description
1.6 Achievements
2 CHAPTER2: SURVEY OF TECHNOLOGIES
3 CHAPTER3: REQUIREMENTS AND ANALYSIS
3.1 Problem Definition
3.2 REQUIREMENT SPECIFICATION
3.2.1 Functional Requirements
3.3 PLANNING AND SCHEDULING
3.4 SOFTWARE AND HARDWARE REQUIREMENTS
3.4.1 Software requirements
3.4.2 Hardware requirements
3.5 CONCEPTUAL MODELS
4 CHAPTER4: SYSTEM DESIGN
4.1 Data Flow Diagrams (DFD)
4.2 Data Design/ UML Diagram
4.3 Procedural Design
4.4 User interface design
4.5 Security Issues & Access Control
4.6 Test Case Design
Blood bank management

CHAPTER 1: INTRODUCTION

1.1 BACKGROUND:

In existing medicine ordering system there are lots of problems that user face. If user

needs medicine on urgent basis then it not possible in the current existing system. There is no

concept of uploading validated prescription to buy medicines in existing system, this can lead

to increase illegal/fraud activities in medicine market.

Today technology is controlling everything in life. Online shopping is one of the

electronic phenomena scattered in this time. So we have decided to make the medicine buying

experience easy and comfortable for the users. Our website 'Online Medication Care system

includes different menus with all medicines category, its prices, some description and pictures

of those medicines. User can easily search the medicines prescribed by the doctor and buy them

by just one click whenever required. Home-delivery of those medicines is People can buy or

sell anything online done for the users. In case of some emergency our delivery services are

also available on urgent basis to the users. Moreover, it has access easy to previous orders and

customer can also re-order the medicines at a rapid pace. Payment of the medicines can be done

at the time of delivery. Its saves lot of time for users.

1|Page
Blood bank management

1.2 OBJECTIVES:

 Our website named 'Online Medication care system' aims to build a system

about online medicine ordering .

 Our motto is to bring revolutionary changes in the medicine buying experience

of the .

 Ordering online medicines makes easy lifestyle for the user.

 Existing system is very time consuming, so user can save a lot of time by using

our delivery facility.

 It also saves money.

 Existing system lacks with the service of urgent delivery that helps the user to

buy medicine on urgent basis.

 To buy allopathic medicines prescribed by doctor, user must upload valid

prescription our system provides with a medicines that are to be consumed

internally .

 Whereas, prescription is not necessary for any basic medicines as well as

lotions, cream or dusting powders.

 Our objective is to provide users with the medicines at their doorstep.

 Customer Satisfaction is our prime objective.

2|Page
Blood bank management

1.3 PURPOSE, SCOPE AND APPLICABILITY:

1.3.1 Purpose: -

Purpose of the project is to bring revolutionary changes in the medicine buying

experience of the users. Existing system is a very tedious process so our main purpose of

creating this project iso make users lifestyle simple. In some pharmacies blending of the

medicines is done, so to avoid that our purpose is to provide reliable and genuine medicines.

The purpose of education has always been the same to be more aware and

knowledgeable and lead a better more fulfilling life. Over the years, its importance has only

increased as the world is becoming more competitive. You need to have an understanding of

the field you want to be in to excel in it. More and more degrees in different areas are being

offered encouraging people.

Campus based institutions have always been a major part of educational

infrastructure. However, in this technology-fueled society, online learning is gradually

gaining popularity. This mode of learning has proved to be more accessible, convenient,

flexible, and affordable for many. Those who are working or do not have time to take classes

at a campus can still pursue higher education through online programs.

3|Page
Blood bank management

1.3.2 Scope:-

In today's generation online shopping has a lot of scope. Online shopping makes life

easy and hassle-free for the users. Online Medication care system' has a bright scope in the

market in today's world. Easy access to the website ,makes user comfortable with the process

and satisfies his needs. In our system user can order the medicines online via website and can

easily get the medicines delivered at the user's doorstep Option of urgent delivery of medicines

is a highlight of this system. User has to simply upload the prescription specified by the doctor

and has to enter the quantities of medicines required. If user is in need of any basic antibiotic

medicines or any kind of lotions, creams or medicated user-friendly GUI and hassle-free

delivery process powder then he can easily search and buy those products. The future scope of

our system is that we will include the module of online payment which will be implemented in

future updates.

4|Page
Blood bank management

1.3.3 Applicability:-
 Users - The users can order their required medicines online through our website just
by one click. It cuts down the physical efforts that the users need to take in the
existing system. The general customers as well as company staff' will be able to use
this system effectively.
 Pharmacist- This project is not only will indirectly help the pharmacist to grow their
business over the internet. useful for the customers, but also to the pharmacist.

1.4 Project Overview:-

The Blood Donation Agent is to create an e-Information about the donor and
organization that are related to donating the blood. Through this application any person
who is interested in donating the blood can register himself in the same way if any
organization wants to register itself with this site that can also 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.

1.5. Project Description:-

This project is aimed to developing an online Blood Donation Information. The entire
project has been developed keeping in view of the distributed client server computing
technology, in mind.
The Blood Donation Agent is to create an e-Information about the donor and
organization that are related to donating the blood. Through this application any person who is
interested in donating the blood can register himself in the same way if any organization wants
to register itself with this site that can also 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 project has been planned to be having the view of distributed architecture, with
centralized storage of the database. The application for the storage of the data has been planned.
Using the constructs of MS-SQL Server and all the user interfaces have been designed using
the ASP.Net technologies.

5|Page
Blood bank management

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 .
The application takes care of different modules and their associated reports, which are
produced as per the applicable strategies and standards that are put forwarded by the
administrative staff.
The entire project has been developed keeping in view of the distributed client server
computing technology, in mind. The specification has been normalized up to 3NFto eliminate
all the anomalies that may arise due to the database transaction that are executed by the general
users and the organizational administration. The user interfaces are browser specific to give
distributed accessibility for the overall system.
The internal database has been selected as MS-SQL server 2000.The basic constructs
of table spaces, clusters and indexes have been exploited to provide higher consistency and
reliability for the data storage. The MS-SQL server2000 was a choice as it provides the
constructs of high-level reliability and security. The total front end was dominated using the
ASP.Net technologies. At all proper levels high care was taken to check that the system
manages the data consistency with proper business rules or validations.
The database connectivity was planned using the latest "SQL Connection" technology
provided by Micros oft Corporation. The authentication and authorization was crosschecked at
all the relevant stages. The user level accessibility has been restricted into two zones namely.

1.6 Achievements

The current scenario is definitely hopeful however challenges continue to exist. The
target for the country is to achieve more than 90% VBD. There are marked regional variations,
some states collect voluntary blood units more than the national average, others are far below
in meeting targets. The VBD in almost 13 states of the country is less than 50 %. Seasonal
variations also account for fluctuations in blood collections. The voluntary blood donation is
less during extremes of weather conditions like harsh summer or winter months. It is also
affected by examination periods of students and vacations of educational institutions. India has
a huge burden of patients with thalassemia major who not only require life sustaining regular
transfusion support but are also challenged by all immunization to minor blood group antigens.

6|Page
Blood bank management

This complication places further constraints on the BTS to issue compatible blood.
Establishment of Rare Donor Registries is a much-needed step in this direction. So far the focus
of VBD has been on whole blood collection, but little attention has been given to a pheresis
donors who are currently brought to the blood bank by the patients' attendants.
Apheresis platelets presently are prepared from patient's relatives and/or friends. Voluntary
plateletpheresis donations have been initiated in some center , but the movement needs to gain
strength. The government has plans to set up a national plasma fractionation center and also
to support existing ones to supply plasma derived medicinal products. The only help for
haemophiliac patients now is fresh frozen plasma or cryoprecipitate, the availability of factor
concentrates is restricted by lack of indigenously prepared coagulation factor VIII or IX
concentrates. Plasmapheresis donors may also need to be enrolled in times to come.

7|Page
Blood bank management

CHAPTER 2: SURVEY OF TECHNOLOGIES

 Asp.Net:-

ASP.NET is a web development platform, which provides comprehensive software

infrastructure and various services required to build up robust web applications for PC, as well
as mobile devices.
ASP.NET works on top of the HTTP protocol, and uses the HTTP commands and policies
to seta programming model, aa browser-to-server bilateral communication and
cooperation.ASP.NET is a part of Microsoft .Net platform. ASP.NET applications are
compiled codes, written using the extensible and reusable components or objects present in Net
framework.
These codes can use the entire hierarchy of classes in Net frame work.
The ASP.NET application codes can be written in any of the following languages:
o C#
o Visual Basic.Net
o Jscript
o J#
ASP.NET is used to produce interactive, data-driven web applications over the internet.
It consists of a large number of controls such as text boxes, buttons, and labels for
assembling, configuring, and manipulating code to create HTML pages.

8|Page
Blood bank management

 Bootstrap:-

Bootstrap is a free and open-source front-end web framework. It contains HTML and
CSS-based design templates for typography, forms, buttons, navigation and other interface
components, as well as optional JavaScript extensions. Unlike many earlier web
frameworks, it concerns itself with front-end development only.
Bootstrap is a web framework that focuses on simplifying the development of
informative webpages (as opposed to web apps). The primary purpose of adding it to a
web project is to apply Bootstrap's choices of colour, size, font and layout to that project.
As such, the primary factor is whether the developers in charge find those choices to their
liking. Once added to a project ,Bootstrap provides basic style definitions for all HTML
elements. The end result is a uniform appearance for prose, tables and form elements across
web browsers. In addition, developers can take advantage of CSS classes defined in
Bootstrap to further customize the appearance of their contents. For example, Bootstrap
has provisioned for light- and dark-coloured tables, page headings more prominent pull
quotes, and text with a highlight .
Bootstrap also comes with several JavaScript components in the form of jQuery
plugins. They provide additional user interface elements such as dialog boxes, tooltips,
and carousels. Each Bootstrap component consists of an HTML structure, CSS
declarations, and in some cases accompanying JavaScript code. They also extend the
functionality of some existing interface elements, including for example an auto-complete
function for input fields.

9|Page
Blood bank management

 Sql Express:-

Microsoft SQL Server specifically management system that is free to download,

distribute and use. It comprises a database version of Microsoft's primary relational
database management system (RDBMS)- the SQL Server. Essentially, the SQL Server is
a database management system that can be used to store and access the information stored
in many different databases. SQL Server comes with an impressive range of features like
business intelligence, reporting, and in-depth advanced analytics.
Express is a version of Microsoft's SQL Server relational database targeted for
embedded and smaller-scale applications. SQL Server Express is a free.
The enterprise edition of SQL Server competes against enterprise-oriented systems like
Oracle Database (DB) and MySQL. SQL Server Enterprise comes loaded with features
and can be too expensive for smaller sized companies to maintain SQL Server Express is
the most basic offering available. It is a full database engine you can deploy to a server or
embed into an application. Express is free and comes with many of the same features as
the enterprise edition. SQL Server Express is probably most suited to supporting
production applications for smaller to midsize businesses. A typical SQL Server Express
use case would be a deployment by developers who do not want to create applications
hosted on a server. Using Express, they would be able to develop apps with their SQL
Server with a database.

SOL Server Express Benefits-

Some benefits come with an SQL Server Express deployment.

o Free:- One huge advantage of SQL Server Express is that it is free. Your only
outlay is the time investment you make downloading and setting up the system.
If you only want to learn how to use SQL Server, then Express is for you. There
is nothing system and getting used to how it works.

10 | P a g e
Blood bank management

o Scalability:-SQL Server Express is an ideal starting point for smaller

independent software vendors (ISVS) since it can be used with any smaller
application. The licensing allows Express to be included as part of an app or
product. While there are limitations on memory and socket usage, they are not
as restrictive as some might think. Express is not limited to a single user which
is a commonly held misconception. There is a 10GB database restriction, but
that is a maximum size per database meaning you can have multiple databases
that store up to 10GB of data. If you are an ISV and your company experiences
high growth rate resulting in increased database demands, then you can upgrade
to paid version of SQL Server.
o Security:- Within SQL Server Express there is the option of free online
backup that will help to protect your valuable business data if anything goes
wrong. Administrators should still follow security best practices like restricting
access to backup folders and following Windows password policies .

 CSS:-

Cascading Style Sheets (CSS) is a style sheet language used for describing the
presentation of a document written in a mark-up language like HTML. CSS is a cornerstone
technology of the World Wide Web, alongside HTML and JavaScript.
CSS is designed to enable the separation of presentation and content, including layout,
colours ,and fonts. This separation can improve content accessibility, provide more flexibility
and control in the specification of presentation characteristics, enable multiple web pages to
share formatting by specifying the relevant CSS in a separate CSS file, and reduce complexity
and repetition in the structural content.
Separation of formatting and content also makes it feasible to present the same mark-
up page indifferent styles for different rendering methods, such as on-screen, in print, by voice
(via speech-based browser or screen reader), and on Braille-based tactile devices. CSS also has
rules for alternate formatting if the content is accessed on a mobile device.
The name cascading comes from the specified priority scheme to determine which style
rule applies if more than one rule matches a particular element. This cascading priority scheme
is predictable.

11 | P a g e
Blood bank management

 C#:-
C# is pronounced as "C-Sharp". It is an object-oriented programming language
provided by Microsoft that runs on Net Framework.

By the help of C# programming language, we can develop different types of secured

and robust applications:

o Window applications
o Web applications
o Distributed applications
o Web service applications
o Database applications etc.

C# is approved as a standard by ECMA and ISO C is designed for CLI(Common

Language Infrastructure). CLI is a specification that describes executable code and runtime
environment.
C# programming language is influenced by C++, Java, Eiffel, Modula-3, Pascal etc.
languages.

12 | P a g e
Blood bank management

 Visual Studio:-

Microsoft Visual Studio is an integrated development environment (IDE) from Visual

Studio used to develop computer programs, as well as websites, web apps, web services and
mobile apps. Forms, Windows Presentation Foundation, Windows Store and Microsoft
Silverlight. It can Microsoft. It issues Microsoft software development platforms such as
Windows API, Windows produce both native code and managed code.
Visual Studio includes a code editor supporting IntelliSense (the code completion
component) as well as code refactoring. The integrated debugger works both as a source-level
debugger a machine-level debugger. Other built-in tools include a code profiler, forms designer
for building GUI applications, web designer, class designer, and database schema designer. It
accepts plug-ins that enhance the functionality at almost every level - including adding support
for source control systems (like Subversion and Git) and adding new toolsets like editors and
visual designers for domain-specific languages or toolsets for other aspects of the software
development lifecycle (like the Team Foundation Server client: Team Explorer).
Visual Studio to support 36 different programming languages and allows the code
editor and Visual Studio debugger to support (to varying degrees) nearly any programming
language, provided a language-specific service exists. Built-in languages include:-
o C/C++
o Visual Basic .NET
o C#
o F#
o JavaScript
o Type-Script
o XML
o XSLT
o HTML
o CSS

13 | P a g e
Blood bank management

 Features Of Asp.Net:-
We will be using asp.net technology for developing our system which will allow
us develop dynamic web-application and rich user interface.

 The framework technology reduces coding time-

If you are building large web applications, you're definitely going to appreciate this
frame work technology because it has the ability to reduce the amount of time needed
to code.

 The applications that you build on this framework are secure-

In truth, because of authentication. your programs have never been more safe and
secure. And this is a huge advantage if you're worried about potential security issues in
the future.

 The framework for ASP.NET has a complementary design and rich toolbox in the form
of Visual Studio-

Some excellent features include automatic deployment, WYSIWYG editing, and

drag-and-drop server incredible tool. controls to name just a few of the amazing features
provided by this incredible tool.

 ASP.NET provides continuous monitoring-

Another reason to love this framework is because of the constant and continuous
monitoring. It will continue to monitor applications, components, and pages that it is
running And even better, if the program happens to notice that there are illegal activities
taking place like infinite loops and memory leaks, it will immediately destroy all of
these activities that shouldn't be happening and then it will actually restart itself.

 Deployment is easier than ever with ASP.NET-

14 | P a g e
Blood bank management

For starters, mainly, the biggest reason why deployment is much easier is because
you no longer need to register components. Instead, the configuration info is already built
into the system, which is going to make your life a heck of a lot easier.

 ASP.NET is server-side technology-

Well, since this technology is purely server-side, the code has the ability to execute
on the server. This is good because it actually executes before it's actually sent to the
browser.

 It's easy to write and maintain pages with ASP.NET-

Yes, it's true. It's much easier to write and maintain pages with this framework .The
reason being is that HTML and source code are together. Plus, since the source code is
executed on the server, It provides more flexibility and power to your web-pages

 Common tasks are easy to perform on this framework-

With this framework, simplicity is the key since it's very easy to perform common
tasks easily performed include site configuration, deployment, form submission and
client authentication to name a few.

 formASP.NET runtime closely manages and monitors all processes-

If one process goes dead, a new one will immediately be created in its place
handling is always available.

15 | P a g e
Blood bank management

 Survey:-

During implementation of the project 'Online Medication Care System we studied

some of the IEEE papers and journals and we came across the exact working of the
system and the methodology and algorithm used to implement the system. The working
and interface of the system will be very user friendly and hassle free for user's
enhancement.
We made a survey of various web-applications which provides online medicine
ordering service in the market such as Pharm-easy, Net-meds, Med-life for developing
our system. This web-application majorly deals with the medicines and antibiotics of
certified pharmaceutical companies like 'Cipla', 'Mankind' and 'Abbott available the
medicines and products of this globally certified companies.
The currently existing websites in the market as mentioned above lacks some of the
concepts and module that will be implemented in our developed system. The urgent
delivery option will be included in our system, this will be for user's betterment and his
need. The user feedback module will be included in our system, this feedback module
will enable the user to give suggestions and it will also help us to improve our website.

16 | P a g e
Blood bank management

CHAPTER 3: REQUIREMENTS AND ANALYSIS

3.1 Problem Definition

As we all know the Working of Blood Bank Management System A blood bank is
provide blood, blood components, stored blood and preserved for later use in blood transfusion.
But the Real Fact is Blood transfusion service is a multibillion-dollar profession/ business
worldwide .During the literature survey I am find some limitation in the conventional blood
bank system , in my literature survey I am collect some of the newspaper cutting as evidence
that shows the some limitation of existing blood bank system .Sometime blood bank are not
able to provide a particular blood to needy person, in casualty case, so many blood bank a
maintain record manually, in the rural area not have a proper resource for storage of blood . A
hospital has its own systems and limitations, the coordination between the blood banks is
practically impossible. Because of low number of donors and a greater number of blood banks,
the efficiency and quality of blood banks are low, resulting in wastage of blood and blood
components. The challenges in the present system are:
 In rural area not have sufficient amount of blood banks.
 In rural area not have a good blood storage facilities or equipment.
 Some of the hospitals are not having blood banks.
 Storage and management- Routine blood storage is 42 days or 6 weeks for stored
packed red blood cells by far the most commonly transfused blood product, and
involves refrigeration but usually not freezing.
 RBC storage lesion- Insufficient transfusion efficacy can result from red blood cell
(RBC)blood product units damaged by so-called storage lesion a set of biochemical and
biomechanical changes which occur during storage.

17 | P a g e
Blood bank management

3.2 REQUIREMENT SPECIFICATION:

3.2.1 Functional Requirements:

Authentication:-
 Login- The users/pharmacist can login in the system with their specific user-id and
password.
 Logout- The users/pharmacist can log out from the system.
 Login failure- II the users does not exist in the database or the users has not yet being
authorized by the system admin.

Authorization:-
 Users role check - After logging in, the user can search from the different medicine
categories medicines.
 Pharmacist role check - After successful login, the pharmacist can view the orders and
Accordingly process it.

Upload/Validate Prescription:

 Upload Prescription - User have to upload validated doctor's prescription on the web-
application in prior to place medicine order for certain medicines.
 Validate Prescription - Pharmacist have to verify and validate the uploaded prescription
and accordingly process particular order.
 Invalid Prescription-If the uploaded prescription is invalid then the users order will be
discarded.

18 | P a g e
Blood bank management

Cart Items:-
 Once the uploaded prescription is verified by the pharmacies then user can add the
required medicines and health care products in the cart.
 Users can also add/remove medicine items from their cart.

Buy Medicines:-
 Further user can confirm the quantity of medicines in the order and place the medicine
order accordingly.

Urgent Normal medicine delivery:-

 User gets the option of normal and urgent medicine delivery.

 Normal Delivery:- This option will be available without any extra cost and medicine
will be delivered at users doorstep within 24 hours' time.
 Urgent Delivery:- This option will be available with some extra cost and
medicine will be delivered to user within 2 hours.

Order processing:-

 Once the order is placed by the user then that particular order is further
processed by the pharmacist.
 Bill will be generated as per the ordered product and accordingly user gets
the notification about the payment amount.
 Further the delivery will be scheduled according to the delivery option the
user has previously selected.

19 | P a g e
Blood bank management

3.2.2 Non-Functional Requirements:-

 Performance:-
For better performance the user a high speed internet so that the
upload and download will be done better.
 Security:-
During registration each condition should be provided a unique ID
and password so their login details are kept confidential.
 Usability:-
The system will be easy to use and also user can give their
feedback comment session in the event review.

20 | P a g e
Blood bank management

3.3 PLANNING AND SCHEDULING:

The activities and considerations included in planning and scheduling a project are intended to
provide the Project Manager and the project team members with a systematic approach to
organizing, defining, scheduling, tracking and managing a project.

3.3.1 Gantt Chart:-

A Gantt chart, commonly used in project management, is one of the most popular and useful
ways of showing activities (tasks or events) displayed against time On the left of the chart Is a
list of the activities and along the top is a suitable time scale. Each activity is represented by a
bar: the position and length of the bar reflects the start date, duration and end date of the
activity. This allows you to see at a glance.

21 | P a g e
Blood bank management

3.4 SOFTWARE AND HARDWARE REQUIREMENTS:

3.4.1 Software requirements:

 Operating System: Windows 7 or later

 Client: Google Chrome

 Front End: Visual Studio 2013 with Asp.net, C# Language, Bootstrap, Css

 Back End: Sql Express

3.4.2Hardware requirements:

 Processor: Intel Pentium and above

 RAM: 2 GB RAM

 Hard Disk: 100 GB

22 | P a g e
Blood bank management

3.5 CONCEPTUAL MODELS:

Spiral Model:

The spiral model is similar to the incremental development for a system, with more

emphasis placed on risk analysis. The spiral model has four phases: Planning, Design,

Construct and Evaluation. A software project repeatedly passes through these phases in

iterations.

The different phases are:-

 Planning:- This phase starts with the gathering of business requirements. In the

subsequent as the product matures, identification of system requirements and unit

requirements are done in this phase. This also includes understanding of system

requirements by continual communication between the customer and the analyst.

 Design:- Design phase starts with the design in the baseline spiral and involves

architectural. logical design of modules, physical product design and final design in the

successive spirals.

 Construct:- Construct phase refers to development of the final software product at

every spiral. In the spiral when the product is just thought and the design is being

developed, a Proof of Concept (POC) is developed in this phase to get the users'

feedback. Then in the successive spirals with higher clarity on requirements and design

a working model of the software called build is developed with a version number. These

versions are sent to the users for feedback.

23 | P a g e
Blood bank management

 Evaluation and Risk Analysis:- Risk analysis includes identifying observing technical

feasibility such as schedule slippage and cost over run.build, at the end of first After

testing building , user evaluates the software and provides the feedback Based on the

customer assessment, development process enters into the next iteration an afterwards

follows the linear approach to implement the feedback provided by the user. The

process of iterations along the spiral carries on with throughout the life of the software.

24 | P a g e
Blood bank management

CHAPTER4: SYSTEM DESIGN

4.1. Data Flow Diagrams (DFD):

A data flow diagram is graphical tool used to describe and analyse movement of data
through a system. These are the central tool and the basis from which the other components are
developed. The transformation of data from input to output, through processed, may be
described logically and independently of physical components associated with the system.
These are known as the logical data flow diagrams.
The physical data flow diagrams show the actual implements and movement of data
between people, departments and workstations. A full description of a system actually consists
of a set of data flow diagrams. Using two familiar notations Yourdon, Gane and Sarson notation
develops the data flow diagrams. Each component in a DFD is labeled with a descriptive name.
Process is further identified with a number that will be used for identification purpose.
The development of DFD'S is done in several levels. Each process in lower level
diagrams can be broken down into a more detailed DFD in the next level. The lop-level diagram
is often called context diagram It consists a single process bit, which plays vital role in studying
the current system. The process in the context level diagram exploded into other process at the
first level DFD.
The idea behind the explosion of a process into more process is that understanding a
tone level of detail is exploded into greater detail at the next level. This is done until further
explosion is necessary and an adequate amount of detail is described for analyst to understand
the process.
Larry Constantine first developed the DFD as a way of expressing system requirements
in a graphical from, this lead to the modular design.
A DFD is also known as a "bubble Chart" has the purpose of clarifying system
requirements and identifying major transformations that will become programs in system
design. So it is the starting point of the design to the lowest level of detail. A DFD consists ofa
series of bubbles joined by data flows in the system.

25 | P a g e
Blood bank management

LEVEL 0 –

26 | P a g e
Blood bank management

LEVEL 1 –

LEVEL 3 –

27 | P a g e
Blood bank management

4.2. DATA DESIGNS / UML DIAGRAMS

4.2.1. DATA INTEGRITY AND CONSTRAINTS:

The Primary-Key Constraint:

The primary key constraint designates a column, or a combination of columns, as the

primary for the table. This action enforces entity integrity, which requires each row to have a

unique identifier, so that data modifications or queries always refer to a specific row without

ambiguity. When you place a primary key constraint on a column, you’re requiring each row

in that column to have a unique value, which can’t be NULL. A primary key constraint on

multiple columns requires the combination of the values in those columns to be unique.

Examples of primary key include invoice number, employee ID, purchase order number and

item or part number.

The Foreign-Key Constraint:

The Foreign-key constraints defines the relationship between a column or combination

of columns in the current table and a column or combination of columns in another table. In

other words, it enforces referential integrity. This relationship might be one to one, such as in

the case of an employee in the payroll table who must already exist in the employees table. Or

it could be a many to one relationship. A typical example too many to one foreign-key

relationship is the Customer ID in the voices table.

28 | P a g e
Blood bank management

4.2.2 ENTITY-RELATIONSHIP DIAGRAM

The Entity-Relationship (ER) model was originally proposed by Peter in 1976 as a

way to unify the network and relational database views. Simply stated the ER model is a

conceptual data model that views the real world as entities and relationships. A basic

component of the model is the Entity-Relationship diagram which is used to visually

represent data objects. Since Chen wrote his paper the model has been extended today it is

commonly used for database design for the database designer, the utility of the ER model is:

 It maps well to the relational model. The constructs used in the ER model can easily

be transformed into relational tables.

 It is simple and easy to understand with a minimum of the training, Therefore, the

model can be used by the database designer to communicate the design to the end

user.

 In addition, the model can be used as a design plan by the database developer to

implement a data model in a specific database management software.

29 | P a g e
Blood bank management

Connectivity and Cardinality

The basic types of connectivity for the relations are: one-to-one, one-to-many and many-to-

many. A one-to-one (1:1) relationship is when at most instance of an entity A is associated

with one instance of entity B. For example, “employees in the company are each assigned their

own office. For each employee there exists a unique office and for each office there exists a

unique employee.

A one-to-many (1: N) relationships is when for one instance of entity A, there are zero, one,

or many instances of entity B, but for one instance of entity B, there is only one instance of

entity A. An example of a 1: N relationships is a department has many employees each

employee is assigned to one department.

A many-to-many (M:N) relationship, sometimes called non-specific, is when for one

instance of entity A, there are zero, one or many instances of entity B and for one instance of

the entity B there are zero, one or many instances of entity A. the connectivity of the

relationship describes the mapping of associated.

Notations of E-R Diagram:

There is no standard for representing the data objects in ER diagrams. Each modelling

methodology uses its own notation. The original notation used by Chen is widely used in

academics texts and journals but rarely seen in either case tools or publications by non-common

are Bachman, crow’s foot, and IDEFIX.

30 | P a g e
Blood bank management

All notational styles represent entices as rectangular boxes and relationships as lines connecting

boxes. Each style uses a special set of symbols to represent the cardinality of a connection. The

notation used in this document is from Martin. The symbols used for the basic ER constructs

are:

 Entities are the represented by labelled rectangles. The label is the name of the entity.

Entity names should be singular nouns.

 Relationships are represented by a solid line connecting two entities. The name of the

relationship is of the relationship is written above the line. Relationship names should

be verbs.

 Attributes when included, are listed inside the entity rectangle. Attributes which are

identifiers are underlined. Attribute names should be singular nouns.

 Cardinality of many is represented by a line ending in a crow’s foot. If the crow’s is

omitted, the cardinality is one.

 Existence is represented by placing a circle or a perpendicular bar on the line.

Mandatory existence is shown by the bar next to the entity for an instance is required.

Optional existence is shown by placing a circle next to the entity that is optional.

31 | P a g e
Blood bank management

32 | P a g e
Blood bank management

4.2.3 USE-CASE DIAGRAM

A Use Case Diagram at its simplest is a representation of a user's interaction with the

system that shows the relationship between the user and the different use cases in which the

user is involved. A use case diagram can identify the different types of users of a system and

the different use cases and will often be accompanied by other types of diagrams as well. The

use cases are represented by either circles or ellipses.

A Use Case is a methodology used in system analysis to identify, clarify, and

organize system requirements. A use case diagram contains four components.

 The boundary, which defines the system of interest in relation to the world around it.

 The actors, usually individuals involved with the system defined according to their roles.

 The use cases, which are the specific roles played by the actors within and around the

system.

 The relationships between and among the actors and the use cases.

33 | P a g e
Blood bank management

Basic Activity Diagram Notations and Symbols:

 System:

Draw your system's boundaries using a rectangle that contains use cases. Place actors

outside the system's boundaries.

 Use Case:

Draw use cases using ovals. Label the ovals with verbs that represent the system's

functions.

 Actors:

Actors are the users of a system. When one system is the actor of another system,

label the actor system with the actor stereotype.

 Relationships:

Illustrate relationships between an actor and a use case with a simple line. For

relationships among use cases, use arrows labeled either "uses" or "extends." A "uses"

relationship indicates that one use case is needed by another in order to perform a

task. An "extends" relationship indicates alternative options under a certain use case.

34 | P a g e
Blood bank management

35 | P a g e
Blood bank management

4.2.5 SEQUENCE DIAGRAM

Sequence diagrams describe interactions among classes in terms of an exchange of

messages over time. They're also called event diagrams. A sequence diagram is a good way to

visualize and validate various runtime scenarios. These can help to predict how a system will

behave and to discover responsibilities a class may need to have in the process of modeling a

new system.

Basic Sequence Diagram Notations

 Class Roles or Participants

Class roles describe the way an object will behave in context. Use the UML object

symbol to illustrate class roles, but don't list object attributes.

 Activation or Execution Occurrence

Activation boxes represent the time an object needs to complete a task. When an object

is busy executing a process or waiting for a reply message, use a thin gray rectangle

placed vertically on its lifeline.

36 | P a g e
Blood bank management

 Messages

Messages are arrows that represent communication between objects. Use half-arrowed

lines to represent asynchronous messages. Asynchronous messages are sent from an

object that will not wait for a response from the receiver before continuing its tasks.

For message types, see below.

37 | P a g e
Blood bank management

1.sequence diagram
Donor

donor location Institution feedback acknowledgment database

register himself/herself to the website

registered

view location

location viewed
search for blood bank query fired
institution viewed details fetched

give feedback feedback is stored

acknowledgment viewed
print acknowledgement

38 | P a g e
Blood bank management

sequence diagram

admin

admin Institute users feedback database

login

logged in

view institute
institute viewed
add institute Addinstitute
institution viewed Institutefetched

view users

return users
view feedback/users/institute
print feedback
/user/institute

39 | P a g e
Blood bank management

4.2. CLASS DIAGRAM

A class diagram is an illustration of the relationships and source code dependencies
among classes in the Unified Modelling Language (UML). In this context, a class defines the
methods and variables in an object, which is a specific entity in a program or the unit of code
representing that entity. Class diagrams are useful in all forms of object-oriented
programming (OOP). The concept is several years old but has been refined as OOP
modelling paradigms have evolved.

In a class diagram, the classes are arranged in groups that share common
characteristics. A class diagram resembles a flowchart in which classes are portrayed as
boxes, each box having three rectangles inside. The top rectangle contains the name of the
class; the middle rectangle contains the attributes of the class; the lower rectangle contains
the methods, also called operations, of the class. Lines, which may have arrows at one or both
ends, connect the boxes. These lines define the relationships, also called associations,
between the classes.

A class notation consists of three parts:

1. Class Name
 The name of the class appears in the first partition.
 A class represents a relevant concept from the domain, a set of persons,
objects, or ideas that are depicted in the IT system:

2. Class Attributes
 Attributes are shown in the second partition.
 The attribute type is shown after the colon.
 Attributes map onto member variables (data members) in code.
 An attribute of a class represents a characteristic of a class that is of interest
for the user of the IT system:

40 | P a g e
Blood bank management

3. Class Operations (Methods)

 Operations are shown in the third partition. They are services the class
provides.
 The return type of a method is shown after the colon at the end of the method
signature.
 The return type of method parameters is shown after the colon following the
parameter name.
 Operations map onto class methods in code

4. Class Relationship
 A class may be involved in one or more relationships with other classes. A
relationship can be one of the following types: (Refer to the figure on the
right for the graphical representation of relationships).
 Generalization is a relationship between two classes: a general class and a
special class:

41 | P a g e
Blood bank management

42 | P a g e
Blood bank management

4.2.7 COMPONENT DIAGRAM

Component diagrams are used in modelling the physical aspects of object-oriented
systems that are used for visualizing, specifying, and documenting component-based systems
and also for constructing executable systems through forward and reverse engineering.

Component diagrams are often drawn to help model implementation details and double-
check that every aspect of the system's required function is covered by planned development.
In the first version of UML, components included in these diagrams were physical: documents,
database table, files, and executables, all physical elements with a location.

Basic Component Diagram Symbols and Notations

Component
A component is a logical unit block of the system, a slightly higher abstraction than classes. It
is represented as a rectangle with a smaller rectangle in the upper right corner with tabs or the
word written above the name of the component to help distinguish it from a class.

Interface

An interface (small circle or semi-circle on a stick) describes a group of operations used

(required) or created (provided) by components. A full circle represents an interface created
or provided by the component. A semi-circle represents a required interface, like a person's
input.

43 | P a g e
Blood bank management

Dependencies

Draw dependencies among components using dashed arrows.

Port

Ports are represented using a square along the edge of the system or a component. A port is
often used to help expose required and provided interfaces of a component.

44 | P a g e
Blood bank management

4.2.8 ACTIVITY DIAGRAM

Activity diagram is another important diagram in UML to describe the dynamic

aspects of the system. Activity diagram is basically a flowchart to represent the flow from
one activity to another activity. The activity can be described as an operation of the system.

Basic Activity Diagram Notations and Symbols:

 Initial State or Start Point:

A small filled circle followed by an arrow represents the initial action state or the start
point for any activity diagram. For activity diagram using swimlanes, make sure the
start point is placed in the top left corner of the first column.

 Activity or Action State:

An action state represents the non-interruptible action of objects. You can draw an
action state in Smart Draw using a rectangle with rounded corners.

 Action Flow:

Action flows, also called edges and paths, illustrate the transitions from one action
state to another. They are usually drawn with an arrowed line.

 Object Flow:

Object flow refers to the creation and modification of objects by activities. An object
flow arrow from an action to an object means that the action creates or influences the
object. An object flow arrow from an object to an action indicates that the action state
uses the object.

45 | P a g e
Blood bank management

 Decisions and Branching:

A diamond represents a decision with alternate paths. When an activity requires a

decision prior to moving on to the next activity, add a diamond between the two
activities. The outgoing alternates should be labeled with a condition or guard
expression. You can also label one of the paths "else."

 Guards:

In UML, guards are a statement written next to a decision diamond that must be true
before moving next to the next activity. These are not essential, but are useful when a
specific answer, such as "Yes, three labels are printed," is needed before moving
forward.

46 | P a g e
Blood bank management

47 | P a g e
Blood bank management

4.3. PROCEDURAL DESIGN

Component level design also called procedural design occurs after data, architectural,

and interface design have been established.

What is it? Info, architectural, and interface style should be translated into operational software.

To accomplish this, the design must be represented at a level of abstraction that is close to code.

Component level design establishes: -

1. The algorithmic detail required to manipulate data structures.

2. Effect communication between software components via their interfaces, and

3. Implement the processing algorithms allocated to each component.

4. Who does it? A software program engineer performs component level design.

Why is it important? You have to be able to determine whether the program will work before

you build it. The component level style represents the software in a way that allows you to

review the details of the design for correctness and regularity with earlier design

representations. It provides a means intended for assessing whether data constructions,

interface and algorithms will continue to work.

What are the steps? Design representations of the data, architecture, and interfaces form the

foundation for component level style. The digesting narrative for each component is converted

into a procedural design model using a set of structured programming constructs. Graphical,

tabular or text-based notation is used to represent the look.

Approach is to represent the procedural style using some intermediate representation that can

be translated easily into source code.

48 | P a g e
Blood bank management

4.4 USER INTERFACE DESIGN

49 | P a g e
Blood bank management

4.5 SECURITY ISSUES

 User friendliness I provided in the website with various controls

 The system makes the overall project management much easier and flexible.

 It provides the security of page load without log in.

Personal facilities

 User/Donor can check their all information by insert the password

 Then Edit their details

 Update their information.

 No Remove/Delete option.

50 | P a g e
Blood bank management

4.6 TEST CASE DESIGN

The importance of the software testing and its impact on the software can not be

underestimated. Software testing is the key component of software quality assurance and is the

revision of specifications, design and coding. The increased visibility of the software system

and the code associated with software failure are motivating factors for planning, through

testing. It is not uncommon for software organization to spend 40% of its efforts on

experimentation.

Test Cases are derived to ensure that all statements in the program have been executed

atleast once during testing and that all logical conditions have been executed.

Using White-box testing methods, the software engineer can drive test cases that

 Guarantee that logical decisions on their true and false sides.

 Exercise all logical decisions on their true and false sides.

 Execute all loops at their boundaries and with in their operational bounds.

 Exercise internal data structure to assure their validity.

The test case specification for system testing has to be submitted for review before system

testing commences.

51 | P a g e