Download - Agile car development automotive webinar
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:
Agenda
Housekeeping
Presentation
Questions and Answers
Wrap-up
Speakers
Mark Warren, Solutions Director, Perforce
Lennart Kjellén, SCM Specialist, Scania
Jiri Walek, VP Product Management, Polarion
Agile Car Development
ISO 26262 Compliance,
Continuous Integration,
and Asset Management
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
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
Perforce Powers Market Leaders
13,000 20,000 users
9,500 users500+ terabytes
5,000+ userscoders & designers
Complete delivery pipeline
7,000+ releases/year11,000+ users
10+ sites
2,500 users10,000,000
Perforce xact/day
Everything! 11,000+ users
Mobile ICsGames
& Animation Cloud/SaaS Electronics Finance Enterprise
Need for
Change
Customer Expectation
Competition
Costs
Compliance
Forces Driving Change
Keys to Success
Agility
Frequent Releases
Openness
Agility
Future is unpredictable
How much effort needed to make a
change?
Ultimate objective:
– Continuously Releasable (even if not
always released)
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 isReshaping the Future of ALM,”
Kurt Bittner, July 22, 2013
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
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
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?
Openness
Auto platforms
– Apple CarPlay
– Open Automotive Alliance
– …
Development Tools
– Adoption of Git
– Enterprise-readiness of Git etc.
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 ProtectionGit
Metadata
Depot with Versioning Files
P4V
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.”
Recommendations
Review existing processes & tools
Automate
Version Everything
Lennart Kjellén, Scania IT 2014-09-30
19
Agile Car DevelopmentLennart Kjellén, Scania IT
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
Lennart Kjellén, Scania IT 2014-09-30
Lean Thinking is the Scania Way
21
• Continuous Improvement
• Quality
• Eliminate Waste
• Flow orientation
• Standardized way
• Continuous Delivery
• Build/Test/Deploy Automation
• Agile Methods
• Common Versioning Repository
Lennart Kjellén, Scania IT 2014-09-30
Software Development at Scania
22
• Database SW
• Embedded SW
• Web Services
• Mobile Apps
• Communication
Lennart Kjellén, Scania IT 2014-09-30
Smartphone access
to driver/vehicle
data
FMP
Communication
Servers
Web Servers
Monitoring
Report
Email and
SMS
remiders/
alarms
Fleet
Management
Portal
Remote
Diagnosis
Current status message
every minute
Web Service
Interface
FMP
MPMP
Scania Connected Services
Lennart Kjellén, Scania IT 2014-09-30
Continuous Delivery
Lennart Kjellén, Scania IT 2014-09-30
Deployment Pipeline Implementation
Pre Commit
Developer
Build &
Package
Version
Control
Artifact
Repository
Unit TestCode
Coverage
Integration
Test
Deploy &
Sanity Check
Component
Test
Database
Test
Deploy &
Sanity Check
System
Test
Deploy &
Sanity Check
Performance
TestLoad Test
Stress TestCapacity
Test
Acceptance
Test Done
Production
Deployable
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
Lennart Kjellén, Scania IT 2014-09-30 27
SCM Tools Framework
CM-system
Project Product
ArtifactsActivities
Version
Control
System
Issue
Mgmt
System
Documents
Requirements
Source Code
Build Tools
Development Tasks
Bug Reports
Consist ofConsist of
Change RequestsTest Specs
Agile Car DevelopmentISO 26262 Compliance, Continuous Integration, and Asset Management
Jiri WalekVP Product Management
2004 Founded with Disruptive Vision
2005 First Unified, 100% Browser-Based ALM
10 Years Focus 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+MExtensions
200+RegisteredCommunityMembers
15K
EMBRACEChange
Agile make the number of functional changes lower
Eliminate Waste
1. Continuous Backlog Prioritization
2. Early and Frequent Product Review, Verification &
Validation
3. Continuous Integration and Continuous Testing
“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
Specifications
(Static)
Maintain when done
Ensures Consistency
Manage Complexity
User Stories
(Dynamic)
Discard when done
Business Plan
Epic Requirements
Ba
cklo
g
Use
r S
torie
s
Product Documentation
Component Specifications
Potentially
Shippable
Product
+Updated
Product
Documentation
+Updated
Product
Backlog
Large Data Scale
50k Requirements
20mil LoC
Impact Analysis
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
Continuous Integration
DeveloperTester
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)
SCM Trigger
Continuous
Integration
• Gather
Changes
• Compile
• Integrate
• Core
Testing
Build job
Full Verification and Validation
User Story Workflow
Story
Verification
• Compile
• Integrate
• Full Testing
Cost of Fix
Specification Coding Story Verification Release Validation Production
Time
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
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
Thank you.
www.polarion.com
46
Audience Q & A
Mark Warren,
Solutions Director,
Perforce
Lennart Kjellén,
SCM Specialist,
Scania
Jiri Walek,
VP Product Management,
Polarion
Thanks for joining us
Event archive available at:
http://ecast.opensystemsmedia.com/
E-mail us at: [email protected]