Swamy Final Doc Modified 23rd June

MOTHER TERESA BLOOD BANK A project report submitted in partial fulfillment Of the requirements for the award of the Degree

Master of Computer Applications By ADDANKI.THIRUPATHI SWAMY (Regd. No. 06L31F0002)

Under the Esteemed Guidance of Mr.P.PRAVEEN KUMAR Associate Professor, Vignans Institute of Information Technology, Duvvada,Visakhapatnam.

Department of Master of Computer Applications

Vignan’s Institute of Information Technology (Affiliated to J.N.T.U University, Kakinada)

Besides VSEZ, Duvvada, Vadlapudi Post, Gajuwaka Visakhapatnam -530046, A.P., India. 2006-2009

Certificate

DEPARTMENT OF COMPUTER APPLICATIONS VIGNAN’S INSTITUTE OF INFORMATION TECHNOLOGY Besides VSEZ, Duvvada, Vadlapudi Post, Gajuwaka Visakhapatnam -530046, A.P., India. May – 2009.

Certificate This is to certify that the project report entitled “Mother Teresa Blood Bank” is a bonafide record of project work carried out by Mr.Addanki Thirupathi Swamy (Regd. No. 06L31F0002), a student of this college, during the academic year 20062009, in partial fulfillment of the requirements for the award of the degree of Master of Computer Applications.

Project Guide

Head of the

Department Mr.P.PRAVEEN KUMAR Associate Professor,VIIT

Mr. M. RAJESH Asst.prof,VIIT

External Examiner

DECLARATION

I, Addanki.Thirupathi Swamy hereby declare that the project report entitled “Mother Teresa Blood Bank” is an original work done at Vignan’s Institute of Information Technology Visakhapatnam, submitted in partial fulfillment of the requirements for the award of Master of Computer Applications, to Vignan’s Institute of Information Technology, affiliated to J.N.T.U University. I assure that this project is not submitted in any other University or college.

(Addanki.Thirupathi Swamy)

Acknowledgment

ACKNOWLEDGEMENT I consider it as a privilege to thank all those people who helped me a lot for successful completion of the project “Mother Teresa Blood Bank”. First of all I express my sincere thanks to my guide Mr.P.Praveen Kumar, Assoc. Prof., Department of Master of Computer Applications, Vignan’s Institute of Information Technology, for the valuable support and keen interest with appropriate Suggestions, which enable me to purse my project with great interest. I would like to express our sincere thanks and deep sense of gratitude towards Vignan’s Institute of Information Technology for giving me this opportunity to work within their environment. I express my performed gratitude to my project client, Mr. B.Prasad, Assoc., Professor, and VIIT who has given me a chance and freedom during my project work. I would like to thank our ever-accommodating Head of the Department of Master of Computer Applications Mr. M. Rajesh, Asst.,Professor who has very obliges in responding to every request though he is busy with him hectic schedule of administration and teaching. I would like to thank our Principal, Prof.A.SheshaRao, who has given me a lot of support and freedom during my project work. I thank all the teaching & non-teaching staff who has been a constant source of support and encouragement during the study tenure. Last but not least, I will be indebted to my family members, all my friends (Especially Mr.M.Mahesh and Mr.P.Narendra) and other members of the department for being so supportive and helpful in every possible way.

ABSTRACT The need of blood is great. On any given day, an average of 34,000 units of blood is needed to save precious human lives from accidents and burns, heart surgery, organ transplants; patients receiving treatment for leukemia, cancer and other diseases. So far so many blood banks and welfare societies have come forward to serve the people but the gap is constant.”Mother Teresa Blood Bank” project is mainly to fill that gap as best as possible by providing very sophisticated web application with accurate and timely information of Donors available to the needy. This is a very powerful online blood donors/blood banks management system that we’ve developed exclusively and user friendly. The whole the objective of the project is an online edge for bringing mutually giving blood donors and patients (blood requesters) that needs blood. The primary objective of the project is to create an interactive Blood donors, Blood requesters and Blood bank clinics. This web application is to be conceived in its current form as a dynamic site-requiring constant updates both from the blood donors as well as the blood requesters and is to enable blood donors (Volunteer) to place their profile and blood requesters (patients) to publish their requests. The web application to be developed is to have functionalities enabling patients to post their requests, search for donors contact numbers and view personal profiles and also have an option to search blood bank addresses. Thus the administrator can only change the general look and feel of the application/site, once blood donors and blood banks becomes a registered user of the site the donors have to just view their profile and update contact numbers and addresses.

Contents

CONTENTS S. No

Topic

Page No.

1. Introduction 01 1.1 Scope of the Project

02

1.2 Problem Statement

03

1.3 Introduction to Modules

04

2. Requirement Elicitation

05

2.1 Introduction

06

2.2 Proposed System

07

2.3 Requirement Specification

08

2.3.1

Introduction

08

2.3.2

Functional requirements

08

2.3.3

Non-Functional requirements

09

2.3.4

Software and Hardware Specifications

10

2.4 Use Cases and Scenarios

11

2.5 Feasibility Study

15

3. Object Oriented Analysis and Design

17

3.1 Introduction

18

3.2 Object Model

19

3.2.1

Class Diagram

19

3.2.2

Object Diagram

20

3.3 Dynamic Model

21

3.3.1

Sequence Diagram

21

3.3.2

Collaboration Diagram

23

3.3.3

State-Chart Diagram

25

3.3.4

Activity Diagram

26

3.3.5

Component Diagram

27

3.3.6

Deployment Diagram

27

4. System Implementation 4.1 Introduction 5. Testing

28 29 31

5.1 Introduction

32

5.2 Software testing techniques

33

6. Scope for Expansion 37 7. Conclusion 38 8. References 39 9. Appendix

40

Appendix I: PHP

41

Appendix II: Web Application Architecture

47

Appendix III: JSP

52

Appendix IV: Java Mail-API

56

Appendix V: Sample Code

68

Appendix VI: Screen shots

79

Introduction

