1. CPSC 875 John D. McGregor C10 – Physical architecture

2. Logical/physical architecture Logical – Whose connected to whom – Data types – Flows inside and between components Physical – Runtime structures that implement the logical structure – Process, thread, and subprogram

3. Physical architecture All architectural elements have the same basic outline of features, flows, properties, etc. What makes them different are the properties All of the physical entities are bound to hardware using Allowed and Actual bindings Certain analyses can not be done until there is a binding

4. Isollete example

5. Virtual elements Virtual bus – a protocol over a hard technology such as TCP/IP over ethernet Virtual processor – an ARINC653 partition on a physical processor

6. Abstract elements Abstract elementName End AbstractName; Does not constrain the type of the element Device elementNameConcrete extends elementName End elementNameConcrete;

7. process implementation control_rt.speed extends control.speed subcomponents scale_speed_data: refined to thread read_data.speed {Dispatch_Protocol => Periodic; Compute_Execution_Time => 1 ms.. 2 ms; Period => 50ms;}; speed_control_laws: refined to thread control_laws.speed {Dispatch_Protocol => Periodic; Compute_Execution_Time => 3 ms.. 5 ms; Period => 50ms;}; end control_rt.speed;

8. abstract interface features set_speed: out data port; disengage: out event port; BA1: requires bus access Marine.Standard; end interface; device sensor features sensor_data: out data port; BA1: requires bus access Marine.Standard; end sensor; device actuator features cmd: in data port; BA1: requires bus access Marine.Standard; end actuator;

9. system implementation Complete.PBA_speed_control_ab subcomponents speed_sensor: device sensor.speed; throttle: device actuator.speed; speed_control: abstract control.speed; interface_unit: abstract interface.pilot; RT_1GHz: processor Real_Time.one_GHz; Standard_Marine_Bus: bus Marine.Standard; Stand_Memory: memory RAM.Standard; connections DC1: port speed_sensor.sensor_data -> speed_control.sensor_data; DC2: port speed_control.command_data -> throttle.cmd; DC3: port interface_unit.set_speed -> speed_control.set_speed; EC4: port interface_unit.disengage -> speed_control.disengage; BAC1: bus access Standard_Marine_Bus speed_sensor.BA1; BAC2: bus access Standard_Marine_Bus RT_1GHz.BA1; BAC3: bus access Standard_Marine_Bus throttle.BA1; BAC4: bus access Standard_Marine_Bus interface_unit.BA1; BAC5: bus access Standard_Marine_Bus Stand_Memory.BA1; end Complete.PBA_speed_control_ab;

10. system implementation Complete_rt.PBA_speed_control_ab extends Complete.PBA_speed_control_ab subcomponents speed_control: refined to process control_rt.speed; interface_unit: refined to device interface_rt.pilot; properties Period => 50ms applies to speed_control.scale_speed_data; Compute_Execution_Time => 1 ms.. 2 ms applies to speed_control.scale_speed_data; Period => 50ms applies to speed_control.speed_control_laws; Compute_Execution_Time => 3 ms.. 5 ms applies to speed_control.speed_control_laws; Dispatch_Protocol => Periodic applies to speed_control.scale_speed_data, speed_control.speed_control_laws; end Complete_rt.PBA_speed_control_ab;

11. Next steps Read: – http://hbswk.hbs.edu/item/5699.html At the bottom of the page there is a place to download “Full Working Paper Text” http://hbswk.hbs.edu/item/5699.htmlFull Working Paper Text – http://www.sei.cmu.edu/reports/07tn043.pdf Design the CACC at both the logical and physical levels – The AADL model should include at least one state machine – Each component should have an error model – Define and bind to a platform Create the DSM for your architecture so far Due Feb 23 rd by 11:59 pm