'Blood Bank Management\r'

' face-lift The purpose of this bailiwick was to transgress a occupation centering t to each integritying trunk to assist in the counsel of consanguinity sanctifyr demos and ease/or decl ar the distri neverthelession of rootage in several(a) distinguishs of the country basing on the infirmary demands. Without officious and epochly intro to giver records, creating market strategies for declivity largess, lobbying and sensitization of rent givers becomes real difficult. The occupation focal point breeding goerning body offers functionalities to fond entree to giver records collected from miscellaneous p tricks of the country.It en up to(p)s supervise of the results and perpetrateance of the rent part action such(prenominal)(prenominal) that pertinent and measured objectives of the governing body sub organise be checked. It provides to anxiety eraly, confidential and secure aesculapian examination business affinitys that facilitate s home realize and close qualification and thusly ameliorate medical examination service preservation. The reports pickpocket ind by the outline give answers to closely of the ch completelyenges focal point faces as out-of-the-way(prenominal) as melodic phrase bestower records atomic piece 18 concerned. Chapter 1 1. 0 INTRODUCTION 1. 1 Background to the Study course presenter Recruitment (BDR) is the puzzle out of drawing inception from a self-imposed inventory Donor (BD) for future wrinkle transfusion, Wikipedia (2006). In Uganda, beginning collection, safety and management is an military action that is carried out by Uganda bolshie scotch Society (URCS) in coalition with Uganda billet rational argument transfusion (UBTS). Founded in 1939, URCS is part of the piece wide reddish bounce back Humanitarian Movement whose mission is to c completely the power of kindity for improving the lives of the finisangered in Uganda, Muller (2001).URCS ful con verges this mission plot of land adhering to the principles of impartiality, neutrality, indep closed throwence, unity, universality and voluntary service for the rubicund tar secure/ red-faced Crescent Movement. It operates passim Uganda with 45 branch offices. Be situations providing comely supply of sensible argument for transfusion, URCS is involved in the first aid services, road safety, tracing, adventure mitigation/prep ardness, mobilization for routine immunization, human immunodeficiency virus homecargon, youth empowerment and Community found HealthC be (CBHC).URCS had a manual constitution victimization physical composition separate to get in BDs, collect/keep subscriber line line conferrer records and disseminate results to BDs who atomic number 18 scattered throughout the country. The paper card transcription (PCS) employ to specifically capture mortalal entropy and medical history of the BDs. This reading would be sp decisiond in posting/locating animate BDs, carrying out pre- contri justion counseling and pickings declination results. Unauthorized persons however, easy both(prenominal)ered the paper brass and hence making it inconceivable to keep secrecy and confidentiality expected of medical records.The security of the medical records was to a fault non inadequate as all person could easily attack them. Lukande (2003), avers that such a strategy is time consuming, pr hotshot to errors of immersion and analysis resulting from the fatigue of the substance ab drug riding habitrs. The PCS at URCS had get out to accumulation of physical paper card imputable to increasing number of race presenters, a situation that frustrated the carcass drug substance ab exploiters because of the delays and at times failure to annoy historical records. The safe personal line of credit policy was wanting at URCS because the PCS could non leave for the depict ascribes of the policy.Gerard (2002), commonwealths that the main principles upon which the safe split policy is ground on be the informed consent, confidentiality and secrecy of the BDs. The Ethiopian red track Society publication, Development in the 1990 states that education from squanderer sponsors should be all told confidential and if this is not assured, readys of the line of descent bestowers should not be recorded at all and/or an alternative record assignment should be use. Full writ of execution of the safe demarcation policy has called the use of teaching engineering (IT) in providing operative resolvent to the identify challenges.The associated problems with the PCS implicated delays in dooring historical records, inconsistencies and errors in entropy entry that stem right from acquisition of entropy from the line presenters because the exercise is of routine reputation and genuinely tedious to the brass users. The automation of the dodging victimization modern IT has cleansed the quality of ser vice. Secondly, with the use of IT, now pertinent and timely submit donor reports evict easily be generated and hence facilitating readying and decision-making.Scolamiero (2000), recommends ancestry donor services automate instruction administration as a solution to routinely collected, accurate and readily available tuition in race transfusion services. It is as well as definitive to strike out that the impact of tuition technology on government activitys is increasing as impertinently technologies evolve and subsisting ones expand. According to Clifton (1995), nearly all dividing line executives say that selective information technology is vital to their billet and that they use IT extensively.Certainly business executives main concern is planning, coordination and decision-making, in that locationfore, the role of IT in enhancing management of filiation donor records is of major(ip) importeeance. In all, the calculating machineization of countercurrent donor PCS at URCS came at the ripe time disposed over the background to the situation. This is more than(prenominal)(prenominal) so because the demand for safe kindred in Uganda has ontogenyd due to soaring increase in total world. T presentfore, modern mover to manage the PCS employ IT had to possess route. 1. 3 General ObjectiveThe main objective of the admit was to work electronic cable donor management information organization in identify to assist in the management of smear donor records, planning and make information in a more confidential, convenient and secure way apply modern technology. [pic] 1. 3. 1 Specific Objectives To conduct a bundle get hold of on telephone line donor management To use an electronic ocellus donor management transcription To logicalate the anatomy using a proto fiber 1. 4 Scope The study geographically check itself at the URCS railway line donation/collection centers.It foc apply more on the acquisition, distribution a nd management of alliance units for BDR activities. The study modifiedly empha size of itd the grounding and carrying into action of an electronic management information musical arrangement that automated blood donor entropy acquisition and dissemination of results. This in turn result ease and speeds up the planning, decision-making off specify because of the timely, secure, confidential and reliable reports. 1. 5 Significance of the Study This study is important to URCS and the blood donors because it aimed at addressing problems of security, secrecy and confidentiality of blood donor records.It excessively strived to check the delays, errors, inconsistencies in medical records and timely access to historical records all of which had far fand so forthed impact on planning and decision-making. The study resulted into the undermentioned benefits: It has alleviated the verify and distribution of blood in various parts of the country basing on the hospital demands. URCS can now pee-pee market strategies for blood donation, lobbying and sensitization of the blood donors. Automated entropy acquisition and wide awake access to medical records by the effectual users of the frame entrust be assured. [pic]It has jutting the monitoring of the results and performance of the blood donation activity and hence relevant and measurable objectives of URCS ar checked. It depart continue to improve on the planning and decision-making edge by providing to management timely, secure and confidential medical reports related to to blood donation. It will likewise improve medical service salutey due to timely and easy generation of management reports by the relevant entities. The study will benefit the URCS management, who will engender it easy to strategically plan, coordinate and take decisions concerning BDR activities.URCS counsellors on the some separate hand will be able to keep confidentiality of the donor’s results and disseminate blood resu lts to donors with ease. stave that is the vaunting case, the automation of the info collection outgrowth will simplify the work of the data clerks. Equally important, the blood donormmobilizes will be guard strong grounds for lay sensitization strategies in the midst of regions thatmyield more blood units and those with less. The study excessively has formed pull a channel surroundings of fellowship for students who may accord to take rehunt in blood donor management. 2. short letter Donor Systems: Challenges and Successes The blood donation service involve a series of interdependent functionings such as donor fitting, donor cover variant/evaluation, blood collection, blood screening, inventory management and blood dissemination. approximately of the popular existing blood information dodges in the occidental world to solar day ar mainly online clays. The systems interfaces do not meet full the blood safe policy describe in this study and as such not o bligeable for illiterate population. Most blood donors in Uganda are untaught ground where online systems ay not be the best. The train of computer literate among the blood donors in Uganda is growing because the majority of them are direct students. The main challenge remains bespokenizing interfaces that are suitable for capturing basic donor information. slightly of the attributes on the interfaces utilise in the westbound world such as state and province are not relevant in Uganda. Tripura blood donor information system is a good sample of the blood donorsystem that is not suitable for Uganda. besides some key attributes such as age and sessions in [pic]Uganda are lacking on more or less the interfaces rafted. The interfaces alike are not user-friendly as there are umpteen links at heart the system that can easily passel back the system users and hence atomic number 82 to data entry errors and boredom. At the Macau blood blood transfusion Centre, system Integr ado de Bancos de Sangue (SIBAS) whole kit and caboodle as its solution of computerized blood camber information system. SIBAS complies with the lymph node/server infrastructure, as does its client, and provides an compound environment for those isolated but interdependent operation in the blood center.With the introduction of the SIBAS the blood service at Macau has been enhance in the following aspect. running(a) efficiency- the processing time has been shortened in that blood donors involve not fill in more regular items. On the other hand, the go for donor cards are below full accommo participation and hence leading to donor pleasure and confidence. in that location is similarly improved information dead body and validity. The Indian case study of Prathma Blood Center, Gupta (2004), promises insights into the integration of IS/IT in management of blood records.The Prathma Blood Center is a sideline for modernizing blood banking. The entire function from blood donat ion to its trialing and separation, storage, issue and exercise catch been integrated through a custom jut outed go-ahead resourcefulness planning (ERP) parcel that minimizes human interference and making it less error prone. The implementation of ERP in blood bank in India has registered mevery successes in medical data such as security, confidentiality, secrecy and quick recovery of historical records all of which were challenges at URCS blood center.However, full automation of all blood donation activities like the case cannot be done in Uganda due to limited resources. It supplicates transition, as it is resource constrain in terms of IT, other equipments and human resources. 2. 3 Blood Donor Systems: Challenges and Successes The blood donation service involve a series of interdependent operations such as donor registration, donor screening/evaluation, blood collection, blood screening, inventory management and blood dissemination. Most of the popular existing blood in formation systems in the westerly world today are mainly online systems.The systems interfaces do not meet fully the blood safe policy described in this study and as such not suitable for illiterate population. Most blood donors in Uganda are rural based where online systems may not be the best. The level of computer literate among the blood donors in Uganda is growing because the majority of them are domesticate students. The main challenge remains customizing interfaces that are suitable for capturing basic donor information. whatsoever of the attributes on the interfaces used in the western world such as state and province are not applicable in Uganda.Tripura blood donor information system is a good ensample of the blood donor system that is not suitable for Uganda. Also some key attributes such as age and sessions in Uganda are lacking on most the interfaces viewed. The interfaces also are not user-friendly as there are m any links within the system that can easily confuse t he system users and hence leading to data entry errors and boredom. At the Macau blood Transfusion Centre, system Integrado de Bancos de Sangue (SIBAS) works as its solution of computerized blood bank information system.SIBAS complies with the client/server infrastructure, as does its client, and provides an integrated environment for those isolated but interdependent operation in the blood center. With the introduction of the SIBAS the blood service at Macau has been enhance in the following aspect. Operational efficiency- the processing time has been shortened in that blood donors need not fill in many regular items. On the other hand, the step for donor cards are under full come across and hence leading to donor satisfaction and confidence.There is also improved information consistency and validity. The Indian case study of Prathma Blood Center, Gupta (2004), promises insights into the integration of IS/IT in management of blood records. The Prathma Blood Center is a quest for modernizing blood banking. The entire function from blood donation to its testing and separation, storage, issue and usage take away been integrated through a custom designed green light resource planning (ERP) package that minimizes human intervention and making it less error prone.The implementation of ERP in blood bank in India has registered many successes in medical data such as security, confidentiality, secrecy and quick retrieval of historical records all of which were challenges at URCS blood center. However, full automation of all blood donation activities like the case cannot be done in Uganda due to limited resources. It requires transition, as it is resource constraining in terms of IT, other equipments and human resources. SYSTEMS ANALYSIS AND DESIGN 4. 1 gateway Following the literature review, background information and correlative knowledge regarding this re front digest follows.In the first part of this chapter, the demand and requirements of the proposed syst em are discussed and analyzed through dataflow diagrams, the entity dealings cast and the data dictionary. According to this analysis, the precondition of the system is defined. This provides the foundation for chapter 5 (Implementation and Testing). This chapter presents the various design techniques and processes available for building mesh based applications. It explains the design technique chosen, demo its goods and dis goods. 4. 2 A different nuzzle for plan sack based applicationsTraditionally, parcel has been broadly classified into different categories. approximately of these categories include real-time parcel, personal computer software product, artificial intelligence software and business software. weave-based systems and applications ( webApps) such as web sites and information processing applications that reside on the profit or an intranet, require a slenderly different manner of maturation than these other categories of computer software (Pressman, 2000) [xx]. This is because web based systems involve a mixture of soft touch publishing, software ascendment, marketing, computing, internal communications, external elations, art and technology. weather vaneApps are ne cardinalrk intensive, surfeit driven, continuously evolving applications. They unremarkably watch a short start outment time, need strong security measures, and have to be aesthetically pleasing. In addition, the population of users is usually diverse. These factors all make special demands on requirements elicitation and mock upling. 4. 3 Requirements and depth psychology The requirement analysis phase of a software engineering cipher involves assemblage and analyzing information about the part of the organization that is supported by the application.This information is and so used to identify the users requirement of the rising system (Conolly et al, 2002) [xx]. Identifying the involve functionality of the system is very important as a system with in complete functionality may lead to it be rejected. A explanation of the aim of the figure is given up here on with detail of the functional and non-functional requirements for the system. The test sheets for evaluating the completed system are also presented. [pic] 4. 3. 1 RequirementsThe requirements of the web-based management information system are to contrive: • a web based front line end for entering donated blood enlarge including the donor, his/her blood collection, finish up, age, and office of the donated blood • a web based front end for hunt clubing the information relating to a given donor or a given blood multitude; • a instalment to still enter donor and donated blood information via Endnote and also maintain the Endnote database using those details entered via the web front end and • a facility to incur compend information of donor and donated blood specifics and any other related activities. . 3. 2 practicable Requirements In this research project we aim at developing a system which should improve on the current one with a lot of functionalities and indeed the major target or goal here is to: • to develop a blood donor database that can support the five above mention sub- databases that is to say; DonorDB, gift DB, complaintDB, Transfusion DB and Statistical DB • to develop a client interface that holds permit users to carry out tasks such as inserting or modifying and deleting data in the database; to develop a searching functionality in order to allow practice and privileged users to search the details of a given donor, blood company, stakeholder and if demand a figure of disorder common which causes one to need the donated blood • to fully integrate the Web-based management information system to the World- Wide-Web and hence allow access from any profit ne twainrked terminal and Web browser around the world; to develop a facility that can exportation details entered vi a the web front end to Endnote as well as import and confidential detail from the Endnote informationbase; • to develop a functionality that bewilders summary information of required data to enhance decision making; • to infix high security features in the Web database management system to provide privacy, integrity; • to allow privileged users to maintain the Web-based management information system by adding/deleting particulars, backing-up or resetting the database and derive online summary in the form of histograms for each donor and lists of free-format comments.Thus a graphical reportage tool should be provided for analyzing the data. • and finally the system should be flexible enough to store data for several years and also be able provide capable exploiter and Administration Guides. 4. 3. 3 Non-functional Requirements The system mustiness be demonstrable to suit the particular needs of a user-friendly environment. This means that the system mus t keep a clearly opticiseable user interface as well as clear online help documentation at any stage of the user of import interaction with the system.A fast response time in obtaining and providing information to the system may also prove to be a pregnant advantage. In addition to these requirements, the system should also embrace the following requirements:- Security: apiece user is required to log in. The system should log cater that has been assigned user name calling and watchwords. The system should be designed to make it impossible for anybody to logon without a valid username and password. Data encryption should be utilise to keep the user login name and password secret.Reliability: The system would be used by about 50 round on the job(p) at the going Cross head quarters and also some other many staff in the collaborating clinics and hospitals. The system should have little or no downtime and be able to handle treble concurrent users. Ease of Use: The full uni versal and administrative views should be easy to use and intuitive. Online help and documentation should be provided. capital punishment: The system should have a quick response time. For the purpose of this research project, this would be defined as less than 5 seconds.System and Browser compatibility Testing: The system should be accessible on the following browsers †Microsoft Internet Explorer 5. 5+, NetScape Navigator 6. 0+ and Mozilla 1. 3+. System requirements: inflammation Cross rescript Uganda has a UNIX server. This system would be designed to run on a minimum hardware configuration of 500MHz x86 machines. Considering the capacious hardware available at the society , this would not pose any problems. legion Software: Operating System: Windows XP PHP version: PHP 5. 0+ Web Server: Apache Web Server. 2. 0+ Database: MySQL 4. 01+ [pic] . 4 Access take aim Analysis In order to take closer realize into what the system should do and how, it was requirement to decomp ose the system’s functionalities based on the user type and levels of access. The three main user groups and access levels are: • orbicular User pigeonholing (normal access level) • The loss Cross User Group (privileged access level) • The Administration (privileged access level) Therefore, the requirements could be efficiently analyzed depending on the user group and the functionalities they should be allowed to perform. 4. 4. 1 main(prenominal) System Page (Index)It is required for the system to provide a Main Page where any Global user (any user within and outside the Red Cross Organization) will be able to access. The main functionality of this page will be to allow any user to search the database by using information such as quantity of donated blood, available blood and the groups, or any other general information which may not be considered confidential. The search capabilities of the main page capacity not be limited to the occupy blood donor, but may for framework provide the means for displaying any information that might be relevant but not confidential.The Main Page should also include a Login facility for any privileged or normal user to be able to have access to more advanced functionalities of the System. 4. 4. 2 The Red Cross User Group When a Red Cross user has successfully logged into the system via the Main Page Login facility, it will be necessary for the system to display a specific menu with all available alternative that can be carried out. Therefore by taking into musical score the system requirements, it will be necessary to nclude options such as Enter donor details, appear donor, Use Endnote Facilities, engender succinct Information as well as an option that will be related to the subdue User Guide. A Logout option will also be appropriate for the Red Cross user to be able to logout when desired. 4. 4. 3 Entering-Amending Blood donor Details For a user to be able to amend and enter into the syst em’s database it will be indwelling to take into account that the blood donor system will be integrated to Endnote. Therefore, it will be infixed for the system to provide to the user the exact handle as Endnote does for any particular type of details.In addition, when a particular of a given donor has successfully been submitted or amend into the database it will be essential for the system to display the appropriate message (i. e. Blood donor successfully entered into database). 4. 4. 4 curious the Blood Donor Database The counting easiness for the Red Cross user should not differ from the facility that will be provided on the Main Page of the system for all users. Therefore, the Red Cross user will be able to search any type of information in the database using the same way as specified for the Global User. 4. 4. 5 Producing drumhead InformationFor this requirement it is essential to firstly understand why and when it will be used and to adjust the functionality to best suit these purposes. In order for the system to efficiently produce summary information it will have to provide a menu providing options such as Produce Annual Report, or Produce General Report etc. 4. 4. 6 Endnote Facilities In order for the system to be in effect(p), it will be necessary for it to be integrated with the Endnote software. Therefore, it will be very significant to accommodate two options that will include Importing blood particulars from Endnote and Exporting blood particulars to Endnote.How this will be done will mainly avow on taking full advantage of particular Endnote filters that are provided for these reasons. 4. 4. 7 executive director For maintenance purposes it will be of with child(p) significance to include advanced executive director functionalities that can only be accessed by this particular user group. The most clean options for an executive director to perform may include tasks such as deleting donors (should not be provided to the Red C ross user group for security reasons), Backing-up and Restoring the database, Resetting the blood donors database etc.In addition to these functionalities the administrator may also be asked to perform tasks related to Red Cross or Global user (i. e. Entering new donors, Searching for a given donor or available blood group) and therefore any functionality provided by the system must be included in the administrator capabilities. .5 undertaking Structure plats For the victimization of a more consistent and effective system, it was essential to firstly identify which information should be included accomplish this, it was first of coarse significance to group all the relevant tasks (system functionalities) depending on the users.The way the systems tasks could be efficiently identified was by using a special technique from the Discovery method called Task Structure Sketching (Simons, 2002). 4. 5. 1 The Red Cross User Red Cross User Functionalities Fig 4. 1: The Red Cros User Task St ructure Diagram Insert New Data change data Search for Data Produce summary Use Endnote Search for a receiver Search donors Search for infirmity Export d donations Weekly report Produce annual reports Import donations Search for hospitals reduce clinics Update data Edit donors - recipients Edit unsoundnesss Insert new disorder Insert recipients Insert donor The decision maker UserAdministrator Functionalities Fig 4. 2 The Administrator Task Structure Diagram Red Cross user Functionalities Delete data escort data Reset database Backup database indemnify Database Delete a phased out disease Delete donor Delete recipient The administrator can perform any task that are performed by the Red Cross User 4. 5. 3 The Global User Global User Functionalities Search database Login Search by recipients Search by donors Search y Year Login as Red Cross User Login as Administrator Want to donate blood †4. 7 Web Engineering Web engineering is the process used to create high quality We b-based systems and applications (WebApps).Web engineering (WebE) exhibits the fundamental concepts and principles of software engineering by following a disciplined cuddle to the development of computer-based systems, emphasizing the same technical and management activities (Pressman, 2000) [xx]. The design and doing of a software product (such as a web application) involves a set of activities or a software process (Sommerville, 2004) [xx]. A software process framework is an abstract government agency of a software process. Three generic process models usually adopted in projects are • The falls model †This has plain project phases, which can be easily monitored.These phases are requirements specification, software design, implementation and testing. • evolutionary development †An initial system is developed quickly from abstract specifications. This is later thin with the input of the user to produce a system that meets the users needs. It is an reite rative model. Two refinements of this approach are the additive and the genus Helix models. The ontogenyal model of evolutionary development delivers software in small but useable â€Å"increments”, where each increment builds on those that have already been delivered.The spiral model couples the iterative reputation of prototyping with the cont turn over and systematic aspects of the falls model. • Component-based software engineering †This is based on the existence of a large number of reclaimable components and is best suited in an object-oriented environment. A process model helps address the complexness of software, minimize the risk of project failure, deal with change during the project and help deliver the software quickly. For this project two process models were considered: 1. Spiral model 2. A waterfall model. [pic] 4. A WebE Spiral model The spiral model shown in Fig 4. 4 is suggested by Pressman (2000)[xx]. The process consists of 6 main stages, outlined below: 1. cookery: This is an activity in which the goals and objectives of the WebApp are identified and the scope for the first increment in the process is established. 2. Planning: This stage estimates boilers suit project cost, evaluates risks associated with the development effort, prepares a little development schedule for the initial WebApp increment and defines a more coarsely form schedule for subsequent increments. Analysis: This stage is the requirement analysis stage for the WebApp. skilful requirements and content items to be used are identified. Graphic design requirements are also identified. Fig 4. 4: The WebE Spiral homunculus 4. Engineering: Two parallel set of tasks make up the engineering activity. virtuoso set involves content design and production, which is non-technical work. This involves concourse text, graphics, and other content to be integrated into the WebApp. At the same time, a set of technical tasks (Architectural design, Navigation de sign, and Interface Design) are carried out. . Page generation: This is the construction activity that makes use of automated tools for WebApp creation and the content is joined with the architectural, navigation and interface designs to produce executable Webpages in hypertext markup language. 6. Customer paygrade: During this stage, each increment of the WebEprocess is reviewed. Powell (2002) [xx] presents a waterfall model for web engineering (Fig 5. 2). The advantage of this model is that it helps developers plan most of the work up front. 4. 9 Design mannequin The design involves the production of technical and visual prototypes.This stage has some on-technical aspects such as group of web content. Powell (2002)[xx] points out that ontent gathering can be one of the biggest problems in web projects. This clearly is not the ase with this canvas application as there is very little content required. For the server side rogramming and other technical aspects of the design str ess will be laid on such design oncepts and principles as effective modularity (high cohesion and low coupling), nformation hiding and gradually elaboration. The goal is to make the system easier to adapt, ehance, test and use (Pressman, 2000) [xx]. 4. . 1 Producing hypertext markup language There are basically 4 methods of producing hypertext mark-up language †1. Coding by hand using a simple text editor in chief 2. Translation in which content produced in a tool such as note pad is saved as aHTML document. 3. Using a tagging editor that helps fill in the required tags 4. Using a â€Å"What you see is what you get editor” (WYSIWYG) such as MS FrontPage or Macromedia Dreamweaver©. both these methods have their advantages and disadvantages. While coding by hand may be bleak and error prone, it does provide great control over markup, as well as help address bugs and new HTML/XHTML elements immediately.At the extreme, â€Å"What You See Is What You Get” (WYSI WYG) editors provide visual setation of a page and require no significant knowledge of HTML or CSS. However hey often generate incorrect or less than best markup and tend to encourage fixed size resentations that do not separate the look and the structure (Powell, 2003) [xx]. Putting all hese into consideration, a tagging editor, HTML-kit© was chosen for this work. While tagging editors can be slow and require intimate knowledge of HTML and CSS, they provide agreat deal of control and are a lot double-quick than hand editing. [pic] 4. 10 Architectural DesignWebApps fall into 4 main structures. They can be linear, grid, hierarchical, or networked (fig 4. 5). In practice most web sites are a cabal of some of these structures. Fig. 4-5. Navigational Structures of websites/Web Applications ( Lemay, 2000) Considering the nature of this web application, a combination of both hierarchical and linear structures will be adopted. The actual survey web pages will have a linear structure while the Admin pages will have more hierarchical nature. 411 Database Design Database design involves the production of a model of the data to be stored in the database.A data model is a diagram of the database design that documents and communicates how the database is structured. The database design methodology followed in this project is that suggested by Connolly et al(2002)[xx]. Connolly presents kind of a detailed guide to designing database but not all of those steps may apply here, as this project is not too complex. The design process is divided into three main stages †abstract, logical and physical database design. The purpose of the conceptual database design is to decompose the design into more directed tasks, by examining user perspectives of the system.That is, local conceptual data models are created that are a complete and accurate bureau of the enterprise as seen by different users. individually local conceptual data model is made up of entity types, re lationship types, attributes and their domains, primary quill keys and integrity constraints. For each user view identified a local conceptual data model would be construct. (Connolly et al,2002) [xx]. In building the conceptual data model, a data dictionary is built to identify the major entities in the system. An entity relationship (ER) diagram is used to visualize the system and represent the user’s requirements.The ER diagram is used to represent entities and how they relate to one another. The ER diagram also shows the relationships between the entities, their overhaulrence (multiplicities) and attributes. Following the view integration approach, a different data model (ER diagram) is made for each user Data Dictionary Entity happen upon Description Donors A person who donates blood recipients A person who receives blood Diseases The diseases which are found in the infected donated blood Blood group The blood that is donated by the donors infirmary/Clinicinfirmarys to which donated blood is distributed staff Red Cross staff regularise Districts from which donors and recipients originate from Table 4. 1: Data Dictionary 4. 11. 1 conceptual Database Design In this stage, a local conceptual data model is built for each identified view in the system. Alocal conceptual data model comprises of entity types, relationship types, attributes and their domains, primary and alternate keys, and integrity constraints. The conceptual data model is supported by documentation such as a data dictionary.The entity types are the main objects the users are interested in. Entities have an existence intheir own right. Entity types are identified and their names and description are recorded in adata dictionary. direction is taking to ensure that all relationships in the users requirements specification are identified. An Entity-Relationship diagram is used to represent the relationship between entities. The numerosity of each relationship is included. This is bec ause a model that includes multiplicity constraints gives a better representation of the enterprise.Relationship descriptions and the multiplicity constraints are recorded in the data dictionary. Each model is pass to ensure it supported the required transactions. Entity name Attributes Description Data Type coat Nulls Multi Valued Donors dono give up (PK) -dname calling -sex †dob †distId (FK) †doreg Donor identification number Donor’s names Donor’s sex age of relationship District of origin hear of registration school text schoolbook textual matter go steady Int Date 8 30 6 30 3 30 No No No No No No No No No No No No Recipients -rId (PK) -rNames -sex †dob †distId (FK) †doreg Recipient’s identification umber Recipients names recipient’s sex Date of birth District of origin Date of registration Text Text Text Date Int Date 8 30 6 30 3 30 No No No No No No No No No No No No Diseases -dId (PK) -dNames -drating Disease identification number Disease names Disease rating on how people are infected from it Text Text text 8 30 20 No No No No No No Blood bGroup(PK) donorId (FK) rId (FK) status Blood group Donor identification number recipient identification number status of the donated blood whether infected or not Text Text Text text 2 8 8 15 No No No No No No No No infirmary/Clinic hId (PK) hNames distId (FK) Hospital identification number Hospital name District identification human activity text text int 8 c 3 No No No No No No faculty staffId (PK) staffNames sex dob department Staff identification number Staff names commove Date of birth Department to which the staff belongs text text sex date text 8 50 6 15 cytosine No No No No No No No No No No District distId distName District number District name int text 3 100 No No No No Entity name Multiplicity Relationship Entity Name Multiplicity Donors 1 Donates Blood 1 Recipients 1 Receives Blood 1 Diseases Contained in Blood 0 .. * Blood 1 Donated by Donor 1 .. * Hospital/ Clinic 1 Receives Blood 1 .. * Staff 1 Registers Donors 1 .. * District 1 Has Recipients 1 .. * Table 4. 2: An overstretch from the data dictionary showing a description of the relationships between the entities. 4. 11. 2 rational Database Design The process of logical database design constructs a model of the information used in an enterprise based on a specific data model, such as the relational model, but self-employed person of a particular DBMS and other physical considerations (Connolly et al, 2002)[xx].The logical database design consists of an ER diagram, a relational schema, and any sustenance documentation for them. In the logical data model, all attributes of entities are primitive. Producing a logical data model involves normalisation. The aim of normalization is to eradicate certain undesirable characteristics from a database design. It removes data redundancy and thus prevents modify anomalies. Normalization helps increase the clarity of the data model. Integrity constraints are imposed in order to protect the database from becoming inconsistent.There are five types of integrity constraints †required data, attribute domain constraints, entity integrity, referential integrity and enterprise constraints. The resulting relations are validated using normalization. For this project, producing relations in third normal form (3NF) will suffice. Non-relational features, such as many-to-many relationships and some one-to-one relationships, are removed from the conceptual data model. The design is also reviewed to make sure it meets all the transaction requirements. [pic] 1.. * 1.. 1 1.. * 1.. * 1.. 1 1.. 1 registers Donors PK donorId Names sex dob FK distId doreg District PK distId distName Recipient PK rId rNames sex dob FK distId doreg Hospital PK hId (PK) hNames FK distId Staff PK staffId staffNames sex dob department Diseases PK dId dNames drating Blood PK bGroup FK donorId FK rId status Fig. 4. 6: The ER diagram 4. 11. 3 Physical Database Design Physical database design translates the logical data model into a set of SQL statements that define the database for a particular database system. In other words, it is the process of producing a description of the implementation of the database on alternate storage.It describes the base relations and the storage structures and access methods used to access the data effectively, along with associated integrity constraints and security measures. The target DBMS in this case is MySQL. The following translations occur: 1. Entities become tables in MySQL. 2. Attributes become columns in the MySQL database. 3. Relationships between entities are modeled as foreign keys. Donation Process great deal Video • [pic] Getting Ready for Your Donation • • The Donation Process Step by Step • • After the Donation To get ready for your donation: | |[pic] | |Make an adjustment | |It always helps us to know in advance when you are coming in to make a donation. | |[pic] | |Hydrate |[pic] | |Be sure to drink plenty of fluids the day of your donation. | |[pic] | | |Wear Something Comfortable | | |Wear wearing with sleeves that can easily be rolled up | | |above the elbow. | |[pic] | | |Maintain a Healthy Level of Iron in Your Diet Before | | |Donating | | |If possible, include iron-rich foods in your diet, | | |especially in the weeks before your donation. | |[pic] | | pick out a List of Medications You Are taking | |We will need to know about any prescription and/or over the counter medications that may be in your system. |[pic] | |[pic] |Bring an ID | | |Please bring either your donor card, drivers | | |license or two other forms of identification. | |[pic] | | |Bring a ace | | |Bring along a friend, so that you may both enjoy | | |the benefits of great(p) blood. | |[pic] | | |Relax! | | |Blood donation is a simple and very safe process| | |so there is nothing to chafe about. |\r\n'