INTRODUCTION Blood donation gives a proud feeling of touching someone’s life in a beautiful way. It’s an experience that no words can define. You have to donate blood yourself to find out. By keeping the blood line flowing, you will greatly contribute towards a healthier, happier society. Do remember, any one may require blood any time including ourselves and our dear ones. You also benefit in other ways by donating blood. It reduces the chances of ischemic heart diseases (beginning of heart problems) as frequent donations reduce the accumulated and unwanted iron load from the body. Your blood donation will also get you your blood insurance from us. Every year India requires 40 million units of 250cc blood out of which only a meager 500,000 of blood units are available. Blood is the part of life that is given to those who need it by those who have the resource to satisfy the need. The love of fellow human and a desire to share something of oneself is what singles out a blood donor from the others. Emergencies occur every minute. For each patient requiring blood, it is an emergency and the patients could have set back if blood is not available.

A single donation from you can help one or more patients. This is possible because whole blood is made up of several useful components. These components perform special functions in your body and in the body of patients who receive your blood. The various blood components are Red Blood Cells, White Blood Cells, Platelets, Plasma and selected Plasma Proteins. Each of these components can be separated

from your donated volume of blood and transfused into a specific patient requiring that particular component. Thus, many can benefit from one unit of blood. Blood is the life line of human body, supplying oxygen & other nutritions. An adult human body has approximately 5 litres of blood. The blood content is reduced in a disease process, accident and surgery. Blood transfusion plays a vital role in providing support to the treatment procedure In recent years blood transfusion services have become an integral part of the health care system. The primary objective planning for a blood bank is to ensure adequacy, accessibility and efficient supply of blood & its products in a safe, cost effective and coordinated manner. However before planning for a blood bank we should know, what is the meaning of a blood bank today? What functions it is supposed to serve? And what is the work load?

A Blood Bank today is a place or organization or unit or institution or other arrangements made by such organization, unit or institution for carrying out all, or any of the operations for collection, apheresis, storage, processing & distribution of blood components. .”Mother Teresa Blood Bank” project is mainly to provide very sophisticated web application with accurate and timely information of Donors available to the needy.

This is a very powerful online blood donors/blood banks management system that We've developed exclusively and user friendly. The whole the objective of the project is an online edge for bringing mutually giving blood donors and patients (blood requesters) that needs blood. The primary objective of the project is to create an interactive Blood donors, Blood requesters and Blood bank clinics. This web application is to be conceived in its current form as a dynamic site-requiring constant updates both from the blood donors as well as the blood requesters and is to enable blood donors (Volunteer) to place their profile and blood requesters (patients) to publish their requests. The web application to be developed is to have functionalities enabling patients to post their requests, search for donors contact numbers and view personal profiles and also have an option to search blood bank addresses. Thus the administrator can only change the general look and feel of the application/site, once blood donors and blood banks becomes a registered user of the site the donors have to just view their profile and update contact numbers and addresses. This will not only help save time for the needy but also make information available at your fingertips thereby making it that much easier to find out the availability of blood at the nearest blood bank instead of running from pillar to post. .

With the emergence of Transfusion Medicine Department the definition of Blood Bank has changed. Today, it is not just a bank to collect & issue blood, it prepares and supplies individual blood component, to the patients as and when the need arises during the course of treatment. The planning & management of any blood bank depends on number of functions it is required to serve and the number of units of demand of blood & blood products. This has also changed the role of nursing from skilled nursing care to managing the blood bank services.

Scope of the Project The scope of the project is not bounded to only one state in our country; people at different states can find registered donors in their region and also can register and donate. Presently serving whole of Visakhapatnam city and its suburbs. Plan to extend to other neighboring districts of A.P, India. •

To ensure sufficient supply of the Blood and its components.

•

To ensure consistency of high quality with no risk.

•

To ensure Donors screening.

This can be achieved by implementing effective system of Quality Assurance. Important areas of the Blood Bank are: •

Donor’s selection.

•

Method and procedure of Blood collection

•

Transportation.

•

Storage during transit period

•

Testing

•

Labeling

•

Dispatch under ideal temperature conditions

Specific objective •

To provide basic information of the types of donors.

•

To teach the staff the method of labeling and record keeping

•

Criteria for donor selection

•

To provide basic information for donor deferral

Problem Statement There are so many websites that promote sevices through their blood banks. Most of the websites not providing reliable and timely information for the people in need. This Project is mainly to fill that gap as best as possible by providing very sophisticated web application with accurate and timely information of Donors available to the needy. Every year our nation requires about 4 Crore units of blood, out of which only a meagre 5 Lakh units of blood are available. It is not that, people do not want to donate blood. Often they are unaware of the need and also they do not have a proper facility to enquire about it. As a result, needy people end up going through a lot of pain. India has many blood banks, all-functioning in a decentralised fashion. In the current system, individual hospitals have their own blood banks and there is no interaction between blood banks. The management is ad-hoc with no semblance of organisation or standard operating procedures. Donors cannot access blood from blood banks other than the bank where they have donated blood.

Proposed System:

Goals of proposed system 1. Planned approach towards working: - The working in the organization will be well planned and organized. The data will be stored properly in data stores, which will help in retrieval of information as well as its storage. 2. Accuracy: - The level of accuracy in the proposed system will be higher. All operation would be done correctly and it ensures that whatever information is coming from the center is accurate. 3. Reliability: - The reliability of the proposed system will be high due to the

above stated reasons. The reason for the increased reliability of the system is that now there would be proper storage of information. 4. No Redundancy: - In the proposed system utmost care would be that no Information is repeated anywhere, in storage or otherwise. This would assure economic use of storage space and consistency in the data stored. 5. Immediate retrieval of information: - The main objective of proposed system is to provide for a quick and efficient retrieval of information. Any type of information would be available whenever the user requires. 6. Immediate storage of information: - In manual system there are many problems to store the largest amount of information. 7. Easy to Operate: - The system should be easy to operate and should be such that it can be developed within a short period of time and fit in the limited budget of the user.

