ANILANEELAK

Blood On Web
INTRODUCTION
Dept .of Computer Applications
AWH Engineering College
Blood On Web
1. INTRODUCTION
Blood on Web is a software application to maintain day to day transactions in a blood bank. This software helps to register all the donors. The main objective of this application is to automate the complete operations of the blood bank. They need maintain hundreds of thousands of records. Also searching should be very faster so they can find required details instantly. This application is built such a way that it should suits for all type of blood banks in future. So every effort is taken to implement this project. This project has following parts to manage all the requirements of the blood bank. 1. Blood Bank details. 2. Donor Details. 3. Recipient Details. 4. Blood Collection Details. 5. Stock Details.
1.1Module Description
1.1.1Blood Bank Details Blood Bank is one of the major components of hospital concerned with various related activities including donor registration, physical examination, blood grouping, blood infectious tests, component separation, blood requisition and cross match. The Blood bank module provides ready information about blood reserve/stock, daily cross matched details, total daily blood requisitions and information regarding blood and donor. 1.1.2 Donor Details Donation of blood is a sign of kindness and care for the fellow human beings.
Blood On Web
There is no gift more valuable than a Gift of Blood, as it is actually a gift of life for the person who receives it. You can go to the nearest government approved blood centre, which is based on voluntary non/remunerated blood donation and make your significant contribution to saving life of a patient by donating blood. 1.1.3Recipient Details The source details screen is only displayed for target groups that have parameters defined. This screen allows the account holder to choose the specific recipients from the target group based on the parameters set up by the administrator. Each parameter is designed by the data administrator. 1.1.4 Blood Collection Details It is the collection of blood in the blood bank. There are different blood groups in the blood bank. Recipients can search the collection details. 1.1.5 Stock Details There are different collections of blood in each hospital. Users can view and search the stock details. They have to choose the blood group.
Blood On Web
SYSTEM ANALYSIS
Blood On Web
2. SYSTEM ANALYSIS
System analysis is a process of gathering and interpreting facts, diagnosing problems and the information to recommend improvements on the system. It is a problem solving activity that requires intensive communication between the system users and system developers. System analysis or study is an important phase of any system development process. The system is studied to the minute detail and analyzed. The system analyst plays the role of the interrogator and dwells deep into the working of the present system. The system is viewed as a whole and the input to the system are identified. The outputs from the organizations are traced to the various processes. System analysis is concerned with becoming aware of the problem, identifying the relevant and decisional variables, analyzing and synthesizing the various factors and determining an optimal or at least a satisfactory solution or program of action. A detailed study of the process must be made by various techniques like interviews, questionnaires etc. The data collected by these sources must be scrutinized to arrive to a conclusion. The conclusion is an understanding of how the system functions. This system is called the existing system. Now the existing system is subjected to close study and problem areas are identified. The designer now functions as a problem solver and tries to sort out the difficulties that the enterprise faces. The solutions are given as proposals. The proposal is then weighed with the existing system analytically and the best one is selected. The proposal is presented to the user for an endorsement by the user. The proposal is reviewed on user request and suitable changes are made. This is loop that ends as soon as the user is satisfied with proposal. Preliminary study is the process of gathering and interpreting facts, using the information for further studies on the system. Preliminary study is problem solving activity that requires intensive communication between the system users and system developers. It does various feasibility studies. In these studies a rough figure of the system activities can be obtained, from which the decision about the strategies to be followed for effective system study and analysis can be taken.
Blood On Web
2.1 Existing system

This project is developed to reduce the drawbacks of existing method. Normally a blood bank gives many transactions in the city. Presently they maintain all records manually. This is windows application so we have to reach the blood bank to know whether the blood is available or not. To solve this problem now we are looking for better alternative solution. Drawbacks of Existing System Difficult for use. All records maintain manually Have to reach blood bank to know details.
2.2 Proposed system

To manage all the transactions we proposed here with software solutions which will takes care of all the necessary transactions. On implementation of this software it will help them in many ways. The blood bank project is implemented for an easier way to search blood group. This is a web application project, so any one can search blood via online from anywhere and donor registration is also possible in this way. Advantages of Proposed system Easy to use Easier way to search blood group Any one can search blood via online. Donor registration is also possible in this way.
Blood On Web
FEASIBILITY STUDY
Blood On Web
3. FEASIBILITY STUDY
The development of a computer-based system is more likely to be plagued by security to resources and difficult delivery rates. The feasibility study is not warranted system in which economic justification is obvious technical risk is low, few legal problems are expected and no reasonable alternative exists. Not all requested projects are feasible. Three essential aspects are involved in the feasibility study promotion of preliminary investigation: technical, economic, Operational feasibility. All projects are feasible when given unlimited resources and infinite time It is both necessary and prudent to evaluate the feasibility of a project at the earliest possible time. A feasibility study is not warranted for systems in which economic justification is obvious, technical risk is low, few legal problems are expected and no reasonable alternative exist. The study will decide if the proposed system will be cost effective from the business point of view and if it can be developed in the given existing budgetary constraints, The feasibility study should be relatively cheap and quick. The result should inform the decision of whether to go ahead with a more detailed analysis. Feasibility study may be documented as a separated report to higher officials of the top-level management and can be included as an appendix to the system specification. Feasibility and risk analysis is related in many ways. If there is more project risk then the feasibility of producing the quality software is reduced
3.1 Technical feasibility

