system-composer

Programmatically building a System Composer architecture model requires an idempotent MATLAB script that uses the architecture-modeling API to create components, assign typed ports, apply stereotypes, and establish correct port connection ordering.

Port connections fail in System Composer models due to call-order mistakes and connection direction mismatches. Ensuring correct `connect(srcPort, dstPort)` dispatch and resolving interface dictionaries before connecting ports prevents missing connections.

To ensure idempotent builds for architecture models, your MATLAB script must recreate artifacts from scratch, arrange layouts explicitly, and save interface dictionaries properly using `dict.save` followed by re-fetching before finalizing the model.

Unresolved interface dictionaries occur when profile save errors and dictionary resolution timing are mishandled. Properly saving the `.sldd` file and re-fetching the interface before applying profiles ensures stereotypes resolve correctly.

System Composer architecture modeling does not support block-diagram edits, as those are intended for Simulink models. The architecture-modeling API strictly enforces separation from block-diagram edits to maintain structural integrity.

Fixing createAllocationSet signature mismatches during architecture verification requires using the correct API call patterns for allocation sets and ensuring sequence and interaction-aware verification parameters match the System Composer schema.