This talk was presented by Dr. Stefan Bussmann (Volkwagen AG) at Intland Connect: Annual User Conference 2020 on 22 Oct 2020. To learn more, visit: https://intland.com/intland-connect-annual-user-conference-2020/

1. codeBeamer
ECU software development
IT aspects
Stuttgart | 22 October 2020 Data classification: Public

2. codeBeamer is used as a tool for
requirements and test management of
in-house ECU software development
within the Volkswagen Group
– A single installation for group-wide use by all brands
(with exceptions for China and USA)
– Installed in the private cloud (based on Openstack) with
multi-factor authentication
– Access possible over the internet for external partners
– Modern technologies for interfacing with other tools
– Process standards combined with high flexibility on project level
The following will focus primarily on the IT aspects of the codeBeamer installation and use.
| Creation date: 22.10.20 | Responsible department for filing: FID | CSD-class: 9.1 – 2 yearsPage 2
Overview

3. Focus on in-house software development
– Requirements and test management on the
system level is covered by the group-wide
application AVW.
– This includes requirement specifications for
customer functions and vehicle systems.
– codeBeamer is used for ECU software
development when developed in-house.
– Most users are located in the Car.Software
organization, but also in business units of other
brands.
| Creation date: 22.10.20 | Responsible department for filing: FID | CSD-class: 9.1 – 2 yearsPage 3
Development model for passenger cars
define
functions
specify
systems
test
functions
integrate and test
systems
develop
hardware
test and approve
products
define
products
develop
electric / electronics
develop
software

4. codeBeamer needs to integrate with many
Volkswagen internal systems
Need to support current and future industrial
standards, e.g.,
– ReqIF, OSLC, XUnit, ASAM ATX
Need for modern interface technologies to
integrate with legacy or group-specific tools:
– REST API / swagger API
– OpenID Connect or SAML2 for authentication
Investigating the use of integration software
| Creation date: 22.10.20 | Responsible department for filing: FID | CSD-class: 9.1 – 2 yearsPage 4
Interface technologies and integration
PREEvision
version42
TVW
DOORS
JIRA
Bitbucket
Artifactory
Jenkins
Enterprise
Architect

5. Good user experience and high security standards
– Web client (no client installation, https-only, firewall-friendly)
– Available over internet for suppliers (no VPN necessary, faster
onboarding)
– High security standards (data is confidential)
– Multi-factor authentication (MFA) for all users and interfaces
based on international standards, such as OpenID Connect (or
SAML2)
– Integration with Volkswagen Group Identity Provider (Single-
Sign-On, many MFA types available)
– Roles & rights model implementing the need-to-know principle
for users and admins
– Fulfillment of all data privacy regulations (GDPR)
| Creation date: 22.10.20 | Responsible department for filing: FID | CSD-class: 9.1 – 2 yearsPage 5
User experience, security and data privacy

6. Goal: Process standards with high flexibility
– Group-wide process standard with all aspects,
covering international standards such as Automotive
SPICE, ISO 26262 as well as internal standards
– Flexibility to adapt on each level to specifics of brand,
business unit or project
– Changes on higher level are propagated to lower levels
– Possibility to view differences between levels
– Best practices on lower level will be pushed back to
higher levels
Feature requests put forward to extend codeBeamer to
achieve the above goal.
| Creation date: 22.10.20 | Responsible department for filing: FID | CSD-class: 9.1 – 2 yearsPage 6
Process templates
group-level
brand-level
business unit
project-level
… …

7. Implementation of need-to-know principle
– Role IT Admin: assigns role BU Admin
– Role BU Admin: creates projects / categories, assigns
project admin, and manages process templates
– Role Project Admin: assigns users to roles in project
– Categories are used to group projects of different
business units. There is also a naming scheme for
projects.
– Role IT Support: enables new users, handles user
incidents
– Open issue: to limit the data access of the IT support
in order to fulfil the need-to-know principle
| Creation date: 22.10.20 | Responsible department for filing: FID | CSD-class: 9.1 – 2 yearsPage 7
Roles & rights model with clear delegation
IT Admin
BU Admin
Project Admin
User
IT Support

8. Rollout plan until end of 2021
– Go-Live in July 2020 with pilot business unit
(development of vw.os)
– Continuous rollout by business unit and project
(until end of 2021)
– Continuous implementation of interfaces
(15 already requested)
– Continuous improvement of
 templating
 variant management
 process integration and
 support & administration
| Creation date: 22.10.20 | Responsible department for filing: FID | CSD-class: 9.1 – 2 yearsPage 8
Rollout
0
50
100
150
200
250
300
350
Q3/2020 Q4/2020 Q2/2021 Q4/2021
Rollout plan
(active users per day)

9. | Creation date: 22.10.20 | Responsible department for filing: FID | CSD-class: 9.1 – 2 yearsPage 9
Thank you.

10. Dr. Stefan Bussmann
IT Business Partner Manager
FID
Email: stefan.bussmann@volkswagen.de
Volkswagen Aktiengesellschaft
Letterbox 011/18120
38436 Wolfsburg, Germany
As of 22 October 2020 I Version 1.0