Current Physical Dataflow Model
Content
For the As-Is business system.
The dataflow model comprises:
- A Context diagram showing the area under study and its external communication.
- A set of Dataflow diagrams showing a hierarchy
of more and more detailed decompositions of the in-scope
processes.
- A set of Elementary Process Descriptions
for each bottom-level process (i.e one not further
decomposed). This includes volumetrics and any hardware and software
that currently provides support.
- A set of descriptions for each dataflow that
crosses the scoping boundary (aka I/O Descriptions)
- Descriptions for each datastore and a
cross-reference to the entities (from the LDS) it
contains.
Remember, this is a warts-and-all view. You will
expect entities to be apper in more than one datastore.
Don't be too pedantic with the Current Physical -
it is only a route to get to a logical view of the current services.
For more about dataflow models, see Dataflow
Modelling (opens in a new window)
Completeness
It has been cross checked for completeness against
the Logical Data Model
(do all LDM entities appear in datastores and move in dataflows?) and
used to identify the main business events for the Event Catalogue (what
happens in the real world that causes a flow into a datastore?).
|
![[<< First]](../arlesimages/tsign_purple_first.gif){kind=small}
![[< Previous]](../arlesimages/tsign_purple_previous.gif){kind=small}
![[Next >]](../arlesimages/tsign_purple_next.gif){kind=small}
![[Last >>]](../arlesimages/tsign_purple_last.gif){kind=small}