Technical feasibility centres on the existing computer and to what extend it can support the proposed addition. For e.g.: the current computer is operating at 80% capacity, then running another application could overload the system and require additional hardware. This system requires a multiple user environment. It needs a powerful RDBMS database MS SQL Server to the purpose. So this system is technically feasible with without requiring any additional hardware or software. If the budget is a serious constraint then the project is judged technically feasible.
Blood On Web
Technical feasibility study deals with the hardware as well as software requirements. The scope was whether the work for the project is done with the current equipments and existing software technology has to be examined in the feasibility study. The outcome was found to be positive. 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. Therefore, the system is technically feasible
3.2 Economic feasibility

Economic analysis is the most frequently used method for evaluating the effectiveness of a candidate system. More commonly known as cost/benefit analysis, the procedure is to determine the benefit and saving that are expected from a candidate system and compare them with the term of time by automating the process of report generation. A system that can be developed technically and that will be used if installed must still be a good investment or the organization is more. Hence this package is economically feasible. A cost evaluation is weighed against the ultimate income or benefit derived from the developed system or product. Economic justification is generally the bottom-line consideration that includes cost benefit analysis, long term corporate income strategies, impact on other profit centres or products, cost of resources needed for development and potential market growth. When compared to the advantage obtained from implementing the system its cost is affordable. Also the system is designed to meet the modifications required in the future. So most of the required modifications can be done without much re-work. Proposed system was developed with the 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. In the existing system, manpower is more required. In the proposed system, number of employees to be involved is reduced drastically. So, the proposed system is said to be economic.
Blood On Web
10
3.3 Operational feasibility

Proposed systems are beneficial only if they can be turned into information system that will meet the organizations operating requirements. People are inheritably resistant to change and computers have been known to facilitate change. An estimate should be made to know how strong the reaction of a user staff is likely to have towards the development computerized system. Since this system ready to use in the organization, it is operationally feasible. As this package is technically, economically and functionally feasible, the system is judged feasible. Viewing the collected information, recommendation and justification, conclusions is made of the proposed system.
Blood On Web
11
SOFTWARE ENGINEERING PARADIGM
Blood On Web
12
4. SOFTWARE ENGINEERING PARADIGM

4.1Waterfall model
The simplest, oldest and most widely used process model for software designing is the waterfall model. It was proposed by Royce in 1970.The essence of this software paradigm is that the process of software designing consists of linear set of distinct phases. These phases are: Stage1: Feasibility Study The goal of feasibility study is to evaluate alternative systems and to purpose the most feasible and desirable system for designing. Five types of feasibility are addressed in this study. 1. Technical feasibility 2. Economic Feasibility 3. Motivational Feasibility 4. Schedule Feasibility 5. Operational Feasibility Stage2: Requirement Analysis and Specification The goal of this phase is to understand the exact requirements of the customers and to document them properly. This activity is usually executed together with the customers, as the goal is to document all functions, performance and interfacing requirements for the software designing and management. The requirements describe what of a system. This phase produces a large document containing a description of what the system will do without describing how it will be done. This document is known as software requirement specification (SRS) document.
Blood On Web
13
Stage3: Design The goal of this phase is to transform the requirement specification produced in the requirement analysis phase into a structure that is suitable for implementation in some programming language, Here, overall software architecture is defined, and the product design and detailed design work is performed. This work is documented and is known as software design description (SDD document). Stage4: Coding and Unit Testing The information contained in CMS is sufficient to begin the coding Phase. The coding Phase of software designing involves translation of design specification into a machine readable form. If design is performed in a detailed manner, code generation can be accomplished easily. This phase is also known as the implementation phase. Here, each component of the design is implemented as a program module, and each of these program modules is unit tested. The purpose of unit testing is to determine the correct working of individual modules. Stage5: Integration and System Testing: During this phase the different program modules are integrated in a planned way and then tested as a completed system to ensure that the designed system functions according to its requirements as specified in the SRS document. After testing, the software is delivered to the customer. Stage6: Software Maintenance This is the last phase of software designing which includes a broad set of activities such as error correction, enhancement of capabilities, deletion of obsolete capabilities and optimization.
Blood On Web
14
Advantages 1. Simple and easy to use. 2. 3. 4. Easily manageable. The phase of the model are processed and completed one at a time. Works very well for smaller software projects.
Disadvantages 1. It is often difficult for the customer to state all the requirements explicitly. 2. Real projects rarely follow the sequential flow that the software model proposes. 3. The customer must have patience, as the product is delivered very late in this software process.
Blood On Web
15
SOFTWARE REQUIREMENT SPECIFICATION
Blood On Web
16
5. SOFTWARE REQUIREMENT SPECIFICATION

A main purpose of software requirement specification is the clear definition and specification of functionality and of the software product. It allows the developer to be carried out, performance level to be obtained and corresponding interface to be established. This section lists out the requirement for developing a software project monitoring system.
5.1 Hardware Requirements

