1.

1 DESCRIPTION OF THE ORGANIZATION

About the Organization:

The Indian Red Cross is a voluntary humanitarian organization having a network of over
700 branches throughout the country, providing relief in times of disasters/emergencies
and promotes health & care of the vulnerable people and communities. It is a leading
member of the largest independent humanitarian organization in the world, the
International Red Cross & Red Crescent Movement.

The Mission of the Indian Red Cross is to inspire, encourage and initiate at all times all
forms of humanitarian activities so that human suffering can be minimized and even
prevented and thus contribute to creating more congenial climate for peace.

About the society

Indian Red Cross Society (IRCS) was established in 1920 under the Indian Red Cross
Society Act and incorporated under Parliament Act XV of 1920. The act was last
amended in 1992 and of rules was formed in 1994.

The IRCS has 35 State / Union Territories Branches with their more than 700 districts
and sub district branches.

His Excellency the President of India is the President and Hon'ble Union Health Minister
is the Chairman of the Society.

The members of the Managing Body elect the Vice Chairman

The National Managing Body consists of 19 members.

The Chairman and 6 members are nominated by the President. The state and union
territory branches through an electoral college elect the remaining 12.

The Managing Body is responsible for governance and supervision of the functions of the
society through a number of committees.
The Secretary General is the Chief Executive of the Society.

Principles of the Organization

Humanity : The International Red Cross and Red Crescent Movement, born of a desire
to bring assistance without discrimination to the wounded on the battlefield, endeavors, in
its international and national capacity, to prevent and alleviate human suffering wherever
it may be found. Its purpose is to protect life and health and to ensure respect for the
human being. It promotes mutual understanding, friendship, cooperation and lasting
peace amongst all peoples.

Impartiality: It makes no discrimination as to nationally, race, religious beliefs, class or

political opinions. It endeavors to relieve the suffering of individuals, being solely by
their needs, and to give priority to the most urgent cases of distress.

Neutrality: In orders to enjoy the confidence of all, the Movement may not take sides in
hostilities or engage in controversies of a political, racial, religious or ideological nature.

Independence: The Movement is independent. The National Societies, while auxiliaries

in the humanitarian services of their governments and subject to the laws of their
respective countries, must always maintain their autonomy so that they may be able at all
times to act in accordance with the principles of the Movement.

Voluntary service: It is voluntary relief movement not prompted in any manner by

desire for gain.

Unity : There can be only one Red Cross Or Red Crescent in any one country. It must be
open to all. It must carry on its humanitarian work throughout its territory.

Universality : The International Red Cross and Red Crescent Movement, in which all
societies have equal status and share equal responsibilities and duties in helping each
other, is worldwide.
Programs and Activities:

The Indian Red Cross's programs are grouped into four main core areas: Promoting
humanitarian principles and values; Disaster response; Disaster preparedness; and Health
and Care in the Community.

Red Cross promotes the Humanitarian values, which encourage respect for other human
beings and a willingness to work together to find solutions to problems. From the seven
fundamental principles, the movement aims to influence the behavior of all the people.

Other Major activities includes : hospital services, blood bank, HIV/AIDS programs,
home for disabled servicemen ,vocational training centers, tracing activities, maternity ,
child and family welfare, nursing, junior red cross activities, preparedness and prevention
of communicable & infectious diseases, relief operations in fire, railway & other
accidents and events .

Promoting Fundamental Principles and Humanitarian Values

The International Committees of the Red Cross and National Societies have a consistent
and inspirational approach to promoting humanitarian values and the seven Fundamental
Principles of the Red Cross and Red Crescent movement.

The aim is to influence the behavior of the people we work with, through a better
understanding of Fundamental Principles and humanitarian values. The three main target
groups are those working within Red Cross and Red Crescent societies, public and
private authorities and members of the communities where we work.

The main priorities are:

Developing a better understanding internally

New initiatives are being taken to ensure that Red Cross Red Crescent volunteers and
staff understand and act based on the Fundamental Principles in their work with
vulnerable people in times of peace, disaster or armed conflict. Training includes the
legal and ideological basis of the Red Cross Red Crescent, decision-making processes,
mandates, as well as communications and relations with others.

Influencing behavior in the community.

The values that the Movement has formally stated to be of importance for promotion are:

• The protection of life, health and human dignity

• Respect for the human being

• Non-discrimination based on nationality, race, gender, religious beliefs, disability,

class or political opinions

• Mutual understanding, friendship, cooperation and lasting peace among people

• Service by volunteers

Disaster Relief

The Indian sub continent is highly prone to droughts, floods and other natural calamities.
Among the states, as many as 22 states are said to be multi-disaster-prone regions.

Among all the disasters that occur in India, floods are the most devastating. Over 40
million hectare of land has been identified as flood prone. An average of 18.6 million
hectare of land is flooded annually. The Ganga-Brahmaputra-Meghna basin, which
carries 60 % of the nation's total river flow, causes floods.

Indian Red Cross with the assistance of the Federation and other National Societies reach
humanitarian services to the victims of calamities.
Disaster Response

Poverty and war. Flooding and drought. Earthquakes and environmental disasters.
Billion people were affected by disasters in the past. The impact is high; leaving people
traumatized by the death of family and friends, their lives devastated by the loss of
homes, possessions and stocks of food. Disasters are becoming more complex, with
increasingly long-term consequences as they strike countries with economic problems or
political instability, and weaken already fragile public services such as health, water and
sanitation. Recurrent crises, such as floods year after year, give people and their crops no
time to recover.

Disaster Preparedness

The Indian Red Cross Society (with Federation support) initiated a nation-wide
Community Based Disaster Preparedness (CBDP) training program in 1999 after a series
of awareness raising workshops between 1996 and 1998. In 2000, the National Society
convened a national strategic planning workshop attended by 19 State Branches from
which a strategic plan for DP/DR (2004-2007) was formulated and its activities are
continuing. The vision of the programmer is institutional strengthening, training and
knowledge sharing through the establishment of a Disaster Management structure,
programs for strengthening and expanding community based disaster preparedness
(CBDP) in disaster affected areas.

INTRODUCTION

Nowadays IT is backbone of business sector. In today’s scenario, all the sectors are
adopting the IT techniques for simplifying their work and solving the day-to-day
Problems. Technology is serious stuff. It empowers the organization and its stakeholders
to be effective. But it can’t be defined simply by bells and whistles. Effective Technology
requires a caring, functional relationship behind it. As more-robust technology is
implemented, it improves an enterprise’s ability to adapt to market charges.
Business organization these days concentrate on accountability, responsibility and
communication to increase throughput and maximum utilization of resources. People
working in different departments all should see same information. When one department
finishes with the data entry, it is automatically routed to the next department. These all
are also the requirements of publishing houses. If we talk about manual or semi-
automated system, manual system is very time consuming and prone to errors and later is
less time consuming as compare to manual but it’s also prone to errors. In today’s fast-
track era where “Time is money”, one has to fully automate the existing system to beat
the competitive world.

Since the advent of computers in the last two decades, every organization is going under
the process of computerization. The computerization has many benefits. Primarily, a
computer is helpful in four major aspects of any kind of organization:

• Time Efficiency
• Cost Effective
• Huge data storage capacity and
• Simple operation

ABOUT THE PROJECT

Whenever we develop software or project certain hardware and the

programmer for developing the project is using software. The hardware and
software to be used by the programmer for developing the project should be
such that it would result in the development of a project, which would satisfy
all the basic needs for which the programmer has created the project
OBJECTIVES:

Objective of this project is to computerize the daily working of the BLOOD BANK. This
project will present the BLOOD result and also show the future applicant and
transactions become very fast. Objective of this software is to computerize the BLOOD
BANK MANAGEMENT SYSTEM , so that the working of the management become
fast and there should not be any mistake in remembering information of availability
number of copies of the books . It keeps details of all the students and modifying their
records .The project provides such user friendliness and easy understandability that even
a novice user will find it easy to use the package and grasp its essence. Main objectives
of Project:

To make the existing system more efficient.

To provide a user friendly enviroment where user can be serviced better.

Make functioning of library faster.

Provide a system where the library staff can catch defaulters and not let them escape.

To minimize the loss done to books.

SIGNIFICANCE OF THE PROJECT:

1.Through the working of a computerized system one can avoid the obvious
complications arising from innumerable aspects.

2. The maintenance, addition, deletion or modification of an existing record becomes a

work regarding only a few seconds using a computerized system.

3. This will not only increase the efficiency and accuracy of the organization but will
also prove to be a massive timesaving factor to it.

4. Computer can easily auto generate to make the entry(s) easily

OVERVIEW

People Details: The new proposed system stores and maintains all the details of the
donors and the recipients of blood.
1. Updations: The new proposed system automatically update the status of donors,
recipients, available blood groups etc. and it is very fast and accurate.
2. Registers: There is no need of keeping and maintaining registers manually. It
remembers each and every record and we can get any report related to any blood
group, blood donor or blood available at any time.
3. Speed: The new proposed system is very fast with 100% accuracy and saves time.
4. Manpower: The new proposed system needs less manpower. Less people can do the
large work as everything is done on computers, which makes easier for us to maintain
a database.
5. Calculations: The new proposed system calculates blood available, units of blood
given, units of blood received etc. It checks whether the person giving blood is
suffering from some disease or not. If not then it calculates the fitness level of that
person automatically and then only the person is allowed to give the blood

TOOLS AND ENVIRONMENT USED

The present software product, Library Management System, has been developed by using
following resources:

HARDWARE:

Hardware is the term given to machinery itself and to various individual pieces of
equipment. It refers to the physical devices of a computer system. Thus the input, storage,
processing control and output devices are hardware.
PROCESSOR: 300 MHz Intel Pentium IV Processor comparable.

RAM : 4GB

HDD : 24 MB free hard disk space plus additional space to hold.

CD-ROM : 52 X

MONIYOR : 14 inches Color Monitor

KEYBOARDS: 104 Keys Keyboards

PRINTER : HP DeskJet 670 C

SOFTWARE:

Software means a collection of program where the objective is to enhance the capabilities
of the hardware machine.

The following paragraph defines the software of the proposed system development.

Operating System : Windows XP

Front end Tool : C++

Back end : File handling techniques in C++

Documentation software: Microsoft Word

FRONTEND

SOFTWARE DESCRIPTION

PLATFORM:

C++ is an object-oriented programming language, and its object-oriented features are

highly interrelated. In several instances, this interrelatedness makes it difficult to describe
one feature of C++ without implicitly involving several others. The object-oriented
features of C++ are, in many places, so intertwined that discussion of one feature implies
prior knowledge of one or more other ones.

