architecture of infotainment systemsconti/presentations_2020/c02... · 2020. 10. 15. ·...
TRANSCRIPT
-
Architecture of Infotainment Systems
Course 2
continental-automotive.com VNI
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania2
9 October 2020
WE ARE HMI
Join via Teams
Join Microsoft Teams Meeting
Learn more about Teams | Meeting options
https://teams.microsoft.com/l/meetup-join/19%3ameeting_NTA0ZWRmOWEtODE3Ny00NTNmLThkZDEtNTg5NWY3OWFmZTMx%40thread.v2/0?context=%7b%22Tid%22%3a%228d4b558f-7b2e-40ba-ad1f-e04d79e6265a%22%2c%22Oid%22%3a%228cf67931-1cba-425e-87c8-96a7483559e2%22%7dhttps://aka.ms/JoinTeamsMeetinghttps://teams.microsoft.com/meetingOptions/?organizerId=8cf67931-1cba-425e-87c8-96a7483559e2&tenantId=8d4b558f-7b2e-40ba-ad1f-e04d79e6265a&threadId=19_meeting_NTA0ZWRmOWEtODE3Ny00NTNmLThkZDEtNTg5NWY3OWFmZTMx@thread.v2&messageId=0&language=en-US
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania3
9 October 2020
WE ARE HMI
1. Introduction
• Infotainment System – @ Continental
• Features
2. System Architecture
• Definitions
• Requirement analysis
• Decomposition
• Decisions
3. Case Study
Agenda
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania4
9 October 2020
WE ARE HMI
1. Introduction
• Infotainment System – @ Continental
• Features
2. System Architecture
• Definitions
• Requirement analysis
• Decomposition
• Decisions
3. Case Study
Agenda
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania5
9 October 2020
WE ARE HMI
What is an Infotainment System?
https://www.continental-automotive.com/en-gl/Passenger-Cars/Information-Management/Cockpit-HPC
https://www.continental-automotive.com/en-gl/Passenger-Cars/Information-Management/Cockpit-HPC
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania6
9 October 2020
WE ARE HMI
Infotainment System - @ Continental - #1
https://www.continental-automotive.com/en-gl/Passenger-Cars/Interior/Infotainment-Systems/Integrated-Interior-Platform
https://www.continental-automotive.com/en-gl/Passenger-Cars/Interior/Infotainment-Systems/Integrated-Interior-Platform
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania7
9 October 2020
WE ARE HMI
Infotainment System - @ Continental - #2
https://www.continental-automotive.com/en-gl/Passenger-Cars/Interior/Infotainment-Systems/Multimedia-Systems
https://www.continental-automotive.com/en-gl/Passenger-Cars/Interior/Infotainment-Systems/Multimedia-Systems
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania8
9 October 2020
WE ARE HMI
Infotainment System - @ Continental - #3
https://www.continental-automotive.com/en-gl/Passenger-Cars/Interior/Infotainment-Systems/Radios
https://www.continental-automotive.com/en-gl/Passenger-Cars/Interior/Infotainment-Systems/Radios
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania9
9 October 2020
WE ARE HMI
1. Introduction
• Infotainment System – @ Continental
• Features
2. System Architecture
• Definitions
• Requirement analysis
• Decomposition
• Decisions
3. Case Study
Agenda
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania10
9 October 2020
WE ARE HMI
(#1) What is a system?
© www.123rf.com© www.earthtimes.org
Figure 1: Various examples of systems
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania11
9 October 2020
WE ARE HMI
✓ https://www.macmillandictionary.com/dictionary/british/system
System
https://www.macmillandictionary.com/dictionary/british/system
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania12
9 October 2020
WE ARE HMI
(#2) What is (system) architecture?
© dreamtime.com
© timeshighereduction.com
Figure 2: Various examples for architecture
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania13
9 October 2020
WE ARE HMI
✓ ISO/IEC/IEEE 42010:2011(E), Systems and software engineering — Architecture
description
Architecture - #1
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania14
9 October 2020
WE ARE HMI
✓ “An architecture is the set of significant decisions about the organization of a software
system, the selection of the structural elements and their interfaces by which the
system is composed, together with their behavior as specified in the collaborations
among those elements, the composition of these structural and behavioral elements
into progressively larger subsystems, and the architectural style that guides this
organization---these elements and their interfaces, their collaborations, and their
composition.” (Kruchten: The Rational Unified Process, 1999)
Architecture - #2
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania15
9 October 2020
WE ARE HMI
(#3) Why do we need System Architecture?
© www.medium.com
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania16
9 October 2020
WE ARE HMI
Process
System Requirements Architecture
Hardware
Requirements Integration & Test
Architecture
Detailed Design
ImplementationSoftware
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania17
9 October 2020
WE ARE HMI
Establish requirements for an Infotainment System.
(#4) Exercise 1
Figure 4: Infotainment System for Fiat
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania18
9 October 2020
WE ARE HMI
Purpose:
• Analyze requirements.
• Create System Use Cases.
• Define the system from the architectural viewpoint: Context
• External entities (within environment)
• Interdependencies
• Connections
• Interactions
• Interfaces
Requirements analysis - #1
Figure 5: Representation of Context View
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania19
9 October 2020
WE ARE HMI
Requirements analysis - #2
Figure 6: (Simplified) Context view
for OVIP system
bdd [Package] FunctionalAnalysis [System Context]
AMFM
«Actor»
AMFM
«Actor»
AMFM
«Actor»
DAB
1 «Actor»
FM
«Actor»
FM
«Actor»
FM
«Actor»
GPS
1 «Actor»
Speaker
«Actor»
Speaker
«Actor»
Speaker
«Actor»
Microphone
«Actor»
Microphone
«Actor»
Microphone
«Actor»
VehicleBattery
«Actor»
VehicleBattery
«Actor»
VehicleBattery
«Actor»
WifiAntenna
«Actor»
WifiAntenna
«Actor»
WifiAntenna
«Actor»
AudioAuxDevice
«Actor»
AudioAuxDevice
«Actor»
AudioAuxDevice
«Actor»
DVDPlayer
«Actor»
DVDPlayer
«Actor»
DVDPlayer
«Actor»
BTAev
1 «Actor»
USBDevice
«Actor»
USBDevice
«Actor»
USBDevice
«Actor»itsMassStorage
«Actor»
itsMassStorage
«Actor»
itsMassStorage
«Actor»
itsUSBHub
«Actor»
itsUSBHub
«Actor»
itsUSBHub
«Actor»itsIOS
«Actor»
itsIOS
«Actor»
itsIOS
«Actor»
itsAuxVideoIn
«Actor»
itsAuxVideoIn
«Actor»
itsAuxVideoIn
«Actor»
OVIP Head Unit1
pLVDS1
pBTAAudio
pUSBHOST2
pWifiInternalAntenna
pAuxVideo2
pAuxVideo1
pSpeaker
pMIC
pGPSpFM2
pUART1
pLVDS
pETH
pDABantenna
pBTinternalAntenna
pUSBOTG
pUSBHOST4
pUSBHOST1
pCAN
pAuxVideo
pAuxAudio
pAMFM1
pBattery
Display
1 «Actor»
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania20
9 October 2020
WE ARE HMI
• A System Use Case describes the interaction between an actor and the
system in order to achieve a goal.
• Description: Multiple templates are available.
System Use Case
Figure 7: Examples of templates
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania21
9 October 2020
WE ARE HMI
Define the System Use Case for: Drive in reverse gear.
(#5) Exercise 2
Figure 8: Part of diagram for system use case: “Drive in reverse gear”
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania22
9 October 2020
WE ARE HMI
Input:
• Requirements.
• Environment.
Output:
• Reviewed requirements.
• System use cases.
• Use case diagrams.
• Requirements refinement diagrams (for each system use cases).
Requirements Analysis - Summary
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania23
9 October 2020
WE ARE HMI
• Subsystem = component of the system (has-a, composition)
• Can be:
• Real
• Examples: Radio (HW), OS (SW);
• Conceptual
• Examples: Audio;
Decomposition
Figure 9: Example of decomposition: Car - Engine
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania24
9 October 2020
WE ARE HMI
• Building-Block view / Component view / Module view
• What are the subsystems?
• What are the responsibilities for each subsystem?
• What are the dependencies between subsystems?
• How are the interfaces used by subsystem to communicate?
• Are the subsystems loose coupled?
Architectural viewpoints - #1
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania25
9 October 2020
WE ARE HMI
Example – Building Blocks
Figure 10: (Simplified) Building-
Block view for OIP
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania26
9 October 2020
WE ARE HMI
• Runtime view
• What is the flow for each system use case?
• What are the subsystems (and what do they do) for each system use case?
Architectural viewpoints - #2
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania27
9 October 2020
WE ARE HMI
Example – Runtime view
Figure 11: (Simplified) Runtime view for Fiat –
Use case: “Drive in reverse gear”
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania28
9 October 2020
WE ARE HMI
Purpose:
• System is decomposed into subsystems. Each subsystem has allocated a specific set of requirements.
• Interfaces & Ports between subsystems are identified and documented.
• Illustrate the dynamic interaction between subsystems for defined use cases.
Decomposition – Summary - #1
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania29
9 October 2020
WE ARE HMI
Input:
• Requirement analysis = done.
• System use cases = done.
Output:
• High level view of subsystems;
• Interfaces, ports;
• Use case realization diagrams.
Decomposition – Summary - #2
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania30
9 October 2020
WE ARE HMI
Based on the requirements defined in
Exercise 1:
• What would be some of the subsystem(s) in our infotainment
system?
(#6) Exercise 3
Figure 4: Infotainment System for Fiat
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania31
9 October 2020
WE ARE HMI
• Resource allocation
➢ Processes
➢ Memory
➢ CPU core, time
• Quality attributes
➢ System Performance
➢ Start-up time
• Middleware
• Make-or-buy
• Reuse existing solutions
• Imtegration Test Requirements
• Alternatives
Architecture Decisions
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania32
9 October 2020
WE ARE HMI
✓ http://www.automotivespice.com/fileadmin/software-
download/AutomotiveSPICE_PAM_31.pdf
✓ https://www.flecsim.de/images/download/AutomotiveSpiceShortened/index.html
Automotive SPICE
http://www.automotivespice.com/fileadmin/software-download/AutomotiveSPICE_PAM_31.pdfhttps://www.flecsim.de/images/download/AutomotiveSpiceShortened/index.html
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania33
9 October 2020
WE ARE HMI
• Rational Rhapsody
✓ Documentation SysML (Systems Modeling Language based on UML)
• Rational Doors
✓ Requirements
• Rational Rhapsody Gateway
✓ Import requirements from Doors to Rhapsody
✓ Requirement Coverage
Tools
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania34
9 October 2020
WE ARE HMI
1. Introduction
• Infotainment System – @ Continental
• Features
2. System Architecture
• Definitions
• Requirement analysis
• Decomposition
• Decisions
3. Case Study
Agenda
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania35
9 October 2020
WE ARE HMI
Q & A
?
-
Andreea Gradinaru © Continental AGConfidential / Internal
Continental Automotive Romania36
9 October 2020
WE ARE HMI
End of theory. Start of practice.
Hear you next time!