The proposed system contains a. Donor Registration with full fledged information b. Through feedback the users can interact with admin through online with their queries. c. Through Web mail support admin can send mails to donors as well as to his referred pages. d. Using “Find a Donor” List, users can easily find the information of a particular donor in a particular region/state.

Introduction to Modules This project having three modules.

They are 1. Admin module 2. Donor module 3. End-user Module

1. Admin Module Through admin module, Administrator can add, edit the donors list, sending mails to registered donors and referred friends, we can control the whole website through admin module.

Admin Panel Feature • • • • • • •

Admin login Website Database Settings Add Blood Banks Address Blood Donors Reports Blood Banks Reports Blood Requesters list Change Admin Password

•

Logout

2. Donor Module

In the Donor module, Donors can view and edit their account details; modified data will be stored in the database. Donors can share their experience with users and admin by providing feedback to the system.

Donor Module Features

• • •

Donors registration Donors login Update donors profile

3. End-user Module In the user module, we are providing the related information of the website, registration, he can view the donor’s feedback and also able to provide feedback. User can view all the static pages of this module without any restrictions. End-user Module Features

• • • • • •

Home Blood Request Search donors Search Blood Banks Request Blood List Blood Banks

Requirements Analysis

Introduction: Requirements are a description of how a system should behave or a description of system properties or attributes. It can alternatively be a statement of ‘what’ an application is expected to do. This is the most important task of a project, before going to initiate the project we have to analyze the project to know the requirements of a project. If the requirements are not elicited and produced properly in the beginning, the cost of fixing those mistakes later in the project will skyrocket.

Requirement Specification Introduction Requirements, once elicited, modeled and analyzed should be documented in clear, unambiguous terms. A written requirements document is critical so that its circulation is possible among all stakeholders including the client, user-groups, the development and testing teams. Current requirements engineering practices reveal that a well-designed, clearly documented Requirements Specification is vital and serves as a: •

Base for validating the stated requirements and resolving stakeholder conflicts, if any

•

Contract between the client and development team

•

Basis for systems design for the development team

•

Bench-mark for project managers for planning project development lifecycle and goals

•

Source for formulating test plans for QA and testing teams

•

Resource for requirements management and requirements tracing

•

Basis for evolving requirements over the project life span

Functional requirements FUNCTIONS OF BLOOD BANK TODAY: The following are the functions of blood bank in modern medicine: I. II. III. IV. V. VI. VII.

Selection of donors (i.e.) to determine the suitability. Blood collection. Screening of blood for various blood borne diseases. Component preparation. Storage of blood & blood products. Record keeping of the above. Training of medical & paramedical staff.

Functional requirements • Getting donors list throughout country/state wide • Sending mails to newly registered donors • Feed Back form • • • •

Search donors Search Blood Banks Request Blood List Blood Banks

Non-functional Requirements: In systems engineering and requirements engineering, a non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that define specific behavior or functions. In general, functional requirements define what a system is supposed to do whereas non-functional requirements define how a system is supposed to be. Non-functional requirements are often called qualities of a system.

Non-functional requirement of this system.



Accessibility



Dependency on other parties



Documentation



Efficiency (resource consumption for given load)



Effectiveness (resulting performance in relation to effort)



Legal and licensing issues



Interoperability



Maintainability



Modifiability



Open Source



Performance / Response time (see Performance Engineering)



Reliability (e.g. Mean Time Between Failures - MTBF)



Response time



Security

SOFTWARE AND HARDWARE SPECIFICATIONS

Software Requirements Language Specification

: PHP (Hypertext Preprocessor)

Databases

:

MYSQL

Operating System

:

Windows XP

Web Server

:

Apache

Hardware Requirements Processor Name

:

Pentium IV

RAM

:

128 MB

Hard Disk Drive

:

40 GB

Use cases and scenarios A use case is a description of a system’s behavior as it responds to a request that originates from outside of that system. Use cases describe the system from the users point of view. A use case defines the interactions between external actors and the system under consideration to accomplish a goal. Use cases describe the interaction between a primary actor (the initiator of the interaction) and the system itself, represented as a sequence of simple steps. Actors are something or someone which exists outside the system under study, and that take part in a sequence of activities in a dialogue with the system to achieve some goal. Actors may be end users, other systems, or hardware devices. Each use case is a complete series of events, described from the point of view of the actor.

What is a Use Case? A use case is a description of how a user might use an application to complete a specific task. Use cases are commonly used in software engineering to help document functionality and how it is used. They can range in the amount of system-specific information from only describing the task to detailed implementation and avenues for completion. This examples describe similar use cases for the print function in Okular, including implementation details and two avenues for completion. Okular example: Print a PDF document • •

John prints a PDF document from the hard drive by opening the file in Okular, and then selecting File -> Print. Sara prints a PDF document from the web by opening the file in Okular, and presses Ctrl+P.

What is a Use Scenario? A use scenario describes the context of a use case — the conditions, motivation, and environment of the task for a particular user. It is important to understand why a user might complete a specific task and how they will complete it in order to create an interface design. Use scenarios are commonly used by designers as a way to understand users’ motivation and tasks in an interface, but good engineering use cases include these extra elements of use scenarios. This example describes different use scenarios for a similar use case (printing) in Okular. Okular example: Print a PDF document •

•

John is using a friend’s computer to print a paper he needs for class. He finds the paper on the hard drive and clicks on the icon to open it in Okular, the default PDF document viewer. He has never used Okular before and doesn’t find the Print button on the toolbar. John is not sure if Okular shares the same keyboard shortcuts as other applications, so to be safe, he goes to the File menu and finds the Print option and clicks it to print the document. Sara wants a PDF document which is stored on the web. When she clicks on the link, instead of opening in her browser, she is prompted with a dialog to save or open the document. She selects the open document option and specifies Okular as the application to open the PDF document. Sara usually only reads PDF files on the web, and this is the first time a PDF did not open in her web browser, and this is the first time she has ever used Okular. She does not see a Print button on the Okular toolbar and so decides to try Ctrl+P, which is a shortcut she is familiar with using in her web browser’s PDF plugin.

