Native terminology
SAP patent US8365136B2; priority 2008-03-10.
Derive parallel process fragments from object lifecycle states and action relationships.
Preserve what the model says and how it works before interpreting its relevance to another system.
SAP patent US8365136B2; priority 2008-03-10.
State-transition-to-workflow derivation and constraint-aware parallelization.
Key precedent for deriving executable structure from existing object models rather than assembling a purely sequential checklist.
Provisional author analysis; follow linked sources for the original descriptions and claims.
| 01. Identity | SAP patent US8365136B2; priority 2008-03-10. |
|---|---|
| 02. Meaning | Composition derives coordinated activities and potential parallel control flows from object lifecycles and relationships. |
| 03. Purpose | Construct process models that recognize dependencies and possible parallelism. |
| 04. Elements | Object lifecycles, states, transitions, actions, preconditions, effects and relation graphs. |
| 05. Structure | Receiving engine, computation engine, relations engine and parallel process engine. |
| 06. Composition | Compute actions and their conditions from states/transitions; derive inter-action relations; generate parallel process fragments. |
| 07. Operation | Generates process models that can support parallel execution; model generation must be distinguished from runtime enactment. |
| 08. Results | Process models and parallel process fragments reflecting action relationships. |
| 09. Assurance | Preconditions, effects and relations provide explicit grounds for consistency checking; execution proof is separate. |
| 10. Standing | Granted patent and published disclosure; operational deployment not established by this record. |
This evaluation grammar is XTechGroup's, not necessarily native to the external model.
Business objective reflected in process model
Action relations and preconditions/effects
Object state transitions
Parallel process fragment generation
Notes are saved locally in your browser when supported. Use Export to create a durable JSON backup; Import restores it. Editing notes does not change the authored model records.