Top Banner
PROJECT REPORT ON BLOOD BANK MANAGEMENT SYSTEM IN Partial fulfillment of Bachelor of Business Administration Degree in Computer Aided Management, BBA(CAM) Submitted to: Submitted by: Mr. Gurjeet Singh Kanan Gupta (0081211908) (Project Guide) Session: 2008-2011
64

Kanan Project File

Oct 15, 2014

Download

Documents

'Kanan Gupta
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Kanan Project File

PROJECT REPORT

ON

BLOOD BANK MANAGEMENT SYSTEM

IN

Partial fulfillment of Bachelor of Business Administration Degree in Computer Aided Management, BBA(CAM)

Submitted to: Submitted by:Mr. Gurjeet Singh Kanan Gupta (0081211908) (Project Guide) Session: 2008-2011

Guru Gobind Singh Indraprastha University

DAV Institute of ManagementNH-3, NIT, Faridabad, Haryana

Phone no.: 0129-4270837

Page 2: Kanan Project File

Acknowledgement

Completing a task is never one man effort. It is often the result of invaluable

contribution of number of individuals in a direct and indirect manner that

helps in sharing and making success.

I take this opportunity to express my deep sense of gratitude and whole

hearted thanks to my guide Mr. Gurjeet for his valuable guidance and

taking keen interest in me and encouraging me throughout the project.

We take this opportunity to all those who have directly and indirectly helped

me during the course of this task.

CONTENTS

Page 3: Kanan Project File

Serial No. Name of Topic Page No.

1. CHAPTER-1INTRODUCTION

1.1 Introduction about Project

1.2 Present state of Art1.3 Need for

Computerization1.4 Scope of System

2. CHAPTER-2PROJECT CATEGORY TOOLS & ENVIORNMENT2.1 Project Category2.2 Choice of Platform 2.2.1 - Software Used2.2.2 - Hardware Used

3. CHAPTER-3PROJECT DEVELOPMENT STAGES3.1 System Investigation3.2 Feasibility Study3.3 Analysis3.4 Design3.5 Development3.6 Implementation

&Testing

4. CHAPTER-4PROJECT FORMS

Page 4: Kanan Project File

5. CHAPTER-5CODING

6. CHAPTER-6FUTURE SCOPE

7. CHAPTER-7BIBLIOGRAPHY

8. CHAPTER-8CONCLUSION

Page 5: Kanan Project File

1.1 INTRODUCTION ABOUT THE PROJECT:

Page 6: Kanan Project File

The term "Blood bank" typically refers to a division of a hospital laboratory

where the storage of blood product occurs and where proper testing is

performed to reduce the risk of transfusion related events. This includes

compatibility testing for transfusion and may include blood donation

processing, depending on the capabilities of the facility.

Because blood availability in Blood Banks is relatively less as compare to

requirement so, to promote this various blood banks organize the blood

donation activities in blood camps. Besides maintaining the records of

various donors, hospitals and blood bank issue registration form which is to

be filled by donor and as well as by recipient. Hence it becomes complex to

maintain all the records manually.

Therefore, need was felt for the computerized Blood Bank Management

System. In order to use this software we have used Visual Basic 6.0 as

front end and Ms-Access 7.0 as back end. It is an attempt to relieve the

burden of manual system by providing fully automated and secure system.

The functioning, which this system provides is: maintaining the records of

blood donors and recipients, availability of blood in the blood bank. The

password system check allows only the authorized person to use the system

in order to maintain the security of the system.

1.2 PRESENT STATE OF ART:

Page 7: Kanan Project File

Computer is served as tool for managing information. Almost all big

organizations are switching towards computerization, as the jobs are

voluminous and repetitive in nature.

India has many blood banks, all functioning in a decentralized fashion. In

the current system, there is no tool to find number of blood donors of the

required blood group in current time and place, there is no interaction

between blood banks, no exchange of blood or its components, or best

practices. In order to explore all these issues an efficient blood bank

management system (BBMS) is required.

Blood Bank Management Software, is readily scalable and adaptable to meet

the complex need of Blood Banks , who are key facilitator for the Healthcare

Sector, it also supports all the functionalities of Blood Bank.

EARLIER SYSTEM NEW SYSTEM

Manual system Implemented with Visual

Basic 6.0 and Ms-Access 7.0

1.3 NEED FOR COMPUTERIZATION:

Page 8: Kanan Project File

TIME SAVING:

Using computers can save a lot of time. This is possible, as computers are

fast, efficient and more accurate as compared to human beings.

QUICK REPORTS:A computerized system can help on generating different types of reports.

This can be done easily by merely pressing few keys. Reports can be easily

obtained whenever needed.

MUCH MORE DETAILS AVAILABLE:

A large amount of details can be obtained easily in a computerized system

which otherwise can’t be available in a manual system.

EFFICIENT & ACCURATE:

Computerization will increase the efficiency and accuracy of the service

station administration in maintaining records.

FASTER & EASIER DATA RETRIEVAL:

By using computerized system data can be retrieved at much faster pace. Old

records can be located immediately and easily.

ECONOMICAL:

Page 9: Kanan Project File

Due to computerization more accurate functioning can be obtained as

compared to manual systems in long term.

DECREASED NUMBER OF PEOPLE:

Computerization will decrease manpower dependence. After automation

only one person will be needed where as in manual system two or three are

required.

1.4 SCOPE OF THE SYSTEM

The system named “Blood Bank Management System” is designed for

proper and smooth functioning of different operations that takes place in

Blood Bank.

The main integrities of Blood Bank Software are:

Generating reports on Stocks-Blood Group wise, Area wise and

Expiry date wise.

Donor Database-Blood Group wise and Area wise

Maintain and update Unique Donor Identifications.

Track And maintain all the Donor Types-Regular as well as

emergency case donors

Improve the Effectiveness and efficiency of Blood Bank-Faster

Response Time and Better Control

Accurate database/Record Management.

Blood Cross Match and Result Storage Facility.

Searched Facility for Destroyed and Expired Blood

Comprehensive Donor database

Page 10: Kanan Project File

Unique Donor Id and Patient record Id for managing future list.

Improve Blood Bank processes by providing efficient and continuous

software support.

Besides this, there are certain loopholes of manual handling in Blood Bank

Handling the records related to Donors and Recipients

Maintaining the staff records, if someone is recruited or left out.

Maintaining the stock record, because it becomes very difficult to

make the changes in quantities of the blood groups that are available.

To overcome all these difficulties we made a sincere effort to develop a

project which made searching and manipulation jobs easy.

The new system has edge over the previous system in accuracy, reliability to

human error, which are detected by validation checks. The new system is

easy to implement because of its adaptability, versatility and easy to

comprehend.

This project can be further helpful in online enquiries regarding blood

donation.

Page 11: Kanan Project File

2.1 PROJECT CATEGORY:

This project is based on the theory of Database Management

System(DBMS).We use Access as a DBMS tool.

Page 12: Kanan Project File

2.2 CHOICE OF PLATFORM:

2.2.1 Software:

The selection of software involves two major decisions namely:

Selection of Front-End

Selection of Back-End

As the client stressed on the user-friendly and windows based product,

Visual Basic was the appropriate choice for the Front-End. For the Back-

End, I have use MS-Access.

Since this is readily available in all the blood banks. Despite the above

specific requirements, based on our learning’s, we can complete this project

using other languages C, C++ etc. and databases like Oracle etc. incase

adequate time and resources are available.

What is Visual Basic?

Visual Basic is a professional application development tool executing in

windows environment that allows professional programmers to build

sophisticated, graphical applications with access to data information stored.

This is what Visual Basic all about…

What is Event- Driven Programming?

Page 13: Kanan Project File

One of the biggest and first adjustments for a programmer to make in

moving from DOS or mainframe based procedural programming to windows

is the concept of Event-Driven Programming.

In the Event-Driven Programming the user is in complete control of the flow

of processing, there is no predefined path. Event-Driven Programming not

only allows deviation from predefined path, it is built on.

Front End and Back End Tools

The concept of front end and back end has been chosen to develop this

software as this suits the DBMS architecture to its full potential. Visual

Basic used as the front end, and any relational package (that supports

tables) is used at the back end.

Microsoft Access

It is a database management system or DBMS. A DBMS helps to manage

data that’s stored in a computer database. It is a full-featured application

development system that includes the Visual Basic.

Programming language and other tools for setting up sophisticated

applications for yourself and your customers.

Microsoft Access is designed from the ground up to provide full support for

all window features.

2.2.2 Hardware:

Page 14: Kanan Project File

The minimum hardware configuration for the implementation of this

software product is:

PROCESSOR: Intel Cerelon M Processor 410(1MB)

MEMORY : 160GB

HARD DISK : 80GB

RAM : 512MB

COMPACT DISK : 700MB

KEYBOARD : 106 Keys

MONITOR : 154” WXGA High Definition bright view widescreen

PRINTER : HP INKJET 2100 Series

MOUSE : 2 Buttons and Scroll

PEN DRIVES : 4GB, 2GB

Hardware Interface Requirements:

Our product will require Windows XP and color display.

Other Software Components:

Operating System: Windows XP/Vista/2007

Performance Requirements:

Page 15: Kanan Project File

The software is inherently designed to handle five users accessing the

database one at a time. Since the blood bank is a small size organization

therefore, this software is designed at a user level (i.e., in a horizontal level)

Page 16: Kanan Project File

The stages of project development are:

1. System Investigation

Page 17: Kanan Project File

2. Feasibility Study

3. Analysis

4. Design

5. Development

6. Implementation and Testing

FEASIBILITY STUDY

The concept of feasibility is to determine whether or not a project is worth

doing. The process followed in making this determination is called

feasibility study. Once it has been determined that a prpject is feasible, the

system analyst can go ahead and prepare the project specifications which

finalizes project requirements.

Types of feasibility

1. Technical Feasibility

2. Operational Feasibility

3. Economic Feasibility

4. Social Feasibility

5. Management Feasibility

6. Legal Feasibility

7. Time Feasibility

Here we describe only few of them in detail:-

Page 18: Kanan Project File

TECHNICAL FEASIBILITY

This is concerned with specifying equipments and software that will

successfully satisfy the user requirement. Technical needs of the system

include:

Facility to produce outputs in a given time

Response time under certain conditions

Ability to process a certain volume of transaction at a particular

period

Facility to communicate data to distant location.

In examining technical feasibility, configuration of the system is given more

importance. Configuration should give the complete picture about the

system’s requirements. What speeds of input and output should be achieved

at particular quality of printing.

The software needed to carry out this project include Visual Basic 6.0 as

front end and Ms-Access 7.0 as back end. So, the technology required

carrying out the project is easily available and affordable, hence the project

is Technically feasible.

Due to all these reasons implementations of such systems becomes not only

feasible but reputed to the organization.

OPERATIONAL FEASIBILITY

Page 19: Kanan Project File

This is mainly related to human organization and political aspects. The

points to be considered are:-

What changes will be brought with the system?

What organizational structure is decided?

What new skills will be required? Do the existing staff members have

these skills or they have to be trained in due course of time?

This feasibility study is carried out by a small group of people who are

familiar with information system techniques, who understand the parts of

business that are relevant to the project and are skilled in a system analysis

and design process. This project is developed on demand of the organization

for which the system is being developed. The time required to carry out the

transaction will be reduced to a large extent, which will make the student

comfortable. The operators now will be able to service more students than

before in the same time period. There is no need to recruit new staff to

operate the system. The existing staff of the institute can be trained to

interact the system which is GUI based software and is easy to use. Hence,

the project is Operationally feasible.

ECONOMIC FEASIBLILITY

Economic analysis is the most frequently used technique foe evaluating the

effectiveness of a proposed system. Commonly known as Cost-Benefit

Analysis, the procedure is to determine the benefits and savings that are

expected from a proposed system and compare them with costs.

Page 20: Kanan Project File

Cost Benefit Analysis

Cost plays an important role in deciding the new system; it must be

identified and estimated properly. Benefits are also of different types and

can be grouped on the basis of advantages they provide to the management.

Cost saving benefit leads to reduction in administrative and operational

costs. Cost avoidance benefits eliminate future administrative and

operational costs. Improved service level benefits are those where the

performance of the system is improved by a new computer based method.

Improved information benefits are where computer based methods lead to

better information for decision making.

Direct or Indirect Costs and Benefits

Direct costs are those which are directly associated with a system. They are

applied to the operator.

Direct Benefits can be specifically attributed to a given project.

Indirect Costs are not directly associated with a specific activity in the

system. They are often referred to as overhead expenses.

For example: cost of space to install a system, maintenance of computer

center, heat, light, air-conditioning are all tangible costs but their proportion

is difficult to calculate to a specific activity like report.

Page 21: Kanan Project File

Therefore we can define cost-benefit analysis as:

1. That method by which we can find and estimate the value of the gross

benefits of a new system specification.

2. That method by which we can find and determine the increased

operating costs associated with gross benefits.

3. The subtraction of these operating costs from the associated gross

benefits to arrive at net benefits.

4. That method by which we find and estimate the monetary value of the

development costs that produce the benefits.

5. Those methods by which we show the time relationship between net

benefits and development costs as they relate to cash flow, payback on

investment, and time in process taking into operation factors such as

inflation etc.

DESIGN

It is a highly creative phase which focuses on how to make software.

Software design is an iterative process through which requirements are

translated in to a “blue print” for constructing the software. Certain issues

are kept in mind while designing software:

It should fulfill the user’s requirement

It’s performance must be reliable

The software should be easy to understand

It must be verifiable in testing phase

It should hold consistency

It must be easy to operate

There are certain objectives of software design phase. These are:

Page 22: Kanan Project File

1. Produce the best possible design keeping in view the limitations

imposed by requirements.

2. Produce a solution of the problem given in software requirement

specification document that is as per the user’s demand.

3. Design must provide mass data and relevant data.

4. Design should such that it makes access to data easy for user.

5. It should provide prompt responses to users request for data.

6. Design should be such that, it makes latest modifications to database

available immediately.

7. Design should be flexible enough to allow for growth in database

system.

8. Design should protect data from physical harm and unauthorized

access.

DATA FLOW DIAGRAMS

It is one of the tools for structured analysis. They are diagrams which depict

the flow of data through the system and express system requirements in a

graphical form. It is also known as bubble chart or work flow diagram.

There are certain objectives to prepare DFD’s. These are:

To provide hierarchical breakdown of the system.

To show what files are used and where the result flows.

To document the information flow in the system.

Page 23: Kanan Project File

To illustrate the essential components of the system or process and the

way they interact.

To provide an overview of what data a system would process.

Because Data Flow Diagrams are easy to use, simple to understand and the

graphical representation is a good communication tool between user and

analyst I choose this tool in my project.

SYMBOLS MEANING

Process or Function

Flow of Data

External or Internal Entity

Page 24: Kanan Project File

File stored in memory

DFD OF BLOOD DONOR

DONOR

Page 25: Kanan Project File

Go through records

Verifying 1 BBMSD001

If unregistered Then

View

DFD OF BLOOD RECIPIENT

Search

Add and Fill new form

RECIPIENT Submit

Page 26: Kanan Project File

Fill Update

Show 1 BBMSR001

DFD OF INVENTORY

Search

Blood TransFusion

DONOR ID

Page 27: Kanan Project File

INVENTORY

Through records

1 BBMSS001

Add 1 units Update Less 1 units

Update

Display

Donated Blood

Transfused Blood

Page 28: Kanan Project File
Page 29: Kanan Project File
Page 30: Kanan Project File
Page 31: Kanan Project File
Page 32: Kanan Project File

FORM DESIGNS

We know that the form provide the basis for information systems. Without

data there is no system, but data must be provided in the right form so that

the information produced must be in a format acceptable to the user.

Page 33: Kanan Project File

It is a tool with message. It is a physical carrier of data and information.

IMPLEMENTATION

Once the design is complete, most of the major decisions about the system

have been made. The goal of the implementation phase is to translate the

design of the system into code in a given programming language. For a

given design, the aim in this phase is to implement the design in the best

possible manner.

The implementation phase affects both testing and maintenance profoundly.

Well-written code can reduce the testing and maintenance effort. Because

the testing and maintenance cost of the software are much higher than

coding cost, the goal of the coding should reduce the testing and

