Scribd
Upload
3 views

Chapter 7 Key Points

Chapter 7 discusses the use of Data Flow Diagrams (DFDs) as a method for analyzing data-oriented systems, highlighting their advantages over narrative explanations. It outlines the symbols used in DFDs, guidelines for creating them, and common errors to avoid. The chapter also covers logical and physical data flow diagrams, their purposes, and the process of partitioning DFDs into separate programs.

Uploaded by

Omotosho Busayor
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3 views

Chapter 7 Key Points

Chapter 7 discusses the use of Data Flow Diagrams (DFDs) as a method for analyzing data-oriented systems, highlighting their advantages over narrative explanations. It outlines the symbols used in DFDs, guidelines for creating them, and common errors to avoid. The chapter also covers logical and physical data flow diagrams, their purposes, and the process of partitioning DFDs into separate programs.

Uploaded by

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

Chapter 7

Using Data Flow Diagrams


Key Points

1. Data flow diagrams (DFDs) are one of the main methods available for analyzing
data-oriented systems.

2. Using DFDs, which emphasize the logic underlying the system, the systems
analysts can put together a graphical representation of data movement through
the organization.

3. The data flow approach has four main advantages over the narrative explanation
of the data movement. They are:

A. Freedom from committing to the technical implementation of the system too


early
B. Further understanding of the interrelationships of systems and subsystems
C. Communicating current system knowledge to users through data flow
diagrams
D. Analysis of the proposed system to determine if all the data and processes
have been defined

4. Four basic symbols are used to chart data movement on data flow diagrams. They
are:

A. A double square for an external entity—a source or destination of data


B. An arrow for movement of data from one point to another
C. A rectangle with rounded corners for the occurrence of transforming
process
D. An open-ended rectangle for a data store

5. Correct naming of data flow objects is necessary for good communication.


Guidelines are:

A. External entities should be named with a noun.


B. Processes should be named:
i. A system name
ii. A subsystem name
iii. With a verb-adjective-noun format
C. Processes should have a unique reference number.
D. Data stores should be named with a noun.
6. Use the following guidelines to develop a data flow diagram:

A. Make a list of business activities.


B. Create the context level diagram, including all external entities and the
major data flow to or from them.
C. Create Diagram 0 by analyzing the major activities within the context
process. Include the external entities and major data stores.
D. Create a child diagram for each complex process on Diagram 0. Include
local data stores and detailed processes.

7. Detailed data flow diagrams may be developed by:

A. Analyzing what happens to an input data flow from an external entity.


B. Analyzing what is necessary to create an output data flow to an external
entity.
C. Examining the data flow to or from a data store.
D. Analyzing a well-defined process for data requirements and the nature of
the information produced.

8. Unclear areas of a data flow diagram should be noted and investigated.

9. An interface data flow is data that is input or output from a child diagram that
matches the parent diagram data flow.

10. Processes that do not create a child diagram are called primitive processes. Logic
is written for these processes.

11. The following conditions are errors that occur when drawing a data flow diagram:

A. A process that has only input data flow to it or only output data flow from it.
B. When data stores or external entities are connected directly to each other,
in any combination.
C. Incorrectly labeling data flow or objects. Examples are:
i. Labels omitted from data flow or objects
ii. Data flow labeled with a verb
iii. Processes labeled with a noun
D. Too many processes on a data flow diagram. Nine is the suggested
maximum.
E. Omitting data flow from the diagram.
F. Unbalanced decomposition between a parent process and a child diagram.
The data flow in and out of a parent process must be present on the child
diagram.

12. Logical data flow diagrams show how the business operates and include
processes that would exist regardless of the type of system implemented.
13. The progression of creating data flow diagrams is:

A. Create a logical data flow diagram of the current system.


B. Next, add all the data and processes not currently in the system, which must
be present in the new system, giving a logical data flow diagram for the new
system.
C. Finally, derive the physical data flow diagram for the new system.

14. Advantages of logical data flow diagrams are:

A. Better communication with users. They are familiar with how the business
operates.
B. More stable systems, because the design is based on a business
framework.
C. Increased understanding of the business by analysts.
D. The system will have increased flexibility and be easier to maintain.
E. Elimination of redundancy.

15. Physical data flow diagrams show how the system operates or how the new
system will be implemented. Physical data flow diagrams include:

A. Clarifying which processes are performed by humans (manual) and which


are automated
B. Describing processes in greater detail
C. Sequencing processes in the order they must be executed
D. Temporary data stores and transaction files
E. Specifying actual document and file names
F. Controls to ensure accuracy and completeness

16. Physical data flow diagrams include processes for adding, reading, changing, and
deleting records. CRUD is an acronym for Create, Read, Update, Delete.

17. A CRUD matrix shows which programs or processes add, read, update, or delete
master file records.

18. Master or transaction files are used to link all processes that operate at different
times.

19. An input flow from an external entity is sometimes called a trigger, because it starts
activities.

20. Elements (or fields) are categorized as either:

A. Base elements that are keyed into the system


B. Derived elements, which are the result of some operation, such as
arithmetic or logic
21. Another approach used to create a data flow fragment is to analyze events, which
are summarized in an event table.

22. Creating a use case is another approach used to develop a data flow diagram. A
use case shows the steps performed to accomplish a task.

23. Partitioning is the process of analyzing a data flow diagram and deriving a series
of manual procedures and computer programs. A dashed line is drawn around a
group of processes that are included in each computer program or manual
procedure.

24. The reasons for partitioning a data flow diagram into separate computer programs
are:

A. Different user groups should have different programs


B. Processes that execute at different times must be in separate programs
C. Similar tasks may be included in the same program
D. Several batch processes may be included in the same program for
efficiency
E. Several processes may be included in the same program or job stream for
consistency of data
F. Processes may be separated into different programs for security

25. Data flow diagrams may be used to partition websites into a series of Web pages
when data is obtained from a database table or an external partner. Ajax is a
technique that allows websites to obtain data from a Web server while remaining
on the current Web page. Ajax may be used to reduce the partitioning of a website.

26. Data flow diagrams can be used for several different purposes.

A. Unexploded data flow diagrams are useful to identify information


requirements.
B. Data flow diagrams can be used for the system documentation.

You might also like