SYNOPSIS

An individual from whom blood, tissue, or an organ is taken for transfusion,

implantation, or transplant. Potential donors are evaluated for anything that might make
their blood unsafe to use. The screening includes testing for diseases that can be transmitted
by a blood transfusion, including HIV and viral hepatitis. The donor must also answer
questions about medical history and take a short physical examination to make sure the
donation is not hazardous to his or her health. How often a donor can give varies from days to
months based on what he or she donates and the laws of the country where the donation takes
place.

This project is aimed to serve the people to provide the information about the donors
detail for blood in emergency situations like operations, accidents, delivery etc. This project
was also used to store the details of organ transplantation throughout the Government
Hospitals and other private hospitals. All the process is executed for voluntary based service
only.

A donor in general is a person who donates something voluntarily. Usually used to

represent a form of pure altruism but sometimes used when the payment for a service is
recognized by all parties as representing less than the value of the donation and that the
motivation is altruistic

A blood donation occurs when a person voluntarily has blood drawn and used for
transfusions or made into medications by a process called fractionation. In the developed
world, most blood donors are unpaid volunteers who give blood for a community supply.

1
 1. INTRODUCTION

1.1. PROJECT OVERVIEW

In poorer countries, established supplies are limited and donors usually give blood
when family or friends need a transfusion. Many donors donate as an act of charity, but some
are paid and in some cases there are incentives other than money such as paid time off from
work. A donor can also have blood drawn for their own future use. Donating is relatively
safe, but some donors have bruising where the needle is inserted or may feel faint.

This project also provides the details of eye donor, human part transplantation donors.
The requisition about blood details contains the type of blood, requested date, place and units.

MODULES
This project consists of six major modules. They are:
 Information
 Application
 Donar Detail
 Requisition
 Service Branches
 Reports

INFORMATION
There are so many known and unknown information’s about blood donation and
organ transplantation. This module clears all the doubts and make awareness about the blood
donation and transplantation. It displays the type of disease, causes, possible for donation or
not are also placed.

APPLICATION
This application module is used to accept the information about the volunteer’s profile
whose who are willing to join in this group. This application requires the blood type, blood
group, diseases, pressures, identification details about the person etc.

2
DONOR DETAIL
After submitting the application form to the donor’s association, they enquiry some
interview and verification about the applicant. After the successful of verification, the
applicant will be permitted to donate blood and other transplantation. This module consists of
applicant name, address, mobile number, email id etc.

REQUISITION
The requisition module plays a vital role in this project. The blood will be required for
major operations, accidents, and other purpose. For that situation, this module is designed for
two purposes like Immediate and advance booking. Immediate is mainly for accidents and
urgent requirement of blood. Advance booking is used to place a request for a particular day
such as post operation.

SERVICE BRANCHES
This module is used to show all the service branches both government and private in
different places throughout the Sivagangai District. This is used to provide the information of
the nearest service center and enquiry for any urgent requirements.

REPORTS
Reports are the main task in every process. This module is used to sort all the records
by the user’s criteria in the enhanced GUI supported screen. This also gives the information
about date wise requisition; donor’s those who are having the eligibility for blood donation
etc.

3
1.2. ORGANIZATION PROFILE
Thamizh Technologies is a professionally managed organization providing total HR
Solutions, Recruitments, Outsourcing and Training to various companies. We provide
services to various types of students which include Engineering, IT, Management department
etc.

 GROUP
We have an enviable history of providing high quality services in the fields of R&D,
Design and Development, Training and HR Consulting in Sivaganga. Our organization has
already established its reputation in offering High quality education in the areas of
Engineering, Arts, Science, and Management Courses.

We have a well-documented quality system, which helps us to monitor measure and

analyze our performance and also to improve our service and delivery standards. We have a
dedicated team of people for monitoring the quality norms.

SERVICES
We dedicate our trainees in Software Development, Human Resource Consulting,
Academic Assistance and Training.

4
 2. SYSTEM SPECIFICATION

2.1. HARDWARE SPECIFICATION

 Main Processor : Pentium Dual Core or above
 RAM : 2 GB DDR-III.
 Display Type : SVGA
 Hard Disk : 160 GB
 Keyboard : 108 Keys
 Mouse : Optical Mouse.

2.2. SOFTWARE SPECIFICATION

 Operating System : Windows 7 or Later
 Front End : VB.NET 2010.
 Back End : MS-ACCESS.
 Database Connectivity : ADO.NET

2.3. SOFTWARE OVERVIEW

VB.Net, the next generation of visual basic is designed to be the easiest and most
productive tool for creating .NET applications, including Windows applications, Web
Services and Web applications. Visual Basic .NET is a major component of Microsoft Visual
Studio .NET suite. The .NET version of Visual Basic is a new improved version with more
features and additions. After these new additions, VB qualify to become a full object-oriented
language such as C++. VB.NET is the following version of VB 6.0. Microsoft .NET is a new
programming and operating framework introduced by Microsoft. All .NET supported
languages access a common .NET library to develop applications and share common tools to
execute applications. Programming with visual basic using .net is called VB.Net.

While providing the traditional ease-of-use of Visual Basic development, Visual

Basic .NET also allows optional use of new language features. Inheritance, method
overloading, structured exception handling, and free threading all make Visual Basic a
powerful object-oriented programming language. Visual Basic .NET fully integrates with
the .NET Framework and the Common Language Runtime, which together provide language
interoperability, simplified deployment, enhanced security, and improved versioning support.
5
.NET FRAMEWORK
The .NET Framework is an environment for building, deploying, and running Web
Services and other applications. It is the infrastructure for the overall .NET Platform. The
framework consists of three main parts: the Common Language Runtime, the class libraries,
and VB.NET.

