Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Blood Donation Document

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 30

ACKNOWLEDGEMENT

First I thank the lord Almighty who blessed us with wonderful facilities, friends and
family whose love and encouragement has given new Significance to our every
accomplishment.

I am privileged to owe my sincere thanks to our beloved Principal Dr.C.Veerabahu


M.Sc., M.Phil., Ph.D., who always cared to fulfill the need of the students and be a moral
support to us.

I whole heartedly thank our Head of the Department Mr.S.Gomathinayagam M.Sc.,


M.Phil., M.C.A., for providing us with constructive criticism and suggestions to fulfill my
project.

I extend our gratitude to guide Mr.I.Arockiyasamy M.C.A., M.Phil., for his


valuable guidance and encouragement throughout my project. It is our profound duty to
thanks who has helped me in Various activities.
SYNOPSIS

The number of persons who are in need of blood are increasing in large number day
by day. In order to help people who are in need of blood, my Online Blood Bank can be
used effectively for getting the details of blood donors having the same blood group and
with in the same city. With the help of my Online Blood Bank people who are having the
thought of donating blood gets registered in my Online Blood Bank giving his total details.

My Online Blood Bank site is available to everyone easily. A person who likes to
donate blood gives his entire details i.e., fill in the registration form and can create a
username with a password by which he can modify his details if at all there are any changes
in his information given before.

My site also helps people who are in need of blood by giving the details of the
donors by searching, if at all there are no donors having the same group and with in their
own city they will be given the addresses with phone numbers of some contact persons in
major cities who represent a club or an organization with free of cost. If at all the people
find any difficulty in getting blood from the contact persons we will give them a MobiLink
i.e., India’s Largest Paging Service number through which they can give the message on
every ones pagers with the blood group and city they are living in, such that the donors who
view the messages in their pagers having the same blood group and the in the same city, he
contacts the person on phone who are in need of a blood. Such that the person gets help
from us which saves his life.
S.No CONTENTS PAGE NO
1. Introduction
2. System Analysis
2.1 Existing System
2.2 Proposed System
2.3 Feasibility Study
3. Project Description
3.1 Modules
3.2 Module Description
4. System Specification
4.1 Hardware Requirements
4.2 Software Requirements
4.3 Software Description
5. System Design
5.1 Logical Design
5.2 Physical Design
5.3 Input and Output Design
6. Form Design
7. Source Code
8. System Testing
9. System Implantation
10. Future Enhancement
11. Conclusion
12. Bibliography
1.INTRODUCTION

In today’s computer age data storage has been growing in size to unthinkable ranges
that only computerized methods applied to find information among these large repositories
of data available to organizations whether it was online or offline. Data mining was
conceptualised in the 1990s as a means of addressing the problem of analysing the vast
repositories of data that are available to mankind, and being added to continuously. Data
mining is necessary to extract hidden useful information from the large datasets in a given
application. This usefulness relates to the user goal, in other words only the user can
determine whether the resulting knowledge answers his goal.

The growing quality demand in the blood bank and donation sector makes it
necessary to exploit the whole potential of stored data efficiently, not only the clinical data
and also to improve the behaviours of the blood donors. Data mining can contribute with
important benefits to the blood bank and donation sector, it can be a fundamental tool to
analyse the data gathered by blood banks through their information systems. In recent years,
along with development of medical informatics and information technology, blood bank
information system grows rapidly. With the growth of the blood banks, enormous Blood
Banks Information Systems (BBIS) and databases are produced.

It creates a need and challenge for data mining. Data mining is a process of the
knowledge discovery in databases and the goal is to find out the hidden and interesting
information. Various important steps are involved in knowledge discovery in databases
(KDD) which helps to convert raw data into knowledge. Data mining is just a step in KDD
which is used to extract interesting patterns from data that are easy to perceive, interpret,
and manipulate. Several major kinds of data mining methods, including generalization,
characterization, classification, clustering, association, evolution, pattern matching, data
visualization, and meta-rule guided mining will be reviewed. The explosive growth of
databases makes the scalability of data mining techniques increasingly important. Data
mining algorithms have the ability to rapidly mine vast amount of data.
2. SYSTEM ANALYSIS
2.1 EXISTING SYSTEM:

In existing system the blood donation maintance service exhibited at a lot of


ineffectiveness and inefficiency that had fetched impact taken by management. The system
which was manual that is based on paper card to collect blood donor data, keep record of
blood donors and disseminate results to blood donors, had weakness that needed IT based
Solutions. The system was characterized by delays and sometimes failure to access historial
records errors were witnesses in entry and manual analysis of results, secrecy and
confidentiality of records lacked because unauthorized persons could easily access the
records.

