bce-diagrams

name	bce-diagrams
description	Create high-level overview diagrams showing interactions between business components (BCs), subsystems, services, or systems. Use when asked to create architecture overviews, BC interaction diagrams, subsystem diagrams, service interaction diagrams, system landscapes, or integration maps. Triggers on "diagram", "overview diagram", "BC interaction", "business component diagram", "subsystem diagram", "service interaction", "component interaction", "architecture overview", "system diagram", "integration diagram", or requests to visualize how BCs, subsystems, or services communicate. Not for detailed class diagrams or sequence diagrams.
argument-hint	[services or components to visualize]

BCE Overview Diagrams

Create diagrams that show interactions and dependencies between business components (BCs), subsystems, and external services at a high level of abstraction. Based on BCE architecture (see bce.design).

BCE Terminology

• Business Component (BC) — a feature-based unit grouping related boundary, control, and entity packages. Named after its domain responsibility (e.g., orders, payments, speakers).
• Boundary — the BC's external interface: JAX-RS resources, facades, health checks.
• Subsystem — a grouping of related BCs at a higher level of abstraction.
• In "between components" mode, show BCs and subsystems as opaque nodes. In "within components" mode, expand BCs to show their boundary, control, and entity layers.

Workflow

1. Gather information - Identify BCs, subsystems, and external services to visualize. Analyze the codebase package structure () or use the user's description.