Structured refers to step-by-step process, with

each step building on the previous one.

Methodology refers to a step- by-step plan for

achieving some desired result.
What is Structured methodologies

It is an alternate method for Modeling & Designing

This method is in utilisation since 1970, this method used

to document, analyze and design the systems.

Structured Methodologies are top-down, progressing from

the highest Most abstract level to the lowest level of detail-from
the general to the specific.

The structured methodology centers on building logical

model of the system in order to give a common picture of the
system and its interrelationships.

It includes partitioning a large system into manageable

smaller ones and organizing the details into an understandable
structure by utilizing a top down approach, i.e., employing
functional or hierarchical decomposition.
Structured methodological example of finance
function in an organisation
Conventional method of system developing
 Differences between Conventional and Structured
methodologies

•Interaction with users is limited.

•Freezing of specifications
•Well-defined methods of analysis and design
•Easy to maintenance
•Feedback to users during intermediate stages
•Documentation is prepared at the end of the project
•Evaluation at the intermediate stages
•Distribute the development work among different
programmers.
Structured method of system developing
Advantages of Structured methods

•Good documentation
•Standardization Predictability of Design
•Maintainability and enhancements
•Communication media
•less scope of Individual methods
•Ease of debugging and testing
•Reduction of complexity and modularization
• Automation
 Structured development methods
•The structured methodologies are process oriented & focusing
primarily on the process of actions,
•Although the data descriptions are part of the methodologies.
• It captures, store manipulate & distribute data through a system

The structured methodologies include the following methods.

Structured Analysis
Structured Design
Structured Programming
Flow charts
Structured Analysis. Structured Analysis is a
development method for the analysis of existing, manual
or automated systems, leading to the development of
specifications (i.e. Design) for a new or modified system.

Structural Analysis allows the analyst to learn about a

system or a process in a manageable and logical way.

The objectives in structured analysis is to completely

understand the current system, from which requirements
are determined, which become the basis for a new or
modified system.
Fully understanding large, complex systems may be
difficult, but structured analysis development method is
aimed at overcoming this difficulty through its
components.
Structured analysis is Communicating more effectively
with users during the entire tem development life cycle.
If structured analysis is done in a per manner, it allows
the systems analysts to develop systems that are
wanted by the users and that can be used by them in an
effective manner.

The aim of structured analysis is to clearly define WHAT

a systems requirements
 Tools of Structured Analysis

Data flow diagrams,

data dictionary
process descriptions

These are the main tools for structured analysis.

Data flow diagrams
Data Flow Diagram (DFDs).
Data flow diagrams are widely used graphic tools
for describing the movement of data within and outside
the system. These diagrams, popularly called as
DFD ‘s quickly convey to both the software
developers and users, the current system is working and
how the proposed system work.

The main advantage of DFDs is that they are

easily understood by the users and hence, users can
suggest modifications in the proposed system.
Customer

Customer
Notation and Construction of DFD

Symbol Meaning, Symbol Meaning

Process of function Data Flow

Data
External Entity as
Source I Destination
Store
How to Draw a DFD

Identify the sources and sinks of data. Sources are the external
entities which originate the data. Sinks are the external entities
which receive the final output. This identification will provide a
boundary to the work and also give a set of flows.

•Identify the processes as the activities under study.

•Join the processes and sources/ sinks via data flow, If you need
to store the data permanently, or for later u, make a data store.

•Most of the processes would be joined through stores.

Generate the first rough draft; modify its data flow to design a
concise and neat diagram without any concise of arrows. If the
crossing cannot be avoided, represent one of the flows with a
curb.
Rules for Drawing a DFD
A set of guidelines and rules should be followed to ensure the
consistency and accuracy of the model. These rules are listed
below.

• Sources cannot leak data directly to a data store

• A data store cannot pass the data directly to a destination.
• A data flow out of a data store is read-only
• Data cannot flow directly from one data store to another.
• Any process producing output by itself should be a source.
• Any process with only input should be a data destination
• Each subsystem must be a process on the next higher
level diagram