add explanation of business and technical context

[gernotstarke]

the distinction of business and technical context needs explanation - likely in our to-be-created content repository #788

[alxlo]

My Take on this:

Context View

What it shows: The system's external boundary and its relationships to external entities (users, other systems, data sources, external services). The system is shown as a black box; everything outside it is the environment.

Two sub-forms — distinct perspectives on the same system boundary:

Business context — answers who and why:

• External actors: users, partner organizations, regulatory bodies, adjacent business systems
• Relationships expressed in domain/business terms: data flows, service dependencies, business events
• No technical details (protocols, formats, or implementation specifics)
• Target audience: product owners, business stakeholders, domain experts
• Created first — helps identify missing requirements and clarify scope

Technical context — answers how:

• External systems and the technical channels/protocols used for communication
• Protocols (REST, AMQP, JDBC), message formats, authentication mechanisms
• Network boundaries and communication directions
• Target audience: developers, architects, infrastructure teams
• Documents interface obligations with external systems

Why both? The same system boundary is described differently depending on what question you are answering. A business stakeholder cares about which customer data flows to the CRM; an infrastructure engineer cares about which TCP port and which API endpoint. Both perspectives are valid and necessary — they serve different stakeholders.

Important: Internal technical details do NOT appear in the context view — only external interfaces are shown. The system remains a black box.

What it documents:

• External interfaces of the system
• Which external entities the system interacts with
• The direction and nature of those interactions

Why it matters: Defines the system's scope. Everything inside the boundary is "our responsibility"; everything outside is a given constraint. Essential for stakeholder alignment.