Writing /www/htdocs/mrtc/projects/decisive/data/cache/1/1d8179d7990cfe32ecd65a1b2460eeec.i failed
Unable to save cache file. Hint: disk full; file permissions; safe_mode setting.
Writing /www/htdocs/mrtc/projects/decisive/data/cache/1/1d8179d7990cfe32ecd65a1b2460eeec.i failed
Unable to save cache file. Hint: disk full; file permissions; safe_mode setting.
Writing /www/htdocs/mrtc/projects/decisive/data/cache/1/1d8179d7990cfe32ecd65a1b2460eeec.xhtml failed

WP1

Work package number 1 Start date or starting event: M1
Work package title Requirements
Participant number 1 6 3 4 13 12 14
Participant short name PHILIPS PAJ CISC NXP-A UoO UEF VTT
Person-months per participant 12 8 4 5 20 11 6
Participant number 9 11 10 8 16 15 17
Participant short name MEGA CON NSN KNR CEA Atego EADS
Person-months per participant 8 6 6 8 6 11 6
Participant number 20 42 22 23 26 25 33
Participant short name CAU ETAS NXP-D CRF RTU LDZ MU
Person-months per participant 3 10 5 28 2 2 5
Participant number 32 31 35 36 37
Participant short name ISYS IKER MDH Volvo ARC
Person-months per participant 5 14 3 8 2

Objectives

Purpose of WP1 is the definition of the requirements for tools and methodologies to be developed by the technology packages. Starting from the evaluation of the current state-of-the-art and state-of-practice approaches related to evolutionary development in the model-based engineering of embedded systems, requirements for tools and methodologies will be defined in order to provide: non-intrusive analysis and monitoring techniques to systematically collect information during the creation and evolution; decision support for the synthesis of system architectures; model management and visualisation, to automate the management of models and improve comprehension during the system evolution. Safety and certification requirements will be also identified. Reusability and cross-domain applicability of the solution will also be considered from the very beginning of the project. WP1 is also responsible for the validation of the methodologies after the 1st phase and for the definition of test methodologies that will be applied during validation phase and the preliminary definition of candidate validation cases and scenarios.

Description of work (possibly broken down into tasks) and role of partners

T1.1 Longevity Requirements and Validation:

Lead: Philips

Contributors: Philips, EADS, NSN, UoO, UEF

This task determines the requirements originating from the longevity validators. These relate to evolution of systems in the field, upgrades of these. It addresses methodology and tools to use system diagnosis to provide improved system designs.

Activities:

  • Initial requirements definition.
  • Validate the results of WP2-5 after 1st phase
  • Update of requirements after 1st phase.
T1.2 Tuning & Scaling Requirements and Validation:

Lead: ETAS

Contributors: ETAS, NXP-A, NXP-D, CISC, MU, ISYS, CRF

This task determines the requirements originating from the tuning & scaling validators. These relate to dealing with tuning and calibrating due to variations originating from the production process, and with user variation. The task deals with tooling and methodology supporting calibration and tuning, and run-time measurement of system properties. Specific care is on resource usage and energy efficiency.

Activities:

  • Initial requirements definition.
  • Validate the results of WP2-5 after 1st phase
  • Update of requirements after 1st phase.
T1.3 Reliability & Safety Requirements and Validation:

Lead: Atego

Contributors: PAJ, IKER, Atego, CISC, CEA, RTU, LDZ

This task determines the requirements originating from the reliability & safety validators. These originate from the need to incorporate reliability and safety standards and the run-time measurement of these properties. The task deals with tooling and methodology supporting design and run-time adherence to reliability and safety properties.

Activities:

  • Initial requirements definition.
  • Validate the results of WP2-5 after 1st phase
  • Update of requirements after 1st phase
T1.4 Industrial applicability, Validation and Test Methodology

Lead: IKER

Contributors: Philips, EADS, NSN, ETAS, NXP-A, NXP-D, CISC, PAJ, IKER, Atego, VTT, CAU, UoO, UEF

This task determines the requirements originating from the industrial applicability. These relate to compositionality, comprehensibility and the management of models. In addition the task prepares a test methodology to evaluate the validators developed in WP6.

Activities:

  • Initial requirements definition.
  • Validate the results of WP2-5 after 1st phase
  • Update of requirements after 1st phase
  • Provide a test methodology
Deliverables month of delivery responsible
D1.1 Requirements definition – each task a separate chapter M6
D1.2 Technical validation – each task a separate chapter M19
D1.3 Requirements update – each task a separate chapter M21
D1.4 Test methodology M30
 
/www/htdocs/mrtc/projects/decisive/data/pages/start/wps/wp1.txt · Last modified: 2011/08/22 22:35 by frank_l
 
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki