- Component is a parts required for the function of an electrical/electronic module (EEM). Examples include capacitors, resistors, ASICs, power-MOSFET, connectors, fasteners and mechatronic assemblies [ZVEI:RobVal].
A mechanical load is an externally applied and internally generated force that acts on a system or device. The application of loads results in stress and strain responses within the structures and materials of the system or device. Loads may be acoustic, fluid, mechanical, thermal, electrical, radiation or chemical in nature [ZVEI:RobVal].
A load distribution is a statistically described load level over time, cycles, temperature, voltage, climatic conditions, or other load types [ZVEI:RobVal].
- MathML Format
- From W3C: MathML is a low-level specification for mathematical and scientific content on the Web and beyond [MathML].
- Mission Profile
A mission profile describes all functional and environmental loads an application/component sustains during production, storage, shipping, assembly and operation.
A Mission Profile is a simplified representation of relevant conditions to which the component population will be exposed in all of their intended application throughout the full life cycle [ZVEI:RobVal].
- Mission Profile Framework (MPFW)
- Software framework to demonstrate the various use models of mission profile documents within the automotive supply and design network/chain.
- Mission Profile Format (MPFO)
- MPFO (Mission Profile Format) is an XML file format that can be used to exchange mission profile information, along with its associated meta data, between software tools from different vendors. The mission profile format also defines a work flow for transmitting the status of mission profile compliance between partners. Although developed in the automotive industry, MPFO is suitable for lossless exchange of mission profile information in any industry.
- Meta Model based Mission Profile Format (MPFO-MM)
- Meta model based formal format for application specific mission profile data.
- From Wikipedia: OpenMath is the name of a markup language for specifying the meaning of mathematical formulae. Among other things, it can be used to complement MathML, a standard which mainly focuses on the presentation of formulae, with information about their semantic meaning. OpenMath can be encoded in XML or in a binary format. See also [OpenMath].
- Operating Conditions
- Operating conditions are environmental parameters such as voltage bias, and other electrical parameters whose limits are defined in the data-sheet and within which the device is expected to operate reliably [ZVEI:RobVal].
- PMML Format
- From Wikipedia: The Predictive Model Markup Language (PMML) is an XML-based predictive model interchange format conceived by Dr. Robert Lee Grossman, … PMML provides a way for analytic applications to describe and exchange predictive models produced by data mining and machine learning algorithms. It supports common models such as logistic regression and feed-forward neural networks. See also [PMML].
- Reliability is the ability of a system or component to perform its required functions under stated conditions for a specified period of time [ZVEI:RobVal].
- REQ-IF Format
- From Wikipedia: RIF/ReqIF (Requirements Interchange Format) is an XML file format that can be used to exchange requirements, along with its associated meta data, between software tools from different vendors. The requirements exchange format also defines a work flow for transmitting the status of requirements between partners. Although developed in the automotive industry, ReqIF is suitable for lossless exchange of requirements in any industry. See also [REQ-IF].
- Robustness is insensitivity to noise (i.e. variation in operating environment, manufacture, distribution, etc., and all factors and stresses in the product life cycle) [ZVEI:RobVal].
- Robustness Validation
From Wikipedia: Robustness validation is a skills strategy with which the Robustness of a product to the loading conditions of a real application is proven and targeted statements about risks and reliability can be made. This strategy is particularly for use in the automotive industry however could be applied to any industry where high levels of reliability are required. See also [ZVEI:RobVal].
A Robustness Validation process demonstrates that a product performs its intended function(s) with sufficient margin under a defined Mission Profile for its specified lifetime. It requires specification of requirements based on a Mission Profile, FMEA to identify the potential risks associated with significant failure mechanisms, and testing to failure, “end-of-life” or acceptable degradation to determine Robustness Margins. The process is based on measuring and maximizing the difference between known application requirements and product capability within timing and economic constraints. It encompasses the activities of verification, legal validation, and producer risk margin validation [ZVEI:RobVal].
- Strict Content MathML Format
- From W3C: In MathML 3, a subset, or profile, of Content MathML is defined: Strict Content MathML. This uses a minimal, but sufficient, set of elements to represent the meaning of a mathematical expression in a uniform structure, while the full Content MathML grammar is backward compatible with MathML 2.0, and generally tries to strike a more pragmatic balance between verbosity and formality [Strict-Content-MathML]. See also the glossary entry for ‘MathML’.
- From Wikipedia: Traceability is the capability to trace something. In some cases, it is interpreted as the ability to verify the history, location, or application of an item by means of documented recorded identification. Other common definitions include the capability (and implementation) of keeping track of a given set or type of information to a given degree, or the ability to chronologically interrelate uniquely identifiable entities in a way that is verifiable. Traceability is applicable to measurement, supply chain, software development, health-care and security.
- XML based Mission Profile Format (MPFO-XML)
- XML based formal format for application specific mission profile data.
- The conclusion of the primary product development learning process supporting progress to the legal validation phase that the product has a high probability for meeting all known application requirements. There are no legal ramifications in verification. Learning may occur with test to failure for capability measurement beyond the established requirements and reliability demonstration [ZVEI:RobVal].
- The process of accumulating evidence to support a declaration with legal force that a system/module/component meets the known application requirements. Validation culminates in producing a formal declaration with legal weight that a product has been confirmed supported by objective evidence that the requirement for a specific intended use have been fulfilled. Tests have a defined success point that becomes the base measurement for the “Robust Validation” phase [ZVEI:RobVal].