The Common Language Runtime and class libraries, including Windows Forms,
ADO.NET, and VB.NET, combine together to provide services and solutions that can be
easily integrated within and across a variety of systems. The .NET Framework provides a
fully managed, protected, and feature-rich application execution environment, simplified
development and deployment, and seamless integration with a wide variety of languages.

OVERVIEW OF THE .NET FRAMEWORK

The .NET Framework is a managed, type-safe environment for application
development and execution.
 It allocates memory for the storage of data and instructions
 Grants or denies the appropriate permissions to your application
 Initiates and manages application execution
 Manages the reallocation of memory for resources that are no longer needed.

The .NET Framework consists of two main components

 The Common Language Runtime and
 The .NET Framework class library.

COMMON LANGUAGE RUNTIME

The common language runtime can be thought of as the environment that manages
code execution. It provides core services such
 Code compilation
 Memory allocation
 Thread management, and
 Garbage collection

6
.NET FRAMEWORK CLASS LIBRARY
The .NET Framework class library provides a collection of useful and reusable types
that are designed to integrate with the common language runtime.
 Types are object-oriented and
 Fully extensible

LANGUAGES AND THE .NET FRAMEWORK

The .NET Framework is designed for cross-language compatibility. This means
that .NET components can interact with each other no matter what language they were
originally written in. This level of cross-language compatibility is possible because of the
common language run time. When a .NET application is compiled, it is converted from the
language it was written in Visual Basic .NET, C#, or any other .NET compliant language to
Microsoft Intermediate Language (MSIL or IL). This is a low-level language designed to be
read and understood by the common language run time. Because all .NET executables and
DLLs exist as intermediate language, they can freely interoperate.

The Common Language Specification defines the minimum standards that .NET
language compilers must conform to, and thus ensures that any source code compiled by a
.NET compiler can interoperate with the .NET Framework. The Common Type System
ensures type compatibility between .NET components. Because .NET applications are
converted to IL prior to deployment and execution, all primitive data types are represented
as .NET types. Thus, a Visual Basic Integer and a C# int are both represented in IL code as a
System.Int32. Because both languages use a common and interconvertable type system, it is
possible to transfer data between components and avoid time-consuming conversions or hard-
to-find errors.

THE STRUCTURE OF A .NET APPLICATION

The primary unit of a .NET application is the assembly. An assembly is a self-
describing collection of code, resources, and metadata. The assembly manifest contains
information about what is contained within the assembly. The assembly manifest provides
 Identity information, such as the name and version number of the assembly.
 A list of all types e7osed by the assembly.
 A list of other assemblies required by the assembly.

7
 Each assembly has one and only one assembly manifest, and it contains all the
description information for the assembly. The assembly manifest can be contained in its own
separate file, or it can be contained within one of the assembly's modules.

COMPILATION AND EXECUTION OF A .NET APPLICATION

When you compile a .NET application, it is not compiled to binary machine code;
rather, it is converted to IL, which is a low-level set of instructions understood by the
common language run time. This is the form that your deployed application takes—one or
more assemblies consisting of executable files and DLL files in IL form. At least one of these
assemblies will contain an executable file that has been designated as the entry point for the
application.

When execution of your program begins,

1. The first assembly is loaded into memory.
2. If the application passes the system's security policy, the common language run time
executes the code.
3. It creates a process for the application to run in and begins application execution.
4. When execution starts, the first bit of code that needs to be executed is loaded into
memory and compiled into native binary code from IL by the common language run
time's Just-In-Time (JIT) compiler.

8
Some of the services provided by the Execution Support are
 Automatic Memory Management
 Security
 Interoperability with Unmanaged Code
 Cross – Language Debugging Support
 Enhanced Deployment and Versioning Support

COMPONENTS OF CLR

VISUAL BASIC TO VISUAL BASIC.NET

There are significant changes to the language:
 A new optional Error handling structure
 Namespaces
 True Inheritance
 Free threading, and many others.

.NET also provides many other features, such as garbage collection for freeing up
resources, true inheritance for the first time, debugging that works across languages and
against running applications, and the ability to create Windows services and console
applications.

9
COMMON TYPE SYSTEM
The Common Type System specifies the types supported by the CLR. The types
specified by the CLR include
 Classes — the definition of what will become an object; includes properties, methods,
and events
 Interfaces — the definition of the functionality a class can implement, but does not
contain any implementation code
 Value Types — User-defined data types that are passed by value
The type system sets out the rules that language compilers must follow to produce
code that is cross-language compatible. By following the type system, vendors can produce
code that is guaranteed to work with code from other languages and other compilers because
all languages are consistent in their use of types.

INTEGRATED DEVELOPMENT ENVIRONMENT

Visual Studio .NET provides a single integrated development environment (IDE) that
helps developers build solutions faster using key productivity features accessible by any
.NET language. The IDE is a completely customizable cockpit that enables the highest
performance for developers.  It provides unified access to the designers, editors, and tools of
Visual Studio from any .NET language.

In this system, the concept of ADO.NET will have different requirements for working
with data. In some cases, the user might simply want to display data on a form. In other cases,
the user might need to device a way to share information with another company. The user
might never need to know some of the details of data handling — for example, user might
never need to directly edit an XML file containing data — but it is very useful to understand
the data architecture in ADO.NET.

In traditional client/server applications, components establish a connection to a

database and keep it open while the application is running. Open database connections take
up valuable system resources. In most cases, databases can maintain only a small number of
concurrent connections. The overhead of maintaining these connections detracts from overall
application performance.

10
 Similarly, applications that require an open database connections are extremely
difficult to scale up. An application that does not scale up well might perform acceptably with
four users but will likely not to do so with hundreds.

A model based on always-connected data can make it difficult and impractical to

exchange data across application and organizational boundaries using a connected
architecture. If two components need to share the same data, both have to be connected, and a
way must be devised for the components to pass data back and forth.

