New Report BloodBank

Index
1. Introduction of the Organization and the project ................. 2

2. Objective .............................................................................. 3
3. System Analysis ................................................................... 5
3.1 Identification of needs............................................................................................... 5
3.2 Preliminary Investigation .......................................................................................... 6
4. Feasibility Study ................................................................... 9
4.1 Technical Feasibility ................................................................................................. 9
5. Software Paradigm Applied ................................................ 14
6. Software and Hardware Specification................................. 18
7. System Design .................................................................... 24
7.1 Data Flow Diagram ................................................................................................. 24
7.2 NUMBER OF MODULES AND THEIR DESCRIPTION:- ................................. 29
7.3 Input/Output Design................................................................................................ 36
8. Coding ................................................................................ 47
9. Validation Checks ............................................................... 96
10. Testing ........................................................................... 100
11. System Security Measures .............................................. 109
12. Reports........................................................................... 110
13. Future Scope of the Project ............................................ 111
14. Bibliography ................................................................... 114
1. Introduction of the Organization and the project
The system to be developed will be referred as Blood Bank

Management. The idea of the system is to have software package
to be developed for Blood Bank for uniform automation of daily
manual activity. To avoid the duplicity in developmental efforts, a
system needs to be developed to meet the common system
requirements with a provision to meet the additional/local
requirements of the respective States.
A Blood Bank Manager is a software product suite designed to
improve the quality and management of blood bank and hospital
health care management in the areas of health process analysis and
activity-based costing. Blood Bank Manager enables you to develop
your organization and improve its effectiveness and quality of work.
Managing the key processes efficiently is critical to the success of
the pharmacy. Blood Bank Manager helps you manage your
processes. A Blood Bank Manager provides all process management
tool elements: modeling, analysis, and simulation. Documentation
though an important part of a blood bank management, is a non-
productive exercise for the intellectual human being, whose ability
lies in core areas of excellence. Hence a systematic approach to the
way documents are managed, can transform your pharmacy
retailing resources to its highest utility and advantage.

2. Objective
This system provides the blood stock and blood issue information for
sale to patient. All the records motioned in the system for point of sale
of blood. Also management can view the detailed report of daily blood
donation, blood recipient, and blood issue. This helps the patient to take
blood more precisely and increase the credibility of the blood bank.
The proposed system however has the following features;
 It provides reliable security measures, which protect the data and the
package from accidental of deliberate threats that could cause
unauthorized modifications, disclosures of destruction of the data and
protection of the information system by the use of password.
 It provides an automated registration of donor code for each type of blood,
thus, storing information on the system rather than using bulky files.
 Set up forms records all the information of blood category and its donor,
recipient and quantity etc. Here we can add edit and search records
information according to need.

 Transaction module is used to keep transaction of all types of operation in
donor registration, recipient registration, blood stock, blood reservation
and blood issue.
 Report section is also there to provide all report to management like daily
donor registration, daily donor test report, recipient registration and stock
& issue record and also blood expiry date report is also there which help
user to take expired blood form their stock.

3. System Analysis
3.1 Identification of needs
In today’s fiercely competitive business environment any organization
that aims to work properly and to grow cannot ill afford to be
indifferent towards the use of new and better work process
(technology). If a particular work process is efficient, cheaper and
gives a certain advantage to the firm over other firms then the firm
should replace the old work process with the new one. The longer the
firm sticks to an old work process the more disadvantaged and
vulnerable it becomes.
 Cumbersome process: The manual generation of work for
sanction, issue and receive for each and every item is a
cumbersome process, which is prone to errors and is a tedious job.
 Time Consuming: Managing all items information, maintain the
current stock, mange all the information about the users etc. In the
manual manners it takes a long time with no guarantee about the
information will be available when required.

 Higher Stationary Requirements: Generally to maintain the
details regarding items, hardware users Required high amount of
unnecessary stationary.
 Not Reliable: The manual system is not reliable because it never
guarantees the accuracy of the system.
 Costly: The manual system is costly, as User has to hire a more of
people at various places to collect the necessary data and make the
entry in various registers.
3.2 Preliminary Investigation
Based on the user requirements and the detailed analysis of a
new system, the new system must be designed. When projects are
formally requested, the systems analysts, under the management’s
direction, conduct a preliminary investigation to analyze the reasons
for the request and collect various facts to respond to request in a
systematic way.
Preliminary or general design: In the preliminary or general design,
the features of the new system are specified. The costs of

implementing these features and the benefits to be derived are
estimated. If the project is still considered to be feasible, we move to
the detailed design stage.
Structure or Detailed design: In the detailed design stage, computer
oriented work begins in earnest. At this stage, the design of the
system becomes more structured. Structure design is a blue print of a
computer system solution to a given problem having the same
components and inter-relationship among the same components as
the original problem. Input, output and processing specifications are
drawn up in detail. In the design stage, the programming language
and the platform in which the new system will run are also decided.
Documents Review:-
To create this software very first I get to know what they want
to be in that software. What information they want from that software.
What information they want to give to their user.
There is an increased risk of error in the manual system. Redundancy
of data creeps in the manual system and it becomes a time-consuming
process to answer management queries and prepare management
reports. The manual registers and files to be maintained increases with

the increase in number of new recruitment, and /or increase in the
number of employee details.
On site Observations
For collecting data, I did on-site observation. In this, I observe
the activities of system directly. My purpose of on-site observation was
to get as chose as possible to the real system being studied. During
on-site observation, I see the office environment, work load of the
system and the users, methods of work and the facilities provided by
the organization to the users, which can help the developer to
understand the processes and procedures in development of new
system.
Conducting interview
Written documents and the on-site observation technique just
tell that how the system should operate, but they may not include
enough details to allow a decision to be made about the merits of a
systems proposal, nor do they present user views about current
operations.
So, I use interviews to learn these details. Interviews allow me
to learn more about the nature of the project request and the reason
for submitting it. Interviews provide details that further explain the
project and show whether assistance is merited economically,
operationally and technically.
4. Feasibility Study
4.1 Technical Feasibility
Technical feasibility explains the likelihood that the system will be
beneficial to the organization. On the basis of result of the initial
study, feasibility study takes place. The feasibility study is basically the
test of the proposed system in the light of its workability, meeting
user’s requirements, effective use of resources and .of course, the cost
effectiveness. Feasibility is the determination of whether or not a
project is worth doing. The process followed in making this
determination is called a feasibility study. This type of study
determines if a project can and should be taken. In the process of
feasibility study, the cost and benefits are estimated with greater
accuracy. Feasibility study is a test of a system proposal according to
its workability impact on the organization, ability to meet user needs
and effective use of resources. Feasibility is carried out to select the
best system that meets performance requirements. The main goal of
feasibility study is not to solve the problem but to achieve the scope.
TECHNICAL FEASIBILITY
This involves questions such as whether the technology needed for the
system exists, how difficult it will be to build, and whether the firm has
enough experience using that technology. The assessment is based on
an outline design of system requirements in terms of Input, Processes,
Output, Fields, Programs, and Procedures. This can be qualified in
terms of volumes of data, trends, frequency of updating, and other
areas in order to give an introduction to the technical system. There
are a number of technical issues which are generally issued during the
feasibility study of the investigation.
1: - Can the work for the project be done with current equipment
existing software technology & available personal?
2: - Can the system if upgraded if developed?
3: - If new technology is needed then what can be developed?
This is concerned with specifying equipment and software that will
successfully satisfy the user requirement. The technical needs of the
system may include:
 The facility to produce outputs in a given time.
 Response time under certain conditions.
 Ability to process a cretin volume of transaction at a particular

