| Viewpoint | Question Answered | Typical Stakeholder | Artefact |
|---|---|---|---|
| Functional | What functions does the system perform? | System engineer, OEM | Functional architecture diagram; function tree |
| Logical | How are functions grouped into logical components? | SW architect, Tier-1 | Component diagram; interface matrix |
| Physical / Hardware | Which ECUs, sensors, actuators exist? | HW engineer, wiring team | Network topology; ECU BOM |
| Communication | How do components exchange data? | Network engineer | Bus load table; signal database (DBC/ARXML) |
| Safety | How is functional safety achieved? | Safety engineer | HARA; safety concept; safety goal allocation |
| Power | How is power supplied and managed? | EE engineer | Power distribution diagram; load analysis |
Architecture Viewpoints
Architecture Frameworks
| Framework | Origin | Key Concept | Automotive Use |
|---|---|---|---|
| EAST-ADL | Automotive academia/AUTOSAR | Four abstraction levels: Feature→Functional→Logical→Technical | Tool-independent modelling of E/E architecture |
| AUTOSAR Classic | AUTOSAR consortium | Layered SW architecture: App / RTE / BSW / MCAL | ECU SW specification and generation |
| AUTOSAR Adaptive | AUTOSAR consortium | POSIX-based service-oriented: App / ARA middleware / OS | HPC compute nodes; SDV middleware |
| TOGAF | The Open Group | Enterprise architecture: Business/Data/Application/Technology | OEM enterprise IT + vehicle integration |
| ISO/IEC/IEEE 42010 | IEEE/ISO | Viewpoint + view + architectural concern + stakeholder | Formal architecture description meta-standard |
Automotive View Specification
YAMLarchitecture_views.yaml
# E/E Architecture view specification per ISO 42010
architecture_description:
system: "Next-Gen Zone Vehicle EEA"
version: "1.0"
views:
functional_view:
purpose: "Define all vehicle functions and their decomposition"
stakeholders: [system_engineer, safety_engineer, oem_product]
artefacts: [function_tree.xlsx, functional_architecture.eapx]
tool: "Enterprise Architect"
logical_view:
purpose: "Group functions into logical SW/HW components"
stakeholders: [sw_architect, tier1_supplier]
artefacts: [component_diagram.eapx, interface_matrix.xlsx]
physical_network_view:
purpose: "Define ECUs, buses, connectors, wiring"
stakeholders: [hw_engineer, wiring_team, ecu_supplier]
artefacts: [network_topology.pveision, ecu_bom.xlsx]
tool: "PREEvision"
safety_view:
purpose: "Allocate safety goals to architecture elements"
stakeholders: [safety_engineer, assessment_body]
artefacts: [safety_concept.pdf, fmea.xlsx, fault_tree.eapx]
communication_view:
purpose: "Specify all signals, PDUs, frames, services"
stakeholders: [network_engineer, sw_developer]
artefacts: [signal_db.dbc, fibex.xml, someip_sd.arxml]Summary
Architecture viewpoints are the practitioner's answer to the impossibility of capturing a complex vehicle E/E architecture in a single diagram. No single view shows everything: a network topology diagram hides the functional decomposition; a function tree hides the physical wiring; a safety concept hides the communication timing. The skill of an automotive system architect is knowing which view to use for which decision -- and ensuring that the views are consistent with each other (a function allocated to a logical component must also be allocated to the physical ECU that implements that component, and the signal interfaces must appear in the communication view). View consistency checking is where architecture tools like PREEvision and Enterprise Architect earn their keep.
🔬 Deep Dive — Core Concepts Expanded
This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.
Key principles to reinforce:
- Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
- Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
- Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.
🏭 How This Topic Appears in Production Projects
- Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
- Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
- Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.
⚠️ Common Mistakes and How to Avoid Them
- Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
- Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
- Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
- Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.
📊 Industry Note
Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.