Chapter No.

3 Designing the Project

3.1 Introduction

Software design sits at the technical kernel of the software engineering process and is applied
regardless of the development paradigm and area of application. Design is the first step in the
development phase for any engineered product or system. The designer’s goal is to produce a
model or representation of an entity that will later be built. Beginning, once system requirement
have been specified and analyzed, system design is the first of the three technical activities -
design, code and test that is required to build and verify software.

The importance can be stated with a single word “Quality”. Design is the place where quality is
fostered in software development. Design provides us with representations of software that can
assess for quality. Design is the only way that we can accurately translate a customer’s view into
a finished software product or system. Software design serves as a foundation for all the software
engineering steps that follow. Without a strong design we risk building an unstable system – one
that will be difficult to test, one whose quality cannot be assessed until the last stage.
During design, progressive refinement of data structure, program structure, and procedural
details are developed reviewed and documented. System design can be viewed from either
technical or project management perspective. From the technical point of view, design is
comprised of four activities – architectural design, data structure design, interface design and
procedural design.

3.2 Purpose

The main purpose of the system is to manage the all issues about blood and make blood
available to patient. The main purpose is to save the life of other and work for human being. The
admin can monitor and control the profile of any donor. The system will have a complete record
about the donor’s their contact number Email address district etc.

Live Blood Donor’s Management System 18

Chapter No.3 Designing the Project

3.3 Scope

The Live Blood Donor’s Management System needs to create the blood bank for properly
transfusion and storage of blood. Each unit of whole blood is normally separated into several
components. Red blood cells may be stored under refrigeration for a maximum of 42 days. Red
cells carry oxygen and are used to treat anemia. Platelets are important in the control of bleeding
and are generally used in patients with leukemia and other forms of cancer.

3.4 Definitions, Acronyms and Abbreviations

While making the Live Blood Donor’s Management System no special acronyms and
abbreviations can be used there are simple terms can be used which is given below.

✓
Admin

In this module Admin will add the donor and update and delete information about the donor’s in
Live Blood Donor’s Management System and can change password.

✓
Donor

In this module donor register himself and can give comment. Also donor can see inspiring
message why became a donor.

3.5 Architectural Representation (Architecture Diagrams)

To show the architecture became a donor (DFD) Data Flow Diagrams can be used.

DFD (Data Flow Diagram)

A data flow diagram is graphical tool used to describe and analyze movement of data through a
system. These are the central tool and the basis from which the other components are developed.
The transformation of data from input to output, through processed, may be described logically
and independently of physical components associated with the system. These are known as the
logical data flow diagrams. The physical data flow diagrams show the actual implements and
movement of data between people, departments and workstations. A full description of a system
actually consists of a set of data flow diagrams. Using two familiar notations Yourdon, Gane

Live Blood Donor’s Management System 19

Chapter No.3 Designing the Project

And Samson notation develops the data flow diagrams. Each component in a DFD is labeled
with a descriptive name. Process is further identified with a number that will be used for
identification purpose. The development of DFD’S is done in several levels. Each process in
lower level diagrams can be broken down into a more detailed DFD in the next level. The lop-
level diagram is often called context diagram. It consist a single process bit, which plays vital
role in studying the current system. The process in the context level diagram is exploded into
other process at the first level DFD.

The idea behind the explosion of a process into more process is that understanding at one level of
detail is exploded into greater detail at the next level. This is done until further explosion is
necessary and an adequate amount of detail is described for analyst to understand the process.

Larry Constantine first developed the DFD as a way of expressing system requirements in a
graphical from, this lead to the modular design. A DFD is also known as a “bubble Chart” has
the purpose of clarifying system requirements and identifying major transformations that will
become programs in system design. So it is the starting point of the design to the lowest level of
detail. A DFD consists of a series of bubbles joined by data flows in the system.

DFD Symbols
In the DFD, there are four symbols
✓
A square defines a source(originator) or destination of system data
✓
An arrow identifies data flow. It is the pipeline through which the information
flows
✓
A circle or a bubble represents a process that transforms incoming data flow into
outgoing data flows.
✓
An open rectangle is a data store, data at rest or a temporary repository of data

Live Blood Donor’s Management System 20

Chapter No.3 Designing the Project

Process that transforms data flow.

Source or Destination of data

Data flow

Data Store

Fig 3.1

Constructing a DFD:

✓
The DFD it is marked with a short diagonal.
When a process is several rules of thumb are used in drawing DFD’S:

✓
Process should be named and numbered for an easy reference. Each name should
be representative of the process.

✓
The direction of flow is from top to bottom and from left to right. Data
traditionally flow from source to the destination although they may flow back to
the source. One way to indicate this is to draw long flow line back to a source. An
alternative way is to repeat the source symbol as a destination. Since it is used
more than once in exploded into lower level details, they are numbered.
✓
The names of data stores and destinations are written in capital letters. Process
and dataflow names have the first letter of each work capitalized.

Live Blood Donor’s Management System 21

