work will have been completed during the Preliminary Requirements
Phase. This phase will build on the work undertaken at that
point. Some discussion will be required as to how deeply processes
will be mapped. Some considerations are:
- The time available
- The people available to do the work
- How much of existing processes will be retained? For example,
if there will be major changes to processes, is it better
to focus on the new processes rather than spend time on
those to be abandoned?
- What existing material is available and it's currency
The starting point is the process maps and functional decomposition
that was done during Preliminary Requirements. Each of the
functions will represent a business process, or sub-process.
Some may be repeated. For example there may be a process for "Change
Customer Details". This may happen a number of times
in different business processes. It could happen as part of
the process to handle customer enquiries and it can happen
as part of the process to take an order. If you use a proper
modeling tool, you can link the "Change Customer Details" process
to various points in other processes. It becomes a generic
In terms of defining the process levels, a list of processes
can be created and agreement gained with the business as to
which of these need to be mapped, and which can be skipped.
The mapping will typically involve interviews and workshops
with those involved to understand the processes. These will
then be mapped using a tool such as Visio or Holocentric
Modeller. They are then reviewed by the users. At this point,
there will probably be some changes to the documented processes
and additional processes identified. As they are mapped, they
can be verified by users and finalised.
When mapping the processes use the Business Process Modeling
Worksheet to manage the various process maps and status of
the work. You can use the numbering system in the worksheet
to identify each process map.