Object-Oriented Programming:

Since object-oriented programming (OOP) drove the creation of C++, it is necessary to

understand its foundational principles. OOP is a powerful way to approach the job of
programming. Programming methodologies have changed dramatically since the
invention of the computer, primarily to accommodate the increasing complexity of
programs. For example, when computers were first invented, programming was done by
toggling in the binary machine instructions using the computer's front panel. As long as
programs were just a few hundred instructions long, this approach worked. As programs
grew, assembly language was invented so that a programmer could deal with larger,
increasingly complex programs, using symbolic representations of the machine
instructions. As programs continued to grow, high-level languages were introduced that
gave the programmer more tools with which to handle complexity.

To support the principles of object-oriented programming, all OOP languages have three
traits in common: encapsulation, polymorphism, and inheritance.

Encapsulation

Encapsulation is the mechanism that binds together code and the data it manipulates, and
keeps both safe from outside interference and misuse. In an object-oriented language,
code and data may be combined in such a way that a self-contained "black box" is
created. When code and data are linked together in this fashion, an object is created. In
other words, an object is the device that supports encapsulation. Within an object, code,
data, or both may be private to that object or public. Private code or data is known to and
accessible only by another part of the object. That is, private code or data may not be
accessed by a piece of the program that exists outside the object. When code or data is
public, other parts of your program may access it even though it is defined within an
object. Typically, the public parts of an object are used to provide a controlled interface
to the private elements of the object. For all intents and purposes, an object is a variable
of a user-defined type. It may seem strange that an object that links both code and data
can be thought of as a variable. However, in object-oriented programming, this is
precisely the case. Each time you define a new type of object, you are creating a new
data type. Each specific instance of this data type is a compound variable.

Polymorphism

Object-oriented programming languages support polymorphism, which is characterized

by the phrase "one interface, multiple methods." In simple terms, polymorphism is the
attribute that allows one interface to control access to a general class of actions. The
specific action selected is determined by the exact nature of the situation. A real-world
example of polymorphism is a thermostat. No matter what type of furnace your house has
(gas, oil, electric, etc.), the thermostat works the same way. In this case, the thermostat
(which is the interface) is the same no matter what type of furnace (method) you have.
For example, if you want a 70-degree temperature, you set the thermostat to 70 degrees.
It doesn't matter what type of furnace actually provides the heat. This same principle can
also apply to programming.

Inheritance

Inheritance is the process by which one object can acquire the properties of another
object. This is important because it supports the concept of classification. If you think
about it, most knowledge is made manageable by hierarchical classifications. For
example, a Red Delicious apple is part of the classification apple, which in turn is part of
the fruit class, which is under the larger class food. Without the use of classifications,
each object would have to define explicitly all of its characteristics. However, through the
use of classifications, an object need only define those qualities that make it unique
within it s class. It is the inheritance mechanism that makes it possible for one object to
be a specific instance of a more general case. As you will see, inheritance is an important
aspect of object-oriented programming.
1.5 BACKEND:

A file in C++ is a sequence of bytes. When a file is opened, a stream object is associated
with the filename. The header file fstream.h contains the definitions for the stream
classes ofstream (output file stream), ifstream (input file stream), and fstream
(input/output file stream).

Creating a Sequential File The ofstream constructor may be used to create a sequential
file. The constructor can take two arguments, the name of the file, and the mode to open
the file.

C++ has two basic classes to handle files, ifstream and ofstream. To use them, include the
header file fstream.h. Ifstream handles file input (reading from files), and ofstream
handles file output (writing to files). The way to declare an instance of the ifstream or
ofstream class is:

Ifstream a_file;
//or
ifstream a_file("filename");

The constructor for both classes will actually open the file if you pass the
name as an argument. As well, both classes have an open command
(a_file.open()) and a close command (a_file.close()). It is generally a good
idea to clean up after yourself and close files once you are finished.

The beauty of the C++ method of handling files rests in the simplicity of the
actual functions used in basic input and output operations. Because C++
supports overloading operators, it is possible to use << and >> in front of the
instance of the class as if it were cout or cin.
 QUESTIONAIRE :

The Manual Procedure of a BLOOD BANK MANAGEMENT SYSTEM was observed.

This was essential to analyze the flow of information and the actual usage of software
programs. There may customize procedure adapted by the BLOOD BANK management.
Those procedures must study deeply, to satisfy the client. This was helpful to design the
reporting requirements from the software.

For the purpose of designing an effective software package, a Questionnaire was

prepared and different Management Staff were interviewed to access their requirement
and how the proposed software can benefit them.

Given below are the questions that were put to different people: -

A) Does it take more time to register information about the donor and the receiver?
B) Is the blood donated and issued during the year, visible?
C) How long does it take to process a report ?
D) Is it possible for different level of staff to view related information?
E) Can one get the list of all employees in different departments?
F) Do you think Computerization will improve things?

Different people had different answers to the above questions.

However a ‘YES’ was received as an answer to the final question. This boosted our
confidence in the selection of the project.

Project Planning
Project planning is part of project management, which relates to the
use of schedules such as Gantt charts to plan and subsequently
report progress within the project environment.

Initially, the project scope is defined and the appropriate methods

