Two-tiered Architectural Design for Automotive Control Systems: An Experience Report
Kevin Steppe, Greg Bylenok, David Garlan, Bradley Schmerl, Kanat Abirov, and Nataliya Shevchenko
Automotive Software Workshop on Future Generation Software Architectures in the Automotive Domain, San Diego, CA, January 10-12, 2004. (Workshop proceedings)
|An attractive approach to architecture-based design is to structure the development process into two tiers. The top tier represents the abstract design (or architecture) of a system in terms of abstract components. The bottom tier refines that design by making specific implementation decisions, such as platform, middleware, and component implementations. While attractive in principle, there has been relatively little industrial-based experience to shed light on problems and solutions involved in such an approach. In this paper we describe our experience in developing tools to introduce a two-tiered model-based approach to the design of Ford Motor Company s automotive control systems, highlighting the principle challenges, and evaluating the effectiveness of our solutions for them.|
Last modified: 4/22/2004. For comments and problems, contact email@example.com.