Online Blood Donation Management System Report

Blood Bequeath Federal
INTRODUCTION
1.1. Project Overview
The Blood Donation Agent is to create an e-Information about the donor and organization that are related to donating the blood. Through this application any person who is interested in donating the blood can register himself in the same way if any organization wants to register itself with this site that can also register. Moreover if any general consumer wants to ma e re!uest blood online he can also ta e the help of this site. Admin is the main authority who can do addition" deletion" and modification if re!uired.
1.2. Project Descri tio!

This pro#ect is aimed to developing an online Blood Donation Information. The entire pro#ect has been developed technology" in mind. The Blood Donation Agent is to create an e-Information about the donor and organization that are related to donating the blood. Through this application any person who is interested in donating the blood can register himself in the same way if any organization wants to register itself with this site that can also register. Moreover if any general consumer wants to ma e re!uest blood online he can also ta e the help of this site. Admin is the main authority who can do addition" deletion" and modification if re!uired. The pro#ect has been planned to be having the view of distributed architecture" with centralized storage of the database. The application for the storage of the data has been planned. $sing the constructs of M%-%&' %erver and all the user interfaces have been designed using the A%(.)et technologies. The database connectivity is planned using the *%&' +onnection, methodology. The standards of security and data protective mechanism have been given a big choice for proper usage. eeping in view of the distributed client server computing
De art"e!t o# C$%
-- -
The application ta es care of different modules and their associated reports" which are produced as per the applicable strategies and standards that are put forwarded by the administrative staff. The entire pro#ect has been developed eeping in view of the distributed client server computing technology" in mind. The specification has been normalized up to .)/ to eliminate all the anomalies that may arise due to the database transaction that are e0ecuted by the general users and the organizational administration. The user interfaces are browser specific to give distributed accessibility for the overall system. The internal database has been selected as M%%&' server 1222. The basic constructs of table spaces" clusters and inde0es have been e0ploited to provide higher consistency and reliability for the data storage. The M%-%&' server 1222 was a choice as it provides the constructs of high-level reliability and security. The total front end was dominated using the A%(.)et technologies. At all proper levels high care was ta en to chec that the system manages the data consistency with proper business rules or validations. The database connectivity was planned using the latest *%&' +onnection, technology provided by Microsoft +orporation. The authentication and authorization was crosschec ed at all the relevant stages. The user level accessibility has been restricted into two zones namely.
De art"e!t o# C$%
-1 -
Pro&le" De#i!itio!
2.1 %'isti!( $)ste"
+annot $pload and Download the latest updates. )o use of 3eb %ervices and 4emoting. 4is of mismanagement and of data when the pro#ect is under development. 'ess %ecurity. )o proper coordination between different Applications and $sers. /ewer $sers 5 /riendly
Disadva!ta(es
-. $ser friendliness is provided in the application with various controls. 1. The system ma es the overall pro#ect management much easier and fle0ible. .. 4eadily upload the latest updates" allows user to download the alerts by clic ing the $4'. 6. There is no ris of data mismanagement at any level while the pro#ect development is under process. 7. It provides high level of security with different level of authentication.
2.2. Pro osed $)ste"

To debug the e0isting system" remove procedures those cause data redundancy" ma e navigational se!uence proper. To provide information about audits on different level and also to reflect the current wor password mechanism. status depending on organization8auditor or date. To build strong
*dva!ta(es+
$ser friendliness I provided in the application with various controls. The system ma es the overall pro#ect management much easier and fle0ible. 4eadily upload the latest updates "allows user to download the alerts by clic ing the url. It provides high level of security with different level of -. authentication. Blood Bequeath Federal
De art"e!t o# C$%
Feasi&ilit) $tud)
(reliminary investigation e0amine pro#ect feasibility" the li elihood the system will be useful to the organization. The main ob#ective of the feasibility study is to test the Technical" 9perational and :conomical feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation; Technical /easibility 9peration /easibility :conomical /easibility
,.1. Tech!ical Feasi&ilit)

The technical issue usually raised during the feasibility stage of the investigation includes the following; Does the necessary technology e0ist to do what is suggested< Do the proposed e!uipments have the technical capacity to hold the data re!uired to use the new system< 3ill the proposed system provide ade!uate response to in!uiries" regardless of the number or location of users< +an the system be upgraded if developed< Are there technical guarantees of accuracy" reliability" ease of access and data security< :arlier no system e0isted to cater to the needs of =%ecure Infrastructure Implementation %ystem>. The current system developed is technically feasible. It is a web based user interface for audit wor flow at )I+-+%D. Thus it provides an easy access to the users. The database>s purpose is to create" establish and maintain a wor flow among various entities in order to facilitate all concerned users in their various capacities or roles. (ermission to the users would be granted based on the roles specified. Therefore" it provides the technical guarantee of accuracy" reliability and security. De art"e!t o# C$% -6 Blood Bequeath Federal
Blood Bequeath Federal The software and hard re!uirements for the development of this pro#ect are not many and are already available in-house at )I+ or are available as free as open source. The wor for the pro#ect is done with the current e!uipment and e0isting software technology. )ecessary bandwidth e0ists for providing a fast feedbac to the users irrespective of the number of users using the system.
,.2. O eratio!al Feasi&ilit)

(roposed pro#ects are beneficial only if they can be turned out into information system. That will meet the organization>s operating re!uirements. 9perational feasibility aspects of the pro#ect are to be ta en as an important part of the pro#ect implementation. %ome of the important issues raised are to test the operational feasibility of a pro#ect includes the following; Is there sufficient support for the management from the users< 3ill the system be used and wor properly if it is being developed and implemented< 3ill there be any resistance from the user that will undermine the possible application benefits< This system is targeted to be in accordance with the above-mentioned issues. Beforehand" the management issues and user re!uirements have been ta en into consideration. %o there is no !uestion of resistance from the users that can undermine the possible application benefits. The well-planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status.
,.,. %co!o"ic Feasi&ilit)

A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility" the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. /inancial benefits must e!ual or e0ceed the costs. The system is economically feasible. It does not re!uire any addition hardware or software. %ince the interface for this system is developed using the e0isting resources and technologies available at )I+" There is nominal e0penditure and economical feasibility for certain. De art"e!t o# C$% -7 Blood Bequeath Federal
$)ste" *!al)sis
-.1.
location. INTRODUCTION Pur ose+ The main purpose for preparing this document is to give a general insight into the analysis and re!uirements of the e0isting system or situation and for determining the operating characteristics of the system. $co e+ This Document plays a vital role in the development life cycle ?%D'+@ and it describes the complete re!uirement of the system. It is meant for use by the developers and will be the basic during testing phase. Any changes made to the re!uirements in the future will have to go through formal change approval process. D%0%1OP%R$ R%$PON$IBI1ITI%$ O0%R0I%2+ The developer is responsible for; Developing the system" which meets the %4% and solving all the re!uirements of the system< Demonstrating the system and installing the system at clientAs location after the acceptance testing is successful. %ubmitting the re!uired user manual describing the system interfaces to wor on it and also the documents of the system. +onducting any user training that might be needed for using the system. Maintaining the system for a period of one year after installation.
$o#tware Require"e!t $ eci#icatio! .$R$/

The software" %ite :0plorer is designed for management of web sites from a remote
De art"e!t o# C$%
-B -
The "odules i!volved are+

-. *d"i!istratio!+
In this module the Administrator has the privileges to add all the Blood Croups" Blood Type" 9rganization" Type" +ountry" %tate" +ity" and 'ocation. De can search all the info about the 9rganization" Donor.
User *ccou!t+
AccountID $sername (assword $serDesc Dint&uestion Answer 4oleID Active
Fu!ctio!alit)
Association $ser Account with $ser4ole. Association $ser Account with 9rganisation. Association $ser Account with personal Details. Association $ser Account with :mployee deatails. Association $ser Account with BloodDonation Details.
De art"e!t o# C$%
-E -
*lerts+
All fields are mandatory %elect user role %elect role id %elect role name
UserRole+
4oleID 4ole)ame 4oleDesc Active
Fu!ctio!alit)+
Association user role with user Account
*lerts+
%elect 4ole Id %elect role name
BD* $tate+
De art"e!t o# C$% -F Blood Bequeath Federal
Blood Bequeath Federal %tateID %tate)ame %tate+ode %tateDesc +ountryID Active
Fu!ctio!alit)+
Association state with city Assocition state with Address
*lerts+
%elect %tate id %elect state name
Cou!tr)+
+ountryID +ountry)ame +ountryDesc +ountry+ode Active
Fu!ctio!alit)+
Association state with country Assocition state with Address
De art"e!t o# C$%
-G -
*lerts+
BD* Cit)+ +ityID +ity)ame +ityDesc +ity+ode %tateID Active %elect countryId %elect countryname %elect country code
Fu!ctio!alit)+
Association 'ocation with city Assocition Address with city.
*lerts+
%elect cityId %elect city)ane %elect state code
BD*1ocatio!+
De art"e!t o# C$% 'ocationID 'ocation)ame 'ocationDesc 'ocation+ode
--2 -

+ityID
(in code Active
Fu!ctio!alit)+
Association 'ocation with Address.
*lerts+
%elect 'ocationId %elect 'ocation )ame %elect (incode.
Blood3rou +
BloodCroupID BloodCroup Description Active
Fu!ctio!alit)+
Association Blood group with (ersonal details.
*lerts+
%elect BloodCroupID %elect BloodCroupID
Blood T) e+
BloodTypeID
De art"e!t o# C$%
--- -
Blood Bequeath Federal Type)ame TypeDesc Active
Fu!ctio!alit)+
Association Blood type with (ersonal details.
*lerts+
%elect BloodCroupID %elect Type)ame
Perso!al Details+
$serAccountID /irst)ame Middle)ame 'ast)ame :mail D9B 3eight Cender Image$4' BloodCroupID
De art"e!t o# C$%
--1 -
Blood Bequeath Federal BloodType BloodType AddressID +ontact)oH9ffice +ontact)oH4esidence Mobile)o Active
Fu!ctio!alit)+
Association personal detaials with preferd location Day Time Details.
*lerts+
%elect user account id %elect :mail id %elect date of birth
Call Ce!ter+
In this module all the employee who has been appointed by Admin will come. Admin will add all the information of employee and assign user name and password to them. By using that user name and password they will enter to their login and can search for all the donor" and about all the blood re!uest which have been made by either consumer" donor or any organization. +all center people will assign donor to related re!uest.
De art"e!t o# C$%
--. -
%" lo)ee Detail+