for completing the project are determined. Following this step, the
durations for the various tasks necessary to complete the work are
listed and grouped into a work breakdown structure. The logical
dependencies between tasks are defined using an activity network
diagram that enables identification of the critical path. Float or
slack time in the schedule can be calculated using project
management software. Then the necessary resources can be
estimated and costs for each activity can be allocated to each
resource, giving the total project cost. At this stage, the project plan
may be optimized to achieve the appropriate balance between
resource usage and project duration to comply with the project
objectives. Once established and agreed, the plan becomes what is
known as the baseline. Progress will be measured against the
baseline throughout the life of the project. Analyzing progress
compared to the baseline is known as earned value management

WORK DISTRIBUTION AMONG MEMBERS :

GANTT CHART

The Gantt chart is the standard format for displaying a schedule

graphically. It consists of a horizontal bar chart with time as a
horizontal axis and either resources, job or orders as the vertical
axis. Individual operations are displayed as horizontal bars in the
chart, indicating the time at which the job begins and ends. Many
variations on the Gantt chart exits to display additional kinds of
information.
Gantt chart can be drawn physically on paper, but now days are
usually implemented through computer software

A Gantt chart is a horizontal bar chart developed as a production

control tool in 1917 by Henry L. Gantt, an American engineer and
social scientist. Frequently used in project management, a Gantt
chart provides a graphical illustration of a schedule that helps to
plan, coordinate, and track specific tasks in a project.

Gantt charts may be simple versions created on graph paper or more

complex automated versions created using project management
applications such as Microsoft Project or Excel.

A Gantt chart is constructed with a horizontal axis representing the

total time span of the project, broken down into increments (for
example, days, weeks, or months) and a vertical axis representing
the tasks that make up the project (for example, if the project is
outfitting your computer with new software, the major tasks
involved might be: conduct research, choose software, install
software). Horizontal bars of varying lengths represent the
sequences, timing, and time span for each task. Using the same
example, you would put "conduct research" at the top of the vertical
axis and draw a bar on the graph that represents the amount of time
you expect to spend on the research, and then enter the other tasks
below the first one and representative bars at the points in time
when you expect to undertake them. The bar spans may overlap, as,
for example, you may conduct research and choose software during
the same time span. As the project progresses, secondary bars,
arrowheads, or darkened bars may be added to indicate completed
tasks, or the portions of tasks that have been completed. A vertical
line is used to represent the report date.
Gantt charts give a clear illustration of project status, but one
problem with them is that they don't indicate task dependencies -
you cannot tell how one task falling behind schedule affects other
tasks. The PERT chart, another popular project management charting
method, is designed to do this. Automated Gantt charts store more
information about tasks, such as the individuals assigned to specific
tasks, and notes about the procedures. They also offer the benefit of
being easy to change, which is helpful. Charts may be adjusted
frequently to reflect the actual status of project tasks as, almost
inevitably; they diverge from the original plan.

GANTT CHART

Chap. 2

SYSTEM ANALYSIS

The analysis of system is done on the basis of the requirement gathered. System Analysis
is the main task, which means analyze how much time it takes to complete & how much
cost is encountered during the development of the software. System Analysis is done to
analyze the hardware & software requirements for the development of the project. The
system analysis is done before the development of the project.

Systems analysis and design refers to the process of examining a business situation with
the intent of improving it through better procedures and methods. Systems development
can generally be thought of as having two major components: Systems Analysis and
Systems Design. Systems design is the process of planning a new system or replace or
complement an existing system. But before this planning can be done, we must
thoroughly understand the existing system and determine how computers can best be
used to make its operation more effective. Systems analysis, then, is the process of
gathering and interpreting facts, diagnosing problems and using the information to
recommend improvement to the system. In brief, we can say that analysis specifies what
the system should do. Design states hew to accomplish the objective.

1: SYSTEM ANALYSIS PHASE: -

