model based development

Model Based Development

23.10.2014Rajdeep Rajput

Seminar Automotive Software Engineering

Evolution of MBD1

What is MBD?2

Traditional vs MBD Design Process3

Steps involved in MBD Design Process4

Tools used in MBD5

Need of MBD6

Limitations of MBD7

References8IAE_SASE/Seminar/Model Based Development/Rajdeep Rajput2

Outline : Model Based Development

Decade Year Simulation Implementation

197x Analog computing Transistor amplifier

198xCustom simulation program Fortran

Mixed signal components

199xStandard simulation platform

Microcontrollers Assembly code

200xMatlab Simulink control schematic

Fast DSP and RISC C code

201xSimulink Model Embedded C code for embedded target

Note : DSP (Digital Signal Processor) are special purpose microprocessors for signal processing i.e. they have extract

instructions, addressing modes etc. RISC (Reduced Instruction Set Computing) are microprocessors for usually generic usage. There are a lot of famous

microprocessor families that fall under this e.g. ARM, MIPS etc.

IAE_SASE/Seminar/Model Based Development/Rajdeep Rajput3

1. Evolution of MBD

Wikipedia

It is a mathematical and visual method of addressingproblems associated with designing complex control, signalprocessing and communication systems.

It is a methodology applied in designing embeddedsoftware.

Mathworks

It is a process that enables faster, more cost-effectivedevelopment of dynamic systems, including controlsystems, signal processing, and communications systems.

A system model is at the center of the developmentprocess, from requirements development, through design,implementation, and testing.

The model is an executable specification that youcontinually refine throughout the development process.


2. What is MBD?

Physical Setup

Subsystem Model

Motor Simplified Model


2. What is MBD?

Requirements

Phase

Design Phase

Realization

Phase

Testing Phase

Integration, Test & Certification

Research & Requirements

Software

Requirements

Design

Realization

Testing

Hardware

Requirements

Design

Realization

Testing

Mechanical

Requirements

Design

Realization

Testing

Traditional Design Process Traditional Design of Multi-domain Systems


3. Traditional vs MBD Design Process

Automate regression testing

Detect design errors

Parameter tuning

Support certification and standards

Generate efficient code

Explore and optimize implementation tradeoffs

Model multi-domain systems

Explore and optimize system behavior in floating point and fixed

point

Collaborate across teams and continents

INTEGRATION

IMPLEMENTATION

DESIGN

TE

ST

& V

ER

IFIC

AT

ION

RESEARCH REQUIREMENTS

ARM

C, C++

Environment Models

Physical Components

Algorithms

MBD Design Process



A. Defining the systemHeating System of a House

Heater SubsystemThermostat Subsystem

Thermodynamic model subsystem


4. Steps involved in MBD Design Process

B. Identifying System Components

Three types of components define a system:

Parameters : System values that remain constant unless you changethem (e.g. mass of vehicle, damping coefficient of spring)

States : Variables in the system that change over time (e.g. Engineis On, Running or Off)

Signals : Input and output values that change dynamically during asimulation (e.g. fuel injection w.r.t. acceleration)



C. Modelling System with Equations and Building Blocks

Your model may include:

Algebraic equations Logical equations Differential equations, for continuous systems Difference equations, for discrete systems



D. Simulation and Validation of Model



E. Code Generation, Building and Linking



SimulinkState flowMatlab GUIDEFixed Point ConversionSimulink V&VRTW Embedded CoderTesting Tools


5. Tools used in MBD

Efficient & cost effective way to develop controls, signalprocessing, image processing, communication & otherembedded system.

Reduced development time and improved product quality

Code generation is fast, systematic, structured, reproducible,portable, optimizable

Faster to model and then auto-code as compared to hand-written C

Lower residual failure rate as compared to the worlds best Cprogrammers


6. Need of MBD

Right level of abstraction

Heavy system requirements for small size code

Learning curve problem

Coding provides more flexibility as compared to modelling

Ability to integrate various systems and extensions asdevelopment takes place

Cost of MBD tools


7. Limitations of MBD

1. MathWorks and its product description at http://www.mathworks.com

2. Devesh Bhatt, Brendan Hall, Samar Dajani-Brown, Steve Hickman, Michael Paulitsch, Model-based development and the implications to design assurance and certification, Digital Avionics Systems Conference, 2005. DASC 2005. The 24th (Volume:2 )

3. Anders Frederiksen, Analog Devices, Inc, Model-Based Design of Advanced Motor Control Systems, Technical Article MS-2577

4. Jerry Krasner, Model-Based Design and Beyond: Solutions for Todays Embedded Systems Requirements, CSI Communications, ISSN 0970 647X/Volume No. 34/Issue No. 5/August 2010

5. Ruben Picek, Vjeran Strahonja, Model Driven Development Future or Failure of Software Development?, http://old.foi.hr

6. N Md Jubair Basha, Salman Abdul Moiz & Mohammed Rizwanullah, Model Based Software Development: Issues & Challenges, IJCSI, ISSN (PRINT) : 22315292, Vol.- II, Issue-1, 2

7. Jrg Holtmann, Jan Meyer, Matthias Meyer, A Seamless Model-Based Development Process for Automotive Systems, http://www.cs.uni-paderborn.de


8. References

Any questions???


Thank You!!!!!!


model based development

Documents

mbd design process4tools

model based development23

developmentrajdeep rajput73

developmentrajdeep rajput52

developmentrajdeep rajput62

developmentrajdeep rajput104

developmentrajdeep rajput83

developmentrajdeep rajput93