Component Architecture Safety Folder Clause Samples

Component Architecture Safety Folder. Under this folder, safety specification of components (DREAMS software Component entities) is given. It is important to note that this model contains only safety relevant software components (i.e., software components which are part of safety functions and have defined safety requirements components that have safety requirements). Non safety software components do not appear here. In the same way that a DREAMS system model can have multiple Component Architecture models, this folder can have multiple roots which correspond to different logical component models (see Figure 3.25). For each component, the following safety relevant properties (see Figure 3.26) may be defined:  RefComponent: Reference to the Component of the project.  Safety Standard and Safety Integrity Level: SIL level claimed for the Component.  RefCore: if the safety engineer wants to make sure that any deployments involving this component deploys the component into a given core, this field contains a reference to the core. For example: The safety engineer in Wind Turbine demonstrator (WP7) wants to ensure (for whatever reason) that for any Deployment (determined automatically using the design-space exploration (provided by WP4) or even manually defined) the Supervision(D) software Component in Figure 3.26 always is deployed into a Partition that is finally deployed into a given Core of a given Tile. The consistency rules will check that for any deployment the Partition is finally deployed into that core.  RefTile: if the safety engineer wants to make sure that any deployments involving this component deploys the component in a given tile, this field contains a reference to the tile. A similar example as above can be given here. However, in this case, the engineer wants to ensure that Component is deployed into a Partition that is deployed to the given Tile (without specifying a particular Core).  Isolated in One Partition (Boolean): True if the safety engineer wants to make sure (for whatever reason) that any deployments involving this component deploys the component “alone” in one partition (i.e., not shared with any other component). In other words, the Partition will contain only this Component.  NeedAccessListHWResources: List of hardware resources (watchdogs, clocks, tiles, etc.) to which the component need access rights. This is for example needed for a software Component that resets a Watchdog and is deployed into a Partition. In this case, the Partition has to be configured i...