Process Improvement in Distributed Software Development Using Eclipse with Mercurial or Git

© 2010 Intland Software 1

Process Improvement in Distributed Software Development

Using Eclipse with Mercurial or Git

Eclipse Integrated Development Day

October 12, 2010

Michael Lukas

Intland Software

Agenda

• Intland Software

• codeBeamer

• Customers

• How do customers use our products

• Centralized vs. distributed VCS

• Working with Centralized VCS

• Working with distributed VCS

• Mobile applications workflow example

• Why Intland choose a DVCS

• Questions & Answers


Intland Software

• Intland Software provides

collaborative ALM solutions.

• Intland is driving different

DVCS related open source

projects:

1. EclipseMercurial plug-in

2. codeBeamer ALM for Eclipse,

Git, Mercurial


CollaborationEngine

codeBeamer

codeBeamer is a collaborative, web-based Application Lifecycle

Management(ALM) solution for software development. It provides

more transparency, improves your software development and

business processes.

Main Functions:


- Knowledge Management with Wiki

- Document Management

- Release Management

- Tracker Function – Tracking

requirements, tasks, change requests,

bugs and tests

- SCM: CVS, Subversion, Git and

Mercurial

Eclipse Integrations:

- codeBeamer Eclipse Studio (CBES)

- Hg Eclipse

Where codeBeamer takes place


development methods: V-Model ,Agile, Scrum

codeBeamer

Screenshot of codeBeamer 5.5


Eclipse Screenshot – HgEclipse & CBES



Customers

• ITIL Management

• Change Management

• Process Management

• Knowledge Management

• Requirements Management

• Project Support

• Communication


• Distributed Software

Development

• Issue/ Excel- Tracking

• Ticketing System

• Business Process Monitoring

• Marketing and Sales

How do Customers use our Products

Centralized vs. Distributed VCS


Repository

Michael

DagmarKlaus

Dagmar

KlausMichael

DistributedVCS

commitupdate

pushpull

Centralized VCS

Working with Centralized VCS System


Shared Repository

developer developer developer

Centralized Systems (SVN, CVS, CC, ..)

-Windows/Linux-Eclipse + Subclipse-Web browser

Chicago

Working with Distributed VCS


codeBeamer ALM,collaboration

Berlin Beijing

Git/MercurialRepositories

Developer Workstation:•Windows/Linux (VMWARE)•Eclipse + Git/Mercurial plug-in•Git/Mercurial•Web browser

�

�

�

�

Integration Workflow


Releaserepository

Developerlocal

Developerlocal

IntegrationManager

Developerpublic

Developerpublic

Mobile Applications Workflow Example


Untrusted-Repository

ReleaseRepository

MobileApps

Bluetooth AppNavigation App

App Developer

App Developer

App Developer

App Developer

•open-source compliance check

•code review

Why we choose a DVCS?

• Offline commits

• Fast local operations

• More robust for our distributed teams

• Fine-grained commits

• Searchable history

• Branching and merging is a natural task

• Better workflows �Better processes

• Clean main repository

• Simplified Backup


Questions & Answers

Questions & Answers


Thank you for your attention

Thank you for your attention

For any 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


Contact information

Contact & further information

Michael Lukas

[email protected]

Phone: (EU) +49-711-67400681• General information: www.intland.com or www.javaforge.com

• Follow @intland on Twitter: http://twitter.com/intland


Process Improvement in Distributed Software Development Using Eclipse with Mercurial or Git

Technology

Transcript of Process Improvement in Distributed Software Development Using Eclipse with Mercurial or Git