Blood donation management system

Blood Donation Management System

ABSTRACT

Emergency situations, such as accidents, create an immediate and critical need for  specific blood types. In addition, advances in medicine have also increased the need of blood for various treatments and surgeries. In short, blood is a saver of all existing lives. So in such emergency cases, it is difficult for hospital staff to collect blood in case of shortage of blood without having appropriate resources. ur system solves this problem. !his pro"ect is to build a web#based, online blood donation management system. !his system provides an online  platform for $uic% access to the re$uired donor. &ence the life at threat can be saved by this optimi'ation techni$ue.

!he Blood Donation management system is to create an e#Information about the donor who wants to donate blood. !hrough this application any person who is interested in donating the blood can register himself. Moreover if any general consumer wants to ma%e re$u re$uest est blo blood od onl onlin inee he can can also also ta%e ta%e the hel help p of this this site site.. (dmin is the mai n aut hor it y who can do addition, deletion, and modification if re$uired.

ABSTRACT

Emergency situations, such as accidents, create an immediate and critical need for  specific blood types. In addition, advances in medicine have also increased the need of blood for various treatments and surgeries. In short, blood is a saver of all existing lives. So in such emergency cases, it is difficult for hospital staff to collect blood in case of shortage of blood without having appropriate resources. ur system solves this problem. !his pro"ect is to build a web#based, online blood donation management system. !his system provides an online  platform for $uic% access to the re$uired donor. &ence the life at threat can be saved by this optimi'ation techni$ue.

!he Blood Donation management system is to create an e#Information about the donor who wants to donate blood. !hrough this application any person who is interested in donating the blood can register himself. Moreover if any general consumer wants to ma%e re$u re$uest est blo blood od onl onlin inee he can can also also ta%e ta%e the hel help p of this this site site.. (dmin is the mai n aut hor it y who can do addition, deletion, and modification if re$uired.

INDEX 1. INTR INTROD ODUC UCTI TION ON

).). ).).

*ro" *ro"ec ectt Desc Descri ript ptio ion n )

).+. ).+.

*rob *robllem Defi efinit nition ion )

2. REQU REQUIR IREM EMEN ENTS TS

+.). unctional -e$uirements

+

+.+. on unctional -e$uirements

/

+./. &ardware -e$uirements

0

+.0. Software -e$uirements 0 3. ANAL NALYSIS SIS

/.).

Existing syst ystem 1

/.+.

*rop roposed System 2

/./.

Modularity 2

/.0.

3M4 Diagrams

)5

4. DESIGN 0.).Software Design 4evels

)1

0.+.6or%ing of ur 6e 6ebsite bsite 0./.Scenario of !he *roposed Method

)7 )2

5.DATABASE TABLES TABLES

1.).Entities

)8

1.+.Entities 1.+.En tities 6ith (ttributes

)8

1./.Data Dictionary

)9

6. DESCRIPTION OF TECHNOLOGIES USED

+5

7.CODING

/+

8.TESTING

/2

.OUTPUT SCREENS

0)

1!.CONCLUSION

09

11.REFERENCE

1)

)

1.INTRODUCTION

 1.1.P"#$%&' D%(&")*')#+

!his pro"ect is aimed to develop an online Blood Donation Information. !he entire pro"ect has been developed %eeping in view of the distributed client server computing technology, technology, in mind. !he pro"ect has been planned to be having the view of distributed architecture, with centrali'ed storage of the database. !he application for the storage of the data has been  planned, using the constructs of racle and all the user interfaces have been designed des igned using the "ava and :S* ;:ava Server *ages< technologies.

!he database connectivity is planned using the racle database connectivity. !he standards of security and data protective mechanism have been given a big choice for proper  usage.

!he application ta%es 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.

O,$%&')-% !his is an online application which allows you to access the information about Blood donor, readily scalable and adaptable to meet the complex need of blood recipient and Blood Ban%s 6ho are =ey acilitator for the &ealthcare Sector.

1.2.P"#,/%0 D%)+)')#+ Entering the details about the blood groups, members, phone number, addresses etc. (nd trac%ing the database is complicated when the details are maintained manually. !his ma%es the maintenance of schedule erroneous.

+

2.REQUIREMENTS

The requirement analysis stage of a software engineering project involves collecting and analyzing information about the part of the organization that is supported by the application. This information is then used to identify the user’s requirement of the new system. Identifying the required functionality of the system is very important as a system with incomplete functionality may lead to it being rejected. A description of the aim of the project is given here along with details of the functional and non-functional requirements for the system. The test sheets for evaluating the completed system are also presented. The requirements of the Web-based management information system are to develop: • A web based front end for entering donated blood details including the donor, his/her blood group, gender, age, and status of the donated blood • A web based front end for searching the information relating to a given donor or a given blood group. • A facility to still enter donor and donated blood information and also maintain the database using those details entered via the web front end.