maintenance effort. Simplicity and clarity should be strived during the

implementation phase.

The concept of structured programming should be adopted. The goal of

structured programming is to simplify the control flow in program. The

program text should be organized as a sequence of statements and during

execution the statements are executed in sequence given in the program.

TESTING

Page 34: Kanan Project File

Testing is the major quality control measure during software development.

Its basic function is to detect in the software. After the implementation

phase, computer programs are available that can be executed for testing

purpose. The goal of testing is to uncover requirements, design and coding

errors in the program. Consequently different level of testing are used,

namely:

1. Unit Testing

2. Integration Testing

3. System Testing

4. User Acceptance Testing

There are certain objectives of testing phase:

To ensure that the software is reliable and working as per the

specifications.

To ensure that the software is according to the requirements of the

user.

To deliver high quality software product.

MAINTENANCE

The maintenance phase is the last phase of the software development life

cycle. Yet, a life cycle is a circular in that the last activity leads back to the

first. This means that the process of maintaining an information system is

Page 35: Kanan Project File

the process of returning to the beginning of the software development life

cycle and repeating steps until the change is implemented.

Four major activities occur within maintenance:

Obtaining maintenance requests

Transforming requests into changes

Designing changes

Implementing changes

Obtaining maintenance request requires that a formal process be established

whereby user can submit software change request. Most companies have

some sort of document to request new development, to report problem, or to

request new software features.

Once a request is received, analysis must be conducted to gain an

understanding of the scope of the request. It must be determined how the

request will affect the current software and duration of such project. Next,

Change request can be transformed into a formal design change, which can

then be fed into the maintenance implementation phase.

There are several types of maintenance:

1. Corrective Maintenance

It refers to the changes made to repair defects in the design, coding, or

implementation of the software. Most corrective maintenance

Page 36: Kanan Project File

problems surface soon after installation. When corrective maintenance

problem surface, they are typically urgent and need to be resolve to

curtail possible interruptions in normal business activities.

2. Adaptive Maintenance

It involves making changes to an information system to evolve its

functionality to changing business needs or to migrate it to different

operating environment. Contrary to corrective maintenance, adaptive

maintenance is generally a small part of a n organization’s

maintenance effort but does add value to the organization.

3. Perfective Maintenance

It involves making enhancement to improve processing performance,

interface usability, or to add desired, but not necessarily required

system features.

4. Preventive Maintenance

It involves changes made to software to reduce the chance of future

system failure. Preventive maintenance might be used to increase the

number of records that software can process far beyond what is

currently needed.

Page 37: Kanan Project File
Page 38: Kanan Project File

CODING OF SPLASH FORM

Option Explicit

Private Sub Form_KeyPress(KeyAscii As Integer) Unload MeEnd Sub

Private Sub Timer1_Timer() Static ictr As Integer 'Run the timer and check the condition

Page 39: Kanan Project File

'when the condition is false 'stop the timer and disply the login form If ictr <= 100 Then ProgressBar1.Value = ictr ictr = ictr + 1 Else frm_login.Show 'frmLogin.Show Unload Me End IfEnd Sub

CODING OF LOGIN PAGE

Private Sub ABOUT_BBMS_Click()frm_about.ShowEnd Sub

Private Sub CHANGE_PASSWORD_Click()frm_chg_pwd.ShowEnd Sub

Private Sub Command1_Click()frm_donor1.ShowEnd Sub

Private Sub Command2_Click()frm_recform.ShowEnd Sub

Private Sub EXIT_Click()

Page 40: Kanan Project File

'This block of code will be executed if the user decides to quit the application 'from the Login page Dim ans As Variant ans = MsgBox("Are You Sure You Wish To Quit The Application?", vbYesNo + vbQuestion, "Quit Application?") If ans = vbYes Then End End If

End Sub

Private Sub INVENTORY_Click()frm_inv.ShowEnd Sub

Private Sub form_load()Combo1.AddItem ("A+")Combo1.AddItem ("A-")Combo1.AddItem ("B+")Combo1.AddItem ("B-")Combo1.AddItem ("AB+")Combo1.AddItem ("AB-")Combo1.AddItem ("O+")Combo1.AddItem ("O-")Label8.Caption = "Date :" & FormatDateTime(Now, vbLongDate)End Sub

