Refine Your Search

Search Results

Viewing 1 to 4 of 4
Technical Paper

Control Software Interface for Managing System Requirements

2004-03-08
2004-01-0363
Not all software tools are created equal and not all software tools are created to perform the same tasks. Therefore, different software tools are used to perform different tasks. However, being able to share the information between the different software tools, without having to manually re-enter (duplicate) any of the information, can save a lot of time and improve the quality of the product. The control software interface presented in this paper, allows system engineers to exchange data between software tools in an efficient manner which maximizes each tools capabilities and ultimately reduces development time and improves the quality of the product.
Technical Paper

Model-Driven Product Line Software Development Process

2005-04-11
2005-01-1288
The past 10 years have created such buzzwords as “model-based development” and “auto-code generation”. Conveniently absent from the tool literature on model-based development are the equally, or more important concepts of Software Architecture and Process. When developing product line software, the process and architecture form a critical foundation to base reusable products and components. The development process can no longer be viewed as “model-based”, but rather as “model-driven”, due to the reliance on the models as the source artifact as opposed to the creators of the source artifacts. A model-driven product line software development process allows capturing of behavior, for commonality across different products, and having a different implementation for a specific product release.
Technical Paper

Algorithms and Software for Development of Modular Vehicle Architectures

2002-03-04
2002-01-0140
Modular systems provide the ability to achieve product variety through the combination and standardization of components. The trend within the automotive industry is towards modular systems. The automotive manufacturers separate the vehicle into modular systems (chunks), which may be built and tested off line before assembled for vehicle installation. In this paper, software that utilizes a new clustering algorithm for development of integrated and modular vehicle architectures is presented. The algorithm and software tool presented in this paper allows the system designer to automate and optimize the vehicle system development process. A vehicle system model that identifies all the functional (data, and control) interfaces between vehicle system functions is the input to the software tool. The software tool is capable of analyzing this input data and determining the vehicle system architecture by optimally grouping (integrating) functions into physical modules.
Technical Paper

Development of Modular Electrical, Electronic, and Software System Architectures for Multiple Vehicle Platforms

2003-03-03
2003-01-0139
Rising costs continue to be a problem within the automotive industry. One way to address these rising costs is through modularity. Modular systems provide the ability to achieve product variety through the combination and standardization of components. Modular design approaches used in development of vehicle electrical, electronic, and software (EES) systems allow sharing of architectures/modules between different product lines (vehicles). This modular design approach may provide economies of scale, reduced development time, reduced order lead-time, easier product diagnostics, maintenance and repair. Other benefits of this design approach include development of a variety of EES systems through component swapping and component sharing. In this paper, new optimization algorithms and software tools are presented that allow vehicle EES system design engineers to develop modular architectures/modules that can be shared across vehicle platforms (for OEMs) and across OEMs (for suppliers).
X