The selection of hardware is very important in the existence and proper working of any software. When select hardware, the size and capacity requirements are also important. Server Client
Processor: Pentium 4 Pentium 4 Processor Speed: 2.8 GHz 1 GHz RAM Capacity: 2GB 2GB Hard disk: Monitor: Key board: 120GB 40 GB
15SVGA 15SVGA 105 keys 105 keys
Mouse: Scroll Mouse Scroll Mouse
Blood On Web
17
5.2 Software Requirements

One of the most difficult task is selecting software for the system, once the system requirements is found out then we have to determine whether a particular software package fits for those system requirements. This section summarizes the application requirement.
Operating System: Windows Vista/2007
Front-End: C#.NET, ASP Back-End : MS SQL Server 2005 In the project Blood on web.NET Framework is used as front-end tool. .NET is one of the most beautiful and recently more popular front-end tools. C#.NET and ASP.NET are used in this project. An interface for users is build-using ASP.NET. SQL Server 2005 is used as the backend tool. Additional technologies used are Internet Information Services (IIS) and ADO.NET. Then it comes the turn of the Operating System. Any .NET framework compatible software platform can be used.
Introduction To .NET
Microsoft .NET is a software that connects information, people, systems and devices. It spans clients, servers and developers tools and consists of the .NET framework used for building and running all kinds of software including Web based application and smart client applications. Developers tools like Microsoft Visual Studio.NET 2008 provide an integrated development environment (IDE) for maximizing developer productivity with the .NET framework. C# programs run on the .NET Framework, an integral component of Windows that includes a virtual execution system called the common language runtime (CLR) and a
Blood On Web
18
unified set of class libraries. The CLR is Microsofts commercial implementation of the common language infrastructure (CLI), an international standard that is the basis for creating execution and the development environment in which languages and libraries work together seamlessly. Source code written in C# is compiled into an intermediate language (IL) that conforms to the CLI specification. The IL code, along with resources such as bitmaps and strings, is stored on disk in an executable file called an assembly, typically with an extension of .exe or .dll. An assembly contains a manifest that provides information on the assemblys types version, culture, and security requirements. When the C# program is executed, the assembly is loaded into the CLR, which might take various actions based on the information in the manifest. Then, if the security requirements are met, the CLR performs just in time (JIT) compilation to convert the IL code into native machine instructions. The CLR also provides other services related to automatic garbage collection, exception handling, and resource management .Code that is executed by the CLR is sometimes referred to as managed code, in contrast to unmanaged code which is compiled into native machine language that targets a specific system. The following diagram illustrate the compile-time and run time relationships of C# source code files, the base class libraries, assemblies and the CLR. 5.3 About C#.NET C#.net is a major component of Microsoft Visual Studio .NET suite. The .NET version of C# is a new improved version with more features and additions. Microsoft .NET is a programming and operating framework introduced by Microsoft. All .NET supported languages access common .NET library to develop applications and share common tools to execute applications. Programming with C# using .NET is called C#.NET. C# is an elegant and type-safe object-oriented language that enables developers to build a wide range of secure and robust applications that run on the .NET Framework. We can use C# to create traditional Windows client applications, XML Web services, distributed components, clientserver applications, database applications and much more. 5.4 Features of C#.NET Inheritance:
Blood On Web
19
Inheritance is one of the most used techniques in an object oriented language. Inheritance provides ability to use an existing classs functionality via its derived (inherited) class. Inheritance refers to the properties of a class being available to many other classes. The properties and methods of the base class are inherited and extracted by the derived classes. By default all the classes created with C#.NET are inheritable. The users can use inheritance to define new forms designed by users are really classes Exception Handling: Exception handling is an in build mechanism in .NET framework to detect and run time errors. The .NET Framework contains lots of standard exceptions. The exceptions re anomalies that occur during the exception of program. They can be because of, logic or system errors. If a user (programmer) does not provide a mechanism to handle these anomalies, the .NET run time environment provides a default mechanism, which terminates the program execution. i. Overloading: C#.NET supports methods overloading using the overloading Keyword. Using this keyword, you can declare same method names with different arguments. ii. Overriding: Overriding is the creation of a method in the subclass that the same signature, i.e. name, number and type of arguments, as method in the super class. This new method hides the method of super class. Derived classes inherit the methods defined in their base class. All methods are not overridable by default but if a method in the base class is marked with overridable keyword the Overrides keyword can be used in derived class to define new implementation of the inherited method. iii. Constructors and Destructors: The procedures that control initialization of new instances of a class are known as constructors. Conversely, destructors are methods that are used to free system resources when a class leaves scope or is set to nothing.C#.NET supports constructors and destructors using the Sub New and Sub Dispose procedures. Sub New method will only run once when a class is created. In addition to these basic object-oriented principles, C# facilities the development of software components through several innovative language constructs, including:
Blood On Web
20
Encapsulated method signatures called delegates, which enables type safe Properties, which serves as assessors for private member variables.
event notifications.
Attributes, which provide declarative metadata about types at run time. Name Spaces As you have seen earlier, most of the .NET types are defined in namespaces. A namespace is a scope in which managed types are defined. If you see .NET Framework Class Library, you will see hundreds of namespaces. For example, System namespaces contains types such as Console, Object and so on. If you want to access Console class, you need to import System namespaces in your application. A Namespace in Microsoft .Net is like containers of objects. They may contain unions, classes, structures, interfaces, enumerators and delegates. Main goal of using namespace in .Net is for creating a hierarchical organization of program. In this case a developer does not need to worry about the naming conflicts of classes, functions,
variables etc., inside a project. In Microsoft .Net, every program is created with a default namespace. This default namespace is called as global namespace. But the program itself can declare any number of namespaces, each of them with a unique name. The advantage is that every namespace can contain any number of classes, functions, variables and also namespaces etc., whose names are unique only inside the namespace. The members with the same name can be created in some other namespace without any compiler complaints from Microsoft .Net. 5.5 SQL Server 2005 A database is a collection of information thats related to a particular subject or purpose, such as tracking client orders or maintaining a list of project details. If the database isnt stored on a computer, or only part of it are one may be tracking information from a variety of sources that one is having to co-ordinate and organize himself using Microsoft SQL Server, one can manage all information from a single database file. Within the file, data is divided into separate storage containers called tables; view, add and update data by using online forms; find and retrieve just the data wanted for reports.
Blood On Web
21
SQL Server allows the user to view, update or analyze the database from the Internet of an intranet by creating data access pages. SQL Server as a relational database stores data in many related tables. A table is a collection of data about a specific topic such as projects or clients. Using a separate table for each topic means that, store that data only once. This makes the database more efficient and reduces data-entry errors.
Tables organize data into columns (called fields) and rows (called records). A common field relates two tables so that Microsoft SQL Server can bring together the data from the two tables for viewing, editing, or printing. In table Design view one can create an entire table from scratch or add, delete or customize the fields in an existing table. The user can also display records from tables that are related to the current table by displaying sub datasheets within the main datasheet. With some restrictions, the user can work with the data in sub datasheets in many of the same ways that they work with data in the main datasheet. In SQL Server a database is the overall container of data and associated with in a single SQL Server database. The user can have hundreds of tables, queries, forms, reports, macros and modules all stored in a single DOS files with the extension db. The data type in a database design defines the type of data contained in fields of the table and six of each value in the table. To store data, create one table for each type of information that is to be tracked. To bring the data from multiple tables together in a query, form, report, or data SQL Server page, define relationships between the tables. To fling and retrieve just the data that meets conditions specified, including data form multiple tables, create a query. SQL server 2005 has a number of tools to help the database administrator and the developer. The relational database engine has been improved to give better performance and support for both structured and un structured data.The replication services include services for distributed or mobile data processing applications. it provides for high system availability, scalable concurrency with secondary data stores, enterprise reporting solutions and integration with heterogenous system such as oracle databases.
Blood On Web
22
The deployment of scalable ,personalized timely information updates through webbased applications has been made possible with the advanced notification capabilities of the SQL server 2005.The data access protocols reduce the time taken for integrating data in SQL server with existing system. A number of development tools have been provided and integrated with Microsoft visual studio to provide an end to end applications development capability. the extraction ,transformation and load process has been further enhanced and online analytical processing render rapid , sophisticated analysis of large and complex data sets using multidimensional storage. The reporting services features have been honed up to create comprehensive solutions for managing, creating and delivering traditional and paper oriented reports or interactive, web based reports.
is easy It to use. It scales from a mobile laptop to systematic multiprocessor system. It provides data warehousing features.
Blood On Web
23
SYSTEM DESIGN
Blood On Web
24
6. SYSTEM DESIGN
Designing is the most important phase of software development. It requires a careful planning and thinking on the part of the system designer. Designing software means to plan how the various parts of the software are going to achieve the desired goal. It should be done with utmost care because if the phase contains any error then that will affect the performance of the system, as a result it may take more processing time, more response time, extra coding workload etc. Software design sits at the technical kernel of the software engineering process and is applied regardless of the software process model that is used. After the software requirements have been analyzed and specified, software design is the first of the three technical activities Designing, Coding and Testing that are required to build and verify the software. Each activity transforms information in such a manner that ultimately results in validated computer software.
6.1 Design goals

