Abstract Process

Intro

An Abstract Process represents interactions between a process and its environment without detailing internal steps. In EA, it provides a high‑level contract for how a process should interact with external parties or services.

Key points:

• Defines external touchpoints and expected inputs/outputs
• Improves interoperability by decoupling internal logic
• Common use cases: BPMN collaboration views, partner integrations, service orchestration, application workflows, compliance mapping
• Pitfall: missing assumptions or data contracts can cause misalignment

Examples:

• Procure‑to‑Pay abstract process showing supplier and finance interactions
• Customer onboarding abstract process interacting with KYC services
• Incident management abstract process connecting to ticketing and comms

In practice:

For related methods and governance, see Business Process Management.

Related terms: Process; Sub‑Process; Choreography

FAQs:

Q: How is an abstract process different from a detailed process?
A: It focuses on external interactions, not the internal sequence of activities.

Q: When should I use an abstract process?
A: When defining contracts with external systems or partners without exposing internal logic.

‍