Intland Software's Presentation at ALMConf 2010 in Stuttgart, October 26 - 28

1. © 2010 Intland Software
1
Refreshing Software Development
with
Distributed Version Control Systemen (DVCS)
ALMConf 2010, October 26 – 28, Stuttgart
Janos Koppany
Intland Software

2. © 2010 Intland Software 2
Intland & Background
• 2000 - founded by formal Cygnus (RedHat) employees
• 2010 - Intland Software is the leading provider of enterprise-
class collaboration solutions that boost the productivity of
development and business projects.
• 350.000+ users worldwide
codeBeamer
ParticipatecodeBeamer
Participate
Source Code
Engineering
Features
Source Code
Engineering
Features
Collaborative
Tool
Extensions
Collaborative
Tool
Extensions
Integrations
SCMs,
IDEs
Integrations
SCMs,
IDEs
Prof.
Services
Prof.
Services
ALM
+
Collaboration
ALM
+
Collaboration

3. © 2010 Intland Software 3
… and further Fortune 500 customers

4. codeBeamer - Agile ALM
© 2010 Intland Software 4
development methods: V-Model ,Agile, Scrum
codeBeamer

5. © 2010 Intland Software 5
Thinking on the old “Centralized” Way
Reqs.
Reqs.
Reqs.
Reqs.
Report
Report
Report
Status
check
Status
report
Status
report
Status
report
Status
report
Test
plan
Test
plan
Test
plan
Test
plan
DokumenteDokumente
Dokumente
Dokumente
DokumenteDokumente
Dokumente
Dokumente
DokumenteDokumente
Dokumente
Status
check
Status
check
Mails
Mails
Excel
Excel
Excel
Mails
Mails
MailsExcel

6. The World is flat, Intland’s Distributed development
© 2010 Intland Software 6

7. Distributed v.s. Centralized VCS
© 2009 Intland Software, Sebastien Auvray 7

8. Stuttgart
Deployment infrastructure with GIT/Mercurial, Eclipse
© 2010 Intland Software 8
codeBeamer
Agile ALM
Budapest Beijing, Taipei
Git/Mercurial
Repositories
Developer Workstation:
•Windows/Linux (VMWARE)
•Eclipse + Intland’s Mercurial plug-in
•Mercurial
•Web browser
Simbirsk

9. Integration workflow example
© 2009 Intland Software 9
Release
repository
developer
local
developer
local
Integration
manager
developer
public
developer
public

10. Why DVCS?
• Offline commits
• Fast local operations
• Results:
– More robust for distributed teams
– Fine-grained commits
– Searchable history
– Branching and merging is a natural task ->
– Better workflows -> processes
© 2010 Intland Software 10

11. untrusted-
repository
Automotive electronic supply-chain workflow example
© 2009 Intland Software 11
Release
repository
Automotive
electronic
break subsystemnavi subsystem
Sub-
contractor
Sub-
contractor
Sub-
contractor
Sub-
contractor
•open-source
compliance check
•code review

12. Eclipse screenshot – HgEclipse & CBES
© 2010 Intland Software 12

13. Agile Scrum, Kanban process
© 2010 Intland Software 13

14. CodeBeamer UI
© 2010 Intland Software 14

15. MercurialEclipse project @Javaforge.com
© 2010 Intland Software 15