The following goals were kept in mind while designing the system: Make system user-friendly: This was necessary so that system could be used efficiently and system could act as catalyst in achieving objectives. Make system compatible: It should fit in the total integrated system. Future maintenance and enhancement must be less. Make the system reliable: understandable and cost-effective.
Blood On Web
25
6.2 Use Case Diagram

Blood on Web
User Registration Login Blood Bank Details
Donor Details Recipient Details Admin Refer friend Blood Collection Stock in Hospital Interesting Friends Feedback User
Blood On Web
26
6.3 Scenario
S1: User Registration: Admin and users can register user details for further usage of this application. S2: Login: Admin and users can login to their own home using their username and password. S3: Donor Details: Store the details of persons who wish to donate blood. S4: Send Feedback: Send feedback to admin. S5: Refer Friend: Users can refer their friends for blood donation. S6: Blood Bank details: Details about Blood Bank. S7: Recipient Details: Details of recipient. S8:
Blood On Web
27
Blood collection: Admin can select information about donor corresponding to the blood group.
6.4 Sequence Diagram

S1: User Registration
: User Registration User Req Reg form () Display reg form Submit ()
: User Controller
Blood On Web
28
S2: Login
: Login
: Login controller
: Admin home
: Donor details
User Req Login () Display login screen Username,pswd Success Failure Usertype=Admin
Usertype=User
Blood On Web
29
S3: Donor Details
: Donor Details
: Donor Controller
admin
Display donor reg form
Submit ()
Blood On Web
30
S4: Send Feedback
: Feedback
: Feedback Controller
admin
Add Feedback ()
Blood On Web
31
S5: Refer Friend

