EAST-ADL2 Overview @Advanced Software Architecture, 2010 Q2 Daniel Karlsson and Henrik Lönn Volvo Technology
Volvo Technology within the Volvo Group AB Volvo Business Areas BA Asia Mack Renault Volvo Construction Volvo Volvo Financial Incl. Buses Trucks Trucks Trucks Equipment Penta Aero Services Nissan Diesel Business Units Volvo 3P Volvo Powertrain Volvo Parts Volvo Technology Volvo Logistics Volvo Information Technology Volvo Technology 2010 Q2 2 EAST-ADL Overview
The Challenge Product Related Challenges - Functionality increase - Complexity increase - Increased Safety-criticality - Quality concerns Challenges Related to Development Process - Supplier-OEM relationship - Multiple sites & departments - Product families - Componentization - Separation of application from infrastructure - Safety Requirements, ISO 26262 Volvo Technology 2010 Q2 3 EAST-ADL Overview
The Response - EAST-ADL2 Architecture Description Language for Handling all engineering information required to sustain the evolution of vehicle electronics Volvo Technology 2010 Q2 4 EAST-ADL Overview
EAST-ADL2 A System Modeling Approach/Architectural Framework that • Is a template for how engineering information is organized and represented • Provides separation of concerns • Embrace the de-facto Feature content representation Abstract functional of automotive Vehicle Level architecture software – Analysis Level Functional architecture, AUTOSAR HW architecture, platform Design Level abstractions Implementation Level AUTOSAR Software Operational Level architecture Embedded system in produced vehicle (not in model) Volvo Technology 2010 Q2 5 EAST-ADL Overview
EAST-ADL2 Characteristics Extended compared to traditional ADL as it covers: EAST-ADL has been developed in: • Variability • EAST-EAA (ITEA 2000-2004) • Requirements • ATESST (EC FP6 2006-2008) • Safety • ATESST2 (EC FP7 2008-2010) • Behavior • TIMMO (ITEA 2007-2009) • Environment Modelling • Design methodology Alignment/integration: •(SysML, AADL) •AUTOSAR EAST-ADL2 •ISO26262 • Language Metamodel • UML2 Profile • Prototype Tool Volvo Technology 2010 Q2 6 EAST-ADL Overview
EAST-ADL Contributors 2000-2009 AUDI AG Valeo BMW AG Vector Carmeq GmbH Volvo Car Corporation CRF Volvo Technology AB Daimler AG ZF ETAS GmbH CEA-LIST Mecel AB INRIA Mentor Graphics LORIA OPEL GmbH Paderborn Univerisity-C-LAB PSA Technical University of Darmstadt Renault Technische Universität Berlin Robert Bosch GmbH The Royal Institute of Technology Siemens, Continental The University of Hull … Volvo Technology 2010 Q2 7 EAST-ADL Overview
Relation to other modeling languages and approaches? Why Not UML? • EAST-ADL2 is domain-specific but its UML2 profile gives access to UML2 tools. Why not SysML? • EAST-ADL takes up applicable SysML concepts but provides additional domain-specific support Why not Autosar? • EAST-ADL complements Autosar with respect to feature content, functional structure, safety properties, etc. Why not AADL • AADL represents the software implementation of a system while EAST-ADL2 starts on a more abstract level. Why not proprietary tools (Simulink, Statemate, Modelica, ASCET, …)? • EAST-ADL2 provides an information structure for the engineering data and integrates external tools Volvo Technology 2010 Q2 8 EAST-ADL Overview
EAST-ADL2 Evolution (Metamodel+Methodology+UML2 Profile) EAST ADL2.0 EEA AIL EAST ADL AUTOSAR UML2 Titus SYSML AADL ... UML2 SYSML AADL ... ATESST Partners Volvo Technology 2010 Q2 9 EAST-ADL Overview
Some Typical Engineering Scenarios The Vehicle Manufacturer decides what to include in the next product A Chassis engineer analyses a novel control algorithm Application expert defines detailed design Software engineer defines software architecture Packaging and allocation, Integration on ECU Early phase validation and verification Volvo Technology 2010 Q2 10 EAST-ADL Overview
Product Planners decide what to put in the next product Features represent the properties/functionality/traits (Brake, Wiper, CollisionWarning,... ) Vehicle Feature Model organize Vehicle Level Features for the vehicle Analysis Level Design Level Variability mechanism supports the Implementation Level definition of rules for inclusion in Operational Level different vehicles – Product Line Architecture Volvo Technology 2010 Q2 11 EAST-ADL Overview
A Chassis engineer analyses a novel control algorithm Control algorithm is defined as a Function connected to a plant Function in the Environment model EAST-ADL2 defines structure, legacy Vehicle Level tools can be used for behavior Analysis Level definition, simulation, etc. Design Level Implementation Level Realization details are omitted: Operational Level • Functional validation and verification can be done with respect to key aspects • Understanding of key aspects is possible Volvo Technology 2010 Q2 12 EAST-ADL Overview
An OEM and Supplier agree on specification A model of the supplied system provides a clear and effective information exchange Functions can be integrated and Vehicle Level validated before SW and HW exists Analysis Level Design Level Requirements are explicit and Implementation Level traceable to model elements Operational Level Interfaces and interaction clarified, avoiding common specification bugs Volvo Technology 2010 Q2 13 EAST-ADL Overview
Application expert defines detailed design A detailed functional architecture is defined, addressing e.g. • Hardware architecture • Allocation Vehicle Level • Fault tolerance Analysis Level • Implementation concerns Design Level • Sensor, actuator constraints Implementation Level • Interfaces to middleware Operational Level Focus on behavior and interaction of functions Abstract system architecture is defined and assessed Volvo Technology 2010 Q2 14 EAST-ADL Overview
Software engineer defines SW Architecture AUTOSAR Application SW Components are defined The set of SW components together realizes the Functional Architecture Vehicle Level Software organization and functional Analysis Level organization is decoupled and Design Level optimization of the SW architecture is Implementation Level possible. Operational Level Legacy, sourcing, allocation, performance, verification, responsibility, re-use, etc. influence which functions are realized by each SW component Volvo Technology 2010 Q2 15 EAST-ADL Overview
Outline •Example usage of EAST-ADL2 • Model Structure •Example Model •AUTOSAR Relation •Areas covered by EAST-ADL2 •Conclusion Volvo Technology 2010 Q2 16 EAST-ADL Overview
How is an EAST-ADL2 model structured? An EAST-ADL2 model is organized in several levels of abstraction, where the software and electronics based artifacts are modeled. Vehicle Level Analysis Level The abstraction levels are “views” on the model Design Level and a complete representation of the system. Implementation Level The contents on an abstraction level forms a Operational Level complete representation of the vehicle embedded system, with respect to the concerns of that abstraction level The levels are refined top-down starting at the vehicle level. Volvo Technology 2010 Q2 17 EAST-ADL Overview
How is an EAST-ADL2 model structured? • On vehicle level the features of the vehicle Vehicle Level • On analysis level the abstract functions Analysis Level Design Level • On design level the hardware topology , concrete functions and their allocation to Implementation Level nodes Operational Level • On Implementation level the software architecture as represented by AUTOSAR Realizes Realizes Realizes Volvo Technology 2010 Q2 18 EAST-ADL Overview
Vehicle Level • A Vehicle is characterized by a set of Features • Features are stakeholder requested functional or non- functional characteristics of a vehicle • A Feature describes that "what", but shall not fix the "how" SystemModel Vehicle • A Feature is specified by VehicleLevel Level VehicleFeatureModel requirements and use cases AnalysisLevel Analysis EnvironmentModel Level FunctionalAnalysisArchitecture • From a top-down architecture Design DesignLevel Level approach the features are the FunctionalDesignArchitecture HardwareDesignArchitecture configuration points to create ImplementationLevel Implementation Level AUTOSAR System a vehicle variant Operational Level Volvo Technology 2010 Q2 19 EAST-ADL Overview
Analysis Level Analysis Level is the abstract Functional description of the EE system • Realizes functionality based on the features and requirements • Captures abstract functional definition while avoiding SystemModel implementation details Vehicle VehicleLevel Level VehicleFeatureModel • Defines the system boundary AnalysisLevel Analysis EnvironmentModel • Environment model and Level FunctionalAnalysisArchitecture stakeholders define context Design DesignLevel Level FunctionalDesignArchitecture • Basis for safety analysis HardwareDesignArchitecture ImplementationLevel Implementation Level AUTOSAR System Operational Level Volvo Technology 2010 Q2 20 EAST-ADL Overview
Recommend
More recommend
