The Structured Approach

In the Structured Approach, DFDs (Data Flow Diagrams) are used as the main tool.
tool to understand the system before translating it into source code. DFD is a diagram in
the ones that participate in processes (methods), data flow (arguments) and files (database). There are
of different levels depending on the complexity of the system being analyzed, speaking of
languages have many differences from object-oriented, a minimal change in the code
it can affect the rest of the program, which does not happen in object-oriented programming.
It is an advantage because this way time is not wasted fixing things that have already been done. A disadvantage is that
a portion of code in structured language is unlikely to be useful in other projects, this
If it is common in object-oriented language, by just importing ready-made classes, you write less.
code and saves time.

Data Flow Diagram

A data flow diagram (DFD) is a logical-graphical model to represent the

functioning of a system in a software project.

Data Dictionary

The data dictionary is an organized list of all the data that belongs to a system.

The purpose of a data dictionary is to provide clarity about the data being handled in a
system, thus avoiding misinterpretations or ambiguities.

Module Design

A data model is a language aimed at describing a Database. Typically a

Data Model allows to describe:

The data structures of the database: The type of data that is in the database and the way in which it is
they relate.

Integrity constraints: A set of conditions that data must meet to

reflect the desired reality correctly.

Data manipulation operations: Aggregate, delete, modification operations and

data recovery from the database.

Another approach is to think that a data model allows describing the elements of reality.
that intervene in a given problem and the way those elements relate to each other.

Process
Set of logically related tasks that exist to achieve a defined outcome
within a business or project.

Structured Approach

Data Flow Diagram

A data flow diagram (DFD) is a graphical representation of the processes that are carried out.
With the data in your organization, it is possible to create a
graphic description of the processes that, over time, will contribute to developing a solid
system documentation.

It then mentions the advantages of descriptive explanations in relation to the way in

that the data moves through the system:

Freedom to undertake the technical implementation of the system in the initial stages.

Deeper understanding of the interrelationship between systems and subsystems.

Communication with users about the knowledge of the current system through diagrams of
data flows.

Analysis of a proposed system to determine if data and processes have been defined.
necessary.

The greatest advantage is the conceptual freedom to use the four symbols, the DFDs do
emphasis on processing or transformation as they go through a variety of
processes. In logical DFDs there is no distinction between manual or automated processes. The
processes are not represented graphically in chronological order. Instead, they are grouped
only if the detailed analysis indicates that it makes sense to do so. Manual processes are grouped, and
automated processes can also be grouped.

Data Dictionary

The data dictionary arises from the need to catalog processes, flows, and warehouses.
data structures and elements. The names that are used are very important. When one has
the opportunity to assign names to the components of data-oriented systems is
It is necessary to work on creating a meaningful name but different from others.
existing data components.

The data dictionary has been proposed as a nearly formal grammar to describe the content of
the objects defined during the structured analysis. This notation has been defined of the
next form by Yourdon in 1989:

The data dictionary is an organized list of all the data elements that are
relevant to the system, with precise and rigorous definitions that allow the user and the
the system analyst has a common understanding of the inputs, outputs, and components
of the warehouses and also the intermediate calculations.

Many database management systems are equipped with a data dictionary.

automated. These dictionaries can be complex or simple, some data dictionaries
computerized systems automatically catalog data elements when the
programming; others simply provide a template to motivate the person to fill in
the dictionary to do it in a uniform way for each entry.

Despite the existence of automated data dictionaries, understanding what data

they make up a data dictionary, the conventions used in these last ones and how it is developed
A data dictionary consists of problems that the systems analyst must always keep in mind.
during the system effort. Understanding the process of compiling a data dictionary can
help the systems analyst to visualize the system and its operation. In addition to providing
documentation and eliminate redundancy, the data dictionary could be used for:

Validate the integrity and accuracy of the data flow diagram.

Provide a starting point for developing screens and reports.

Determine the content of the data stored in files.

Develop the logic for the data flow diagram processes.

Module Design

The concept of modularity has been presented for nearly five decades in software.
computer. Computer architecture expresses modularity; that is, the software is
divided into named components and addressed separately, often called
modules that integrate to meet the requirements of the problem.

It has been stated that 'Modularity is the only attribute of software that allows for management of a
intellectually programmed.” The monolithic software (that is, a large program formed by
a single module) cannot be easily understood by the reader. The number of control paths,
the breadth of references, the number of variables, and the overall complexity will make it
understanding is very close to being impossible. To illustrate this point, let's take
consider the following argument based on human observations about resolution
problems.

Structured Approach and Design

The Approach refers to the 'initial stage' of a systems development project, during the
time when user requirements are defined and documented.

The structured approach introduces the use of graphic documentation tools to

produce a different type of functional specification: 'the structured specification'.

Concepts related to the Structured Approach

— • Graphic symbols; icons and conventions to identify and describe the components of a
system along with the relationships between these components.

Data dictionary; descriptions of all the data used in the system.

—• Descriptions of processes and procedures; formal statements that employ techniques and
languages that allow analysts to describe important activities that are part of the
system.

—• Rules; standards for describing and documenting the system correctly and completely.
Design Phase

In this phase, the structured design produces the design model with the following elements:

— • Data design. Transforms the information domain model created during the
analysis, in the data structures necessary to implement the software. The data objects
and the relationships defined in the entity-relationship diagram and the detailed data content of
Data dictionaries form the basis for data design.

Architectural design. Defines the relationship between the main structural elements of
The program is obtained from the analysis model and the interaction of defined subsystems.
within the analysis model.

Interface design. Describe how the software communicates with itself and with the systems.
who operate with it and with the operators who use it. The data and control flow diagrams
they provide the necessary information for the interface design.

Procedural design. Transforms structural elements of the program's architecture

in a procedural description of the components of the software. It is obtained from the
process specification, control specification, and state transition diagram

According to the Structured Model

The Structured approach was chosen as a requirements gathering technique, as

that allows the analyst to understand the system or process in a logical and manageable way, at the same time
time that provides the basis to ensure that no detail is overlooked. This is a method
for the analysis of manual or automated systems, which leads to the development of
specifications for new systems or to make modifications to existing ones. In addition
to it and because they are considered as a tool capable of describing and analyzing movement of
data through a system, the graphical representation of the system processes will be at
cargo of the Data Flow Diagrams (DFD).