Fig. 14.1.3 Process and data are in lock step.The building of functional decompositions and data flow diagrams are used to define and
build applications. As a rule, these constructs can be very complex. One of the tools that
are used in order to manage the complexity is that of the definition of the scope of
development. At the very beginning, there is an exercise that requires that the scope of
the application be defined. The scope definition is necessary in order to keep the size of
the development reasonable. If a designer is not careful, the scope will become so large
that the system will never be built. Therefore, it is necessary to rigorously define the
scope before the development effort ever begins.
The result of the definition of the scope is that—over time—the organization ends up
with multiple applications, each of which have their own functional decompositions and
data flow diagrams.
Fig. 14.1.4 shows that over time, each application has its own set of definitions.
Fig. 14.1.4 Each application has its own functional decomposition and set of data
flow diagrams.Chapter 14.1: Data Models Across the End-State Architecture