uCANca

h1. Systems

We can see the system as a box with inputs and outputs.  The system is able to perform one, some of part of a function.  Internally, if the work to be done by the system is not trivial, it is divided into subsystems.  The system hierarchy is like an inverted tree where each node is a system, being more general and abstract on the top (root) and more concrete and specialized at the bottom (leafs).

We will visit some systems: the top most system of our tree (root) and one of the "leaf" nodes.

In the root node we can see a mechatronic module, with hardware and software functionalities (and thus, hardware and software inputs and outputs).  In the leaf one, pure software functionality and software inputs and outputs.

h2. The root system

Can be found at http://ucanca.gatatac.org/sub_systems/1-controlunit

{{iframe(http://ucanca.gatatac.org/sub_systems/1-controlunit,1024,400,yes)}}

We can see here these things:

* Left column:

** System properties.

** Connectors: J1, J2...

*** Numbered pins with assigned flows.

* Children view 

** Tree view: we can see all the children subtree as a tree-view control, we can expand/collapse nodes, etc...  This view also includes connectors and flows.

** First level children.

* Function sub systems (or how the functions are "mapped" on this subsystem, to be described later).

** We can see two behaviours satisfied by this system: CULowBeam and BCMParkLights.