Poesis
Usage / Use case
Trace a software incident to affected business processes
Trace an observed software incident through identified deployed components and service dependencies to affected business processes and owners, distinguishing confirmed disruption, possible exposure and missing evidence to prioritize response.
Incident commander / IT service owner / Application owner / Business-process owner / Platform / Ops / SRE lead
Platform
What serves this use case
No platform coverage declared.
Values
Values composed with this use case
- Value Planned
Prioritize incident response by business consequences
Connect observed software disruption to affected business processes and accountable owners, separating confirmed impact from possible exposure so response and communication follow justified priorities.
Realized through Use cases(1)
Pains
Pain points
- Pain point Planned
We know which software failed, but not which business processes are disrupted or whom to notify.
Response priorities follow technical alarms instead of confirmed business consequences, delaying workarounds and recovery for critical activities.
Experienced by Actor types(5)
Addressed through Use cases(1)