:mpId )ame Address (hone :mail Active
Fu!ctio!alit)+
Association :mployee Details type with user Accounts.
*lerts+
%elect :mp Id %elect email id
Do!or+
Donor is that person who is interested in donating their blood so they can register themselves through this website. If any re!uirement comes then they will be contacted and they can donate their blood. Along with it they can search for the various organization locations wise and can also ma e re!uest for blood if needed
Do!atio! Freque!cies+
/re!uency ID /re!uency Description
Fu!ctio!alit)+
Association Donor /re!uencies with Blood donation preferences.
De art"e!t o# C$%
--6 -
*lerts+
%elect /re!uency Id
Do!or Pre#erred Or(a!i4atio!+

$ser Account D 9rganization ID Active
Fu!ctio!alit)+
Association Donor preferred organization with personal details.
*lerts+
%elect user account id %elect organization id.
Or(a!i4atio!+
In this module if any organization wants to register itself then it can do it. It can also search for donor location wise and if needed then it can also ma e re!uest for blood
Or(a!i4atio!+
De art"e!t o# C$% 9rgID 9rg)ame 9rgType :mail 9rgAddrID 9rgImage$4' --7 Blood Bequeath Federal
Blood Bequeath Federal 9rgDescription +ontact)o Mobile)o Active +omment
Fu!ctio!alit)+
Association organization type with 9rganization type.
*lerts+
%elect 9rgId %elect :mail
Or(a!i4atio! T) e+
TypeID Type)ame Type Description
Fu!ctio!alit)+
Association organization type with 9rganization.
*lerts+
%elect Type Id %elect Type )ame
De art"e!t o# C$%
--B -
5*RD2*R% R%6UIR%7%NT$+
(II 1.F CDz (rocessor and Above 4AM 7-1MB and Above DDD 12 CB Dard Dis %pace and Above
$OFT2*R% R%6UIR%7%NT$+
3I)D93% 9% ?J( 8 1222 8 122 %erver 8 122. %erver@ Iisual %tudio .)et 1227 :nterprise :dition Internet Information %erver 7.2 ?II%@ Iisual %tudio .)et /ramewor ?Minimal for Deployment@ %&' %erver 1222 :nterprise :dition
De art"e!t o# C$%
--E -
$)ste" Desi(!
8.1.
Data Flow Dia(ra"s .DFD/

A data flow diagram is graphical tool used to describe and analyze movement of data
through a system. These are the central tool and the basis from which the other components are developed. The transformation of data from input to output" through processed" may be described logically and independently of physical components associated with the system. These are nown as the logical data flow diagrams. The physical data flow diagrams show the actual implements and movement of data between people" departments and wor stations. A full description of a system actually consists of a set of data flow diagrams. $sing two familiar notations Kourdon" Cane and %arson notation develops the data flow diagrams. :ach component in a D/D is labeled with a descriptive name. (rocess is further identified with a number that will be used for identification purpose. The development of D/D>% is done in several levels. :ach process in lower level diagrams can be bro en down into a more detailed D/D in the ne0t level. The lop-level diagram is often called conte0t diagram. It consists a single process bit" which plays vital role in studying the current system. The process in the conte0t level diagram is e0ploded into other process at the first level D/D. The idea behind the e0plosion of a process into more process is that understanding at one level of detail is e0ploded into greater detail at the ne0t level. This is done until further e0plosion is necessary and an ade!uate amount of detail is described for analyst to understand the process.
De art"e!t o# C$%
--F -
Blood Bequeath Federal 'arry +onstantine first developed the D/D as a way of e0pressing system re!uirements in a graphical from" this lead to the modular design. A D/D is also nown as a *bubble +hart, has the purpose of clarifying system re!uirements and identifying ma#or transformations that will become programs in system design. %o it is the starting point of the design to the lowest level of detail. A D/D consists of a series of bubbles #oined by data flows in the system.
DFD $97BO1$+
In the D/D" there are four symbols -. A s!uare defines a source?originator@ or destination of system data 1. An arrow identifies data flow. It is the pipeline through which the information flows .. A circle or a bubble represents a process that transforms incoming data flow into outgoing data flows. 6. An open rectangle is a data store" data at rest or a temporary repository of data
(rocess that transforms data flow.
%ource or Destination of data Data flow Data %tore
CON$TRUCTIN3 * DFD+
%everal rules of thumb are used in drawing D/D>%; -. (rocess should be named and numbered for an easy reference. representative of the process. 1. The direction of flow is from top to bottom and from left to right. Data traditionally flow from source to the destination although they may flow bac to the source. 9ne way to indicate this is to draw long flow line bac to a source. An alternative way is to repeat the De art"e!t o# C$% --G Blood Bequeath Federal :ach name should be
Blood Bequeath Federal source symbol as a destination. %ince it is used more than once in the D/D it is mar ed with a short diagonal. .. 3hen a process is e0ploded into lower level details" they are numbered. 6. The names of data stores and destinations are written in capital letters. (rocess and dataflow names have the first letter of each wor capitalized A D/D typically shows the minimum contents of data store. :ach data store should contain all the data elements that flow in and out. &uestionnaires should contain all the data elements that flow in and out. interfaces redundancies and li e is then accounted for often through interviews. Missing
$*I1%NT F%*TUR%$ OF DFD:$

-. The D/D shows flow of data" not of control loops and decision are controlled considerations do not appear on a D/D. 1. The D/D does not indicate the time factor involved in any process whether the dataflow ta e place daily" wee ly" monthly or yearly. .. The se!uence of events is not brought out on the D/D.
T9P%$ OF D*T* F1O2 DI*3R*7$

-. +urrent (hysical 1. +urrent 'ogical .. )ew 'ogical 6. )ew (hysical
CURR%NT P59$IC*1+
In +urrent (hysical D/D proecess label include the name of people or their positions or the names of computer systems that might provide some of the overall system-processing label includes an identification of the technology used to process the data. %imilarly data flows and data stores are often labels with the names of the actual physical media on which data are stored such as file folders" computer files" business forms or computer tapes.
CURR%NT 1O3IC*1+
De art"e!t o# C$%
-12 -
Blood Bequeath Federal The physical aspects at the system are removed as mush as possible so that the current system is reduced to its essence to the data and the processors that transform them regardless of actual physical form.
N%2 1O3IC*1;
This is e0actly li e a current logical model if the user were completely happy with he user were completely happy with the functionality of the current system but had problems with how it was implemented typically through the new logical model will differ from current logical model while having additional functions" absolute function removal and inefficient flows recognized.
N%2 P59$IC*1+
The new physical represents only the physical implementation of the new system.
RU1%$ 3O0%RNIN3 T5% DFD:$

PROC%$$ -@ )o process can have only outputs. 1@ )o process can have only inputs. If an ob#ect has only inputs than it must be a sin . .@ A process has a verb phrase label. D*T* $TOR% -@ Data cannot move directly from one data store to another data store" a process must move data. 1@ Data cannot move directly from an outside source to a data store" a process" which receives" must move data from the source and place the data into data store .@ A data store has a noun phrase label. $OURC% OR $IN; The origin and 8or destination of data. De art"e!t o# C$% -1- Blood Bequeath Federal
-@ Data cannot move direly from a source to sin it must be moved by a process 1@ A source and 8or sin has a noun phrase land
D*T* F1O2 -@ A Data /low has only one direction of flow between symbols. It may flow in both directions between a process and a data store to show a read before an update. The later is usually indicated however by two separate arrows since these happen at different type. 1@ A #oin in D/D means that e0actly the same data comes from any of two or more different processes data store or sin to a common location. .@ A data flow cannot go directly bac to the same process it leads. There must be atleast one other process that handles the data flow produce some other data flow returns the original data into the beginning process. 6@ A Data flow to a data store means update ?delete or change@. 7@ A data /low from a data store means retrieve or use.
+onte0t Diagram
*d"i!
DataBase
Call Center
Donor
Blood Donation Agent
Organization
De art"e!t o# C$%
Future -11 Use
1st 1evel DFD:s
1evel 1 DFD+ For *d"i! 7odule
Admin
1o(i! data
login
Value Abilities Table
View of value Abilities details
1evel 1 DFD+ For Users 7odule
Call Center
Login
De art"e!t o# C$% Value Abilities Table
-1. -
updating and Blood Bequeath Federal editing
DFD For Do!or Creatio!
Donor
Details
Do!or Id
Insert New Donor

Verify Data
Insert Donor Id
Verify Data
!"
Insert
Donor Details De art"e!t o# C$% -16 Blood Bequeath Federal
DFD For O erator Creatio!

Operator Id
9perator Details
Insert New Operator

Verify Data
Verify Data
"!"
"!
Insert Operator Id
Insert
Operator Details
De art"e!t o# C$%
-17 -
DFD For Call Ce!ter Creatio!
+all +enter Details
Call Center Id
Insert New Call Center
Verify Data
Verify Data
#!
#!"
Insert Call Center Id
Details Insert
Call Center
Donor
Details
De art"e!t o# C$%
-1B -
DFD #or Do!or Creatio!

Donor Details
Insert New Donor
Ierify Data $! Ierify Data Ierify Data $!"
Donor Id
Organizati on Details
$!#
Insert Donor Details Insert Donor Id
Check in Organization Check for Dates

Verify Data
Ierify Data 6.B
Check for Blood Type
Ierify Data 6.7
Check for Appointm ent Details
$!$
Blood Details
Appointment Details
Dates Details
Insert
Donor Details
De art"e!t o# C$%
-1E -
,rd 1evel DFD:$
DFD For Do!or Creatio!
Donor Details
Organization Details
Dates Details
Req est for new Donor
'enerate Donor$Id %&
#alidate Org$Id %&
0alidate Dates=Id ./
Commit %&
#alidate Blood$Id %&
#alidate App$ Id %&
Data!ase "pdated
Donar Details
Blood Details
Appointment Details
2or< Flow o# *ll 7odules

De art"e!t o# C$% -1F Blood Bequeath Federal
Administrator
(ogin data
Logs In Donar
Call
Appointment Details
Organiza tion
Center
#ario s Reports 'enerated the Donar
Blood Details Donor Report
#iew Random Information for the App Donar
Operator Report Call Center Report
8.2.
U71 Dia(ra"s
-1G Blood Bequeath Federal
De art"e!t o# C$%
Use Case Dia(ra"+

The unified modeling language allows the software engineer to e0press an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules. A $M' system is represented using five different views that describe the system from distinctly different perspective. :ach view is defined by a set of diagram" which is as follows. $ser Model Iiew i. This view represents the system from the users perspective. ii. The analysis representation describes a usage scenario from the end-users perspective.
$tructural "odel view

In this model the data and functionality are arrived from inside the system. This model view models the static structures.
Behavioral "odel view

It represents the dynamic of behavioral as parts of the system" depicting the interactions of collection between various structural elements described in the user model and structural model view.
I" le"e!tatio! 7odel 0iew

In this the structural and behavioral as parts of the system are represented as they are to be built.
%!viro!"e!tal 7odel 0iew

In this the structural and behavioral aspects of the environment in which the system is to be implemented are represented. $M' is specifically constructed through two different domains they are
De art"e!t o# C$%
-.2 -
Blood Bequeath Federal $M' Analysis modeling" which focuses on the user model and structural model views of the system.
$M' design modeling" which focuses on the behavioral modeling" implementation modeling and environmental model views.
$se case Diagrams represent the functionality of the system from a user>s point of view. $se cases are used during re!uirements elicitation and analysis to represent the functionality of the system. $se cases focus on the behavior of the system from e0ternal point of view.
*ctors are e0ternal entities that interact with the system. :0amples of actors include users li e
administrator" ban customer Letc." or another system li e central database.
Use case 7odel

SYSTEM NAME
Use case 1
Use case 2
Actor
Actor
Use case n
Use Cases o# Blood Do!atio! *(e!t I!ter#ace Use case For *d"i! 7odule
De art"e!t o# C$% -.- Blood Bequeath Federal
Blood Donation Agent Interface
Dome (age
'ogin (age
Donar Dome (age
DonorAccountDetail
*d"i!
Ma e4e!uest/orBlood
9rganization %earch (age
%earch
+ontact %
About $%
Use case For Do!or 7odule

De art"e!t o# C$% -.1 Blood Bequeath Federal
Blood Do!atio! *(e!t I!ter#ace
Dome (age 'ogin (age Donar Dome (age Donor Account Detail Ma e 4e!uest /or Blood 9rganization %earch (age %earch +ontact %
About us
Do!or
Use case For Call Ce!ter 7odule

De art"e!t o# C$% -.. Blood Bequeath Federal
Blood Do!atio! *(e!t I!ter#ace
Dome (age 'ogin (age +all +enter Dome (age Blood Donation Detail %earch Donor According To 4e!uest %earch Blood Donor
Call Ce!ter
%earch
+ontact % About $%
De art"e!t o# C$%
-.6 -
Use case For Or(a!i4atio! 7odule
Blood Donation Agent Interface
Dome (age 'ogin (age 9rganization Dome (age Donor%earch(age Ma e4e!uest/orBlood 9rganizationAccountDetail %earch +ontact %
Or(a!i4atio!
About $%
Use case name
'ogin
De art"e!t o# C$%
-.7 -
Blood Bequeath Federal Participating actors Flow of events Entry Condition Exit condition Quality Requirements Admin" Donor" +all +enter" 9rganization The Actor will give the user name and password to the system. The system will verify the authentication. The actor will enter the system by using username and password If un authenticated should be e0ited (assword must satisfy the comple0ity re!uirements.
Use case name Participating actors Flow of events Entry Condition Exit condition Quality Requirements
Admin 4egistration Admin The Admin will submit all the details and place in the application. Must satisfy all the norms given by the Blood Donation Agent interface site. %uccessful or $n successful completion of creation of account. All fields are mandatory.
Use case name Participating actors Flow of events Entry Condition Exit condition Quality Requirements Use case name Participating actors Flow of events
Donor 4egistration Donor The Donor must enter all his personal details. Iiew Dome page 4egistered Donor should be successfully logged out. :rror Message should be displayed on $n successful creation. Best :rror Dandling techni!ues. +hec on Mandatory fields.
+all +enter 4egistration +all +enter The +all +enter must enter all his personal details.
De art"e!t o# C$%
-.B -
Blood Bequeath Federal Entry Condition Exit condition Quality Requirements Use case name Participating actors Flow of events Entry Condition Exit condition Quality Requirements 9rganization 4egistration 9rganization The 9rganization must enter all his personal details. Iiew Dome page 4egistered 9rganization should be successfully logged out. :rror Message should be displayed on $n successful creation. Best :rror Dandling techni!ues. +hec on Mandatory fields. Iiew Dome page 4egistered +all +enter should be successfully logged out. :rror Message should be displayed on $n successful creation. Best :rror Dandling techni!ues. +hec on Mandatory fields.
$%6U%NC% DI*3R*7$
%e!uence Diagrams 4epresent the ob#ects participating the interaction horizontally and time vertically. $eque!ce Dia(ra" #or *d"i!
De art"e!t o# C$%
-.E -
; 'ogin
Admin $se url (ress login button
; +reate Ban Account
; 'og 9ut
(ress +reate Account
Time
$eque!ce Dia(ra" #or Do!or
; 'ogin
Donor (ress login button ?@ Cet login page ?@
; Accounts
DB
Ialidate forms ?@
(ress create accounts button ?@
$eque!ce Dia(ra" #or callce!ter
; 'ogin
; Accounts
DB
De art"e!t o# C$%
(ress login button ?@
+all +enter
-.F -
Cet login page ?@
Ialidate forms ?@
$eque!ce Dia(ra" #or or(a!i4atio!
; 'ogin
9rganization (ress login button ?@ Cet login page ?@
; Accounts
DB
Ialidate forms ?@
; 'ogin
; TJ Ialidate
; DB
$eque!ce Dia(ra" 8
(ress login button?@
Admin
Admin Dome (age
(ress Accept84e#ect Button ; Account
Ialidate -.G Blood Bequeath Federal

or 4e#ect Account?@
De art"e!t o# C$%
%elect Ialidate or 4e#ect %elect Ialidate 4eports?@ Transaction ?@
8.-. Data&ase Desi(! %!tities with *ttri&utes+ 1.*d"i!istratio!+

Use r*ccou!t+
AccountID $sername (assword $serDesc Dint&uestion Answer 4oleID Active
UserRole+
4oleID 4ole)ame 4oleDesc Active
BD*$tate+
De art"e!t o# C$%
-62 -
Blood Bequeath Federal %tateID %tate)ame %tate+ode %tateDesc +ountryID Active
Cou!tr)+
+ountryID +ountry)ame +ountryDesc +ountry+ode
BD*Cit)
+ +ityID +ity)ame +ityDesc +ity+ode %tateID Active
BD*1ocatio!+
'ocationID 'ocation)ame 'ocationDesc 'ocation+ode +ityID (in code
De art"e!t o# C$%
-6- -
Blood Bequeath Federal Active
Blood3rou +
BloodCroupID BloodCroup Description Active
BloodT) e+
BloodTypeID Type)ame TypeDesc Active
Perso!alDetails+
$serAccountID /irst)ame Middle)ame 'ast)ame :mail D9B 3eight Cender Image$4'
De art"e!t o# C$%
-61 -
Blood Bequeath Federal BloodCroupID BloodType BloodType AddressID +ontact)oH9ffice +ontact)oH4esidence Mobile)o Active
%" lo)eeDetail+
:mpId )ame Address (hone :mail
Active Do!atio!Freque!cies+
/re!uencyID /re!uency Description Active
Do!or Pre#erred Or(a!i4atio!+

$serAcountID 9rganisationID
De art"e!t o# C$%
-6. -
Or(a!isatio!+
9rgID 9rg)ame 9rgType :mail 9rgAddrID 9rgImage$4' 9rgDescription +ontact)o Mobile)o Active +omment
Or(a!isatio!T) e+
TypeID Type)ame TypeDescription 9rgImage Active
De art"e!t o# C$%
-66 -
%R Dia(ra"s
%R dia(ra" #or User *ccou!t a!d Users
User *ccou!t+
Das8 belo ngs
UserRole+
De art"e!t o# C$%
-67 -
Blood Bequeath Federal User*ccou!t+ AccountID $sername (assword $serDesc Dint&uestion Answer 4oleID UserRole+ 4oleID 4ole)ame 4oleDesc Active
%R dia(ra" #or User *ccou!t a!d Or(a!isatio!
User *ccou!t
Das8 belo ngs -6B -
Or(a!isatio!+
De art"e!t o# C$%
User*ccou!t+ AccountID $sername (assword $serDesc Dint &uestion Answer 4oleID
Or(a!isatio!+
9rgID 9rg)ame 9rgType :mail 9rgAddrID 9rgImage$4' 9rgDescription +ontact)o Mobile)o Active +omment
De art"e!t o# C$%
-6E -
%R dia(ra" #or Users *ccou!t a!d Perso!al Details
User *ccou!t+ User*ccou!t+ AccountID $sername (assword $serDesc Dint&uestion Answer 4oleID
Das8 belo ngs
Perso!al details
Perso!al Details+ /irst )ame :mail D9B 3eight Cender Image$4' BloodCroupID BloodType BloodType AddressID +ontact)oH9ffice +ontact)oH4esidence Mobile)o Active Middle)ame
De art"e!t o# C$%
-6F -
%R dia(ra" #or User *ccou!t a!d %" lo)ee Details
$ser Account
:mployee Details Das8 belo ngs
De art"e!t o# C$%
-6G -
Blood Bequeath Federal User *ccou!t+ AccountID $sername (assword $ser Desc Dint &uestion Answer 4ole ID %" lo)ee Details+ :mp Id )ame Address (hone :mail Active
%R dia(ra" #or User Role a!d Blood User accou!t
De art"e!t o# C$%
-72 -
$ser4ole
Das8 belo ngs
$ser Account
User *ccou!t+ AccountID $sername (assword $ser Desc Dint &uestion Answer 4ole ID
UserRole+ 4oleID 4ole)ame 4oleDesc Active
De art"e!t o# C$%
-7- -
dia(ra" #or $tate a!d BD* Cit)
%tate
Das8 belo ngs
BDAcity
BD*Cit)+ +ityID +ity)ame +ityDesc +ity+ode %tateID
De art"e!t o# C$%
-71 -
Active
BD*$tate+ %tateID %tate)ame %tate+ode %tateDesc +ountryID Active
De art"e!t o# C$%
-7. -
%R dia(ra" #or $tate a!d *ddress
%tate
Das8 belo ngs
Address;
De art"e!t o# C$%
-76 -
dBD*>*ddress AddressID Address'ine'ocationID +ityID %tateID +ountryID +ountryID Mipcode Active
De art"e!t o# C$%
-77 -
%R dia(ra" #or $tate a!d Cou!tr)+
%tate
Das8 belo ngs
+ountry
De art"e!t o# C$%
-7B -

Cou!tr)+ +ountryID +ountry)ame +ountryDesc +ountry+ode Active
%R dia(ra" #or 1ocatio! a!d Cit)

De art"e!t o# C$% -7E Blood Bequeath Federal
1ocatio!+
Das8 belo ngs
%tate
BD*1ocatio!+ 'ocationID 'ocation)ame 'ocationDesc 'ocation+ode +ityID (in code Active BD*$tate+ %tateID %tate)ame %tate+ode %tateDesc +ountryID Active
De art"e!t o# C$%
-7F -
%R dia(ra" #or 1ocatio! a!d Cit)
DBD*ddress+
Das8 belo ngs
Cit)+
De art"e!t o# C$%
-7G -
BD*Cit)+ dBD*>*ddress AddressID Address'ine'ocationID +ityID %tateID +ountryID +ountryID Mipcode Active +ityID +ity)ame +ityDesc +ity+ode %tateID Active
De art"e!t o# C$%
-B2 -
%R dia(ra" #or 1ocatio! a!d *ddress
BDALo%ation&
DBD*ddress+ Das8 belo ngs
De art"e!t o# C$%
-B- -
BD*1ocatio!+ 'ocationID 'ocation)ame 'ocationDesc 'ocation+ode +ityID (in code Active
DBD**ddress AddressID Address'ine'ocationID +ityID %tateID +ountryID +ountryID Mipcode Active
De art"e!t o# C$%
-B1 -
%R dia(ra" #or Blood (rou

Das8 belo ngs
Perso!al details
Blood (rou +
Perso!al details
De art"e!t o# C$%
-B. -
Blood Bequeath Federal Perso!al details+ $serAccountID /irst)ame Middle)ame

Description
Blood3rou +
BloodCroupID BloodCroup
'ast)ame
Active
:mail D9B 3eight Cender Image$4' BloodCroupID BloodType AddressID +ontact)oH9ffice +ontact)oH4esidence Mobile)o Active
De art"e!t o# C$%
-B6 -
%R dia(ra" #or Perso!al details a!d Blood Do!atio!

Perso!al details
re#ere!ces
Das8 belo ngs
Pre#erd locatio! Da) Ti"e Details.
De art"e!t o# C$%
-B7 -
Perso!al details+ $serAccountID /irst)ame Middle)ame 'ast)ame :mail D9B 3eight Cender Image$4' BloodCroupID BloodType AddressID +ontact)oH9ffice +ontact)oH4esidence Mobile)o Active
De art"e!t o# C$%
-BB -
Blood Bequeath Federal Pre#erredDo!atio!Da)Ti"e

Donor(referenceID 3ee Day Time/rom
Time/rom Time$pto $serAccountID +omment Active
De art"e!t o# C$%
-BE -
%R dia(ra" #or Do!or Freque!cies a!d Blood Do!atio! Pre#ere!ces
DonationFre'uen%ies&
Das8 belo ngs
BloodDo!atio!Pre#ere !ce
BloodDo!atio!Pre#ere!ce+
Do!atio!Freque!cies+ /re!uencyID /re!uency Description Active
(referenceID $serAccountID Donation/re!uencyID 3antToDonate3hitecells Active
De art"e!t o# C$%
-BF -
%R dia(ra" #or Do!or re#erred or(a!i4atio! a!d erso!al details
Do!ar
re#erred or(a!i4atio!
Das8 belo ngs
Persa!al Details
Do!orPre#erredOr(a!isatio!+ $serAcountID 9rganisationID Active
De art"e!t o# C$%
-BG -
Perso!al details+ $serAccountID /irst)ame Middle)ame 'ast)ame :mail D9B 3eight Cender Image$4' BloodCroupID BloodType AddressID +ontact)oH9ffice +ontact)oH4esidence Mobile)o Active
%R dia(ra" #or Or(a!i4atio! t) e a!d Or(a!i4atio! .
Or(a!i4atio! t) e De art"e!t o# C$% -E2 -
Das8 belo ngs
Or(a!i4atio! Blood Bequeath Federal
Or(a!isatio!+ Or(a!isatio!T) e+
TypeID Type)ame TypeDescription 9rgImage Active 9rgID 9rg)ame 9rgType :mail 9rgAddrID 9rgImage$4' 9rgDescription +ontact)o Mobile)o Active +omment
De art"e!t o# C$%
-E- -
8.8. Data&ase Ta&les

1.%!tities
BDAHBloodDonationDetails BDAHBloodDonation(reference BDAHBloodCroup BDAHBlood4e!uest BDAHBloodType BDAH+ity BDAH+ountry BDAHDonation/re!uencies BDAHDonor(referred9rganisation BDAH:mployeeDetail BDAH/A& BDAH'ocation BDAH9rganisation BDAH9rganisationType BDAH(ersonalDetails BDAH(referredDonationDayTime BDAH%tate BDAH$serAccount BDAH$ser4ole
2.%!tities with *ttri&utes

-. BDAHAddress AddressID Address'ine-
De art"e!t o# C$%
-E1 -
Blood Bequeath Federal 'ocationID +ityID %tateID +ountryID Mipcode Active
1. BDAHBloodDonationDetails ID DonorID DonationDate Ta erID 9rgID &uantity +omment Active
.. BDAHBloodDonation(reference (referenceID $serAccountID Donation/re!uencyID 3antToDonate3hitecells Active
6. BDAHBlood4e!uest 4e!uestID DonorId 9rgId )ame :mail (hone
De art"e!t o# C$%
-E. -
Blood Bequeath Federal +ountry %tate +ity 'ocation Blood4e!uireAddress BloodType BloodCroup AppDate 4e!Date %tatus 4e!uestType
7. BDAHBloodCroup BloodCroupID BloodCroup Description Active
B. BDAHBloodType BloodTypeID Type)ame TypeDesc Active
E. BDAH+ity +ityID +ity)ame +ityDesc +ity+ode %tateID Active
De art"e!t o# C$%
-E6 -
Blood Bequeath Federal F. BDAH+ountry +ountryID +ountry)ame +ountryDesc +ountry+ode Active
G. BDAHDonation/re!uencies /re!uencyID /re!uency Description Active
-2. BDAHDonor(referred9rganisation $serAcountID 9rganisationID Active
--. BDAH:mployeeDetail :mpId )ame Address (hone :mail Active
-1. BDAH/A& /a!ID &uestion Answer
De art"e!t o# C$%
-E7 -
-.. BDAH'ocation 'ocationID 'ocation)ame 'ocationDesc 'ocation+ode +ityID (incode Active
-6. BDAH9rganisation 9rgID 9rg)ame 9rgType :mail 9rgAddrID 9rgImage$4' 9rgDescription +ontact)o Mobile)o Active +omment
-7. BDAH9rganisationType TypeID Type)ame TypeDescription 9rgImage Active
De art"e!t o# C$%
-EB -
Blood Bequeath Federal -B. BDAH(ersonalDetails $serAccountID /irst)ame Middle)ame 'ast)ame :mail D9B 3eight Cender Image$4' BloodCroupID BloodType AddressID +ontact)oH9ffice +ontact)oH4esidence Mobile)o Active
-E. BDAH(referredDonationDayTime Donor(referenceID 3ee Day Time/rom Time$pto $serAccountID +omment Active
-F. BDAH%tate %tateID %tate)ame
De art"e!t o# C$%
-EE -
Blood Bequeath Federal %tate+ode %tateDesc +ountryID Active
-G. BDAH$serAccount AccountID $sername (assword $serDesc Dint&uestion Answer 4oleID Active
2.Data Dictio!ar)
BD*> *ddress
$! o 1 . 6 7 B E F Colu"! !a"e Data t) e AddressID Address'ine'ocationID +ityID %tateID +ountryID Mipcode Active Bigint varchar?7-1@ Bigint Bigint Bigint Bigint varchar?-2@ Bit Co!strai!t (rimary Ney )ot null /oreign ey /oreign ey /oreign ey Allow )ull Allow )ull )ot )ull re#ere!ce
BDAH'ocation BDAH+ity BDAHstate BDAH+ountry
BD*>BloodDo!atio!Details
De art"e!t o# C$%
-EF -
Blood Bequeath Federal $! o 1 . 6 7 B E F Colu"! !a"e Datat) e ID DonorID DonationDate Ta erID 9rgID &uantity +omment Active Bigint Bigint Datetime Bigint Bigint varchar?-2@ varchar?-216@ Bit Co!strai!t re#ere!ce
(rimary Ney /oreign ey BDAHBlood4e!uest )otnull /oreign ey BDAH$serAccount /oreign ey BdaH9rganisation Allow )ull Allow )ull )otnull
BD*>BloodDo!atio!Pre#ere!ce
$!o 1 . 6 7
Colu"!!a"e (referenceID $serAccountID Donation/re!uencyID 3antToDonate3hitecells Active
Datat) e bigint bigint tinyint bit bit
Co!strai!t (rimary ey /oreign ey /oreign ey Allow)ull Allow)ull
Re#ere!ce BDAH$serAccount BDAHDonation /re!uencies
BD*>Blood3rou
$! o 1 . 6
Colu"!!a"e BloodCroupID BloodCroup Description Active
Datat) e tinyint varchar?-2@ varchar?-216@ bit
Co!strai!t (rimary Ney )ot )ull Allow )ull )ot )ull
re#ere!ce
BD*>BloodRequest
De art"e!t o# C$%
-EG -
$! o 1 . 6 7 B E F G -2 --1 -. -6 -7 -B -E
Colu"!!a"e 4e!uestID DonorId 9rgId )ame :mail (hone +ountry %tate +ity 'ocation Blood4e!uireAddress BloodType BloodCroup AppDate 4e!Date %tatus 4e!uestType
Datat) e int bigint bigint varchar?72@ varchar?72@ varchar?12@ varchar?72@ varchar?72@ varchar?72@ varchar?72@ varchar?-22@ varchar?72@ varchar?72@ datetime datetime varchar?-2@ varchar?72@
Co!strai!t
Re#ere!ce
(rimary Ney /oreign ey BDAH$serAccount /oreign ey BDAH9rganisation Allow )ull Allow )ull Allow )ull Allow )ull Allow )ull Allow )ull Allow )ull Allow )ull Allow )ull Allow )ull Allow )ull Allow )ull Allow )ull Allow )ull
BD*>Cit)
$! o 1 . 6 7 B
Colu"!!a"e Datat) e +ityID +ity)ame +ityDesc +ity+ode %tateID Active bigint varchar?-22@ varchar?-216@ varchar?7@ bigint bit
Co!strai!t
Re#ere!ce
(rimary ey )ot null allownull Allownull /oreign ey BDAH%tate notnull
BD*>BloodT) e $! o 1 . 6 Colu"!!a"es Datat) es BloodTypeID Type)ame TypeDesc Active tinyint varchar?72@ varchar?-216@ bit Co!strai!t (rimary Ney )ot null Allow)ull )otnull re#ere!ce
De art"e!t o# C$%
-F2 -
BD*>Cou!tr)
$! o 1 . 6 7
Colu"!!a"e Datat) e +ountryID +ountry)ame +ountryDesc +ountry+ode Active bigint varchar?-22@ varchar?-216@ varchar?7@ bit
Co!strai!t (rimary ey )ot null Allow )ull Allow )ull )ot null
Re#ere!ce
BD*>Do!atio!Freque!cies $! o 1 . 6 Colu"!!a"e Datat) e /re!uencyID /re!uency Description Active tinyint varchar?72@ varchar?177@ bit Co!strai!t (rimary ey )ot null Allow null Allow null Re#ere!ce
BD*>Do!orPre#erredOr(a!isatio!
$! o 1 .
Colu"!!a"e $serAcountID 9rganisationI D Active
Datat) e Co!strai!t bigint bigint bit (rimary ey )ot null Allow null
Re#ere!ce
BD*>%" lo)eeDetail
$! o
Colu"!!a"e Datat) e
Co!strai!t
re#ere!ce
De art"e!t o# C$%
-F- -
Blood Bequeath Federal 1 . 6 7 B :mpId )ame Address (hone :mail Active bigint varchar?B2@ varchar?-72@ varchar?12@ varchar?17@ tinyint (rimary Ney Allow )ull Allow )ull Allow )ull Allow )ull Allow )ull
BD*>F*6
$! o 1 . 6
Colu"!!a"e Datat) e /a!ID &uestion Answer Active bigint varchar?.22@ varchar?-222@ bit
Co!strai!t (rimary ey Allow null Allow null Allow null
re#ere!ce
BD*>1ocatio!
%no 1 . 6 7 B E
+olumnname 'ocationID 'ocation)ame 'ocationDesc 'ocation+ode +ityID (incode Active
Datatype bigint varchar?-22@ varchar?-216@ varchar?7@ bigint varchar?-2@ bit
+onstraints reference (rimary Ney )ot )ull Allow null Allow null Allow null Allow null Allow null
BD*>Or(a!isatio! %no 1 . +olumnname 9rgID 9rg)ame 9rgType Datatype bigint varchar?-22@ tinyint +onstraint reference (rimary ey )ot null /oreign ey BDAH9rganisation Type
De art"e!t o# C$%
-F1 -
Blood Bequeath Federal 6 7 B E :mail 9rgAddrID 9rgImage$4' 9rgDescriptio varchar?72@ bigint varchar?-77@ varchar?-216@ Allownull /oreign ey Allownull Allownull Allownull Allownull Allownull Allownull Co!strai!t (rimary ey )ot null Allow null Allow null Allow null Re#ere!ce
BDAHAddress
n F +ontact)o varchar?12@ G Mobile)o varchar?12@ -2 Active bit -- +omment varchar?7-1@ BD*>Or(a!isatio!T) e $! Colu"!!a"e Datat) e o TypeID tinyint 1 Type)ame varchar?72@ . TypeDescription varchar?72@ 6 9rgImage varchar?.22@ 7 Active bit BD*>Pre#erredDo!atio!Da)Ti"e
$!o Colu"!!a"es
Donor(referenceID 1 3ee Day . Time/rom 6 Time$pto 7 $serAccountID B +omment E Active F BD*>Perso!alDetails $! o 1 . 6 7 B E F G -2 --1 Colu"!!a"e $serAccountID /irst)ame Middle)ame 'ast)ame :mail D9B 3eight Cender Image$4' BloodCroupID BloodType AddressID
Datatt) e
bigint varchar?-2@ varchar?-2@ varchar?-2@ bigint varchar?-216@ bit
Co!stari!t Re#ere!ce
(rimary Ney )ot null Allow null Allow null Allow null Allow null )ot null
Datat) e bigint varchar?72@ varchar?72@ varchar?72@ varchar?-22@ datetime float varchar?B@ varchar?-77@ tinyint tinyint bigint -F. -
Co!strai!t
Re#ere!ce
(rimary Ney )ot )ull Allow )ull Allow )ull Allow )ull )otnull Allow )ull )ot )ull Allow )ull /oreign ey BDAHBloodgroup /oreign ey BDAHBloodType /oreign ey BDAHAddress Blood Bequeath Federal
De art"e!t o# C$%
Blood Bequeath Federal -. -6 -7 -B +ontact)oH9ffice +ontact)oH4esidence Mobile)o Active varchar?12@ varchar?12@ varchar?12@ bit Allow )ull Allow )ull )ot )ull Allow )ull
BD*>UserRole $! o 1 . 6 Colu"!!a"e D*tat) e 4oleID 4ole)ame 4oleDesc Active tinyint varchar?72@ varchar?-216@ bit Co!strai!t (rimary ey )ot null Allow null )ot null Re#ere!ce
BD*>$tate
$!o 1 . 6 7 B
Colu"!!a"e %tateID %tate)ame %tate+ode %tateDesc +ountryID Active
Datat) e bigint varchar?-22@ varchar?7@
Co!strai!t (rimary ey )ot null Allow null
Re#ere!ce
varchar?-216 Allow null @ bigint bit /oreign Ney )ot null BDAH+ountry
BD*>User*ccou!t
De art"e!t o# C$%
-F6 -
$! o 1 . 6 7 B E F
Colu"!!a"e Datat) e AccountID $sername (assword $serDesc Dint&uestion Answer 4oleID Active bigint varchar?-22@ varchar?-22@ varchar?-216@ varchar?-77@ varchar?-77@ tinyint bit
Co!strai!t
Re#ere!ce
(rimary ey )ot null )ot null Allow null Allow null Allow null /oreign ey BDAH$ser4ole )ot null
$o#tware Develo "e!t %!viro!"e!t

?.1. I!troductio! To .Net Fra"ewor<
The .):T /ramewor is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .):T /ramewor is designed to fulfill the following ob#ectives;
To provide a consistent ob#ect-oriented programming environment whether ob#ect code is stored and e0ecuted locally" e0ecuted locally but Internet-distributed" or e0ecuted remotely. To provide a code-e0ecution environment that minimizes software deployment and versioning conflicts. To provide a code-e0ecution environment that guarantees safe e0ecution of code" including code created by an un nown or semi-trusted third party. To provide a code-e0ecution environment that eliminates the performance problems of scripted or interpreted environments.
De art"e!t o# C$%
-F7 -
To ma e the developer e0perience consistent across widely varying types of applications" such as 3indows-based applications and 3eb-based applications. To build all communication on industry standards to ensure that code based on the .):T /ramewor can integrate with any other code.
The .):T /ramewor has two main components; the common language runtime and the .):T /ramewor class library. The common language runtime is the foundation of the .):T /ramewor . Kou can thin of the runtime as an agent that manages code at e0ecution time" providing core services such as memory management" thread management" and 4emoting" while also enforcing strict type safety and other forms of code accuracy that ensure security and robustness. In fact" the concept of code management is a fundamental principle of the runtime. +ode that targets the runtime is nown as managed code" while code that does not target the runtime is nown as unmanaged code.
F%*TUR%$ OF T5% CO77ON 1*N3U*3% RUNTI7%+

