User interface for semiconductor field application engineers
This topic is migrated from NXP's Excel based requirement list for medini, entries MEDNXP038, MEDNXP042, MEDNXP077, MEDNXP04281 and MEDNXP085. Background: Semiconductor components are developed as "Safety Elements out of Context" (SEooC) based on assumptions and one or several generic use cases. During the development phase the safety architect also performs generic safety analyses. They are released together with the product. Safety architects are expected to trained and experienced to use all necessary functionalities of medini. When semiconductor components are integrated by customers of the semiconductor supplier into their systems, then the generic analyses often have to be adapted to the individual use cases. This is not usually not done by the original safety architect. Often this is done by skilled field application engineers (FAEs). However, due to the wide topics covered by field application engineers, they are typically not as experienced in using medini as safety architects. Also, for adaptations of a generic analysis to a particular use case, it is not necessary to be familiar with all functionalities in medini (e.g. creating a component's model from scratch), but only a limited sub set (e.g. mission profiles, de/selection of safety mechanisms, setting the safety relevance of IP modules for certain system architectures and related safety goals, ...). Challenge: Medini shall offer a dedicated user interface for FAEs, which exposes the FAEs only to those functionalities necessary to configure a given generic safety analysis to match a given customer use case. All other, unnecessary functionalities shall not confuse the FAE specific user interface. This will allow to train FAEs efficiently and to ramp up the community of safety skilled FAEs.