The analysis phase defines the requirements of the system, independent of how these
requirements will be accomplished. This phase defines the problem that the customer is
trying to solve. The deliverable result at the end of this phase is a requirement document.
Ideally, this document states in a clear and precise fashion what is to be built. This
analysis represents the “what” phase. The requirement document tries to capture the
requirements from the customer's perspective by defining goals and interactions at a level
removed from the implementation details.
The analysis phase is a problem-solving phase. The problem is that in manual restaurant
record keeping system, excessive staff employment is required, extremely time
consuming process is involved, inconveniences to both customers as well as to the
manager. So, while analyzing I found many requirements expected from the system like:
- to save time of both the manager as well as the customer of the restaurant, to perform
automatic calculation of bill according to the purchased made by the customer. To reduce
the whole paper work involved in restaurant, which otherwise without computerization
would very tedious to maintain and keeping it update. To make easy work procedure
which otherwise monotonous and tedious and involves at least two staff members, now
can be managed and handled by only one person.
So, the above description was the requirements of the system and the proposed system
was expected to perform these functions.
The requirement document may be expressed in formal language. Traditionally, the
requirement document is written in English or another written language. The
requirement document does not specify the architectural or implementation details, but
specifies information at the higher level of description. The problem statement, the
customer's expectations, and the criteria for success are examples of high-level
descriptions. There is a fuzzy line between high-level descriptions and low-level details.
Sometimes, if an exact engineering detail needs to be specified, this detail will also
appear in the requirement document. This is the exception and should not be the rule.
These exceptions occur for many reasons including maintaining the consistency with
other established systems, availability of particular options, customer's demands, and to
establish, at the requirement level, a particular architecture vision. An example of a low-
level detail that might appear in the requirement document is the usage of a particular
vendor's product line, or the usage of some accepted computer industry standard, or a
constraint on the image size of the application. There is a fundamental conflict between
high levels and low levels of details. The requirement document states what the system
should accomplish, independent of many of the details. The discovery process used in
establishing the requirements during the analysis phase is best described as a refinement
process than as a levels-of-detail process.
Top-down and bottom-up approaches force a greater distinction between high levels and
low levels of detail. Interactive approaches lead to the refinement of those details.
Traditionally, the requirement document describes the things in the system and the
actions that can be done on these things. Things might be expressed as objects in an
object-based technology where data and algorithms are hidden behind hierarchical-
polymorphic methods. Alternatively, things might be expressed as services accessing
databases in a functional approach where data is a fundamentally different concept than
functions. In general, the description of things in the system can be much more general
and not confined to a particular technology. In a more general sense, this document
describes the ontology that is the noun phrases and the verb phrases that will become the
guidelines for defining the application specific protocol.
The requirement descriptions of the things in the system and their actions do not imply an
architecture design rather a description of the artifacts of the system and how they
behave, from the customer's perspective. Later, in the design phase, these requirement
descriptions are mapped into computer science based primitives, such as lists, stacks,
trees, graphs, algorithms, and data structures.
The description of the abstraction of the noun phrases and the verb phrases are not bound
to the use of a written human language. Most written human languages are too vague to
capture the precision necessary to build a system. Alternative descriptive mechanisms
based on mathematical logic are sometimes more suitable but much more difficult to
accomplish. Mathematical logic provides a scientific foundation for precisely expressing
information. However, frequently in the real world, a precise description is not attainable.
Again the requirement document should state in a clear and precise fashion what is to be
built. The definitive mechanism to author such a document, either formally or informally,
has yet to be developed, although reasonable success has been achieved with existing
methods including CASE tools and tools based on mathematical logic.
Later, in the design phase, the very important decomposition of the problem leads to the
development of data structures and algorithms. A functional decomposition for a
distributed environment leads to a natural split of the data structures and algorithms.
Examples include distributed client-server systems, where a database holds the data in a
server while the algorithms manipulating the data reside on the client. An object-based
decomposition leads to a natural joining of data structures and algorithms forming objects
with methods. The requirement documents should be independent of the decomposition
technique. The analysis team develops the requirement document, which talks about
things and actions on things. This document should also include states, events, typical
scenarios of usage, and atypical scenarios of usage.
REQUIREMENT ANALYSIS: -
A software project is initiated by the client’s need. In the beginning these needs are in the
minds of various people in the client organization. The requirement analyst has to
identify the requirement by talking to these people and understanding their needs.
Hence identifying requirements necessarily involves a specifying what some people have
in their minds. As the information in their minds by nature is not formally stated or
organized, the input to the software requirement specification is inherently informal and
imprecise, and it is likely to incomplete when inputs from multiple people are to be
gather, as is often the case these inputs are likely to be inconsistent as well.

Regardless of how the requirement process precedes it ultimately ends with the software
requirement specification.
(a) PROBLEM ANALYSIS: -
In this project we have tried to simulate the functioning of “BLOOD BANK PROJECT.”
using C++. This system automates the process of “BLOOD BANK PROJECT”. The
system allows user to add items into the system and provide list of all items in the system.
The system also allows user to modify and delete into the system.
(b) PROPOSED SYSTEM ANALYSIS: -
In this system Analysis, we have carefully study all the requirements of a
BLOOD BANK and the system is designed in such a manner so the system
should be user friendly.
(c) ADVANTAGES OF THE PROJECT: -

This project on BLOOD BANK system tries to provide some amount of

automation in the system. The objective of the project is to helP BLOOD
BANK Data collection in making their business more efficient. It is also
believed that automated system might be an added attraction for their
potential customers. It will also show the attitute of the management that
they are aware to the newly introduced technologies and ready to adopt
them.
The system provides a very good user interface to make the system user
friendly. The system also provides features to gracefully come out from the
system at any time to the main menu and select any other option or can exit
from the system.

2.1 Description Of Information System

Block Diagram

DONOR

DONOR’S BLOOD GROUP

DETAILS DETAILS

DONATION
UNITSPROCESS
With
OF BLOOD Details

RECEIVER
ISSUE
PROCESS REPORTS
DETAILS
Invoice

RECEIVER

Figure 2: Block Diagram

2.2 Identification Of Process

Table 3: Process of the Project

DONOR Name, Address,Blood group, Units OF Blood Donated

RECEIVER Name, , Address,Blood group, Units OF Blood Needed
DETAILS

2.3 Identify the “Input to” & “Output of” each process

DONATION PROCESS : It is the process of donating blood .It also keeps records of
number of units of blood donated

ISSUE PROCESS :It is the process of issuing blood .It also keeps records of number of
units of blood issued

GENERATION OF REPORTS :It generates the reports of the donation process and the
issue process .

CHAP. 3

FEASIBILITY STUDY

The process followed in the determination of, whether or not a project is worth doing is
called a feasibility analysis. This type of study determines if a project can and should be
taken or not. Once it has been determined, the analyst can go ahead and prepare the
project specifications which finalize the project requirements. The contents and
recommendations of such a study will be used as a sound basis for deciding whether to
proceed, postpone or cancel the project.
Steps in feasibility analysis

Eight steps are involved in the feasibility analysis. They are:

1. Form a project team and appoint a project leader.