The common language runtime manages memory" thread e0ecution" code e0ecution" code safety verification" compilation" and other system services. These features are intrinsic to the managed code that runs on the common language runtime. 3ith regards to security" managed components are awarded varying degrees of trust" depending on a number of factors that include their origin ?such as the Internet" enterprise networ " or local computer@. This means that a managed component might or might not be able to perform file-access operations" registry-access operations" or other sensitive functions" even if it is being used in the same active application. The runtime enforces code access security. /or e0ample" users can trust that an e0ecutable embedded in a 3eb page can play an animation on screen or sing a song" but cannot access their personal data" file system" or networ . The security features of the runtime thus enable legitimate Internet-deployed software to be e0ceptionally featuring rich. The runtime also enforces code robustness by implementing a strict type- and codeverification infrastructure called the common type system ?+T%@. The +T% ensures that all managed code is self-describing. The various Microsoft and third-party language compilers
De art"e!t o# C$%
-FB -
Blood Bequeath Federal Cenerate managed code that conforms to the +T%. This means that managed code can consume other managed types and instances" while strictly enforcing type fidelity and type safety. In addition" the managed environment of the runtime eliminates many common software issues. /or e0ample" the runtime automatically handles ob#ect layout and manages references to ob#ects" releasing them when they are no longer being used. This automatic memory management resolves the two most common application errors" memory lea s and invalid memory references. The runtime also accelerates developer productivity. /or e0ample" programmers can write applications in their development language of choice" yet ta e full advantage of the runtime" the class library" and components written in other languages by other developers. Any compiler vendor who chooses to target the runtime can do so. 'anguage compilers that target the .):T /ramewor ma e the features of the .):T /ramewor available to e0isting code written in that language" greatly easing the migration process for e0isting applications. .N%T FR*7%2OR; C1*$$ 1IBR*R9 The .):T /ramewor class library is a collection of reusable types that tightly integrate with the common language runtime. The class library is ob#ect oriented" providing types from which your own managed code can derive functionality. This not only ma es the .):T /ramewor types easy to use" but also reduces the time associated with learning new features of the .):T /ramewor . In addition" third-party components can integrate seamlessly with classes in the .):T /ramewor . /or e0ample" the .):T /ramewor collection classes implement a set of interfaces that you can use to develop your own collection classes. Kour collection classes will blend seamlessly with the classes in the .):T /ramewor . As you would e0pect from an ob#ect-oriented class library" the .):T /ramewor types enable you to accomplish a range of common programming tas s" including tas s such as string management" data collection" database connectivity" and file access. In addition to these common tas s" the class library includes types that support a variety of specialized development scenarios.
De art"e!t o# C$%
-FE -
Blood Bequeath Federal /or e0ample" you can use the .):T /ramewor to develop the following types of applications and services;

