|
|
| Step 1:
For each requirement, look at the diagram and decide which processes,
data flows or data stores might have to be modified to meet the
requirement. If you need:
 to
change a process, write the number of the requirement
inside the process bubble. |
| to
change the content of a data flow, write the number beside
the arrow. |
| to
change a data store, write the number inside the data
store. |
Note that a single requirement may require a number of changes
to all three components of the diagram.
Indicate the priority of requirements by color-coding or circling
the number. |
Requirements List
 |
|
| |
LEGEND:
=
Low Priority
= Medium
Priority
= High Priority |
| |
|
DFD with Requirements
Overlay
|
|
|
| Step 2: Evaluate the
diagram to attempt to isolate requirements or sets of requirements
that are localized to a single area on the diagram.
Draw a scope circle around all processes, data flows and data
stores that need to be changed to meet your requirement (or set). |
Impacted Area
|
|
|
| Step 3: Try to think
of at least 3 different solutions you could apply to meet the defined
requirement (or set).
Write down the solution in sufficient detail to be able to discuss
it in the context of the diagram. |
List of Potential
Solutions to R3
|
|
|
| Step 4: Pick the solution
that requires the least amount of effort and evaluate it using the
short-term improvement criteria defined
above. If it passes all tests, recommend implementing it.
To be effective, the recommendation should define the proposed
solution, contain a rough estimate of the costs, identify
the problem being addressed and the benefits of solving
that problem. |
Short Term Improvement
Criteria
| 1. |
Solve an Existing
Problem |
| 2. |
No New Training |
| 3. |
Short Development
Time |
| 4. |
No Side Effects |
| 5. |
Rescindable |
|
 |
Process and Workflow Modeling