2.1.Functional Requirements In this research project we aim at developing a system which should improve on the current one with a lot of functionalities and therefore the Major target or goal here is to: • To develop a blood donor database • To develop a client interface that allows privileged users to carry out tasks such as inserting or modifying and deleting data in the database; • To develop a searching functionality in order to allow normal and privileged users to search the details of a given donor, blood group. • To fully integrate the Web-based management information system to the World-

/ Wide-Web and hence allow access from any Internet networked terminal and Web browser around the world. •Finally the system should be flexible enough to store data for several years and also be able provide sufficient User and Administration Guides.

2.2.Non-Functional Requirements

!he system must be developed to suit the particular needs of a user#friendly environment. !his means that the system must accommodate a clearly understandable user interface as well as clear online help documentation at any stage of the user interaction with the system. ( fast response time in obtaining and providing information to the system may also  prove to be a significant advantage. In addition to these re$uirements, the system should also embrace the following re$uirements>#

Security: Each user is required to log in. The system should log staff that has been assigned

user names and passwords. The system should be designed to make it impossible for anybody to logon without a valid username and password.

Reliability: The system should have little or no downtime and be able to handle multiple

concurrent users.

Ease of Use: The general and administrative views should be easy to use and intuitive.

Online help and documentation should be provided.

Performance: The system should have a quick response time.

System and Browser compatibility Testing: The system should be accessible on the

following browsers - Microsoft Internet Explorer 5.5+, NetScape Navigator 6.0+ and Mozilla 1. 3+.

0

2.3.H""% R%)"%0%+'(

•

*entium;-< Dual#?ore ?*3 /.55@&A

•

