Blood Bank Management System

BLOOD BANK MANAGEMENT SYSTEM

SYNOPSIS

Blood bank management system(BBMS) is a browser based system that is designed to store, process, retrieve and analyze information concerned with the administrative and inventory management with a blood bank. This project is aims at maintaining all the information pertaining to blood donors, different blood groups available in each blood bank and help them manage in a better way. Aim is to prove transparency in this field, make the process of obtaining blood from blood bank hassle free and corruption free and make. The main objective of this application is to automate the complete operation of the blood bank. They need maintain hundreds of thousands of records. This application is built such a way that it should suits for all type of blood bank in a future. The front end of the software is PHP and back end of the MYSQL.

INTRODUCTION The population of the world is multiplying with each coming year and so are the diseases and health issues. With an increase in the population there is an increase in the need of blood. The growing population of the world results in a lot of potential blood donors. But in spite of this not more than 10% of the total world population participates in blood donation. With the growing population and the advancement in medical science the demand for blood has also increased. Due to the lack of communication between the blood donors and the blood recipients, most of the patients in need of blood do not get blood on time and hence lose their lives. There is a dire need of synchronization between the blood donors and hospitals and the blood banks. This improper management of blood leads to wastage of the available blood inventory. Improper communication and synchronization between the blood banks and hospitals leads to wastage of the blood available. These problems can be dealt with by automating the existing manual blood bank management system. A high-end, efficient, highly available and scalable system has to be developed to bridge the gap between the donors and the recipients and to reduce the efforts required to search for blood donors.

PROBLEM DEFINITION Problem definition deals with observation, site visits and discussions to identify analyze and document project requirements and carry out feasibility studies and technical assessments to determine the best approaches for full system development. Addition of new features is very difficult and creates more overheads. In existing system , data are not maintained properly which leads the followed-ups slow and lack of reports. The changes in one module or any part of the system is widely affected in other part or section. Keeping the problem definition in mind the proposed system evolves which is the user friendly, easy to update with the new in features, data is maintained and reports generated will be more useful for management to take quick business and so on.

SYSTEM STUDY EXISTING SYSTEM In order to elicit the requirements and to identify the elements, input, output, subsystems and the procedures the existing had to be examined and analyzed in details. The constituted the system study. Record slips, procedures, rules etc. were examined thoroughly. The existing system was studied involving a complete cooperation from the employees who run the system at present.

THE PROBLEMS WITH THE EXISTING SYSTEM  So much time consuming this application also one machine and one by one   

   

record stored. Single blood bank information also no inquiry for direct blood bank. It leads to error prone results. It consumes lot of manpower to better results. It lacks of data security. Retrieval data take lot of time. Percentage of accuracy is less. Reports take time to produce. The existing system is manually operated. The main drawbacks of the existing system is it take a lot of time to record various data and keeping is also difficult procedure because it take large number of space to store details and difficult to create reports on basis of various condition and also the searching is difficult because of medium storage like files. So it take a lot of manual effort and time. To overcome this drawback we implement the proposed system.

PROPOSED SYSTEM When I get the study I knew that the existing manual system contains a lot of drawbacks like it take more manual effort and also it is very time consuming etc. So in the proposed system all the drawbacks of the system is get overcome and the work that is going over there is changed to computerized and this make the work more easy like the consent giving details and also stored the minimum requirements etc. can be stored in the data base and the checking is automatically done by the software itself and the details of the consent get filled. This increase the total productivity. The use of paper file is avoided and all the data are efficiently manipulated by the system. The new system facilitates more automation of the various processes in the organization. It is easy to generate the report to know the status and which is difficult in the existing system we can reduce error which is difficult in the existing system. So by using this proposed system we can reduce the error which is occurred manually so that is why we introduce this proposed system.

ADVANTAGES OF THE PROPOSED SYSTEM  User view all blood bank information is location wise.  Donor easily donate blood near blood bank location.  Patient easily request for blood near blood bank location.  In this system also supported inquiry for user.

