The level of sophistication in automobiles is skyrocketing. And the number of critical digital assets involved is not limited to software - firmware, maps, manuals, and entertainment objects all represent important product components that must be managed effectively for high quality and standards compliance. Market demands require smaller development cycles, continuous integration and incremental feature releases while still maintaining compliance with the 26262 automotive standards. Experts in agile digital asset management discuss problems, options, solutions, and examples of agile car development and utilizing digital asset management techniques across a large range of digital objects to achieve agility in the development cycle while maintaining quality and compliance.

1. Mark Warren, Solutions Director, PerforceLennart Kjellén, SCM Specialist, Scania
Jiri Walek, VP Product Management, Polarion
Agile Car Development: 26262 Compliance, Continuous Integration, and Asset Management
Moderator:
Curt Schwaderer, OpenSystems Media
Speakers:

2. Agenda
Housekeeping
Presentation
Questions and Answers
Wrap-up

3. Speakers
Mark Warren, Solutions Director, Perforce
LennartKjellén, SCM Specialist, Scania
Jiri Walek, VP Product Management, Polarion

4. Agile Car Development
ISO 26262 Compliance,
Continuous Integration,
and Asset Management

5. Agenda
 Challenges for Modern Automotive
Development
– Mark Warren, Perforce
 Agile/Continuous Delivery at Scania
– Lennart Kjellén, Scania
 Agile Car Development
– Jiri Walek, Polarion
 Panel discussion

6. Versions Everything
Perforce Overview
Global Availability and Support
 Fastest, most scalable,
version management
and collaboration
 Commonly used
for all types of content
– Code
– Binaries
– Movies
– Chip Designs
– Gaming
– Images

7. Perforce Powers Market Leaders
13,000 
20,000 users
9,500 users
500+ terabytes
5,000+ users
coders & designers
Complete delivery
pipeline
7,000+ releases/year
11,000+ users
10+ sites
2,500 users
10,000,000
Perforce xact/day
Everything! 11,000+ users
Mobile ICs
Games
& Animation Cloud/SaaS Electronics Finance Enterprise

8. Need for Change
Customer Expectation
Competition
Costs
Compliance
Forces Driving Change

9. Keys to Success
Agility
Frequent
Releases
Openness

10. Agility
 Future is unpredictable
 How much effort needed to make a
change?
 Ultimate objective:
– Continuously Releasable (even if not
always released)

11. Frequent Releases
Waterfall
• Annual releases
• Mostly manual
Agile
• Release more than
once a year
• Some automation
Continuous
• Weekly/daily updates
• Massive automation
“The days when a
successful organization
could release software
once every 12 to 18
months are over.
Forrester, “Continuous Delivery is
Reshaping the Future of ALM,”
Kurt Bittner, July 22, 2013

12. P I P E L I N E
Continuous Delivery
 Deliver working product to users as quickly as possible
 Every change (check-in) leads to a potential release
 Give business the option to release – what, when, to
whom
 A change in process, and culture
Reqs Dev Test Integ Deploy

13. Frequent Releases
 Consider the different paces of change in a
vehicle
 What are the release cycles now? What should
they be?
 Tune existing systems/build into new projects

14. Version Everything
Consider the elements of a component
•Requirements
•Designs
•Models
•Hardware
•Firmware
•Application
•Source code
•Executables
•Documentation
•Graphics
•Test data
•…
Where is the single source of truth?

15. Openness
 Auto platforms
– Apple CarPlay
– Open Automotive Alliance
– …
 Development Tools
– Adoption of Git
– Enterprise-readiness of Git etc.

16. Hybrid Version Control
 Software Developers *love* git
 Designers, artists, writers: not so
much
 Hybrid Approach
– Contributors use the tools &
workflows they need
– Single point of control &
visibility
– Enterprise scale
– IP Protection
Git
Metadata
Depot with Versioning
Files
P4V

17. Continuous Delivery at NVIDIA
 Leading supplier of automotive
graphics systems
 Invented the GPU in 1999; shipped
over 1 billion to date
 First code check in to Perforce in
1998, now 556M files,1.3B
revisions, 327Tb of data
 7,800 Perforce users (88% of all
employees across 32 locations)
“If it isn’t in Perforce, it’s not in the product.”

18. Recommendations
Review existing processes & tools
Automate
Version Everything

19. Lennart Kjellén, Scania IT
2014-09-30
19
Agile Car Development
Lennart Kjellén, Scania IT

20. Lennart Kjellén, Scania IT
2014-09-30 20
Provider of Transport Solutions
Heavy trucks
Heavy buses
Engines
Workshops
Service agreements
Parts
Driver training
Scania Assistance
Operational leases
Financial leases
Hire purchase
Insurance solutions
Products
Services
Financing

21. Lennart Kjellén, Scania IT
2014-09-30
LeanThinkingis the Scania Way
21
•ContinuousImprovement
•Quality
•EliminateWaste
•Flow orientation
•Standardizedway
•ContinuousDelivery
•Build/Test/DeployAutomation
•AgileMethods
•Common Versioning Repository

