Scribd
Upload
1K views19 pages

Chapter 4 Software Analysis and Design Tools

Software analysis and design tools like data flow diagrams (DFDs), structure charts, HIPO diagrams, and entity-relationship models are used to transform human-readable software requirements into implementation. DFDs depict the flow of data through a system at various levels of abstraction. Structure charts break a system down into hierarchical functional modules. HIPO diagrams represent system functions and subfunctions. Entity-relationship models map real world entities and relationships to a conceptual database design. A data dictionary centralizes information about data elements to facilitate software design and implementation.

Uploaded by

MK Milly
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
1K views19 pages

Chapter 4 Software Analysis and Design Tools

Software analysis and design tools like data flow diagrams (DFDs), structure charts, HIPO diagrams, and entity-relationship models are used to transform human-readable software requirements into implementation. DFDs depict the flow of data through a system at various levels of abstraction. Structure charts break a system down into hierarchical functional modules. HIPO diagrams represent system functions and subfunctions. Entity-relationship models map real world entities and relationships to a conceptual database design. A data dictionary centralizes information about data elements to facilitate software design and implementation.

Uploaded by

MK Milly
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

SOFTWARE ENGINEERING

CHAPTER FOUR
Software Analysis and Design Tools
Software Analysis and Design Tools

Software analysis and design includes all activities, which help


the transformation of requirement specification into
implementation. Requirement specifications specify all functional
and non-functional expectations from the software.

These requirement specifications come in the shape of human


readable and understandable documents, to which a computer has
nothing to do.

Software analysis and design is the intermediate stage, which


helps human-readable requirements to be transformed into actual
code.
Analysis and Design tools used by software designers:

Data Flow Diagram

Data Flow Diagram (DFD) is a graphical representation of flow of


data in an information system. It is capable of depicting incoming
data flow, outgoing data flow, and stored data.

The DFD does not mention anything about how data flows through
the system. There is a prominent difference between DFD and
Flowchart. The flowchart depicts flow of control in program
modules.

DFDs depict flow of data in the system at various levels. It does


not contain any control or branch elements.
Types of DFD

Data Flow Diagrams are either Logical or Physical.

Logical DFD - This type of DFD concentrates on the system


process, and flow of data in the system. For example in a banking
software system, how data is moved between different entities.

Physical DFD - This type of DFD shows how the data flow is
actually implemented in the system. It is more specific and close to
the implementation.
DFD Components

DFD can represent source, destination, storage, and flow of data


using the following set of components -

Entities - Entities are sources and destinations of information data.


Entities are represented by rectangles with their respective names.

Process - Activities and action taken on the data are represented by


Circle or Round-edged rectangles.
Data Storage - There are two variants of data storage - it can
either be represented as a rectangle with absence of both smaller
sides or as an open-sided rectangle with only one side missing.

Data Flow - Movement of data is shown by pointed arrows. Data


movement is shown from the base of arrow as its source towards
head of the arrow as destination.

Levels of DFD

Level 0 - Highest abstraction level DFD is known as Level 0


DFD, which depicts the entire information system as one diagram
concealing all the underlying details. Level 0 DFDs are also
known as context level (Frame work level) DFDs.
Level 1 - The Level 0 DFD is broken down into more specific,
Level 1 DFD. Level 1 DFD depicts basic modules in the
system and flow of data among various modules.

Level 1 DFD also mentions basic processes and sources of


information.
Level 2 - At this level, DFD shows how data flows inside the
modules mentioned in Level 1.

Higher level DFDs can be transformed into more specific lower


level DFDs with deeper level of understanding unless the desired
level of specification is achieved.

Structure Charts
Structure chart is a chart derived from Data Flow Diagram. It
represents the system in more detail than DFD.

It breaks down the entire system into lowest functional modules,


describes functions and sub-functions of each module of the
system to a greater detail than DFD.

Structure chart represents hierarchical structure of modules. At


each layer a specific task is performed.
The symbols used in construction of structure charts :

Module - It represents process or subroutine or task. A control


module branches to more than one sub-module. Library
Modules are re-usable and invokable from any module.
Condition - It is represented by small
diamond at base of the module. It
depicts that control module can select
any of sub-routine based on some
condition.

Jump - An arrow is shown pointing


inside the module to depict that the
control will jump in the middle of
the sub-module.
Loop - A curved arrow represents
loop in the module. All sub-
modules covered by loop repeat
execution of module.

Data flow - A directed arrow


with empty circle at the end
represents data flow.
Control flow - A directed arrow
with filled circle at the end
represents control flow.

HIPO Diagram
Hierarchical Input Process Output (HIPO) diagram is a
combination of two organized methods to analyze the system
and provide the means of documentation. HIPO model was
developed by IBM in year 1970.
HIPO diagram represents the hierarchy of modules in the
software system. Analyst uses HIPO diagram in order to obtain
high-level view of system functions. It
It decomposes functions into sub-functions in a hierarchical
manner. It depicts the functions performed by system.

HIPO diagrams are good for documentation purpose. Their


graphical representation makes it easier for designers and
managers to get the pictorial idea of the system structure.
In contrast to Input Process Output (IPO) diagram, which depicts
the flow of control and data in a module, HIPO does not provide
any information about data flow or control flow.
Entity-Relationship Model
Entity-Relationship model is a type of database model based on the
notion of real world entities and relationship among them. We can
map real world scenario onto ER database model. ER Model creates
a set of entities with their attributes, a set of constraints and relation
among them. ER Model is best used for the conceptual design of
database. ER Model can be represented as follows :
Entity - An entity in ER Model is a real world being, which has
some properties called attributes. Every attribute is defined by its
corresponding set of values, called domain.

For example, Consider a school database. Here, a student is an


entity. Student has various attributes like name, id, age and class
etc.

Relationship - The logical association among entities is called


relationship. Relationships are mapped with entities in various
ways. Mapping cardinalities define the number of associations
between two entities.
Data Dictionary

Data dictionary is the centralized collection of information


about data. It stores meaning and origin of data, its relationship
with other data, data format for usage, etc.

Data dictionary has rigorous definitions of all names in order to


facilitate user and software designers.

Data dictionary is often referenced as meta-data (data about


data) repository. It is created along with DFD (Data Flow
Diagram) model of software program and is expected to be
updated whenever DFD is changed or updated.
Requirement of Data Dictionary

The data is referenced via data dictionary while designing and


implementing software. Data dictionary removes any chances of
ambiguity.

It helps keeping work of programmers and designers synchronized


while using same object reference everywhere in the program.

Data dictionary provides a way of documentation for the complete


database system in one place. Validation of DFD is carried out using
data dictionary.

You might also like