All System Analysis Articles

System context diagram for “Some Software System” with external entities such as User, Sensor Input, Mainframe and Perform Physical Operation connected by arrows labeled requests, readings, queries, commands, data and diagnostic information.




System Analysis is the structured process of examining a system, its components, interactions, and environment to understand how it works and what it must achieve. It provides the foundation for IT Business Analysis and Requirements Engineering by turning complex business needs into clear, structured, and actionable insights.


This page brings together practical articles on System Analysis. Discover how to investigate existing systems, define system boundaries, identify stakeholders, and analyze dependencies. Learn how to uncover hidden assumptions, clarify business objectives, and distinguish between current capabilities and future requirements.


In IT Business Analysis, System Analysis connects business processes, organizational goals, and technical solutions. It helps business analysts identify gaps, evaluate system behavior, and recommend improvements. In Requirements Engineering, it supports requirements elicitation, specification, validation, and traceability. Clear system boundaries and interfaces help prevent misunderstandings, unnecessary complexity, and costly rework.


The articles also explore essential techniques, including:

  • System Context Analysis: Understand external actors, systems, and dependencies.
  • Interface Analysis: Identify information exchanges and integration requirements.
  • Functional Analysis: Examine system capabilities, processes, and behavior.
  • Gap Analysis: Compare existing capabilities with desired outcomes.
  • Impact Analysis: Assess how changes affect components, interfaces, and requirements.

Whether you are analyzing an existing application or designing a new IT solution, these articles offer practical methods and reusable techniques.


Explore System Analysis and learn how to transform complex systems into understandable models, well-defined requirements, and better technical decisions.




Cropped TARGET Services diagram showing the T2 Service CLM area with Main Cash Accounts (MCA), central bank operations, liquidity management, and liquidity transfer arrows.

Defining the System Boundary of T2

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 »

TARGET Services T2 in the TARGET Landscape

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 »

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

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 »

What Is T2 within TARGET Services?

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 »

Scroll to Top
WordPress Cookie Plugin by Real Cookie Banner