Requirements from WT2. 1: Identifications of needs 10
Requirements from WT2. 1: Identifications of needs A2#11: A formalized meta-model of the architecture description language shall be developed. (including structural elements, behavioural description means, models of computations, and transformation rules to prototype tools and Simulink.) DOW#0112: The Simulink import-export ( FAA, FDA ) shall be modelled in MAW-Simulink plugin.
Requirements from WT2. 1: Identifications of needs VTEC#UC006: A model of the validator with timing, dependability and cost annotations as well as design space, variability and take rate annotations is defined and exported to EAXML. An optimization tool computes the optimal design for the defined product line. The resulting optimized model is recorded in the model (design space variability removed) and exported in the EAXML file. UOH#0002: The EAST-ADL error model should fully support automatic optimisation, e.g. through rules that specify a 1:1 mapping from nominal to error models. UOH#0005: To support multi-objective optimisation, there must be a standardised way of passing design candidates to analysis tools/plugins and receiving results in a given format.
Requirements from WT2. 1: Identifications of needs The AUTOSAR gateway is mentioned in the following requirement: DOW#0111: The SWC Synthesis ( FDA-IL ) shall be modeled in MAW-AR Gateway plugin [4].
Requirements from WT2. 1: Identifications of needs Modelica exchange is mentioned in e.g.: CON#0009: Annotate SysML/Modelica models with EAST-ADL stereotypes. On base of a defined mapping between SysML and EAST-ADL, the SysML model of the profile and mode selection logic shall be annotated with EAST-ADL stereotypes. Structural as well as behavioral elements shall be annotated with EAST-ADL stereotypes CON#0012: EAST-ADL supports the definition of timing of constraints by the inclusion of the TADL language. A verification of the TADL constraints shall be possible. It is an option to verify TADL constraints either by the use of timing analysis techniques as provided by languages as XXXXX or AADL or model simulation techniques as provided by Modelica. Within the scope of the project, it has to be evaluated, if the verification of timing constraints on base of these techniques is possible and samples shall be given. CON#0014: VV Case Development, including fault injection and verification of model constraints in a Modelica simulation environment. CON#0021: Virtual integration is an important use case during development within the ID4EV project. It is obvious that the physical demonstrator will not be available for a long time and the SW modules must be integrated in a virtual environment. The Modelica simulation environment is very well suited for integration C-code into the simulation environment.
Requirements from WT2. 1: Identifications of needs MODELISAR FMU import is not explicitly mentioned in the requirements, although it relates to behavioural simulation in general. DOW#0012 O2-2: Behavioural Simulation of EAST-ADL2 models 4SG#0003: Perform behavioural Simulation of EAST-ADL2 models according to performance evaluation standards 4SG#0004: Perform behavioural Simulation of EAST-ADL2 models according to standards covering communication with infrastructures 4SG#0019: The project shall enable to perform behavioural simulation according to ISO 8715: Electric road vehicles - Road operating characteristics There are more similar requirements on behaviour simulations, see e.g. 4SG#0020, 4SG#0021, 4SG#0022, 4SG#0023, 4SG#0024, 4SG#0025, 4SG#0026 3 References [1] xxx.xxxxxx.xxx, accessed 2011-05-26 [2] xxx.xxxxx.xx, accessed 2011-05-26 [3] xxx.xxxxx.xxx, accessed 2011-05-26 [4] MAENAD: Deliverable D2.1.1, draft version 0.5 [5] xxx.xxx-xxxxxxxx.xxx, accessed 2013-03-19 [6] MAENAD: Deliverable D3.1.1
Requirements from WT2. 1: Identification of needs 38
Requirements from WT2. 1: Identifications of needs 16 3 References 17 1 Introduction
Requirements from WT2. 1: Identifications of needs The Timing Analysis plugin is mentioned in the following requirement: DOW#0110: The Timing analysis ( DL ) shall be modelled in MAW-Timing plugin [4].
Requirements from WT2. 1: Identifications of needs EAXML is mentioned in VTEC#UC001 through VTEC#UC008 [4], which describe scenarios where
