Poesis
Usage / Use case Planned
Inspect a change before committing to it
Trace affected definitions and obligations, then record what remains unknown before deciding.
Enterprise Architect / CTO / CIO / Platform / Ops / SRE lead
Platform
What serves this use case
Features
Values
Values composed with this use case
- Value Partial
Reduce uncertainty about a specified change
Bring relevant context and affected definitions into a shared review, making dependency paths and missing evidence visible before deciding.
Supported by Capabilities(2)
Supported by Features(2)
- Value Planned
Coordinate IT work around shared definitions.
Reuse common inputs across appraisal, analysis and document generation so profiles can review decisions against the same definitions. Outputs and scenarios remain subject to review.
Supported by Capabilities(1)
Supported by Features(3)
- Value Planned
Inspect possible effects before deciding.
Follow dependency and obligation paths to affected definitions. Timing, probability and causal predictions belong to the further simulation scope.
Supported by Features(1)
Realized through Use cases(2)
Pains
Pain points
- Pain point Planned
Impact analysis is a guess made in a meeting.
Coupling is discovered in incident reviews, after the change shipped.
Addressed by Capabilities(1)
Addressed by Features(1)
Experienced by Actor types(6)