Requirements

Requirements, i.e., legal, functional, and non-functional requirements, as well as constraints, are the basis for item definition and security analysis.

Use the EnCo SOX requirements management module (RM) to create and manage your requirements.

Requirements can be classified as security-related after security goals and their associated ASILs have been defined (see HARA section below).

SOX Integrations

• Import requirements from other RM tools via interchange formats ReqIF (XML) or Excel.

• Additionally, SOX provides full synchronization of requirements with the following tools

  • IBM Doors (DNG)

  • PTC Windchill

  • Polarion

  • Jama

Please follow the link to a video demonstrating, inter alia, integration with Intland codebeamer: SOX-CB Synchronization.

An overview of available third-party interfaces is at Integrations.

System Design and Item Definition

With Eclipse Papyrus^TM, SOX provides a full functional system modeling tool based on UML 2.5 and SysML 1.6.

• Model your system architecture directly in SOX using standard UML/SysML diagrams.

• Import UML/SysML models via XMI 2.1 from other tools.

• In addition to XMI, SOX provides full interfaces to the following design tools:

  • MagicDraw (to be implemented)

  • Enterprise Architect (to be implemented).

Define the item and describe its functionality:

• Use a SysML requirement diagram to model requirements and their relations.

• Use a SOX concepts diagram (SCD) to model requirements and their relations to other model elements like system elements, functions, and malfunctions.

• Use a SOX concepts diagram (SCD) to represent the system elements of the item. You may add the item’s functions and their malfunctions, as well as requirements and safety goals.

• Use an internal block diagram (IBD) to model the boundary of the item, interactions between the parts of the item and with other systems in the context of the item.

HARA

Derive a HARA document from the item.

• analyze malfunctions, hazards, and situations

• derive ASILs

• define safety goals

This module has now migrated to the new web-based SOX interface.

Safety Concept

Based on your safety goals, derive functional and / or technical safety requirements (FSR/TSR) and model your functional and / or technical safety concept (FSC/TSC).

• Use the SOX requirements module for documentation and management.

• Use SOX concepts diagram or SysML requirement diagram to model structure and dependencies between safety goals and derived safety requirements (FSR/TSR).

• Allocate requirements (FSR/TSR) to system elements or (diagnosis) functions to represent your functional and / or technical safety concept (FSC/TSC).

Failure Mode and Effects Analysis (FMEA)

Derive FMEA from a system element by right-clicking on it in model explorer. As described in section [Link] model information is used to set up FMEA structure as well as function and failure net.

Failure Tree Analysis (FTA)

Malfunctions available in the model can be used in FTA. If a malfunction net is created in FMEA or system design, a complete failure tree can be added to an FTA document. A new FTA document can also be created on a malfunction being the root element of the failure tree.

Failure Modes, Effects and Diagnostic Analysis (FMEDA)

Use the SOX FMEDA module to obtain failure rates, failure modes and diagnostic capability and calculate your safety target-specific metrics per assembly and overall system. Take over hardware and system effects from the FMEA or map them by dragging and dropping.

Report Designer

Create templates for your reports and use them in your SOX projects. You can also create reports from scratch. SOX content can be added to reports easily by dragging and dropping.