Disadvantages:

 Without integrating the blood banks will lead to time consuming while searching of a
particular group of blood.
 Without having proper information it is very difficult to supply the blood to the
required people.

2.2. PROPOSED SYSTEM:

The proposed Blood Bank management system helps the people who are in need of a
blood by giving them all details of blood group availability or regarding the donors with the
same blood group. Our website work 24x7 so user can get information of blood donor any
time. Blood donor can also get registered and save life of other person. When blood is
need in the operation then people have very less to get the blood available so if he/she get
the information like who can give him blood in time in his city is life saving.

Advantages:

 Speed and accuracy there is no redundancy of data.


 It will be easily handle.
 Reduce the Time spend on the paper work.
2.3.FEASIBILITY STUDY:

Feasibility study is performed to determine whether the proposed system is viable


considering the Technical, Operational and Economical factors. After going through
feasibility study we can have a clear-cut view of the system’s benefits and drawbacks.

1.Technical Feasibility:

The proposed system is developed using Active Server Page, VB Script and HTML
as front-end tool and Oracle 8 as the back end. The proposed system needs a Personal Web
Server to serve the requests submitted by the users. The Web browser is used to view the
web page that is available within the Windows operating system itself. The proposed system
will run under Win9x, NT, and win2000 environment. As Windows is very user friendly
and GUI OS it is very easy to use. All the required hardware and software are readily
available in the market. Hence the system is technically feasible.

2.Operational Feasibility:

The proposed system is operationally feasible because of the following reasons.


 The customer is benefited more as most of his time is saved. The customer is
serviced at his place of work.

 The cost of the proposed system is almost negligible when compared to the
benefits gained.

3.Economical Feasibility:

As the necessary hardware and software are available in the market at a low cost, the
initial investment is the only cost incurred and does not need any further enhancements.
Hence it is economically feasible.

The system is feasible in all respects and hence it encourages taking up the system
design.
3.PROJECT DESCRIPTION

3.1.MODULES:
Blood Donation Maintanence system is to provide services for the people who are in
need of blood by getting help from the donors who are interested in donating blood for the
people.

 Donor Registration
 Seekers
 Donor Details
3.2.MODULE DESCRIPTION:

Donor Registration:
In this module, people who are interested in donating blood get registered in my site
and give his overall details related to him, i.e. he fills in a registration form by giving the
total details such as name, father name, address, city, gender, weight, dob, blood group,
phone number, e-mail address, etc…

Seekers:
The module helps user to find blood group. When user click on find a blood group
system ask him to enter blood group he want to search. After entering the blood group,
system search for the availability of the blood group and give him the list of the donors
who has the same blood group.

Donor Details:
The people who are in need of blood can search in our site for getting the details of
for get donors having the same blood group. They can search a donor and they can select
the blood group which he needs. He then gets the details of the donors who exist with in the
same blood group that he has selected.
4.SYSTEM SPECIFICATION

In the system specification, the latest hardware and software specifications must be
proposed to enable faster retrieval of the information. The System Specifications involves
two concepts. They are as follows:

 Hardware Requirements
 Software Requirements
 Software Descriptions

The detailed Hardware and Software Specifications are given below

4.1 HARDWARE REQUIREMENTS

System: Intel(R) Core(TM) is

Hard Disk: 500GB

Keyboard: 104 Keys

RAM: 2GB

Speed: 3.06 GHz

4.2.SOFTWARE REQUIREMENTS

Operating System: Windows 7

Coding Language: ASP.Net

Back-end: SQL Server


4.3. SOFTWARE DESCRIPTION
FRONT END DESCRIPTION

ASP.Net

.Net is the Microsoft services strategy to connect information, people, systems and
devices through software. Integrated across the Microsoft platform, ASP .Net technology
provides the ability to quickly build, deploy, manage and use connected, security-enhanced
solutions with Web services.

In future, the .Net infrastructure will be integrated into all Microsoft's operating
systems, desktop and server products. Windows .NET is the next generation Windows. It
will provide support for all the .Net building blocks and .Net digital media.

The major components of the .NET consists of

 Common Language Runtime


 .NET Framework Class Library
 Common Language Specification
 .Net Languages
 Visual Studio.NET

.NET Framework:

The .NET Framework is a new computing platform that simplifies application


