Seminar Topics & Project Ideas On Computer Science Electronics Electrical Mechanical Engineering Civil MBA Medicine Nursing Science Physics Mathematics Chemistry ppt pdf doc presentation downloads and Abstract

Full Version: Blood Bank Management System
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Blood Bank Management System
[attachment=27645]
INTRODUCTION
INFORMATION SYSTEM
It is an organized combination of people hardware, software communication network and data resources that collect transform and discriminates information in an organization.
People have relied on information system to communicate with each other using variety of physical devices(hardware), information processing instruction and procedure (software), communication channels (networks) and stored data (data resources).
INFORMATION SYSTEM RESOURCES
 People
 Data
 Software
 Hardware
 Networks
ACTIVITIES
 Input of data into information
 Processing of data into information
 Output of information products
 Storage of data
 Control of system performance
EXISTING SYSTEM
In early days, it was such that everything was done manually i.e. maintaining records, maintaining accounts and particulars. It is a burden and huge headache for the people to handle each and every minute detail. Moreover it is not possible for any human being to update thousands of information every day.
Thus it may ultimately land up to some dies – balance, which may affect the whole constitution.
NEED FOR COMPUTERIZATION
In modern days, due to the enhancements of computers, we can easily simplify our tasks. Modern computerization is the solution to the entire above problems. It needs only the updating of the new information/data into the computer. Only the things are that the user has to be perfect. A part from this, the user can easily detect the errors, if any, and there is no question of computer making mistakes. Thus, computerized database are really helpful for such big organizations like college.
LIMITATION OF EXISTING SYSTEM
1. Everything was done manually (only human being makes mistakes).
2. In big organizations, registers were maintained to record all the information.
3. The register may be damaged, stolen or it may get lost.
4. The records were maintained by a group of people (i.e. more manpower).
5. If any section goes wrong, all other sections get pulled up which in turn effect the whole organization.
6. Above all, it was very time consuming.
PROPOSED SYSTEM
1. Everything is computerized (computer does not make much mistakes).
2. There is no question of database getting lost or damaged, provide the user has to be perfect.
3. A single person is enough to maintain each and every record, provide the user has to be correct.
4. In case of any problem in any particular field, they can easily detect where the problem is and the computer update the database accordingly.
5. It saves the most valuable time of the users and the organizations.
SOFTWARE REQUIREMENT SPECIFICATION
DEFINITION

Software requirement specification is the beginning point of the development activity. Software requirement is one such area, to which a little importance was attached in the early days of Software development as the emphasis was in coding and design. The tacit assumption was that developers understood the problem clearly when it was explained to them. As system grew more complex, it becomes evident that the goals of the entire system couldn’t be easily comprehended.
Hence the needs for a rigorous requirement analysis phase arrive. Now for larger software system the requirement analysis is the most difficult and iterative activity.
The software project is initiated by the clients need. These needs are in mind of various people in the client organization. The requirement analyst has to identify the requirement after discussing with the people and understanding their needs. In situations where the software is to automate a currently manual process, most of the needs can be understood by observing the current practice.
Hence, identifying requirement involve specifying what some people have in their minds as the information in their minds is not formally sorted or organized. When inputs from multiple people are to be gathered, as in most cases, these inputs are likely to be inconsistent as well.
The SRS is a means of translating the ideas in the minds of the client into a formal document. Thus, the output of the phase is a set of formally specified requirements, which hopefully are complete and consistent, while the input has none of these properties. Clearly the process of specifying requirements cannot be totally formal. Any formal translation process producing a formula output must have a precise and unambiguous input.
The requirement specification phase consist of two basic activities
1) Problem or requirement analysis, and
2) Requirement specifications
PURPOSE OF SRS
There are three major parts in a new system:-
a) Client.
b) User.
c) Developer.
The requirements of the system that will satisfy the needs of the clients and the concerns of the users have to communicate to the developer. The problem is that, the developer usually doesn’t understand the client’s problem and applications area. This causes a communication gap between the parties involved in the development project.
The basic purpose of software requirement specification is to bridge this communication gap. SRS is a medium through which the client and user needs are accurately specified; Indeed, SRS forms the basis of software development. A good SRS should specify something very hard to achieve and involving tradeoffs and persuasion.
The introduction of software System offers strong and effective features such as providing new services, performing activation in a different manner to collecting data which were either impossible or unfeasible without a software system.
A good SRS provides many benefits. Some of the benefits are
1. An SRS established the basis for agreement between the client and supplier on what the software products will do.
2. An SRS provides a reference validation of the final product.
3. A high quality SRS reduce the development cost.