A safety analysis can be started from an existing model by switching to a safety modelling view-point. There are two options: in case of standard UML, you need to switch to the Safety modeling context, as shown on the left in the following figure. This context contains a safety viewpoint in addition to the standard UML one. Some Papyrus customizations, such as Papyrus for Robotics, define a safety viewpoint within the domain specific modeling context, as shown on the right of the figure below. In this case, you only need to activate the viewpoint without switching the context (while you can deactivate other viewpoints, as shown in the figure, there is no need to do that, you can keep several viewpoints active).
The safety tool offers four different activities
The first action is typically to create a new safety requirements table. The command can be executed in the context of package. This step will first make sure that the required profiles (SafetyRequirements and SysML) will be applied to the user model. It then creates the model.
Once the table is created, it is possible to add new safety requirements to the table or tag existing SysML requirements as safety requirements
The first action is to start a new component analysis for an existing class or component. For convenience, it is also possible to execute this class on a package. In this case, a dialog pops up and shows available classes within that package.
For creating a new system fault diagram, right click on a class and then click "Create ESF Architecture Diagram". Before, you should assure that the architecture annotations are applied to the existing miodel.
The diagram offers a palette with the elements of ESF Architecture Concepts profile. However, it's not recommended to create new elements with the diagram, if you use a Papyrus customization such as the one for the robotics domain. The reason is that the new elements have the specific stereotype from the architecture concepts profile, but not those of the customization. In this case, the user should create new elements with the diagrams supported by the customization and then drag and drop these from the modelexplorer into the fault-analysis diagram when needed.
Note:When a SPart is added a dialog is opened for setting a type to SPart. By the dialog, there are two ways to define a type: the first is to create a new SBlock element; the second is to select a SBlock element present in the model.
Example of Recovery System with ESF Architecture Diagram: