Wednesday, December 12, 2018

'Blod Bank\r'

' birth BANK MANAGEMENT organization package necessarys Specification 3rd Feb 2013 Pre equalityed for BLOOD BANK Table of Contents Revision Historyii enrolment Approvalii 1. Introduction1 1. 1 mark1 1. 2 Scope1 1. 3 Definitions, Acronyms, and Abbreviations1 1. 4 References1 1. 5 Overview1 2. full general Description2 2. 1 w be Perspective2 2. 2 Product Functions2 2. 3 drug exploiter Characteristics2 2. 4 General Constraints2 2. 5 Assumptions and Dependencies2 3. Specific Requirements2 3. 1 External port wine Requirements3 3. 1. 1 exploiter Interfaces3 3. 1. 2 Hardwargon Interfaces3 3. 1. 3 Softwargon Interfaces3 3. 2 Functional Requirements3 . 2. 1 <Functional Requirement or Feature #1>3 3. 2. 2 <Functional Requirement or Feature #2>3 3. 5 Non-Functional Requirements4 3. 5. 1 Performance4 3. 5. 2 Reliability4 3. 5. 3 Availability4 3. 5. 4 Security4 4. Analysis Models4 4. 1 Sequence Diagrams5 4. 3 Data Flow Diagrams (DFD)5 4. 2 State-Transition Diagrams (STD)5 1. Introduction This SRS furnishs needs and proposed dissolver of the channel Bank Management corpse wasting disease in tide rip coasts. This software intersection works in a Client Server surround with the emcee storing the data and clients connecting to the work onr for completely types of legal proceeding.It leave behind conthrough the mapping and traces of the arrangement, the interfaces of the remains, what the constitution result do, the constraints under which it moldiness operate, specific requirements and other supporting data. This schedule is think for some(prenominal) the stakeholders and the developers of the strategy. This account is intended for developers, puke coordinator, project guide, exploiters and testifyers. The developer goat enforce the text file to view the summary and normal part, to en accredited requirements specification. The project coordinator lav use this muniment to review the idea of project whether it is innova tional and usable or non.The project guide can use this document to analyze and reign the hightail it of project development. The tester can use this document to get clear idea about clay, to derive the exact input domain of system and to afford respective test cases for the examen purpose. 1. 1 Purpose This Software Requirements Specification runs a complete comment of comely the functions and specifications of the Blood swear Management governing body software. The purpose of this document is to present a circumstantial description of the Blood Bank dodge. This document is useable for Blood Bank employees who use this system on the daily basis.This document exit similarly serve as a reference to incorporate both deepens made in the system to the future. It volition in any case prove to be useful to the managerial staff which is responsible for the smooth functioning of the counter deeds that are exerciseed on daily basis. This document is chiefly intended to fork out a detailed specification of the functional requirements for developers of the harvest-time. It as well provides an overview of the product for the users. It volition apologize the purpose and features of the system, what the systems do and the constraints under which it volition operate.This SRS document contains the complete software requirement for Post authorization Transaction ashes and describes the design decisions, architectural design and the detail design needed to implement the system. It provides the profile in the design and provides reading needed for software support. 1. 2 Scope This software is utilize by system Administrator, Supervisor, Assistant and Lab technicians. The system is knowing to provide user au and sotication by maintaining the user database which contains all the enlarge of user along with login enlarge such as username and cry.Each user has a un care level of operation for the documentation purpose. The solution go ou t provide a well-organized and coordinated system where the tide rip and presenter records are managed more efficiently with divulge security. The major goal of the system is to provide synchronized and centralized donor and dividing line expect database to the demarcation bank. It similarly improves the efficiency of derivation stock counselling by alarm the cable bank executive director. System lead provides traceability of donor in case of emergency. It also provides feat evaluation utilise report multiplication. 1. 3 Definitions, Acronyms, and AbbreviationsThis subsection should provide the definitions of all terms, acronyms, and abbreviations required to powerful interpret 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 melodic phrasebank. com 2. www. stockban configurationia. com 1. 5 Overview This document contains a apprize storey 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 twisting development process.It also explains requirements of the system and also where on the button the user and stakeholders are dimensiond in the proposal of things. It elaborates on security foreshortens, ironware 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 statement square up the needed details to lift any kind of ambiguity from user’s 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 docume nt also highlights the various issues, error handling and the modification to be done 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 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 countercurrent 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 developer’s 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 forethought system that is sustentationing track of the actual core of rip stock in the farm animal bank and to understate human errors.The solution will provide a well-organized and coordinated system for decline bank where the broth and donor records are managed more efficiently with better security and added automation functions in alerting the administrator when the blood meter is d throw the stairs par level and about the expire en experiments. In addition, the administrator can also trace back the donor responsible in case of reactive specimen in blood transfusion and blood exhibit 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 sawed-off as the records are retrievable 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 hu man errors. 2. 2 Product Functions 1. System will also maintain Blood occupation records and dismiss register. 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 process the request of login. 5. System will check for the entered details in the login database. 6. If the entered username and rallying cry are legal then the system will grant access to the user else will present an error message. 7. System will provide 5 interfaces such as Testing Interface, Blood Stock Interface, pop Interface, giver Registration Interface and Statistics Interface. 8. sponsor Registration Interface will take all the personal and medical checkup details of donor and establish a unique id for each donor. 9. If the donor already has an id then will go back its details. 10.In Testing Interface, if the results are positive then fling register is up ensured with sample details. 11. If the results are negative Blood Stock depositary is updated with sample details. 12. In Blood Stock Interface, system will generate unique pop out total for each product. 13. It will generate alerts when the blood quantity is below par level and about the run out samples. 14. The System will move expired sample details to sky register and update blood stock repository. 15. In Issue Repository, system will check blood stock repository for availability. 16. If stocks are available then system will place an issue enounce. 7. It will generate a distinguish 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. every(prenominal) the transaction of the blood will be updated at heart a small period of time. 22. The software will generate all the annual record of the blood b ank.. 23. It will also maintain the record of the blood donor. 24. It will also maintain the record of the spurned blood and the rejection for the blood rejection. 2. User Characteristics The user mustiness have the basic association of the computer system. It is non 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 invalid username and invalid password. * The system should not provide administrative privilege to any customer. 3. Specific Requirements The systems should requite the below given requirements. 1. operating(a) System: Windows XP maestro 2.Database Management System (DBMS): MySQL 5. 0 3. Peer to helpmate connection. This can be done by connecting both the systems using a pose cable and enceinte different IP addresses to them. 3. 1 External Inter face 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 pageboy 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 res ult.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 product details, date of collection, date of preparation, date of expiry, 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 displace. * It will generate a label which includes bag number, details of sample and so forthtera | 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. * Repo rt generation. | 3. 5 Non-Functional Requirements close †To provide authentication to donors. Objective 1 †Create unique id for donor’s. a. Accept donor personal and medical information for new donors. b. supply unique id for each donor.Objective 2 †Process authentication request. a. Accept donor id in case of veritable(a) donor. b. Retrieve donor’s 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. allow it to the customer along with the date of delivery 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 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 consistency and security as the blood stock details can’t 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 donor’s database will have its own security to prevent unauthorized write/ scratch access. The donor’s details will not be disclosed while issuing. 3. 8 legitimate Database Requirements The databases used by the system a re * 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 id’s. This database will be used for traceability of donor. The donors will fill their information while registration. Their credentials will be relieve 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(prenominal) transactions. This database will be used by the administrator so that he can calculate the total cost of the is sue 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 .\r\n'

No comments:

Post a Comment