SYSTEM ANALYSIS One of the main meanings of the feasibility is possibility. Checking of the different criteria for success is included in feasibility study section. These criteria’s are cost,time, efficiency etc….all these factors play an important role in achieving objective of the system. That means the system should be such it gives optimum performance at minimum cost, time, requirements. The system contributes to the overall objectives of the organization. The system be implemented using current technology and within given cost and schedule constrains. The system is integrated with systems which are already in place.

FEASIBILITY STUDY Feasibility is conducted to identify the best system that meets all requirements. It is both necessary and important to evaluate the feasibility of a project at the earliest possible time. Feasibility study includes an identification description, an evaluation of proposed system and feasibility study of the proposed system is to be carried out. This is to ensure that the proposed system is not a burden to the shop. The feasibility study should be relatively cheap and quick. The results should inform the decision of whether to go ahead with a more detailed analysis for feasibility analysis, some understanding of the major requirements for the system is essential. Four key consideration involved in the feasibility analysis are

 ECONOMICAL FEASIBILITY.  TECHNICAL FEASIBILITY.  OPERATIONAL FEASIBILITY.

ECONOMICAL FEASIBILITY: Economical feasibility is the most frequently used method for evaluating the effectiveness of the candidate system. It is very essential because the main goal of the proposed system is to have economically better result along with increased efficiency. A cost evaluation is weighed against the ultimate income or

product. Economic justification is generally the bottom-line consideration that includes cost benefit analysis, long term corporate income strategies, and cost of resources needed for development and potential market growth. When compared to the advantage obtained from implemented the system its cost is affordable. This organization. The amount of fund that company can pour into the research and development of the system is limited. The expenditures must be justified. Thus the developed system as well within the budget and this was achieved because most of the technologies used are freely available Installation of new system will reduce administrative and operational cost. The newly developed software that doesn’t require any existing manual paper works and files. So cost also can reduced by removing these types of materials. Proposed system was developed with available resources. Since cost input for the software is almost nil the output of the software is always a profit. Hence software is economically feasible.

4.1.2 TECHNICAL FEASIBILITY: The study is carried out to check the technical feasibility, that is, the technical requirements of the system. Any system developed must not have a high demand on the available technical resources. This will lead to high demands on the available technical resources. The developed system must have a modest requirement, as only minimal or null changes are required for implementing this system. This is related to the technicality of the project. This evaluation determines whether the technology needed for the proposed system is available or not. It deals with hardware as well as software requirements. That is, type of hardware, software and the methods required for running the system are analyzed. A study of function, performance and constraints may improve the ability to create an acceptable system, technical feasibility is frequently the most difficult area to achieve at the stage of product engineering process. The scope was whether the work for the project is done with the current equipment and the existing system technology has to be examined in the feasibility study. The result was found to be true. This feasibility is carried out to check the technical requirements of the system

This system is implemented by using php. So it can be used in any windows OS computer. This system requires very low system resources and it will work in almost all configurations. In the existing system all functions are doing manually. So if they get this designed software, the problems can be avoided and thus the system will run smoothly. In the proposed system, data can be easily stored and managed using database management system software. The reports and results for various queries can be generated easily. Our proposed system is technically feasible to use by any user.

4.1.3 OPERATIONAL FEASIBILITY:

The purpose of the operational feasibility is to determine whether the new system will be used if it is developed and implemented and whether there will be resistance from user that will undermine the possible application benefits. The aspect of study is to check the level of acceptance of the system by the user. This includes the process of training the user to use the system efficiently. The user must not feel threatened by the system, instead must accept it as a necessity. The level of acceptance by the user solely depends on the methods that are employed to educate the user about the system and to make him familiar with it. His level of confidence must be raised so that he is also able to make some constructive. The proposed system is an upgrade version of the current system new fields have been implemented according to the user need, hence it ensure a user friendly environment in such a way that it ensures all the aspects. The proposed system is very much user friendly and the system is easily understood by simple training and it is operationally feasible to use by any users.

