Adds ProblemStatement, SuccessDefinition, SpecificNeed, Risk, Project, Responsibility classes, plus SuccessContract-related classes and properties that operationalize success criteria, outcomes, constraints, evidence, beneficiaries, review rhythm, and metric-gaming risk.
BIZ-VAL-O v5.1 — success contract enrichment
BIZ-VAL-O v5.1 — success contract enriched ontology
commits to KPI
Links a success contract to a success criterion included in that contract.
contract defines criterion
Links a success contract to a constraint that must not be violated while pursuing the outcome.
contract has constraint
Links a success contract to a non-negotiable boundary that cannot be traded off.
contract has non-negotiable
Links a success contract to the cadence used to revisit and update the definition of success.
contract has review rhythm
Links a success contract to a rule that decides which priority prevails when objectives or constraints conflict.
contract has trade-off rule
Links a success contract to the specific beneficiary expected to be better off.
contract names beneficiary
Links a success contract to an intended outcome it is meant to govern or evaluate.
contract targets outcome
Links a success criterion to the evidence expected to prove that it has been satisfied.
criterion evidenced by
defines success as
Links success evidence to a quantitative or qualitative measure used to assess it.
evidence uses measure
has responsibility
has risk
Links a project, use case, initiative, solution, or work package to the shared success contract that governs its definition of success.
has success contract
is source of truth for
Links a measure to the risk that it may be optimized in a way that undermines the intent it was meant to represent.
measure has gaming risk
Links an outcome to the named beneficiary that should experience the improvement.
outcome benefits beneficiary
Links a project, use case, initiative, solution, or outcome to the concrete improvement experienced by a beneficiary.
produces beneficiary impact
use case uses dataset
The concrete improvement, benefit, or change experienced by a named beneficiary as a result of an initiative or solution.
Beneficiary Impact
A condition, rule, boundary, or limitation that must not be violated while pursuing an outcome.
Constraint
A quantitative or qualitative way of assessing whether a criterion, outcome, constraint, or impact has been achieved or respected.
Measure
The behavior of optimizing a reported measure while undermining the intent, outcome, or value that the measure was meant to represent.
Metric Gaming
A specific person, role, group, organization, or community expected to be better off because of a project, use case, initiative, or solution.
Named Beneficiary
A constraint, principle, or boundary that cannot be traded off, even when delivery pressure, cost pressure, or stakeholder conflict increases.
Non-Negotiable
A result, state change, or practical improvement that an initiative is intended to produce for a stakeholder, beneficiary, process, system, or organization.
Outcome
An articulated problem a stakeholder wants resolved. Narrower than archimate:Driver: treated as a linkable resource rather than a free-text literal so the same problem can be referenced by several use-cases, solutions, and success definitions.
Problem Statement
A bounded, funded effort delivering a set of outcomes. Narrower than archimate:WorkPackage: adds the connotation of a time-boxed effort with a named owner and budget — distinct from a use-case (which is scoped to a specific need) and a plateau (which is a target architecture state).
Project
A bounded duty or accountability that a stakeholder carries with respect to a role, project or use-case. Narrower than archimate:Assessment: treated as a resource so duties can be reassigned, versioned, and traced across reorganisations.
Responsibility
The agreed cadence for revisiting and updating success definitions, criteria, evidence, constraints, trade-off rules, and ownership.
Review Rhythm
A negatively-oriented assessment: a condition or event that could impair the outcomes of a use-case, project, or solution. Narrower than archimate:Assessment; conventionally paired with a probability and impact qualifier (captured via datatype properties in future revisions).
Risk
A concrete, often verbalised, need a stakeholder expresses — typically a refinement of a broader ProblemStatement. Narrower than archimate:Driver.
Specific Need
A shared, explicit agreement defining what success means for a project, use case, initiative, or solution, including success criteria, evidence, constraints, owners, trade-off rules, and review rhythm.
Success Contract
A specific condition that must be satisfied for a project, use case, initiative, or solution to count as successful.
Success Criterion
A stakeholder's operational definition of what counts as success for a use-case, solution or project. Narrower than archimate:Goal: scoped to a single stakeholder's viewpoint so different stakeholders can hold divergent success definitions for the same artefact.
Success Definition
Observable proof, qualitative or quantitative, showing that a success criterion has been satisfied or that a beneficiary is better off.
Success Evidence
A predefined decision rule specifying which priority, outcome, or constraint prevails when objectives conflict during execution.
Trade-off Rule