We are very proud to announce the following invited speakers:
MDA is often promoted to enable the portability of applications across platforms, but what of the development of platforms themselves? Today's consumer electronics products, such as TVs and mobile phones are based on complex integrated circuits to support their many functions. Cost and power consumption is crucial and semiconductor suppliers have to deliver substantial amounts of software to deliver the best performance from their hardware designs. This low-level software might be exposed to customers as device drivers for the operating system of their choice, and their development gives a different perspective on "platform specific models". Given the sensitivity of this software to changes in both customer requirements and their overall software architecture, and to changes in the underlying hardware, software development and maintenance effort becomes an increasing proportion of the overall engineering effort.
The presentation will describe the software development challenges faced by a semiconductor supplier and some of our experiments in meeting these challenges with MDA. It will reveal the technical limitations encountered and the greater problems of deploying unfamilar technology across large development teams. This guides us in the hunt for the "sweet spot", where MDA delivers benefits with an acceptable learning curve and project risk.
This talk reports on a recent dream/vision paper I published last year, whose title is a play on that of John Backus' famous Turing Award Lecture (and paper). I will propose that --- or rather ask whether --- programming can be made to be a lot closer to the way humans think about dynamics, and manage to get others (e.g., their children, their employees, etc.) to do what they have in mind. Technically, the question is whether we can liberate programming from its three main straightjackets: (1) having to produce a tangible artifact in some language; (2) having actually to produce two separate artifacts (the program and the requirements) and having then to pit one against the other; (3) having to program each piece/part/object of the system separately. Time permitting, the talk will get a little more technical, providing some modest evidence of feasibility of the dream, via LSCs and the play-in/play-out approach to scenario-based programming.
Model-Driving your System Development: When, for what purpose and at what cost do we need this approach?
In this presentation, we give an overview of the trend for applying a modeling paradigm to cope with the inherent complexity of the system engineering activities. Although often seen as an attractive approach, modeling comes at a cost (authoring effort, maintenance, reuse, etc.), and benefits are not earned without a careful application of this emerging technology. As a result, the industry has been slow in adopting modeling as a general solution to embedded sofware product development pains. We discuss some current successful application, expose some of the key issues related to this approach and review some recent results on the delicate balance between tooling and process in the pursue of maximizing return on investment.
Abstract: The automotive industry has encountered the complexity issue in the development of automotive control systems. Model-Based Development (MBD), proposed from the application side, has been expected to alleviate the issue and reports of observed benefits have been increasing. However, it seems that there are gaps between control system and embedded control software developers. Creating the bridge between both can be effective in creating an automotive control system development environment. The basic concepts of Automotive MBD will be introduced in this presentation.