SOFTWARE REQUIREMENT SPECIFICATION INTRODUCTION This project is developed to manage the blood stock in the “BLOOD BANK” and the blood prices are maintained in the database. New blood details are entered in to the project to manage blood details. Blood donor details are entered and maintained in the database. Blood sales and blood purchases are entered maintained in this project. Blood stock reports, sales reports and blood purchases reports are managed in this project.

PURPOSE The blood bank management system has been created with a purpose of replacing of the paperwork done at the blood bank. All aspect of blood banking, be it donors record management, blood stock details management, acceptor record management, blood issues, all is completely managed by the software. The system boasts in variety and number of reports made available for analysis, legal documentation and insight.

SCOPE The specification builds on the experience of users of IT technology in blood transfusion that is currently available and informs both Connecting For Health(CFH) and commercial companies producing both hardware and software. The main objective of this specification is to support the automated tracking of

blood products from the initial ordering of blood transfusion for and subsequent updates to care records.

REFERENCES Wikipedia Google play store

OVERVIEW Blood bank management system is to maintained all the information o blood donors, different blood groups available in each and help them manage in best way. This system provides transparency in this field, make the process of obtaining blood from blood bank corruption free and make the system of blood bank management effective.

OVERALL DESCRIPTION Blood bank management system is to maintained all the information o blood donors, different blood groups available in each and help them manage in best way. Blood bank management system can help to collect blood from many donors from various sources and distribute the blood to needy people who require

blood. This system have many facilities like online transfer blood from one blood bank to another. This project can manage list of donors who are eligible for donation on a particular date with contact number. This system is an blood bank management system that helps in managing various blood bank operations effectively.

SOFTWARE FEATURES  Admin  Donor  Acceptor  Blood Bank

FUNCTIONAL SPECIFICATION Admin Module This module focuses on the donor, acceptor, blood bank. Each member in donor, acceptor and blood bank is given a user id and password, which identifies him uniquely. The member is given a user id and password.

Donor Module Each member in a donor is given a user id and password, which identifies him uniquely. The member is given a login form. He enters the login details user id and password.

Acceptor Module This module contains the information about acceptor. This module manages the acceptor information. Each member in the acceptor is given a user id and password, which identifies him uniquely.

Blood Bank This module contains blood bank information(view/delete) and also view the stock of available blood. This module manages acceptor blood request.

HARDWARE REQUIREMENTS Hardware Requirements for Development are as listed below.  Processor: Pentium 4 or above  RAM :2 GB or above  Hard disk :40 GB or above

SOFTWARE REQUIREMENTS Windows operating system Dream Viewer Wamp server

SOFTWARE FEATURES Dream Viewer Dreamweaver features an integrated browser for previewing developed web pages in the program's own preview pane in addition to allowing content to be open in locally installed web browsers and manipulate the layout of HTML elements. Dreamweaver, like other HTML editors, edits files locally then uploads them to the remote web server using FTP, SFTP, or WebDAV. Dreamweaver CS4 now supports the Subversion (SVN) version control system. Dreamweaver is a website editor WYSIWYG for Microsoft Windows and Mac OS X created in 1997, marketed by Macromedia and Adobe Systems on End User License .Dreamweaver was one of the first publishers HTML type "such a display, such a result", but also one of the first to integrate a site manager (Adobe Dreamweaver is a web design and development application that provides a visual WYSIWYG editor (colloquially referred to as the Design view) and a code editor with standard features such as syntax highlighting, code completion, and code collapsing as well as more sophisticated features such as real-time syntax checking and code introspection for generating code hints to assist the user in writing code.[4] The Design view facilitates rapid layout design and code generation as it allows users to quickly create CyberStudioGoLive being the first). These innovations quickly imposed it as a leading site web , both used by the novice as professional.

SYSTEM DESIGN

System design is the process of developing specification for candidate system that meet the criteria established in the system analysis. Major step in system design is the preparation of the input forms and the output reports in a form to the user. The main objectives of the system design is to the packages easily by any computer operator system design is the creative act of invention, developing new outputs, a database, offline files, methods, procedures and out for processing business to meet an organization objectives. System builds information gathered during the system analysis. System design has four phases.  Input design  Output design  Dataflow diagram  E-R diagram  Activity diagram  Use-case diagram