: Refer Friend : Refer Friend Controller
admin
Add Friend ()
Blood On Web
32
S6: Blood Bank Details
: Blood Bank
: Blood bank Controller
Add Friend () admin
Blood On Web
33
S7: Recepient Details

: Recepient Details : Recepient Controller
Add Friend () admin
Blood On Web
34
S8: Blood Collection

: Blood Collection : Donor Controller
Select Blood group () View Donor admin
Blood On Web
35
6.5 Class Diagram
Login
Admin 1 1
User 0..m
m Blood Bank Details Feedback
0..n
Donor Details
Friend
Blood On Web
36
6.6 Database Design

Software project monitoring system stores the data in a database. A database is a structured collection of data. To add, access, and process the data stored in database, one need a database management system such as SQL server. SQL is a relational database management system stores the data in separate tables.
Tables:
User Registration Bank Details Donor Details Recipient Details Feedback Refer Friend
User Registration
Field Name
id Name Age Gender Phone Email Place Username Password role
Type
Integer Varchar Integer Varchar Integer Varchar Varchar Varchar Varchar varchar 20 50 20 20 10 50 50 50 50 20
Size
Description
Id of user Name Age Gender Phone no: Email id Place Username Password Role
Key Specification
Primary key
Blood On Web
37
Blood Bank Details
Field Name
Name Id Type Location Phone email
Type
Varchar Integer Varchar Varchar Integer Varchar 50 20 50 50 10 50
Size
Description
Name Id of blood bank Type of hospital Location Phone no: Email id
Key Specification
Primary key
Donor Details
Field Name
Name Age Bloodgroup hospital Gender Weight Disabilities Location Phone email
Type
Varchar Integer Varchar Varchar Varchar Integer Varchar Varchar Integer Varchar 50 20 20 50 20 20 50 50 10 50
Size
Description
Name Age Bloodgroup hospital Gender Weight Disabilities Location Phone email
Key Specification
Primary key
Blood On Web
38
Recipient Details
Field Name
Blood group Select Sample Patient Name Disease gender Date number
Type
Varchar Varchar Varchar Varchar Varchar datetime Integer 20 20 50 50 20 30 10
Size
Description
Blood group Select Sample Patient Name Disease gender Date Phone number
Key Specification
Primary key
Feed back
Field Name
Name Phone feedback
Type
Varchar integer Varchar 50 10 100
Size
Description
Name Phone no: feedback
Key Specification
Refer Friend
Field Name
Name Gender Contact number place
Type
Varchar Varchar Integer Varchar 50 20 10 50
Size
Description
Name Gender Contact number place
Key Specification
Blood On Web
39
SYSTEM DEVELOPMENT
Blood On Web
40
7. SYSTEM DEVELOPMENT
System development is a series of operations performed to manipulate data to produce output from a computer system. This is highly dependent on the programming language used. During the system development phase, the system is constructed from the specifications prepared in the design phase. The principal activities performed during the development phase can be divided into two major related sequences. They are: 1. External system development 2. Internal system development The major external system development activities are: 1. Implementation 2. Planning 3. Equipment acquisition 4. Installation The major internal system development activities are: 1. Computer program development 2. Performance testing
Blood On Web
41
7.1 Code Design

The purpose of the code is to facilitate the identification and the retrieval of items of information. A code is an ordered collection of symbols designed to provide unique identification of an entity or an attribute. Codes are built with mutually exclusive features. Code in all cases specify objects physical or on performance characteristics. They are used to give operational distractions and other information.
Codes also show interrelationship among different items. Codes are used for identifying, accessing, sorting and matching records. The code ensures that only one value of code with a single meaning is correctly applied to give entity or attribute as described in various ways.
SYSTEM TESTING AND IMPLEMENTATION
Blood On Web
42
8. SYSTEM TESTING AND IMPLEMENTATION