Speed.
When we check the technical feasibility configuration of the
system is given more importance than the actual make of
hardware. The processing environment is windows zone used
for. The client configuration is window XP workstation min 20 GB
hard disk, 64MB ram, Pentium processors 1 Ghz, the necessary
software’s required running the Employee Management System
are VS 2005 and SQL 2000 From the point of technical
feasibility, the software is worth doing.
ECONOMIC FEASIBILITY
Establishing the cost-effectiveness of the proposed system i.e. if
the benefits do not outweigh the costs then it is not worth going
ahead. In this we determine the benefits and savings that are expected
from a proposed system and compare them with costs. It benefits
outweigh costs; a decision is taken to design and implement the
system. This is an ongoing effort that improves in accuracy at each
phase of the system life cycle.
Economic analysis is the most frequently used technique for
evaluating the effectiveness of a proposed system. Most commonly
known as cost/ benefit analysis the procedure is to determine the
benefits and savings that are expected from a proposed system &
compare them with cost. In this feasibility financial and economic
question during the preliminary investigation to estimate the following.
1: - The cost to conduct a full system investigation.
2: - The cost of hardware and software for the class of application
being
considered.
3: - The cost of nothing charges.
4: - The benefits in the form of reduced cost.
Economic feasibility is an on going effort that improves inaccuracy at
each phase of the system life cycle. During interviewee I asked several
questions related with the cost of site.
OPERATIONAL FEASIBILITY
Do the current work practices and procedures support a new system?
Also social factors i.e. how the organizational changes will affect the
working lives of those affected by the system. It is mainly related to
human organizational and political aspects. The points to be
considered are:
 What changes will be brought with the system?
 What organizational structures are disturbed?

 What new skills will be required? Do the existing staff members
have these skills? If not, can they be trained in due course of
time?
Such considerations are likely to critically affect the nature and scope
of the eventual recommendations. This feasibility study is carried out
by a small group of people who are familiar with
Information system techniques, who understand the parts of the
business that are relevant to the project and are skilled in system
analysis and design process.
Issues that appear to be quite minor at the early stage can grow
into major problem after implementation. Therefore we should
consider operation aspects carefully. When I check the operational
feasibility. I found that the upper as well as the lower staff is fully
satisfied with it. The staff is cooperative and they feel easily with this
site. So I can say that proposed project is passing the operation
feasibility also.
5. Software Paradigm Applied
For any system, the development process revolves around a life cycle
that begins with the recognition of user needs. The key stages of the
cycle are an evaluation of the present system information gathering, a
Cost/Benefit analysis, a detailed design, and the implementation of the
system. The life cycle is not a procedure that deals with hardware and
software. Instead, it deals with building computer based systems to
help the users to operate a business or make decisions effectively and
manage an enterprise successfully. If all the people who are involved
in the project understand and accept a life-cycle model, it would help
to improve project communication, project manageability, resource
allocation, cost control, and system quality.
In this project (Consultancy Automation System), I followed
Waterfall Model. The waterfall model, also called the Phased model
included the sequential move from one phase to another. The system
cascaded from one level to the next in smooth progression. Each
phase required well-defined information, utilized well defined
processes, and resulted in well defined outputs. Following were the
seven phase of development:
 Conception
 Initiation
 Analysis
 Design
 Construction
 Testing
 Implementation and Maintenance
PHASE 1: CONCEPTION
This was the first phase with which I started. In this phase I
understood the problem. I understood what are the goals to be
achieved and what benefits will result from achieving the solution and
mainly the scope of the project.
PHASE 2: INITIATION
In this phase I identified all the client’s requirements, did Cost/Benefit
analysis and discussed the same with the client. I did it to ensure that
the client will get an economic justification for the money to be
invested in developing the project. Also I discussed the details about
the time and effort required to develop the project. This helped client
to decide on the resource commitment to this project. It also involved
selecting and recommending the most appropriate solution among the
alternatives considered.
PHASE 3: ANALYSIS
In this phase I finalized the functions that the system had to perform
and prepared a document in which following details were recorded:
 The outputs to be produced
 The inputs that must be received
 The records to be retained
 The procedure to get the outputs from the given inputs
 The audit and control requirements: These are required for
the user to monitor the system to check its functioning.
 System acceptance criteria: These lists the tests that the user
would actually perform to check whether the system is
accepted.
In addition to this, the Cost/Benefit analysis prepared during the
initiation phase was reviewed for accuracy. Also, the cost and estimate
was also reviewed.
PHASE 4: DESIGN
In this phase the document that was prepared during the analysis
phase was converted into a design of the desired system. More stress
was laid on system functionality instead of user requirement. That is,
the emphasis changed from defining the user requirements to defining
how the system will work.
At this point again, the Cost/Benefit analysis and Cost/Time estimates
were revised.
PHASE 5: CONSTRUCTION
In this phase, I got into full-fledged construction. I developed all the
modules that made up the entire application. I checked the programs
and instruction for each module. Actually, I transformed the proposed
system to an implement able one.
PHASE 6: TESTING
All the modules that were developed by me were integrated in this
phase and tested as a complete system.
It was tested for stress, recovery from failure and usability.
PHASE 7: IMPLEMENTATION AND MAINTENANCE
In this phase the new system was made operational. The activities
involved training operational staff, setting up the hardware.
I chose Waterfall Model because-----
Waterfall Model------
 Is easy to explain to user
 Has well defined stages and activities
 Ensures that the information required is obtained as and when it
needs to be used
 Helps to plan and schedule projects
 Detects errors/misunderstandings early due to verification at
each stage
 Ensures that the system meets user needs

 Minimizes the cost of rectifying errors
 Creates an environment that allows correction through feedback
Also we thought waterfall model was ideal because requirements were
well defined from the beginning.
6. Software and Hardware Specification
Hardware Platform:
Hardware Platform Used For The Development Of Institute
management System Are: -
An Intel compatible PC with
 166 MHz Pentium Processor or above are recommended.
 PCI Mother Board.
 32 MB SDRAM.4.3 G.B.
 Hard Disk and other standard configuration are to be used.
 SVGA Color Monitor with AGP display.
Software Platform:
The proposed project will work on Microsoft Windows and Windows
NT®, and all other platforms that support the above mentioned
Hardware as well as mentioned Software together with 32bit color
combination.
The project can successfully run on all the IBM and its compatible
architecture. Since the project including some multimedia properties,
the memory requirements will be larger. The necessary software’s
required running the Mobile Shop Automation are:
Microsoft Windows with Visual Basic .Net and SQL 2000
LANGUAGES
Visual Basic .NET (VB.NET):
Visual Basic .NET (VB.NET) is an object-oriented computer language
that can be viewed as an evolution of Microsoft's Visual Basic (VB)
implemented on the Microsoft .NET framework. Its introduction has
been controversial, as significant changes were made that broke
backward compatibility with older versions and caused a rift within the
developer community.
Microsoft .NET Framework is a software component that is a part of
several Microsoft Windows operating systems. It has a large library of
pre-coded solutions to common programming problems and manages