+onsole applications. %cripted or hosted applications. 3indows C$I applications ?3indows /orms@. A%(.):T applications. JM' 3eb services. 3indows services. /or e0ample" the 3indows /orms classes are a comprehensive set of reusable types that
vastly simplify 3indows C$I development. If you write an A%(.):T 3eb /orm application" you can use the 3eb /orms classes.
C1I%NT *PP1IC*TION D%0%1OP7%NT

+lient applications are the closest to a traditional style of application in 3indows-based programming. These are the types of applications that display windows or forms on the des top" enabling a user to perform a tas . +lient applications include applications such as word processors and spreadsheets" as well as custom business applications such as data-entry tools" reporting tools" and so on. +lient applications usually employ windows" menus" buttons" and other C$I elements" and they li ely access local resources such as the file system and peripherals such as printers. Another ind of client application is the traditional ActiveJ control ?now replaced by the managed 3indows /orms control@ deployed over the Internet as a 3eb page. This application is much li e other client applications; it is e0ecuted natively" has access to local resources" and includes graphical elements. In the past" developers created such applications using +8+OO in con#unction with the Microsoft /oundation +lasses ?M/+@ or with a rapid application development ?4AD@
De art"e!t o# C$%
-FF -
Blood Bequeath Federal environment such as MicrosoftP Iisual BasicP. The .):T /ramewor incorporates aspects of these e0isting products into a single" consistent development environment that drastically simplifies the development of client applications. The 3indows /orms classes contained in the .):T /ramewor are designed to be used for C$I development. Kou can easily create command windows" buttons" menus" toolbars" and other screen elements with the fle0ibility necessary to accommodate shifting business needs. /or e0ample" the .):T /ramewor provides simple properties to ad#ust visual attributes associated with forms. In some cases the underlying operating system does not support changing these attributes directly" and in these cases the .):T /ramewor automatically recreates the forms. This is one of many ways in which the .):T /ramewor interface" ma ing coding simpler and more consistent. integrates the developer
*$P.N%T
$erver * licatio! Develo "e!t
%erver-side applications in the managed world are implemented through runtime hosts. $nmanaged applications host the common language runtime" which allows your custom managed code to control the behavior of the server. This model provides you with all the features of the common language runtime and class library while gaining the performance and scalability of the host server. The following illustration shows a basic networ schema with managed code running in different server environments. %ervers such as II% and %&' %erver can perform standard operations while your application logic e0ecutes through the managed code.
$erver=$ide 7a!a(ed Code+

A%(.):T is the hosting environment that enables developers to use the .):T /ramewor to target 3eb-based applications. Dowever" A%(.):T is more than #ust a runtime hostQ it is a complete architecture for developing 3eb sites and Internet-distributed ob#ects using managed code. Both 3eb /orms and JM' 3eb services use II% and A%(.):T as the publishing
De art"e!t o# C$%
-FG -
Blood Bequeath Federal mechanism for applications" and both have a collection of supporting classes in the .):T /ramewor . If you develop and publish your own JM' 3eb service" the .):T /ramewor provides a set of classes that conform to all the underlying communication standards" such as %9A(" 3%D'" and JM'. $sing those classes enables you to focus on the logic of your service" without concerning yourself with the communications infrastructure re!uired by distributed software development. /inally" li e 3eb /orms pages in the managed environment" your JM' 3eb service will run with the speed of native machine language using the scalable communication of II%.
*ctive $erver Pa(es.N%T

A%(.):T is a programming framewor built on the common language runtime that can be used on a server to build powerful 3eb applications. A%(.):T offers several important advantages over previous 3eb development models; %!ha!ced Per#or"a!ce. A%(.):T is compiled common language runtime code running on the server. $nli e its interpreted predecessors" A%(.):T can ta e advantage of early binding" #ust-in-time compilation" native optimization" and caching services right out of the bo0. This amounts to dramatically better performance before you ever write a line of code. 2orld=Class Tool $u ort. The A%(.):T framewor is complemented by a rich toolbo0 and designer in the Iisual %tudio integrated development environment. 3K%I3KC editing" drag-and-drop server controls" and automatic deployment are #ust a few of the features this powerful tool provides. Power a!d Fle'i&ilit). Because A%(.):T is based on the common language runtime" the power and fle0ibility of that entire platform is available to 3eb application developers. The .):T /ramewor class library" Messaging" and Data Access solutions are all seamlessly accessible from the 3eb. A%(.):T is also language-independent" so you can choose the language that best applies to your application or partition your application across many languages. /urther" common language runtime interoperability guarantees that your e0isting investment in +9M-based development is preserved when migrating to A%(.):T. $i" licit). A%(.):T ma es it easy to perform common tas s" from simple form submission and client authentication to deployment and site configuration. /or e0ample" the De art"e!t o# C$% -G2 Blood Bequeath Federal
Blood Bequeath Federal A%(.):T page framewor allows you to build user interfaces that cleanly separate
application logic from presentation code and to handle events in a simple" Iisual Basic - li e forms processing model. Additionally" the common language runtime simplifies development" with managed code services such as automatic reference counting and garbage collection. 7a!a(ea&ilit). A%(.):T employs a te0t-based" hierarchical configuration system" which simplifies applying settings to your server environment and 3eb applications. Because configuration information is stored as plain te0t" new settings may be applied without the aid of local administration tools. This Rzero local administrationR philosophy e0tends to deploying A%(.):T $cala&ilit) a!d *vaila&ilit). A%(.):T has been designed with scalability in mind" with features specifically tailored to improve performance in clustered and multiprocessor environments. /urther" processes are closely monitored and managed by the A%(.):T runtime" so that if one misbehaves ?lea s" deadloc s@" a new process can be created in its place" which helps eep your application constantly available to handle re!uests. Custo"i4a&ilit) a!d %'te!si&ilit). A%(.):T delivers a well-factored architecture that allows developers to Rplug-inR their code at the appropriate level. In fact" it is possible to e0tend or replace any subcomponent of the A%(.):T runtime with your own custom-written component. Implementing custom authentication or state services has never been easier. $ecurit). 3ith built in 3indows authentication and per-application configuration" you can be assured that your applications are secure. 1*N3U*3% $UPPORT
The Microsoft .):T (latform currently offers built-in support for three languages; +S" Iisual Basic" and T%cript.
25*T I$ *$P.N%T 2%B FOR7$@ The A%(.):T 3eb /orms page framewor is a scalable common language runtime programming model that can be used on the server to dynamically generate 3eb pages.
De art"e!t o# C$%
-G- -
Blood Bequeath Federal Intended as a logical evolution of A%( ?A%(.):T provides synta0 compatibility with e0isting pages@" the A%(.):T 3eb /orms framewor has been specifically designed to address a number of ey deficiencies in the previous model. In particular" it provides; The ability to create and use reusable $I controls that can encapsulate common functionality and thus reduce the amount of code that a page developer has to write. The ability for developers to cleanly structure their page logic in an orderly fashion ?not Rspaghetti codeR@. The ability for development tools to provide strong 3K%I3KC design support for pages ?e0isting A%( code is opa!ue to tools@. COD%=B%5IND 2%B FOR7$ A%(.):T supports two methods of authoring dynamic pages. The first is the method shown in the preceding samples" where the page code is physically declared within the originating .asp0 file. An alternative approach-- nown as the code-behind method--enables the page code to be more cleanly separated from the DTM' content into an entirely separate file.
CA.N%T *DO.N%T O0%R0I%2

AD9.):T is an evolution of the AD9 data access model that directly addresses user re!uirements for developing scalable applications. It was designed specifically for the web with scalability" statelessness" and JM' in mind. AD9.):T uses some AD9 ob#ects" such as the Co!!ectio! and Co""a!d ob#ects" and also introduces new ob#ects. Ney new AD9.):T ob#ects include the Data$et" DataReader" and Data*da ter. The important distinction between this evolved stage of AD9.):T and previous data architectures is that there e0ists an ob#ect -- the Data$et -- that is separate and distinct from any data stores. Because of that" the Data$et functions as a standalone entity. Kou can thin of the
De art"e!t o# C$%
-G1 -
Blood Bequeath Federal Data%et as an always disconnected recordset that nows nothing about the source or destination of the data it contains. Inside a Data$et" much li e in a database" there are tables" columns" relationships" constraints" views" and so forth. A Data*da ter is the ob#ect that connects to the database to fill the Data$et. Then" it connects bac to the database to update the data there" based on operations performed while the Data$et held the data. In the past" data processing has been primarily connection-based. )ow" in an effort to ma e multi-tiered apps more efficient" data processing is turning to a message-based approach that revolves around chun s of information. At the center of this approach is the Data*da ter" which provides a bridge to retrieve and save data between a Data$et and its source data store. It accomplishes this by means of re!uests to the appropriate %&' commands made against the data store.

Co!!ectio!s. /or connection to and managing transactions against a database. Co""a!ds. /or issuing %&' commands against a database. DataReaders. /or reading a forward-only stream of data records from a %&' %erver data source. Data$ets. /or storing" 4emoting and programming against flat data" JM' data and relational data. Data *da ters. /or pushing data into a Data$et" and reconciling data against a database. @.
Co!!ectio!s+ +onnections are used to Atal toA databases" and are represented by provider-specific classes such as $qlCo!!ectio!. +ommands travel over connections and resultsets are returned in the form of streams which can be read by a DataReader ob#ect" or pushed into a Data$et ob#ect. Co""a!ds+ +ommands contain the information that is submitted to a database" and are represented by provider-specific classes such as $qlCo""a!d. A command can be a stored procedure call" an $(DAT: statement" or a statement that returns results. Kou can also use input and output
De art"e!t o# C$%
-G. -
Blood Bequeath Federal parameters" and return values as part of your command synta0. The e0ample below shows how to issue an I)%:4T statement against the Northwi!d database. DataReaders+ The DataReader ob#ect is somewhat synonymous with a read-only8forward-only cursor over data. The DataReader A(I supports flat as well as hierarchical data. A DataReader ob#ect is returned after e0ecuting a command against a database. The format of the returned DataReader ob#ect is different from a recordset. /or e0ample" you might use the DataReader to show the results of a search list in a web page. $61 $%R0%R A database management" or DBM%" gives the user access to their data and helps them transform the data into information. %uch database management systems include dBase" parado0" IM%" %&' %erver and %&' %erver. These systems allow users to create" update and e0tract information from their database. A database is a structured collection of data. Data refers to the characteristics of people" things and events. %&' %erver stores each data item in its own fields. In %&' %erver" the fields relating to a particular person" thing or event are bundled together to form a single complete unit of data" called a record ?it can also be referred to as raw or an occurrence@. :ach record is made up of a number of fields. )o two fields in a record can have the same field name. During an %&' %erver Database design pro#ect" the analysis of your business needs identifies all the fields or attributes of interest. If your business needs change over time" you define any additional fields or change the definition of e0isting fields. $61 $erver Ta&les
%&' %erver stores records relating to each other in a table. Different tables are created for the various groups of information. 4elated tables are grouped together to form a database.
Pri"ar) ;e) :very table in %&' %erver has a field or a combination of fields that uni!uely identifies each record in the table. The $ni!ue identifier is called the (rimary Ney" or simply the Ney. The primary ey provides the means to distinguish one record from all other in a table. It allows the user and the database system to identify" locate and refer to one particular record in the database.
De art"e!t o# C$%
-G6 -
Relatio!al Data&ase %ometimes all the information of interest to a business operation can be stored in one table. %&' %erver ma es it very easy to lin the data in multiple tables. Matching an employee to the department in which they wor is one e0ample. This is what ma es %&' %erver a relational database management system" or 4DBM%. It stores data in two or more tables and enables you to define relationships between the table and enables you to define relationships between the tables. Forei(! ;e) 3hen a field is one table matches the primary ey of another field is referred to as a foreign ey. A foreign ey is a field or a group of fields in one table whose values match those of the primary ey of another table. Re#ere!tial I!te(rit) )ot only does %&' %erver allow you to lin multiple tables" it also maintains consistency between them. :nsuring that the data among related tables is correctly matched is referred to as maintaining referential integrity.
CODIN3
2%BCONFI3 FI1%+.Desi(! Code/ $sed to set the connections of each page.
<?xml version="1.0"?> <!-Note: As an alternative to hand editing this file yo !an se the "e# admin tool to !onfig re settings for yo r a$$li!ation. %se the &e#site->As$.Net 'onfig ration o$tion in (is al )t dio. A f ll list of settings and !omments !an #e fo nd in ma!hine.!onfig.!omments s ally lo!ated in *&indo"s*+i!rosoft.Net*,rame"or-*v..x*'onfig --> <!onfig ration> <a$$)ettings>
De art"e!t o# C$%
-G7 -
Blood Bequeath Federal <add -ey="'onn)tr" val e="data so r!e=/A+0A.1'A231.45data#ase=3lood3e6 eath,ederalAgent5integrated se! rity=ss$i"7> <7a$$)ettings> <!onne!tion)trings> <add name="3lood1onationAgent'onne!tion)tring" !onne!tion)tring="1ata )o r!e=/A+0A-.1'A231.458nitial 'atalog=3lood1onationAgent5integrated se! rity=ss$i" $roviderName=")ystem.1ata.)6l'lient" 7> <7!onne!tion)trings> <system."e#> <!-)et !om$ilation de# g="tr e" to insert de# gging sym#ols into the !om$iled $age. 3e!a se this affe!ts $erforman!e9 set this val e to tr e only d ring develo$ment. --> <!om$ilation de# g="tr e"> <assem#lies> <add assem#ly=")ystem.1esign9 (ersion=..0.0.09 ' lt re=ne tral9 : #li!;ey<o-en=304,2,=,11120A4A"7> <add assem#ly=")ystem.&e#.>xtensions9 (ersion=1.0.?10.2.09 ' lt re=ne tral9 : #li!;ey<o-en=413,4@2?A14?A>42"7> <add assem#ly=")ystem.&e#.>xtensions.1esign9 (ersion=1.0.?10.2.09 ' lt re=ne tral9 : #li!;ey<o-en=413,4@2?A14?A>42"7> <add assem#ly=")ystem.&indo"s.,orms9 (ersion=..0.0.09 ' lt re=ne tral9 : #li!;ey<o-en=3==A2'2?1B4A>0@B"7><7assem#lies><7!om$ilation> <!-<he <a thenti!ation> se!tion ena#les !onfig ration of the se! rity a thenti!ation mode sed #y A):.N>< to identify an in!oming ser. --> <a thenti!ation mode="&indo"s"7> <!-<he <! stom>rrors> se!tion ena#les !onfig ration of "hat to do if7"hen an nhandled error o!! rs d ring the exe! tion of a re6 est. )$e!ifi!ally9 it ena#les develo$ers to !onfig re html error $ages to #e dis$layed in $la!e of a error sta!- tra!e. <! stom>rrors mode="/emoteCnly" defa lt/edire!t="Deneri!>rror:age.htm"> <error stat s'ode="A04" redire!t="NoA!!ess.htm" 7>
De art"e!t o# C$%
-GB -
Blood Bequeath Federal <error stat s'ode="A0A" redire!t=",ileNot,o nd.htm" 7> <7! stom>rrors> --> <7system."e#> <7!onfig ration>
User 1o(i! For"

sing )ystem5 sing )ystem.1ata5 sing )ystem.'onfig ration5 sing )ystem.'olle!tions5 sing )ystem.&e#5 sing )ystem.&e#.)e! rity5 sing )ystem.&e#.%85 sing )ystem.&e#.%8.&e#'ontrols5 sing )ystem.&e#.%8.&e#'ontrols.&e#:arts5 sing )ystem.&e#.%8.Etml'ontrols5 $ #li! $artial !lass Fogin : )ystem.&e#.%8.:age G 'he!-%ser ser = ne" 'he!-%serHI5 %serA!!o nt3 sinessFayer a!!o nt = ne" %serA!!o nt3 sinessFayerHI5 CrganiJationA!!o nt3 sinessFayer org = ne" CrganiJationA!!o nt3 sinessFayerHI5 $rote!ted void :ageKFoadHo#Le!t sender9 >ventArgs eI G txt%sername.,o! sHI5 M $rote!ted void #tnFoginK'li!-Ho#Le!t sender9 >ventArgs eI G try G ser.%sername = txt%sername.<ext5 ser.:ass"ord = txt:ass"ord.<ext5 77'he!- %ser if H ser.Det%serHI == tr eI G a!!o nt.%sername = txt%sername.<ext5 1ata)et ds = ne" 1ata)etHI5 ds = a!!o nt.DetA!!o nt8dHI5 string A!8d = ds.<a#lesN0O./o"sN0ON0O.<o)tringHI5 )essionN" sername"O = txt%sername.<ext5 )essionN"A!id"O = A!8d5 1ata)et ds1 = ne" 1ata)etHI5 a!!o nt.A!!o ntid =int.:arseHA!8dI5 ds1 = a!!o nt.DetAddress8dHI5 )essionN"addid"O = ds1.<a#lesN0O./o"sN0ON0O.<o)tringHI5 /es$onse./edire!tH"P71onor71onorEome.as$x"I5 M else 8mage..(isi#le = tr e5 l#l+sg.<ext = "0o r Fogin Attem$t 8s ,ailed :lJ try Again....!"5
De art"e!t o# C$%
-GE -

