Blod Bank Essay

It testament explain the purpose and features of the outline, the interfaces of the organization, what the corpse submit do, the constraints under which it must operate, specific unavoidablenesss and other supporting information. This memorial is intend for both the s suck inh olders and the developers of the formation. This written document is intended for developers, project coordinator, project guide, ingestionrs and testers. The developer mess hire the document to view the analysis and design part, to understand requirements specification. The project coordinator dejection use this document to review the idea of project whether it is innovative and featal or non.The project guide can use this document to probe and manage the flow of project phylogeny. The tester can use this document to get clear idea to the highest degree body, to understand the exact enter domain of system and to fuss respective test cases for the testing purpose. 1. 1 Purpose This Softw atomic number 18 Requirements Specification provides a complete description of completely the functions and specifications of the line bank trouble corpse computer package. The purpose of this document is to demonstrate a detailed description of the declension money box transcription. This document is useable for line of merchandise Bank employees who use this system on the daily basis.This document impart likewise serve as a reference to turn back all changes made in the system to the future. It allow for overly switch off to be useful to the managerial staff which is responsible for the smooth carrying into action of the counter transactions that are performed on daily basis. This document is in the beginning intended to provide a detailed specification of the functional requirements for developers of the product. It also provides an overview of the product for the users. It lead explain the purpose and features of the system, what the systems do and the cons traints under which it ordain operate.This SRS document hold backs the complete software requirement for Post Office exertion organization and describes the design decisions, architectural design and the detail design need to implement the system. It provides the visibility in the design and provides information needed for software support. 1. 2 Scope This software is use by brass Administrator, Supervisor, help and Lab technicians. The system is designed to provide user authentication by maintaining the user database which contains all the inside information of user along with login enlarge such(prenominal) as username and password.Each user has a different level of operation for the authentication purpose. The solution go outing provide a well-organized and coordinated system where the broth and conferrer personalitys are managed more efficiently with remediate security. The study goal of the system is to provide synchronized and centralized sponsor and communicati on channel production line database to the contrast bank. It also improves the efficiency of source stock perplexity by alerting the line of products bank executive director. organisation leave behind provides traceability of presenter in case of emergency. It also provides process evaluation using proclaim generation. 1. 3 Definitions, Acronyms, and AbbreviationsThis subsection should provide the definitions of all terms, acronyms, and abbreviations required to properly represent the SRS. This information may be provided by reference to one or more appendixes in the SRS or by reference to other documents. 1. 4 References 1. www. bharat rail linebank. com 2. www. bloodbankindia. com 1. 5 Overview This document contains a brief score and insight into the task as well as what the system is designed to do, the scope of the solution. It gives a brief summary of whom the system is targeted at, its capabilities, and its positioning in the device development process.It also explains requirements of the system and also where exactly the user and stakeholders are lay in the scheme of things. It elaborates on security give ups, hardware and software requirement and also the priorities of various functionalities. The document helps the user to understand the Blood Bank System. The first part of the document provides the purpose, objectives and scope of the proposed system. It includes important definition, the problem education specify the needed lucubrate to avoid any kind of ambiguity from users perspective. The document also states the feature set and capabilities of the system.The document also highlights the feature of proposed system and the advantages over the existing system. The document also highlights the various issues, error handling and the modification to be make in the system. The document is helpful to the user as it gives them opportunities to state what they expect from the system. In addition, the hardware specification required for the system is also mentioned. The user can read the document and make sure that his machine is equipped to put up the system to avoid any inconvenience The user should make use of the document to understand the system better.The rest of this document provides a teeming description of the project for the blood bank. It lists all the functions performed by the system. It gives the details of each(prenominal) of the system functions and actions in full for the software developers assistance. It also gives the overview of the problems currently faced by the system and provides solutions for the same. 2. General Description The project deals with the problem of automated management system that is keeping track of the actual union of blood stock in the blood bank and to minimize benignant errors.The solution will provide a well-organized and coordinated system for blood bank where the blood and conferrer records are managed more efficiently with better security and added automat ion functions in alerting the decision maker when the blood touchstone is below par level and about the expire types. In addition, the administrator can also trace back the donor responsible in case of reactive sample in blood transfusion and blood screening result. This system also creates a convenient and paperless environment for the blood bank in managing donors and processing blood stocks.The registration time for old donor is shortened as the records are retrievable from the system. Also the performance evaluation is possible using report generation facility. 2. 1 crossing Perspective This system keep the track of all the actual summation of the blood stock in the blood bank to minimize the tender errors. 2. 2 Product Functions 1. System will also maintain Blood Stock records and Discard registry. 2. System will provide levels of operators for authentication purpose. 3. System will provide an authentication form where the users will fill the details. 4.System will proce ss the request of login. 5. System will check for the entered details in the login database. 6. If the entered username and password are valid then the system will grant access to the user else will display an error message. 7. System will provide five interfaces such as Testing Interface, Blood Stock Interface, electric outlet Interface, Donor alteration Interface and Statistics Interface. 8. Donor Registration Interface will take all the personal and medical exam details of donor and generate a unique id for each donor. 9. If the donor already has an id then will retrieve its details. 10.In Testing Interface, if the results are demonstrable then discard take is up fancyd with sample details. 11. If the results are negative Blood Stock Repository is updated with sample details. 12. In Blood Stock Interface, system will generate unique bag numbers for each product. 13. It will generate alerts when the blood quantity is below par level and about the expired samples. 14. The Syst em will move expired sample details to discard register and update blood stock repository. 15. In make out Repository, system will check blood stock repository for availability. 16. If stocks are available then system will place an issue order. 7. It will generate a label which includes bag number and details of sample. 18. In Statistics analysis, system will generate various reports. 19. The whole transaction of the blood will be recorded in a system 20. The software will perform the stock management & bill generation. 21. any the transaction of the blood will be updated within a down in the mouth period of time. 22. The software will generate all the annual record of the blood bank.. 23. It will also maintain the record of the blood donor. 24. It will also maintain the record of the rejected blood and the rejection for the blood rejection. 2. substance abuser Characteristics The user must have the basic knowledge of the computer system. It is not necessary that the user must have the knowledge of the computer hardware. System administrator, supervisor, assistant and lab technicians. 2. 4 General Constraints * Blood bank employees ,donors 2. 5 Assumptions and Dependencies * The System will not allow any user with hamper username and invalid password. * The system should not provide administrative privilege to any customer. 3. Specific Requirements The systems should satisfy the below given requirements. 1. Operating System Windows XP pro 2.Database Management System (DBMS) MySQL 5. 0 3. Peer to peer connection. This can be done by connecting both the systems using a cross parentage and freehand different IP addresses to them. 3. 1 External Interface Requirements System Interfaces The systems should satisfy the below given requirements. 4. Operating System Windows XP Professional 5. Database Management System (DBMS) MySQL 5. 0 6. Peer to peer connection. This can be done by connecting both the systems using a cross cable and giving different IP addre sses to them. User Interfaces User Type Intended interaction 1. DONOR REGISTRATION a. New donor b.Regular donor * The system will take all the personal and medical details of donor and generate an unique id for the donor. * The system will take donors id as input signal, substantiate it and retrieve all its details including last donations. 2. Administrator Login * This login page will take input as username and password from the administrator * The system will validate the inputs and provide access to the system with more privileges to system and administrator Testing * This will take the input as blood group, donor id, date of collection test carried out and its result.If the test results are affirmative then sample details are moved to discard register otherwise to blood stock repository. Blood stock * It will take all the details of the samples including blood group, its product details, date of collection, date of preparation, date of expiry, result of testing and gener ate a bag number. * It will generate alerts when the blood quantity is below par level and about the expired samples. * The expired sample details are moved to discard register and removed from blood stock repository. Issue * It will take input as product name, quantity, blood group and validate it with blood stock repository. If the stock is available then issue order will be placed. * It will generate a label which includes bag number, details of sample etc. Statistics Display Page * The administrator has access to this page. It displays all statistical data regarding the various issue orders placed, blood stock repository and testing screening. * Report generation. 3. 5 Non-Functional Requirements Goal To provide authentication to donors. neutral 1 Create unique id for donors. a. Accept donor personal and medical information for new donors. b. Generate unique id for each donor. accusing 2 Process authentication request. a. Accept donor id in case of constant donor. b. Ret rieve donors profile. Goal To manage Blood Stocks. Objective 1 Process blood stock details. a. Accept product details like collection date, expiry date, blood group etc. b. Generates a unique bag number. Objective 2 Establish connection with Issue interface and testing interface. a. Validate stock details for issue. b. Update blood stock repository after testing is negative. Goal To generate reports and label. Objective 1 To generate report. a.Generate product statistics b. Generate yearly, monthly reports and provide it to the administrator. Objective 1 To generate labels for issue. a. Generate labels for the issue order placed. b. append it to the customer along with the date of delivery 3. 5 Non-Functional Requirements 7. 1. 1 approachability * For the customers, the services available are Registration as a donor, situation of issue order. * For the administrator, the services available are Manipulation of databases, change the functionalities provided by the system and monthly and yearly reports generation. . 1. 2 Security * This system maintains unity and security as the blood stock details cant be modified by the administrator or the other user. The system analyses the issue order placed by the customer and accordingly fulfills it. The system will also provide authentication by using username and password. * The donors database will have its own security to prevent self-appointed write/delete access. The donors details will not be disclosed while issuing. 3. 8 Logical Database Requirements The databases utilize by the system are * Donor database Blood stock database * Discard database * bet database User database The purpose of this database is to computer storage the required information of the donors and their ids. This database will be used for traceability of donor. The donors will fill their information while registration. Their credentials will be saved in this particular database. Blood Stock database This database is used to maintai n blood stock information. It maintains the details of valid samples. Discard database This database is used to store details of blood samples which have to be discarded.This will contain information of expired samples and those samples which reacted positively in testing screening. Accounts database The purpose of this database is to store the account details regarding issue of blood sample and to maintain the history of all the previous transactions. This database will be used by the administrator so that he can calculate the total cost of the issue orders placed. Accessing capabilities 1. Only administrator can set the role of users and their access capabilities 2. No user can access anything outside its accessing capability .