-(M +@B and (bove

•

&DD +5 @B &ard Dis% Space and (bove

2.4.S#'"% R%)"%0%+'( •

6ID6S S *

•

!ext editor 

•

(pache !omcat 9.5.x software

•

:ava SE Development =it 8

•

:ava Standard Edition -untime Environment

•

racle Database Express Edition ))g

•

6eb browsers i. Internet Explorer 8 or newer  ii. Mo'illa irefox iii. @oogle chrome

1

3.ANALYSIS

3.1.E)(')+ S9('%0 Manual systems put pressure on people to be correct in all details of their wor% at all times, the problem being that people arenCt perfect, however much each of us wishes we were. 6ith manual systems the level of service is dependent on individuals and this puts a re$uirement on management to run training continuously for staff to %eep them motivated and to ensure they are following the correct procedures. It can be all too easy to accidentally switch details and end up with inconsistency in data entry or in hand written orders. !his has the effect of not only causing problems with customer service but also ma%ing information unable be used for reporting or finding trends with data discovery. -eporting and chec%ing that data is robust can be timely and expensive. !his is often an area where significant money can be saved by automation. It ta%es more effort and physical space to %eep trac% of paper documents, to find information and to %eep details secure. 6hen mista%es are made or changes or corrections are needed, often a manual transaction must be completely redone rather than "ust updated.  6ith manual or partially automated systems information often has to be written down and copied or entered more than once. Systemisation can reduce the amount of duplication of data entry. (nother impact of manual systems is on ?ustomer service. ?ustomer $ueries can be difficult to respond to as information is stored in different places and may even re$uire that you find the right person before being able to respond. !his is no good if they are out to lunch or only wor% part time. •

Inconsistency in data entry, room for errors.

•

4arge ongoing staff training cost.

•

System is dependent on good individuals.

7

•

-eduction in sharing information and customer services.

•

!ime consuming and costly to produce reports.

•

4ac% of security.

•

Duplication of data entry. 6hich raises the $uestion if systemisation has such benefits, why arenCt all

organisations running fully integrated systems. !here is always the obvious balance of cost vs benefit, as an organisation grows and adds people and functions the benefits of systems increases. ften when an organisation is growing itCs the time that they need to put in a new system, however this is also the time that there is significant pressure on existing resources and itCs the hardest time to ma%e a change. !hese is another factor to be considered before automating your organisation and this is that good processes must already be in place. *utting in a system in most cases wonCt successfully apply a process where one hasnCt existed before. !he most effective way to get  benefit from a new system is where a good manual operations exist and your new system automate these. 4imitations of the Manual system> •

It is time consuming

•

It leads to error prone results

•

It consumes lot of manpower to better results

•

It lac%s data security

•

-etrieval of data ta%es lot of time

•

*ercentage of accuracy is less

•

3pdating records ta%es lot of time

•

(ccessing records also ta%e time.

2

3.2.P"#*#(% S9('%0> (n efficient blood ban% management system should be developed, with the aim of ensuring that every patient has access to an ade$uate $uantity of safe blood. !he management system should solve the issue of demand and wastage and lead to self#sufficiency in blood re$uirement. !his should encourage new donors and retain old donors to donate blood. !his system is used to maintain whole information about blood donation management.

3.3.M#/"):')#+ Modulari'ation is a techni$ue to divide a software system into multiple discrete and independent modules, which are expected to be capable of carrying out tas%;s< independently. !hese modules may wor% as basic constructs for the entire software. Designers tend to design modules such that they can be executed andor compiled separately and independently. Modular design unintentionally follows the rules of divide and con$uerC problem# solving strategy this is because there are many other benefits attached with the modular design of a software. (dvantage of modulari'ation> •

Smaller components are easier to maintain

•

*rogram can be divided based on functional aspects

•

Desired level of abstraction can be brought in the program

•

?omponents with high cohesion can be re#used again

•

?oncurrent execution can be made possible

•

Desired from security aspect

In this pro"ect there are mainly / modules. •

(dmin

•

Donors

•

(cceptors

8

A0)+ > In this module the (dministrator has the privileges to add all the Blood @roups, Blood !ype. &e can search about all the information about the Donor. !his module focuses on the both donors F acceptors. Each member in a donor is given a user name and password, which identifies him uni$uely. !he options given to administrator in the interface are # ?hange *assword, Maintain donor details, 3pdate donor details. (dmin can •

Maintain donor details

•

3pdate donor details

•

Delete donor details

•

?hange password

D#+#"> Donor is that person who is interested in donating their blood so they can register themselves through this website. If any re$uirement comes then they will be contacted and they can donate their blood. (long with it they can search for a particular blood group if needed.  Each member in a Donor module is given a user id and password, which identifies him uni$uely. !he member is given a login form. &e enters the login details user id and password.

!he options given to Donor are> •

?hange password

•

ind a Blood donor of a specific blood group.

•

Edit *rofile

•

re$uently (s%ed Guestions about Blood donation.

•

4ogout

A&&%*'#"> In this module any general user who is not registered as a Donor can also ma%e re$uest for blood if needed. Donor can also ma%e a re$uest for blood if needed. &e can visit

9 all the static pages and can get information about the various issues related with blood donation. In this you can search for donors. !he options given to (cceptors are> •

-egister as a blood Donor. ;If not yet registered<

•

ind a Blood donor for a specific blood group.

•

re$uently (s%ed Guestions about Blood donation.

(-+'%( ). 3ser friendliness is provided in the application with various controls. +. !he system ma%es the overall pro"ect management much easier and flexible. /. !here is no ris% of data mismanagement at any level while the pro"ect development is under process. 0. It provides high level of security with different level of authentication.

S9('%0 D',(% Stores all the details about the donor information. !here will be an option for updating the personal information by the users. !his is for trac%ing and managing information.

)5

3.4.UML D)"0(

U(% C(% D)"0 •

!he unified modeling language allows the software engineer to express an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules.

•

( 3M4 system is represented using five different views that describe the system from distinctly different perspective. Each view is defined by a set of diagram, which is as follows.

U(%" M#%/ ;)% •

!his view represents the system from the userCs perspective.

•

!he analysis representation describes a usage scenario from the end#users  perspective.

S'"&'"/ 0#%/ -)% •

In this model the data and functionality are arrived from inside the system.

•

!his model view models the static structures.

B%

+/

•

-ead the explicit data sent by the clients ;browsers LO field or method declaration N

H9*%" T%' M"?=* L+% &!M4 is a predominant mar%#up language for the creation of web pages. It provides a means to describe the structure of text#based information in a document by denoting certain text as headings, paragraphs, lists and to supplement that text with interactive forms, embedded images, and other ob"ects.

C(&)+ S'9/% S !he connection 3-4 for the oracle)5@ database is

 "dbc>oracle>thin>Rlocalhost>)1+)>xe where :DB? is the (*I, oracle is the database, thin is the driver, localhost is the server name on which oracle is running, we may also use I* address, )1+) is the port number and E is the racle service name. ou may get all these information from the tnsnames.ora file. •

U(%"+0%> !he default username for the oracle database is system.

•

P((#" > *assword is given by the user at the time of installing the oracle database.

step) load the driver class ?lass.forame;Joracle."dbc.driver.racleDriverJoracle>thin>Rlocalhost>)1+)>xeJ,Jsyst emJ,JoracleJ -(?4E DBC ")-%" +0%  oracle."dbc.driver.racleDriver URL #"0'  "dbc>oracle>thin>Rhostname>port umber>databaseame

O"&/% ( database management, or DBMS, gives the user access to their data and helps them transform the data into information. Such database management systems include dBase,  paradox, IMS and SG4 Server. !hese systems allow users to create, update and extract information from their database.

( database is a structured collection of data. Data refers to the characteristics of   people, things and events. racle stores each data item in its own fields. In racle, the fields relating to a particular person, thing or event are bundled together to form a single complete

/+ unit of data, called a record ;it can also be referred to as raw or an occurrence

Manual testing is the process of manually testing software for defects. It re$uires a tester to play the role of an end user and use most of all features of the application to ensure correct behavior. !o ensure completeness of testing, the tester often follows a written test plan that leads them through a set of important test cases.

O-%"-)% ( %ey step in the process is, testing the software for correct behaviour prior to release to end users. or small scale engineering efforts ;including prototypeswww.google.co.in http>www.w/schools.com http>stac%overflow.com http>www."avatpoint.com http>www.friends+support.orgindex.aspx http>www.redcross.org https>www.wi%ipedia.org www.tutorialspoint.com