The document provides details about a proposed blood bank management system project including objectives, platforms, technologies used, timelines, functions, hardware/software specifications, data flow, entity relationship and UML diagrams. The system will allow administrators to manage blood banks, donors, patient requests and inquiries online. It will be a web application developed using ASP.NET, C# and SQL Server over 50 days. Key features include donor registration, blood donation, patient requests, blood bank management and location-based search.
This document outlines a database project for a blood bank management system. It includes sections on the project proposal, requirements, scope, architecture, data flow diagram, use case diagram, system sequence diagram, class diagram, entity relationship diagram, hardware and software specifications, tools and technologies used, screenshots of tables with sample data, and examples of select, update, delete and insert queries. The overall goal is to develop software to manage the daily operations of a blood bank such as registering donors, collecting and distributing blood, and generating various reports.
This chapter will help you to demonstrate the working of the online blood bank system with the help of the diagrams, it includes DFD's ,architecture,block diagrams,ER-diagrams and state transition,table structure Etc.
Blood Bank System Peroject (website) Full Document DAV.PG COLLAGE
This document appears to be a project report submitted for a Bachelor of Science degree in IT. It includes sections like the declaration, acknowledgements, abstract, and index. The project involves developing a blood bank management system website. The report discusses the various modules of the system like admin, donor registration and search, blood cells, and blood stock. It also includes system flow diagrams, screenshots and discusses the coding used to develop the website.
Blood Bank Management Information System [Web-Url: http://infobloodbank.somee...Showrav Mazumder
Software development project presentation on Blood Bank Management Information System. It was my first own project with asp.net.
Web-Url: http://infobloodbank.somee.com/
The document describes a blood bank management system project created by Rohit, Rakesh and Chirag and guided by Prof. Channabasava. The project aims to automate the operations of a blood bank by developing software to register donors, track blood collection and distribution, and generate reports. The existing manual system is time-consuming and error-prone. The new system will make the blood bank's procedures faster, more accurate and help address issues like scarcity of rare blood groups and availability of blood during emergencies.
The document proposes an Online Blood Bank Management System to address limitations of a manual system. The proposed system has 3 modules - Admin, Donors, and Acceptors - to store and manage donor and acceptor details and blood group information. It allows users to login, update profiles, find blood groups, and address blood donation and needs. The system is intended to make management of donor/acceptor databases and scheduling less error-prone by automating the process.
Use Case, Activity, Sequence, Class Diagram of Blood Bank Management System.
Poster Design of Blood Bank Management System.
By- CSE Students of East West University
This is a presentation of a software project on Online Blood Banking System. It contain the objective of the project, about blood donation, how our website will look like and about the modules.
This document outlines a database project for a blood bank management system. It includes sections on the project proposal, requirements, scope, architecture, data flow diagram, use case diagram, system sequence diagram, class diagram, entity relationship diagram, hardware and software specifications, tools and technologies used, screenshots of tables with sample data, and examples of select, update, delete and insert queries. The overall goal is to develop software to manage the daily operations of a blood bank such as registering donors, collecting and distributing blood, and generating various reports.
This chapter will help you to demonstrate the working of the online blood bank system with the help of the diagrams, it includes DFD's ,architecture,block diagrams,ER-diagrams and state transition,table structure Etc.
Blood Bank System Peroject (website) Full Document DAV.PG COLLAGE
This document appears to be a project report submitted for a Bachelor of Science degree in IT. It includes sections like the declaration, acknowledgements, abstract, and index. The project involves developing a blood bank management system website. The report discusses the various modules of the system like admin, donor registration and search, blood cells, and blood stock. It also includes system flow diagrams, screenshots and discusses the coding used to develop the website.
Blood Bank Management Information System [Web-Url: http://infobloodbank.somee...Showrav Mazumder
Software development project presentation on Blood Bank Management Information System. It was my first own project with asp.net.
Web-Url: http://infobloodbank.somee.com/
The document describes a blood bank management system project created by Rohit, Rakesh and Chirag and guided by Prof. Channabasava. The project aims to automate the operations of a blood bank by developing software to register donors, track blood collection and distribution, and generate reports. The existing manual system is time-consuming and error-prone. The new system will make the blood bank's procedures faster, more accurate and help address issues like scarcity of rare blood groups and availability of blood during emergencies.
The document proposes an Online Blood Bank Management System to address limitations of a manual system. The proposed system has 3 modules - Admin, Donors, and Acceptors - to store and manage donor and acceptor details and blood group information. It allows users to login, update profiles, find blood groups, and address blood donation and needs. The system is intended to make management of donor/acceptor databases and scheduling less error-prone by automating the process.
Use Case, Activity, Sequence, Class Diagram of Blood Bank Management System.
Poster Design of Blood Bank Management System.
By- CSE Students of East West University
This is a presentation of a software project on Online Blood Banking System. It contain the objective of the project, about blood donation, how our website will look like and about the modules.
The document discusses the development of a blood management information system to assist in managing blood donor records and distributing blood supplies based on hospital demands. It aims to provide quick access to donor records, enable monitoring of donation activities, and generate timely reports to facilitate planning and decision making. The system was designed to address challenges with the previous paper-based system, such as delays in accessing records, data errors, and lack of security and confidentiality of medical information. It analyzes requirements for the new electronic system and compares other blood donor management systems to identify successes and limitations.
This document describes a blood bank management system with four main modules: administration, donor, receiver, and activities. The system is designed to gather blood from various sources, distribute it to hospitals and those in need, and manage the database. It allows users to track donor details, blood collection, screening, component preparation, storage, requests, compatibility testing, issue blood, and generate monthly statistics. The system provides functionality to efficiently manage all processes within the blood bank.
This document describes a blood bank management system that was created using Microsoft Access for the database and Visual Studio .NET for the interfaces. The system allows users to maintain donor details, blood component stock, screening details, compatibility testing, and blood requests and issues. It also provides monthly statistical reports on blood collection, blood groups, and RBC analysis. The objective is to efficiently manage all aspects of the blood bank's operations through this centralized computer system.
ER diagrams for blood bank management systemSoham Nanekar
It contains information for the blood bank management system,it's scope, requirements specification.
It also contains ER digram,use case diagram,class digram, sequence digram, collaboration digram, activity digram ,state chart digram, component digram and deployment digram for blood bank management system.
SRS on Online Blood Bank Managment system... GCWUF
This document outlines the requirements for an online blood bank management system. The system will allow administrators to register blood donors and enter new blood details. It will track blood stock levels and facilitate blood sales and purchases. The system aims to automate the tracking of blood products from initial ordering through administration and updates to medical records. It will support routine transfusions as well as special cases and emergencies. The system requirements include specifications for hardware, software, databases, and functional modules for administrators, donors and acceptors.
The purpose of the Blood Bank Management System is to simplify and automate the process of searching for blood in case of emergency and maintain the records of blood donors, recipients, blood donation programs and blood stocks in the bank.
The document describes a proposed blood bank management system with the following key points:
1. The system would automate the process of ordering, collecting, cross-matching, and administering blood transfusions as well as updating patient records.
2. It would allow donors to search for and match with recipients in need of blood and make donation requests.
3. The intended users are donors, recipients, hospitals, blood banks, and the public who can view donation events and requests.
This document provides an overview of a blood bank management system project. It includes a project brief outlining the goals of automating blood bank operations and making the system paperless, accurate, and tamper-proof. It then lists the various data structures that will be used like structures, linked lists, trees, arrays, stacks, and graphs. The document also provides an initial list of programs developed and to be developed for different modules. It identifies some complex parts of the program like setting structure links between different object types and creating objects with multiple linked lists. Finally, it provides some website references for blood bank information.
Blood Bank Management System Project ProposalAzmeen Gadit
This document proposes a blood bank management system project that will allow blood banks to store, process, retrieve, and analyze donor and recipient information. The project aims to help blood banks manage their operations more effectively by keeping records of blood type availability and donor/recipient details. It will use a MySQL database to store blood and user data and provide functions like searching for blood based on various criteria, managing online records of blood stock and donors, and tracking all blood group and donation information. The project intends to utilize resources efficiently, satisfy user requirements, and be delivered on schedule and budget.
This project presentation summarizes a blood bank management system that was developed. The system aims to bridge the gap between blood banks, hospitals, donors and patients. It allows for easy searching of donors with rare blood types. The presentation includes the objective, technologies used which include HTML, CSS, PHP and MySQL. It also includes diagrams like the use case diagram, activity diagram, sequence diagram and ER diagram. The presentation demonstrates the implementation of the system and provides a comparison. It is intended to reduce data entry and allow effective communication between blood banks and donors.
The document outlines the need for a systematic blood donor management system to address current issues like being time consuming, error prone, and lacking donor information. It proposes a new online system that would allow anyone to access donor data anytime from anywhere for quick searching. The system would have three user types - administrators who manage the donor database, donors who can update their own profiles, and acceptors who can search for donors. It would use tools like HTML, CSS, JavaScript, PHP and a MySQL database. The system aims to optimize time, costs and better serve volunteers and emergencies.
Our blood bank database system consists of attributes related to blood banks, donors, recipients, and blood inventory. It includes tables to store this data, an ER diagram depicting the relationships between tables, and SQL queries to interact with and analyze the data. The system aims to simplify the process of matching blood donors and recipients, maintain accurate records, and alert staff about low blood supplies. It provides a centralized platform to help connect donors, hospitals, and blood banks.
The document describes a blood bank management system project created by Rohit, Rakesh and Chirag and guided by Prof. Channabasava. The project aims to automate the operations of a blood bank by developing software to register donors, track blood collection and distribution, and generate reports. The existing manual system is time-consuming and error-prone. The new system will make the blood bank's procedures faster, more accurate and help address issues like scarcity of rare blood groups and availability of blood during emergencies.
Project proposal presentation(blood bank management system)Ikhtiar Khan Sohan
The document describes a proposed Blood Bank Management System (BBMS) that would allow blood banks to advertise blood donation events, track donor and blood stock records, and allow the public to make online donations and requests. The system would keep records of donors, recipients, blood donation programs, and rejected bloods. It would also alert staff when blood quantities are low or expired. The goals are to improve efficiency, allow publicizing of events and searches for donors, and provide efficient donor and stock management through a centralized database.
To build a solution to the ever growing requirement of blood due to accidents and various health problems the system is developed for accessing the information about various blood banks and hospitals and their blood stock. Providing information of donor.
Page 3 Software Requirements Specification Blood donation
1.0 Introduction
1.1 Purpose:
The web based blood donation system is mainly uses for helping the patient who need blood. So this SRS document consists of a simple explanation about the system and its features. The document mainly focuses on providing sufficient design information to the blood donor authorities. And also it will satisfy the functional, design, performance requirements of the system in briefly.
1.2 Objective:
This system presents an alert system to the donor about requirement of their blood to a person need and also provide online status of blood group wise availability of blood unit.
Page 4 Software Requirements Specification Blood donation
2.0 Problem Definition of Existing system
Entering the details about the blood groups, members, addresses etc. And tracking the database is complicated when the details are maintained manually. This makes the maintenance of schedule erroneous. Limitation of manual system. It is time consuming. Retrieval of data takes lots of time. It lacks of data security. Reports takes time to produce. Percentage of accuracy is less.
3.0 Proposed System
This system is used for maintain whole information about blood. In this project mainly 3 modules are there:
Admin
Donor
User
Page 5 Software Requirements Specification Blood donation
4.0 Software Requirements Specification
4.1 Software Requirement:
Operating System : Windows Xp, Windows 7/8/10
Front End : Codeigniter 3.1.4
Back End : MySql
Technology : Xampp
4.2 Hardware Requirement:
Processor : Amd A6-44006 Apu
Hard Disk : 2.75GHz
Memory : 6.0GB RAM
Page 6 Software Requirements Specification Blood donation
Data Flow Diagram:
Figure -1
Page 7 Software Requirements Specification Blood donation
Use Case Diagram
Figure-2: Admin and donor
Page 8 Software Requirements Specification Blood donation
Class Diagram
Figure-3
Page 9 Software Requirements Specification Blood donation
E-R Diagram
Figure-4
Page 10 Software Requirements Specification Blood donation
User interface diagram
Figure 5:The admin or donor login
Figure 6:The user registration
This document provides an overview of a blood bank management system project. It includes sections on the project profile, existing system limitations, need for a new system, functional specifications, hardware and software requirements, system flow chart, timeline chart, entity relationship diagram, use case diagram, activity diagrams, class diagram, sequence diagram, collaboration diagram, and input design. The key aspects summarized are that the project involves developing a web application for online blood bank management, the system will allow administrators, donors, and patients to manage blood bank information and requests, and technical specifications and design diagrams are provided.
This document provides a software requirements specification for an online blood bank management system. The key objectives of the system are to automate the tracking of blood products from initial ordering through administration and updating of patient records. This includes routines for blood transfusions, special requests, emergencies, and returned/unused blood units. The system aims to address limitations of a manual process such as time consumption, errors, lack of data security and report generation time. It specifies requirements for features, users, interfaces, functionality, capacity, security and more to support effective management of blood donation, procurement, storage and transfusion.
The document discusses the development of a blood management information system to assist in managing blood donor records and distributing blood supplies based on hospital demands. It aims to provide quick access to donor records, enable monitoring of donation activities, and generate timely reports to facilitate planning and decision making. The system was designed to address challenges with the previous paper-based system, such as delays in accessing records, data errors, and lack of security and confidentiality of medical information. It analyzes requirements for the new electronic system and compares other blood donor management systems to identify successes and limitations.
This document describes a blood bank management system with four main modules: administration, donor, receiver, and activities. The system is designed to gather blood from various sources, distribute it to hospitals and those in need, and manage the database. It allows users to track donor details, blood collection, screening, component preparation, storage, requests, compatibility testing, issue blood, and generate monthly statistics. The system provides functionality to efficiently manage all processes within the blood bank.
This document describes a blood bank management system that was created using Microsoft Access for the database and Visual Studio .NET for the interfaces. The system allows users to maintain donor details, blood component stock, screening details, compatibility testing, and blood requests and issues. It also provides monthly statistical reports on blood collection, blood groups, and RBC analysis. The objective is to efficiently manage all aspects of the blood bank's operations through this centralized computer system.
ER diagrams for blood bank management systemSoham Nanekar
It contains information for the blood bank management system,it's scope, requirements specification.
It also contains ER digram,use case diagram,class digram, sequence digram, collaboration digram, activity digram ,state chart digram, component digram and deployment digram for blood bank management system.
SRS on Online Blood Bank Managment system... GCWUF
This document outlines the requirements for an online blood bank management system. The system will allow administrators to register blood donors and enter new blood details. It will track blood stock levels and facilitate blood sales and purchases. The system aims to automate the tracking of blood products from initial ordering through administration and updates to medical records. It will support routine transfusions as well as special cases and emergencies. The system requirements include specifications for hardware, software, databases, and functional modules for administrators, donors and acceptors.
The purpose of the Blood Bank Management System is to simplify and automate the process of searching for blood in case of emergency and maintain the records of blood donors, recipients, blood donation programs and blood stocks in the bank.
The document describes a proposed blood bank management system with the following key points:
1. The system would automate the process of ordering, collecting, cross-matching, and administering blood transfusions as well as updating patient records.
2. It would allow donors to search for and match with recipients in need of blood and make donation requests.
3. The intended users are donors, recipients, hospitals, blood banks, and the public who can view donation events and requests.
This document provides an overview of a blood bank management system project. It includes a project brief outlining the goals of automating blood bank operations and making the system paperless, accurate, and tamper-proof. It then lists the various data structures that will be used like structures, linked lists, trees, arrays, stacks, and graphs. The document also provides an initial list of programs developed and to be developed for different modules. It identifies some complex parts of the program like setting structure links between different object types and creating objects with multiple linked lists. Finally, it provides some website references for blood bank information.
Blood Bank Management System Project ProposalAzmeen Gadit
This document proposes a blood bank management system project that will allow blood banks to store, process, retrieve, and analyze donor and recipient information. The project aims to help blood banks manage their operations more effectively by keeping records of blood type availability and donor/recipient details. It will use a MySQL database to store blood and user data and provide functions like searching for blood based on various criteria, managing online records of blood stock and donors, and tracking all blood group and donation information. The project intends to utilize resources efficiently, satisfy user requirements, and be delivered on schedule and budget.
This project presentation summarizes a blood bank management system that was developed. The system aims to bridge the gap between blood banks, hospitals, donors and patients. It allows for easy searching of donors with rare blood types. The presentation includes the objective, technologies used which include HTML, CSS, PHP and MySQL. It also includes diagrams like the use case diagram, activity diagram, sequence diagram and ER diagram. The presentation demonstrates the implementation of the system and provides a comparison. It is intended to reduce data entry and allow effective communication between blood banks and donors.
The document outlines the need for a systematic blood donor management system to address current issues like being time consuming, error prone, and lacking donor information. It proposes a new online system that would allow anyone to access donor data anytime from anywhere for quick searching. The system would have three user types - administrators who manage the donor database, donors who can update their own profiles, and acceptors who can search for donors. It would use tools like HTML, CSS, JavaScript, PHP and a MySQL database. The system aims to optimize time, costs and better serve volunteers and emergencies.
Our blood bank database system consists of attributes related to blood banks, donors, recipients, and blood inventory. It includes tables to store this data, an ER diagram depicting the relationships between tables, and SQL queries to interact with and analyze the data. The system aims to simplify the process of matching blood donors and recipients, maintain accurate records, and alert staff about low blood supplies. It provides a centralized platform to help connect donors, hospitals, and blood banks.
The document describes a blood bank management system project created by Rohit, Rakesh and Chirag and guided by Prof. Channabasava. The project aims to automate the operations of a blood bank by developing software to register donors, track blood collection and distribution, and generate reports. The existing manual system is time-consuming and error-prone. The new system will make the blood bank's procedures faster, more accurate and help address issues like scarcity of rare blood groups and availability of blood during emergencies.
Project proposal presentation(blood bank management system)Ikhtiar Khan Sohan
The document describes a proposed Blood Bank Management System (BBMS) that would allow blood banks to advertise blood donation events, track donor and blood stock records, and allow the public to make online donations and requests. The system would keep records of donors, recipients, blood donation programs, and rejected bloods. It would also alert staff when blood quantities are low or expired. The goals are to improve efficiency, allow publicizing of events and searches for donors, and provide efficient donor and stock management through a centralized database.
To build a solution to the ever growing requirement of blood due to accidents and various health problems the system is developed for accessing the information about various blood banks and hospitals and their blood stock. Providing information of donor.
Page 3 Software Requirements Specification Blood donation
1.0 Introduction
1.1 Purpose:
The web based blood donation system is mainly uses for helping the patient who need blood. So this SRS document consists of a simple explanation about the system and its features. The document mainly focuses on providing sufficient design information to the blood donor authorities. And also it will satisfy the functional, design, performance requirements of the system in briefly.
1.2 Objective:
This system presents an alert system to the donor about requirement of their blood to a person need and also provide online status of blood group wise availability of blood unit.
Page 4 Software Requirements Specification Blood donation
2.0 Problem Definition of Existing system
Entering the details about the blood groups, members, addresses etc. And tracking the database is complicated when the details are maintained manually. This makes the maintenance of schedule erroneous. Limitation of manual system. It is time consuming. Retrieval of data takes lots of time. It lacks of data security. Reports takes time to produce. Percentage of accuracy is less.
3.0 Proposed System
This system is used for maintain whole information about blood. In this project mainly 3 modules are there:
Admin
Donor
User
Page 5 Software Requirements Specification Blood donation
4.0 Software Requirements Specification
4.1 Software Requirement:
Operating System : Windows Xp, Windows 7/8/10
Front End : Codeigniter 3.1.4
Back End : MySql
Technology : Xampp
4.2 Hardware Requirement:
Processor : Amd A6-44006 Apu
Hard Disk : 2.75GHz
Memory : 6.0GB RAM
Page 6 Software Requirements Specification Blood donation
Data Flow Diagram:
Figure -1
Page 7 Software Requirements Specification Blood donation
Use Case Diagram
Figure-2: Admin and donor
Page 8 Software Requirements Specification Blood donation
Class Diagram
Figure-3
Page 9 Software Requirements Specification Blood donation
E-R Diagram
Figure-4
Page 10 Software Requirements Specification Blood donation
User interface diagram
Figure 5:The admin or donor login
Figure 6:The user registration
This document provides an overview of a blood bank management system project. It includes sections on the project profile, existing system limitations, need for a new system, functional specifications, hardware and software requirements, system flow chart, timeline chart, entity relationship diagram, use case diagram, activity diagrams, class diagram, sequence diagram, collaboration diagram, and input design. The key aspects summarized are that the project involves developing a web application for online blood bank management, the system will allow administrators, donors, and patients to manage blood bank information and requests, and technical specifications and design diagrams are provided.
This document provides a software requirements specification for an online blood bank management system. The key objectives of the system are to automate the tracking of blood products from initial ordering through administration and updating of patient records. This includes routines for blood transfusions, special requests, emergencies, and returned/unused blood units. The system aims to address limitations of a manual process such as time consumption, errors, lack of data security and report generation time. It specifies requirements for features, users, interfaces, functionality, capacity, security and more to support effective management of blood donation, procurement, storage and transfusion.
This document describes a blood bank management system created by Shweta Rathod, Radheahyam Sorte, and Tejaswini Rathod. The system aims to automate the manual processes of a blood bank to make operations more accurate, fast, and precise. It will register donors, track blood collection and distribution, and generate reports to help meet hospitals' blood needs and address shortages of rare blood groups. Currently, the blood bank's manual system is time-consuming, error-prone, and difficult to maintain accurate records and stock levels.
The document summarizes a proposed blood donation management system with the following key points:
1. The system allows users to register as blood donors, send requests for needed blood types, and search for donors by blood type. Donors can manage their donation history and view requests.
2. The existing systems lack features like online blood requests and integrated donor searching. The proposed system addresses these issues and allows for improved information sharing between blood banks.
3. The system has modules for users, donors, and administrators to manage donations, requests, profiles, and the overall system. Screenshots demonstrate sample outputs of the modules.
This document describes a web based claim processing system project. It provides details on the project such as the developers, technologies used, modules, use case and activity diagrams, database structure, input and output screens, limitations, and proposed enhancements. The system allows clients to file and check status of claims online, and the claims processing department to manage claims. It uses C# and ASP.NET for the front end and SQL Server as the backend database.
This document describes a blood bank management system created using Microsoft Access and Visual Studio.NET. It allows users to maintain donor details, blood component stock, screening details, compatibility testing, and monthly statistics. The system includes interfaces to insert, search, update, delete, and view details for donors, blood collection, screening, component preparation, storage, requests, issue, and returns. It also generates reports on blood collection, groups, and component analysis. The goal is to properly manage donor information, stock, and compatibility testing to issue safe and compatible blood components. Future work may include linking the system online, adding statistical graphs and backups, and changing the database.
The document presents an E-Hospital Management System project that was developed to digitize hospital operations and management. The key features of the system include online doctor and patient registration, computerized billing in the pharmacy, and storing all user details and medical records in a database. The system aims to reduce paperwork, improve efficiency over the manual process, and increase security and access to health records. It uses Java and related technologies and was implemented across main modules for administration, doctors, patients, and the pharmacy. Sample outputs demonstrate functionality like online registration, doctor scheduling, medical records, and bill generation.
This document outlines a proposed web portal for a blood donor database. The portal would allow users to search for blood donors and access information about blood donation organizations. It would provide secure registration and profile management for donors, volunteers, recipients and administrators. The system would display up-to-date blood stock details for hospitals and blood banks and allow online requests and fulfillment of blood units. It would also accept feedback and suggestions from users.
This document summarizes a management system created for Satyanarayan Ice Cream Parlour. The system was created to help with billing, accounting, and inventory management. It allows users to track customer and supplier information, generate reports, and maintain accurate financial records. The system was built using Visual Basic 6.0 and an Oracle database to provide a user-friendly interface for efficient parlour operations.
This document describes a proposed mobile application called the Information System for Donors and Acceptors. The application aims to connect blood donors and those needing donations. It allows users to view registered donor profiles, blood group availability, and register to donate. The main objectives are to speed up the donor search process and decrease deaths from a lack of available blood. Currently, donor information is managed manually which is time-consuming and error-prone. The proposed system would offer faster donor matching and ensure data accuracy. It would have modules for donors, acceptors, and admins to manage reports. The technical architecture involves Java, Firebase database, and adheres to requirements for usability, security, and portability. User stories, sequence diagrams
Build a centralized Blood bank management system. Registered for a developer edition, created an app using all custom objects, workflow rules, validations, Master-detail relationships and lookup relationships. To facilitate the process used different
email templates, tasks. Uploaded randomly generated data to all the fields and generated reports, dashboards and insights for analysis
The document describes a blood bank management system that allows users to manage blood stock details, blood sales and purchases. It tracks blood products from initial ordering through administration and updates patient records. The system allows administrators to register and manage donor details, send donation requests to donors, and send blood test results to doctors. It also has requirements for user login/authentication, password changes, and ensuring system performance, security, capacity and business continuity.
This document discusses using event streams as the system of record for data, rather than traditional databases. It argues that streams can serve as the single source of truth for data, providing benefits like data lineage, auditing, and integrity. It also describes how healthcare company Liaison uses a streaming platform from MapR to power their data integration platform, gaining the advantages of streams while meeting various compliance requirements.
This document describes an online blood bank system created by students at Savitribai Phule Pune University. The system aims to develop an online platform to maintain information about blood donors, recipients, and donation camps. It allows users to create, update, and delete donor and recipient profiles. The system was built using tools like PHP and MySQL on a Dell laptop. It includes modules for login, admin access, donor registration, user access, and FAQs. Screenshots show interfaces for the home page, contact/about pages, registration, donation lists, employee lists, campaigns and more. Future work could expand functionality based on blood bank feedback.
The document discusses customer query resolution and prospect tracking systems implemented by Newgen for Sahara Life Insurance, HSBC Bank, and FIC Banks.
It provides an overview of the key features of each system, including interfaces for customer and prospect search, logging new queries and prospects, viewing query and activity histories, and routing items to the appropriate teams for resolution. Workflow automation is highlighted for tracking internal bank processes more efficiently.
The document outlines requirements for an online banking system. It includes sections on system analysis, software requirements, system design, and modules. The key modules are login, account creation, deposit, withdrawal, money transfer, and loan application. The system aims to provide 24/7 secure access to banking services through a web-based interface for users. It is designed to reduce costs and improve efficiency over present manual systems.
Fusion Blood Bank Management System ImplementationAnish Sojan
The document describes the implementation of a centralized blood bank management system using Salesforce. It outlines the key objects used like Donor Details, Recipient Details, Employee Details, and Inventories. It then describes the user interfaces developed for donor registration, recipient requests, and employee management. It also discusses validations, workflows, and reports created to analyze data on donors, inventory levels, employees and revenue. The system aims to centralize data storage and allow analytics to improve operations.
Blood bank system
Blood Bank Management System (BBMS) is a web based system that can assists the information of blood bag during its handling in the blood bank. With this system, the user of this system can key in the result of blood test that has been conducted to each of the blood bag received by the blood bank.
This document provides an overview and description of a proposed online blood bank management system. The system aims to address issues with the current manual blood bank system, such as a lack of available blood types when needed. The proposed system would allow online registration of blood donors and organizations, requests for blood, and management of donor and medical history information. It would be developed using technologies like ASP.NET, SQL Server, and a client-server architecture to provide distributed access. Conducting a feasibility study is discussed to evaluate the technical, operational, and economic viability of the new system.
Online Credit Society is “public prosperity” by offering financial services to all groups of people and offering equal opportunity to all. Online Banking Society is an online banking through which the customer can know about different schemes for the welfare of the self and family.
Literature Review Basics and Understanding Reference Management.pptxDr Ramhari Poudyal
Three-day training on academic research focuses on analytical tools at United Technical College, supported by the University Grant Commission, Nepal. 24-26 May 2024
Presentation of IEEE Slovenia CIS (Computational Intelligence Society) Chapte...University of Maribor
Slides from talk presenting:
Aleš Zamuda: Presentation of IEEE Slovenia CIS (Computational Intelligence Society) Chapter and Networking.
Presentation at IcETRAN 2024 session:
"Inter-Society Networking Panel GRSS/MTT-S/CIS
Panel Session: Promoting Connection and Cooperation"
IEEE Slovenia GRSS
IEEE Serbia and Montenegro MTT-S
IEEE Slovenia CIS
11TH INTERNATIONAL CONFERENCE ON ELECTRICAL, ELECTRONIC AND COMPUTING ENGINEERING
3-6 June 2024, Niš, Serbia
Advanced control scheme of doubly fed induction generator for wind turbine us...IJECEIAES
This paper describes a speed control device for generating electrical energy on an electricity network based on the doubly fed induction generator (DFIG) used for wind power conversion systems. At first, a double-fed induction generator model was constructed. A control law is formulated to govern the flow of energy between the stator of a DFIG and the energy network using three types of controllers: proportional integral (PI), sliding mode controller (SMC) and second order sliding mode controller (SOSMC). Their different results in terms of power reference tracking, reaction to unexpected speed fluctuations, sensitivity to perturbations, and resilience against machine parameter alterations are compared. MATLAB/Simulink was used to conduct the simulations for the preceding study. Multiple simulations have shown very satisfying results, and the investigations demonstrate the efficacy and power-enhancing capabilities of the suggested control system.
International Conference on NLP, Artificial Intelligence, Machine Learning an...gerogepatton
International Conference on NLP, Artificial Intelligence, Machine Learning and Applications (NLAIM 2024) offers a premier global platform for exchanging insights and findings in the theory, methodology, and applications of NLP, Artificial Intelligence, Machine Learning, and their applications. The conference seeks substantial contributions across all key domains of NLP, Artificial Intelligence, Machine Learning, and their practical applications, aiming to foster both theoretical advancements and real-world implementations. With a focus on facilitating collaboration between researchers and practitioners from academia and industry, the conference serves as a nexus for sharing the latest developments in the field.
Using recycled concrete aggregates (RCA) for pavements is crucial to achieving sustainability. Implementing RCA for new pavement can minimize carbon footprint, conserve natural resources, reduce harmful emissions, and lower life cycle costs. Compared to natural aggregate (NA), RCA pavement has fewer comprehensive studies and sustainability assessments.
CHINA’S GEO-ECONOMIC OUTREACH IN CENTRAL ASIAN COUNTRIES AND FUTURE PROSPECTjpsjournal1
The rivalry between prominent international actors for dominance over Central Asia's hydrocarbon
reserves and the ancient silk trade route, along with China's diplomatic endeavours in the area, has been
referred to as the "New Great Game." This research centres on the power struggle, considering
geopolitical, geostrategic, and geoeconomic variables. Topics including trade, political hegemony, oil
politics, and conventional and nontraditional security are all explored and explained by the researcher.
Using Mackinder's Heartland, Spykman Rimland, and Hegemonic Stability theories, examines China's role
in Central Asia. This study adheres to the empirical epistemological method and has taken care of
objectivity. This study analyze primary and secondary research documents critically to elaborate role of
china’s geo economic outreach in central Asian countries and its future prospect. China is thriving in trade,
pipeline politics, and winning states, according to this study, thanks to important instruments like the
Shanghai Cooperation Organisation and the Belt and Road Economic Initiative. According to this study,
China is seeing significant success in commerce, pipeline politics, and gaining influence on other
governments. This success may be attributed to the effective utilisation of key tools such as the Shanghai
Cooperation Organisation and the Belt and Road Economic Initiative.
TIME DIVISION MULTIPLEXING TECHNIQUE FOR COMMUNICATION SYSTEMHODECEDSIET
Time Division Multiplexing (TDM) is a method of transmitting multiple signals over a single communication channel by dividing the signal into many segments, each having a very short duration of time. These time slots are then allocated to different data streams, allowing multiple signals to share the same transmission medium efficiently. TDM is widely used in telecommunications and data communication systems.
### How TDM Works
1. **Time Slots Allocation**: The core principle of TDM is to assign distinct time slots to each signal. During each time slot, the respective signal is transmitted, and then the process repeats cyclically. For example, if there are four signals to be transmitted, the TDM cycle will divide time into four slots, each assigned to one signal.
2. **Synchronization**: Synchronization is crucial in TDM systems to ensure that the signals are correctly aligned with their respective time slots. Both the transmitter and receiver must be synchronized to avoid any overlap or loss of data. This synchronization is typically maintained by a clock signal that ensures time slots are accurately aligned.
3. **Frame Structure**: TDM data is organized into frames, where each frame consists of a set of time slots. Each frame is repeated at regular intervals, ensuring continuous transmission of data streams. The frame structure helps in managing the data streams and maintaining the synchronization between the transmitter and receiver.
4. **Multiplexer and Demultiplexer**: At the transmitting end, a multiplexer combines multiple input signals into a single composite signal by assigning each signal to a specific time slot. At the receiving end, a demultiplexer separates the composite signal back into individual signals based on their respective time slots.
### Types of TDM
1. **Synchronous TDM**: In synchronous TDM, time slots are pre-assigned to each signal, regardless of whether the signal has data to transmit or not. This can lead to inefficiencies if some time slots remain empty due to the absence of data.
2. **Asynchronous TDM (or Statistical TDM)**: Asynchronous TDM addresses the inefficiencies of synchronous TDM by allocating time slots dynamically based on the presence of data. Time slots are assigned only when there is data to transmit, which optimizes the use of the communication channel.
### Applications of TDM
- **Telecommunications**: TDM is extensively used in telecommunication systems, such as in T1 and E1 lines, where multiple telephone calls are transmitted over a single line by assigning each call to a specific time slot.
- **Digital Audio and Video Broadcasting**: TDM is used in broadcasting systems to transmit multiple audio or video streams over a single channel, ensuring efficient use of bandwidth.
- **Computer Networks**: TDM is used in network protocols and systems to manage the transmission of data from multiple sources over a single network medium.
### Advantages of TDM
- **Efficient Use of Bandwidth**: TDM all
ACEP Magazine edition 4th launched on 05.06.2024Rahul
This document provides information about the third edition of the magazine "Sthapatya" published by the Association of Civil Engineers (Practicing) Aurangabad. It includes messages from current and past presidents of ACEP, memories and photos from past ACEP events, information on life time achievement awards given by ACEP, and a technical article on concrete maintenance, repairs and strengthening. The document highlights activities of ACEP and provides a technical educational article for members.
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODELgerogepatton
As digital technology becomes more deeply embedded in power systems, protecting the communication
networks of Smart Grids (SG) has emerged as a critical concern. Distributed Network Protocol 3 (DNP3)
represents a multi-tiered application layer protocol extensively utilized in Supervisory Control and Data
Acquisition (SCADA)-based smart grids to facilitate real-time data gathering and control functionalities.
Robust Intrusion Detection Systems (IDS) are necessary for early threat detection and mitigation because
of the interconnection of these networks, which makes them vulnerable to a variety of cyberattacks. To
solve this issue, this paper develops a hybrid Deep Learning (DL) model specifically designed for intrusion
detection in smart grids. The proposed approach is a combination of the Convolutional Neural Network
(CNN) and the Long-Short-Term Memory algorithms (LSTM). We employed a recent intrusion detection
dataset (DNP3), which focuses on unauthorized commands and Denial of Service (DoS) cyberattacks, to
train and test our model. The results of our experiments show that our CNN-LSTM method is much better
at finding smart grid intrusions than other deep learning algorithms used for classification. In addition,
our proposed approach improves accuracy, precision, recall, and F1 score, achieving a high detection
accuracy rate of 99.50%.
Comparative analysis between traditional aquaponics and reconstructed aquapon...bijceesjournal
The aquaponic system of planting is a method that does not require soil usage. It is a method that only needs water, fish, lava rocks (a substitute for soil), and plants. Aquaponic systems are sustainable and environmentally friendly. Its use not only helps to plant in small spaces but also helps reduce artificial chemical use and minimizes excess water use, as aquaponics consumes 90% less water than soil-based gardening. The study applied a descriptive and experimental design to assess and compare conventional and reconstructed aquaponic methods for reproducing tomatoes. The researchers created an observation checklist to determine the significant factors of the study. The study aims to determine the significant difference between traditional aquaponics and reconstructed aquaponics systems propagating tomatoes in terms of height, weight, girth, and number of fruits. The reconstructed aquaponics system’s higher growth yield results in a much more nourished crop than the traditional aquaponics system. It is superior in its number of fruits, height, weight, and girth measurement. Moreover, the reconstructed aquaponics system is proven to eliminate all the hindrances present in the traditional aquaponics system, which are overcrowding of fish, algae growth, pest problems, contaminated water, and dead fish.
Using recycled concrete aggregates (RCA) for pavements is crucial to achieving sustainability. Implementing RCA for new pavement can minimize carbon footprint, conserve natural resources, reduce harmful emissions, and lower life cycle costs. Compared to natural aggregate (NA), RCA pavement has fewer comprehensive studies and sustainability assessments.
Recycled Concrete Aggregate in Construction Part II
Blood bank management system
1. Blood Bank Management System
A Project Presentation
on
Submitted By:
Rinku S. Patel (13084231181)
Poonam K. Patel (13084231173)
Internal Guide:
Mr. Dhaval K. Raval
Submitted To:
Department of Computer Science,
Ganpat University,384012
2. PROJECT PROFILE
Project Name Blood Bank Managemant System
Objective The system provide online information of blood bank and administrators can also all information about
blood bank,donor,patient request and blood requriments.
Platform Web application
Front End Asp . NET 4.0 with c#
Back End Microsoft Sql Server 2008
Other Tools MS Office 2007 ,Visual studio
Project Duration 50 days
Internal Guide Mr. Dhaval K.Raval
Submitted To Department of computer science,Ganpat University
Develop By Rinku S.Patel
Poonam K.patel
3. EXISTING SYSTEM
• Existing system is window Application.
• So much time consuming this application also one machine and one by one record stored.
• Single Blood bank information also no inquiry for directly Blood bank.
4. NEED FOR NEW SYSTEM
• User view all Blood bank information is location wise.
• Donor easily donate the blood near Blood bank Location.
• Patient easily request for blood near Blood bank location
• In this system also supported inquiry form for user.
5. FUNCTION SPECIFICATION
ADMIN:-
• Manage Registration for user
• Manage Blood bank information like (update, delete)
• Manage Donor Request for Donor
• Manage patient Request for needy people
• Manage Inquiry form for Appropriate Reply
• Manage feedback for Appropriate Reply
• Blood bank information view/update
• View Donor information
• Manage Patient Blood Request.
BLOOD BANK:-
1.Admin
2.Blood bank
3.Donor
4.Patient
DONOR:-
• Manage Donor information(profile)
• Add new Donation for Blood
PATIENT:-
• Manage patient information(profile)
• Give the Request for patient for blood
6. HARDWARE & SOFTWARE SPECIFICATION
Hardware Specification :
Server Side:
Client Side:
Processor 3.6 GHz
RAM 2 GB
Hard Disk 80 GB
Processor 2.40 GHz
RAM 1 GB
Hard Disk 20 GB
7. Software Specification :
• Server Side
• Client Side
Operating System Window Server 2008
Runtime Environment .Net Framework 4.0
Web Server IIS 7.0
Front End Microsoft Asp.Net 2010 with c#
Back End SQL server 2008
Operating System Windows XP or any compatible OS
Web Browser Internet Explorer 6.0 or any compatible web browser.
11. TIMELINE CHART
Development
Phase
50 Days
Duration
(Day)
0 to 05
Day
06 to 10
Day
11 to 20
Day
21 to 30
Day
31 to 40
Day
41 to 50
Day
Requirement
Gathering and
Analysis
10
Design 10
Coding 20
Testing 5
Implementation
&
Documentation
5
Total Time (Day) 50
15. Registration
Login
Manage Blood bank
Manage Donor
Manage Patient request
View Feedback
Manage City/Location
Blood Bank Management System
Use case Diagram
Admin:
Manage inquiry
23. Class diagram
1 * 1 <<Use> > *
1 <<Use>>
1
*
*
ma
1 * *
ADMIN
-ID : STRING
-Bloodbank_management()
+Donor_management()
+Patient_Request()
+User_management()
+Login()
USER
-ID: INT
NAME
BIRTH_DATE
CONTACT_NO
EMAIL_ID
+Register()
+Login()
+Make_request()
+View_services()
+Feedback()
Blood bank
-B_ID : INT
Name: STRING
S_ID : ID
+Login()
+Sign_up()
+Request_management()
+Donor_management()
view_profile()
New Donor Request
-DD :INT
B ID :INT
D NAME :STRING
L_ID : INT
+Check Donore ()
+Request new Donor ()
Patient Request Location
-ID :INT
B ID :INT
-L_ID : INT
S NAME: STRING
V_ID : INT
+Check service ()
+Request service ()
STATE
-S ID : INT
STATE:STRING
+ Provide State()
CITY
-C ID : INT
SID : INT
SNAME : STRING
+Provide state wise city()
LOCATION
-LOC ID : INT
CID : INT
L NAME: STRING
+Provide City wise location
()
25. S:System D:Database
Admin
Send Request
Get interfaceSuccessfully registerated
Login(user name,passward) Send request
Get interfaceSuccessfully login
Manage blood bank Store blood bank details
Acknowledgement
Manage successfully
Manage donor Store donor details
Manage successfully
Acknowledgement
Manage request patient Store request patient details
AcknowledgementManage successfully
Manage city/location Store city/location details
Manage successfully Acknowledgement
view feedback
Manage inquiry Store inquiry details
Manage successfully
logout
logout successfully
Admin:
X
Get reply Fetch feedback details
Store feedback details
Acknowledgement
Registration
XX
26. S:System D:Database
Blood bank
Blood bank :
X X X
Successfully registerated
Send Request
Get interface
Login(user name,passward)
Send request
Get interfaceSuccessfully login
Store request
View request
Fetch request
Add new blood bank Store add new blood bank details
AcknowledgementSuccessfully add new blood bank
Manage donor
Manage donor successfully
Store donor details
Acknowledgement
Get reply
Manage patient blood request
Manage patient blood request successfully
Manage stock Store stock details
AcknowledgementManage stock successfully
logout
logout successfully
Store patient blood request
Acknowledgement
Registration
27. S:System D:Database
donor
Donor :
X X X
Send Request
Successfully registerated Get interface
Login(user name,passward)
Get interface
Send request
Successfully login
View profile
Store profile details
Fetch profile detailsGet reply
Store new blood details
AcknowledgementSuccessfully new blood donation
logout successfully
logout
Make new Blood Donation
Registration
28. S:System D:Database
patient
Patient :
X X X
Successfully registerated
Send Request
Get interface
Login(user name,passward)
Successfully login
Send request
Get interface
View profile
Get reply
Store profile details
Fetch profile details
Search patient request for blood
Fetch patient request for bloodGive request for blood
logout
logout successfully
Patient Request for blood
Registration
29. Collaboration Diagram
Blood Bank
Management
Admin
Data Base
1.3 successfully reg.
2.3 successfully login
3.3 manage successfully
4.3 manage successfully
5.3 manage successfully
6.3 manage successfully
7.3 get reply
8.3 manage successfully
9.1 successfully logout
1.0
2.0 login user/password
3.0 manage blood bank
4.0 manage donor
5.0 manage req.patient
6.0 manage city/location
7.0 view feedback
8.0 manage inquiry
9.0 logout
1.1 check user details
2.1 check user/password
3.1 store blood bank details
4.1 store donor details
5.1 store req.patient details
6.1 store city/location details
7.1 store feedback details
8.1 store inquiry details
1.2 fetch user details
2.2 fetch user/password
3.2 fetch blood bank details
4.2fetch donor details
5.2 fetch req.patient details
6.2 fetch city/location details
7.2 fetch feedback details
8.2 fetch inquiry details
Admin:
Registration
30. Blood Bank
Management
bloodbank
Data Base
1.3 successfully reg.
2.3 successfully login
3.3 get reply
4.3 manage add new blood bank
successfully
5.3 manage donor successfully
6.3 manage patient blood request
successfully
7.3 manage stock
8.1 successfully logout
1.0
2.0 login user/password
3.0 view request
4.0 add new blood bank
5.0 manage donor
6.0 manage patient blood request
7.0 manage stock
8.0 logout
1.1 check user details
2.1 check user/password
3.1 store request
4.1 store add new blood bank details
5.1 store donor details
6.1 store patient blood request
7.1 store stock
1.2 fetch user details
2.2 fetch user/password
3.2 fetch request
4.2fetch new blood bank details
5.2 fetch donor details
6.2 fetch patient blood details
7.2 fetch stock
Blood bank:
Registration
31. Blood Bank
Management
Donor
Data Base
1.3 successfully reg.
2.3 successfully login
3.3 get reply
4.3 successfully new blood donation
5.1 successfully logout
1.0
2.0 login user/password
3.0 view profile
4.0 make new Blood Donation
5.0 logout
1.1 check user details
2.1 check user/password
3.1 store profile details
4.1 store new blood details
1.2 fetch user details
2.2 fetch user/password
3.2 fetch profile details
4.2fetch new blood details
Donor :
Registration
32. Blood Bank
Management
patient
Data Base
1.3 successfully reg.
2.3 successfully login
3.3 get reply
4.3 give patient request for blood
5.1 successfully logout
1.0 Registration
2.0 login user/password
3.0 view profile
4.0 patient Request for blood
5.0 logout
1.1 check user details
2.1 check user/password
3.1 store profile details
4.1 Search patient request for blood
1.2 fetch user details
2.2 fetch user/password
3.2 fetch profile details
4.2fetch patient request for blood details
Patient :
33. Table Name: Usertype_mst
Field Name Data Type Size Constraints Description
U_id bigint 4 Primary key To store the user id
U_type nvarchar 50 NOT NULL To store the user type
Data Dictionary
Primary key:-u_id
Description:- This Table is store the user information
34. Field Name Data Type Size Constraints Description
State_id bigint 4 Primary key To store the state id
State name nvarchar 50 NOT NULL To store the state name
Table Name: State_mst
Primary key:-state id
Description:- This Table is store the states information
35. Field Name Data Type Size Constraints Description
city_id bigint 4 Primary key To store the city_id
state_id bigint 4 Foreign key References of the state
id from state_mst
city _name nvarchar 15 NOT NULL Reference of the city
name form city_mst
Table Name: City_mst
Primary key:-city id
Foreign key:-state_id
Description:- This Table is store cities information with states wise
36. Field Name Data Type Size Constraints Description
location_id bigint 4 Primary key To store the location id
City_id bigint 4 Foreign key Reference fo the city id
from city_mst
location _name nvarchar 50 NOT NULL To store the location
name
Table Name: Location_mst
Primary key:-location id
Foreign key:-city_id
Description:- This Table is store location information cities wise
37. Field Name Data Type Size Constraint Description
Reg_id Numeric 4 Primary key To store the reg_id
U_id Numeric 10 Foreign key References of the User_id from
usertype_mst
Name Nvarchar 50 NOT NULL To store the name
Cont_no nvarchar 10 NOT NULL To store the cont no
Address nvarchar 50 NOT NULL To store the address
State nvarchar 15 NOT NULL To store the state
City nvarchar 15 NOT NULL To store the city
Location nvarchar 15 NOT NULL To store the location
Pin-code nvarchar 10 NOT NULL To store the pin code
Email nvarchar 30 NOT NULL To store the email
Table Name: Registration
Primary key:-R_ id
Foreign key:-u_id
Description:- This Table is store user registration information
Co t…..
38. Birth date datetime NOT NULL To store the birthdate
Gender nvarchar 6 NOT NULL To store the gender
User_name nvarchar 20 Unique key To store the user name
Password nvarchar 20 NOT NULL To store the password
Security_que nvarchar 30 NOT NULL To store the security que
Answer nvarchar 15 NOT NULL To store the answer
Flag Bit 1 NOT NULL To store the flag
Co t…..
39. Field Name Data Type Size Constraint Description
b_id bigint 4 Primary Key To store the blood bank _id
reg_id bigint 4 Foreign key References of the
regstration_id from regstration
Bb_name nvarchar 10 NOT NULL To store the blood bank name
Loc_id bigint 4 Foreign key References the location id from
location_mst
City id bigint 4 Foreign key References of the city id from
city_mst
Contact no Numeric 12 NOT NULL To store the contact no
Status bit 1 NOT NULL To store the status
ddate datetime NOT NULL To store the donated date
Table Name: Bloodbank_mst
Primary key:-b_id
Foreign key:-Reg_id,loc_id,city_id
Description:- This Table is store blood bank information location and cities wise
40. Field Name Data Type Size Constraint Description
D_id bigint 4 Primary Key To store the donation id
Reg_id bigint 4 Foreign key References of the registration id
from registration
Name nvarchar 10 NOT NULL To store the name
b_id bigint 4 Foreign key References of the blood bank id
from bloodbank_mst
bgroup nvarchar 10 NOT NULL To store the blood group
Qty nvarchar 20 NOT NULL To store the qty
ddate datetime NOT NULL To store donated date
Table Name: Donation_mst
Primary key:-d_id
Foreign key:-Reg_id,bb_id
Description:- This Table is store donor information for blood bank wise
41. Field Name Data Type Size Constraint Description
br_id bigint 4 Primary Key To store the blood bank _id
Reg_id Bigint 4 Foreign Key To store regtraction id for
Patient
B_id Bigint 4 Foreign key To fetch blood bank id
Loc_id bigint 4 Foreign key References the location id from
location_mst
City id bigint 4 Foreign key References of the city id from
city_mst
Contact no Numeric 12 NOT NULL To store the contact no
bgroup nvarchar 10 NOT NULL To store the blood group
qty nvarchar 10 NOT NULL To store the qty
Status bit 1 NOT NULL To store the blood request
status for patient
D_date datetime NOT NULL To store the donate date
Table Name: Blood Request
Primary key:-br_id
Foreign key:-user_id,loc_id,city_id,b_id
Description:- This Table is use to store blood request information
42. Field Name Data Type Size Constraint Description
Inq_Id bigint 4 Primary key To store the id
Name nvarchar 20 NOT NULL To store the name
Inquiry nvarchar Max NOT NULL To store the inquiry
Address nvarchar 50 NOT NULL To store the address
Phone no nvarchar 20 NOT NULL To store the phone no
Email nvarchar 30 NOT NULL To store the email
Date Datetime NOT NULL To store the date
Flage bit 1 NOT NULL To store the flage
Table Name: inquiry _Form
Primary key:- inq_id
Description:- This Table to store inquiry information submitted for user and visitor
43. Field Name Data Type Size Constraints Description
fid bigint 4 Primary key To store the id
Name nvarchar 50 NOT NULL To store the name
Email nvarchar 50 NOT NULL To store the email
Feed back nvarchar max NOT NULL To store the feed back
Table Name: Feedback
Primary key:- fid
Description:- This Table to store feedback information
103. Testing
No Test condition Expected Result Actual output Status
(pass, fail)
Test 1 Click on submit
button without user
name and password.
System does not allow
user to login.
System displays
message and resume
to the same page.
pass
Test 2 Click on submit
button with invalid
user name and or
password.
Message "please fill
up the username or
password
As expected. pass
Test 3 Click on submit
button with correct
user name add
password.
System allow user to
login.
System allow user to
access application
based on rights given
to him.
pass
Name :- User login module
104. No Test condition Expected Result Actual output Status
(pass, fail)
Test 1
Click on submit button
without user name and
password.
System does not allow
user to login.
System displays
message and resume
to the same page.
pass
Test 2 Click on submit button
without correct
password & re-
password.
Message please fill
up the correct
password & re
password
System displays
message and resume
to the same page.
pass
Test 3 Select on user type
with correct user
registration
System allow user to
login.
System allow user to
access application
based on right given
to him.
pass
Name :-User Registration
105. No Test condition Expected Result Actual output Status
(pass, fail)
Test 1 Click on update
button without add
new information of
blood bank name.
System does not allow
admin to save data
without add blood
bank information.
System displays
message to the same
page.
pass
Test 2 Click on edit button all
blood bank location
information.
Message update
successfully .
System allow admin
to add new category
information into the
system.
pass
Name :- Blood bank
106. No Test condition Expected Result Actual output Status
(pass, fail)
Test 1 Click on update
button without add
new information of
request for blood
bank name
System does not allow
admin to save data
without add blood
bank name
System displays
message to the same
page.
pass
Name :- Blood request
107. No Test condition Expected Result Actual output Status
(pass, fail)
Test 1 Click on update
button without add
new information of
donor request for
blood bank name.
System does not allow
admin to save data
without add blood
bank name
System displays
message to the same
page.
pass
Name :- Donor request
108. No Test condition Expected Result Actual output Status
(pass, fail)
Test 1 Click on submit
button without name.
System does not allow
user name
System displays
message and resume
to the same page.
pass
Test 2 Click on submit
button with invalid
email id
Message "please fill
up their e ail id
As expected. pass
Test 3 Click on submit
button with require
Feedback message
System allow user to
feedback.
System allow user to
access application
based on rights given
to him.
pass
Name :- Feed back
109. No Test condition Expected Result Actual output Status
(pass, fail)
Test 1 Click on submit
button without name.
System does not allow
user to login.
System displays
message and resume
to the same page.
pass
Test 2 Click on submit
button with invalid
email id
Message "please fill
up the username or
password
As expected. pass
Test 3 Click on submit
button with correct
contact no
System allow user to
login.
System allow user to
access application
based on rights given
to him.
pass
Name :- Inquiry
110. Post Implementation Review
• The important point that to keep during post implementation review is determining whether the
application has met its objective that is, analysts want to know if the performance level of users has
improved.
• It contain all information about the blood bank and also show the user can search by their blood
requirement.
• Reviews are taken until Application fulfills users requirement. After implementation it is easy to manage
the application and is easy to solve the difficulties. In this requirement are fulfill.
• And also it display blood bank list and all information.
111. FEATURE ENHANCEMENTS
• Through online directory user can search any blood bank data by location.
• User can also message module.
• User can see this website and search blood bank.
• This website can manage and create their own information.
112. BIBLIOGRAPHY
Reference Books and journal
• Asp.net4.0
• Asp.net 3.5 complete reference
Referring online manual from website
•www.codeproject.com
•www.tutorialpoints.com
•www.w3school.com