txt:ass"ord.<ext = ""5 txt%sername.,o! sHI5 77'he!-ing CrganiJation if H ser.DetCrganiJationHI == tr eI G a!!o nt.%sername = txt%sername.<ext5 1ata)et ds = ne" 1ata)etHI5 ds = a!!o nt.DetA!!o nt8dHI5 string A!8d = ds.<a#lesN0O./o"sN0ON0O.<o)tringHI5 )essionN" sername"O = txt%sername.<ext5 )essionN"A!id"O = A!8d5 1ata)et ds1 = ne" 1ata)etHI5 org.Crgid =int.:arseHA!8dI5 ds1 = org.DetCrgAddress8dHI5 )essionN"addid"O=ds1.<a#lesN0O./o"sN0ON0O.<o)tringHI5 /es$onse./edire!tH"P7CrganiJation7CrganiJationEome.as$x"I5 M else 8mage..(isi#le = tr e5 l#l+sg.<ext = "0o r Fogin Atem$t 8s ,ailed :lJ try Again....!"5 txt:ass"ord.<ext = ""5 txt%sername.,o! sHI5 77>m$loyee 'he!-ing if H ser.'he!->m$loyeeHI == tr eI G a!!o nt.%sername = txt%sername.<ext5 1ata)et ds = ne" 1ata)etHI5 ds = a!!o nt.DetA!!o nt8dHI5 string A!8d = ds.<a#lesN0O./o"sN0ON0O.<o)tringHI5 )essionN" sername"O = txt%sername.<ext5 )essionN"A!id"O = A!8d5 /es$onse./edire!tH"P7'all'enter7'all'enterEome.as$x"I5 M M M
Testi!(
B.1. INTRODUCTION
%oftware testing is a critical element of software !uality assurance and represents the ultimate review of specification" design and coding. In fact" testing is the one step in the software engineering process that could be viewed as destructive rather than constructive. A strategy for software testing integrates software test case design methods into a wellplanned series of steps that result in the successful construction of software. Testing is the set of activities that can be planned in advance and conducted systematically. The underlying motivation of program testing is to affirm software !uality with methods that can economically and effectively apply to both strategic to both large and small-scale systems.
De art"e!t o# C$%
-GF -
Blood Bequeath Federal B.2. $TR*T%3IC *PPRO*C5 TO $OFT2*R% T%$TIN3 The software engineering process can be viewed as a spiral. Initially system engineering defines the role of software and leads to software re!uirement analysis where the information domain" functions" behavior" performance" constraints and validation criteria for software are established. Moving inward along the spiral" we come to design and finally to coding. To develop computer software we spiral in along streamlines that decrease the level of abstraction on each turn. $)IT T:%TI)C
M9D$': T:%TI)C
Component Testing
%$B-%K%T:M T:%I)C
Integration Testing
%K%T:M T:%TI)C
B.,. U!it Testi!(

A++:(TA)+: $nit testing focuses verification effort on the smallest unit of software design" the module. The T:%TI)C User Testing unit testing we have is white bo0 oriented and some modules the steps are conducted in parallel. 1. 25IT% BOC T%$TIN3 This type of testing ensures that All independent paths have been e0ercised at least once All logical decisions have been e0ercised on their true and false sides All loops are e0ecuted at their boundaries and within their operational bounds All internal data structures have been e0ercised to assure their validity.
To follow the concept of white bo0 testing we have tested each form .we have created independently to verify that Data flow is correct" All conditions are e0ercised to chec their validity" All loops are e0ecuted on their boundaries. De art"e!t o# C$% -GG Blood Bequeath Federal
Blood Bequeath Federal 2. B*$IC P*T5 T%$TIN3 :stablished techni!ue of flow graph with +yclomatic comple0ity was used to derive test cases for all the functions. The main steps in deriving test cases were; $se the design of the code and draw correspondent flow graph. Determine the +yclomatic comple0ity of resultant flow graph" using formula; I?C@U:-)O1 or I?C@U(O- or I?C@U)umber 9f 4egions 3here I?C@ is +yclomatic comple0ity" : is the number of edges" ) is the number of flow graph nodes" ( is the number of predicate nodes. Determine the basis of set of linearly independent paths. ,. CONDITION*1 T%$TIN3 In this part of the testing each of the conditions were tested to both true and false aspects. And all the resulting paths were tested. %o that each path that may be generate on particular condition is traced to uncover any possible errors. -. D*T* F1O2 T%$TIN3 This type of testing selects the path of the program according to the location of definition and use of variables. This ind of testing was used only when some local variable were declared. The definition-use chain method was used in this type of testing. These were particularly useful in nested statements. 8. 1OOP T%$TIN3 In this type of testing all the loops are tested to all the limits possible. The following e0ercise was adopted for all loops; All the loops were tested at their limits" #ust above them and #ust below them. All the loops were s ipped at least once. /or nested loops test the inner most loop first and then wor outwards.
De art"e!t o# C$% Federal
--22 -
Blood Bequeath
Blood Bequeath Federal /or concatenated loops the values of dependent loops were set with the help of connected loop. $nstructured loops were resolved into nested loops or concatenated loops and tested as above. :ach unit has been separately tested by the development team itself and all the input have been validated.
Out ut $cree!s
5o"e Pa(e
--2- -
Blood Bequeath
*d"i! 1o(i!
--21 -
Blood Bequeath
*d"i! 5o"e
*dd !ew Or(a!i4atio!

De art"e!t o# C$% Federal --2. Blood Bequeath
Retrievi!( Or(a!i4atio! i!#or"atio!
*DD N%2 COUNTR9

De art"e!t o# C$% Federal --26 Blood Bequeath
Cou!tr) I!#or"atio!
*DD N%2 $T*T%
--27 -
Blood Bequeath
$tate I!#or"atio!
--2B -
Blood Bequeath
*DD N%2 CIT9
Cit) I!#or"atio!
--2E -
Blood Bequeath
*DD N%2 1OC*TION
1ocatio! I!#or"atio!
Re(istratio! For" For *ll Users

De art"e!t o# C$% Federal --2F Blood Bequeath
1o(i! #or"
User 5o"e
De art"e!t o# C$% Federal --2G Blood Bequeath
$earchForDo!or
U date *ccou!t Details

De art"e!t o# C$% Federal ---2 Blood Bequeath
Request #or &lood
CONC1U$ION
De art"e!t o# C$% Federal ---- Blood Bequeath
Blood Bequeath Federal It has been a great pleasure for me to wor on this e0citing and challenging pro#ect. This pro#ect proved good for me as it provided practical nowledge of not only programming in A%(.):T and IB.):T web based application and no some e0tent 3indows Application and %&' %erver" but also about all handling procedure related with DBlood Bequeath FederalE. It also provides nowledge about the latest technology used in developing web enabled application and client server technology that will be great demand in future. This will provide better opportunities and guidance in future in developing pro#ects independently.
B%N%FIT$+ The pro#ect is identified by the merits of the system offered to the user. The merits of this pro#ect are as follows; It>s a web-enabled pro#ect. This pro#ect offers user to enter the data through simple and interactive forms. This is very helpful for the client to enter the desired information through so much simplicity. The user is mainly more concerned about the validity of the data" whatever he is entering. There are chec s on every stages of any new creation" data entry or updation so that the user cannot enter the invalid data" which can create problems at later date. %ometimes the user finds in the later stages of using pro#ect that he needs to update some of the information that he entered earlier. There are options for him by which he can update the records. Moreover there is restriction for his that he cannot change the primary data field. This eeps the validity of the data to longer e0tent. $ser is provided the option of monitoring the records he entered earlier. De can see the desired records with the variety of options provided by him.
---1 -
Blood Bequeath
Blood Bequeath Federal /rom every part of the pro#ect the user is provided with the lin s through framing so that he can go from one option of the pro#ect to other as per the re!uirement. This is bound to be simple and very friendly as per the user is concerned. That is" we can sat that the pro#ect is user friendly which is one of the primary concerns of any good pro#ect. Data storage and retrieval will become faster and easier to maintain because data is stored in a systematic manner and in a single database. Decision ma ing process would be greatly enhanced because of faster processing of information since data collection from information available on computer ta es much less time then manual system. Allocating of sample results becomes much faster because at a time the user can see the records of last years. :asier and faster data transfer through latest technology associated with the computer and communication. Through these features it will increase the efficiency" accuracy and transparency"
F.1 1I7IT*TION$+ The size of the database increases day-by-day" increasing the load on the database bac up and data maintenance activity. Training for simple computer operations is necessary for the users wor ing on the system.
---. -
Blood Bequeath
BIB1IO3R*P59
FOR .N%T IN$T*11*TION www.support.mircosoft.com FOR D%P1O97%NT *ND P*C;IN3 ON $%R0%R www.developer.com www.-7seconds.com FOR $61 www.msdn.microsoft.com FOR *$P.N%T www.msdn.microsoft.com8net8!uic start8aspplus8default.com www.asp.net www.fme0pense.com8!uic start8aspplus8default.com www.asptoday.com www.aspfree.com www.6guysfromrolla.com8inde0.asp0
---6 -
Blood Bequeath
---7 -
Blood Bequeath
---B -
Blood Bequeath

Online Blood Donation Management System Report

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Online Blood Donation Management System Report

Hochgeladen von

Copyright:

Verfügbare Formate

Blood Bequeath Federal

1.2. Project Descri tio!

Blood Bequeath Federal

Blood Bequeath Federal

Blood Bequeath Federal

Blood Bequeath Federal

2.2. Pro osed $)ste"

Blood Bequeath Federal

,.1. Tech!ical Feasi&ilit)

,.2. O eratio!al Feasi&ilit)

,.,. %co!o"ic Feasi&ilit)

Blood Bequeath Federal

$o#tware Require"e!t $ eci#icatio! .$R$/

Blood Bequeath Federal

Blood Bequeath Federal

The "odules i!volved are+

Blood Bequeath Federal

Blood Bequeath Federal

Blood Bequeath Federal %tateID %tate)ame %tate+ode %tateDesc +ountryID Active

Blood Bequeath Federal

Blood Bequeath Federal

Blood Bequeath Federal

Blood Bequeath Federal

Blood Bequeath Federal

Blood Bequeath Federal Type)ame TypeDesc Active

