Process Modeling z Graphically represent the processes that

  • Slides: 20
Download presentation
Process Modeling z. Graphically represent the processes that capture, manipulate, store, and distribute data

Process Modeling z. Graphically represent the processes that capture, manipulate, store, and distribute data between a system and its environment z. Models y. DFDs -- Process, Data & Externals y. ERDs -- Data Structure -- no Process y. Process Logic and Timing

Process Modeling Deliverables z. Context DFD (Not in D/2000) z. DFD of current physical

Process Modeling Deliverables z. Context DFD (Not in D/2000) z. DFD of current physical system z. DFD of current logical system z. DFD of new logical system z. Adequate descriptions of each DFD component (Oracle Repository)

DFD Mechanics

DFD Mechanics

Context Level DFD Figure 8. 4, p 284

Context Level DFD Figure 8. 4, p 284

Level Zero (First Level) Diagram Figure 8. 5, p 285

Level Zero (First Level) Diagram Figure 8. 5, p 285

DFD Rules -- Process A. No process can have only outputs B. No process

DFD Rules -- Process A. No process can have only outputs B. No process can have only inputs Every Process has Input & Output C. (1) Use Verb phrase labels for the lowest level (Basic Function Module - a BFM has no explosion) (2) Use xxx Process for the others

DFD Rules -- Process Incorrect A. B. Correct

DFD Rules -- Process Incorrect A. B. Correct

DFD Rules -- Data Store D. E. F. Data cannot move directly from one

DFD Rules -- Data Store D. E. F. Data cannot move directly from one data store to another data store Data cannot move directly from an outside source to a data store Data cannot move directly to an outside sink from a data store One end of a Data Flow must be a Process G. Use a Noun phrase label (Entity Name)

DFD Rules -- Source / Sink H. Data cannot move directly from a source

DFD Rules -- Source / Sink H. Data cannot move directly from a source to a sink. It must be moved by a process. I. Noun phrase label. (External) Contents are Entities - one Primary

DFD Rules -- Data Flow J. K. L. A data flow has only one

DFD Rules -- Data Flow J. K. L. A data flow has only one direction of flow between symbols; a data flow may flow in both directions to and from a data store (usually two symbols) A fork in a data flow means that exactly the same data goes to two different processes or data stores. A join in a data flow means that exactly the same data comes from two different processes and data stores.

DFD Rules -- Data Flow Incorrect J. K. L. Correct

DFD Rules -- Data Flow Incorrect J. K. L. Correct

DFD Rules -- Data Flow M. N. O. P. A data flow cannot go

DFD Rules -- Data Flow M. N. O. P. A data flow cannot go directly back to the same process it leaves A data flow to a data store means create, update or delete A data flow from a data store means retrieve or use Use a Noun phrase label. Contents are attributes of entities and data items

Other DFD Issues z. Decomposition (Explosion) y. Explode a single process into subprocesses z.

Other DFD Issues z. Decomposition (Explosion) y. Explode a single process into subprocesses z. Balancing (the Great Circle Rule) y. Conserve all process inputs and outputs when decomposing a process

Decomposition of 4. 0 Figure 8. 8 and 8. 7, p 289

Decomposition of 4. 0 Figure 8. 8 and 8. 7, p 289

Decomposition of 4. 3 Figure 8. 9, p 290

Decomposition of 4. 3 Figure 8. 9, p 290

Balance - Context Level 0 Source 1 A System B Sink 1

Balance - Context Level 0 Source 1 A System B Sink 1

Unbalanced DFD 1 Source 1 A C Source 2 Formatted A C 2 B

Unbalanced DFD 1 Source 1 A C Source 2 Formatted A C 2 B Sink 1

DFD Rules -- Advanced Rules R. The inputs to a process must be sufficient

DFD Rules -- Advanced Rules R. The inputs to a process must be sufficient to produce the outputs S. At the lowest level of DFDs, new data flows may be added to represent data that are transmitted under exceptional conditions (e. g. , error messages). T. To avoid having data flow lines cross each other, you may repeat data stores or sources / sinks on a DFD.

DFD Guidelines z. Completeness z. Consistency z. Timing z. Iterative Development

DFD Guidelines z. Completeness z. Consistency z. Timing z. Iterative Development

Primitive DFDs -- BFM Level z. Single database operation - update, retrieve, create, delete

Primitive DFDs -- BFM Level z. Single database operation - update, retrieve, create, delete z. Single other process function -- input or output data; calculate; decision z. Process for each option or choice z. Data flow split to each use set z. User and Analyst are satisfied z. Element of Personal Choice