Files
ARCADIA-Studio/docs/research-v2-ui.md
T

3.2 KiB
Raw Blame History

Original Capella runtime inspection — V2

2026-09-05, Windows, installed Capella 7.0.1. The lead engineer used native Computer Use to reopen the repaired application, import its bundled In-Flight Entertainment System example through the UI into the isolated D:/CodexBuilds/Capella2-v2-01a06e2e/capella-workspace, and inspect the following. The installed original sample was not edited. These are observations of Capella, not evidence of Studio V2 behavior.

  • At 1009×763 the Activity Explorer provides explicit OA/SA phase tabs and engineering tasks. The diagram browser and long task labels are cramped. Maximizing to 2560×1392 exposes the full task flow and diagram list.
  • System Analysis tasks include transition from operational activities; actors/missions/capabilities; functional refinement/exchanges; allocation to System/Actors; interfaces/scenarios. This is useful contextual guidance, though the many separate tool panes consume substantial canvas space.
  • Opened [SAB] High Level System Overview: blue System/Actor containers, green functions inside, external Passenger/Aircraft/Cabin Crew/Ground Operator. Nested work makes allocation readable. Dense orthogonal edges, truncated labels, small ports and a long palette add clutter; focused views and progressive disclosure should improve this.
  • Selected Manage Video and Audio Diffusion. Properties expose condition, mode/state availability and realized operational activities. The semantic browser shows computed allocating actor/component, incoming/outgoing exchanges, decomposition, parent and related diagrams. This independently confirms that displayed nesting and functional parent differ.
  • Expanded the OA model tree: activities, capabilities, interfaces, data, roles and operational entities. Selected Broadcast Movies; semantic browser showed Aircraft allocation, operational process, several realizing System Functions, outgoing interactions and Cruising/Takeoff state availability.
  • Opened the context menu and Transitions submenu. An OA activity offers Functional Transition, Activity to System Capability, and Activity to System Mission. Started Functional Transition: a real comparison dialog shows Synthesis, Candidate model, Resulting model, Details, Apply/OK/Cancel and 23 differences under root System Function. Cancelled without applying. Studio should show meaningful choices directly and explain dependency scope before commit.
  • Navigated directly from the semantic browser to [OAB] All Operational Activities and Entities. Yellow activities are allocated inside participant containers; Pilot and Cabin Crew are nested in Crew. A blue highlighted operational process traverses three activities while ordinary exchanges remain thin. This is the desired separation of containment, allocation and selected behavior emphasis.

V2 adaptations: visible OA/SA switch and task context; focused hierarchy plus inspector; independent semantic parent and performer; nested containers with restrained semantic colors; selective edge emphasis; direct two-way counterpart and source navigation; explicit create/link/compare actions; transition preview with readable field changes and atomic undo. No copied assets or claims of native Capella interchange.