For all these reasons, data access with ADO.NET is designed around an architecture
that uses connections sparingly. Applications are connected to the database only long enough
to fetch or update the data. Because the database is not holding on to connections that are
largely idle, it can service many more users of languages.

ADO.NET
ActiveX ® Data Objects.NET (ADO.NET), formerly known as ADO+, is a new set of
classes that e7ose the data access services of the .NET Framework. ADO.NET is a natural
evolution of ADO and is built around N-Tier application development. ADO.NET has
been created with XML at its core. The ADO.NET object model is composed of two central
components: the connected layer, which consists of the classes that comprise the .NET Data
Provider, and the disconnected layer, which is rooted in the Dataset. 

.NET Data Providers includes the following components: the Connection object, the

Command object, the Data Reader, and the Data Adapter. The first two should be familiar
to existing ADO programmers; they are used to open a connection to a data source and
execute a command against it. The Data Reader loosely corresponds to a forward-only, read-
only

ADO.NET is essentially a collection of classes that e7ose methods and attributes used
to manage communications between an application and a data store. An integral part of the
.NET Framework, ADO.NET simplifies integration of data sharing in distributed VB.NET
applications.ADO.NET is an e7ansion of ADO with some of the key concepts retained.
ADO.NET has greatly extended to provide access to structured data from diverse sources,
which are all accommodated in a consistent, standardized programming model. ADO.NET
11
can be used in any consumer application that needs to connect to, and communicate with,
data sources such as Microsoft SQL Server, as well as data sources e7osed via OLE DB and
XML.

The ADO.NET object model is made up

 Data View
 Data Set
 Data Provider

DATA VIEW
The Data View speaks to the Dataset and is a special class designed for objects to
bind to and can provide customized views of the Data Set. It provides methods and properties
that enable objects such as a Data Grid to bind to a Dataset and contains properties such as
Allow Edit and Count that allow the object to work with the data in meaningful ways. A Data
View is only used in conjunction with a Dataset and never with a Data Reader.

DATA SET
The Dataset is the core component of the disconnected architecture of ADO.NET that
caches data locally on the client. The Dataset is e7licitly designed for data access independent
of any data source. As a result it can be used with multiple and differing data sources, XML
data, or used to manage data local to the application. The Dataset contains a collection of one
or more Data Table objects made up of rows and columns of data, as well as primary key,
foreign key, constraint and relation information about the data in the Data Table objects.

DATA PROVIDER
The Data Provider connects to the database on behalf of ADO.NET. It encapsulates all
connections to a database. The Data Provider containing some objects in it:
 Connection
 Command
 DataAdaptor
 DataReaderS

12
CONNECTIONS
Connections are part of a Data Provider and the Connection object provides
connectivity to a data source. Connections can be opened in two ways:
1. E7licitly by calling the Open method on the connection;
2. Implicitly when using a DataAdapter.

CLOSING THE CONNECTION

We must always close the Connection when we are finished using it. This can be done
using either the Close or Dispose methods of the Connection object. Connections are not
implicitly released when the Connection object falls out of scope or is reclaimed by garbage
collection.

COMMANDS
The Command object enables access to database commands to return data, modify
data, run stored procedures, and send or retrieve parameter information. Commands contain
information that is submitted to a database as a query, and, like connections, are represented
by the provider-specific classes SqlCommand and OleDbCommand. Functionally, once the
Connections are established and the Commands are executed the results are in the form of
streams. These resultant streams can be accessed either by DataReader object, or passed into
a DataSet object via a DataAdapter. The SqlCommand class provides four different methods
to execute a command. They are: ExecuteReader, ExecuteNonQuery, ExecuteScalar and
ExecuteXmlReader.

DATA ADAPTERS
The DataAdapter provides a set of methods and properties to retrieve and save data
between a DataSet and its source data store. It does the actual work of putting returned data
from a database into a DataSet. It also manages reconciling how data should be updated
against a database. Connections and Commands whose properties are set early on in code are
often passed into DataAdapters for use when their action methods are invoked. The
DataAdapter object encapsulates a set of data commands and a database connection, which
are used to fill the DataSet and update the data source.

13
DATA READERS
When dealing with large read only data, e.g. reading 5,000 rows of data, the .NET
framework includes the DataReader object, which is a read-only, forward-only stream
returned from the database record set. It is a highly optimized, no buffering, and fire hose-
style interface for getting the results of a query executed against the data source. The Data
Adapter provides the bridge between the .NET Data Providers and the Dataset. The Dataset
is a local buffer of tables or a collection of disconnected record sets.

BACK END: MS-ACCESS

A database program for windows, available separately or included in the Microsoft
office suite. Access is programmable using visual basic for applications (VBA). Access can
read Paradox, dBase and Btrieve files, and using ODBC, Microsoft SQL Server, SYBASE
SQL Server and Oracle data.

Microsoft Access (current full name Microsoft Office Access) is a relational database
management system from Microsoft, packaged with Microsoft Office Professional which
combines the relational Microsoft Jet Database Engine with a graphical user interface.

Microsoft Access can use data stored in Access/Jet, Microsoft SQL Server, Oracle, or
any ODBC-complaint data container. Skilled software developers and data architects use it
to develop application software. Relatively unskilled programmers and non-programmer
“power users” can use it to build simple applications. It supports some object-oriented (OO)
techniques but falls short of being a fully OO development tool.

Microsoft Access was also the name of a communications program from Microsoft,
meant to compete with ProComm and other programs. This Microsoft Access proved a
failure and was dropped. Years later Microsoft reused the name for its database software.

FEATURES
One of the benefits of Access from a programmers perspective is its relative
compatibility with SQL – queries may be viewed and edited as SQL statements, and SQL
statements can be used directly in Macros and VBA Modules to manipulate Access tables.
Users may mix and use both VBA and “Macros” for programming forms and logic and offers
object-oriented possibilities.
14
 MSDE (Microsoft SQL Server Desktop Engine) 2000, a mini-version of MS SQL