development in the highly distributed environment of the Internet. The .NET Framework is
designed to fulfill the following objectives:

 To provide a consistent object-oriented programming environment whether object


code is stored and executed locally, executed locally but internet-distributed, or
executed remotely.
 To provide a code-executicn environment that minimizes software deployment and
versioning conflicts.
 To provide a code-executicn environment that guarantees safe execution of code,
including code created by an unknown or semitrusted third party.
 To provide a code-execution environment that eliminates the performance problems
of scripted or interpreted environments.
 To make the developer experience consistent across widely varying types of
applications, such as Windows-based applications and Web-based applications.
 To build all communication on industry standards to ensure that code based on the
.NET Framework can integrate with any other code.

The .NET Framework has two main components: the common language runtime and
the .NET Framework class library. The common language runtime is the foundation of the
.NET Framework .You can think of the runtime as an agent that manages code at execution
time, providing core services such as memory management, thread management, and
remoting, while also enforcing strict type safety and other forms of code accuracy that
ensure security and robustness. In fact, the concept of code management is a fundamental
principle of the runtime. Code that targets the runtime is known as managed code, while
code that does not target the runtime is known as unmanaged code. The class library, the
other main component of the .NET Framework, is a comprehensive, object-oriented
collection of reusable types that you can use to develop applications ranging from
traditional command-line or graphical user interface (GUI) applications to applications
based on the latest innovations provided by ASP.NET, such as Web Forms and XML Web
services.

The .NET Framework can be hosted by unmanaged components that load the
common language runtime into their processes and initiate the execution of managed code,
thereby creating a software environment that can exploit both managed and unmanaged
features. The .NET Framework not only provides several runtime hosts, but also supports
the development of third-party runtime hosts.

For example, ASP .NET hosts the runtime to provide a scalable, server-side
environment for managed code. ASP NET works directly with the runtime to enable Web
Forms applications and XML Web services, both of which are discussed later in this topic.

Internet Explorer is an example of an unmanaged application that hosts the runtime


(in the form of a MIME type extension). Using Internet Explorer to host the runtime enables
you to embed managed components or Windows Forms controls in HTML documents.
Hosting the runtime in this way makes managed mobile code possible, but with significant
improvements that only managed code can offer, such as semi-trusted execution and secure
isolated file storage.

The following illustration shows the relationship of the common language runtime
and the class library to your applications and to the overall system. The illustration also
shows how managed code operates within a larger architecture.
Features of the Common Language Runtime

The common language runtime manages memory, thread execution, code execution,
code safety verification, compilation, and other system services. These features are intrinsic
to the managed code that runs on the common language runtime.

With regards to security, managed components are awarded varying degrees of trust,
depending on a number of factors that include their origin (such as the Internet, enterprise
network, or local computer). This means that a managed component might or might not be
able to perform file-access operations, registry-access operations, or other sensitive
functions, even if it is being used in the same active application.

The runtime enforces code access security. For example, users can trust that an
executable embedded in a Web page can play an animation on screen or sing a song, but
cannot access their personal data, file system, or network. The security features of the
runtime thus enable legitimate Internet-deployed software to exceptionally featuring rich.

The runtime also enforces code robustness by implementing a strict type and code-
verification infrastructure called the common type system (CTS). The CTS ensures that all
managed code is self-describing. The various Microsoft and third-party language compilers
generate managed code that conforms to the CTS. This means that managed code can
consume other managed types and instances, while strictly enforcing type fidelity and type
safety.

In addition, the managed environment of the runtime eliminates many common


software issues. For example, the runtime automatically handles object layout and manages
references to objects, releasing them when they are no longer being used. This automatic
memory management resolves the two most common application errors, memory leaks and
invalid memory references.

The runtime also accelerates developer productivity. For example programmers can
write applications in their development language of choice, yet take full advantage of the
runtime, the class library, and components written in other languages by other developers
Any compiler vendor who chooses to target the runtime can do so. Language compilers that
target the .NET Framework make the features of the NET Framework available to existing
code written in that language greatly easing the migration process for existing applications.

While the runtime is designed for the software of the future, it also supports software
of today and yesterday. Interoperability between managed and unmanaged code enables
developers to continue to use necessary COM components and DLLS.
The runtime is designed to enhance performance. Although the common language
runtime provides many standard runtime services, managed code is never interpreted. A
feature called just-in-time JIT) compiling enables all managed code to run in the native
machine language of the system on which it is executing. Meanwhile, the memory manager
removes the possibilities of fragmented memory and increases memory locality-of-reference
to further increase performance.

