I have a common design pattern in my work that I am not sure how to best represent in Arcadia. Often I will (1) Buy a computer (hardware), (2) Take an operating system image, (3) develop custom software, (4) integrate the hardware, operating system and custom software together.
When I try to model this with a PAB I get a diagram similar to the attached example ‘PAB-Embedded Computer.png’. This looks good, except that Capella won’t let me do a Component Port Allocation for the RS-232 physical link to the flow port GPSD Service. Therefore I assume that isn’t valid Arcadia syntax. The focus here is on the Embedded Linux behavioural component.
Alternatively, I am able to draw Component Exchanges between the Embedded Linux and GPSD Service components. From there I can draw a Component Port Allocation from the RS-232 Physical Link ports to flow ports on the Embedded Linux component.
The intent of my modelling threefold:
- To explain the functional exchanges in the system.
- To identify which physical links each functional exchange will take place upon.
- To provide a comprehensive list of components to populate in my build strategy.
My questions are:
*How should I be structuring the behavioural components when it comes to software images or operating systems and the software installed onto them?
*Capella has several tools in the Palette that use the word ‘Deployment’. For example, ‘Manage Behavior PCs Deployment’. However, the word ‘Deployment’ isn’t used in Jean-Luc Voirin’s book on the Arcardia method in this way. What word in Jean-Luc’s book is synonymous with ‘Deployment’ in Capella so I can understand this further?
Thanks in advance.