Codex
01bb52a76d
Rust checks / check (ubuntu-latest) (push) Canceled after 0s
Rust checks / check (windows-latest) (push) Canceled after 0s
45 lines
2.6 KiB
Markdown
45 lines
2.6 KiB
Markdown
# Native Capella scenario benchmark — 2026-09-10
|
||
|
||
Codex-956atf /root used the installed Capella 7.1 executable through Computer
|
||
Use in an isolated `.local/capella-reference-20260910` workspace. The generated
|
||
project is `Behavior workflow benchmark`; no existing user model was opened.
|
||
This evaluates reference-product behavior, not the current Studio binary.
|
||
|
||
At the observed 1010×760 window size:
|
||
|
||
- Operational Analysis → Define Operational Activities and describe Interactions
|
||
exposes creation of activity breakdown, interaction and activity-scenario views.
|
||
The scenario workflow created `[OAS] Response workflow` and its capability.
|
||
- The right scenario palette exposes Activity, Activities, Interaction,
|
||
Interaction with return branch, Reference, LOOP and Operand. Activity is a
|
||
direct point-placement tool: clicking the canvas created a represented activity
|
||
and a lifeline. The lifeline is a separate InstanceRole, not the work definition.
|
||
- Selecting LOOP and dragging a region across the lifeline created a visible
|
||
combined fragment. Its tooltip explains the repeated scenario part and covered
|
||
lifelines. The actual drag created one operand and explicit start/end records.
|
||
- Selecting the new object expanded formatting/context controls and moved the
|
||
canvas vertically. Preserve direct interaction and coverage meaning in Studio
|
||
without copying this unstable canvas origin or the clipped palette labels.
|
||
|
||
Ctrl+S saved the model, and the saved XML independently confirms:
|
||
|
||
| Record | Identity / relationship |
|
||
|---|---|
|
||
| Activity | `04b58488-e33b-4693-ae8d-6f830cbc0cf3` |
|
||
| Scenario | `49f702e0-1e0d-45c2-a0e8-e40545ce5b6c`, kind INTERACTION |
|
||
| InstanceRole | `29115069-194d-4c1a-ac2c-ee86486a04fb`, represents the Activity |
|
||
| LOOP | `1b4a102e-4c20-4e92-bd4f-71e6b677d2fa` |
|
||
| Operand | `ac05a0af-60d1-48f2-9548-17214d3ebdc1`, covers the InstanceRole |
|
||
| Fragment interval | start `8d988d2b-c191-46b2-8c92-1ff1e62251cb`, end `a8c26302-a5bb-49c0-8e7c-d2fe8026fe1a` |
|
||
|
||
These observations support scenario tool/point authoring and explicit occurrence
|
||
versus definition identity. They do not demonstrate wrapping existing messages,
|
||
cross-operand movement, lifecycle drawing or successful scenario reuse; those
|
||
operations were not exercised. Studio's current clicked-slot improvement creates
|
||
an empty typed fragment using its existing occurrence/branch model. Persisted
|
||
horizontal lifeline arrangement and drag-range wrapping need separate design and
|
||
acceptance if adopted; this benchmark does not silently introduce either.
|
||
|
||
After saving, Alt+F4 requested a clean Capella close. Root checks process absence
|
||
before reclaiming memory for compilation; no forced termination was used.
|