Modelling at the actor-task level (15%) Flashcards
Actor-Task view
Level 3
Documents the steps needed / work needed to complete the task
Rationale for task analysis
- Useful for improvement as it understands work in detail
- Uncovers decisions made and identifies alternative scenarios
Task Analysis
Task description for each task
(ASCOMBINES)For each task in the process we need to know the following:
Name of the task
Actor / role carrying out the task
Business event triggering the task
Inputs to the task
Outputs expected from the task
Costs associated with the task
Measures / metrics applied to the task
Standards that constrain the task
Business rules that are to be followed
Detailed breakdown of steps within the task
Documenting steps of tasks
- Narrative
- UML activity diagram notation (single lane)
- Use case description
- Structured English
2 Types of Business Rules
Constraints: restrict how an activity is performed (internal/external)
Outside world: customers must pay VAT on cinema tickets
Other parts of the business: never leave single seats unfilled in the middle of a row
Operational Guidance: determine how activities are done (external/internal)
External: how to calculate VAT on cinema tickets
Within the business: what to do when if we can’t seat a group of customers together
How do do we measure performance of a task
TQC
3 E’s
Note that improving the efficiency of a task may not improve the efficiency of the process overall
Use Case Descriptions
Actor
Use Case (task) name
Goal of the use case
Event that starts the Use Case
Preconditions that must obtain to allow the use case to start
Postconditions that will be in place after each flow
The Main Flow of steps (ie, the most common/happy flow)
The Alternate Flows
Structured English decision
IF THEN (decisions)
ELSE(IF) (if no above conditions apply
ENDIF
Structured English - Repeat task
DOWHILE condition…ENDWHILE (repeats while condition is true)
DOUNTIL condition…ENDUNTIL (repeats while condition is false)
DO
DOUNTIL payment successful OR there are no more payment methods
IF payment method is cash THEN
take cash payment
IF change required THEN
give change
ENDIF
ELSE IF payment method is cheque THEN
check details
IF details not correct
reject cheque
ENDIF
ELSE
key in amount on card machine
ask customer for PIN
ENDIF
IF payment successful THEN
generate receipt
ELSE
ask for alternative payment method
ENDIF
ENDUNTIL
ENDDO
Here is the translation of the structured English into sentences:
Do the following until payment is successful or there are no more payment methods available.
If the payment method is cash, accept the cash payment.
If change is required, provide the necessary change.
Otherwise, if the payment method is a cheque, verify the cheque details.
If the details are not correct, reject the cheque.
If none of the above conditions apply, key in the payment amount on the card machine and ask the customer for their PIN.
If the payment is successful, generate a receipt.
If the payment is not successful, ask the customer for an alternative payment method.
Repeat the entire process until payment is successful or there are no more payment methods available.
Task Analysis description
Actor: Role/group/system with responsibility of performing the task
Event: Event that triggers the task (other than initial task, each task initiated by a sub event)
Input: Information required to start work
Output: Deliverable produced from conducting the task
Cost: Cost associated with performance of the task
- i.e. Average time to handle call is 3 mins equates to 1/20 hourly rate
Performance Measure: Evaluate the performance of the task. Concerned with 1) Accuracy 2) Timeliness
- Normally start with a verb i.e. Complete call within 5 mins / Check identity of 100% of calls
Steps: Individual actions (actor may be require to apply BR when performing a step)