Chapter No.3 Designing the Project

Data Flow

✓
A Data Flow has only one direction of flow between symbols. It may flow in both
directions between a process and a data store to show a read before an update. The
latter is usually indicated however by two separate arrows since these happen at
different type.
✓
A join in DFD means that exactly the same data comes from any of two or more
different processes data store or sink to a common location.

✓
A data flow cannot go directly back to the same process it leads. There must be at
least one other process that handles the data flow produce some other data flow
returns the original data into the beginning process.
✓
A Data flow to a data store means update (delete or change).
✓
A data Flow from a data store means retrieve or use.

DFD Diagrams Showing Architecture of the Project

Level 0

Input Out Put

Data Base System User/ Admin

Live Blood Donor’s Management System 22

Chapter No.3 Designing the Project

Level 1

Login

In Valid Became a
Admin Password donor

Home

Here in above level (1) shown the process of dfd diagram architecture of the project
define a complete process for user login. Also shown the login process of the Admin, in
the case of wrong entry of the data/user id or password the process of the project will not
be proceeding when there will be the invalid user name and password its will make
process.
Correct password.
Correct user name.
Process

Live Blood Donor’s Management System 23

Chapter No.3 Designing the Project

Level 2:
User Module:

Home

DB
Donor registration

Update Donor
Search donors
Allocate

End

Live Blood Donor’s Management System 24

Chapter No.3 Designing the Project

Level 3:

Admin Module:

Login
Admin

Add, View
Update
Delete the DB
Donor’s information

Reporting

Mang
cntact
us
View donor Add or del donor

Live Blood Donor’s Management System 25

Chapter No.3 Designing the Project

3.6 Dynamic Model: Sequence Diagrams

The dynamic model describes the behavior of a distributed parameter system in terms of how
one qualitative state can turn into another. A qualitative state is described by a static model, i.e.
the distributions and intersections of the qualitative fields at a particular time instant or interval.
The sequence Diagram is best way to show Dynamic

3.7 Object Model/Logical Model: Class Diagram

An object model consists of the following important features:
✓
Object Reference: Objects can be accessed via object references. To invoke a method in
an object, the object reference and method name are given, together with any arguments.
✓

Live Blood Donor’s Management System 26

Chapter No.3 Designing the Project

✓
Interfaces: An interface provides a definition of the signature of a set of methods without
specifying their implementation. An object will provide a particular interface if its class
contains code that implements the method of that interface. An interface also defines
types that can be used to declare the type of variables or parameters and return values of
methods.

✓
Actions: Action in an OOP is initiated by an object invoking a method in another object.
An invocation can include additional information needed to carry out the method. The
receiver executes the appropriate method and then returns control to the invoking object,
sometimes supplying a result.

✓
Exceptions: Programs can encounter various errors and unexpected conditions of varying
seriousness. During the execution of the method many different problems may be
discovered. Exceptions provide a clean way to deal with error conditions without
complicating the code. A block of code may be defined to throw an exception whenever
particular unexpected conditions or errors arise. This means that control passes to another
block of code that catches the exception.

✓
Garbage collection: It is necessary to provide the means of freeing the space occupied
by objects when they are no longer needed. For example, Java can detect automatically
when an object is no longer accessible, recover the space and make it available for
allocation to other objects. This process is called garbage collection.

Live Blood Donor’s Management System 27

Chapter No.3 Designing the Project

3.8 Deployment Model (Deployment Diagram)

The concept of deployment in predictive data mining refers to the application of a model for
prediction to new data. Building a model is generally not the end of the project. Even if the
purpose of the model is to increase knowledge of the data, the knowledge gained will need to be
organized and presented in a way that the customer can use it.

The Deployment Model of the Live Blood Donor’s Management System is not so complex as it a
web application so it has three main parts. Which are as below?
✓
Web Server :
There is used to display the effects of server side language and controls the web main role

Live Blood Donor’s Management System 28

 Chapter No.3 Designing the Project

✓
Database Server :

As it is clear from the name that the MS Sql server is used to maintained the database of project

✓
Web Browser :

Web browsers perform the main the task it show the final output and ready to work environment
for user. If any user want to the web application or a web site one can should install a web
browser first.

Deployment Diagram

User
Web role Worker role
Browser PHP 4.0

Table’s blocks

Live Blood Donor’s Management System

Live Blood Donor’s Management System 29

Chapter No.3 Designing the Project

3.10 Graphical User Interfaces

Admin Login

Live Blood Donor’s Management System 30

Chapter No.3 Designing the Project

Contact Us

Live Blood Donor’s Management System 31

Chapter No.3 Designing the Project

Admin Profile

Live Blood Donor’s Management System 32

Chapter No.3 Designing the Project

Search Donor

Live Blood Donor’s Management System 33

Chapter No.3 Designing the Project

Became a Donor

Live Blood Donor’s Management System 34

Chapter No.3 Designing the Project

Home

Live Blood Donor’s Management System 35