INPUT DESIGN

Input design is the link that ties the information system into the world of its users. The input design involves determining what the input is, how the data should be performed, how to validate data, how to minimize data entry and how to provide a multi user facility, Inaccurate input data are the most common cause of errors in data processing. Errors entered by data entry operator can be controlled by input design. Input design is the process of converting user originated input to a computer-based format. Input data are collected and organized into groups of similar data. Once identified, appropriate input media are selected for processing All the input data re validated in the order and if any data violates any conditions, the user is warned by a message. If the data satisfies all the conditions then it is transferred to the appropriate table in the database. A form is designed to enter the details should be user friendlier so that authorized user with even less knowledge can enter the data. The form is designed using V B tools like command boxes, text boxes, labels, option buttons, combo boxes etc. System analyst decodes the following input design details,     

What data to input. What medium to use. How the data should be arranged or coded. The dialogue to guide the users in providing input. Methods for performing input validation and stud to follow when error occur. The input screens are displayed in a way that the user can understand entries very easily. Proper validation and controlling of input data will reduce the chance of errors. All major operations are done only after checking the result of information messages. This makes the system reliable and user friendly

DATAFLOW DIAGRAM

A DFD, also known as a “bubble chart” has the purpose of clarifying system- requirements and identifying major transformations that will become programs in system design. A DFD consists of a series of bubbles joined by lines. The bubbles represents data transformations and the lines represents data flow in the system. A data flow diagram may be used to represent a system or software at any level of abstraction. A DFD is a diagram that describes the flow of data and the processes that change or transform data throughout a system. It is a structured analysis and design tool that can be used or flowcharting in place of, or in association with, information oriented and process oriented system flowchart. When analyst prepare the DFD, they specify the user needs at a level of detail that virtually determines the information flow into and out of the system and the required data resources. This network is constructed by using a set of symbols that do not imply a physical implementation. The DFD reviews the current physical system, prepare input and output specification, specifies the implementation plan etc.

Context Diagram A context diagram is a level-0 DFD and represents the entire system elements as a single bubble with input and output data indicated by incoming and outgoing arrows respectively. The user gives data or commands as input and the user will get the details as output.

Basic data flow diagrams symbols are: - A “Rectangle” defines a source or destination destination of a system data

- An “Arrow” identifies data flow. It is a pipeline through which information flows.

- A “circle “ represents a process that transforms incoming data flow(s) into outgoing data flow(s).

- An “open rectangle” is a data store.

Steps to construct Data Flow Diagram Four steps are commonly used to construct a DFD  Process should be named and numbered for easy reference. Each name should be representative of the process.  The direction of flow is from top to bottom and from left to right.  Then a process is exploded in to lower level details they are numbered

CONTEXT LEVEL(LEVEL 0)

REQUEST

USER

RESPOND

REQUEST BLOOD BANK MANAGEMENT SYSTEM

RESPOND

USER

LEVEL 1 ADMIN

REGISTRATION

ADMIN

REGISTRATION DETAILS

VIEW DONOR DEATILS

DONOR DETAILS

VIEW BLOOD REQUEST

BLOOD REQUEST DETAILS

VIEW BLOOD REQUEST

BLOOD STOCK DETAILS

DONOR REG REGISTRATION DONOR

REGISTRATION DETAILS

ACCEPTOR REG REGISTRATION

ACCEPTOR

REGISTRATION DETAILS

SEARCH DONOR

DONOR DETAILS

REGISTRATION

REGISTRATION DETAILS

BLOOD BANK

REG BLOOD BANK

BLOOD STOCK

BLOOD STOCK DETAILS

E-R DIAGRAM

PASSWORD

USERNAME

ADMIN 1

1 1 MANAGES

MANAGES

NAME

NAME M ACCEPTOR

M DONOR

M

M

BLOOD GROUP

