Features for reviewers and assessors

medini_1036867805

This topic is migrated from NXP's Excel based requirement list for medini, entries MEDNXP044, MEDNXP045, MEDNXP046 and MEDNXP082. Background: Safety analyses do not only have to be created, but also reviewed and assessed. There are many things an author of a safety analysis implicitly has in mind, which remain undocumented in the analysis itself. Examples will follow. Request: medini shall be enhanced by features which support the task to review and assess a safety analysis or the changes in a safety analysis. Examples will be given in the first reply to this topic. Additional review and assessment features on top of these examples shall be identified.

medini_1036867805

Original description and discussion MEDNXP044: Feature to create a tabular report for all values originally calculated or set by the tool automatically (e.g. a DC from a SM library) but then overwritten manually. Intention is to support checking during reviews and assessments. 2018-03-09 requires feature spec and  implementation: - should be doable based on SysML table editor report? 2018-04-20 If scaling is applied, this is visible today already (SysML table editor). Additional indication needed of manual value changes. 2018-07-20 For medini to understand this better, NXP must provide more clarity on what type of modifications shall be reported. Most likely we have to go through a complete review of a first medini FMEDA to be more precise what's needed here. Original description and discussion MEDNXP045: Generation of a textual "diff report" between two medini projects. This is currently only possible in GUI. 2018-03-09 will be added to product roadmap 2018-04-20 Intention understood (support review to find intentional/unintentional/accidental manual modifications of tool calculated values). Difficulty is to identify what to compare against. Needs ANSYS internal discussion. Original description and discussion MEDNXP046: Provide a text field for every manually entered value, both for values which are intended to be manually entered and for automatically calculated values which are overwritten manually. The text field intended to capture the reasoning behind the change. 2018-03-09 for worksheets, this can be provided through a profile attribute. Additional investigation required for VARIABLES 2018-04-20 Can be added to profile. 2018-10-05 See also MEDNXP044 Original description and discussion MEDNXP082: How to add Row ID in FMEDA worksheet. It brings easiest communication with assessors, with colleagues during reviews and later on improves the customer's interaction. 2019-08-14 Michael said that this is not possible as native feature, but he will propose a profiling with a Javascript code to have an ID per FMEDA's row. ID will be automatically updated when a new row is added in any place other than the end.