2. Prepare system flowcharts.
3. Enumerate potential proposed systems.
4. Define and identify characteristics of proposed system.
5. Determine and evaluate performance and cost effectiveness of each proposed
system.
6. Weight system performance and cost data.
7. Select the best-proposed system.
8. Prepare and report final project directive to management

Type of feasibilities

1. Economic Feasibility

Economic analysis is the most frequently used technique for evaluating the effectiveness
of a proposed system. More commonly known as cost / benefit analysis; in this procedure
we determine the benefits and savings that are expected from a proposed system and
compare them with costs. We found the benefits outweigh the costs; we take a decision to
design and implement the new proposed system.

It is very essential to ascertain the cost, which is to incur for developing the
project, before starting the development of the project. If the benefit, which is to be
accrued by developing the software, exceeds the cost to be incurred for developing the
project by a fair amount of margin, then only the software should be developed. The
process of cost and benefit analysis is not only limited prior to the time period of
development of the project, but this process is a continuous process, and it keeps on
going during the entire life cycle of the software.
 ANALYSIS OF COST: -

The programmer has done the analysis of cost of the project named “Blood Bank
Management” in a very effective manner. According to the programmer, the total cost
involved in the development and implementation of the software at the client site would
be around Rs. 50000. This is so, as if the WORK .is manual, a computer system is to be
purchased to implement the project at the business. The computer system would cost
around Rs.50000, the cost involved in the development of the project would be around
Rs.10000, the cost involved in the purchase of software required for implementing the
project would be around Rs.5000, and above all the cost of training the manager to use
the software is around Rs.5000 as the manager is not familiar with computers.

ANALYSIS OF BENEFIT: -

As it is necessary to do cost analysis of the developed project, it is also very

essential to do benefit analysis along with it. The programmer has done the analysis of
the benefit arising from the use of the software named “Blood Bank Management.” in a
very effective way. The points which the programmer has kept in mind while performing
the task of benefit analysis of the software are as follows:-

(i) Stationery Cost: -

The use of stationery in the day-to-day functioning of the restaurant is on a large
scale. Thus, the cost of purchasing the stationery for the business .is also very
high. But, since after the implementation of software it would become fully
computerized, this step would save a big amount of money, which is previously
used for purchasing the stationery for the business. Now, all the work for which a
large amount of stationery was being used previously can now be done on the
computer.
(ii) Manager Assistants Salary: -
In a restaurant, as there are number of activities involved in the day-to-day
working, the workload becomes so much that the owner of the Blood Bank
Management has to keep two or more assistants along with the Manager. This
step increases the financial burden of the owner. Now, the owner has to pay the
salary of assistants along with the Manager’s salary. But, since after the
implementation of the software, the whole of the work, which is previously spread
over large number of files, becomes computerized and centralized to a single
computer, the work can now be handled by a single person thus saving the cost of
employing the manager assistants.

Thus, by doing the cost and benefit analysis of the software, we find that there are more
benefits arising by using the software as compared to the cost involved in the
development and implementation of the software

2. Technical Feasibility

This is concerned with specifying equipment and software that will successfully satisfy
the user requirement. The technical needs of the system may vary considerably, but might
include:

· The facility to produce outputs in a given time.

· Response time under certain conditions.

· Ability to process a certain volume of transaction at a particular speed.

· Facility to communicate data to distant location.

After examining technical feasibility, we give more importance to the configuration of

the system than the actual make of hardware. The configuration gives the complete
picture about the system's requirements: Ten to twelve workstations are required; these
units should be interconnected through LAN so that they could operate and communicate
smoothly. They should have enough speeds of input and output to achieve a particular
quality of printing.

3. Operational Feasibility

It is mainly related to human organizational and political aspects. The points to be

considered are:

· What changes will be brought with the system?

· What organizational structures are disturbed?

· What new skills will be required? Do the existing staff members have these skills?

· If not, can they be trained in due course of time?

Generally project will not be rejected simply because of operational infeasibility but such
considerations are likely to critically affect the nature and scope of the eventual
recommendations.

For operational feasibility study we appointed a small group of people who are familiar
with information system techniques, who understand the parts of the business that are
relevant to the project and are skilled in system analysis and design process.

4. Social feasibility

Social feasibility is a determination of whether a proposed project will be acceptable to

the people or not. This determination typically examines the probability of the project
being accepted by the group directly affected by the proposed system change.

5. Management feasibility
It is a determination of whether a proposed project will be acceptable to management. If
management does not accept a project or gives a negligible support to it, the analyst will
tend to view the project as a non-feasible one.

6. Legal feasibility

Legal feasibility is a determination of whether a proposed project infringes on known

Acts, Statutes, as well as any pending legislation. Although in some instances the project
might appear sound, on closer investigation it may be found to infringe on several legal
areas.

6. Time feasibility

Time feasibility is a determination of whether a proposed project can be implemented

fully within a stipulated time frame. If a project takes too much time it is likely to be
rejected.
CHAP 4

System Requirement Specification

SRS is the acronym of system requirement specification the it is a document which

should list all the term conditions and functionality that the customer aspect from the
system. It also contains any condition that link to the data and the environment in which
the system lives or performs operation.
SRS contains all visible attribute of the system so this document must be
unambiguous consistent and complete as much as possible.
SRS is produced at the culmination of analysis task. It is the document that
following information.

