Click ‘View Next’ / ‘View Previous’ to see the next / previous modules.
Scroll down to see an overview and the lessons for this module.
Module overview and objectives
This module provides guidance on modelling tasks including a discussion on business rules and task measurement.
The syllabus states that there is no prescribed method of documenting tasks. We know that different business analysts and other process modellers will have their own preferred forms of documentation.
The syllabus references the BCS publication, Business Analysis, which contains a ‘discussion’ on the topic. The syllabus also refers to a format for task descriptions in the publication, Business Process Change by Paul Harmon, now in its third edition; the syllabus refers to the second edition.
The syllabus points out that Harmon uses the term ‘activity’ rather than ‘task’ but says that they are effectively the same thing. Given that many modellers develop process hierarchies with more levels than the three proposed in the BCS syllabus, this does not appear to be quite correct; the term, ‘activity’, can refer to an action element at any level in a process model, e.g. Process, Sub-Process, Task and anything in between.
- Be able to describe a task in such a manner that it can be understood by business stakeholders and by system development staff.
- Be able to answer questions on tasks in the open book, provider written, form of the BCS exam, ‘Certificate in Business Process Modelling’.
- Be able to answer questions in future centrally written, multi-choice, forms of the BCS exam, ‘Certificate in Modelling Business Processes’.
Terms used in the syllabus
Note particularly the following terms specified in the syllabus:
Task, activity, trigger, business event, (task) inputs, (task) outputs, step, decision tree and decision table.