Poesis
Usage / Use case Planned
Bind selected obligations to an organizational scope
Establish the subjects, conditions and accountable interpretation that make selected obligations applicable to a specific adopting scope.
Platform
What serves this use case
Features
Values
Values composed with this use case
- Value Partial
Make obligation applicability explicit
Separate reusable templates and vocabulary coverage from the subjects, conditions and accountable interpretation that establish applicable obligations.
Supported by Affordances(1)
Supported by Capabilities(1)
Supported by Features(1)
- Value Partial
Review obligations together.
Reuse selected packages in one scoped review, with applicability, conflicting obligations and missing evidence visible for resolution.
Supported by Affordances(1)
Supported by Capabilities(1)
Supported by Features(1)
- Value Partial
Start from reusable vocabulary.
Build on selected sourced content, then focus authoring effort on installation, interpretation and bindings for your domain.
Supported by Capabilities(1)
Supported by Features(7)
Pains
Pain points
- Pain point Partial
Selected vocabulary and unbound templates are mistaken for complete, applicable obligations.
Subjects or concerns are omitted and requirements are applied without a justified adopting scope.
Addressed by Affordances(1)
Addressed by Capabilities(2)
Addressed by Features(7)
Experienced by Actor types(5)
Addressed through Use cases(6)