Server 2000, is included with the developer edition of Office 7 and may be used with Access
as an alternative to the Jet Database Engine.

Unlike a complete RDBMS, the Jet Engine lacks database triggers and stored
procedures. Starting in MS-Access 2000(Jet 4.0), there is a syntax that allows creating
queries with parameters, in a way that looks like creating stored procedures, but these
procedures are limited to one statement per procedure. Microsoft Access does allow forms to
contain code that is trigged as changes are made to the underlying table (as long as the
modifications are done only with that form), and it is common to use pass-through queries
and other techniques in Access to run stored procedures in RDBMS that support these.

In ADP files (supported in MS Access 2000 and later), the database-related features
are entirely different, because this type of file connects to a MSDE or Microsoft SQL Server,
instead of using the Jet Engine. Thus, it supports the creation of nearly all objects in the
underlying server (tables with constraints and triggers, views, stored procedures and UDF-s).
However, only forms, reports, macros and modules are stored in the ADP file (the other
objects are stored in the back-end database).

OPERATING SYSTEM : WINDOWS 7

Microsoft Windows 7 is software program that makes IBM PC systems easy to use, it
does this by simplifying the computers. User Interface is a buzzword that refers to the way
we give commands to the computer and the way in which we interact with it.

With windows the user can run programs, enter and move data around and performs
DOS tasks by simply using the mouse to point objects on the screen. Windows owes its name
to the fact it runs each program or each document in its own separate window. Further, the
user can have any number of Windows on the screen at time, each containing its own
program. It is possible to switch between windows easily.

Another advanced feature in windows is that it has clipboard facility. It lets the user to
copy data of different document types, make it easy to cut and paste information from one
application to another.

15
FEATURES OF WINDOWS 7
Microsoft windows 7 is more compatible and more powerful than any workstation
that you have used before.
- Easier to use
- Easier to manage
- More compatible and Powerful

EASIER TO USE
Windows 7 makes it easier to:
- Work with files
- Find information
- Personalize your computer environment
- Work on the web Work remotely

WINDOWS 7 ALSO PROVIDES

- Improved Driver support
- Increased support for new generation hardware and
multimedia technologies
- Integration of new Symbols

MORE POWERFUL
Windows 7 provides
- Industrial Strength reliability
- The highest level of security
- Powerful performance

DISTRIBUTED PROCESSING
Windows 7 allows the connectivity with variety of host environment through its
support of multiple transport protocol an client server facilities.

16
 3. SYSTEM ANALYSIS

A single-user application which is typically found on a desktop computer there is no

need for any access control - the user has access to every function within the application.
However, in a multi-user application which is deployed over numerous devices which are
linked together in a network it is more than likely that not all functionality will be available to
all users.

In this situation a method is required to allocate a suitable person for the correct job at
correct time and maintain the donor, program and applicant details, requisition of blood and
other organ transplantation information whereby functions within the application can only be
accessed by persons to whom permission has been granted.

3.1. EXISTING SYSTEM

 Existing System available in this case are less sensitive; that means they won’t take
care of the failure conditions of any attempts other than login, security modules.
 The system to be developed is must be taken much care in implementing the logging
module, otherwise the storage area and the memory consumed for that case will
exceed the normal limit.
 It may require additional settings to be done to maintain them for analysis.

DRAWBACKS OF EXISTING SYSTEM:

 Automatic reporting system, responding system is not yet implemented fully in the
security maintenance applications.
 Manual supervising required in all the cases to realize the severity of an issue taken
place in any part of the application.
 Security log file, Database entries for future analysis purpose and immediate
intimation to the management category users through mails are not yet implemented
in the existing system.

17
3.2. PROPOSED SYSTEM
Maintaining different category wise security using the types like roles,
responsibilities, and the links with the above two to assign user roles.

NEED FOR PROPOSED SYSTEM

 Reporting and with the case maintenance with the severity level is easily give the
identity of the event traced and the response to be taken against the system.

 Automatic mailing to the users with the administrative category users will the next
added advantage over all the systems present. Since they are all automated the
hacking possibility is totally reduced to considerable extend in our system.

 Analysis will give as further implementation of the system more secured, and the
design of the future system can be modified as per the results of the analysis of the
system proposed.

 Process can be assigned to the donor to identify the category level with configured
identity e7lains the development design involved behind the application.

System proposed in entirely new to the world with the web technology and
application wise security enhancement. Since in all the cases all the systems will take care of
the positive results from the users and they normally won’t care of the issues regarding the
failures, which only can prove the applications reliability and user interface, and mainly the
accessibility control. Our application will surely met that criteria and it can be included to any
module to support the same.

18
3.3. FEASIBILITY STUDY
Feasibility is the determination of whether or not a project is worth doing. the
processes is followed in making this determination is called a feasibility study is the test of
system proposal according to its work ability impact on the organization ability to meet users
needs, and effective use of resources the result feasibility is a formal proposal.

This simply reports – a formal document detailing the nature and scope of the
proposed solution. The main objective of the feasibility study is test the technical, social and
economic feasibility of developing a computer system. this is done by investigation the
existing system in the area under investigation and generating ideas about a new system.

On studying the feasibility of the system three major consideration are deal with, to
find whether the automation of the system feasible.

TECHNICAL FEASIBILITY
All the process of the enterprise is managed in manually. In manual system, the data
storage, data security is very tedious. And it is very difficult to secure and maintain for long
years without any damages or corruptions. Redundancy, misusing of data are the main
problems by using manual process.

Its also takes much of time to retrieve a particular information and some more man
powers are needed. Manage and maintain large amount of data by a single person is not
possible. So many problems raised like storage space, maintenance etc. Much of time will be
spent for to consolidate for a group of data, which was need by the user. Correction or
modification of data makes a way for malfunction.

ECONOMICAL FEASIBILITY
All the problems which are denoted in the existing systems are overcome. The data will
be secured with authentication by providing passwords. The retrieval of data is much faster
than the manual processing. The user can create their reports within a time. There is no data
redundancy, malfunction, data mismatching, timely execution, concurrent updating are the
advantages placed in this project.

19
 4. SYSTEM DESIGN

The design of the system is essentially a blue print or a plan for a solution for the
system. At the first level the focus is made which modules are needed for the system and how
modules should be interconnected. This is called system design.

In the second level, the internal design of the modules and how the specification of
the module can be satisfied is decide upon. Thus design level is called detailed design. Since
the detailed design delineates the major characteristics of the system and also its efficiency. A
Design methodology is a systematic approach to create a design by application of a set of
techniques and guidelines.

ARCHITECTURAL DESIGN

20
PROCESS FLOW DIAGRAM

21
4.1. DATAFLOW DIAGRAM
Data Flow Diagram (DFD) is a directed graph in which the nodes specify processing
activities and the arcs specify data items transmitted between processing nodes. Data Flow
Diagrams are excellent mechanisms for communicating with customers during analysis. Data
Flow Diagram are quit valuable for establishing naming conventions and names of system
components such as subsystems, files and data link.

DFD is used to represent the functional relationship of input, process and output
values presented by system. DFD shows how information moves through the system and how
it is modified by series of transformation that are applied as data moves from input to output.
DFD may be used to represent a system at any level of abstraction.

A DFD also called context diagram represents entire system as a single module with
input to output data indicated by incoming and outgoing allows respectively. Additional
processes and information flow paths are represent as a DFD is partitioned to reveal more
detail represent the system with major modules, data flows and data stores, the other levels
will show each module in the top level DFD in a more detailed fashion.

LEVEL – 0

22
LEVEL - 1

23
4.2. INPUT DESIGN
Identification of the correct input and output for a system are the major parts of a
system analysis. During the System analysis the provider’s and seeker’s needs, the data
stores, the key system elements are identified. Based on this identification the input to be
provided to the system and the outputs that are to be generated and their formats are decided.
The Input Design is the kind that ties the information system into the World of its users.
Output refers to the results that are generated by the system. The design decision for handling
input specified how data are accepted for computer processing.

OBJECTIVES OF INPUT DESIGN

The quality of system input determines the quality of system output. Input
specification describes the manner in which data enter the system for processing. Input
design features can ensure the reliability of the system and produce results from accurate
data, or they can result in the production of erroneous information. The input design also
determines whether the user can interact efficiently with the system.

Four Objectives guiding the design of the input focus on

 Effectiveness
 Accuracy
 Easy to use
 Consistency
 Effectiveness
This means that input forms and screens serve specific purposes.
 Accuracy
Refers to design that assures proper completion.
 Easy to Use
Means that forms and screens should are straight forward and require no extra
time to understand.
 Consistency
Means that forms and screens should group data of similar nature together.

24
4.3. OUTPUT DESIGN
One of the most important features of an information system for users is the output it
produces. Output is the information delivered to the users through the information system.
Without quality output, the entire system may appear to the unnecessary that users will avoid
using it. Users generally merit the system solely by its output. Therefore an effective output
design is an important feature of design specifications.

OBJECTIVE OF THE OUTPUT DESIGN

Since useful output is essential to gaining use and acceptance of the system, the
system analyst should try and follow the following objectives, which are useful for designing
acceptable outputs.
 Design the output to serve the intended purpose.
 Design the output to fit the users.
 Deliver the appropriate quantity of output.

25
4.4. DATABASE DESIGN
Database Name: MyDB
TableName:Information
FIELD NAME FIELD TYPE FIELD SIZE DESCRIPTION

SNo Number Long integer Serial number

Stype Text 50 Disease type
Doornot Text 50 Donate Or Not
Sumry Text 250 Summary

TableName:Application
FIELD NAME FIELD TYPE FIELD SIZE DESCRIPTION
Appid Number Long integer Applicant id number
Appname Text 50 Applicant name
Fname Text 50 Applicant father name
Dob Text 50 Date of birth
Address Text 250 Address
City Text 50 City
Height Number Long integer Height
weight Number Long integer Weight
Phno Number Long integer Phone number
Email Text 50 Email id
Rcid Number Long integer Recommend id number
Rcname Text 50 Recommend name
Applyby Text 50 Apply by
Proof id type Text 50 Proof id type
Proof id no Number Long integer Proof id number
Photo Text 50 Photo

TableName:DonarsDetails
FIELD NAME FIELD TYPE FIELD SIZE DESCRIPTION
Did Number Long integer Donar id number
Dname Text 50 Donar name
Fname Text 50 Donar father name
Dob Text 50 Date of birth
Address Text 250 Address
City Text 50 City
Blood group Text 50 Blood group
Height Number Long integer Height
Weight Number Long integer Weight
Phno Number Long integer Phone number
Email Text 50 Email id
Photo Number Long integer Photo
Doj Text 50 Date of joining
Proof id type Text 50 Proof id type

26
Proof id no Number Long integer Proof id number
Last donated Text 50 Status
Status Text 250 Summary
Other transplanted Text 50 Other transplanted type
type

TableName:Requisition
FIELD NAME FIELD TYPE FIELD SIZE DESCRIPTION
Rid Number Long integer Requisition id
Rtype Text 50 Requisition type
Sumry Text 50 Summary
Redate Text 50 Requistion date
Applyname Text 50 Applicant name
Address Text 50 Address
City Text 50 City
Phno Number Long integer Phone number
Email id Text 50 Email id

TableName:BranchDetails
FIELD NAME FIELD TYPE FIELD SIZE DESCRIPTION
Bid Number Long integer Branch id number

Bname Text 50 Branch name

Address Text 250 Address
City Text 50 City
Phno Number Long integer Phone number
Email Text 50 Email id

TableName:Program
FIELD NAME FIELD TYPE FIELD SIZE DESCRIPTION
Pid Number Long integer Program id number
Pname Text 50 Program name
Date Text 50 Date
Time Number Long integer Time
Place Text 50 Place
City Text 50 City
Conducted by Text 50 Conducted by

27
 5. SYSTEM IMPLEMENTATION

Implementation is the stage, which is crucial in the life cycle of the new system
designed. This project “Donor’s Chronicle System” was implemented on VB.NET 2010 as
Frontend. The main stage in the implementation is planning, training, system testing.
Implementation is converting a new or revised system into an operational one.

Conversion is the main aspect of implementation. It is the process of changing from

the old system to the new one. After system is implemented, user conducts a review of the
system. It is used to gather information for the maintenance of the system. The basic review
method is a data collection method of questionnaire, interview etc.

The proposed system is implemented by direct method in which a new a system will
be designed and implemented. The implementation plan consists of testing.
 Developed system with a high capacity.
 Detection and correction of errors.
 Making necessary changes in the system.
 Checking the report with that of the existing system

28
 6. SYSTEM TESTING

The system “Donor’s Chronicle System” as a whole was deployed in the VB.NET
2010 and was tested. The system was found to be working perfect and an end user has been
asked to enter the data, and further the connected systems has been tested with the sample.

6.1. UNIT TESTING

Unit testing different modules are tested against the specifications produced during
the design of the modules. Unit testing is essential for Verification of the code produced
during the coding phase and hence the goal is to test the internal logic of the modules. Using
the details design description as a guide, important paths are tested to uncover errors within
the boundary of the Modules.

In the project, the login details of the user are being verified by various conditions.
All the conditions are satisfied, then after the user go to visit the system project.

This testing was carried out during the programming stage itself.
 Performance Test
 Stress Test

PERFORMANCE TESTING
It determines the amount of execution time spent in various parts of the unit, program
throughput, and response time and device utilization by the program unit. To recover the
project from the slow response time, try to avoid of apply the looping statement instead of the
control statements.

STRESS TESTING
Stress Test is those test designed to intentionally break the unit. A Great deal can be
learned about the strength and limitations of a program by examining the manner in which a
programmer in which a program unit breaks.

29
6.2. SYSTEM TESTING
System Testing involves two kinds of activities: Integration Testing and Acceptance
Testing. Strategies for integrating software components into a functioning product include the
bottom-up strategy, the top-down strategy and the sandwich strategy. Acceptance Testing
involves planning and execution of the functional tests, performance tests and the stress tests
to verify that the implemented system satisfies its requirements.

The System testing does not test the module wise, but the integration of each module
in the systems. System testing helps to find in discrepancies between the original objectives
of the system.

6.3. ACCEPTANCE TESTING

Acceptance testing is done with live data provided by the administrator to ensure that
the software works satisfactorily. Acceptance testing focuses on the external behavior of the
system. Giving inputs from actual data tested the system and the results were found to be
satisfactory.

The inputs are well verified by different conditions at different stages. Suppose the
user may give wrong username or password, then the system will inform the wrong entry.
The ID will be automatically generated for to avoid the redundancy and duplication.

6.4. INTEGRATION TESTING

System has been partitioned into sub Modules. The integration of them must be
subjected to a strong checking, so that data gets prevented from loss across the interface.
Thus Integration Testing system is subjected to integration.

Here donor detail is the base of the project. The applicants and requisition detailed
report for the donation are maintained under the same category. They can order by the
requisition for a particular date and blood group.

30
 7. CONCLUSION

The “Donor’s Chronicle System” has been developed for the present requirement of
volunteer blood donation and organ transplantation and it works satisfactorily under all
circumstances that may arise in the real environment. It caters to need of the volunteers
effectively and easy to handle.

The programming convention followed ensures future updating such as applicant

information, donor’s profile, general information, programs, awareness camps details,
requisition of blood for urgent operations or booked surgeries. Future enhancement
capabilities can be carried out without having to perform too many environment and
correction of software bugs. This newly development system consumes less processing time
and high productivity. Since screens are user friendly and user get familiarized with use it.

The data generated with live data have proved to be information and also helpful in
making important decisions. This newly developed project consuming less processing time
because all the process are assumed to a single event and high productivity. The system is
designed to be highly flexible so that any future modifications and requirement can be easily
incorporated without much design complications.

31
 8. BIBLIOGRAPHY

BOOK REFERENCE
o Essential .NET, James S.Miller, Tata McGraw Hill Publications, 2002 Second
Edition.

o Visual Basic.NET Programming, Matt J.Crouch, Neway Publicatons Private Limited,

Third Edition, 2003.

o Programming in the .NET Environment, Damien Watking, Mark Hammond, Brand

Abrams, APress S Publications, 2002.

o Software Engineering Concepts, Richard E.Fairly, Tata McGraw-Hill Education

Private Limited,20s11.

WEBSITE REFERENCE
. http://code.msdn.microsoft.com/GotDotNet.aspx

. http://www.devarticles.com/c/b/MSACCESS/

. http://www.vbdotnetheaven.com/

32
 9. APPENDIX

(A) SCREEN LAYOUTS

33
34
35
36
37
38
39
40
41
42
43
44
45
(B) SAMPLE SOURCE CODE

Public Class infor