Testing and implementation is the phase by which we implements what we design yet. If we have a well-defined design, coding is just a mechanical process. Just need to write the code for what we have already designed. Coding is the part where we program the main functionality of the system. As specified earlier, we starts by stored procedures through the other logic system and then goes to coding of the application Implementation is the stage where the theoretical design is turned into a working system. The implementation phase constructs install and operational the new system. The most crucial and very important stage of achieving a new successfully system for the users, which will work efficiently and effectively is the implementation stage. In general, software engineers distinguish software faults from software failures. In case of a failure, the software does not do what the user expects. A fault is a programming error that may or may not actually manifest as a failure. A fault can also be described as an error in the correctness of the semantic of a computer program. A fault will
Blood On Web
43
become a failure if the exact computation conditions are met, one of them being that the faulty portion of computer software executes on the CPU. A fault can also turn into a failure when the software is ported to a different hardware platform or a different compiler, or when the software gets extended. Software testing is the technical investigation of the product under test to provide stakeholders with quality related information. Software testing may be viewed as a sub-field of Software Quality Assurance but typically exists independently (and there may be no SQA areas in some companies). In SQA, software process specialists and auditors take a broader view on software and its development. They examine and change the software engineering process itself to reduce the amount of faults that end up in the code or deliver faster. Regardless of the methods used or level of formality involved the desired result of testing is a level of confidence in the software so that the organization is confident that the software has an acceptable defect rate. What constitutes an acceptable defect rate depends on the nature of the software. An arcade video game designed to simulate flying an airplane would presumably have a much higher tolerance for defects than software used to control an actual airliner. A problem with software testing is that the number of defects in a software product can be very large, and the number of configurations of the product larger still. Bugs that occur infrequently are difficult to find in testing. A rule of thumb is that a system that is expected to function without faults for a certain length of time must have already been tested for at least that length of time. This has severe consequences for projects to write long-lived reliable software. A common practice of software testing is that it is performed by an independent group of testers after the functionality is developed but before it is shipped to the customer. This practice often results in the testing phase being used as project buffer to compensate for project delays. Another practice is to start software testing at the same moment the project starts and it is a continuous process until the project finishes.
Blood On Web
44
Another common practice is for test suites to be developed during technical support escalation procedures. Such tests are then maintained in regression testing suites to ensure that future updates to the software don't repeat any of the known mistakes. In counterpoint, some emerging software disciplines such as extreme programming and the agile software development movement, adhere to a "test-driven software development" model. In this process unit tests are written first, by the programmers (often with pair programming in the extreme programming methodology). Of course these tests fail initially; as they are expected to. Then as code is written it passes incrementally larger portions of the test suites. The test suites are continuously updated as new failure conditions and corner cases are discovered, and they are integrated with any regression tests that are developed. Unit tests are maintained along with the rest of the software source code and generally integrated into the build process (with inherently interactive tests being relegated to a partially manual build acceptance process). The software, tools, samples of data input and output, and configurations are all referred to collectively as a test harness.
8.1 SYSTEM TESTING

