Object-Process Methodology, OPM
Updated 2026-08-13
INTRODUCTION
English translation pending.
CORE DEFINITION
Object-process methodology represents a system with just two kinds of element, objects that exist and processes that transform them, expressed in a single diagram type called an object-process diagram. It aims to unify structure and behaviour that other notations separate into class and activity diagrams. The qualification is that the single-model approach demands discipline, since a diagram mixing both concerns without a clear rule about what changes becomes harder to read than two focused views.
SCAFFOLDING EFFECT
Reduce cognitive load
- Use Unified View: draw objects and the processes that change them on the same diagram. - Use Transformation Check: verify that every process is linked to the objects it creates, consumes, or alters.
Anchor fast decisions
Structure without behaviour cannot show how the system changes, and behaviour without structure cannot show what is being changed. Linking each process to the objects it affects keeps both in one frame, so inconsistencies between the two views appear as unlinked elements instead of hiding between documents.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Object_Process_Methodologyverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS