Catalogs >
SIEMENS EDA >
Volcano? VSA

Volcano? VSA
2Pages

Catalog excerpts

Volcano™ VSA Vehicle Systems Architect Vehicle Systems Design D A T A S H E E T FEATURES AND BENEFITS: ■■ Software architecture design defines software components and compositions ■■ Hardware architecture design defines ECUs, networks, sensors, and actuators ■■ Scripting language support provides implementation of consistency checks or custom operations The Volcano Vehicle System Architect is part of the comprehensive Mentor Graphics vehicle systems design toolset, which provides a robust medium for an AUTOSAR-based vehicle system design flow, including E/E architectural design, application software development, virtual validation, and software test. Enabling AUTOSAR System Design for Development Teams The Volcano Vehicle Systems Architect (VSA) is a system design tool for AUTOSAR-based systems. It enables engineers to design automotive softwre and hardware architectures and to manage the relationships between the two.At the same time, it provides the user with required support to manage industrialscale projects with distributed development partners. A “Correct-by-Design” Development Methodology VSA enables the design of the software and hardware architecture of an AUTOSAR system, the mapping of the software components to electronic control units (ECUs), and the system signals exchanged between them. VSA supports the full AUTOSAR data model. It enables industrial-scale development projects with multiple users and iterative development through the use of integrated configuration management and merge technologies. By leveraging the EAST-ADL language and the results of the TIMMO research project, VSA enables users to capture requirements on a higher level of abstraction than even AUTOSAR supports. This provides the foundation for a contract-based development process where correctness can be guaranteed at design time. ■■ Consistency checks help ensure consistency of design data, both at the component and system levels ■■ Supports the full AUTOSAR meta model and its formats to provide true AUTOSAR compliance ■■ Captures system-level timing requirements by incorporating TIMMO elements within the AUTOSAR objects of the design ■■ User-configurable organization of design data maximizes reuse of existing objects ■■ Powerful merge features allows combined design data to be edited in various locations ■■ Generates AUTOSAR ECU extract and other AUTOSAR standard files ■■ Supports the ODX diagnostics exchange format ■■ Open, flexible Eclipse-based platform enables creation of design environment tailored to individual needs ■■ Integration with industry-standard configuration mangement systems

Open the catalog to page 1

Development Process Steps Software Architecture: Defining the software architecture is largely about defining software components in terms of their ports, interfaces, and connections between the software components. This can be done by software designers, architects, or functional Hardware Architecture (topology/ECUs): System architects define the structure of the system in terms of comunication networks and ECUs. In AUTOSAR terms, this is about defining the "core technology" of the Software Components Deployment: Software components must be assigned to ECUs. This can be done by system...

Open the catalog to page 2