the execution of programs written specifically for the framework. The
.NET Framework is a key Microsoft offering and is intended to be used
by most new applications created for the Windows platform.
The pre-coded solutions that form the framework's Base Class Library
cover a large range of programming needs in a number of areas,
including user interface, data access, database connectivity,
cryptography, web application development, numeric algorithms, and
network communications. The class library is used by programmers
who combine it with their own code to produce applications.
Programs written for the .NET Framework execute in a software
environment that manages the program's runtime requirements. Also
part of the .NET Framework, this runtime environment is known as the
Common Language Runtime (CLR). The CLR provides the appearance
of an application virtual machine so that programmers need not
consider the capabilities of the specific CPU that will execute the
program. The CLR also provides other important services such as
security, memory management, and exception handling. The class
library and the CLR together compose the .NET Framework.
The .NET Framework is included with Windows Server 2008 and
Windows Vista. The current version of the framework can also be

installed on Windows XP and the Windows Server 2003 family of
operating systems.
For this release, Microsoft added many features, including:
 Edit and Continue - probably the biggest "missing feature" from
Visual Basic .NET, allowing the modification of code and
immediate resumption of execution
 Design-time expression evaluation
 The My pseudo-namespace (overview, details), which provides:
o easy access to certain areas of the .NET Framework that
otherwise require significant code to access
o dynamically-generated classes (notably My.Forms)
 Improvements to the VB-to-VB.NET converter
 The Using keyword, simplifying the use of objects that require
the Dispose pattern to free resources
 Just My Code, which hides boilerplate code written by the Visual
Studio .NET IDE
 Data Source binding, easing database client/server development
The above functions (particularly My) are intended to reinforce Visual
Basic .NET's focus as a rapid application development platform and
further differentiate it from C#.

Visual Basic 2005 introduced features meant to fill in the gaps between
itself and other "more powerful" .NET languages, adding:
 .NET 2.0 languages features such as:
o Partial classes, a method of defining some parts of a class
in one file and then adding more definitions later;
particularly useful for integrating user code with auto-
generated code
o Null able Types
 XML comments that can be processed by tools like NDoc to
produce "automatic" documentation
 Operator overloading
 Support for unsigned integer data types commonly used in other
languages
RDBMS
Microsoft Windows with SQL Server:
SQL SERVER Is A Part Of Microsoft’s Back Office Suite Of Products,
Which Also Included Back Office Server, Exchange Server, Proxy
Server, Site Server, Small Business Server, SNA Server And System
Management Server. It Has Been Targeted To Support Not Only The
Small-To Medium-Sized Business That Have Been SQL Server’s

Traditional Market, But Also The Larger Organization Tasked With
Implementing Transactional System, Very Large Databases, And Data
Warehousing.
SQL Server Had Its Humble Beginnings In A Joint
Partnership With IBM On A New Operating System Called OS\2. They
Wanted A Database That Would Run Under OS\2, So They Partnered
With Sybase To Port Their Existing UNIX-Based Data Server Product To
OS|2. The Current Version Of SQL Server 2005 Is Completely Re-
architected Database Engine, Full Row-Level Locking, And A New
Query Processor. This Version Responded To A Demand Of Scalability,
Going Home Desktop To Enterprise To Internet. SQL Server Is Now A
Database Platform Contender For Enterprise Wide And Data
Warehousing Application With Technologies Like OLAP.
The Standard Installation Is The Full Database
Server And Runs Only On Windows NT Server And Windows 2000.
SQL Server Desktop Runs Under Windows 95/98, Windows NT
Server, Windows NT Workstation and Windows NT Server
Enterprise.
7. System Design
7.1 Data Flow Diagram
Data flow diagrams are a network representation of a system.
They are the cornerstone for structured systems analysis and
design. The diagrams use four symbols to represent any system
at any level of detail. The four entities that must be represented
are:
 Data flows - movement of data in the system
 Data stores - data repositories for data that is not moving
 Processes - transforms of incoming data flow(s) to
outgoing data flow(s)
 External entities - sources or destinations outside the
specified system boundary

Data flow diagrams do not show decisions or timing of events.
Their function is to illustrate data sources, destinations, flows,
stores, and transformations. The capabilities of data flow
diagramming align directly with general definitions of systems.
Data flow diagrams are an implementation of a method for
representing systems concepts including boundaries,
input/outputs, processes/sub processes, etc.
The data flow diagram is analogous to a road map. It is a
network model of all possibilities with different detail shown on
different hierarchical levels. The process of representing different
detail levels is called "leveling" or "partitioning" by some data
flow diagram advocates.
The Data Flow Diagram helps us in understanding the flow of
information and the flow of data. The abstract idea about the
system “Blood Bank Management” can be obtained from the
diagram, which is shown below.

Registration Registration
Donor Blood Recipient

Issue Bank Issue
Stock Update
Stock Records
ZZeerroo LLeevveell D
DFFD
D
D
DFFD
D ffoorr D
Doonnoorr R
Reeggiissttrraattiioonn aanndd D
Doonnoorr TTeesstt
Registration
Donor Blood
Bank
Database
Test
Get Donor ID
Blood
Test
Update
Result
Test Result
D
DFFD
D ffoorr R
Reecciippiieenntt R
Reeggiissttrraattiioonn aanndd B
Blloooodd IIssssuuee
Recipient Blood
Bank
Database
Blood
Stock
Database
Blood
Issue
7.2 NUMBER OF MODULES AND THEIR DESCRIPTION:-
User Login Screen. User will enter the user password and login
name to enter application. After successful login and password the
application will load the entire database and its modules. If
username or password is incorrect a massage will appear “Invalid
Password or Username”.
Application Manager: - This form is loaded first if the user is an
authorized user. It is a MDI form i.e. it is the parent form from
which all other forms can be referenced.
It has the following menus and submenus. This application has
been divided into separate Four sub modules: These sub modules
are
Donor Management: - This is the module of the system which
have sub menu also. This module records donor registration and
donor test.
a) Donor Registration-In this form we keep track of all the donor
registration information and its details which is entered in the
system. It is also useful in searching the donor member
information. Donor Id will be auto generated. To enter a donor

registration enters name, address, city, and phone number and
email id. Click on Save to Save the records. To Search the records
enter the donor id and click on search, respective donor details will
shown. User can also edit the records and click on modify to save
the modified records.
b) Donor Blood Test: .This module keeps the records of that
donor blood test which are registered for blood donation. Before
taking blood of any donor test of his/her blood required. Enter
donor id, test id, Test name, Test date, blood type and test result.
Click on Save to Save the records. To Search the records enter the
donor id and click on search, respective donor details will shown.
User can also edit the records and click on modify to save the
modified records.
Recipient Management: - This module records recipient
registration details.
a) Recipient Registration-In this form we keep track of all the
recipient registration information and its details which is entered in
the system. It is also useful in searching the recipient member
information. Recipient Id will be auto generated. To enter a
recipient registration enters name, address, city, and phone

number and email id. Click on Save to Save the records. To Search
the records enter the recipient id and click on search, respective
donor details will shown. User can also edit the records and click on
modify to save the modified records.
Blood Management: - This is the module of the system which
have sub menu also. This module records blood stock, blood
reservation and blood issue
a) Blood Stock-In this form we keep track of all the blood stock
quantity donated by donor. Stock is mentioned on blood type and
its number of bags donated by donor. Also each bag has expiry
date set so that after certain period this blood is expired . It is also
useful in searching the blood stock information. Blood Bag Id will be
auto generated. To enter a blood stock enters blood type, donor id,
number of bags, stock date and expiry date. Click on Save to Save
the records. To Search the records enter the donor id and click on
search, respective donor details will shown. User can also edit the
records and click on modify to save the modified records.
b) Blood Reservation-In this form we keep track of all the blood
reservation donated by donor or any other recipient for the certain
period. Reservation is made on blood type and its number of bags
donated by donor or as per requirement of the recipient. Also each

bag has reservation up to date set so that after set period if this
blood is not issue then it will discard. It is also useful in searching
the blood reservation information. Blood reservation Id will be auto
generated. To enter a blood reservation enters blood recipient id,
blood type, donor id, number of bags, reserve stock up to date.
Click on Save to Save the records. To Search the records enter the
reservation id and click on search, respective donor details will
shown. User can also edit the records and click on modify to save
the modified records.
b) Blood Reservation-In this form we keep track of all the blood
issue to recipient. If reservation is made on blood type and its
number of bags donated by donor or as per requirement of the
recipient then select reservation id and update the records by
entering the issue date. Or enter the fresh issue records. Blood
issue Id will be auto generated. To issue blood enter a blood
reservation enters blood recipient id, blood type, donor id, number
of bags, reserve stock up to date. Click on Save to Save the
records. To Search the records enter the reservation id and click on
search, respective donor details will shown. User can also edit the
records and click on modify to save the modified records.
Also Quick Launch menu tool is also there for easy use.
Data structure (Tables) for all the modules
Table 1: Tbl_User
NAME TYPE Description CONSTRAINT

UName nvarchar(4) User Login Primary key
Name
UPaswd nvarchar(4) User --
Password
Table 2: Tbl_DonorTest

DonorID int(5) Donor Id PK
TestID int(5) Test Id --
TestName nvarchar (10) Test name --
TestDate smalldatetime(4) Test Date --
BType nvarchar(50) Blood Type --
TestResult smalldatetime(4) Test Result --
Table 3: Tbl_DonorTest

DonorID int(5) Donor Id PK
TestID int(5) Test Id --
TestName nvarchar (10) Test name --
TestDate smalldatetime(4) Test Date --
TestResult Int(5) Test Result --
Table 4: Tbl_Recipient

ReprId int(5) Recipient Id PK
Name nvarchar(50) Recipient --
Name
Address nvarchar(50) Recipient --
Address
City nvarchar(50) Recipient --
City
PhNo nvarchar(50) Recipient --
Phone
Number
Email nvarchar(50) Recipient --
Email id
Btype nvarchar(50) Blood type
Req. by
Recipient
Amount nvarchar(50) Amount per
bag
Table 5: Tbl_BloodStock

BID int(5) Blood Stock PK
Id
NBag nvarchar(50) Number of --
Blood
SDate smalldatetime(4) Stock Date --
EDate smalldatetime(4) Blood Expiry --
Date
DonorID int(5) Donor Id --
Table 6: Tbl_BloodReservation

BResID int(5) Blood PK
Reservation
ReprID nvarchar(50) Recipient ID --
BID nvarchar(50) Stock ID --
NBag nvarchar(10) Number of --
Blood Bags
RecipientType nvarchar(10) Donor or --
Non Donor
DonorID int(5) Donor Id
Amount nvarchar(50) Amount
DateResv smalldatetime(4) Reservation
Date
DateResvUpto smalldatetime(4) Reserve Up
to date
Table 7: Tbl_BloodIssue

BIID int(5) Blood Issue PK
ID
BID nvarchar(50) Blood Bad --
Id
RecipientType nvarchar(50) Donor or --
Non Donor
ReprId nvarchar(10) Recipient ID --
BResID nvarchar(10) Rreservation --
Id
DonorID nvarchar(10) Donor Id --
NBag int(5) number of
Bags
BType nvarchar(50) Blood Type
Amount smalldatetime(4) Amount
DateIssue smalldatetime(4) Date of
Issue
7.3 Input/Output Design
8. Coding
BloodIssue
Imports System.Data.OleDb
Public Class BloodIssue
Private Sub DonorRegistration_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
ref3()
ref4()
ref5()
ref6()
Try
Dim cmd As New OleDbCommand("Select * from Tbl_BloodIssue", cn)
cn.Open()
Dim dr As OleDbDataReader = cmd.ExecuteReader
While dr.Read
TextBox6.Text = dr(0)
End While
TextBox6.Text = Val(TextBox6.Text) + 1
dr.Close()
cn.Close()
Dim da As New OleDbDataAdapter("Select * from Tbl_BloodIssue", cn)
Dim ds As New DataSet
da.Fill(ds, "Mast")
DataGridView1.DataSource = ds.Tables(0)
Catch ex As Exception
MsgBox(ex.Message, MsgBoxStyle.Critical, Me.Text)