CODING OF DONOR FORM

Private Sub Command1_Click()Adodc1.Recordset.Update

Page 41: Kanan Project File

frm_donor2.ShowEnd Sub

Private Sub Command2_Click()Adodc1.Recordset.AddNewEnd Sub

Private Sub Command3_Click()Adodc1.Recordset.DeleteEnd Sub

Private Sub Form_Load()Label2.Caption = "Date :" & FormatDateTime(Now, vbLongDate)

End Sub

Private Sub Command1_Click()Adodc1.Recordset.AddNewEnd Sub

Private Sub Command2_Click()Adodc1.Recordset.Updatefrm_main.ShowEnd Sub

Private Sub Command3_Click()frm_donor1.ShowUnload MeEnd Sub

Private Sub Command4_Click()Adodc1.Recordset.Delete

End Sub

CODING OF RECIPIENT FORM

Private Sub Command1_Click()

Page 42: Kanan Project File

Adodc1.Recordset.DeleteEnd Sub

Private Sub Command2_Click()Adodc1.Recordset.UpdateEnd Sub

Private Sub Command3_Click()Adodc1.Recordset.AddNewEnd Sub

CODING OF INVENTORY FORM

Private Sub Command1_Click()Dim y As Integery = Text2.TextText2.Text = y + 1Adodc1.Recordset.UpdateEnd Sub

Private Sub Command10_Click()Dim y As Integery = Text2.TextText2.Text = y - 1End Sub

Private Sub Command11_Click()Dim y As Integery = Text3.TextText3.Text = y - 1End Sub

Private Sub Command12_Click()Dim y As Integery = Text1.TextText1.Text = y - 1End Sub

Page 43: Kanan Project File

Private Sub Command13_Click()Dim y As Integery = Text5.TextText5.Text = y - 1End Sub

Private Sub Command14_Click()Dim y As Integery = Text6.TextText6.Text = y - 1End Sub

Private Sub Command15_Click()Dim y As Integery = Text7.TextText7.Text = y - 1End Sub

Private Sub Command16_Click()Dim y As Integery = Text8.TextText8.Text = y - 1End Sub

Private Sub Command17_Click()Dim y As Integery = Text9.TextText9.Text = y - 1End Sub

Private Sub Command2_Click()Dim y As Integery = Text3.TextText3.Text = y + 1End Sub

Private Sub Command3_Click()Dim y As Integery = Text1.TextText1.Text = y + 1

Page 44: Kanan Project File

End Sub

Private Sub Command4_Click()Dim y As Integery = Text5.TextText5.Text = y + 1End Sub

Private Sub Command5_Click()Adodc1.Recordset.UpdateUnload Mefrm_main.ShowEnd Sub

Private Sub Command6_Click()Dim y As Integery = Text6.TextText6.Text = y + 1End Sub

Private Sub Command7_Click()Dim y As Integery = Text7.TextText7.Text = y + 1End Sub

Private Sub Command8_Click()Dim y As Integery = Text8.TextText8.Text = y + 1End Sub

Private Sub Command9_Click()Dim y As Integery = Text9.TextText9.Text = y + 1End Sub

Private Sub Form_Load()

Page 45: Kanan Project File

End Sub

The scope of future application of BBMS is:

Page 46: Kanan Project File

A large Blood Bank Database can be accommodated in our

application in the future.

In emergency cases patient will not have to wait for immediate blood

transfusion.

Blood recipients can place order for blood.

As requirement of blood is increasing day by day, Blood Bank play a

very crucial role by issuing blood anytime and anywhere by

introducing MOBILE BLOOD BANKS.

Page 47: Kanan Project File

At last we conclude that this project can help all the staff members of any

blood bank. This project work as not a major part of any blood bank, but it

helps in removing the complexities and sorting the records more efficiently.

This will reduce the burden of maintaining the records manually.

Page 48: Kanan Project File

VISUAL BASIC 6.0 ANURADHA AGGARWAL

BLACK BOOK OF VISUAL BASIC

SOFTWARE ENGINEERING PANKAJ JALOTE