Checklist Description

Use the following tests to determine whether a set of business process diagrams are internally consistent with one another.

Checklist

1. Completeness checks:

   • all processes and sub-processes have their own diagrams

   • all forms, standard letters, screen, and reports used in interactions are included as supporting documentation.

2. Naming checks:

   • process names consistent throughout the diagram(s) (especially in GOTO calls and common sub-processes)

   • role names consistent throughout the diagram(s).

3. Levelling checks:

   • ensure sub-process has trigger with the same name(s) as the calling process(es) so you know where it's called from

   • ensure sub-processes (i.e. perform then return to main process) are distinguished from next process (GOTOs which are the next in sequence)

   • trace circular process loops (infinite GOTOs or sub-processes which call their parents).

4. Interactions completeness:

   • correct identification of method and content not send form but send form X , not contact customer but request payment etc.

   • transfer of responsibility is there a transfer sub-process? Does the transfer of responsibility start a new process which may be inside/outside the scope of investigation? If so, is it marked as such?

   • is the initiator of the interaction identified? Are there any interactions without forms or letters? Are there any forms or letters without interactions?

5. State indicators:

   • check all key management states, handovers, authorizations are identified (by state markers e.g. now require authorization)

   • check waiting states are identified.

Definitions/Techniques

None.

Next Steps

Once the diagrams are in a consistent state...