Why do we need both Use Cases and Use Scenarios? Use cases and scenarios complement each other. They get interesting when you have similar use cases driven from different use scenarios or different use scenarios leading to similar use cases. You want to try and develop use cases and scenarios for as many functions or features and user types as possible. The goal is to make sure the different ways different users try to complete the same tasks do not conflict with each other. These example use cases and scenarios describe how different users under different conditions might try to print a document in Okular. In particular, notice how the decision to remove the Print button from the toolbar to make the interface more simple and pleasing effects how these sample users might complete their tasks. What might happened if Okular has a number of users who rely on toolbar buttons to assist in completing tasks? Are these types of users familiar with looking through menu items or keyboard shortcuts? At the same time, consider how inexperienced a user must be to not consider looking through an application menu when all else fails. These users are not really a target user type for KDE or Okular, and so changing the design to accommodate them might not be reasonable.

Use cases and scenarios help provide developers with information to make these types of informed decisions. The next time Okular gets a bug report complaining about the Print button not available on the toolbar by default, the project has a reasoning they can cite. (BTW, users who are knowledgeable enough about using bugtracker can probably also figure out how to add the print button to their toolbar.) Also, I am in no way agreeing or disagreeing with Okular’s decision to remove the Print button from the toolbar by default. It was just a really good example.

Feasibility Study Depending on the results of the initial investigation the survey is now expanded to a more detailed feasibility study. “FEASIBILITY STUDY” is a test of system proposal according to its workability, impact of the organization, ability to meet needs and effective use of the resources. It focuses on these major questions: 1. What are the user’s demonstrable needs and how does a candidate system meet them? 2. What resources are available for given candidate system? 3. What are the likely impacts of the candidate system on the organization? 4. Whether it is worth to solve the problem? During feasibility analysis for this project, following primary areas of interest are to be considered. Investigation and generating ideas about a new system does this. Steps in feasibility analysis Eight steps involved in the feasibility analysis are: • • • • • • • •

Form a project team and appoint a project leader. Prepare system flowcharts. Enumerate potential proposed system. Define and identify characteristics of proposed system. Determine and evaluate performance and cost effective of each proposed system. Weight system performance and cost data. Select the best-proposed system. Prepare and report final project directive to management.

Technical feasibility A study of resource availability that may affect the ability to achieve an acceptable system. This evaluation determines whether the technology needed for the proposed system is available or not. • Can the work for the project be done with current equipment existing software technology & available personal? • Can the system be upgraded if developed? • If new technology is needed then what can be developed? This is concerned with specifying equipment and software that will successfully satisfy the user requirement. The technical needs of the system may include:

Front-end and back-end selection An important issue for the development of a project is the selection of suitable frontend and back-end. When we decided to develop the project we went through an extensive study to determine the most suitable platform that suits the needs of the organization as well as helps in development of the project. The aspects of our study included the following factors. Front-end selection: 1. It must have a graphical user interface that assists employees that are not from IT background. 2. Scalability and extensibility. 3. Flexibility. 4. Robustness. 5. According to the organization requirement and the culture. 6. Must provide excellent reporting features with good printing support. 7. Platform independent. 8. Easy to debug and maintain. 9. Event driven programming facility. 10. Front end must support some popular back end like Ms Access. According to the above stated features we selected VB6.0 as the front-end for developing our project. Back-end Selection: 1. Multiple user support. 2. Efficient data handling. 3. Provide inherent features for security. 4. Efficient data retrieval and maintenance. 5. Stored procedures. 6. Popularity. 7. Operating System compatible. 8. Easy to install. 9. Various drivers must be available. 10. Easy to implant with the Front-end. According to above stated features we selected Mysql as the backend. The technical feasibility is frequently the most difficult area encountered at this stage. It is essential that the process of analysis and definition be conducted in parallel with an assessment to technical feasibility. It centers on the existing computer system (Hardware, software etc.) And to what extent it can support the proposed system. Economical feasibility Economic justification is generally the “Bottom Line” consideration for most systems. Economic justification includes a broad range of concerns that includes cost benefit analysis. In this we weight the cost and the benefits associated with the

candidate system and if it suits the basic purpose of the organization i.e. profit making, the project is making to the analysis and design phase. The financial and the economic questions during the preliminary investigation are verified to estimate the following: • • • • •

The cost to conduct a full system investigation. The cost of hardware and software for the class of application being considered. The benefits in the form of reduced cost. The proposed system will give the minute information, as a result the performance is improved which in turn may be expected to provide increased profits. This feasibility checks whether the system can be developed with the available funds.

The Blood bank system does not require enormous amount of money to be developed. This can be done economically if planned judicially, so it is economically feasible. The cost of project depends upon the number of man hours required. 3.3) Operational Feasibility It is mainly related to human organizations and political aspects. The points to be considered are: • • • •

What changes will be brought with the system? What organization structures are disturbed? What new skills will be required? Do the existing staff members have these skills? If not, can they be trained in due course of time?

The system is operationally feasible as it very easy for the End users to operate it. It only needs basic information about Windows platform. Schedule feasibility Time evaluation is the most important consideration in the development of project. The time schedule required for the developed of this project is very important since more development time effect machine time, cost and cause delay in the development of other systems. A reliable “Mother Teresa Blood Bank “system can be developed in the considerable amount of time.

Object Oriented Analysis and Design Introduction Object-oriented analysis and design (OOAD) is a software engineering approach that models a system as a group of interacting objects. Each object represents some entity of interest in the system being modeled, and is characterised by its class, its state (data elements), and its behavior. Various models can be created to show the static structure, dynamic behavior, and run-time deployment of these collaborating objects. There are a number of different notations for representing these models, such as the Unified Modeling Language (UML). Object-oriented analysis (OOA) applies object-modeling techniques to analyze the functional requirements for a system. Object-oriented design (OOD) elaborates the analysis models to produce implementation specifications. OOA focuses on what the system does, OOD on how the system does it.

Object-oriented systems An object-oriented system is composed of objects. The behavior of the system results from the collaboration of those objects. Collaboration between objects involves them sending messages to each other. Sending a message differs from calling a function in that when a target object receives a message, it itself decides what function to carry out to service that message. The same message may be implemented by many different functions, the one selected depending on the state of the target object. The implementation of "message sending" varies depending on the architecture of the system being modeled, and the location of the objects being communicated with.

Object-oriented analysis Object-oriented analysis (OOA) looks at the problem domain, with the aim of producing a conceptual model of the information that exists in the area being analyzed. Analysis models do not consider any implementation constraints that might exist, such as concurrency, distribution, persistence, or how the system is to be built. Implementation constraints are dealt with during object-oriented design (OOD). Analysis is done before the DesignThe sources for the analysis can be a written

requirements statement, a formal vision document, interviews with stakeholders or other interested parties. A system may be divided into multiple domains, representing different business, technological, or other areas of interest, each of which are analyzed separately. The result of object-oriented analysis is a description of what the system is functionally required to do, in the form of a conceptual model. That will typically be presented as a set of use cases, one or more UML class diagrams, and a number of interaction diagrams. It may also include some kind of user interface mock-up.

Object-oriented design Object-oriented design (OOD) transforms the conceptual model produced in objectoriented analysis to take account of the constraints imposed by the chosen architecture and any non-functional – technological or environmental – constraints, such as transaction throughput, response time, run-time platform, development environment, or programming language. The concepts in the analysis model are mapped onto implementation classes and interfaces. The result is a model of the solution domain, a detailed description of how the system is to be built.

The Document Object Model is a platform- and language-neutral interface that will allow programs and scripts to dynamically access and update the content, structure and style of documents. The document can be further processed and the results of that processing can be incorporated back into the presented page. This is an overview of DOM-related materials here at W3C and around the web.

System Implementation Purpose The purpose of System Implementation can be summarized as follows: making the new system available to a prepared set of users (the deployment), and positioning on-going support and maintenance of the system within the Performing Organization(the transition). At a finer level of detail, deploying the system consists of executing all steps necessary to educate the Consumers on the use of the new system, placing the newly developed system into production, confirming that all data required at the start of operations is available and accurate, and validating that business functions that interact with the system are functioning properly. Transitioning the system support responsibilities involves changing from a system development to a system support and maintenance mode of operation, with ownership of the new system moving from the Project Team to the Performing Organization. A key difference between System Implementation and all other phases of the lifecycle is that all project activities up to this point have been performed in safe, protected, and secure environments, where project issues that arise have little or no impact on day-to-day business operations. Once the system goes live, however, this is no longer the case. Any miscues at this point will almost certainly translate into direct operational and/or financial impacts on the Performing Organization. It is through the careful planning, execution, and management of System Implementation activities that the Project Team can minimize the likelihood of these occurrences, and determine appropriate contingency plans in the event of a problem.

List of Processes This phase consists of the following processes:

Prepare for System Implementation, where all steps needed in advance of actually deploying the application are performed, including preparation of both the production environment and the Consumer communities. Deploy System, where the full deployment plan, initially developed during System Design and evolved throughout subsequent lifecycle phases, is executed and validated. Transition to Performing Organization, where responsibility for and ownership of the application are transitioned from the Project Team to the unit in the Performing Organization that will provide system support and maintenance.

The term implementation has different meanings, ranging from the conversion of a basic application to a compatible replacement of a computer system. Implementation is use here to mean the process converting a new or a revised system design in to an operation one. During the implementation stage we convert the detailed code in a programming language. Goals for Implementation Stage The first goal of implementation is to provide a faithful translation of design. The choice of a language should be pragmatic, governed by mixture theoretical needs and practical constraints. Good software should avoid any gap between design codes. This is particularly important for reuse of component or for maintenance work that will require tracing the connection of design to code. CHARACTERISTICS OF IMPLEMENTATION Abstraction Abstraction deals with the ability of an implementation to allow the programmer to ignore the portion of details that is important at the current level of consideration. Each of the three kinds of abstraction control, data and process should present in the code. Modularization Modularization requires as partitioning the implementation, with each abstraction occupying its own separate and identifiable units. Encapsulation

While implementing a design, care should be taken to truly hide within a module. Verification Assertions use during format verifications of the detailed design should be included as comments in the source code. Implementation is the stage of the project when theoretical design is turned in to a working system.

Testing INRODUCTION The Software Testing process commences once the program is created and documentation and related data structures and designed. Software Testing is essential for correcting errors. Otherwise the program or the Project is not said to be completed. TESTING TYPES 1. 2. 3. 4.

Unit Testing Integration Testing Validation Testing System Testing

UNIT TESTING Unit testing focuses verification effort on the smallest unit of software design (i.e.), the module. Unit testing exercises specific paths in a module’s control structure to ensure complete coverage and maximum error detection. This test focuses on each individually, enduring that it functioned properly as a unit. Hence, the name is Unit Testing.

In this project, after completion of each module the validity and performance of the module tested. INTEGRATION TESTING Integration Testing addresses the issued associated with the dual problems of verification and program construction. After the Software has been integrated a set of high-order tests are conducted. The main objective in this testing process is to take unit-tested modules and build a program structure that has been dictated by design. The following are the types of Integration Testing. Top-Down Integration This method is and incremental approach to the construction of program structure. Modules are integrated by moving downward through the control hierarchy, beginning with the main program module. The module subordinates to the main program module are incorporated into the structure in either a depth first or breadthfirst manner. Bottom-Up Integration This method begins the construction and testing with the modules at the lowest level in the program structure. Since the modules are integrated in the bottom-up, processing required for modules subordinate to a give level is always available and the need for stubs is eliminated. The bottom-up integration strategy may be implemented with the following steps. After integration of these modules, the performance and reliability of the software was tested. VALIDATION TESTING At the end of integration testing, Software is completely assembled as a package, interfacing errors have been uncovered and correction testing begins. SYSTEM TESTING System Testing is series of different test whose primary purpose is to fully exercise the computer based system. Although each test has a different purpose, al the work should verify that all system elements have been properly integrated and perform allocated functions