• introduction
• information Description
• Function Description
• Behavior Constrain
• Performance constrain Appendix
• Bibliography

Now I include following listed requirement that I feel to be needed in the classification of
our web based online Database of Journals.

Introduction:- it deals the goals and objective of the system. The online Database of
journals is a system in which the various records are kept and much transaction takes
place everyday. The records of journals are also maintained.

Information description:- This part of the SRS describes the scope of the software, what
exactly software must solve.
 In online Database of journals the information about the
journals stored in the computer. The information about the free user and paid user.
Function Description: - In this function the records are maintained regarding Train
Details along with Reservation Of Train Ticket.

Behavioral Description:- In behavioral description part the system are examined. The
operation invoked after the external events like enquiry made by user, updating or entry
Of the record etc.
Firstly the data input in computer regarding site in Railway Reservation
The proper security will be provided in the software. There will be reservation of Ticket
PNR status, Train Schedule, search Train.

Bibliography:- In the course of development of the proposed website the information

will
Be collected from various documents and websites to synchronize the integrity of the
Contents present in the website. Not only this we have also taken the help of so many
Railway Reservation site.

Appendix:- To specify the online learning here we have to use various types of tabular
Data, charts and other material during the course of software development. So that every
Use or client could know that the real data references. These all will be included in report
Generation after the development of software.
FLOW CHART

START

1. DONATE
BLOOD
2. ISSUE BLOOD MENU
3. IMIDIATE
STATUS
4.REPORT
5. QUIT
Enter yourCh
Input Choice:

If Y
1
Ch=1

If Y
2
Ch=2

If Y 3
Ch=3

Y 4
N N
 Y If N If
STOP Ch=6 Ch=4

Open file Donor.dat in

append mode.

Ask the donor details .

Save it in the file

MENU
 2

Open file Patient.dat in

append mode.

Ask the Patient details.

Save it in the file

MENU
 3

Open file Blood.dat in

read only mode.

Read data from file and

Blood information.

if Y
eof MENU

switch to next record

 4

Display the Report Sub

Menu

MENU

DATA FLOW DIAGRAM

Data flow diagrams are commonly used during problem analysis. Data flow diagrams are
quite general and not limited to problem analysis for software requirement specification.

A DFD shows the flow of data through a system. It views a system a function that
transforms the inputs into desired outputs. Any complex system does not perform this
transformation into a single step and a data will typically undergo a series of
transformation before it becomes an output. The DFD aims to capture the transformations
that take place within a system to the input data so that eventually the output data is
produced.
The agent that performs the transformation of data from one state to another is called a
process. So, a DFD shows the movement of data through the different transformations or
processes in the system. Named circles show the processes and data named arrows
entering or leaving the bubbles represent flows.

Process Activity

The rectangle represents a source and sink and is a net originator or consumer of data. A
source or sink is typically outside the main system of study.

Originator or Consumer of data

All external files are shown as a labeled straight line.

File name

The need ofr multiple data flows by a process is represented by a “*” between the data
flows.the symbol represents the AND relationship.for example, if there is a “*” between
the two input data flows A and B for a process,it means that A AND B are needed for the
process.

*
B

CHAP 5

SYSTEM DESIGN
The systems objectives outlined during the feasibility study serve as the basis
from which the work of system design is initiated. Much of the activities
involved at this stage is of technical nature requiring a certain degree of
experience in designing systems, sound knowledge of computer related
technology and thorough understanding of computers available in the market
and the various facilities provided by the vendors. Nevertheless, a system
cannot be designed in isolation without the active involvement of the user.
The user has a vital role to play at this stage too. As we know that data
collected during feasibility study will be utilized systematically during the
system design. It should, however, be kept in mind that detailed study of the
existing system is not necessarily over with the completion of the feasibility
study. Depending on the plan of feasibility study, the level of detailed study
will vary and the system design stage will also vary in the amount of
investigation that still needs to be done. This investigation is generally an
urgent activity during the system design, as the designer needs to study
minutes details in all aspects of the system. Sometimes, but rarely, this
investigation may form a separate stage between Feasibility Study and
Computer System Design. Designing a new system is a creative process,
which calls for logical as well as lateral thinking. The logical approach
involves systematic moves towards the end product keeping in mind the
capabilities of the personnel and the equipment at each decision making
step. Lateral thought implies encompassing of ideas beyond the usual
functions and equipment This is to ensure that no efforts are being made to
fit previous solutions into new situations.

System Design Considerations

The system design process is not a step-by-step adherence of clear procedures and
guidelines. Though, certain clear procedures and guidelines have emerged in recent days,
but still much of design work depends on knowledge and experience of the designer.

When designer starts working on system design, he will face different type of problems.
Many of these will be due to constraints imposed by the user or limitations of the
hardware and software available in the market. Sometimes, it is difficult to enumerate the
complexity of the problems and solutions thereof since the variety of likely problems is
so great and no solutions are exactly similar. However, following considerations should
be kept in mind during the system-designing phase:

The primary objective of the design: Of course, is to deliver the requirements as

specified in the feasibility report. In general, the following design objectives should be
kept in mind:

a. Practicality: The system must be stable and can be operated by people with average +

b. Efficiency: This involves accuracy, timeliness and comprehensiveness of the system

output.
c. Cost: it is desirable to aim for a system with a minimum cost subject to the condition
that it must satisfy all the requirements.