Dim con As New OleDb.OleDbConnection
Dim cmd As New OleDb.OleDbCommand
Dim dr As OleDb.OleDbDataReader

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button1.Click
ListView1.Items.Clear()
con = New OleDb.OleDbConnection("provider=microsoft.Jet.OLEDB.4.0;Data
source=" & System.AppDomain.CurrentDomain.BaseDirectory & "MyDB.mdb;")
con.Open()
cmd = New OleDb.OleDbCommand("select * from Infor", con)
dr = cmd.ExecuteReader
If (dr.HasRows = 0) Then
MsgBox("no record found")
Else
Do While dr.Read
Dim mylist As New ListViewItem
mylist.Text = dr(0).ToString
mylist.SubItems.Add(dr(1).ToString)
mylist.SubItems.Add(dr(2).ToString)
mylist.SubItems.Add(dr(3).ToString)
ListView1.Items.Add(mylist)
Loop
End If
con.Close()
End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button2.Click
Dim a, b, c, d
a = Val(TextBox1.Text)
b = TextBox2.Text
c = Label5.Text
d = TextBox3.Text
con = New OleDb.OleDbConnection("provider=microsoft.Jet.OLEDB.4.0;Data
source=" & System.AppDomain.CurrentDomain.BaseDirectory & "MyDB.mdb;")
con.Open()
cmd = New OleDb.OleDbCommand("insert into Infor values(" & a & ",'" & b & "','" &
c & "','" & d & "')", con)
cmd.ExecuteNonQuery()
MsgBox("record add")
46
 con.Close()
End Sub

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button3.Click
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox2.Focus()
End Sub

Private Sub RadioButton1_CheckedChanged(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles RadioButton1.CheckedChanged
If RadioButton1.Checked Then
Label5.Text = "Donate"
End If
End Sub

Private Sub RadioButton2_CheckedChanged(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles RadioButton2.CheckedChanged
If RadioButton2.Checked Then
Label5.Text = "Not"
End If
End Sub

Private Sub infor_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles MyBase.Load
Dim x
con = New OleDb.OleDbConnection("provider=microsoft.Jet.OLEDB.4.0;Data
source=" & System.AppDomain.CurrentDomain.BaseDirectory & "MyDB.mdb;")
con.Open()
cmd = New OleDb.OleDbCommand("select max(sno) from Infor", con)
x = cmd.ExecuteScalar
TextBox1.Text = Val(x) + 1
con.Close()
End Sub
End Class

Public Class Applicant_Entry

Dim con As New OleDb.OleDbConnection
Dim cmd As New OleDb.OleDbCommand
Dim dr As OleDb.OleDbDataReader

47
 Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Dim a, b, c, d, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t
a = Val(TextBox1.Text)
b = TextBox2.Text
c = TextBox3.Text
d = CDate(DateTimePicker1.Text)
f = Label18.Text
t = TextBox4.Text
g = TextBox5.Text
h = Val(ComboBox3.Text)
i = Val(ComboBox4.Text)
j = Val(TextBox6.Text)
k = TextBox7.Text
l = Val(TextBox8.Text)
m = TextBox9.Text
n = ComboBox1.Text
o = CDate(DateTimePicker2.Text)
p = ComboBox2.Text
q = TextBox10.Text
r = TextBox11.Text
s = TextBox12.Text
con = New OleDb.OleDbConnection("provider=microsoft.Jet.OLEDB.4.0;Data
source=" & System.AppDomain.CurrentDomain.BaseDirectory & "MyDB.mdb;")
con.Open()
cmd = New OleDb.OleDbCommand("insert into Application values(" & a & ",'" & b &
"','" & c & "',#" & d & "#,'" & f & "','" & t & "','" & g & "'," & h & "," & i & ",'" & j & "','" &
k & "','" & l & "','" & m & "','" & n & "',#" & o & "#,'" & p & "','" & q & "','" & r & "','" & s
& "')", con)
cmd.ExecuteNonQuery()
MsgBox("Record Added Sucessfully")
con.Close()
End Sub

Private Sub RadioButton1_CheckedChanged(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles RadioButton1.CheckedChanged
If RadioButton1.Checked Then
Label18.Text = "Male"
Label18.Visible = False
End If
End Sub

Private Sub RadioButton2_CheckedChanged(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles RadioButton2.CheckedChanged
48
 If RadioButton2.Checked = True Then
Label18.Text = "Female"
Label18.Visible = False
End If
End Sub

Private Sub Form3_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles MyBase.Load
Dim i
ComboBox3.BeginUpdate()
For i = 100 To 200
ComboBox3.Items.Add(i)
Next
ComboBox3.EndUpdate()

ComboBox4.BeginUpdate()
For i = 50 To 120
ComboBox4.Items.Add(i)
Next
ComboBox4.EndUpdate()
appid_inc()
End Sub

Sub appid_inc()
Dim x
con = New OleDb.OleDbConnection("provider=microsoft.Jet.OLEDB.4.0;Data
source=" & System.AppDomain.CurrentDomain.BaseDirectory & "MyDB.mdb;")
con.Open()
cmd = New OleDb.OleDbCommand("select max(appid) from Application", con)
x = cmd.ExecuteScalar
ComboBox3.Items.Add(i)
Next
ComboBox3.EndUpdate()
Did_inc()
End Sub

Sub Did_inc()
Dim x
con = New OleDb.OleDbConnection("provider=microsoft.Jet.OLEDB.4.0;Data
source=" & System.AppDomain.CurrentDomain.BaseDirectory & "MyDB.mdb;")
con.Open()
cmd = New OleDb.OleDbCommand("select max(DId) from Donars", con)
x = cmd.ExecuteScalar
TextBox1.Text = Val(x) + 1
49
 con.Close()
End Sub
Private Sub RadioButton1_CheckedChanged(ByVal sender As System.Object, ByVal e As
System.EventArgs)
If RadioButton1.Checked Then
Label2.Text = "Male"
End If
End Sub

Private Sub RadioButton2_CheckedChanged(ByVal sender As System.Object, ByVal e As

System.EventArgs)
If RadioButton2.Checked = True Then
Label2.Text = "Female"
End If
End Sub

Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button4.Click
OpenFileDialog1.Title = "get photo"
If (OpenFileDialog1.ShowDialog = Windows.Forms.DialogResult.OK) Then
PictureBox1.Image = Image.FromFile(OpenFileDialog1.FileName)

Public Class Applicant_Entry

Dim con As New OleDb.OleDbConnection
Dim cmd As New OleDb.OleDbCommand
Dim dr As OleDb.OleDbDataReader

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button1.Click
Dim a, b, c, d, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t
a = Val(TextBox1.Text)
b = TextBox2.Text
c = TextBox3.Text
d = CDate(DateTimePicker1.Text)
f = Label18.Text
t = TextBox4.Text
g = TextBox5.Text
h = Val(ComboBox3.Text)
i = Val(ComboBox4.Text)
j = Val(TextBox6.Text)
k = TextBox7.Text
l = Val(TextBox8.Text)
m = TextBox9.Text
n = ComboBox1.Text
50
 o = CDate(DateTimePicker2.Text)
p = ComboBox2.Text
q = TextBox10.Text
r = TextBox11.Text
s = TextBox12.Text
con = New OleDb.OleDbConnection("provider=microsoft.Jet.OLEDB.4.0;Data
source=" & System.AppDomain.CurrentDomain.BaseDirectory & "MyDB.mdb;")
con.Open()
cmd = New OleDb.OleDbCommand("insert into Application values(" & a & ",'" & b &
"','" & c & "',#" & d & "#,'" & f & "','" & t & "','" & g & "'," & h & "," & i & ",'" & j & "','" &
k & "','" & l & "','" & m & "','" & n & "',#" & o & "#,'" & p & "','" & q & "','" & r & "','" & s
& "')", con)
cmd.ExecuteNonQuery()
MsgBox("Record Added Sucessfully")
con.Close()
End Sub

Private Sub RadioButton1_CheckedChanged(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles RadioButton1.CheckedChanged
If RadioButton1.Checked Then
Label18.Text = "Male"
Label18.Visible = False
End If
End Sub

Private Sub RadioButton2_CheckedChanged(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles RadioButton2.CheckedChanged
If RadioButton2.Checked = True Then
Label18.Text = "Female"
Label18.Visible = False
End If
End Sub

Private Sub Form3_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles MyBase.Load
Dim i
ComboBox3.BeginUpdate()
For i = 100 To 200
ComboBox3.Items.Add(i)
Next
ComboBox3.EndUpdate()
ComboBox4.BeginUpdate()
For i = 50 To 120
ComboBox4.Items.Add(i)
51
 Next
ComboBox4.EndUpdate()
appid_inc()
End Sub

BaseDirectory & TextBox11.Text)

MsgBox("photosaved", MsgBoxStyle.Information)
End Sub
End Class

Public Class donars

Dim con As New OleDb.OleDbConnection
Dim cmd As New OleDb.OleDbCommand
Dim dr As OleDb.OleDbDataReader

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs)
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
TextBox7.Text = ""
TextBox8.Text = ""
TextBox9.Text = ""
TextBox10.Text = ""
End Sub

Private Sub Form4_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles MyBase.Load
Dim i
ComboBox2.BeginUpdate()
For i = 100 To 200
ComboBox2.Items.Add(i)
Next
ComboBox2.EndUpdate()
ComboBox3.BeginUpdate()
For i = 50 To 120
ComboBox3.Items.Add(i)
Next
ComboBox3.EndUpdate()
Did_inc()
End Sub
52
 Sub Did_inc()
Dim x
con = New OleDb.OleDbConnection("provider=microsoft.Jet.OLEDB.4.0;Data
source=" & System.AppDomain.CurrentDomain.BaseDirectory & "MyDB.mdb;")
con.Open()
cmd = New OleDb.OleDbCommand("select max(DId) from Donars", con)
x = cmd.ExecuteScalar
TextBox1.Text = Val(x) + 1
con.Close()
End Sub
Private Sub RadioButton1_CheckedChanged(ByVal sender As System.Object, ByVal e As
System.EventArgs)
If RadioButton1.Checked Then
Label2.Text = "Male"
End If
End Sub

Private Sub RadioButton2_CheckedChanged(ByVal sender As System.Object, ByVal e As

System.EventArgs)
If RadioButton2.Checked = True Then
Label2.Text = "Female"
End If
End Sub

Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button4.Click
OpenFileDialog1.Title = "get photo"
If (OpenFileDialog1.ShowDialog = Windows.Forms.DialogResult.OK) Then
PictureBox1.Image = Image.FromFile(OpenFileDialog1.FileName)

Public Class Applicant_Entry

Dim con As New OleDb.OleDbConnection
Dim cmd As New OleDb.OleDbCommand
Dim dr As OleDb.OleDbDataReader

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button1.Click
Dim a, b, c, d, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t
a = Val(TextBox1.Text)
b = TextBox2.Text
c = TextBox3.Text
d = CDate(DateTimePicker1.Text)
f = Label18.Text
t = TextBox4.Text
53
 g = TextBox5.Text
h = Val(ComboBox3.Text)
i = Val(ComboBox4.Text)
j = Val(TextBox6.Text)
k = TextBox7.Text
l = Val(TextBox8.Text)
m = TextBox9.Text
n = ComboBox1.Text
o = CDate(DateTimePicker2.Text)
p = ComboBox2.Text
q = TextBox10.Text
r = TextBox11.Text
s = TextBox12.Text
con = New OleDb.OleDbConnection("provider=microsoft.Jet.OLEDB.4.0;Data
source=" & System.AppDomain.CurrentDomain.BaseDirectory & "MyDB.mdb;")

Sub appid_inc()
Dim x
con = New OleDb.OleDbConnection("provider=microsoft.Jet.OLEDB.4.0;Data
source=" & System.AppDomain.CurrentDomain.BaseDirectory & "MyDB.mdb;")
con.Open()
cmd = New OleDb.OleDbCommand("select max(appid) from Application", con)
x = cmd.ExecuteScalar
TextBox1.Text = Val(x) + 1
con.Close()
End Sub

54