When I model business processes, I also prepare for failure. Not every task works as planned. That is why I use an error event in BPMN. It helps me show where something can go wrong and how the process should react. In this article, I explain the main error event types and show how they create clear failure paths in a real-world BPMN example.
BPMN 2.0 Error Events: Semantics, Scope, and Use Cases Read More »
When a customer message changes a process, I need a clear BPMN response. That is when I use an attached message event in BPMN. It can interrupt a task or react without stopping the current work. This helps me model feedback, urgent updates, and alternative paths in a clean way. In this article, I explain the concept with a simple BPMN 2.0 example step by step.
BPMN Message Boundary Events Explained: Behavior and Use Cases Read More »
Embedding a diagram on a website should be simple and useful. That is why I explain How to embed an IFrame draw.io diagram in this guide. You’ll learn the step-by-step process, the benefits of iframe embedding, and how this method can improve sharing, presentation, and collaboration in real business use. If you’d prefer to watch
How to Load a draw.io Diagram in an IFrame Read More »
Communication drives every successful process. That’s why I rely on message events in BPMN when different participants need to exchange information. In this article, I’ll show you how message events work and how you can model them correctly using BPMN 2.0. Let’s explore each event type through a practical example. I’ll walk you through it step by step.
BPMN 2.0 Message Events Explained: Types, Triggers, and Behavior Read More »
Sometimes, timing is everything in a process. Especially when I wait for multiple signals before continuing. That’s when modeling intermediate events in BPMN 2.0 becomes essential. In this article, I’ll show you how to capture multiple events correctly—without running into dead ends or lost signals.
BPMN Intermediate Events Explained: Modeling Multiple Events Correctly Read More »
Sometimes, a business process must undo a completed action. A payment may be refunded, or a service may be canceled. In BPMN 2.0, I model this with the compensation event in BPMN. It helps me show how a process reacts when earlier work needs to be reversed. In this article, I explain what compensation events are, when I use them, and how they work with a simple example.
BPMN Compensation Events Explained: Purpose, Behavior, and Use Cases Read More »
A signal event in bpmn helps me model communication without one fixed receiver. I use it when a process must announce something broadly and any listening process may react. In this article, I explain all BPMN 2.0 signal events with simple examples, clear use cases, and practical modeling tips. Let’s dive in.
BPMN Signal Events Explained: Purpose, Behavior, and Use Cases Read More »
Whenever I model a business process, I want clarity. Especially when it comes to responsibilities. That’s why I use the nesting of BPMN lanes. This technique gives structure. It shows clearly who does what—without overwhelming the diagram.
How I Structure Responsibilities with Nested BPMN Lanes Read More »
Leadership starts with daily behavior. It shows in how I speak, listen, and decide. Therefore, I see leadership as a visible attitude, not only as a title. Leadership values help me create orientation when pressure rises. They also guide me in complex situations. In this article, I focus on appreciation, communication, responsibility, judgment, equal opportunities, and motivation. As a result, leadership becomes clearer and easier to follow.
Leadership Values: How I Lead with Appreciation, Responsibility, and Trust Read More »
I use draw.io to turn ideas into clear diagrams. However, the editor view can distract during a presentation. Menus, panels, and toolbars help me while I work. But they can also pull attention away from the final diagram. Therefore, I use presentation mode in draw.io. It gives me a cleaner view. As a result, I can present my diagram clearly and guide my audience through each part step by step.
How to Activate the Presentation Mode in draw.io Read More »
I rename files in draw.io when I want a clear structure. A good file name saves time, reduces mistakes, and makes diagrams easier to find. In this guide, I show how to rename a file in draw.io directly inside the editor. I keep each step short and clear. Therefore, you can follow along fast and use the same workflow in many projects.
Renaming a File in draw.io: A Simple Step-by-Step Guide Read More »
The system boundary of T2 defines which responsibilities belong to T2 and which belong to its environment. I use this boundary to separate the T2 core from connected TARGET Services and shared infrastructure. T2 combines Central Liquidity Management (CLM) and Real-Time Gross Settlement (RTGS). Other services exchange liquidity, data, or settlement instructions with T2, but that does not make them part of T2. A clear boundary therefore keeps requirements, interfaces, ownership, and testing precise.
Defining the System Boundary of T2 Read More »
When I analyse T2 in TARGET Services, I do not treat it as an isolated payment system. I place it inside the wider Eurosystem infrastructure for payments, securities, instant payments, and collateral. This context matters because many important T2 requirements arise at service boundaries. Liquidity moves between systems. Collateral affects credit. Settlement depends on connected services. Therefore, I first define the landscape, responsibilities, and interfaces before I analyse individual T2 functions.
TARGET Services T2 in the TARGET Landscape Read More »
When I analyse T2, I start with its purpose. T2 Objectives explain why the Eurosystem operates this infrastructure and which outcomes its design must support. T2 is more than a platform for large-value payments. It links settlement in central bank money with monetary policy, financial stability, and efficient liquidity management. Therefore, I use these objectives as the basis for understanding its core capabilities, quality requirements, interfaces, and operational rules across TARGET Services.
T2 Objectives: Why T2 Exists for Monetary Policy, Stability, and Efficiency Read More »
When I analyse T2 within TARGET Services, I start with its role in the Eurosystem. T2 is the core service for settling large-value and other time-critical payments in central bank money. It connects payment settlement with central liquidity management and supports monetary policy operations, interbank transfers, and commercial payments. Therefore, understanding T2 means understanding how the Eurosystem moves liquidity safely, finally, and efficiently across its financial market infrastructure.
What Is T2 within TARGET Services? Read More »
TARGET Services T2 – System Analysis Article Series Part 1: Strategic & Business Context Article 3 When I analyse payment infrastructures, I start with T2 Stakeholders. T2 sits at the heart of the euro payment system. Therefore, many parties depend on it, shape it, or govern it. In this article, I identify the key stakeholder
Who Are the Stakeholders of T2 at TARGET Services? Read More »
What is a requirements attribute schema? I use an attribute schema to describe requirements with consistent information. It defines which attributes I record, what they mean, and which values I allow. Typical attributes include priority, status, source, risk, effort, owner, and release. Therefore, I can compare requirements, detect missing information, filter large requirement sets, support traceability, and improve requirements management.
What Is a Requirements Attribute Schema? Read More »
Forms of requirements presentation shape how teams understand, discuss, review, and implement requirements. I use the right presentation form to create clarity and reduce misunderstandings. For example, I can document requirements as text, models, diagrams, tables, or user stories. Therefore, the chosen form strongly influences communication, validation, and project success.
Forms of Documenting Requirements Presentation Read More »