Model-based System Development

Model-based System Development

 

This white paper guides Automotive Industry systems engineers and software engineers to use IBM® Rational® Statemate® for the following:

Besides the methodological aspect of the integrated process, “best practice” advice is given which enables a seamless transition “from concept to code.”

It should be noted that the purpose of this document is to supplement the existing training courses offered. It is assumed that the reader has a basic knowledge of the Rational Statemate and an understanding of the basic elements and syntax of the Rational Statemate “language.” The following are the major topics covered in the ratepayer:

The Model-based System Development section describes the model-based system development process as it is typically applied in the Automotive Industry. It also defines where in this process the tools Rational Statemate and MicroC should be used. It also addresses the car manufacturer/supplier trade-off from the process and tools point of view.
The Requirements Capture and System Design with Rational Statemate section describes details of the functional analysis and modeling paradigm that should be adopted for requirements capture and systems design either by means of Rational Statemate or - to a lesser extend - by means of MicroC. Driven by the need to harmonize and standardize body electronic designs cross-platform, many car manufacturers follow a “feature-based approach” in their system designs. The role of Rational Statemate in this process is outlined in detail, especially with respect to a seamless transition to the S/W development using MicroC.
The Model Verification and Validation section gives an overview on the model verification and validation process supported by Rational Statemate and - to a lesser extend - by MicroC. Test strategies and test vector gene-ration are emphasized for the later use during the software design stage with MicroC.
Style Guidelines and Best Practices summarizes the common set of supported language elements. In addition, formal guidelines and “best practice” advice for the usage of the language of Rational Statemate are given. These “best practices” are based on many years of modeling experience in aerospace/defense and automotive projects and have proved to significantly enhance the readability of specifications developed using Rational Statemate.