If the RM HierarchyView displays data from an RM document and the editor is switched for example to an FMEA document, the view is cleared. This should not happen, as the contents of the view is supposed to be used for D&D purposes.
SOX release notes. (Click on the relevant note to get more information)
FTA documents can be copied by drag & drop between different projects.
Implementation of a statistic dialog that provides you with information about the changed, added or deleted objects.
The completely new module Test supports specifying and managing Test Specifications and Test Runs and their linkage to requirements. SOX enables full traceability among the whole engineering process, from requirements to tests.
The module HARA has been completely reworked with improved structure, presentation, and usability. The HARA module now delivers additional efficiency gains by supporting reuse of events (e.g. effects, hazards) via catalogs. Included permutation algorithms improve the general handling of rated scenarios and additionally provide automatic restrictions to provide a manageable overview of all rated scenarios. Adaptable standard catalogs for the automotive driving scenarios are now delivered as default as well.
Users can move back in project history and view any previous version of a project. Previous version can be fully loaded into the workspace to inspect all details using all available SOX views and editors. Versions can be created manually on requested specific times.
Integration of the latest version of Papyrus UML/ SysML tool (Papyrus Oxygen 3.1), providing various usability and stability improvements.
Enhanced analysis of differences between FMEA documents and System Design as well as between FMEA and FMEDA documents. Automated adaptation of detected differences on demand.
Enhanced and customizable support for setting the status of work products, such as requirements, component definitions or hazard definitions. Easy customization of states and permitted state transitions using state machine graphs. Specific states of elements can now also be assigned to assigned roles (SOX Users).
Trace graph providing a visual representation of the SOX Trace View, allowing users visual inspection of all types of links between elements within the same or different documents.
Possibility to run multiple repositories on the same SOX server using different
ports.
Note: Server must be updated due to migration procedures. The instructions are
delivered in
a separate documentation for MySQL Servers available in the
EnCo Download management center.
Significant performance improvements for server-based repositories. Significant performance improvements for FMEA document editing. Advanced data integrity checks via checksum calculations for project import/export and catalogues.
Every existing SOX module has been under steady development. Smaller and greater
application improvements are made to improve
the general efficiency of SOX.
For instance, copy requirements across different modules or manage the order
of failure mode
splits.
SOX starts with a Welcome Screen that allows to jump directly to the most important starting and administration tasks, tutorials, user help and information.
Search dialog on FMEA Editor, FailureNetView and FunctionNetView triggers on "Ctrl-f" provide text viewer search functionality.
It is now possible to export FMEA and FTA in svg format. Please see user help for details and limitations.
You are now able to drag a module from BOM and add this to the FMEA document. It will be used there as a system element with the model of the system design (UML).
Semiautomatic support for synchronization of FMEDA system effects and hardware failures with FMEA.
The FMEDA now contains a filter that filters for components with FMC < 90%.
A new filter tool in FMEDA supports the identification of
discrepancies in FMEDA safety goal activation and associations
of safety goals to system effects on UML level.
Information is displayed in the SR cell of the FMEDA. A
tooltip indicates the reason for the info
mark. A preference on the FMEDA preference page can be used to
configure the display.
Add a general import facility to import system elements, functions (diagnosis) and malfunctions to FMEA and FMEDA. See user help for details.
SOX starts with a Welcome Screen that allows to jump directly to the most important starting and administration tasks, tutorials, user help and information.
The completely new module Test supports specifying and managing Test Specifications and Test Runs and their linkage to requirements. SOX enables full traceability among the whole engineering process, from requirements to tests.
The module HARA has been completely reworked with improved structure, presentation, and usability. The HARA module now brings additional efficiency gains by supporting reuse of scenarios via catalogs.
Integration of the latest version of Papyrus UML/ SysML tool (Papyrus Oxygen 3.1), providing various usability and stability improvements.
Enhanced analysis of differences between FMEA documents and System Design and between FMEA and FMEDA documents. Automated adaptation of detected differences on demand.
Enhanced and customizable support for setting the status of work products, such as requirements, component definitions or hazard definitions. Easy customization of states and permitted state transitions using state machine graphs.
Customize and apply activity-specific reduced user interfaces based on user roles. Users then see only those parts of the SOX user interface relevant for them.
Users can move back in project history and view any previous version of a project. Previous version can be fully loaded into the workspace to inspect all details using all available SOX views and editors.
Trace graph providing a visual representation of the SOX Trace View, allowing users visual inspection of all types of links between elements within the same or different documents.
Possibility to run multiple repositories on the same SOX server using different ports.
Significant performance improvements for server-based repositories. Significant performance improvements for FMEA document editing. Advanced data integrity checks via checksum calculations for project import/export and catalogues.
For instance, copy requirements across different modules or manage the order of failure mode splits.
Search dialog on FMEA Editor, FailureNetView and FunctionNetView triggers on "Ctrl-f" provide text viewer search functionality.
It is now possible to export FMEA and FTA in svg format. Please see user help for details and limitations.
You are now able to drag a module from BOM and add this to the FMEA document. It will be used there as a system element with the model of the system design (UML).
Semiautomatic support for synchronization of FMEDA system effects and hardware failures with FMEA.
The FMEDA now contains a filter that filters for components with FMC < 90%.
A new filter tool in FMEDA supports the identification of discrepancies in FMEDA safety goal activation and associations of safety goals to system effects on UML level.
Information is displayed in the SR cell of the FMEDA. A tooltip indicates the reason for the info mark. A preference on the FMEDA preference page can be used to configure the display.
Add a general import facility to import system elements, functions (diagnosis) and malfunctions to FMEA and FMEDA. See user help for details.
Context menus are inconsistent in order and sometimes change order.
If the RM HierarchyView displays data from an RM document and the editor is switched for example to an FMEA document, the view is cleared. This should not happen, as the contents of the view is supposed to be used for D&D purposes.
If the index of a hierachy number is higher than 9 the order of the requirements is wrong (e.g. 1.1.22).
You can now assign documents to requirements.
The "Show in object list" function on catalogs does not work for the specific catalogs. The context menu is provided but it's selection has no effect.
Provide a dedicated functions details page in catalogs that allows switching the function type and input of diagnosis attributes if applicable.
It is possible to finish the remote repository selection dialog without selecting a repository. The result is a program termination.
It is now possibility to change the server address or local repository location in case of a connection failure to the SOX repository.
The system is now able to properly recover from connection failures.
The performance of the application in some VPN scenarios has been increased by optimizing the load process of specific data.
Provide a facility to export FMEA graphs to image formats. This function is accessible from all FMEA graphs. See the user help for special limitations on svg export.
Linking of functions and malfunctions is now also supported for zoomed graphs.
Like other diagrams FMEA editor and failure net\function net view supports zooming by mouse wheel. In order to zoom. press "Ctrl" and move the mouse wheel.
In case of malfunction assignment to system effect or hardware effect the table looses it's focus.
The background color of diagnosis can be colored according to their FMC. The ranges can be configured in the project properties.
If a fmea system element is dropped to the fmeda module view a new module is created which refers to the same element in the system design model (UML).
Factor of 0 does not lead to failure in FMEDA report anymore. Components with factor = 0 are not considered in the report.
You can now assign external documents to failure modes.
If a component has the FIT value 0, an info icon will be added and a tooltip is presented to the user.
The Temp Profile view is implemented in analogy to the Mission Profile view.
Components and failure modes in the BOM and FMEDA are decorated with a document icon if objects have respective assignments.
Description value in BOM template will now properly be imported to modules.