Blod Bank

rip curse MANAGEMENT SYSTEM Softw atomic number 18 Requirements specialation 3rd Feb 2013 Prep ard for BLOOD BANK Table of Contents Revision Historyii Document Approvalii 1. psychiatric hospital1 1. 1 Purpose1 1. 2 Scope1 1. 3 Definitions, Acronyms, and Abbreviations1 1. 4 References1 1. 5 Overview1 2. General explanation2 2. 1 Product Perspective2 2. 2 Product Functions2 2. 3 User Characteristics2 2. 4 General Constraints2 2. 5 Assumptions and Dependencies2 3. special Requirements2 3. 1 External Interface Requirements3 3. 1. 1 User Interfaces3 3. 1. 2 computer computer hardware Interfaces3 3. 1. 3 Software Interfaces3 3. 2 Functional Requirements3 . 2. 1 3 3. 2. 2 3 3. 5 Non-Functional Requirements4 3. 5. 1 Performance4 3. 5. 2 Reliability4 3. 5. 3 Availability4 3. 5. 4 Security4 4. abridgment Models4 4. 1 Sequence Diagrams5 4. 3 Data Flow Diagrams (DFD)5 4. 2 State-Transition Diagrams (STD)5 1. Introduction This SRS trys needs and proposed solution of the slant Bank guid ance establishment utilize in argumentation swan buildings. This parcel works in a Client horde environment with the server storing the data and clients connecting to the server for on the whole types of consummations.It testament justify the pottle and gives of the governance, the interfaces of the ashes, what the carcass domiciliateing do, the constraints under which it must operate, specific requirements and early(a) supporting data. This document is intended for both the s carry awayholders and the developers of the constitution. This document is intended for developers, give coordinator, project guide, exploiters and examiners. The developer spate use the document to view the analysis and tendency part, to hear requirements specification. The project coordinator can use this document to review the belief of project whether it is innovative and usable or not.The project guide can use this document to analyze and manage the flow of project developme nt. The tester can use this document to get clear idea active system, to understand the exact gossip domain of system and to repay individual test cases for the testing purpose. 1. 1 Purpose This Software Requirements Specification suffers a complete description of wholly the functions and specifications of the squanderer bank Management strategy software. The purpose of this document is to present a diminutive description of the communication channel Bank organisation. This document is useful for Blood Bank employees who use this system on the daily basis.This document go forth overly serve as a compose to incorporate each changes made in the system to the future. It will in like manner prove to be useful to the managerial supply which is responsible for the smooth functioning of the counter transactions that are performed on daily basis. This document is primarily intended to provide a detailed specification of the functional requirements for developers of the produceion. It withal provides an overview of the product for the exploiters. It will explain the purpose and features of the system, what the systems do and the constraints under which it will operate.This SRS document contains the complete software requirement for Post Office Transaction system and describes the determination decisions, architectural visualise and the detail design needed to implement the system. It provides the visibility in the design and provides information needed for software support. 1. 2 Scope This software is used by System Administrator, Supervisor, Assistant and Lab technicians. The system is knowing to provide substance ab exploiter enfranchisement by maintaining the user database which contains all the detail of user along with login elaborate such as username and password.Each user has a assorted level of operation for the authentication purpose. The solution will provide a well-organized and twin(a) system where the birth and giver reco rds are managed more(prenominal) efficiently with better security. The major goal of the system is to provide synchronized and modify sponsor and line of merchandise gestate database to the snag bank. It also improves the efficiency of decline stock management by alerting the origin bank executive director. System will provides traceability of donor in case of emergency. It also provides performance evaluation using report contemporaries. 1. 3 Definitions, Acronyms, and AbbreviationsThis subsection should provide the definitions of all terms, acronyms, and abbreviations take to properly interpret the SRS. This information may be provided by indication to one or more appendixes in the SRS or by reference to other documents. 1. 4 References 1. www. bharat simple eyebank. com 2. www. phone linebankindia. com 1. 5 Overview This document contains a brief record and insight into the problem 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 placed in the scheme of things. It elaborates on security issues, hardware and software requirement and also the priorities of confused 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 definitive definition, the problem give inment specify the needed details 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 exist system. The document also highlights the various issues, computer error handling and the modification to be do in the system. The document is helpf ul to the user as it gives them opportunities to state what they expect from the system. In addition, the hardware specification unavoidable for the system is also mentioned. The user can read the document and make sure that his railroad car is equipped to run 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 full description of the project for the blood bank. It lists all the functions performed by the system. It gives the details of each 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 address of the actual amount of blood stock in the blood bank and to minimize human errors.The solution will provide a well-organized and coordinated sys tem for blood bank where the blood and donor records are managed more efficiently with better security and added automation functions in alerting the administrator when the blood bill is below par level and most the run out archetypes. In addition, the administrator can also trace back the donor responsible in case of reactive prove in blood transfusion and blood screening result. This system also creates a favourable and paperless environment for the blood bank in managing donors and processing blood stocks.The enrolment time for old donor is shortened as the records are recoverable from the system. Also the performance evaluation is possible using report generation facility. 2. 1 Product Perspective This system keep the track of all the actual amount of the blood stock in the blood bank to minimize the human errors. 2. 2 Product Functions 1. System will also maintain Blood Stock records and Discard register. 2. System will provide levels of operators for authentication purp ose. 3. System will provide an authentication form where the users will fill the details. 4.System will process the request of login. 5. System will stop 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 examination Interface, Blood Stock Interface, come forth Interface, conferrer allowance Interface and Statistics Interface. 8. Donor Registration Interface will take all the personal and medical exam details of donor and generate a quaint 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 unequivocal then discard register is updated 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 preposterous bag numbers for each prod uct. 13. It will generate alerts when the blood quantity is below par level and about the expired samples. 14. The System will move expired sample details to discard register and update blood stock repository. 15. In Issue Repository, system will check blood stock repository for availability. 16. If stocks are acquirable 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. All the transaction of the blood will be updated within a small stage 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. User Characteristics The user must withstand the basic knowledge of the computer system. It is not requisite that the user must have the knowledge of the computer hardware. System administrator, supervisor, sponsor and lab technicians. 2. 4 General Constraints * Blood bank employees ,donors 2. 5 Assumptions and Dependencies * The System will not allow any user with incapacitate username and invalid password. * The system should not provide administrative privilege to any customer. 3. Specific Requirements The systems should converge the below given requirements. 1. Operating System Windows XP Professional 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 cable and with child(p) 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 addresses to them. User Interfaces User Type Intended Interaction 1. presenter 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, validate 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 accruement test carried out and its result.If the test results are positive 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 prod uct details, date of collection, date of preparation, date of expiration, result of testing and generate 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 boasting 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. intention 1 Create unique id for donors. a. bring donor personal and medical information for spic-and-span donors. b. induce unique i d for each donor.Objective 2 Process authentication request. a. Accept donor id in case of regular donor. b. Retrieve 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. sustain stock details for issue. b. Update blood stock repository after(prenominal) 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. Provide it to the customer along with the date of economy 3. 5 Non-Functional Requirements 7. 1. 1 Availability * For the customers, the services available are Registration as a donor, placement of issue order. * For the ad ministrator, 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 consistency 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 have security to prevent unauthorized write/delete access. The donors details will not be disclosed while issuing. 3. 8 Logical Database Requirements The databases used by the system are * Donor database Blood stock database * Discard database * Account database User database The purpose of this database is to store 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. Th eir credentials will be saved in this particular database. Blood Stock database This database is used to maintain 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 rate 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 out of doors its accessing capability .