Scope for Expansion

Conclusion References Web Application Architecture

http://www.ibm.com/developerworks/ibm/library/it-booch_web/

Company Profile

Software Profile SOFTWARE PROFILE WINDOWS XP To use Windows XP professional! There are many new and exciting features at your fingertips. Some of these features are making their debut in Windows XP Professional, and others have been improved upon since earlier releases of Windows. There are new tools you can use to get the most out of your computer experience, and

other technologies that run in the background, making your computer run more efficiently and reliably. Windows XP Professional has great capability in the behind the scenes running of your computer. Overall security has been improved, making it even sager for u to shop and browse on the Internet. You can also communicate with other people on other networks without worrying about compromising your privacy or your personal data files. Performance is at an all – time high, allowing you to use more programs and have them run faster than ever. Windows XP Professional is dependable and stable, so you can always rely on the performance and effectiveness on your computer. Best of all, compatibility with other programs is better than ever. Windows XP Professional has many features and tools that will make using your computer easy, effective and entertaining. For example, you can use Remote Desktop to access your work computer and its resources from home and to view files and documents on your computer’s desktop from a co-worker’s with NetMeeting you can have virtual meeting with anyone, anywhere and you an participate in discussions using audio, video or chat.

PHP & MYSQL PHP stand for HYPERTEXT PREPROCESSOR. The product was originally named Personal Home Page Tools. PHP is widely used general purpose scripting language that is especially suited for web development and can be embedded into HTML. PHP is a Server-Side scripting language. PHP is an open source. Rasmus lerdrof, Apache team member and international man of mystery is PHP creator. The first part of PHP was developed for this personal use in late 1994.

MYSQL is an open source, SQL Relational Database Management System that is free for many uses. MYSQL found a broad, enthusiastic user base for its liberal licensing terms, perky performance and ease of use. Reason to Choose PHP and MYSQL There are so many reasons to Love PHP and MYSQL. Cost PHP cost is nothing. It is open source software. Open Source Software Don’t fear the chapter. It probably does not help that until recently software that did not cost money-formally called freeware, shareware or free software was generally through to fall into one of three categories. • • •

Program filling small, un commercial niches. Programs performing grungy, low-level jobs. Programs for people with bizarre socio-political issue.

The PHP License The freeness of open source and free software is guaranteed by a gaggle of licensing schemes, most famous the GPL (General Public Licensing) or copy left you can read the fine print about the relevant license at this websites. www.php.net/license/ www.mysql.com/doc/en/Gpl_license.html www.troll.no/qpl/annotated.html

Ease to Use PHP is easy to learn compared to the other ways of achieve similar functionality. PHP has a syntax that is quite easy to parse and human friendly. Many to the useful function are predefined. HTML Embedded ness PHP is embedded within HTML. PP pages are ordinarily HTML pages that escape into PHP mode only when necessary.

• • •

PHP can quickly be added to code produced by WYSIWYG editor. PHP lends itself to a division of labor between designers and scripter Every line of HTML does not need to be rewritten in a programming language • PHP can reduce labor costs and increase efficiency due to its shallow learning curve and ease of use. Cross-Platform compatibility PHP and MYSQL run native on every popular of UNIX and Windows. PP is compatible with the three leading web servers: Apache HTTP server for UNIX and Windows, Microsoft Internet Information server and Netscape enterprise server. PHP is almost totally cross-platform. Stability The server does not need to reboot often. The software does not change radically and incompatibly from release to release. Both of these connotations apply to both MYSQL and PHP. The Server Side Scripting good for • • • • • • • •

Content sites (both production and display) E-mail (web mail, mail forwarding and sending mail from a web application) Custer support and technical support systems Advertising networks Web-delivered business application Surveys, polls and tests Filling out submitting forms online Any other application that needs to connect a backend server to web serer.

PHP can handle all these essential tasks. A Note on Text Editors: There are many text editors and Integrates Development Environments (IDEs) that you can use to create, edit and manage PHP files. A Note on Word Processors: Word Processors such as Star Office Writer, Microsoft Word and Abiword are not optional for editing PHP files. If you wish to use one for this test script, you must ensure that you save the file as plain text or PHP will not be able to read and execute the script.

A Note on Windows Notepad: If you are writing your PHP scripts using Windows Notepad, you will need to ensure that your files are saved with the .php extension. (Notepad adds a .txt extension to files automatically unless you take one of the following steps to prevent it). When you save the file and are prompted to provide a name for the file, place the filename in quotes (i.e “hellow.php”). Alternatively, you can click on the “Text Documents” drop-down menu in the ‘save’ dialog box and change the setting to “All Files”. You can then enter your file name without quotes. Dealing with Forms One of the most powerful features of PHP is the way it handles HTML forms. The basic concept that is important to understand is that any form element will automatically be available to your PHP scripts. When a form is submitted to a PHP script, the information from that form is automatically made available to the script. There are many ways access this information. Basics Variables in PHP are represented by a dollar sign followed by the name of the variable. The variable name is case-sensitive. Database A database is a separate Application that stores a collection or data. Each database has one or many distinct APLs for Creating, Accessing, Managing, Searching and replicating the data it holds.

HTML HTML stands for Hypertext Markup Language. It was created by Timbernerslee and maintained by w3c (world wide consortium). The objects of HTML in the words of w3c are “a universally understood language, a kind of publishing mother tongue that all the computers may potentially understand”.