BLOOD GROUP

HAS

HAS

M BLOOD BANK 1 BLOOD ID

1 BANK NAME NNNNNNNN AME NAMENAME

ACTIVITY DIAGRAM Activity diagram is another important diagram in UML to describe dynamic aspects of the system. Activity diagram is basically a flow chart to represent the flow from one activity to another activity. The activity can be described as an operation of the system. So the control flow is drawn from one operation to another. This flow can be sequential, branched or concurrent. Activity diagrams deals with all type of flow control by using different elements like fork, join etc. The basic purposes of activity diagrams are similar to other four diagrams. It captures the dynamic behaviour of the system. Other four diagrams are used to show the message flow from one object to another but activity diagram is used to show message flow from one activity to another. Activity is a particular operation of the system. Activity diagrams are not only used for visualizing dynamic nature of a system but they are also used to construct the executable system by using forward and reverse engineering techniques. The only missing thing in activity diagram is the message part. It does not show any message flow from one activity to another. Activity diagram is some time considered as the flow chart. Although the diagrams looks like a flow chart but it is not. It shows different flow like parallel, branched, concurrent and single.

ACTIVITY DIAGRAM Activity diagram for admin:

NO REGISTRATION

REG YES

LOGIN

NO

VALID?

YES

MANAGE THE DONOR

MANGE THE ACCEPTOR REQUEST

VIEW BLOOD STOCK

LOGOUT

END

Activity diagram for donor:

NO

REGISTRATION

YES

REG

LOGIN

NO

VALID

YES

MAKE NEW BLOOD DONATION

VIEW PROFILE

LOGOUT

END

Activity diagram for Acceptor:

NO

REGISTRATION

YES

REG

LOGIN

VALID NO

YES

ACCEPTOR REQUEST FOR BLOOD

VIEW PROFILE

LOGOUT

END

Activity diagram for Blood Bank:

NO

REGISTRATION

YES

REG

LOGIN

NO

VALID

YES

MANAGE BLOOD STOCK

ADD NEW BLOOD BANK

LOGOUT

END

USE CASE DIAGRAM

To model a system the most important aspect is to capture the dynamic behavior. To clarify a bit in details, dynamic behaviour means the behaviour of the system when it is running /operating. So only static behaviour is not sufficient to model a system rather dynamic behaviour is more important than static behaviour. In UML there are five diagrams available to model dynamic nature and use case diagram is one of them. Now as we have to discuss that the use case diagram is dynamic in nature there should be some internal or external factors for making the interaction. These internal and external agents are known as actors. So use case diagrams are consists of actors, use cases and their relationships. The diagram is used to model the system/subsystem of an application. A single use case diagram captures a particular functionality of a system. The purpose of use case diagram is to capture the dynamic aspect of a system. But this definition is too generic to describe the purpose. Because other four diagrams (activity, sequence, collaboration and State chart) are also having the same purpose. So we will look into some specific purpose which will distinguish it from other four diagrams. Use case diagrams are used to gather the requirements of a system including internal and external influences. These requirements are mostly design requirements. So when a system is analyzed to gather its functionalities use cases are prepared and actors are identified.

USE CASE DIAGRAM USE CASE FOR ADMIN:

REGISTRATION

LOGIN

MANAGE DONOR

MANAGE ACCEPTOR REQUEST

VIEW BLOOD STOCK

USE CASE FOR DONOR:

REGISTRATION

LOGIN

VIEW PROFILE

MAKE NEW BLOOD DONATION

USE CASE FOR ACCEPTOR:

REGISTRATION

LOGIN

VIEW PROFILE

ACCEPTOR REQUEST FOR BLOOD

TABLES

Table name: sign up Primary key: regno Description: This table store the sign up information. Field Name regno

Data Type int

Size 10

Constraints Primary key

fname

varchar

50

Not null

lname

varchar

50

Not null

email

varchar

50

Not null

bigint

12

Not null

varchar

50

Not null

contact

username

Description To Store register number To store first name To store last name To store email To store contact number To store username

