Program

Monday, Nov. 26th 2018

8:30 Registration
9:00 Welcome speech and Introduction to the MESCONF
9:15 Dr. Li Xiang: Current level of model-driven development of embedded systems in China
9:30 Tim Weilkiens: The New Engineering Game – Strategies for the Industrial Internet
10:30 Coffee Break
11:00 Walter van der Heiden: Still Programming or already Modeling?
12:00 Lunch
13:30 Alexander Huwaldt: Model-driven development of embedded systems using the example of a control unit for mobile machines
14:30 Coffee Break
15:00 Alexander Schneider: Development Processes with UML for Embedded Systems – 10 Years of Modeling at a tier1, an honest review
16:00 Coffee Break
16:15 Panel discussion, Future of model-driven development of embedded systems in China
17:00 Closing note

Tim WeilkiensTim Weilkiens: The New Engineering Game – Strategies for the Industrial Internet

The markets are getting more and more complex and dynamic. They have passed a tipping point, and companies face new rules of the game. The Internet of Things or Industry 4.0 are concrete examples of the change. The development of systems requires a new kind of engineering and thinking. Companies that are capable of adapting themselves to the frequent and partially disruptive changes in the complex and dynamic markets will be successful in the future.

The talk shows up the new playfield and provides strategies to be a successful player. It is based on the book “The New Engineering Game” published by MBSE4U.


Walter van der HeidenWalter van der Heiden: Still Programming or already Modeling?

Programming is easy. One thinks. It is not (or actually not any more), because for some time the complexity of projects is increasing tremendously. Is not that all easy.

Modeling is difficult. One thinks. But it is not as difficult as programming. For quite some time there are UML tools that assist the developers in their work.

So what would be the perfect time to do the paradigm shift from coding to modeling? That would be: Now! because it never fits, if a new development method should be introduced: Everyday life ensures that there is always something more urgent and there will be always more important issues. Or as the farmer says, “We don’t have time to fix the fence, we are busy catching chickens”. If the farmer is smart, He lets a few chickens fly so that he can rest later. If you are also smart, invest now in the future of software development! This presentation shows you how.

Benefits and special features: The participants will learn how UML has progressed over the last 10 years, what can you do with it and how software development can become faster and safer.


Alexander Huwaldt: Model-driven development of embedded systems using the example of a control unit for mobile machines

The case study of a concrete class library discusses important aspects of the design of portable classes. Using the example of a simple class, the mentioned criteria for their portability are applied and demonstratively implemented on an 8-bit AVR and a 32-bit ARM controller. The development environment uses a UML tool.

Benefits and special features: With C ++, UML and object orientation portability is by no means automatic. The listener is given a vivid and step-by-step explanation of how portability can be realized in a specific case.


Alexander Schneider: Development process with the UML for embedded Systems – 10 years of modeling at a Tier1, an honest statement

Alexander Schneider

Many developers, especially in the area of embedded Systems say, that the effort of the usage of UML is too big, while the benefit is too low. On the other hand, the Systems become more and more complex. One has to face this complexity somehow.

We started to fully use the UML more than 10 years ago in a project for an embedded System with security requirements. Also, the successor projects were developed with help of UML, while the methods were more and more refined. The reasons for the usage of the UML are volatile. In the following, I will name some reasons.

The requirements for the development lifecycle itself, to make the Systems reproducible and traceable, are getting higher and higher. One has the duty to document the Systems understandable and consistent and to provide evidence that everything was done to develop the Systems in a way that they are doing the right things without errors.

Standards for processes (CMMI, SPICE), functional safety and others require clear and hard requirements for the development process. The processing of requirements with Excel, the definition of architectures with PowerPoint or Visio, the decoupled programming in Visual Studio or other IDEs, the documentation in Word, etc., is by far not enough to fulfill the hard requirements of standards, respectively it will be very hard to maintain the data and to keep it consistent. The UML provides big support to fulfill these requirements.

In my talk, I will show how we used the UML in a real project in order to satisfy these requirements. I will address some advantages compared to the traditional development and clean up with some prejudices. I will show that the usage of the UML in the daily work is worth and the effort is not too big. The UML supports in many ways and finally reduces the effort, increases the understandability and potentially prevents errors.