Skip to main content

EPC

This document was generated using AI assistance

Content may include inaccuracies, outdated information, or technical errors. Users are advised to cross-check critical information before implementation.

An event-driven process chain alternates events and functions. An event describes the state the process has reached, a function describes the work that follows that state. Gateways split the chain into branches and bring them back together.

The start of an event-driven process chain: an event, the function that answers it and the event that function produces

Create the model​

Create a model Interview Process of the type EventDrivenProcessChain (EPC) and open its diagram.

The notation is defined by a metamodel in another project, so creating the model adds that project to the imports, see Importing notations.

The first gateway​

  1. Create an Event Candidate applied.
  2. Create a Function Recruiter reviews the CV and draw a ControlFlow from the event to the function.
  3. Create an XorGateway Does the CV meet the requirements? and draw a control flow from the function to the gateway.
  4. Create the events CV approved and CV rejected and draw a control flow from the gateway to each. Name the flows Yes and No.

The CV rejected path ends here; the chain continues from CV approved.

Interview stages​

Every stage consists of four elements: a function schedules the stage, an event reports that it is scheduled, a second function runs it, a gateway judges the result. For the phone screen:

Schedule the phone screen → Phone interview scheduled → Run the phone screen → Phone screen passed? → Screen passed / Candidate failed the screen.

Build the technical, system design and behavioural stages the same way. Each starts from the success event of the one before.

Finish the chain with the function Hold the hiring committee review, the function Prepare and send the offer, the event Offer sent and the gateway Did the candidate accept the offer?.

Who does the work​

Create four Participant elements: Recruiter, Technical interviewer, Hiring manager and Hiring committee. Draw a Responsibility relationship from each to the functions it performs.

Systems and resources attach the same way: Automation names the ApplicationSystem behind a function, ResourceFlow what a function consumes or produces - a Document, a Database or another Resource.

The table​

Open the model as Event Driven Process Chain Table. Every event, function, gateway and participant takes its own row. The table makes it easier to check that every gateway has both branches and every function has someone responsible for it.