d. Flexibility: The system should be modifiable depending on the changing needs of the
user. Such modifications should not entail extensive reconstructing or recreation of
software. It should also be portable to different computer systems.

e. Security: This is very important aspect of the design and should cover areas of
hardware reliability, fall back procedures, physical security of data and provision for
detection of fraud and abuse.

System design involves first logical design and then physical construction of the system.
The logical design describes the structure and characteristics of features, like the outputs,
inputs, files, databases and procedures. The physical construction, which follows the
logical design, produces actual program software, files and a working system.

The designer normally will work under following constraints:

1. Hardware: The existing hardware will obviously affect the system design.
2. Software: The available software (operating system, utilities, language etc.) in the
market will constrain the design.
3. Budget: The budget allocated for the project will affect the scope and depth of
design.
4. Time-scale: The new system may be required by a particular time (e.g. the start of
a financial year). This may put a constraint on the designer to find the best design.
5. Interface with other systems: The new system may require some data from
another computerized system or may provide data to another system in which case
the files must be compatible in format and the system must operate with a certain
processing cycle.

Processing Techniques
The processing options available to the designer are:

- Batch processing

- Real-time processing

- On-line processing

- A combination of all the above

You are already aware of these techniques. It is quite interesting to note, however, that a
combination of these is often found to be ideal in traditional data processing applications.
This increases throughput of the system as also brings down the response time of on-line
activities. In most of die business applications, 24-hour data is acceptable enough and
hence it is possible to update voluminous data after office-hours in batch mode.

DESIGN METHODOLOGIES

The scope of the systems design is guided by the framework for the new system
developed during analysis. More clearly defined logical method for developing system
that meets user requirements has led to new techniques and methodologies that
fundamentally attempt to do the following:

- Improve productivity of analysts and programmers

- Improve documentation and subsequent maintenance and enhancements.

- Cut down drastically on cost overruns and delays

- improve communication among the user, analyst, designer, and programmer.

- standardize the approach to analysis and design

- simplify design by segmentation.

STRUCTURED DESIGN Structured design is a data flow based methodology. The
approach begins with a system specification that identifies inputs and outputs and
describes the functional aspects of the system. The specifications then are used as a basis
for the graphic representation. The next step is the definition of the modules and their
relationships to one another in a form called a structure chart, using a data dictionary and
other structured tools.

Logical design proceeds from the top down. General features, such as reports and inputs
are identified first. Then each is studied individually and in more detail. Hence, the
structured design partitions a program into small, independent modules. They are
arranged in a hierarchy that approximates a model of the business area and is organized
in a top-down manner. Thus, structured design is an attempt to minimize the complexity
and make a problem manageable by subdividing it into smaller segments, which is called
Modularization or decomposition. In this way, structuring minimizes intuitive reasoning
and promotes maintainable provovable systems.

A design is said to be top-down if it consists of a hierarchy of modules, with each module

having a single entry and a single exit subroutine. The primary advantages of this design
are as follows:

 Critical interfaces are tested first.

 Early versions of the design, though incomplete, are useful enough to resemble
the real system.
 Structuring the design, perse, provides control and improves morale.
 The procedural characteristics define the order that determines processing.

Major System Design Activities

Several development activities are carried out during structured design. They are data
base design, implementation planning, system test preparation, system interface
specification, and user documentation.
a. Data base design: This activity deals with the design of the physical database. A key
is to determine how the access paths art to be implemented.

b. Program design: In conjunction with database design is a decision on the

programming language to be used and the flowcharting, coding, and debugging
procedure prior to conversion. The operating system limits the programming
languages that will run of the system.

c. System and program test preparation: Each aspect of the system has a separate test
requirement. System testing is done after all programming and testing completed The
test cases cover every aspect of the proposed system, actual operations, user interface
and so on. System and program test requirements become a part of design
specifications - a pre requisite to implementation.

In contrast to the system testing is acceptance testing, which puts the system through a
procedure design to convince the user that the proposed system will meet the stated n
requirements. Acceptance testing is technically similar to system testing but politically it
is different. Acceptance testing is conducted in the presence of the user, audit
representatives, or the entire staff.
PROCESS MODELING

Graphical description of a system's data and how the processes transform the data is
known as Data Flow Diagram (or DFD).

Unlike detail flowcharts, DFDs do not supply detailed descriptions of modules but
graphically describe a system's data and how the data interact with the system.

To construct data flow diagrams, we use:

i. arrows,
ii. circles,
iii. open-ended boxes, and
iv. squares

An arrow identifies data flow - data in motion. It is a pipeline through which information
flows. Like the rectangle in flowcharts, circles stand for a process that converts data/into
in- formation. An open-ended box represents a datalstore-data at rest, or a temporary
repository of data. A square defines a source (originator) or destination of system data.

The following seven rules govern construction of data flow diagrams (DFD):

1. Arrows should not cross each other.

2. Squares, circles, and files must bear names.
3. Decomposed data flows must be balanced (all data flows on the decomposed
diagram must reflect flows in the original diagram).

4. No two data flows, squares, or circles can have the same name.
5. Draw all data flows around the outside of the diagram.
6. Choose meaningful names for data flows, processes, and data stores. Use strong
verbs followed by nouns.
7. Control information such as record counts, passwords, and validation
requirements are not pertinent to a data-flow diagram.

If too many events seem to be occurring at a given point, an analyst can decompose a
data conversion (circle). The new data conversions form a parent-child relationship
with the original data conversion: the child circle