Transaction

Term

Transaction

Aliases

-

Identity

  • Term ID: src/main/doxsite/glossary/development-process/transaction.dox

  • English label: Transaction

  • Japanese label: トランザクション

  • Category: Development Process

  • Status: normative

  • Definition authority: SimpleModeling BoK

Definition

A Transaction is a platform mechanism that treats multiple state changes as one execution boundary, committing them on completion or restoring a consistent state on failure.

UML

Not applicable. Transaction does not define the UML classification of Classes or Objects.

CML

CML can describe operation preconditions, postconditions, invariants, and state changes. Concrete Transaction boundaries are designed by separating domain meaning from platform realization.

Scala

Scala can implement Transaction control, but a language-level function call or exception boundary is not automatically a Transaction boundary.

simplemodeling-lib

simplemodeling-lib provides contracts for states, constraints, and results, but no single generic Transaction runtime is treated as this term’s canonical definition.

Public Usage

Japanese videos introduce the term as トランザクション(transaction).

Boundary

  • Transaction is not synonymous with Use Case, Operation, or Capability.

  • A domain business unit and a technical Transaction boundary are not necessarily one-to-one.

  • Platform

  • State

  • Operation

  • Invariant

  • Precondition

  • Postcondition

References

  • src/main/doxsite/glossary/development-process/platform.dox

  • src/main/doxsite/glossary/object-foundation/invariant.dox

  • docs/spec/glossary-entry-format.md