Massimo

Diagram editor interface showing a timed start (“Start the task every Monday at 9:00 am.”) leading to reminder and logging steps.

BPMN 2.0 Message Events Explained: Types, Triggers, and Behavior

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 »

Partial screenshot of a diagram editor showing tasks, gateways, and labeled compensation-style icons under two tasks.

BPMN Compensation Events Explained: Purpose, Behavior, and Use Cases

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 »

Leadership Values: How I Lead with Appreciation, Responsibility, and Trust

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 »

How to Activate the Presentation Mode in draw.io

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 »

Defining the System Boundary of T2

I define the T2 system boundary with a clear, CPRE-style scope cut. I place CLM and RTGS inside T2, because they form the T2 Service core. Then I keep connected systems outside on purpose, even if liquidity and messages flow constantly. This way, I prevent scope creep. Moreover, I write requirements with stable ownership and test scope.

Defining the System Boundary of T2 Read More »

TARGET Services T2 in the TARGET Landscape

When I analyse payment infrastructures, I start with context. I skip screens and message fields at first. Instead, I map where T2 in TARGET Services sits and why its neighbours matter. This matches the CPRE (IREB) mindset. First, I define scope and interfaces. Then, I derive requirements that fit reality. T2 works with CLM, TIPS, T2S, and ECMS. Therefore, I treat interactions as core analysis objects and avoid rework.

TARGET Services T2 in the TARGET Landscape Read More »

T2 Objectives: Why T2 Exists for Monetary Policy, Stability, and Efficiency

When I analyse a payment and market infrastructure system, I start with “why”. I do not start with screens, messages, or data fields. Instead, I clarify business goals and policy aims first. This mindset fits the CPRE approach from IREB. CPRE anchors requirements in goals, stakeholders, and context. Therefore, T2 Objectives2 become my compass for every later requirement decision.

T2 Objectives: Why T2 Exists for Monetary Policy, Stability, and Efficiency Read More »

What Is T2 within TARGET Services?

What Is T2 TARGET Services? I describe T2 as the Eurosystem’s core service for settling large-value euro payments in central bank money. It combines Central Liquidity Management and RTGS, and it connects to other TARGET Services via liquidity transfers and harmonised operating schedules. For requirements engineering system analysis, I use T2 to derive scope, actors, timing constraints, and resilience requirements for payment infrastructure.

What Is T2 within TARGET Services? Read More »

What Is a Requirements Attribute Schema?

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 »

Scroll to Top
WordPress Cookie Plugin by Real Cookie Banner