HistoryViewLinks to this page 2013 June 8 | 04:23 pm

Agenda

  1. Go through Actions List
  2. from the http://open-services.net/wiki/embedded-systems/ “Approach”: What are the “typical embedded development setups”?
    • To complement starting with what we have - e.g. BBW case, it might make sense looking for some overview of the current situation to if possible ensure we are making a somewhat informed decision of what scenarios to focus on - or what “weight” they should have. Approximate no of developers in the embedded domain, of those - approximate no of users of different tools. Have not recently looked for what market intelligence is available, but imagine there is some. In any case, I will try getting the corresponding info for Ericsson. And along with a dev setup, it would obviously be great to have some info - or even better - contact with experience of working in that setup, to interview for major obstacles and places for improvement.
  3. go through the IntegrationScenario SimulinkToCode from the Brake-by-wire example

Minutes

  1. from the http://open-services.net/wiki/embedded-systems/ “Approach”: What are the “typical embedded development setups”?
    • Suggestion to step back (or in parallel with working with scenarios) to see how does the ES setups typically look like.
    • Need to make sure we are addressing the right cases, while/before we jump into specific cases.
    • example questions: How many are using Visio? MBD? How many are using code generation from models?
    • Rainer: this is a long process. The ES user group is very broad, so it will be a challenge to do such a survey.
    • Nils: planning to do a “survey” anyway - in the context of Ericsson.
    • conclusion: Nils will check with Ericsson what they will find of interest to deal with in this group.
    • Action: Frederic to setup a wiki page for common themes/patterns that we identify from our different use cases & scenarios.
  2. go through the IntegrationScenario SimulinkToCode from the Brake-by-wire example
    • Initial discussions of the application in general, and the scenario presented was started.
    • To be continued…
    • Action: Jad checks if it is systemDesk or Articstudio that is used to model the architecture.
    • Action: Frederic identifies BBW scenarios of relevance in MBAT project. Frederic checks how correct & relevant the current scenario is for Volvo. Ask Mbat partners.
    • Action: Jad ask if step from EAST-ADL to Simulink is automated, or purely manual? Irrespective, define a scenario (placeholder) to define such a need.

Attendees

Nils Kronqvist, Rainer Ersch, Jad El-khoury, Frederic Loiret

Category:Meetings


Categories