Table name: login Primary key: loginid Description: This table store the login information.

Field Name Data Type loginid int

Size 10

Constraints Primary key

Username

varchar

50

Not null

password

varchar

50

Not null

usertype

varchar

50

Not null

Description To store loginid To store username To store password To store usertype

Table name: Donor Primary key: donorid Description: This table store the donor information. Field Name Donorid

Data Type int

Size 10

Constraints Primary key

donorname

varchar

50

Not null

bloodgroup

varchar

12

Not null

gender

varchar

12

Not null

city

varchar

50

Not null

Hosdeatils

varchar

100

Not null

doctorname

varchar

50

Not null

cname

varchar

50

Not null

cemail

varchar

50

Not null

cnumber

bigint

12

Not null

message

varchar

100

Not null

Description To store the donor id To store the donor name To store the blood group To store the gender To store the city

To store the hospital name&address To store the doctor name To store the contact name To store the contact email To store the contact number To store the messages

Table name: Acceptor Primary key: acceptorid Description: This table store the acceptor information. Field Name

Data Type

Size

Constraints

Description

acceptorid

int

10

Primary key

To store the acceptor id

acceptor name

varchar

50

Not null

To store the acceptor name

bloodgroup

varchar

12

Not null

To store the blood group

gender

varchar

12

Not null

To store the gender

city

varchar

50

Not null

To store the city

Hosdeatils

varchar

100

Not null

To store the hospital name&address

doctorname

varchar

50

Not null

To store the doctor name

cname

varchar

50

Not null

To store the contact name

cemail

varchar

50

Not null

To store the contact email

cnumber

bigint

12

Not null

To store the contact number

message

varchar

100

Not null

To store the messages

Table name: blood bank Primary key: bankid Description: This table store the blood bank information. Field Name bankid

Data Type int

Size 10

Constraints Primary key

Bloodbankname varchar

50

Not null

username

varchar

12

Not null

password

varchar

12

Not null

city

varchar

50

Not null

Hosdeatils

varchar

100

Not null

cname

varchar

50

Not null

cemail

varchar

50

Not null

cnumber

bigint

12

Not null

message

varchar

100

Not null

Description To store the bank id To store the bank name To store the username To store the password To store the city To store the hospital name&addres s To store the contact name To store the contact email To store the contact number To store the messages

Table name: stock details Primary key: stockid Description: This table store the stock information. Field Name stockid

Data Type int

Size 12

Constraints Primary key

bloodgroup

varchar

12

Not null

quantity

int

20

Not null

12

Not null

Expairydate date

Description To store stock id To store blood group To store quantity To store expairydate

Table name: contact Primary key:contactid Description: This table store the contact information. Field Name cid

Data Type Int

Size 10

Constraints Primary key

Name Email Phone

Varchar Varchar Bigint

50 50 12

Not null Not null Not null

Message

Varchar

50

Not null

Description To store contact id To store name To store email To store phone number To store message

System testing Testing is an important phase in software development. After completion, the system may work without any problem. But, there should be several unknown or hidden errors in the system still remaining. The error chances may injected into the system at any stage of the development. Even if there are techniques to detect and eliminate the errors, some errors may retain in the system. So after the completion of coding, the system is to be executed with the only purpose of detecting maximum number of errors. The tester executes the system, and inputs different types of values those may cause error or some exceptional situation in the system. The error locations detected through the testing are to be corrected in the system then. So, the important and the only aim of testing is to detect and cure even a less possible of an error that may face in the future executions of the system. Testing is a set of activity that can be planned in advance and conducted systematically. Testing begins at the module level and work towards the integration of entire computers based system. Nothing is completed without testing, as it is vital to the success of the system. System testing makes a logical assumption that if all parts of the system are corrected, the goal will be successfully achieved. Inadequate testing or non-testing may lead to errors that may not appear until months later.

PURPOSE OF TESTING Testing is the success of the system. System Testing makes a logical assumption that if all part of the system is correct, the goal will be successfully achieved. The following points shows how testing is essential. Existence of program defects of Inadequacies is inferred.    