Finally, the runtime can be hosted by high-performance, server-side applications,


such as Microsoft SQL Server and Internet Information Services (IIS). This infrastructure
enables you to use managed code to write your business logic, while still enjoying the
superior performance of the industry's best enterprise servers that support runtime hosting.

.NET Framework Class Library

The NET Framework class library is a collection of reusable types that tightly
integrate with the common language runtime. The class library is object oriented, providing
types from which your own managed code can derive functionality. This not only makes the
.NET Framework types easy to use, but also reduces the time associated with learning new
features of the .NET Framework In addition, third-party components can integrate
seamlessly with classes in the .NET Framework.

For example, the .NET Framework collection classes implement a set of interfaces
that you can use to develop your own collection classes. Your collection classes will blend
seamlessly with the classes in the .NET Framework.

As you would expect from an object-oriented class library, the .NET Framework types
enable you to accomplish a range of common programming tasks including tasks such as
string management, data collection, database connectivity, and file access. In addition to
these common tasks, the class library includes types that support a variety of specialized
development scenarios. For example, you can use the NET Framework to develop the
following types of applications and services:

 Console applications
 Scripted or hosted applications.
 Windows GUI applications (Windows Forms).
 ASP.NET applications
 XML Web services
 Windows services
For example, the Windows Forms classes are a comprehensive set of reusable types that
vastly simplify Windows GUI development. If you write an ASP.NET Web Form
application, you can use the Web Forms classes.

Client Application Development

Client applications are the closest to a traditional style of application in Windows-


based programming. These are the types of applications that display windows or forms on
the desktop, enabling a user to perform a task. Client applications include applications such
as word processors and spreadsheets, as well a custom business applications such as data-
entry tools, reporting tools, and so or Client applications usually employ windows, menus,
buttons, and other GL elements, and they likely access local resources such as the file
system an peripherals such as printers.

Another kind of client application is the traditional Activex control (now replaced by
the managed Windows Forms control) deployed over the internet as Web page. This
application is much like other client applications: it is executed natively, has access to
local resources, and includes graphical elements.

In the past. developers created such applications using C/C++ in conjunction with the
Microsoft Foundation Classes (MFC) or with rapid application development (RAD)
environment such as Microsoft Visual Basic. The.NET Framework incorporates aspects of
these existing products into a single, consistent development environment that drastically
simplifies the development of client applications. The Windows Forms classes contained in
the .NET Framework are designed to be used for GUI development. You can easily create
command windows, buttons, menus, toolbars, and other screen elements with the flexibility
necessary to accommodate shifting business needs.

For example, the .NET Framework provides simple properties to adjust visual
attributes associated with forms. In some cases the underlying operating system does not
support changing these attributes directly, and in these cases the .NET Framework
automatically recreates the forms. This is one of many ways in which the .NET Framework
integrates the developer interface, making coding simpler and more consistent.

Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a


user's computer. This means that binary or natively executing code can access some of the
resources on the user's system (such as GUI elements and limited file access) without being
able to access or compromise other resources. Because of code access security, many
applications that once needed to be installed on a user's system can now be safely deployed
through the Web. Your applications can implement the features of a local application while
being deployed like a Web page.

Server Application Development

Server-side applications in the managed world are implemented through runtime


hosts. Unmanaged applications host the common language runtime, which allows your
custom managed code to control the behavior of the server. This model provides you with
all the features of the common language runtime and class library while gaining the
performance and scalability of the host server.

The following illustration shows a basic network schema with managed code running
in different server environments. Servers such as IIS and SQL Server can perform standard
operations while your application logic executes through the managed code.

Server-side managed code

ASP.NET is the hosting environment that enables developers to use the .NET
Framework to target Web-based applications. However, ASPNET is mere than just a
runtime host; it is a complete architecture for developing Web sites and Internet distributed
objects using managed code. Both Web Forms and XML Web services use IIS and
ASP.NET as the publishing mechanism for applications, and both have collection of
supporting classes in the .NET Framework.

XML Web services, an important evolution in Web-based technology, are


distributed, server-side application components similar to common Web sites. However,
unlike Web-based applications, XML Web services components have no UI and are not
targeted for browsers such as Internet Explorer and Netscape Navigator. Instead, XML
Web services consist of reusable software components designed to be consumed other
applications, such as traditional client applications, Web-based applications, or even other
XML Web services, As a result, XML Web services. As are result, XML Web services
technology is rapidly moving application development and deployment into the highly
distributed environment of the Internet.

