Activity

Intro

An Activity is work performed by an organisation using business processes. In enterprise architecture, defining activities helps model how work is executed and understood across processes and tasks.

Key points:

• Clarifies units of work within process models
• Supports consistent design of Sub-Processes and Tasks
• Common use cases: EA process modelling, BPM notation, workflow definition, application orchestration, technology automation
• Pitfall: confusing atomic vs compound activities can break traceability

Examples:

• Process activity that aggregates multiple tasks to deliver a step
• Atomic task activity executed by a single system or user
• Sub-Process activity reused across several business processes

In practice: With OrbusInfinity, teams link this concept across strategy, processes, applications, and technology for traceability.‍

Related terms: Process; Sub-Process; Task

‍FAQs:

Q: What’s the difference between an activity and a task?
A: A task is atomic; an activity can be compound and include multiple tasks.

Q: Where do activities appear in EA?
A: In process models and workflow designs that map how work is performed.

‍