© 2011 Intland Software 1

Process Optimization and Quality Improvement with

Distributed Version Control Systems (DVCS) for the

Integration of Software Development

Janos Koppany / Michael Lukas

Intland Software

embedded world 2011, Nuremberg

© 2011 Intland Software 2

Intland & Vision

• Intland Software is leading provider of enterprise-class Agile

ALM & collaboration solutions that boost productivity of

development and business projects.

• Intland’s headquarter is located in Stuttgart.

codeBeamer - Agile ALM

© 2011 Intland Software 3

development methods: V-Model ,Agile, Scrum

codeBeamer

Agenda

• The Problems with centralized Systems

• Why using DVCS?

• Centralized vs. distributed VCS

• Processes in DVCS

• Deployment infrastructure with DVCS

• Summary

• LIVE DEMO

© 2011 Intland Software 4

The Problems with centralized Systems

• Bandwidth between continents (i.e. Asia and EU )

• Slow Update, Sync.

• Merge is …

• Offline working/ commit

© 2011 Intland Software 5

© 2011 Intland Software 6

Thinking on the old “Centralized” Way

Reqs.

Reqs.

Reqs.

Reqs.

Report

Report

Report

Statuscheck

Statusreport

Statusreport

Statusreport

Statusreport

Testplan

Testplan

Testplan

Testplan

DokumenteDokumente

Dokumente

Dokumente

DokumenteDokumente

Dokumente

Dokumente

DokumenteDokumenteDokumente

Statuscheck

Statuscheck

MailsMails

Excel

Excel

Excel

Mails

Mails

MailsExcel

The World is flat, Distributed development

© 2011 Intland Software 7

Distributed vs. Centralized VCS

© 2009 Intland Software, Sebastien Auvray 8

Centralized Version Control, Subversion, CVS, CC, …

© 2011 Intland Software 9

Shared Repository

developer developer developer

Decentralized Process Workflow Example

© 2009 Intland Software 10

Releaserepository

developerlocal

developerlocal

Integrationmanager

developerpublic

developerpublic

untrusted-repository

Example: Automotive electronic supply-chain workflow

© 2009 Intland Software 11

Releaserepository

Automotiveelectronic

break subsystemnavi subsystem

Sub-contractor

Sub-contractor

Sub-contractor

Sub-contractor

•open-source compliance check

•code review

Summary – Why DVCS

• Online/Offline working

• Processes improvment

• Fast local operations

• Higher quality

• Results:

– More robust for distributed teams

– Fine-grained commits

– Searchable history

– Branching and merging is a natural task

© 2011 Intland Software 12

Chicago

Example: ALM deployment with Git/Mercurial, Eclipse

© 2011 Intland Software 13

Seoul Tokyo

VMWARE8 CPU | 32 GB RAM•Windows / Linux •Apache, Git/Mercurial-Oracle/MySQL RDBMS•codeBeamer

VMWARE2 CPU | 16 GB RAMWindows / LinuxGiT/Mercurial

Disk:•100 GB for Git/Mercurial•100 GB Disk for Oracle (issues, attachments, history)•2 TB for documents, binaries

codeBeamer integrated services for issue/task/incident tracking, continuous integration, testing, release management, baselines, search, code review , source and binary management

Developer:Windows/Linux2 GB RAMWindows / LinuxGiT/MercurialeGit/MercurialEclipseEclipse

Eclipse IDE Integration

© 2011 Intland Software 14

codeBeamer Web UI

© 2011 Intland Software 15

Thank you!

Thank you for your attention!

If you need further information

please visit our homepage:

www.intland.com

www.javaforge.com

HgEclipse: http://www.javaforge.com/project/HGE

codeBeamer Eclipse Studio: http://www.javaforge.com/project/CBES

© 2011 Intland Software 16