HTML documents are also called web documents and each HTM L document is known as a web page. HTML is the language that is used to design web pages. Meaning of HTML H-------Hyper Hyper is a nonlinear way of accessing information, which means consequential reading. This enables the reader to skip between sections. This “loss of order” makes the HTML Hyper. HTML allows the person viewing the World Wide web page to go anywhere. T--------Text This refers to the text conveys the information. A hypertext document is an electronic document that contains links to related of information. M-------Markup This refers to the way in which the text is marked up. Markup tells the browser about the method the content should be displayed. L--------Language This refers to language that is used to create web pages. A web page is basically a text file that contains the text to be displayed and references to element such as images, sounds and hyp0erlinks to other documents. HTML pages can be created using a simple text editor such as Microsoft front page. The browser interprets this textile and displays the output. Each web site, whether on the Internet is composed of multiple pages. We can switch between them by following hyperlinks. HTML is not a Computer language The abbreviation of HTML ends with word Language. Yet is not a language because it does not specify any logic. HTML is a structured language. It specifies only the layout format and structure of a document. But unlike a programming language, in which the compiler enforces rules, browser does ot strictly enforce HTML rules. HTML is Incomplete HTML is not over. The language does not provide all the facilities it should. For example it still does not provide font or pixel level control. Which is very important HTML knowledge is not required for creating web pages. Web pages can

be creating by using editors like front page, Visual Inter Dev, Cute HTML without knowing anything about HTML. The layout of the page must be done. However, to make a good page in web design, a strong understanding of HTML tags is needed. Requirements to Write HTML The following are the requirements to write HTML. • •

Browsers like Netscape navigator, Microsoft Internet explorer to hot java, which supports imager. A text edition like Notepad or WordPad or Dos editor.

HTML Tag The HTML tag identifies a document as an HTML document. The tag appears in the beginning and the tag appears at the document. Any HTML document is divided into two parts. • •

Header Body

Head The tag is used to identify the Header element. This tag contains information about the documents and can be used to define global settings. All the header information should be enclosed between the and tags. Title The <TITLE> tag specifies the title of the document. The text inside this tag appears in the title bar the browser window. This tag is generally used to give a name for the document. Meta The <META> tag specifies the information about the document Search engines or web browsers to identify the document use this information. The META tag is also used to create an HTTP response header. Body There can be only on tag per document. It specifies the main content of the document. The tag’s content can be plain text, forms, graphics, special content etc. All base contents should be enclosed between the and tags.

Heading Tags starting from H1 to H6 are used to display text in a big and bold font and they result in a new line. Paragraph The

tag identifies the paragraph element. A paragraph starts on a new line. This tag is also to insert a new break, but an empty

and

pair does not insert a line break in all browsers.

System Analysis SYSTEM ANALYSIS Generally System Study / Analysis and Design refer to the process of examining a business solution with the indent of improving it through better procedures and methods. System Analysis and System Design are the two major components of System Development. System Study is the process of gathering information and interpreting facts diagnosing problems and using the facts to improve the system.

In the process of planning a new system to replace or complement the old system, through analysis of existing system has to be done. So System Study plays an important role in the process of System Development. System Study has the following milestones that have to be crossed to produce good results. • • •

Analysis of Existing System Analysis of Proposed System Feasibility Study

FEASIBILITY STUDY The feasibility study concerns with the consideration made to verify whether the system fit to be developed in all terms. Once an idea to develop software is put the question that arise first will pertained to the feasibility aspects. There are different aspects in the feasibility study. • • •

Operational Feasibility Technical Feasibility Economical Feasibility

Operational Feasibility There is no difficulty in implementing the system, if the user has the knowledge in internal working of the system. Therefore, it is assumed that he will not faced during development of a new system is getting acceptance form the users. As users are responsible for initiating the development of a new system this is rooted out. Technical Feasibility Technical feasibility deals with the study of function , performance and constraints like resources availability, technology, development that may affect the ability to achieve an acceptable system. Economical Feasibility One of the factors, which affect the development of a new system, is the cost it would incur. The existing resources available in the company are sufficient for implementing the proposed and hence no extra cost has to be incurred to run the system developed. Thus, the system is financially feasible.

MOTHER TERESA BLOOD BANK SYSTEM REQUIREMENTS SOFTWARE AND HARDWARE SPECIFICATIONS Software Requirements Front End

:

PHP (Hypertext Preprocessor)

Back End

:

MYSQL

Operating System

:

Windows XP

Web Server

:

Apache

Design Tool

:

Macromedia Dream weaver

Hardware Requirements Processor Name

:

Pentium IV

RAM

:

128 MB

Hard Disk Drive

:

40 GB

Key Board

:

101 keys Standard

Mouse

:

Scrolling Mouse

Monitor

:

Samsung

System Design SYSTEM DESIGN LOGICAL DESIGN As there is no exist from manual system, the system has to be developed from manual system. Study of manual system is done thoroughly. • • • •

All the entities that affect the system are identified. Relationships between the entities are identified. All the attributes and constraints of each attributes are determined. All the entities are normalized for eliminating redundancy and to functional dependency.

PHYSICAL DESIGN Database Design Its schema defines the basic design of a database. The schema is the model, plan or structure around which fields, records and files are organized. The particular

schema selected depends upon many factors, including the kind and data type to be processed, the number of types of users, and the hardware available. The organization of data in the database is aimed to achieve two major objectives • •

Data Integrity Data Dependence

In relational database such as those created using Access, we store information about different subjects I suspects tables. To bring the information together in a meaningful way, we the tell database how the different subjects relates to each other. To Design a Database • • • • • • • • • • •

This helps we decided which facts we want database to store. Determine the tables. Divide the information into separate subjects. Each subject will be a table in the database. Determine the fields. Decide what information we want to store in each table. Each field is displayed as a column in the table. Determine the relationships between information. Look at each table and decide how the data in each table is related to the data on the other tables in the database. Add fields to the table. Determine the relationship between tables. Refine out design. Analysis the design for errors.

INPUT DESIGN Input design includes data mediums used for inputting data and validations that are to be done during data entry. Different messages and data are given to guide users during data entry. Validations checks are done for each input. Data entry screens are designed so that a system interacts with the users in providing an effective dialogue. Fields in the screen are logically arranged to help the user. The design is the process of converting the user-originated inputs into a computer-based format. The goal of the input designs is to make the data entry is easier, logical and free from errors. Errors in the input data are controlled by input design. The application has been developed in a user-friendly manner. The windows have been designed in such a way that during the processing the cursor is placed in the position where the data must be entered. If any of the data going into the system is wrong then the process and output will magnify these errors.