The purpose of testing is to discover errors. Testing is the process of trying to discover every conceivable fault or weakness in a work product. It provides a way to check the functionality of components, sub assemblies, assemblies and/or a finished product It is the process of exercising software with the intent of ensuring that the Software system meets its requirements and user expectations and does not fail in an unacceptable manner. There are various types of test. Each test type addresses a specific testing requirement. 8.1.1 Functional test
Blood On Web
45
Functional tests provide systematic demonstrations that functions tested are available as specified by the business and technical requirements, system documentation, and user manuals. Functional testing is centered on the following items: Valid Input Invalid Input Functions Output : identified classes of valid input must be accepted. : identified classes of invalid input must be rejected. : identified functions must be exercised. : identified classes of application outputs must be exercised.
Systems/Procedures: interfacing systems or procedures must be invoked.
Organization and preparation of functional tests is focused on requirements, key functions, or special test cases. In addition, systematic coverage pertaining to identify Business process flows; data fields, predefined processes, and successive processes must be considered for testing. Before functional testing is complete, additional tests are identified and the effective value of current tests is determined. 8.1.2 System Test System testing ensures that the entire integrated software system meets requirements. It tests a configuration to ensure known and predictable results. An example of system testing is the configuration oriented system integration test. System testing is based on process descriptions and flows, emphasizing pre-driven process links and integration points. 8.2 TYPES OF TESTS 8.2.1 Unit testing Unit testing involves the design of test cases that validate that the internal program logic is functioning properly, and that program inputs produce valid outputs. All decision branches and internal code flow should be validated. It is the testing of individual
Blood On Web
46
software units of the application .it is done after the completion of an individual unit before integration. This is a structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform basic tests at component level and test a specific business process, application, and/or system configuration. Unit tests ensure that each unique path of a business process performs accurately to the documented specifications and contains clearly defined inputs and expected results. Unit testing is usually conducted as part of a combined code and unit test phase of the software lifecycle, although it is not uncommon for coding and unit testing to be conducted as two distinct phases.
Test strategy and approach Field testing will be performed manually and functional tests will be written in detail. Test objectives All field entries must work properly. Pages must be activated from the identified link. The entry screen, messages and responses must not be delayed. Features to be tested Verify that the entries are of the correct format No duplicate entries should be allowed All links should take the user to the correct page. 8.2.2 Integration testing Integration tests are designed to test integrated software components to determine if they actually run as one program. Testing is event driven and is more concerned with the basic outcome of screens or fields. Integration tests demonstrate that although the components were individually satisfaction, as shown by successfully unit
Blood On Web
47
testing, the combination of components is correct and consistent. Integration testing is specifically aimed at exposing the problems that arise from the combination of components. Software integration testing is the incremental integration testing of two or more integrated software components on a single platform to produce failures caused by interface defects. The task of the integration test is to check that components or software applications, e.g. components in a software system or one step up software applications at the company level interact without error. Test Results: All the test cases mentioned above passed successfully. No defects encountered.
8.2.3 White Box Testing White Box Testing is a testing in which in which the software tester has knowledge of the inner workings, structure and language of the software, or at least its purpose. It is purpose. It is used to test areas that cannot be reached from a black box level. Test Results: All the test cases mentioned above passed successfully. No defects encountered.
8.2.4 Black Box Testing Black Box Testing is testing the software without any knowledge of the inner workings, structure or language of the module being tested. Black box tests, as most other kinds of tests, must be written from a definitive source document, such as specification or requirements document, such as specification or requirements document. It is a testing in
Blood On Web
48
which the software under test is treated, as a black box .you cannot see into it. The test provides inputs and responds to outputs without considering how the software works. Test Results: All the test cases mentioned above passed successfully. No defects encountered.
8.2.5 Acceptance Testing User Acceptance Testing is a critical phase of any project and requires significant participation by the end user. It also ensures that the system meets the functional requirements. Test Results: All the test cases mentioned above passed successfully. No defects encountered.
A Sample Testing Cycle: Although testing varies between organizations, there is a cycle to testing: 1. Requirements Analysis: Testing should begin in the requirements phase of the software development life cycle. During the design phase, testers work with developers in determining what aspects of a design are testable and under what parameter those tests work. 1. Test Planning: Test Strategy, Test Plan(s), Test Bed creation. 2. Test Development: Test Procedures, Test Scenarios, Test Cases, and Test Scripts to use in testing software. 3. Test Execution: Testers execute the software based on the plans and tests and report any errors found to the development team.
Blood On Web
49
4. Test Reporting: Once testing is completed, testers generate metrics and make final reports on their test effort and whether or not the software tested is ready for release. 5. Retesting the Defects Not all errors or defects reported must be fixed by a software development team. Some may be caused by errors in configuring the test software to match the development or production environment. Some defects can be handled by a workaround in the production environment. Others might be deferred to future releases of the software, or the deficiency might be accepted by the business user. There are yet other defects that may be rejected by the development team (of course, with due reason) if they deem it inappropriate to be called a defect.
8.3 IMPLEMENTATION
Implementation is the stage of the project when the theoretical design is turned out into a working system. Thus it can be considered to be the most critical stage in achieving a successful new system and in giving the user, confidence that the new system will work and be effective. The implementation is the processing of converting a new or revised system into operational one. It is the key stage in. achieving a new successful system because; usually it involves lot of upheaval in the user department. System testing is an expensive but critical process that can take as much as 50% of the budget of the program development. Testing is the stage of implementation, which is aimed at ensuring that the works accurately and efficiently before live operation commences. It is the process of executing a program with the explicit intention of finding errors.
Blood On Web
50
The implementation includes all those activities that take place to connect from old system to new. The new system may be totally replacing the existing system or it may be automated some activities or it may be a major modification to an existing system The method of implementation and time scale to be adopted are found out initially. The proper implementation is essential to provide a reliable system to meet organization requirements. Successful implementation may not guaranty improvement in the organization using the new system, but improper installation will prevent it The implementation stage involves careful planning, investigation of the existing system and its constraints on implementation, designing of methods to achieve changeover and evaluation of changeover methods. Implementation of software refers to the final installation of the package in its real environment, to the satisfaction of the intended users and operation of the system. In many organizations someone who will not be operation it, will commission the software development Project. The people are not sure that the software is meant to make their job easier. In the initial stage, they doubt about the software but we have to ensure that resistance does build up as one has to makes sure that: The active user must be aware of the benefits of using the system. Their confidence in the software is built up. Proper guidance is imparted to the user so that he is comfortable in using the Application. The implementation phase of a project covers the period from the acceptance of the tested design to its satisfactory operations, supported by the appropriate user and operations manual. It is a major operation across the whole organizational structure and requires a great deal of planning. The implementation plan involves the following:
Blood On Web
51
SYSTEM MAINTENANCE
Blood On Web
52
9. SYSTEM MAINTENANCE
Software Development has many phases. These phases include Requirements Engineering, Architecting, Design, Implementation, Testing, Software Deployment, and Maintenance. Maintenance is the last stage of the software life cycle. After the product has been released, the maintenance phase keeps the software up to date with environment changes and changing user requirements. The earlier phases should be done so that the product is easily maintainable. The design phase should plan the structure in a way that can be easily altered. Similarly, the Software maintenance is the modification of a software product after delivery to correct faults, to improve performance or other attributes, or to adapt the product to a modified environment implementation phase should create code that can be easily read, understood, and changed. Maintenance can only happen efficiently if the earlier phases are done properly.
Blood On Web
53
There are four major problems that can slow down the maintenance process: unstructured code, maintenance programmers having insufficient knowledge of the system, documentation being absent, out of date, or at best insufficient, and software maintenance having a bad image. The success of the maintenance phase relies on these problems being fixed earlier in the life cycle.
Maintenance consists of four parts. Corrective maintenance deals with fixing bugs in the code. Adaptive maintenance deals with adapting the software to new environments. Perfective maintenance deals with updating the software according to changes in user requirements. Finally, preventive maintenance deals with updating documentation and making the software more maintainable. All changes to the system can be characterized by these four types of maintenance. Corrective maintenance is traditional maintenance while the other types are considered as software evolution. Maintenance is one of the important steps in the system development After the installation phase is completed and the user staff is adjusted to the changes created by the candidate system, evaluation and maintenance begins. The important of maintenance is to continue to bring the new system to standards. Maintenance can be classified as corrective, adaptive perceptive. Corrective maintenance means repairing, processing performance failure or making changes because previously uncorrected problems or false assumptions. Adaptive maintenance means enhancing the performance or modifying programs to respond to the users additional or changing needs. Maintenance covers a wide range of activities, including correcting coding and design errors, updating documentation and test data, and upgrading user support. Maintenance means restoring something to its original condition
Blood On Web
54
FUTURE ENHANCEMENT
Blood On Web
55
10. FUTURE ENHANCEMENT

