User Tools

Site Tools


tutorials:vec:working_with_partial_systems

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
tutorials:vec:working_with_partial_systems [2019/05/20 11:22]
4soft.fehlmann
tutorials:vec:working_with_partial_systems [2019/05/21 12:43]
4soft.fehlmann
Line 9: Line 9:
 Sometimes there is the situation that concrete target components are unknown (or not yet defined) or different (topic specific) parts of a system schematic are developed independently as partial systems (e.g. vehicle infrastructure like power, ground or bus systems). In these cases more than one schematic plan exists like the "​blue"​ and the "​red"​ one, which are shown in the example in <imgref plan>. Sometimes there is the situation that concrete target components are unknown (or not yet defined) or different (topic specific) parts of a system schematic are developed independently as partial systems (e.g. vehicle infrastructure like power, ground or bus systems). In these cases more than one schematic plan exists like the "​blue"​ and the "​red"​ one, which are shown in the example in <imgref plan>.
  
-For theses situations the enumeration //​ComponentNodeType//​ contains the specific value "​OpenLink"​ (<imgref enum>​).\\+For theses situations the enumeration //​ComponentNodeType//​ contains the specific value "​OpenLink"​ (see <imgref enum>​).\\
 In the diagram in <imgref diagram> you can see the corresponding model to the "​blue"​ system schematic from the plan. Each component is represented by a //​ComponentNode//​ with it's slots and pins underneath which are represented by the //​ComponentConnector//​ and the //​ComponentPort//​ class. In addition to that the component M.31 is also shown in the diagram even though it is not existing on the blue plan.\\ In the diagram in <imgref diagram> you can see the corresponding model to the "​blue"​ system schematic from the plan. Each component is represented by a //​ComponentNode//​ with it's slots and pins underneath which are represented by the //​ComponentConnector//​ and the //​ComponentPort//​ class. In addition to that the component M.31 is also shown in the diagram even though it is not existing on the blue plan.\\