If you have used earlier versions of ASP technology, you will immediately notice the
improvements that ASP.NET and Web Forms offers. For example, you can develop Web
Forms pages in any language that supports the .NET Framework. In Web addition, your
code no longer needs to share the same file with your HTTP text. Web Forms pages execute
in native machine language because, like any other application, they take full advantage of
the runtime. In contrast, unmanaged always scripted and interpreted. ASP.NET pages are
faster, more pages are functional, and easier to develop than unmanaged ASP pages because
they interact with the runtime like any managed application.

The .NET Framework also provides a collection of classes and tools to aid in
development and consumption of XML Web services applications XML Web services are
built on standards such as SOAP (a remote procedure-call protocol),XML (an extensible
data format), and WSDL (the Web Services Description .NET Framework is built on these
standards to promote interoperability with non-Microsoft solutions.

For example, the Web Services Description Language tool included with the .NET
Framework SDK can query an XML Web service published on the Web, parse its WSDL
description, and produce C# or Visual Basic Source code that your application can use to
become a client of the XMI. Web service. The source code can create classes derived from
classes in the class library that handle all the underlying communication using SOAP and
XML parsing. Although you can use the class library to consume XML Web services
directly, the Web Services Description Language tool and the other tools contained in the
SDK facilitate your development efforts with the .NET Framework.

If you develop and publish your own XML Web service, the .NET Framework
provides a set of classes that conform to all the underlying communication standards, such
as SOAP, WSDL and XML. Using those classes enables you to focus on the logic of your
service, without concerning yourself with the communications infrastructure required by
distributed software development.

Finally, like Web Forms pages in the managed environment, your XML Web service
will run with the speed of native machine the scalable communication of IIS.

Active Server Pages.NET

ASP.NET is a programming framework built on the common language runtime that


can be used on a server to build powerful Web applications. ASPNET offers several
important advantages over previous Web development models.

Enhanced Performance

ASP.NET is compiled common language runtime code running on the server.


Unlike its interpreted predecessors, ASP NET can take advantage of early binding, just-in-
time compilation, native optimization, and caching services right out of the box. This
amounts to dramatically better performance before you ever write a line of code.

World-Class Tool Support:


The ASP.NET framework is complemented by a rich toolbox and designer in the
Visual Studio integrated development environment. WYSWYG editing drag-and-drop
server controls, and automatic deployment are just a few of the features this powerful tool
provides.

Power and Flexibility:

Because ASP.NET is based on the common language runtime the power and
flexibility of that entire platform is available to Web application developers. The .NET
Framework class library, Messaging, and Data Access solutions are all seamlessly
accessible from the Web. ASP.NET is also language-independent, so you can choose the
language that best applies to your application or partition your application across many
languages. Further, common interoperability guarantees n your existing investment in
COM-based development is preserved when migrating to ASP.NET.

Simplicity:

ASP.NET makes it easy to perform common tasks from simple form submission and
client authentication to deployment and site configuration. For example, the ASP.NET page
framework allows you to build user interfaces that cleanly separate application logic from
presentation code and to handle events in a simple, Visual Basic like forms processing
model. Additionally, the common language runtime simplifies development, with managed
code services such as automatic reference counting and garbage collection.

Manageability:

ASP.NET employs a text-based, hierarchical configuration system, which simplifies


applying settings to your server environment and Web applications. Because configuration
information is stored as plain text, new settings may be applied without the aid of local
administration tools, This "zero local administration philosophy extends to deploying
ASP.NET Framework applications as well. An ASP.NET Framework application is
deployed to a server simply by copying the necessary files lo the server. No server restart is
required, even to deploy or replace running compiled code.

Scalability and Availability:

ASP.NET has been designed with scalability in mind, with features specifically
tailored to improve environments. Further, processes are closely monitored and managed by
the performance in clustered and multiprocessor ASP.NET runtime, so that if one
misbehaves (leaks, deadlocks), a new process can be created in its place, which helps keep
your application constantly available to handle requests.
Customizability and Extensibility:

ASP.NET delivers a well-factored architecture that allows developers to "plug-in"


their code at the appropriate level. In fact, it is possible to extend or replace any
subcomponent the ASP.NET runtime with your own custom-written component.
Implementing custom authentication or state services has never been easier.

Security:

With built in Windows authentication and per-application configuration, you can be


assured that your applications are secure.

ASP.NET Web Forms

The ASP.NET Web Forms page framework is a scalable common language runtime
programming model that can be used on the server to dynamically generate Web pages.

Intended as a logical evolution of ASP (ASP.NET provides syntax ASP.NET Web


Forms framework has been compatibility with existing pages), the specifically designed to
address a number of key deficiencies in the previous model.

In particular, it provides:

 The ability to create and use reusable UI controls that can encapsulate common
functionality and thus reduce the amount of code that a page developer has to write.
 The ability for developers to cleanly structure their page logic in an orderly fashion
(not "spaghetti code").
 The ability for development tools to provide strong WYSIWYG design support for
pages (existing ASP code is opaque to tools).

ASP.NET Web Forms pages are text files with an asps tile name extension. They
can be deployed throughout an IIS virtual root directory tree. When a browser client
requests .aspx resources the ASP NET runtime parses and compiles the target file into a
.NET Framework class. This class can then be used to dynamically process incoming
requests. (The .aspx file is compiled only the first time it is accessed: the compiled type
instance is then reused across multiple requests).

An ASP.NET page can be created simply by taking an existing HTML file and
changing its file name extension to .aspx (no modification of code is required). For
example, the following sample demonstrates a simple HTML page that collects a user's
name and category reference and then performs a form post back to the originating page
when a button is clicked.

ASP.NET provides syntax compatibility with existing ASP pages. This includes
support for <% %> code render blocks that can be intermixed with HIML content within an
.aspx file. These code blocks execute in a top-down manner at page render time.

Code-Behind Web Forms

ASP.NET supports two methods of authoring dynamic pages. The first is the method
shown in the preceding samples, where the page code is physically declared within the
originating aspx file. An alternative approach-known as the code-behind method--enables
the page code to be more cleanly separated from the HTML content into an entirely separate
file.

Introduction to ANP.NET Server Controls

In addition to (or instead of) using <% %> code blocks to program dynamic content,
ASP.NET page developers can use ASP.NET server controls to program Web pages.
Server controls are declared within an.aspx file using custom tags or intrinsic HTML tags
that contain a runat =”server” attributes value. Intrinsic HTML tags are handled by one of
the controls in the System. Web.UI.HtmlControls namespace. Any tag that does not
explicitly map to one of the controls is assigned the type of
System.Web.UI.HtmlControls.HmlGenericControl.

 ASP.NET Web Forms provide an easy and powerful way to build dynamic Web UI
 ASP.NET Web Forms pages can target any browser client
 ASP.NET Web Forms pages provide syntax compatibility with existing ASP pages.

BACK END DESCRIPTION

SQL SERVER

Microsoft SQL Server is a Structured Query Language (SQL) based, client/server


relational database. Each of these terms describes a fundamental part of the architecture of
SQL Server.
Database

A database is similar to a data file in that it is a storage place for data. Like a data
file, a database does not present information directly to a user; the user runs an application
that accesses data from the database and presents it to the user in an understandable format.

A database typically has two components: the files holding the physical database and
the database management system (DBMS) software that applications use to access data. The
DBMS is responsible for enforcing the database structure, including:

Maintaining the relationships between data in the database

Ensuring that data is stored correctly and that the rules defining data relationships are
not violated Recovering all data to a point of known consistency in case of system failures.

Relational Database

There are different ways to organize data in a database but relational databases are
one of the most effective. Relational database systems are an application of mathematical
set theory to the problem of effectively organizing data. In a relational database, data is
collected into tables.

When organizing data into tables, you can usually find many different ways to define
tables. Relational database theory defines a process, normalization, which ensures that the
set of tables you define will organize your data effectively.

Client/Server

In a client/server system, the server is a relatively large computer in a central location


that manages a resource used by many people. When individuals need to use the resource,
they connect over the network from their computers, or clients, to the server.

Examples of servers are: In a client/server database architecture, the database files


and DBMS software reside on a server. A communications component is provided so
applications can run on separate clients and communicate to the database server over a
network. The SQL Server communication component also allows communication between
an application running on the server and SQL Server.

Server applications are usually capable of working with several clients at the same
time. SQL Server can work with thousands of client applications simultaneously. The server
has features to prevent the logical problems that occur if a user tries to read or modify data
currently being used by others.
While SQL Server is designed to work as a server in a client/server network, it is also
capable of working as a stand-alone database directly on the client. The Scalability and
case-of-use features of SQL Server allow it to work efficiently on a client without
consuming too many resources.

Structured Query Language (SQL)

To work with data in a database, you must use a set of commands and statements
defined by the DBMS software. There are several different languages that can be used with
relational databases the most common is SQL Both the American National Standards
Institute (ANSI) and the International Standards Organization (ISO) have defined standards
for SQL.

SQL Server Features

Microsoft SQL Server supports a set of features that result in the following benefits

 Ease of installation, deployment and use SQL Server includes a set of


administrative and development tools that improve your ability to install, deploy,
manage, and use SQL Server across several sites.
 Scalability: The same database engine can be used across platforms ranging from
laptop computers running Microsoft Windows 98 to large, multiprocessor servers
running Microsoft Windows NT, Enterprise Edition.
 Data warehousing: SQL Server includes tools for extracting and analysing
summary data for online analytical processing (OLAP). SQL Server also includes
tools for visually designing databases and analysing data using English-based
questions.
 System integration with other server software :SQL Server integrates with e-mail,
the Internet and Windows.

Databases

A database in Microsoft SQL Server consists of a collection of tables that contain


data, and other objects, such as views, indexes, stored procedures, and triggers, defined to
support activities performed with the data. The data stored in a database is usually related to
a particular subject or process such as inventory information for a manufacturing
warehouse.

SQL Server can support many databases and each database can store either
interrelated data or data unrelated to that in the other databases. For example, a server can
have one database that stores personnel data and another that stores product- related data.
Alternatively, one database can store current customer order data, and another; related
database can store historical customer orders that are used for yearly reporting. Before you
create a database, it is important to understand the parts of a database and how to design
these parts to ensure that the database performs well after

it is implemented.
5.SYSTEM DESIGN

5.1 INTRODUCTION

Design is the first step in the development phase for any techniques and principles
for the purpose of defining a device, a process or system in sufficient detail to permit its
physical realization.
Once the software requirements have been analyzed and specified the software
design involves three technical activities – design, coding, implementation and testing that
are required to build and verify the software.
The design activities are of main importance in this phase, because in this activity,
decisions ultimately affecting the success of the software implementation and its ease of
maintenance are made. These decisions have the final bearing upon reliability and
maintainability of the system. Design is the only way to accurately translate the customer’s
requirements into finished software or a system.
Design is the place where quality is fostered in development. Software design is a
process through which requirements are translated into a representation of software.

5.2 LOGICAL DESIGN

System Flow Diagram

5.3 PHYSICAL DESIGN


5.3.1. DATABASE DESIGN

Donor Registration:

Field Name Data Type


Id
Name
Father Name
Dob
Gender
Weight
Blood Group

5.3. INPUT AND OUTPUT DESIGN

INPUT DESIGN:

The input design is the link between the information system and the user. It
comprises the developing specification and procedures for data preparation and those steps
are necessary to put transaction data in to a usable form for processing can be achieved by
inspecting the computer to read data from a written or printed document or it can occur by
having people keying the data directly into the system. The design of input focuses on
controlling the amount of input required, controlling the errors, avoiding delay, avoiding
extra steps and keeping the process simple. The input is designed in such a way so that it
provides security and ease of use with retaining the privacy. Input Design considered the
following things:

OBJECTIVES

 Input Design is the process of converting a user-oriented description of the input into
a computer-based system. This design is important to avoid errors in the data input
process and show the correct direction to the management for getting correct
information from the computerized system.
 It is achieved by creating user-friendly screens for the data entry to handle large
volume of data. The goal of designing input is to make data entry easier and to be
free from errors. The data entry screen is designed in such a way that all the data
manipulates can be performed. It also provides record viewing facilities.
 When the data is entered it will check for its validity. Data can be entered with the
help of screens. Appropriate messages are provided as when needed so that the user
will not be in maize of instant. Thus the objective of input design is to create an input
layout that is easy to follow.

OUTPUT DESIGN

A quality output is one, which meets the requirements of the end user and presents
the information clearly, In any system results of processing are communicated to the users
and to other system through outputs In output design it is determined how the information is
to be displaced for immediate need and also the hard copy output. It is the most important
and direct source information to the user Efficient and intelligent output design improves
the system's relationship to help use decision-making.

1. Designing computer output should proceed in an organized, well thought out


manner; the right output must be developed while ensuring that each output element
is designed so that people will find the system can use easily and effectively. When
analysis design computer output, they should Identify the specific output that is
needed to meet the requirements
2. Select methods for presenting information.
3. Create document, report, or other formats that contain information produced by the
system.
8. SYSTEM TESTING
System Testing is an important stage in any system development life cycle. Testing
is a process of executing a program with the intention of finding errors. The importance of
software testing and its implications with respect to software quality into be
overemphasized. Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding. A good test case is one
that has a high probability of finding a yet undiscovered error.

The purpose of testing is to discover errors. Testing is the process of trying to


discover every conceivable fault or weakness in a work product It provides a way to check
the functionality of components, sub-assemblies, assemblies and/or a finished product.

Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific
testing requirement.

UNIT TESTING

Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be conducted
as two distinct phases.

Test strategy and approach

Field testing will be performed manually and functional tests will be written in detail.

Test objectives

 All field entries must work properly.


 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.

Features to be tested

 Verify that the entries are of the correct format.


 No duplicate entries should be allowed.
 All links should take the user to the correct page.

INTEGRATION TESTING
Integration tests are designed to test integrated software components to determine if
they actually run as one program. Testing is event driven and is more concerned with the
basic outcome of screens or fields. Integration testes demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the
combination of components is correct and consistent. Integration testing is specifically
aimed at exposing the problems that arise from the combination of components.

Software integration testing is the incremental integration testing of two or more


integrated software components on a single platform to produce failures caused by interface
defects. The task of the integration test is to check that components or software applications,
e.g. components in a software system or- one step up- software applications at the company
level-interact without error.

Test Results : All the test cases mentioned above passed successfully. No defects
encountered.

ACCEPTANCE TESTING

Acceptance Testing checks the system against the "Requirements". It is similar to


systems testing in that the whole system is checked but the important difference is the
change in focus. Systems Testing checks that the system that was specified has been
delivered. Acceptance Testing checks that the system delivers what was requested. The
customer, and not the developer should always do acceptance testing. The customer knows
what is required from the system to achieve value in the business and is the only person
qualified to make that judgment.

User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

SYSTEM TESTING

Once the entire system has been built then it has to be tested against the “System
Specification" to check if it delivers the features required. It is still developer focused
although specialist developers known a systems testers are normally employed to do it. In
essence System Testing is not about checking the individual parts of the design, but about
checking the system as a whole. In effect it is one giant component. System testing can
involve a number of specialist types of test to see if all the functional and non-functional
requirements have been met.

FUNCTIONAL TEST

Functional tests provide systematic demonstrations that functions tested are available as
available as specified by the business and technical requirements, system documentation,
and user manuals.

Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted

Invalid Input : identified classes of invalid input must be rejected

Functions : identified functions must be exercised

Output : identified classes of application outputs must be exericised.

Systems Procedures : interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused an requirements key


functions, or special test cases. In addition, systematic coverage pertaining to fields,
predefined processes, and successive identify Business process flows data processes must
be considered for testing. Before functional testing is complete, additional tests are
identified and the effective value of current tests is determined.
9. SYSTEM IMPLEMENTATION
The process of putting the developed system to actual use is called as system
implementation. This application is successfully developed and implemented. This
application satisfies the entire requirement posted in the proposed system. Implementation
is the process of converting a new or revised program into an operation. The process of
putting the developed system to actual use is called system implementation.

Types

There are three types of implementation

 Implementation of computer system replaces a manual work.


 Implementation of a new computer system to replace an existing one
 Implementation of a modified application to replace an existing one using the same
computer.

Implementation Review

It is a formal process to determine how well the system is working, how it has been
accepted and whether adjustments are needed. It is also important to gather information for
the maintenance.

The system is implemented to satisfy all the requirements specified in the proposed
system. The system is implemented as a new form of the existing websites for the concern.

This system is implemented with the help of ASP.NET features. The forms are
designed with web server controls in a user-friendly manner. The data are properly
maintained in the back end as MYSQL server.
10.FUTURE ENHANCEMENT

As there was a little number of contact person's information giving, some people
may face difficulty in getting, blood fast. So i like to gather more information regarding he
contact persons in other cities and will provide much more service for the people and help
everyone with humanity. This service will provide the special compliments for the regular
blood donor.
11.CONCLUSION

This project presents an overview of data mining and its techniques which have been
used to extract interesting patterns and to develop significant relationships among
variables stored in a huge dataset. Data mining is needed in many fields to extract the
useful information from the large amount of data. Large amount of data is maintained
in every field to keep different records such as medical data, scientific data,
educational data, demographic data, financial data, marketing data etc. Therefore,
different ways have been found to automatically analyze the data, to summarize it, to
discover and characterize trends in it and to automatically flag anomalies. The data
mining techniques are used to do classification, to do clustering, to find interesting
patterns. In our future work, the data mining techniques will be implemented on
blood donor’s data set for predicting the blood donor’s behavior and attitude, which
have been collected from the blood bank centers.

You might also like