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

WP2

Work package number 2 Start date or starting event: M1
Work package title Modelling and design frameworks
Participant number 27 28 39 5 3 4 13
Participant short name ALM OCE TUD DTU CISC NXP-A UoO
Person-months per participant 11 4 40 14 24 28 20
Participant number 12 9 11 10 16 15 18
Participant short name UEF MEGA CON NSN CEA Atego Valeo
Person-months per participant 44 7 5 36 30 37 24
Participant number 17 22 23 43 33 32 31
Participant short name EADS NXP-D CRF FBK MU ISYS IKER
Person-months per participant 10 23 12 45 30 7 30
Participant number 35 36 37
Participant short name MDH Volvo ARC
Person-months per participant 24 4 6

Objectives

The starting point for engineering systems is models. Usually, a wide-variety of models is needed to capture the essentials of systems. These models are not orthogonal. They provide partly overlapping viewpoints of the system. During system engineering one starts with high-level models that are then step-wise refined to system descriptions that can be realized in hardware and software.

This workpackage specifically addresses the issues of annotation of models and traceability as these are the means to keep models consistent and alive during the evolution of the systems.

This workpackage identifies the models needed to support the use-cases of the industrial partners in WP6. It is related to other work packages as follows:

  • Workpackage 6: It draws upon wp6 to derive the requirements for the models for longevity, tuning & scaling, and reliability & scaling.
  • Workpackage 3: WP3 associates simulation and real-time behaviour with the models. This allows us to extend the information on the system under development and help us make the proper engineering steps. Data mining techniques will help us sieve through the large amount of data generated.
  • Workpackage 4-5: WP4 uses the models of WP2 (and the associated WP3 data) and puts them into a framework that forms the input of WP5’s decision support system.

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

T2.1 Models for longevity:

Lead: EADS

Contributors: NXP-D, NSN, EADS, TUD

These models deal with how best to evolve new products out of the existing ones. To maintain products in the field, models will be developed to capture the status of product parts and correlate them to draw conclusions on the overall product status.

Activities:

  • Identify the models needed and do a benchmark.
  • Select the proper models.
  • Develop/Extend the syntax and semantics of the models if needed.
  • Show applicability of models in industrial use-cases.
T2.2 Tuning & Scaling Models:

Lead: OCE

Contributors: NXP-A, OCE, DTU, CISC, MU, ISYS, IKER, ALM

These models need to specify the high configurability of systems. This configurability is needed to meet the wide variety of customer, national, and international requirements. This type of models is also needed to deal with variations in the production process.

Activities:

  • Identify the models needed and do a benchmark.
  • Select the proper models.
  • Develop/Extend the syntax and semantics of the models if needed.
  • Show applicability of models in industrial use-cases.
T2.3 Reliability & Safety

Lead: FBK

Contributors: CEA, Atego, Valeo, CRF, FBK, LDZ, CG, UoO, UEF

These models are needed to specify reliable and safe systems. An important characteristic of these models is compositionality; i.e. showing that if the parts are reliable and safe the system built out of these parts is this too.

Activities:

  • Identify the models needed and do a benchmark.
  • Select the proper models.
  • Develop/Extend the syntax and semantics of the models if needed.
  • Show applicability of models in industrial use-cases.
Deliverables month of delivery responsible
D2.1 Model frameworks for 1st phase baseline – each task has a chapter M6
D2.2 Model frameworks for 1st phase – each task has a chapter M18
D2.3 Model frameworks for 2nd phase – each task has a chapter M33
 
/www/htdocs/mrtc/projects/decisive/data/pages/start/wps/wp2.txt · Last modified: 2011/08/22 22:36 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