Verifies whether the software behave as intended by its designer. Checks conformance with requirements specification or user need. Assesses the operational reliability of the system. Test the performance of the system.

    

Find the fault which caused the output anomaly. Detect flaws and deficiencies in requirements. Exercise the program using data like the real data processed by the program. Test the system capabilities. Judges whether or not the program is usable in practice.

TESTING OBJECTIVES There are several rules that can serve as testing objectives. They are;  Testing is a process of executing a program with the intent of finding error.  A good test case is one that has high probability of finding an undiscovered error.  A successful test is one that uncovers an undiscovered error. If testing is conducted successfully according to the objectives as stated above, it would uncover errors in the software. Also testing demonstrates that software functions appear to the working according to the specifications, that performance requirement appear to have been met. These are three ways to test a program  For correctness  For implementation Efficiency  For Computational Complexity Test for correctness are supported to verify that a program does exactly what it was designed to do. This is much difficult that it may at first appear especially for large programs. Tests for implementation efficiency attempt to find ways to make a correct program faster or use less storage. It is a code-refining process, which reexamines the implementation phase algorithm development. Tests for computational complexity amount to an experiment analysis of the complexity of an algorithm or an experiment comparison of two or more algorithms, which solve the same problem.

TYPES OF TESTING System testing is the stage of implementation, which is aimed at ensuring that the system works accurately and efficiently before live operation commences. Testing is vital to the success of the system. System testing makes a logical assumption that if all the parts of the system are correct. The goal will be successfully achieves. The candidate system is subject to a variety of tests. A series of tests are performed for the proposed system is ready for system acceptance testing. The various levels at which testing are conducted are     

Unit testing Integration testing Sequential testing System testing Validation testing

UNIT TESTING In unit testing each program unit is tested individually.so any errors in a unit are debugged. Sample data is given for unit testing. The unit test results are recorded for future references. Unit testing focus verification efforts on the smallest unit of software design, the module. This is known as “module testing”. It comprises of the set test performed by an individual programmer prior to the integration of unit into the large system. The modules are tested separately, this testing is carried out programming stage itself. In this step each module is found to be working satisfactory as regard to the expected out from module. The unit testing was done for every module in the software for various inputs, such they each line of code is at least once executed. This testing was carried out during the unit to a large system.

INTEGRATION TESTING Integration testing is a systematic technique for constructing the program structure while at the same time conducting test to uncover errors associated with interfacing. The objectives is to takr units tested components and build a program structure that has been dedicated by design. Incremental integration is a type of integration testing where in the program is constructed and tested in small increments, where the error are easier to isolate and correct.

USER ACCEPTANCE TESTING Acceptance testing is running the system with live data by the actual user. An acceptance test has the objective of selling the user in the validity and reliability of the system. A comprehensive test report is prepared. The report indicates the system’s tolerance, performance range,error rate and accuracy. It verifies the system procedures operate to system specification and the integrity of important data is maintained, performance of an acceptance test is actually the users show. User motivation is very important for the successful performance of the system. After that a comprehensive test report is prepared. This report shows the systems tolerance, performance range, error rate and accuracy.

VALIDATION TESTING Here the inputs are given by the user are validated. That is password validation, format of data are correct, textbox validation. Changes are need to be done after result of this testing. Verification testing runs the system in a simulated data. Validation refers to the process of using software in order to find errors. The feedback from the validation phase generally produces changes in software to deal with errors and failures that are uncovered. Validation may continue for several months.

SYSTEM IMPLEMENTATION A Crucial phase in the system life cycle is the successful implementation of the new system design. Implementation involves creating computer compatible files, training the operating staff, installing hardware, terminals. In the system implementation, user training is crucial for minimizing resistance to change and giving the new System a chance to prove its worth. The objectives og the system implementation is to put the system into operation while holding costs, risks and personal irritation to minimum. Once the physical system has been designed in details, the next stage is to run the design into a working system and then to monitor the operation of the system to ensure that is continue to work efficiently and the operation of the system to ensure that is continues to work efficiently and effectively. The implementation stage of a is often very complex and time consuming because many more people are involved than in the earlier stages. The system implementation took place through various stages as follows,     

Implantation planning. Education and training. System testing. System implementation. Change over.

The implementation plan includes a description of all the activities that must occurs to implement the new system and to put it into operation. To achieve the objectives and benefits from computer based system, it is essential for the people who will be confident of their role in the new jobs. After software is developed to meet usre’s requirements, users test it for acceptance. The changes over phase is used to provide adaptability for the new system.

SYSTEM MAINTENANCE Software maintenance is the process of modifying a software system or component after its delivery in order to correct faults, improve the performance and other attributes, or to adapt to the changed environment. Maintenance covers a wide range of activities including correcting the error and design coding, updating the documentation and test data, and upgrading the user support. There is an aging process that calls for periodic maintenance of hardware and software. Maintenance is always necessary to keep the software usable and useful. Hardware also requires periodic maintenance to keep the system in to its standards. After installation is completed and the user starts is adjust to the changes created by the candidate system. Evaluation and maintenance begin. If new information is consistent with design specification the changes have to be made. Hardware also requires periodic maintenance to keep in tune with design specification. User priorities changes in organizational requirements or environmental factors also called for system enhancements. Maintenance covers a wide range of activities, including correcting, coding and design errors, updating documentation and test data, and upgrading user support. Any activities classified as maintenance are actually enhancements. Maintenance means restoring something to its original condition. Unlike hardware, however, software does not wear out; it is corrected. In contrast enhancement means adding, modifying or developing the code to support changes in the specifications. It is necessary to keep up with changing user needs and the operational environment. Maintenance can be classified as corrective, adaptive or perfective. Corrective maintenance means repairing processing or performance failures or making changes because of previously uncorrected problems or false assumption. Adaptive maintenance means changing the program function. Perfective maintenance means enhancing the performance or modifying the program to respond to the user’s additional or changing needs. Of these types, more time and money are spend on perfective than on corrective and adaptive maintenance together. in a formal system project. A major problem with software maintenance is its labor intensive nature. Documentation is as much a part of maintenance as it is of system development. To put maintenance in its proper

perspective requires considerable skill and experience and is an important and ongoing aspect of system development. An additional factor in the success of the maintenance programmer is the work environment. Software maintenance activities can be classified into:  Corrective maintenance  Adaptive maintenance  Perceptive maintenance Corrective maintenance removes software faults. Perfective maintenance improves the system without changing its functionality. The objective of perfective maintenance should be to prevent failures and optimize the software. Adaptive maintenance modifies the software to keep it up to date with its operative environment it may be needed because of changes in the user requirements, changes in target platform, or changes in external interfaces… If you want to change the software to improve future maintainability or reliability or to provide better basic for future enhancement then perceptive maintenance is perform.

9.FUTURE ENHANCEMENT Almost every project is subjected to change on depending on the client requirements. Since this system is subjected to change for each and every client, there is always a scope for further enhancement. The system and the architecture of the assessment system is a compatible one, so addition of new modules can be done without much difficulty. The software is developed in php which makes the system more reliable and compatible with other environments. The application proves better extensibility and flexibility for future enhancements. Any further requirement application is possible with the same feature guaranteed. It is a user –friendly system, which is very easy and convenient to use. The system is complete in the sense that it is operational and it is tested by entering data and getting reports in proper order. During the development of this project coding standards are followed for easy maintainability and extensibility. Though the new system provides a base for improving the efficiency of operations, there are lots of further enhancement that can be added to this project. Keeping this in view, provision has been made in the system to facilitate easy modification updating in future. Any modification will not affect the normal working of the system. The developed system is very interactive, coded in such a way to ensure maximum user friendliness and also allows flexibility for future. The system developed automates most needed activities in an organization. The new system can be combined with an existing system as well. More and better advanced separation system can be build on top of the proposed system as and when the need arises. This is one of the main special feature of the proposed system.