OUTPUT DESIGN Output refers to the results and information that are generated by the system. Output is the main reason for developing the system and based on this, the usefulness and applicability of system are primarily and communicate the results of processing to users. Efficiently designed outputs enhance the understandability of the information. According to the requirement of the system, various types of outputs are considered and designed as follows. 1. Internal outputs, whose determination is within the organization and which require careful, design because they are the user’s main interface with the computer. 2. Interactive outputs, in which the users communicate with the computer is essential. Data Flow Diagram DATA FLOW DIAGRAM (DFD) Introduction Data flow Diagram is a graphical technique that depicts information flow and transforms that are applied as data move from input. It serves two purposes: To provide an indication of how data are transformed as they move through the system. To depict the function that transforms the data flow. The DFD provides additional information that is used during the analysis of the information domain and servers as basics for the modeling of function. Symbols It denotes the information that resides outside the bounds of the system to be modeled. It denotes the information that resides within the bounds of the system to be modeled.

It denotes a data object the arrowhead indicates the direction of the data flow. It denotes a repository of data that is to be stored for use by one or more process.

DFD FOR ADMIN DFD FOR USER VIEW

Table Design NAME admin_id admin_uname psw

1. TABLE NAME: admin TYPE Int Varchar Varchar

2. TABLE NAME: donorregister

VALUE 10 250 250

NAME

TYPE

VALUE

reg_id

Int

10

name

Varchar

250

uname

longtext

pwd

Varchar

250

addr state city area email bg age gender weight

NAME bloodgroup_id Bloodgroup_name

3. TABLE NAME: bloodgroups TYPE VALUE Int 10 Varchar 250

4.TABLE NAME: states NAME state_id state_name

TYPE Int Varchar

VALUE 10 250

5.TABLE NAME: cities

NAME city_id state_ref_id city_name

TYPE Int int Varchar

VALUE 10 250 250

6.TABLE NAME: areas NAME

TYPE

VALUE

area_id

10

state_ref_id

Int Int

city_ref_id

Int

10

area_name

Varchar

250

10

7. TABLE NAME: sharefeel NAME

TYPE

VALUE

id

Int

11

msg

Varchar

250

System testing and Implementation SYSTEM TESTING INRODUCTION The Software Testing process commences once the program is created and documentation and related data structures and designed. Software Testing is essential

for correcting errors. Otherwise the program or the Project is not said to be completed. TESTING TYPES 5. 6. 7. 8.

Unit Testing Integration Testing Validation Testing System Testing

UNIT TESTING Unit testing focuses verification effort on the smallest unit of software design (i.e.), the module. Unit testing exercises specific paths in a module’s control structure to ensure complete coverage and maximum error detection. This test focuses on each individually, enduring that it functioned properly as a unit. Hence, the name is Unit Testing. In this project, after completion of each module the validity and performance of the module tested. INTEGRATION TESTING Integration Testing addresses the issued associated with the dual problems of verification and program construction. After the Software has been integrated a set of high-order tests are conducted. The main objective in this testing process is to take unit-tested modules and build a program structure that has been dictated by design. The following are the types of Integration Testing. Top-Down Integration This method is and incremental approach to the construction of program structure. Modules are integrated by moving downward through the control hierarchy, beginning with the main program module. The module subordinates to the main program module are incorporated into the structure in either a depth first or breadthfirst manner. Bottom-Up Integration This method begins the construction and testing with the modules at the lowest level in the program structure. Since the modules are integrated in the bottom-up, processing required for modules subordinate to a give level is always available and the need for stubs is eliminated. The bottom-up integration strategy may be implemented with the following steps.

After integration of these modules, the performance and reliability of the software was tested. VALIDATION TESTING At the end of integration testing, Software is completely assembled as a package, interfacing errors have been uncovered and correction testing begins. SYSTEM TESTING System Testing is series of different test whose primary purpose is to fully exercise the computer based system. Although each test has a different purpose, al the work should verify that all system elements have been properly integrated and perform allocated functions.

SYSTEM IMPLEMENTATION The term implementation has different meanings, ranging from the conversion of a basic application to a compatible replacement of a computer system. Implementation is use here to mean the process converting a new or a revised system design in to an operation one. During the implementation stage we convert the detailed code in a programming language. Goals for Implementation Stage The first goal of implementation is to provide a faithful translation of design. The choice of a language should be pragmatic, governed by mixture theoretical needs and practical constraints. Good software should avoid any gap between design codes. This is particularly important for reuse of component or for maintenance work that will require tracing the connection of design to code. CHARACTERISTICS OF IMPLEMENTATION Abstraction Abstraction deals with the ability of an implementation to allow the programmer to ignore the portion of details that is important at the current level of consideration. Each of the three kinds of abstraction control, data and process should present in the code. Modularization Modularization requires as partitioning the implementation, with each abstraction occupying its own separate and identifiable units.

Encapsulation While implementing a design , care should be taken to truly hide within a module. Verification Assertions use during format verifications of the detailed design should be included as comments in the source code. Implementation is the stage of the project when theoretical design is turned in to a working system.

6. SCOPE FOR EXPANSION 1)

Conclusion

The project “Mother Teresa Blood Bank “is for computerizing the working in a blood bank. The software takes care of all the requirements of an average blood bank and is capable to provide easy and effective storage of information related to donors that come up to the blood bank. It generates donors report; provide donor feedback details including various tests, diet advice. The system also provides the facility of backup as per the requirement.

Screen Layouts

Home page

Donor Registration Page

Why to Donate Blood page

Refer a Friend page

Quick Search for Donor

Donor Login

Contact us page

Related Blood Bank Links

Sharing Donor’s experience

Donor’s Voice

BIBILIOGRAHY RELATED BOOKS RELATED SITES