Model Based Development

Why would you use model-based development?

• A model is a specification you can test. You can run a model, which means you can try it out, shake it down and test it.
• You can check that your model does what you want instead of relying on someone to ‘get it from a document. By helping you test your ideas early on, you inevitably test more of them. This always means your delivered system is better, more robust and fully thought through.
• A picture is a better way of describing complex things than text. A model is a pictorial version of the written specification. Even better than that, it is a tested picture, since you can run it.
• With a model of your system to be controlled, you can run it to destruction millions of times. A model of the thing you are controlling, known as a plant model, can be used to test your control algorithms. Your controller, controlling a plant model, can now be tested in every which way imaginable. It can be tested to destruction again and again at next to no cost at all.
• You can sell your models. Since you can generate code from the models for the end product you are effectively working on the product from day one.

Looking at the facts above, why would you not use model-based development?

Below shows you the model-based development process we use to deliver your projects. The tools that are used in the different phases to speed development, whilst still ensuring the quality of your system.

We recommend you model your requirements in SysML, to trace your needs throughout the design all the way to tests. This makes sure you get what you want. Likewise, you should model the behaviour in the best tool on the market, Simulink®. In Simulink, you can ensure the system under design is fully tested too. Finally, your software is validated using the automated testing environment VectorCAST. This gives you full confidence in the delivered product.

Model-based development process with the key tools