22. Lennart Kjellén, Scania IT
2014-09-30
Software Development at Scania
22
•DatabaseSW
•EmbeddedSW
•Web Services
•Mobile Apps
•Communication

23. Lennart Kjellén, Scania IT
2014-09-30
Smartphone access to driver/vehicle data
FMP
CommunicationServers
Web Servers
Monitoring Report
Email and SMS remiders/ alarms
Fleet Management Portal
Remote Diagnosis
Current status message every minute
Web Service Interface
FMP
MP
MP
Scania Connected Services

24. Lennart Kjellén, Scania IT
2014-09-30
Continuous Delivery

25. Lennart Kjellén, Scania IT
2014-09-30
DeploymentPipeline Implementation
PreCommit
Developer
Build& Package
Version
Control
Artifact
Repository
UnitTest
CodeCoverage
Integration Test
Deploy& SanityCheck
ComponentTest
Database
Test
Deploy& SanityCheck
System Test
Deploy& SanityCheck
Performance Test
LoadTest
Stress Test
CapacityTest
AcceptanceTest Done
ProductionDeployable

26. Lennart Kjellén, Scania IT
2014-09-30
Principles of Continuous Integration
Every Commit Should Build the Mainline on an Integration Machine
Keep the Build Fast
Maintain a Single Source Repository
Automate the Build
Make Your Build Self-Testing
Everyone Commits To the Mainline Every Day
Test in a Clone of the Production Environment
Make it Easy for Anyone to Get the Latest Executable
Everyone can see what's happening
Automate Deployment

27. Lennart Kjellén, Scania IT
2014-09-30 27
SCM Tools Framework
CM-system
Project
Product
Artifacts
Activities
Version ControlSystem
Issue MgmtSystem
Documents
Requirements
Source Code
Build Tools
Development Tasks
Bug Reports
Consist of
Consist of
Change Requests
Test Specs

28. Agile Car DevelopmentISO 26262 Compliance, Continuous Integration, and Asset Management
Jiri Walek
VP Product Management

29. 2004Founded with Disruptive Vision
2005First Unified, 100% Browser-Based ALM
10 YearsFocus on Unlocking Synergies:
Full Traceability, Real-Time Collaboration, Intuitive UI
10 Years Customer Satisfaction & Growth
2014$10M Siemens VC Investment
Fortune 1000
Deployments
250+
Users
2.5+M
Extensions
200+
Registered
Community
Members
15K

30. EMBRACE
Change

31. Agile make the number of functional changeslower

32. Eliminate Waste
1.Continuous Backlog Prioritization
2.Early and Frequent Product Review, Verification & Validation
3.Continuous Integration and Continuous Testing

33. “The radio and navigation system in the current S-class Mercedes-Benz requires over 20 million lines of code alone, and that car contains nearly as many ECUs as the new Airbus A380”
Alfred Katzenbach, director of Information Technology Management at Daimler

34. Specifications
(Static)
Maintain when done
 Ensures Consistency
 Manage Complexity
User Stories
(Dynamic)
Discard when done

35. Business Plan
Epic Requirements
Backlog
User Stories
Product DocumentationComponentSpecifications
Potentially
Shippable
Product
+
Updated
Product Documentation
+
Updated
Product
Backlog

36. Large Data Scale
50k Requirements
20mil LoC
Impact Analysis

37. Regulatory Compliance
Demonstrate that the software units fulfill the software specifications and do not contain undesired functionality.
 Requirements are documented
 Verification Scenarios are documented and results traceable
 Source code changes are verified and traceable
ISO 26262/IEC 61508 Qualification by TÜV

38. Continuous Integration
Developer
Tester
SVN Server
Build Server
Trigger CI Build Job
Commit
Changes
Build SW Component
Build Test Automation
Execute Test Automation on SW Component
Feedback
(Report, Build Result)

39. SCM Trigger
Continuous Integration
•Gather Changes
•Compile
•Integrate
•CoreTesting
Build job

40. Full Verification and Validation
User Story Workflow
Story
Verification
•Compile
•Integrate
•Full Testing

41. Cost ofFix
Specification Coding Story Verification Release Validation Production
Time

43. Unified Quality Management
1.One Central Place for the Quality Assurance
2.Same instant processing for all the test issues
3.Traceable to User Stories and Requirements

44. Polarion Solution Highlights
Transparency
Sirona Dental Systems uses Polarion solutions not solely to achieve compliance
with medical device regulations like FDA or IEC 62304, but moreover to make the
development process lifecycle more transparent for all parties involved.
Sirona Dental Systems
Ease of Use
The main reasons we ultimately decided to partner with Polarion were: ease of
use, and the ability to capture all project info in one system.
LifeWatch
Efficiency
Major benefits for us include the "automated" traceability, impact analysis and
suspect link traces fully unified with change and version management.
LifeWatch

45. Thank you.
www.polarion.com

46. 46

47. Audience Q & A
Mark Warren,
Solutions Director,
Perforce
Lennart Kjellén,
SCM Specialist,
Scania
Jiri Walek,
VP Product Management,
Polarion

48. Thanks for joining us
Event archive available at:
http://ecast.opensystemsmedia.com/
E-mail us at: clong@opensystemsmedia.com