Blood Bank Management Final (1)

7/27/2019 Blood Bank Management Final (1)

1/32

1. INTRODUCTION

1.1 ABOUT THE PROJECT

The project entitled BLOOD BANK MANAGEMENT SYSTEM has been

developed to computerize the manual work involved in the college admission. This project is

aimed to provide all the required information and to reduce the work overhead in the college.

` is the most complex of all the programs in the system and has concomitantly undergone

more revisions than any other. To accomodate all the events that can involve a blood product, a

system was developed to code these events and store their transaction date, as an offset of the

date of receipt of the blood product. Transaction types were divided into those which involved

patients versus those which did not. They were also divided into those which were "final"

transactions and non "final" transactions.

All patient-related transactions have a presumed crossmatch or set-up associated with

them. After that, three events are possible: 1) the product is issued to the patient, 2) the product

is released for reuse, or 3) the product is wasted (no longer usable).

If a unit is issued, however, it may be either used by the patient, wasted (at the nursing

station), or returned to the Blood Bank for reuse. In the last instance the unit may be reissued

and the same follow-up events are possible as above. If the unit is issued and used the issue

time is saved in computer storage.

1


2/32

1.2 SYSTEM SPECIFICATION

1.2.1 HARDWARE CONFIGURATION

The physical components of the computer such as electrical, electronic and mechanical

units are known as the hardware of computer (i.e.). The input unit, output unit and central

processing unit, (CPU) are called as hardware. Thus hardware is the equipment involved in the

functioning of a computer. It consists of the components that can be physically handed. The

selection of hardware configuration is very important task relating to the software development

and running of the software.

The configuration given below is the hardware for the system development.

Processor : 2.66GHZ

Ram : 256MB

Hard Disk : 40GB

Monitor : 14 Samsung CRT monitor

Mouse : Zebronic

Key board : standard 101/102 key ps/2 keyboard

1.2.2 SOFTWARE SPECIFICATION

The configuration given below is the software handled for the system development.

Operating system : Windows XP

Front- End : Visual Basic 6.0

Back-End : MS Access

1.3.1 SOFTWARE DESCRIPTION

Visual Basic 6.0

2


3/32

Visual Basic is a Windows programming language that has been developed at Microsoft

Corporation in 1982. Visual Basic is a powerful programming language to develop sophisticated

windows programs very quickly and event-driven programming. Visual Basic is one of this RAD

(Rapid Application Development) tools as it enables the programmer to develop applications

very easily and very quickly.

The Visual part refers to the method used to create the Graphical User Interface (GUI).

Rather than writing numerous line of code to describe the appearance and location of interface

elements, simply add pre built object into place on screen. The Basic part refers to the BASIC

language, a language used by more programmers than any other language in the history of

computing.

Visual Basic EditionVisual Basic software comes in three editions:

Learning Editions : which includes the Visual Basic development environment and use of

standard tools to develop applications

Professional Edition : is used by computer professionals as it supports the tools to develop

ActiveX and Internet controls

Enterprise Edition: which includes all the features of professional edition well as

Microsoft Visual Source safe for source code control and Automation and Componentmanager

Visual Basic 6.0

Version 6.0 of Visual Basic is specially designed to utilize the internet. It comes with

several controls that allow user to create web-based application called ActiveX executables.

Additional features

1. OLE Automation is an industrial standard technology that application uses to expose their

OLE objects to development tools, macro language, and other application that support

OLE Automation.

2. To distinguish Visual Basic project files from source files used by other development

tools, the file extension. VBP used.

3


4/32

3. Object Browser is used for hierarchal display of classes, properties, and methods

available to the application.

4. The 32-bit version of Visual Basic supports long files names.

5. programmers can define classes, which are contained in Visual Basic class module. Class

module is the one, which contains the definition of class; its properties and definition.

6. Enhanced Object Browser, Auto list numbers features and auto quick information feature

is also provided.

7. ActiveX is a new buzzword that refers to technologies that previously may have been

associated with the term OLE. ActiveX is Microsofts name for technologies that are

based on the Component Object Model (COM).

8. Visual Basics internet capability allows one to create powerful applications hosted by

standard browser. Visual Basic as a front-end tool

Visual Basic is Windows application development platform with a strong combination of

a front-end tool and programming language .The ease of the visual approach coupled with the

power of programming and the straightforward BASIC language syntax makes programming

easy. By using visual Basic, the programmer can create powerful, full feature application that

exploit the key feature of MS Windows, including Multiple Document Interface (MDI) , Object

Linking and Embedding (OLE), Dynamic Data Exchange (DDE), graphics and many more.

Visual Basic can be extended by adding custom controls and by calling procedure in Dynamic

Link Libraries (DLLs).

Using MDI in Visual Basic:

MDI stands for Multiple Document Interface. Visual Basic application can have only one

MDI form. A child form is an ordinary form that has its MDI-Child property set to true. The

application can include MDI-Child forms. At run time, child forms are displayed within the

internal areas of MDI form. When a child form is minimized, its icon appears on the MDI form

instead of appearing on the desktop.

Element of Visual Basic

Visual Basic interface consists of the following elements.

4


5/32

Toolbar

Provides quick access to commonly used commands in the programming environment. An

icon in the toolbar can be clicked to carry out the action represented by that icon.

Toolbox

Provides as set of tools that can be used at design time to place controls on a form.

Menu bar

Displays the commands that can be used to build an application.

Form

Serves as a window that can be used to customize the interface of an application.

Controls, graphics and pictures can be added to a from to create the Visual effect required by the

user.

Project Window

Lists the dow form, code, modules and custom control files that make up the current

project. A project is the collection of files that a programmer uses to build up his application.

Total number of controls

The maximum number of controls allowed on a single form up to 254. The limit control

array index is 0 to 32,767 on all versions.

MS-ACCESS (Back-End Tool)

Ms-access is a powerful multi user relational database managements system developed

by Microsoft used to implement large amount of information with minimum memory allocation

and auto make repetitive task, such as maintaining and generating invoice. Data in ms-access is

organized in the form of tables within a table records are arranged to a common reference value

known as primary key.

FEATURE OF MS-ACCESS

Access is window based application and therefore it has an interface similar to

windows.

Access maintains a single disk file for a database and all its associated objects.

Access lets you import from or export to foxpro, oracle and other data form.

5


6/32

Access wizard is a vitality that helps to perform complex task by guiding

through out the access. Access contains nearly hundred.

Wizards to design database application, tables, forms, reports, graphs, mailing

labels, control and properties.

ADVANTAGES OF MS ACCESS:

Less time consumption and quick response.

Access has a friendly environment.

Microsoft access is not needed for keeping register for recording.

DISADVANTAGES OF MS ACCESS:

The data security is very less. The database would not be opened.

No availability of temporary tables.

6


7/32

2. SYSTEM STUDY

System study is for finding out what happens in existing system deciding on what changes

and new features are required and defining exactly what the proposed system must be. The

process of system analysis is largely concerned with determining, developing and agreeing to the

users requirements. It provides prime opportunity to communicate well with the user and

conceive a joint understanding of what a system should be doing together with a view of relative

importance of the system facilities using interactive techniques.

2.1 EXISTING SYSTEM

There are certain features limiting the process of the present system.The drawbacks of the present system are listed below.

The increase in number of vehicles now a days

The increase in number of accidents now a days

The patients cannot get the information of donors easily

2.1.1 DRAWBACKS

The present system has following limitations:

Limitations in report generations

Manual recording consumes excess time

Chances of error

Difficulty in allocating cabins

The retrieval of information regarding a client is time consuming

Lack of billing system and manual calculation of daily income Repeated recording of frequent user details

7


8/32

2.2 PROPOSED SYSTEM

The proposed system, Online Blood Bank site overcomes the drawbacks of the presentsystem. The Blood Bank helps the people who are in need of a blood by giving them overall

details regarding the donors with the same blood group and with in their city.

The advantages of the proposed system are listed below.

The people in need of blood can search for the donors by giving their blood group and

city name.

It is very flexible and user friendly.

The persons time and work is reduced very much which prevails in the present system. Easy and Helpful

The people are not limited to receive or provide services in working hours of the branch

only; he is serviced 24 hours a day, 7 days of week and 365 days of the year.

In this project the searching can be done for donors for majority of cities but not for every

city.

In this project the contact persons details are given for the limited cities only.

2.2.1 FEATURES 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.

Complete Key Consumables Inventory Management.

Track And maintain all the Donor Types-Voluntary,Exchange and Directed.

Improve the Effectiveness and efficiency of Blood Bank-Faster Response Time andBetter Control

Accurate database/Record Management.

Blood Cross Match and Result Storage Facility.

8


9/32

Digital Record archival backup and restoring facility-Better House keeping and Record

Maintenance. Rejected Donor Database for Donor Control and Identification-Blood Transfusion related

disease control and prevention

Searched Facility for Destroyed and Expired Blood

Comprehensive Donor database with Search Facility.

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

Improve Blood Bank processes by providing efficient and continuous software support.

9


10/32

3. SYSTEM DESIGN AND DEVELOPMENT

3.1 FILE DESIGN

The system design focuses on data base design, architectural design, interface design and

procedural design. In general there are two types of design structure. The first one assesses thetranslation of requirements to the design of data architecture. The second one called a design

walk through, concentrates on the procedural correctness and algorithms as they are

implemented with in the program modules.

The system begin with the software requirement specification. The specification

describes the features of the system, the components and elements of the system and how it will

be useful to the user. The term design describes the aspects of the final system. The system

gets the input through the relational data base and store it in the data bases and outputs are given

as per the requirements of the user. An integrated solution for complete computerization for

College, build on the most futuristic and highly sophisticated ASP.Net environment, denoted as

College Admission Management System. The solution has been implemented in many prominent

and reputed Colleges.

10


11/32

3.2 INPUT DESIGN

Input design is one of the most expensive phases of the operation of computerized system

and is often the major problem of a system. A large number of problems with a system can

usually be tracked back to fault input design and method.

Input design should be analyzed with utmost care and consideration. The decision made

during input design is to provide cost effective method of input.

Input data of a system may not be necessarily in the form of raw data captured in the

system from scratch. These can also be the output of another system or sub system.

Screen design is a part of overall system design, which requires careful attention. Themajor objective of the screen design is to make the data entry easy, logical and free from errors,

logical and easy. A good screen requires complete fact-finding, careful design and rigorous

testing. Screen design both input and output.

REQUIREMENTS OF SCREEN DESIGN

IDENTIFICATION AND WORKING

The screen title should clearly identify its purpose. The screen should also be identified

by the screen name.

MAXIMUM READBILITY AND USE

The screen must be easy to use and fill out. It should be legible and enough space must be

provided for inserting data.

PHYSICAL FACTORS

The screens composition, color, layout should be attractive.

11


12/32

3.3 OUTPUT DESIGNOutput design generally refers to the results and information that are generated by the

system for many end users. Output is the main reason for developing the system and the basis

with which usefulness of the application is evaluated.

REPORTS

Depending on the input given, various reports are generated, like.

Blood Donor details

Registration

Login

BloodHelp Line

Services

3.4 DATABASE DESIGN

This procedural design has been completed after the data and architectural design.

Procedures specify what tasks must be performed in using the system and who is responsible for

carrying out. There should be methods for capturing transactions data and entering it into theinformation system, such as procedures are called data entry procedures.

Error handling procedures should be there to take care of the system when unexpected

results occur, also there should be actions to protect the system and its resources against

damages. Many procedures are used. Data entry procedures are used to display appropriate

messages when incorrect data is entered. Runtime procedures and error handling procedures are

used to give appropriate messages when expected results occur.

12


13/32

3.5 SYSTEM DEVELOPMENT

3.5.1 DESCRIPTION OF MODULES

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 indonating 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.

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.

Login: In this module a user id and password is provided to the Administrator and user, to

provide access control. The Administrator has the rights to make modifications from time to

time. The user can make use of the software but does have the rights to make modifications in

the way it performs.

Donor Registration

In this module store the donors registration details it include donor name address, age,

type of blood, mobile number, and personal information of donors. After completed his

registration form each donors get user id and password.

Blood Reservation

In this module store the blood reservation details. The blood needed and type place

quantity of blood.

13


14/32

4. TESTING AND IMPLEMENTATION

System testing involves unit testing, integration testing, white-box testing, black-box

testing. Strategies for integration software components into a functional product include the

bottom-up strategy, the top-down strategy, and sandwich strategy. Careful planning andscheduling are required to ensure that modules that will be available for integration into evolving

software product when needed a serious of testing are performed for the proposed system before

the system is ready for user acceptance testing.

4.1 UNIT TESTNG

Instead of testing the system as a whole, Unit testing focuses on the modules that make

up the system. Each module is taken up individually and tested for correctness in coding and

logic.

The advantages of unit testing are:

Size of the module is quite small and that errors can easily are located.

Confusing interactions of multiple errors in wide different parts of the software is

eliminated.

Modules level testing can be exhaustive.

INTEGRATION TESTING

It tests for the errors resulting from integration of modules. One specification of

integration testing is whether parameters match on both sides of type, permissible ranges and

meaning. Integration testing is functional black box test method. It includes testing each module

as an impenetrable mechanism for information. The only concern during integration testing is

that the modules work together properly.

WHITE BOX TESTING (CODE TESTING)The code-testing strategy examines the logic of the program. To follow this testing

method, the analyst develops test cases that result in executing every instruction in the program

or module so that every path through the program is tested. A path is a specific combination of

14


15/32


16/32

engineering, an emerging computer science practice which strives to build performance into the

design and architecture of a system, prior to the onset of actual coding effort.

Performance testing can serve different purposes. It can demonstrate that the system meets

performance criteria. It can compare two systems to find which performs better. Or it can

measure what parts of the system or workload cause the system to perform badly. In the

diagnostic case, software engineers use tools such as profilers to measure what parts of a device

or software contribute most to the poor performance or to establish throughput levels (and

thresholds) for maintained acceptable response time. It is critical to the cost performance of a

new system; the performance test efforts begin at the inception of the development project and

extend through to deployment. The later a performance defect is detected, the higher the cost of

remediation. This is true in the case of functional testing, but even more so with performance

testing, due to the end-to-end nature of its scope.

In performance testing, it is often crucial (and often difficult to arrange) for the test

conditions to be similar to the expected actual use. This is, however, not entirely possible in

actual practice. The reason is that production systems have a random nature of the workload and

while the test workloads do their best to mimic what may happen in the production environment,

it is impossible to exactly replicate this workload variability - except in the simplest system.

STRESS TEST

The application is tested against heavy load such as complex numerical values,

large number of inputs, large number of queries etc. which checks for the stress/load the

applications can withstand. Stress testing deals with the quality of the application in the

environment. The idea is to create an environment more demanding of the application than the

application would experience under normal work loads. A test environment is established with

many testing stations. At each station, a script is exercising the system. These scripts are usually

based on the regression suite. More and more stations are added, all simultaneous hammering on

the system, until the system breaks. The system is repaired and the stress test is repeated until a

level of stress is reached that is higher than expected to be present at a customer site. Race

conditions and memory leaks are often found under stress testing. A race condition is a conflict

between at least two tests. Each test works correctly when done in isolation. When the two tests

16


17/32

are run in parallel, one or both of the tests fail. This is usually due to an incorrectly managed

lock. A memory leak happens when a test leaves allocated memory behind and does not correctly

return the memory to the memory allocation scheme. The test seems to run correctly, but after

being exercised several times, available memory is reduced until the system fails.

STRUCTURE TEST

White-box testing, on the other hand is concerned with testing the implementation

of the program. The intent of this testing is not to exercise all the different input or output

conditions but to exercise the different programming structures and data structures used in the

program. White-box testing is also called structural testing and we will use the two terms

interchangeably.

VALIDATION TEST

After the culmination of black box testing, software is completely assembled as a

package, interfacing errors have been uncovered and corrected and final series of software

validation tests begin. Validation testing can be defined as many, but a single definition is that

validation succeeds when the software functions in a manner that can be reasonably expected by

the customer. Validation refers to the process of using the software in a live environment to find

errors. During the course of validation system may occur and the software will be changed.

OUTPUT TEST

In this output is tested by entering sample data and checking out for its efficiency.

USER ACCEPTANCE TEST

In this type of testing, the software is handed over to the user in order to find out if

the software meets the user expectations and works as it is expected to. In software development,

user acceptance testing (UAT) - also called beta testing, application testing, and end user testing

- is a phase of software development in which the software is tested in the "real world" by the

intended audience. UAT can be done by in-house testing in which volunteers or paid test subjects

use the software or, more typically for widely-distributed software, by making the test version

available for downloading and free trial over the Web. The experiences of the early users are

17


18/32

forwarded back to the developers who make final changes before releasing the software

commercially

CHANGE OVER PLAN

Testing commences with a test plan and terminates with acceptance testing. A test

plan is a general document for the entire project that defines the scope, approach to be taken, and

the schedule of testing as well as identifies the test items for the entire testing process and the

personnel responsible for the different activities of testing.

18


19/32

5. CONCLUSION

This project has given me an ample opportunity to design, code, test and implements an

application. This has helped in putting into practice of various Software Engineering principles

and Database Management concepts like maintaining integrity and consistency of data.

To debug the existing system, remove procedures those cause data redundancy, make

navigational sequence proper. To provide information about audits on different level and also to

reflect the current work status depending on organization/auditor or date. To build strong

password mechanism.

It will support for further modification, which again can be implemented if required in

the existing one. The blood bank management system is also tested in the organization for its

desired functionalities and it was found that it is functioning well without any errors. Thus this

development is found that it is functioning satisfactory to the organization in rendering its service

efficiently and effectively or successfully.

19


20/32

BIBLIOGRAPHY

1. Alex Homer, ASP.NET Programming , Wrox Publications, Second Edition , 2001.

2. Elias M.Awad , System Analysis and Design , Galgotia Publications, Second

Edition, 1997.

3. Robert Hottmalk SQL Server 2000 Administrating , Galgotia Publications, 2001

4. Roger S.Pressman , Software Engineering , Tata McGraw Hill Publications,

Second Edition, 1997

5. Gray D.Knott , Adaptive Delta Modulation,, Dr.Dobbs Journal, April 1998.

6. Tenkins G.M. and Walts D.G., Spectral Analysis and its Application ,

Sanfrancisco, CA, Holder Day 1968

Web Site

www.systemspymaster.com

www.w3schools.com

www.suntech.com/systemspy.html

www.sun.com www.wikipedia.org

20
http://www.systemspymaster.com/http://www.w3schools.com/http://www.suntech.com/systemspy.htmlhttp://www.sun.com/http://www.wikipedia.org/systemspyhttp://www.systemspymaster.com/http://www.w3schools.com/http://www.suntech.com/systemspy.htmlhttp://www.sun.com/http://www.wikipedia.org/systemspy


21/32

APPENDICES

A. DATA FLOW DIAGRAM

Data - Flow Diagrams:Data - Flow Di agrams:

Context Level - DFD:Context Level - DFD:

I Level DFD:I Level DFD:

21

BloodDonors

BloodBank

BloodSeekers

BloodDonors

Life SavingContacts

Search

BloodBank

Registration

MobilinkPaging

ServicesBloodSeekers


22/32

II Level DFD:II Level DFD:

22

BloodDonors

Life SavingContacts

Search

BloodBank

Registration

MobilinkPaging

Services

BloodSeekers

ReceiveDonorDetails


23/32

Login Form

23


24/32

MDI Form

24


25/32

25


26/32

26


27/32

27


28/32

28


29/32

29


30/32

30


31/32

31


32/32

Documents

Blood Bank Management Final (1)