If cn.State = ConnectionState.Open Then
cn.Close()
End If
End Try
End Sub
Private Sub ref3()
OleDbConnection1.Open()
Dim objReader As OleDbDataReader = OleDbSelectCommand1.ExecuteReader
Do While objReader.Read
ComboBox6.Items.Add(objReader("BID"))
Loop
OleDbConnection1.Close()
End Sub
Private Sub ref4()
'ComboBox1.Items.Clear()
'On Error Resume Next
ComboBox1.Items.Add(objReader("ReprID"))
Loop
End Sub
Private Sub ref5()
'ComboBox1.Items.Clear()
'On Error Resume Next
ComboBox2.Items.Add(objReader("BResID"))
Loop
End Sub
Private Sub ref6()
ComboBox5.Items.Add(objReader("DonorID"))
Loop
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Try
Dim cmd As New OleDbCommand("Insert into Tbl_BloodIssue Values(" &
TextBox6.Text & "','" & ComboBox6.Text & "','" & ComboBox4.Text & "','" &
ComboBox1.Text & "','" & ComboBox2.Text & "','" & ComboBox5.Text & "'," &
TextBox2.Text & "'," & ComboBox3.Text & "'," & TextBox3.Text & "'," &
TextBox4.Text & "')", cn)
cn.Open()
cmd.ExecuteNonQuery()
MsgBox("Successfully Record Saved.....!", MsgBoxStyle.Information,
Me.Text)
cn.Close()
Me.Close()
Dim o As New BloodIssue
o.MdiParent = MainMenu.ActiveForm
o.Show()
cn.Close()
End If
End Try
End Sub
Try
If Len(Trim(TextBox6.Text)) = 0 Then
MsgBox("Please Select Id Number...!", MsgBoxStyle.Exclamation,
Me.Text)
'FindGroupBox.Visible = False
Exit Sub
Else
Dim cmd As New OleDbCommand("Select * from Tbl_BloodIssue where
BIID=" & TextBox6.Text, cn)

cn.Open()
While dr.Read
ComboBox6.Text = dr(1)
End While
dr.Close()
cn.Close()
Button1.Enabled = False
Button3.Enabled = True
End If
cn.Close()
End If
End Try
End Sub
Try
Dim cmd As New OleDbCommand("Update Tbl_BloodIssue set BID='" &
ComboBox6.Text & "',RecipientType='" & ComboBox4.Text & "',ReprId='" &
ComboBox1.Text & "',BResID='" & ComboBox2.Text & "',DonorID='" &
ComboBox5.Text & "',NBag='" & TextBox2.Text & "',BType='" & ComboBox3.Text & "
', Amount ='" & TextBox3.Text & "',DateIssue='" & TextBox4.Text & "' where BIID="
& TextBox6.Text, cn)
cn.Open()
MsgBox("Successfully Record Updated.....!", MsgBoxStyle.Information,
Me.Text)
cn.Close()
Me.Close()
o.Show()
cn.Close()
End If
End Try
End Sub
Try
Dim cmd As New OleDbCommand("Delete from Tbl_BloodIssue where
BIID=" & TextBox6.Text, cn)
cn.Open()
MsgBox("Successfully Record Deleted.....!", MsgBoxStyle.Information,
Me.Text)
cn.Close()
Me.Close()
o.Show()
cn.Close()
End If
End Try
End Sub
Private Sub ComboBox6_SelectedIndexChanged(ByVal sender As Object, ByVal e
As System.EventArgs) Handles ComboBox6.SelectedIndexChanged
ref3()
End Sub
ref4()
End Sub
ref5()
End Sub
End Class
BloodReservation
Public Class BloodReservation
ref()
ref1()
ref2()
Try
Dim cmd As New OleDbCommand("Select * from Tbl_BloodReservation", cn)
cn.Open()
While dr.Read
End While
dr.Close()
cn.Close()
Dim da As New OleDbDataAdapter("Select * from Tbl_BloodReservation",
cn)
da.Fill(ds, "Mast")
cn.Close()
End If
End Try
End Sub
Private Sub ref()
ComboBox1.Items.Add(objReader("ReprId"))
Loop
End Sub
Private Sub ref1()
ComboBox2.Items.Add(objReader("BID"))
Loop
End Sub
Private Sub ref2()
Loop
End Sub
Try
Dim cmd As New OleDbCommand("Insert into Tbl_BloodReservation
Values(" & TextBox1.Text & ",'" & ComboBox1.Text & "','" & ComboBox2.Text & "','"
& TextBox2.Text & "','" & ComboBox3.Text & "','" & ComboBox4.Text & "','" &
ComboBox5.Text & "','" & TextBox3.Text & "','" & TextBox4.Text & "','" &
cn.Open()
Me.Text)
cn.Close()
Me.Close()
Dim o As New BloodReservation
o.Show()
cn.Close()
End If
End Try
End Sub
Try
Me.Text)
Exit Sub
Else
Dim cmd As New OleDbCommand("Select * from Tbl_BloodReservation
where BResID=" & TextBox1.Text, cn)
cn.Open()
While dr.Read
End While
dr.Close()
cn.Close()
End If
cn.Close()
End If
End Try
End Sub
Try
Dim cmd As New OleDbCommand("Update Tbl_BloodReservation set BID='" &
ComboBox2.Text & "',ReprID='" & ComboBox1.Text & "',NBag='" & TextBox2.Text &
"',BType='" & ComboBox3.Text & "',RecipientType='" & ComboBox4.Text &
"',DonorID='" & ComboBox5.Text & "',Amount='" & TextBox3.Text & " ', DateResv
='" & TextBox4.Text & "',DateResvUpto='" & TextBox5.Text & "' where BResID=" &
TextBox1.Text, cn)
cn.Open()
Me.Text)
cn.Close()
Me.Close()
o.Show()
cn.Close()
End If
End Try
End Sub
Try
Dim cmd As New OleDbCommand("Delete from Tbl_BloodReservation where
BResID=" & TextBox1.Text, cn)
cn.Open()
Me.Text)
cn.Close()
Me.Close()
o.Show()
cn.Close()
End If
End Try
End Sub
ref()
End Sub
ref1()
End Sub
ref2()
End Sub
End Class
BloodStock
Public Class BloodStock
ref2()
Try
Dim cmd As New OleDbCommand("Select * from Tbl_BloodStock", cn)
cn.Open()

While dr.Read
End While
dr.Close()
cn.Close()
Dim da As New OleDbDataAdapter("Select * from Tbl_BloodStock", cn)
da.Fill(ds, "Mast")
cn.Close()
End If
End Try
End Sub
Private Sub ref2()
ComboBox2.Items.Clear()
Dim objReader As OleDbDataReader = OleDbSelectCommand.ExecuteReader
Loop
End Sub
System.EventArgs)
Try
Dim cmd As New OleDbCommand("Insert into Tbl_BloodStock Values(" &
TextBox1.Text & ",'" & ComboBox1.Text & "','" & TextBox2.Text & "','" &
TextBox4.Text & "','" & TextBox6.Text & "','" & ComboBox2.Text & "')", cn)
cn.Open()
Me.Text)
cn.Close()
Me.Close()
Dim o As New BloodStock
o.Show()
cn.Close()
End If
End Try
End Sub
System.EventArgs)
Try
Me.Text)
Exit Sub
Else
Dim cmd As New OleDbCommand("Select * from Tbl_BloodStock where
BID=" & TextBox1.Text, cn)
cn.Open()
While dr.Read
End While
dr.Close()
cn.Close()
End If
cn.Close()
End If
End Try
End Sub
System.EventArgs)
Try
Dim cmd As New OleDbCommand("Update Tbl_BloodStock set BType='" &
ComboBox1.Text & "',NBag='" & TextBox2.Text & "',SDate='" & TextBox4.Text &
"',EDate='" & TextBox6.Text & "',DonorID='" & ComboBox2.Text & "' where BID=" &
TextBox1.Text, cn)
cn.Open()
Me.Text)
cn.Close()
Me.Close()
o.Show()
cn.Close()
End If
End Try
End Sub
System.EventArgs)
Try
Dim cmd As New OleDbCommand("Delete from Tbl_BloodStock where BID="
& TextBox1.Text, cn)
cn.Open()
Me.Text)
cn.Close()
Me.Close()
o.Show()
cn.Close()
End If
End Try
End Sub
As System.EventArgs)
ref2()
End Sub
End Class
DonorRegistration
Public Class DonorRegistration

