State: reading is verified on 52 public ARXML files against autosar-data, every element compared. Editing is verified by 160 chained edits re-read strictly by autosar-data, 118 of them validated against the AUTOSAR schema the file names. Not yet run against DaVinci Developer or ISOLAR-A; no customer project.
Read the design
From AUTOSAR 4 ARXML files (schemas 4.1.2 to R23-11), with references followed through the workspace's other ARXML files:
- component types of every kind (application, sensor-actuator, composition, service, complex device driver, ECU abstraction, NV block, parameter, service proxy) with their P-, R- and PR-ports and
MAY-BE-UNCONNECTED; - port interfaces: sender-receiver, client-server (operations with arguments), mode-switch, parameter, NV data and trigger, and whether each is a service interface;
- internal behaviours: runnables with their data access points, server call points and mode access points; RTE events of every kind with the runnable each starts and a timing event's period;
- compositions: component prototypes and assembly and delegation connectors, as a table of connections and as an outline of prototypes and ports;
- data types: application and implementation data types with category, computation method, unit, base type and data type mapping sets.
See the design checked
Problems (source "Software Components") reports: a port that names no interface or the wrong kind; a required port nothing in its composition connects (not for service ports, ports marked MAY-BE-UNCONNECTED, or unknown interfaces); a connector between incompatible interfaces, of the wrong direction, or to a port the prototype's type does not have; a data type differing between the two ends (a warning); an event that names no runnable and a runnable no event starts; an application data type no mapping set maps.
Design in the Software Components editor
Run Open Software Components (Command Palette, an ARXML file's editor title, or Reopen Editor With).
- The file's component types, interfaces and data types as a tree, filtered by name, kind or interface, each with the worst problem it holds.
- The selected element as a form, with links to the elements it names and to those that use it, and its problems at their rows. Show in Text opens it in the ARXML.
- From the forms: Add a Component Type, Add a Port Interface, Add a Port to ..., Add a Data Element, Add an Operation, Add an Argument, Add a Runnable (writing the internal behaviour when there is none), Add an Event That Starts ... (timing, init, background, data received, operation invoked) and Add a Component Prototype; change a port's interface, a data type, an argument's direction, an event's runnable and period, a prototype's type; rename or remove any of them. References are picked from valid targets only.
- Connect Ports offers only the compatible ports of the composition; the others are listed under "Not possible, with the reason" (direction, interface kind, missing elements).
Connect Ports offering the one compatible provided port, with every other port listed with the reason it does not fit, and the unconnected required ports flagged in Problems.
Every change is one minimal edit of the ARXML text, placed where the AUTOSAR schema orders it. A change in one file is one undo step shared with the text editor; a rename or removal reaching other files is one workspace edit, undone in one step. Agents use describeSoftwareComponents (read only) and connectSoftwareComponentPorts (writes one connector, unsaved, after the chat's confirmation).
Not verified: no file written here has been opened in DaVinci Developer or ISOLAR-A. The design is read from its ARXML only, so a rename does not reach a name one of their diagram files may hold. Compatibility follows the AUTOSAR rules for interfaces of the same kind by element name.