Professional Documents
Culture Documents
Blood Management
Blood Management
INTRODUCTION:
The project entitled BLOOD DONOR’S MANAGEMENT is a pilot project
for new Blood donor to be start soon in the College. The management planned
this blood donor to operate on the next month. They have a big plan to collect the
blood Group from many different students. To manage all these they require full-
fledged software, which will take care all these.
PROJECT:
BLOOD DONOR MANAGEMENT is a software site to maintain day-to-day
transactions in blood donors. This software help to register all the donors, Blood
collection details, blood issued details etc.,
OBJECTIVE:
The main objective of this site is to automate the complete operations of the
blood donor. They need maintain hundreds of thousands of records. Also
searching should be very faster so they can find required details instantly.
MAIN MODULES OF THE PROJECT:
This project has the following modules, to manage all the requirements
of the blood donor.
DONOR DETAILS:
The donor details allow the donor to enter their identities with respective address
and associative contact details.
REPORTS:
The reporting module allows the user as well as administrator to maintain the
records in a report wise for printing state manner.
PLATFORM:
SOFTWARE REQUIREMENTS:
HARDWARE REQUIREMENTS:
Batch Master:
FEEDBACK:
SCREENS & CODINGS:
using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
using System.Data.OleDb;
using System.Windows.Forms;
if (Page.IsPostBack == false)
{
string S;
S = "Select * From DeptMstr";
Cmd = new OleDbCommand(S, Cn);
dr = Cmd.ExecuteReader();
DrpDept.Items.Add("-----------------------------------
Select------------------------------");
while (dr.Read())
{
DrpDept.Items.Add(dr.GetString(1).ToString());
}
Cmd.Dispose();
dr.Close();
string S1;
S1 = "Select * From BldGrp";
Cmd = new OleDbCommand(S1, Cn);
dr = Cmd.ExecuteReader();
DrpBldGrp.Items.Add("----------------------------------
-Select------------------------------");
while (dr.Read())
{
DrpBldGrp.Items.Add(dr.GetString(1).ToString());
}
Cmd.Dispose();
dr.Close();
string S2;
S2 = "Select * From Batch";
Cmd = new OleDbCommand(S2, Cn);
dr = Cmd.ExecuteReader();
DrpBatch.Items.Add("-----------------------------------
Select------------------------------");
while (dr.Read())
{
DrpBatch.Items.Add(dr.GetString(1).ToString());
}
Cmd.Dispose();
dr.Close();
DrpDegree.Items.Add("----------------------------------
-Select------------------------------");
DrpDegree.Items.Add("UG");
DrpDegree.Items.Add("PG");
DrpGender.Items.Add("----------------------------------
-Select------------------------------");
DrpGender.Items.Add("MALE");
DrpGender.Items.Add("FEMALE");
DrpWillToDon.Items.Add("-------------------------------
----Select------------------------------");
DrpWillToDon.Items.Add("YES");
DrpWillToDon.Items.Add("NO");
}
}
protected void ImageButton2_Click(object sender,
ImageClickEventArgs e)
{
Clear();
}
using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
using System.Data.OleDb;
using System.Windows.Forms;
public partial class Login : System.Web.UI.Page
{
OleDbConnection Cn;
OleDbCommand Cmd;
OleDbDataReader dr;
protected void Page_Load(object sender, EventArgs
e)
{
Cn = new
OleDbConnection(ConfigurationManager.ConnectionStrings[
"Con"].ConnectionString);
Cn.Open();
}
using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
using System.Data.OleDb;
using System.Windows.Forms;
if (Page.IsPostBack == false)
{
string S;
S = "Select * From Register";
Cmd = new OleDbCommand(S, Cn);
dr = Cmd.ExecuteReader();
DrpBldGrp.Items.Add("----------------------------------
-Select------------------------------");
while (dr.Read())
{
DrpBldGrp.Items.Add(dr.GetString(4).ToString());
}
Cmd.Dispose();
dr.Close();
}
}
protected void
DrpBldGrp_SelectedIndexChanged(object sender, EventArgs
e)
{
if (DrpBldGrp.Text !=
"-----------------------------------
Select------------------------------")
{
LstSrch.Items.Clear();
string S;
S = "Select * From Register";
Cmd = new OleDbCommand(S, Cn);
dr = Cmd.ExecuteReader();
while (dr.Read())
{
LstSrch.Items.Add(dr.GetValue(0).ToString());
}
dr.Close();
Cmd.Dispose();
}
}
protected void LstSrch_SelectedIndexChanged(object
sender, EventArgs e)
{
string S;
S = "Select * From Register Where RNO=" +
LstSrch.SelectedItem.Value.ToString() + "";
Cmd = new OleDbCommand(S, Cn);
dr = Cmd.ExecuteReader();
if(dr.Read())
{
LblDisp.Text +="NAME : "+
dr.GetString(1).ToString()+"<br>";
LblDisp.Text += "CONTACT NUMBER : " +
dr.GetString(11).ToString() + "<br>";
LblDisp.Text += "E-MAIL-ID : " +
dr.GetString(12).ToString() + "<br>";
LblDisp.Text += "DEGREE : " +
dr.GetString(6).ToString() + "<br>";
LblDisp.Text += "DEPARTMENT : " +
dr.GetString(5).ToString() + "<br>";
LblDisp.Text += "BATCH : " +
dr.GetString(7).ToString() + "<br>";
LblDisp.Text += "SECTION : " +
dr.GetString(8).ToString() + "<br>";
LblDisp.Text += "ADDRESS : " +
dr.GetString(13).ToString() + "<br>";
}
dr.Close();
Cmd.Dispose();
}
protected void ImageButton2_Click(object sender,
ImageClickEventArgs e)
{
LstSrch.Items.Clear();
DrpBldGrp.Text =
"-----------------------------------
Select------------------------------";
LblDisp.Text = "";
}
}
using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
using System.Data.OleDb;
using System.Windows.Forms;
int a;
if (Page.IsPostBack == false)
{
Disp();
}
}
using System.Data.OleDb;
using System.Windows.Forms;
int a;
if (Page.IsPostBack == false)
{
Disp();
}
}
public void Disp()
{
string S;
S = "Select MAX(BID) From BldGrp";
Cmd = new OleDbCommand(S, Cn);
dr = Cmd.ExecuteReader();
if (dr.Read())
{
a = Convert.ToInt32(dr.GetValue(0)) + 1;
TxtBGID.Text = a.ToString();
}
dr.Close();
Cmd.Dispose();
}
using System.Data.OleDb;
using System.Windows.Forms;
int a;
if (Page.IsPostBack == false)
{
Disp();
}
}
using System.Data.OleDb;
string S;
S = "Select Name as NAME,Mail as MailID,Contact
as CONTACT,Comment as COMMENTS From Feedback";
da = new OleDbDataAdapter(S,Cn);
ds = new DataSet();
da.Fill(ds, "SS");
GridView1.DataSource = ds.Tables["SS"];
GridView1.DataBind();
}
SOFTWARE DESCRIPTION
About ASP.Net
ASP.NET is more than the next version of Active Server Pages (ASP); it is a
unified Web development platform that provides the services necessary for developers to
build enterprise-class Web applications. While ASP.NET is largely syntax compatible
with ASP, it also provides a new programming model and infrastructure for more secure,
scalable and stable applications. You can feel free to augment your existing ASP
applications by incrementally adding ASP.NET functionality to them.
ASP.NET is a compiled, NET-based environment; you can author applications in
any .NET compatible language, including Visual Basic .NET, C#, and JScript .NET.
Additionally, the entire .NET Framework is available to any ASP.NET application.
Developers can easily access the benefits of these technologies, which include the
managed common language runtime environment, type safety, inheritance and so on.
ASP.NET has been designed to work seamlessly with WYSIWYG HTML editors
and other programming tools, including Microsoft Visual Studio .NET. Not only does this
make Web development easier, but it also provides all the benefits that these tools have to
offer, including a GUI that developers can use to drop server controls onto a Web page
and fully integrated debugging support.
Application Events
Configuration
Deployment
Debugging Support
Optimization
This release of ASP.NET uses IIS 5.0 as the priKim host environment. When
considering ASP.NET authentication, you should understand the interaction with IIS
authentication services.
IIS always assumes that a set of credentials maps to a Windows NT account and
uses them to authenticate a user. There are three different kinds of authentication
available in IIS 5.0: basic, digest, and Integrated Windows Authentication (NTLM or
Kerberos). You can select the type of authentication to use in the IIS administrative
services. For more information on IIS authentication, see the IIS documentation.
If you request a URL containing an ASP.NET application, the request and
authentication information are handed off to the application. ASP.NET provides the two
additional types of authentication described in the following table.
There are three major subsections: authentication, authorization and identity. The
values for each of the elements are usually set by overriding this section of the computer-
level configuration file with a similar section in an application configuration file placed
in the application root. All subdirectories automatically inherit those settings. However,
subdirectories can have their own configuration files that override other settings.
ASP.NET Data Access
The .NET Framework includes a new data access technology
named ADO.NET, an evolutionary improvement to ADO. However, the
classes that make up ADO.NET are different from the ADO objects that
you might be familiar with. Some changes must be made to existing
ADO applications to convert them to ADO.NET. The changes do not
have to be made to existing ADO applications immediately for them to
run under ASP.NET, however, as ADO will function under ASP.NET.
Nonetheless, converting ADO applications to ADO.NET is worthwhile.
For disconnected applications, ADO.NET offers performance
advantages over ADO disconnected record sets. Whereas ADO requires
that transmitting and receiving components be COM objects, ADO.NET
transmits data in standard XML format so that COM marshaling or
data-type conversions are not required.
Data retrieved from a database is generally used in one of two ways. The records
may be examined and manipulated by ASP code as a precursor to some other action,
without being displayed directly to the client, or the records simply may be displayed to
the client in a table or grid. The examples in this topic show how to convert a typical
ADO scenario to ADO.NET. There is a great deal more to the ADO.NET model than
these short examples illustrate; this is simply a quick overview of how to port common
ASP and ADO scenarios to the .NET Framework.
The first block of code in the following example is typical of an ASP application
that uses ADO to read and manipulate a set of records returned from a single SQL query.
It uses an ADO Recordset object to read the data records returned from the Northwind
sample database supplied with Microsoft Access. This code would be contained in a file
with an .asp file name extension.
ADO.NET DataSet object, which in this case contains one data table that is used
in much the same way as an ADO Recordset. Note that a DataSet can consist of
collections of one or more DataTables, DataRelations, and Constraints that form a
memory-resident database, so an ADO.NET DataSet is a great deal more flexible than an
ADO Recordset.
In order to use ADO.NET, you need to import the System.Data
and System.Data.OleDb namespaces. If your data source is a SQL
Server database, import the System.Data.SqlClient namespace instead
of System.Data.OleDb. For details on using the connection objects for
ADO and SQL .NET Data Providers, see Managed Connections.
In cases where a database query (even a multi-table join query), returns a single
set of records, you can use a single DataTable (MyTable in the example) in much the
same way that you use an ADO Recordset.
The ADO.NET DataSet can contain multiple tables and a set of relations that
describes a local copy of a relational database. Think of it as a mini-database in server
memory. Using the relation objects, your code can navigate through the collection of
tables to access data records in complex ways without making further queries to the main
data store. For more information about the components of a Dataset.
up ADO.NET are different from the ADO objects that you might be familiar with.
Some changes must be made to existing ADO applications to convert them to ADO.NET.
In this day of business-to-business and business-to-consumer e-commerce, slow Web
applications can waste resources and drive customers away from your company. Web site
performance is an extremely important issue for the developer writing code and for the
system administrator maintaining applications.
Fortunately, ASP.NET incorporates a variety of features and tools that allow you
to design and implement high-performance Web applications. These features include the
following:
ASP.NET gives you the ability to create Web applications that meet the demands
that arise when they must process large numbers of requests simultaneously
ADO The .NET Framework includes a new data access technology named
ADO.NET, an evolutionary improvement to ADO. However, the classes that make
The changes do not have to be made to existing ADO applications immediately for
them to run under ASP.NET, however, as ADO will function under ASP.NET.
Nonetheless, converting ADO applications to ADO.NET is worthwhile. For disconnected
applications, ADO.NET offers performance advantages over ADO disconnected record
sets. Whereas ADO requires that transmitting and receiving components be COM objects,
ADO.NET transmits data in standard XML format so that COM marshaling or data-type
conversions are not required.
Data retrieved from a database is generally used in one of two ways. The records
may be examined and manipulated by ASP code as a precursor to some other action,
without being displayed directly to the client, or the records simply may be displayed to
the client in a table or grid. The examples in this topic show how to convert a typical
ADO scenario to ASP.NET. There is a great deal more to the ADO.NET model than these
short examples illustrate; this is simply a quick overview of how to port common ASP
and ADO scenarios to the .NET Framework.
Working with a Single Table
The first block of code in the following example is typical of an ASP application
that uses ADO to read and manipulate a set of records returned from a single SQL query.
It uses an ADO Recordset object to read the data records returned from the Northwind
sample database supplied with Microsoft Access. This code would be contained in a file
with an .asp file name extension.
ADO.NET DataSet object, which in this case contains one data table that is used in
much the same way as an ADO Recordset. Note that a DataSet can consist of collections
of one or more DataTables, DataRelations, and Constraints that form a memory-resident
database, so an ADO.NET DataSet is a great deal more flexible than an ADO Recordset.
The ADO.NET DataSet can contain multiple tables and a set of relations that
describes a local copy of a relational database. Think of it as a mini-database in server
memory. Using the relation objects, your code can navigate through the collection of
tables to access data records in complex ways without making further queries to the main
data store. For more information about the components of a Datasets.
To display database data in tabular format in a browser, ASP developers have had to
write code to intersperse the data with HTML tags to build HTML tables on the fly.
ASP.NET includes DataGrid, DataList, and Repeater server controls that greatly
simplify the task of displaying tabular data on a Web page. ADO.NET datasets can be
easily bound to these controls; the ASP.NET engine, working with a control, sends pure
HTML 3.2 to the browser, producing richly formatted layouts to the user.
Most Web sites need to selectively restrict access to some portions of the site. You
can think of a Web site as somewhat analogous to an art gallery. The gallery is open for
the public to come in and browse, but there are certain parts of the facility, such as the
business offices, that are restricted to people with certain credentials, such as employees.
When a Web site records users' must be secured from public access. ASP.NET security
features address these and many credit card information, for example, the file or database
that stores such information other security issues.
ASP.NET, in conjunction with Internet Information Services (IIS), can authenticate user
credentials such as names and passwords, using any of the following authentication
methods:
ASP.NET Optimization
Fortunately, ASP.NET incorporates a variety of features and tools that allow you to
design and implement high-performance Web applications. These features include the
following:
ASP.NET gives you the ability to create Web applications that meet the demands that
arise when they must process large numbers of requests simultaneously
MS-ACCESS
Access offers a variety of features for different database needs. It can be used to
develop five general types of applications:
Personal applications
Applications used to run a small business
Department applications
Corporations- wide applications
Front-end for enterprise-wide client/server applications
Backend tables can be linked to the front-end applications. The process of linking
to backend tables is almost identical to that of linking to tables in other access databases.
After the back end tables have been linked to the front-end applications, they can be
treated like any other linked tables. Access utilizes ODBC to communicate with the back
end tables. Our application sends an Access SQL statement to the Access Jet Engine.
Jet translates the Access SQL statement into ODBC SQL. The ODBC SQL
statement is then sent to the ODBC Manager. The ODBC manger locates the correct
ODBC driver and passes it the ODBC SQL statement. The ODBC driver, supplied by the
back end vendor, translates the ODBC SQL statement into the back-end’s specific dialect.
The back end specific is sent to the SQL server and to the appropriate database.
Data Base
Access is a RDBMS that you can store and manipulate large amount of
information. A relational database is a database, which consist of tables of related
information that are linked together based on key field. <S Access supports GUI features
and entire programming language, VBA (Visual Basic or Application) that can be used to
develop richer and more developed application. MS Access database can act as a backend
database for VB. While using VB as a front-end tool, MS Access supports the user with
its powerful DBMS functions.
Main Elements of Access
Database Windows
In Access all, objects a dataase are stored in a single file and the file name has an
MDB extension.
Tables
Tables are the primary building block of ACCESS database. All data’s are stored
in tables.
Queries
A query is a question that you ask of the data that I stored in the tables of your
database
New Features in MS Access
MS Accesss offers many new and improved features to help create powerful
databse applications.
Testing Principles:
o All the test should be traceable to assessed requirements.
o Test should be planned long by testing begins.
o Testing should begin in the small and progress toward testing in the large.
In this testing inputs are given to the system and outputs are tested. There is no
necessary for watching the internal variables in the system and what are the changes
made on them for the required output. Giving input and testing output, as said above,
implement testing the system.
System Testing
System testing is design to uncover weakness that was not found in earlier tests.
This includes forced system failure and validation of the total system, as its users in the
operational environment will implement it. The total system is also testing or recovery
and fallback after various major failures to ensure that no data are lost during emergency.
It is concerned with interface, decision logic, and control flow recovery procedures,
throughput capacity and timing characteristics of the output system.
Regression Testing
Regression testing involves executing old test cases to test that no new errors have
been introduced. This testing is performed when some changes are made to an existing
system. The modified system needs to be tested to make sure that the new features to be
added to indeed work. However, as modification have been made to an existing system,
testing also has to be done to make sure that the modification has not had any undesired
side effect of making some of the earlier services faulty. This is the task of regression
testing.
Device Testing
The software testing process commences once the program is created and the
documentation and related data structures are design. Software testing is essential for
correcting errors. Otherwise the program or the project is not said to complete.
Validation Testing
If the user enters invalid data type, it will show the error message. For example, in
this module the user type the employee number as character it indicates the error to
validate data.
Integration Testing
CONCLUSION:
This project “Blood Donor System” handling and managing the donor database in
an efficient manner. This system is more innovative to use, any user can make up an
easier and faster transactions between users. This site can be used under any private
concern, for flexibly handling the databases, to get dispatches the data to process them for
individual usages. Thus it makes the system more flexible, and more reliable for use.
For all the above this site is the perfect place for the users especially students who
preferred to save the time, and entered into the current trend. Thus the entire project of
Blood Donor System is clearly tested, all the modules are working correctly, as well as
the output is verified.
BIBLIOGRAPHY
1. Professional ASP.NET 1.0, Special Edition
Author(s): Alex Homer, Brian Francis, David Sussman, Karli Watson, Richard Anderson
and Robert Howard
Released: February 2002
Publisher: Wrox Press
Author(s): Shaun Walker, Patrick J. Santry, Joe Brinkman, Dan Caron, Scott McCulloch,
Scott Willhite, Bruce Hopkins
Released: June 2005
Publisher: wrox press.