The solution should give complete information about blood donors, and various activities of hospitals and blood banks regarding the blood donation.Donors are provided with registration process to maintain their information for future donations as well as to make their information available to search. Blood recipients can place order for blood. This system is totally targeted for immediate donation of blood.People can get registration by sitting at home. Department can collect information regarding various blood groups.Provides the stock of blood for various groups in the various blood banks.All the process of submission of registration form is quite simple. People can get registration by sitting at home. Department can collect information regarding various blood groups.This system also takes feedback for future enhancements.
Blood On Web
56
Blood On Web
57
CONCLUSION
11. CONCLUSION
Blood on Web is a software application to maintain day to day transactions in a blood bank. This software helps to register all the donors. The main objective of this application is to automate the complete operations of the blood bank. They need maintain hundreds of thousands of records. Also searching should be very faster so they can find required details instantly. This application is built such a way that it should suits for all type of blood banks in future. So every effort is taken to implement this project. This project is based on the recipients and donors and also the valuable words Give blood Save Life . This application is built in such a way that it should suits for all types of blood banks in future. So every effort is taken to implement this project. Successful implementation of this project will help so many peoples who are seeking for blood.
Blood On Web
58
APPENDIX
Blood On Web
59
12. Appendix
Home page
Blood On Web
60
User Registration
Blood On Web
61
Blood bank Details
Blood On Web
62
Donor Details
Blood On Web
63
Send Feedback
Blood On Web
64
Refer Friend
Blood On Web
65
Recipient Details
Blood On Web
66
Blood Collection Details
Blood On Web
67
Stock in Hospital
Blood On Web
68
Interesting Friends
Blood On Web
69
View Feedback
Blood On Web
70
Search Details
Blood On Web
71
Contact Us
Blood On Web
72
Blood On Web
73
BIBLIOGRAPHY
Blood On Web
74
13.BIBLIOGRAPHY
Websites http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visualcsharp-express [2] [3] [4] [5] Books http://www.msdn.microsoft.com http://www.ebookers.com http://en.wikipedia.org/wiki/Microsoft_SQL_Server http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express
[1] [2] [3] [4]
C# Progamming Language, Anders Hejlsberg, 4th Edition, year C# for programmers, Harvey M. Deitel, Paul J. Deitel. Programming Microsoft SQL Server 2005,Andrew Brust and Stephen Forte. Beginning Visual C# 2005,Karli Watson, Christian Nagel, Jacob Hammer Pedersen, Jon D. Reid, Morgan Skinner, Eric Whit,2005.
[5]
Beginning SQL Server 2005 Programming,Robert Vieira,2006.

ANILANEELAK

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ANILANEELAK

Încărcat de

Drepturi de autor:

Formate disponibile

Blood On Web

Dept .of Computer Applications

AWH Engineering College

Dept .of Computer Applications

AWH Engineering College

Dept .of Computer Applications

AWH Engineering College

Dept .of Computer Applications

AWH Engineering College

Dept .of Computer Applications

AWH Engineering College

2.1 Existing system

2.2 Proposed system

Dept .of Computer Applications

AWH Engineering College

Dept .of Computer Applications

AWH Engineering College

3.1 Technical feasibility

Dept .of Computer Applications

AWH Engineering College

3.2 Economic feasibility

Dept .of Computer Applications

AWH Engineering College

3.3 Operational feasibility

Dept .of Computer Applications

AWH Engineering College

SOFTWARE ENGINEERING PARADIGM

Dept .of Computer Applications

AWH Engineering College

4. SOFTWARE ENGINEERING PARADIGM

Dept .of Computer Applications

AWH Engineering College

Dept .of Computer Applications

AWH Engineering College

Dept .of Computer Applications

AWH Engineering College

SOFTWARE REQUIREMENT SPECIFICATION

Dept .of Computer Applications

AWH Engineering College

5. SOFTWARE REQUIREMENT SPECIFICATION

5.1 Hardware Requirements

15SVGA 15SVGA 105 keys 105 keys

Mouse: Scroll Mouse Scroll Mouse

Dept .of Computer Applications

AWH Engineering College

5.2 Software Requirements

Operating System: Windows Vista/2007

Dept .of Computer Applications

AWH Engineering College

Dept .of Computer Applications

AWH Engineering College

Dept .of Computer Applications

AWH Engineering College

Dept .of Computer Applications

AWH Engineering College

Dept .of Computer Applications

AWH Engineering College

Dept .of Computer Applications

AWH Engineering College

Dept .of Computer Applications

AWH Engineering College

6.1 Design goals

Dept .of Computer Applications