12:10 - 12:45  Paper 4

Overcome the Challenges Posed by Increased Design Complexity and Reduced Times in the Automotive Market Through Model-Driven Development

I-Logix

The spiralling growth of electronics in automobiles has reached a frantic pace.  This explosion of new electronic features that differentiate one car from another coupled with the need to distribute these features across one or more networks of embedded control units (ECUs) provides a real challenge.  In addition recall concerns, shrinking development cycles, emissions regulations, cost controls, safety concerns and the introduction of the latest in high tech gadgetry make automotive systems and software design a real and unique challenge.  Many automotive companies today are tackling these challenges of embedded systems development by adopting a standards based Model-Driven Development (MDD) approach for systems and software engineering. I-Logix has been working with our many customers in this area for over 15 years and has developed products and services tuned to the needs of the automotive engineer.  

Join us to see how, you can drive your way to success.  In this seminar we will use a Telematic Control Unit model to demonstrate:

       How, using a natural and intuitive design environment based on UML2.0^TM , it is easy to communicate design intend and to create reusable components.

       Integration of requirements modelling into the design to ensure it meets the requirements.

       Design collaboration enabling teams of any size to work together effectively even when they are geographically distributed.

       Design for Testability (DFT) to eliminate defects early while increasing quality in the end product.

       Full application generation reducing development times.

       Reverse engineering and code visualization to easily integrate existing source code into the modelling environment.

       Dynamic Model/Code Associativity enabling work at either the code or model level for maximum flexibility and to ensure that the design, implementation and documentation are always synchronized.

       Easily retarget the systems to any real-time operation system (RTOS) or even run with no operating system at all, providing true platform independence.