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.................................38 8. Coding................................................ 38 9. Validation Checks.....................................38 10. Testing.............................................. 42 11. System Security Measures.............................51 12. Reports.............................................. 52 13. Future Scope of the Project..........................54 14. Bibliography.........................................54
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Index
1. Introduction of the Organization and the project.................22. Objective...........................................................................33. System Analysis................................................................5
3.1 Identification of needs...............................................................................................53.2 Preliminary Investigation...........................................................................................6
5. Software Paradigm Applied..............................................146. Software and Hardware Specification................................187. System Design.................................................................24
7.1 Data Flow Diagram..................................................................................................247.2 NUMBER OF MODULES AND THEIR DESCRIPTION:-..................................297.3 Input/Output Design................................................................................................38
8. Coding.............................................................................389. Validation Checks............................................................3810. Testing..........................................................................4211. System Security Measures..............................................5112. Reports.........................................................................5213. Future Scope of the Project............................................5414. Bibliography..................................................................54
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
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
DonorBlood Bank
Recipient
Stock Records
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
Issue Issue
Stock Update
DonorBlood Bank
Test Result
Zero Level DFDZero Level DFD
DFD for Donor Registration and Donor TestDFD for Donor Registration and Donor Test
Registration
Database
Test
Get Donor ID
Update
Result
Blood Test
Recipient Blood Bank
Blood Issue
Blood Stock
DFD for Recipient Registration and Blood IssueDFD for Recipient Registration and Blood Issue
Database
Database
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 Name
Primary key
UPaswd nvarchar(4) User Password
--
Table 2: Tbl_DonorTest
NAME TYPE Description
CONSTRAINT
DonorID int(5) Donor Id PKTestID 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
NAME TYPE Description
CONSTRAINT
DonorID int(5) Donor Id PKTestID int(5) Test Id --TestName nvarchar (10) Test name --TestDate smalldatetime(4) Test Date --BType nvarchar(50) Blood Type --TestResult Int(5) Test Result --
Table 4: Tbl_Recipient
NAME TYPE Description
CONSTRAINT
ReprId int(5) Recipient Id PKName 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
NAME TYPE Description
CONSTRAINT
BID int(5) Blood Stock Id
PK
BType nvarchar(50) Blood Type --NBag nvarchar(50) Number of
Blood --
SDate smalldatetime(4) Stock Date --EDate smalldatetime(4) Blood Expiry --
DateDonorID int(5) Donor Id --
Table 6: Tbl_BloodReservation
NAME TYPE Description
CONSTRAINT
BResID int(5) Blood Reservation
PK
ReprID nvarchar(50) Recipient ID --BID nvarchar(50) Stock ID --NBag nvarchar(10) Number of
Blood Bags--
BType nvarchar(10) Blood Type --RecipientType nvarchar(10) Donor or