Blood Bequeath Federal

Blood Bequeath Federal

Blood Bequeath Federal

%" lo)ee Detail+

Blood Bequeath Federal

Blood Bequeath Federal

Do!or Pre#erred Or(a!i4atio!+

Blood Bequeath Federal 9rgDescription +ontact)o Mobile)o Active +omment

Blood Bequeath Federal

Blood Bequeath Federal

Blood Bequeath Federal

Blood Bequeath Federal

Data Flow Dia(ra"s .DFD/

Blood Bequeath Federal

(rocess that transforms data flow.

%ource or Destination of data Data flow Data %tore

$*I1%NT F%*TUR%$ OF DFD:$

T9P%$ OF D*T* F1O2 DI*3R*7$

Blood Bequeath Federal

RU1%$ 3O0%RNIN3 T5% DFD:$

Blood Bequeath Federal

Blood Donation Agent

Future -11 Use

Blood Bequeath Federal

Blood Bequeath Federal

1st 1evel DFD:s

1evel 1 DFD+ For *d"i! 7odule

Value Abilities Table

View of value Abilities details

1evel 1 DFD+ For Users 7odule

De art"e!t o# C$% Value Abilities Table

updating and Blood Bequeath Federal editing

Blood Bequeath Federal

DFD For Do!or Creatio!

Insert New Donor

Donor Details De art"e!t o# C$% -16 Blood Bequeath Federal

Blood Bequeath Federal

DFD For O erator Creatio!

$I1%NT F%TUR%$ OF DFD:$

T9P%$ OF DT F1O2 DI3R7$