Try
Dim cmd As New OleDbCommand("Select * from Tbl_DonorReg", cn)
cn.Open()
While dr.Read
End While
dr.Close()
cn.Close()
Dim da As New OleDbDataAdapter("Select * from Tbl_DonorReg", cn)
da.Fill(ds, "Mast")
cn.Close()
End If
End Try
End Sub
Try
Dim cmd As New OleDbCommand("Insert into Tbl_DonorReg Values(" &
TextBox1.Text & ",'" & TextBox3.Text & "','" & TextBox2.Text & "','" & TextBox4.Text
& "','" & TextBox6.Text & "','" & TextBox5.Text & "')", cn)
cn.Open()
Me.Text)
cn.Close()
Me.Close()
Dim o As New DonorRegistration
o.Show()
cn.Close()
End If
End Try
End Sub
Try
Me.Text)
Exit Sub
Else
Dim cmd As New OleDbCommand("Select * from Tbl_DonorReg where
DonorID=" & TextBox1.Text, cn)
cn.Open()
While dr.Read
End While
dr.Close()
cn.Close()
End If
cn.Close()
End If
End Try
End Sub
Try
Dim cmd As New OleDbCommand("Update Tbl_DonorReg set Name='" &
TextBox3.Text & "',Address='" & TextBox2.Text & "',City='" & TextBox4.Text &
"',PhNo='" & TextBox6.Text & "',EMail='" & TextBox5.Text & "' where DonorID=" &
TextBox1.Text, cn)
cn.Open()
Me.Text)
cn.Close()
Me.Close()
o.Show()
cn.Close()
End If
End Try
End Sub
Try
Dim cmd As New OleDbCommand("Delete from Tbl_DonorReg where
cn.Open()
Me.Text)
cn.Close()
Me.Close()
o.Show()
cn.Close()
End If
End Try
End Sub
End Class
DonorTest
Public Class DonorTest
Try
Dim cmd As New OleDbCommand("Select * from Tbl_DonorTest", cn)
cn.Open()
While dr.Read
End While
dr.Close()
cn.Close()
Dim da As New OleDbDataAdapter("Select * from Tbl_DonorTest", cn)
da.Fill(ds, "Mast")
cn.Close()
End If
End Try
End Sub
Try
Dim cmd As New OleDbCommand("Insert into Tbl_DonorTest Values(" &
& "','" & TextBox6.Text & "','" & ComboBox1.Text & "')", cn)
cn.Open()
Me.Text)
cn.Close()
Me.Close()
Dim o As New DonorTest
o.Show()
cn.Close()
End If
End Try
End Sub
Try
Me.Text)
Exit Sub
Else
Dim cmd As New OleDbCommand("Select * from Tbl_DonorTest where
cn.Open()
While dr.Read
End While
dr.Close()
cn.Close()
End If
cn.Close()
End If
End Try
End Sub
Try
Dim cmd As New OleDbCommand("Update Tbl_DonorTest set TestID='" &
TextBox3.Text & "',TestName='" & TextBox2.Text & "',TestDate='" & TextBox4.Text
& "',Btype='" & TextBox6.Text & "',TestResult='" & ComboBox1.Text & "' where
cn.Open()
Me.Text)
cn.Close()
Me.Close()
o.Show()
cn.Close()
End If
End Try
End Sub
Try
Dim cmd As New OleDbCommand("Delete from Tbl_DonorTest where
cn.Open()
Me.Text)
cn.Close()
Me.Close()
o.Show()
cn.Close()
End If
End Try
End Sub
End Class
Login
Option Compare Text
Public Class LoginForm1
Private Sub OK_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles OK.Click
Try
Dim cmd As New OleDbCommand("Select * from Tbl_User where UName='"
& UsernameTextBox.Text & "' And UPaswd='" & PasswordTextBox.Text & "'", cn)
cn.Open()

If dr.Read Then
MsgBox("Wel Come To Blood Bank System......!",
MsgBoxStyle.Information, Me.Text)
Dim o As New MainMenu
Me.Hide()
cn.Close()
o.Show()
Else
MsgBox("Plz Insert Valid UserName And Password......!",
MsgBoxStyle.Exclamation, Me.Text)
UsernameTextBox.Clear()
PasswordTextBox.Clear()
UsernameTextBox.Focus()
cn.Close()
Exit Sub
End If
cn.Close()
End If
End Try
End Sub
End Class
MainMenu
Imports System.Windows.Forms
Public Class MainMenu
Private Sub ShowNewForm(ByVal sender As Object, ByVal e As EventArgs)
Handles NewToolStripMenuItem.Click
o.MdiParent = Me
o.Show()
End Sub
Private Sub OpenFile(ByVal sender As Object, ByVal e As EventArgs) Handles
OpenToolStripMenuItem.Click
o.MdiParent = Me
o.Show()
End Sub
Private Sub SaveAsToolStripMenuItem_Click(ByVal sender As Object, ByVal e As
EventArgs)
Dim SaveFileDialog As New SaveFileDialog
SaveFileDialog.InitialDirectory =
My.Computer.FileSystem.SpecialDirectories.MyDocuments
SaveFileDialog.Filter = "Text Files (*.txt)|*.txt|All Files (*.*)|*.*"
If (SaveFileDialog.ShowDialog(Me) = System.Windows.Forms.DialogResult.OK)
Then
Dim FileName As String = SaveFileDialog.FileName
End If
End Sub
Private Sub ExitToolsStripMenuItem_Click(ByVal sender As Object, ByVal e As
EventArgs)
Global.System.Windows.Forms.Application.Exit()
End Sub
Private Sub CutToolStripMenuItem_Click(ByVal sender As Object, ByVal e As
EventArgs)
End Sub
Private Sub CopyToolStripMenuItem_Click(ByVal sender As Object, ByVal e As
EventArgs)
' Use My.Computer.Clipboard to insert the selected text or images into the
clipboard
End Sub
Private Sub PasteToolStripMenuItem_Click(ByVal sender As Object, ByVal e As
EventArgs)
'Use My.Computer.Clipboard.GetText() or My.Computer.Clipboard.GetData to
retrieve information from the clipboard.
End Sub
Private Sub ToolBarToolStripMenuItem_Click(ByVal sender As Object, ByVal e As
EventArgs) Handles ToolBarToolStripMenuItem.Click
o.MdiParent = Me
o.Show()
End Sub
Private Sub StatusBarToolStripMenuItem_Click(ByVal sender As Object, ByVal e
As EventArgs) Handles StatusBarToolStripMenuItem.Click
o.MdiParent = Me
o.Show()
End Sub
Private Sub CascadeToolStripMenuItem_Click(ByVal sender As Object, ByVal e As
EventArgs)
Me.LayoutMdi(MdiLayout.Cascade)
End Sub
Private Sub TileVerticleToolStripMenuItem_Click(ByVal sender As Object, ByVal e
As EventArgs)
Me.LayoutMdi(MdiLayout.TileVertical)
End Sub
Private Sub TileHorizontalToolStripMenuItem_Click(ByVal sender As Object, ByVal
e As EventArgs)
Me.LayoutMdi(MdiLayout.TileHorizontal)
End Sub
Private Sub ArrangeIconsToolStripMenuItem_Click(ByVal sender As Object, ByVal
e As EventArgs)
Me.LayoutMdi(MdiLayout.ArrangeIcons)
End Sub
Private Sub CloseAllToolStripMenuItem_Click(ByVal sender As Object, ByVal e As
EventArgs)
Dim o As New Recipient
o.MdiParent = Me
o.Show()
End Sub
Private m_ChildFormNumber As Integer = 0

Private Sub UndoToolStripMenuItem_Click(ByVal sender As System.Object, ByVal
e As System.EventArgs) Handles UndoToolStripMenuItem.Click
o.MdiParent = Me
o.Show()
End Sub
Private Sub IssueBloodToolStripMenuItem_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles IssueBloodToolStripMenuItem.Click
o.MdiParent = Me
o.Show()
End Sub
Private Sub EditMenu_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles EditMenu.Click
End Sub
Private Sub OptionsToolStripMenuItem_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles OptionsToolStripMenuItem.Click
rptStr = "Donor Registration"
Dim o As New ReportForm
o.MdiParent = Me
o.Show()
End Sub
Private Sub DonarTestResultToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
DonarTestResultToolStripMenuItem.Click
rptStr = "Donor Test Result"
o.MdiParent = Me
o.Show()
End Sub
Private Sub RecipentToolStripMenuItem_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles RecipentToolStripMenuItem.Click
rptStr = "Blood Recipient"
o.MdiParent = Me
o.Show()
End Sub
Private Sub BloodStockToolStripMenuItem_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles BloodStockToolStripMenuItem.Click
rptStr = "Blood Stock"
o.MdiParent = Me
o.Show()
End Sub
Private Sub BloodReserveToolStripMenuItem_Click(ByVal sender As
BloodReserveToolStripMenuItem.Click
rptStr = "Blood Reservation"

o.MdiParent = Me
o.Show()
End Sub
Private Sub BloodExpiredToolStripMenuItem_Click(ByVal sender As
BloodExpiredToolStripMenuItem.Click
rptStr = "Blood Expired"
o.MdiParent = Me
o.Show()
End Sub
Private Sub ToolsMenu_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles ToolsMenu.Click
End Sub
End Class
Recipient
Public Class Recipient
Try
Dim cmd As New OleDbCommand("Select * from Tbl_Recipient", cn)
cn.Open()
While dr.Read
End While
dr.Close()
cn.Close()
Dim da As New OleDbDataAdapter("Select * from Tbl_Recipient", cn)
da.Fill(ds, "Mast")
cn.Close()
End If
End Try
End Sub
Try
Dim cmd As New OleDbCommand("Insert into Tbl_Recipient Values(" &
& "','" & TextBox6.Text & "','" & TextBox5.Text & "','" & ComboBox1.Text & "','" &

cn.Open()
Me.Text)
cn.Close()
Me.Close()
o.Show()
cn.Close()
End If
End Try
End Sub
Try
Me.Text)
Exit Sub
Else
Dim cmd As New OleDbCommand("Select * from Tbl_Recipient where
ReprId=" & TextBox1.Text, cn)
cn.Open()
While dr.Read
End While
dr.Close()
cn.Close()
End If

cn.Close()
End If
End Try
End Sub
Try
Dim cmd As New OleDbCommand("Update Tbl_Recipient set Name='" &
TextBox3.Text & "',Address='" & TextBox2.Text & "',City='" & TextBox4.Text &
"',PhNo='" & TextBox6.Text & "',EMail='" & TextBox5.Text & "',Btype='" &
ComboBox1.Text & "',Amount='" & TextBox7.Text & "' where ReprId=" &
TextBox1.Text, cn)
cn.Open()
Me.Text)
cn.Close()
Me.Close()
o.Show()
cn.Close()
End If
End Try
End Sub
Try
Dim cmd As New OleDbCommand("Delete from Tbl_Recipient where
ReprId=" & TextBox1.Text, cn)
cn.Open()
Me.Text)
cn.Close()
Me.Close()
o.Show()

cn.Close()
End If
End Try
End Sub
End Class
9. Validation Checks
Validation refers to checking the quality of web-site in both
simulated and live environments; whereas Verification refers to the
set of activities that ensure that website correctly implements a
specific function. Validation checks are a set of activities carried
out to ensure that the website that has been built is traceable to
user and company requirements. Software Testing is one element
of a broader topic that is often referred to as Verification and
Validation (V & V). This definition of V & V encompasses many of
the activities that we have referred to as Software Quality
Assurance (SQA).
Input designs are aimed at reducing the chance of mistakes or
errors during data entry. However, we must always assume that errors
will occur. They must be found during input and corrected prior to
storing or processing the data. It is much more difficult to correct
erroneous data after storage has taken place Methods aimed at
detecting errors in input is input validation.
First and foremost, it is essential to identify any transactions that
are not valid, that is, not acceptable. Transactions can be invalid
because they are incomplete, unauthorized, or even out of order.
Software Validation checks in this application were achieved
through a series of black-box tests that demonstrated conformity with
the company’s requirements. Both the plan and procedure were

designed to ensure that all functional requirements are satisfied; all
performance requirements are achieved; documentation is correct and
human-engineered; and other requirements are met (e.g.,
transportability, compatibility, error recovery, maintainability).
All the testing was done before this website is uploaded. These
Validation checks were carried out to ensure that:
 The input forms/output reports bear the same format at that was
required by the user
 The calculations carried out at various instances of data processing
in the application are valid and correct.
 The data processing after entry and reports generations fast
enough so as to be useful
 The application is user friendly and that the user is not facing any
problems in any part of the applications
The security provided for access to various options in the
application is
appropriately enforced-Security Testing.
The application can also perform well under peak loads of data
entry and processing –Stress Testing
The operations staff can maintain the software application easily.
There is a graceful error recovery as coded into the software
application
List of Common Validations
1. No field in a form should be left blank.
2. The name of a person cannot be numeric value. It has to be in
alphabets
3. Data has to be entered in a valid format.
4. Data of birth has to be a date previous than the current date.
5. Time has to be entered in valid format.
6. In any form, only one option can be selected from the given
number of options
7. Email address should be entered in a valid format.

10. Testing
Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design, and coding.
The increasing visibility of software as a system element and the
attendant “costs” associated with a software failure are motivating
forces for well-planned, thorough testing. It is not unusual for a
software development organization to expand 30 and 40 percent of
total project effort on testing. In the extreme, testing of human rated
software (e.g. flight control, nuclear reactor monitoring) can cost three
to five times as much as all other software engineering activities
combined.
Actually, testing presents an increasingly anomaly for the software
engineer. Earlier in the software process, the engineer attempts to
build software from an abstract concept to a tangible implementation.
Now comes testing. The engineer creates a series of test cases that
are intended to “demolish” the software that has been built. In fact,
testing is the one step in the software engineering process that could
be viewed (psychology at least) as destructive rather than
constructive.
Testing Objectives
Software testing objectives include:
 Testing is a process of executing a program with an intent of
finding an error.
 A good test case is one that has a high probability of finding an
as-yet undiscovered error.
 A successful test is one that uncovers an as-yet undiscovered
error.
The above objective implies a dramatic change in viewpoint. They
move counter to the commonly held view that a successful test is one
in which no errors are found. In fact, our objective is to design tests
that systematically uncover different classes of errors and do so with a
minimum amount of time and effort.
Testing Principles
Before applying methods to the design effective test cases, software
engineering must understand the basic principles that guide the
software testing process. Some of the most commonly followed
principles are:
 All test should be traceable to customer requirements as the
objective of testing is to uncover errors, it follows that the most
severe defects are those that cause the program to fail.
 Test should be planned long before the testing begins test
planning can begin as soon as the requirement model is complete.
Detailed definition of test cases can begin as soon as the design
model has been formed. Therefore, all tests can be planned and
designed before any code can be generated.
 The pare to principle applies to software testing Stated simply the
pare to principle implies that 80 percent of all errors uncovered
during testing will likely be traceable to 20 percent of all program
modules. The problem of course, is to isolate these suspects’
modules and to thoroughly test them.
 Testing should begin “in the small” and progress towards testing
“in the large”. The first tests planned and executed generally
focus on individual modules. As testing progresses, test shifts
focus in an attempt to find errors in integrated clusters of
modules and ultimately in the entire system.

 Exhaustive testing is not possible. The number of path
permutations for even a moderately sized program is
exceptionally large. For this reason it is impossible to execute
every combination of paths during testing. It is possible however
to adequately cover program logic and to ensure that all condition
in the procedural design have been exercised.
 To be most effective, testing should be conducted by an
independent third party. By most effective we mean, testing that
has the highest probability of finding errors.
Software project management is an umbrella activity within software
engineering. It begins before any technical activity is initiated and
continues throughout the definition, development, and maintenance of
computer software.
Sample Data
Software testing is the process that is done time and again to ensure
the perfect working of the system. Software testing is done at program
level, sub-module level, than at module level, and finally at the system
level testing is done more than one time.

The testing of various programs and modules of this system is done
with the help of trivial data i.e. two or three records were entered to
the Admin table, UserData table and Rooms table that are the
driving tables of the entire data. Now with the help of these records or
sample data the testing of various modules is done. We tested the
inventory system module using the records entered in the Rooms table
where this module displays all the records of the table, Rooms.
Similarly, login module, product module, and bill module are also
tested on the records entered in these three tables. These three
modules are responsible for adding records to the other tables. So the
testing of these modules went side by side along with some sub-
modules of administration module that give us access to other tables
of the data. Like view supplier, view ststus and system administration
sub-modules gave us access to tables supplier and UserOptions
respectively. This is done to make sure that these modules updating
the tables according to what is expected or not.
TYPES OF TESTING
The following types of tests are performed:
UNIT TESTING: This is done to check syntax and logical errors in
programs. At the time of preparation of technical specifications, unit
test data was also prepared. The coding for that program was
considered complete after verifying its output against this test data.
FUNCTIONAL TESTING: This is done for each module/submodule of
the system. Functional testing serve as a means of validating whether
the functionality of the system confers the original user requirement
i.e. does the module do what it was spposed to do? Separate
schedules were made for functional testing. It involves preparation of
test data, writing of test cases, testing for conformance to cases and
preparation of bugs listing for non-conformities.
SYSTEM TESTING: System testing is done when the entire system
has been fully integrated. The purpose of the system testing is to test
how the different modules interact with each other and whether the
entire system provides the functionality that was expected.
System testing consists of following steps:
1. Program Testing
2. String Testing
3. System Testing
4. System Documentation
5. User Acceptance Testing
ACCEPTANCE TESTING: This is the final testing when the user is
satisfied and finally accepts the software development.
VARIOUS LEVELS OF TESTING
Before implementation system is tested at three levels:
Level 1 Testing (ALPHA TESTING)

At this level a test data is prepared for testing. The system was tested
on this test data keeping the following points into consideration:
 Proper error handling
 Exit points in code
 Exception handling
 Input/Output format
 Glass box testing
 Black box testing
During this phase it was found that the exit points in the codes
which were written were not properly.
If the system is through with testing phase at Level 1 then it is passed
on to Level 2.
Level 2 Testing (BETA TESTING)
Here the testing is done on the live database. If errors are detected
then it is sent back to Level 1 for modification otherwise it is passed
onto Level 3.
This is the level at which the system actually become live and
implemented for the use of end-users.
Level 3 Testing
Here the error free and properly tested system is implemented.
TESTING STRATEGY
In this system individual application paths are very important; hence
White Box testing will be carried out.
WHITE BOX TESTING
White-Box testing, sometimes called Glass-Box testing, is a test case
design method that uses the control structure of the procedural design
to derive test cases. Using this method, the software engineer can
derive test cases that:
 Guarantee that all independent paths within a module have been
exercised at least once.
 Exercise all logical decisions on there true and false sides.
 Execute all loops at their boundaries and within their operational
bounds.
 Exercise internal data-structures to ensure their validity.
A reasonable question might be posed at this juncture: ‘Why don’t
we spend all of our energy on black-box tests? The answer lies in the
nature of software defects:
 Logic errors and incorrect assumptions are inversely proportional
to the probability that a program path will be executed.
 We often believe that a logical path is not likely to be executed
when, infact, it may be executed on a regular basis.
 Typographical errors are random

Each of these reasons provides an argument for conducting White-box
test.
TEST REVIEW
Test Review is the process which ensures that testing is carried out as
planned. Test review decides whether or not the program is ready to
be shipped out for implementation.
For each data entry screen, I prepared test data with extreme values
and tested under all relevant test condition. It was extensively tested
that all shell scripts, package, database functions are behaving in the
manner as expected of them and giving accurate results. After my own
satisfaction, the testing was done by my batch mates which were not
even concerned with this project and I asked them to put the data of
their own fashion and the defects (if any) were removed(generally
known as peer testing). I also invited the concerned users to test the
relevant data -entry screens against real data. This process helped in
rectifying/ modifying the modules time and again

11. System Security Measures
As the name indicates we needed to develop a tool for managing the
activities of inventory control we wanted security for which we needed
to differ tic the access right of general user that with the
administrator.
 Automatic generation of date at the time of data entry and also
have the option to change it.
 In the validation I check individual fields like the customer Name
can not be numeric.
 All the Ids are automatic generated by the system

 User can not delete and edit data. Only authorized user can edit
and delete data.
 System considers only the exiting value or details of master
entry.
 System has the security at user level.
 Any un-authorized person can not enter into the system because
each and every user of this system is already validated in
system. At the time of entry system will ask for the password.
12. Reports
 Donor Registration: - Here we can give report on all the donor
records made in this system in particular day.
 Donor Test Result: - Here we get all the details of donor test result
for the donor in particular day.
 Blood recipient: - Here we all the blood recipient records registered
for particular day.
 Blood Stock: This Report will give blood stock in the blood bank at
present day.
 Blood Expired: - This sales report section give list blood bag is whose
expired date is passed or about to pass.
 Blood Reserve: - Here we can get all the details of all the blood
reservation made by recipient for particular type of blood.
13. Future Scope of the Project
o We have already entered the age of Information Technology, where
all the paper work / manually managed files are about to finish,
now with the help of this user friendly software all the files stored in
the computer can be very well formatted.
o With little more modifications it will become the good software for
Blood Bank. The present “Blood Bank” project may be further
developed for more complex transactions and to meet the

requirements of modern day dynamic System Operation New
options and their respective implementation may be done for this
purpose.
14. Bibliography

New Report BloodBank

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

New Report BloodBank

Загружено:

Авторское право:

Доступные форматы

Index

1. Introduction of the Organization and the project ................. 2

The system to be developed will be referred as Blood Bank

A Blood Bank Manager is a software product suite designed to

improve the quality and management of blood bank and hospital

health care management in the areas of health process analysis and

activity-based costing. Blood Bank Manager enables you to develop

your organization and improve its effectiveness and quality of work.

Managing the key processes efficiently is critical to the success of

the pharmacy. Blood Bank Manager helps you manage your

processes. A Blood Bank Manager provides all process management

tool elements: modeling, analysis, and simulation. Documentation

though an important part of a blood bank management, is a non-

productive exercise for the intellectual human being, whose ability

lies in core areas of excellence. Hence a systematic approach to the

way documents are managed, can transform your pharmacy

retailing resources to its highest utility and advantage.

The proposed system however has the following features;

package from accidental of deliberate threats that could cause

unauthorized modifications, disclosures of destruction of the data and

protection of the information system by the use of password.

 It provides an automated registration of donor code for each type of blood,

information according to need.

donor registration, recipient registration, blood stock, blood reservation

and blood issue.

user to take expired blood form their stock.

3.1 Identification of needs

In today’s fiercely competitive business environment any organization

that aims to work properly and to grow cannot ill afford to be

indifferent towards the use of new and better work process

(technology). If a particular work process is efficient, cheaper and

firm sticks to an old work process the more disadvantaged and

 Cumbersome process: The manual generation of work for

sanction, issue and receive for each and every item is a

cumbersome process, which is prone to errors and is a tedious job.

 Time Consuming: Managing all items information, maintain the

manual manners it takes a long time with no guarantee about the

information will be available when required.

details regarding items, hardware users Required high amount of

 Not Reliable: The manual system is not reliable because it never

guarantees the accuracy of the system.

 Costly: The manual system is costly, as User has to hire a more of

entry in various registers.

3.2 Preliminary Investigation

Based on the user requirements and the detailed analysis of a

formally requested, the systems analysts, under the management’s

direction, conduct a preliminary investigation to analyze the reasons

for the request and collect various facts to respond to request in a

Preliminary or general design: In the preliminary or general design,

the features of the new system are specified. The costs of

estimated. If the project is still considered to be feasible, we move to

the detailed design stage.

Structure or Detailed design: In the detailed design stage, computer

oriented work begins in earnest. At this stage, the design of the

system becomes more structured. Structure design is a blue print of a

computer system solution to a given problem having the same

components and inter-relationship among the same components as

the original problem. Input, output and processing specifications are

drawn up in detail. In the design stage, the programming language

to be in that software. What information they want from that software.

What information they want to give to their user.

There is an increased risk of error in the manual system. Redundancy

of data creeps in the manual system and it becomes a time-consuming