from requirements management to release with git for android system
DESCRIPTION
Currently, Android is becoming the favourite systems software within the embedded developments field. codeBeamer’s Requirements Management platform supports Android’s complex code structure of 80 repositories and 1-10 GB Code in Git repositories.TRANSCRIPT
From Requirements Management to Release with Git for Android System
© 2012 Intland Software 1
ReConf 2012
Janos Koppany, Falko Dautel Intland Software GmbH
Agenda
• Introduction
• Intland and codeBeamer
• Requirements Management with codeBeamer
• Git
• (eGit)
© 2012 Intland Software 2
© 2012 Intland Software 3
Company Profile: Intland Software GmbH
• Founded in 1999
• Headquarters in Stuttgart, Germany
• Office in Sunnyvale, CA, USA
• Partners in Taiwan and Korea
• A leading provider of enterprise-class RM + ALM solutions
• Host of www.javaforge.com = OpenSource development platform with more than 40,000 registrations
4 © 2012 Intland Software 4
Intland's History
• 2002 - codeBeamer 1.0 – for early adopters
• 2008 – codeBeamer, Jolt Award, > 100.000 users
• 2011 – Cloud support over 30.000 SaaS users
• 2011 – codeBeamer RM
codeBeamer
RM + ALM
Source Code Engineering
Features
Collaborative Tool
Extensions
Integrations SCMs, IDEs
Prof. Services
codeBeamer
ALM
codeBeamer
What is codeBeamer? • Requirements Management and Application Lifecycle Management
Platform
• Designed for centralized management of processes, users and projects
• Integrated wiki, document workflow and escalation management
• Provides full traceability, improves visibility and reduces costs
• Integrates Git, Mercurial and Subversion as version control systems
• 100% browser-based
• Runs on Windows, Linux and Mac OS
© 2012 Intland Software 5
© 2012 Intland Software 6
How do customers use codeBeamer?
• Requirements Management
• Distributed Software Development
• Change Management
• Knowledge Management
• IT, ITIL, SLA Management
• Project & Process Management
• Issue Tracking
• Ticketing System
• Business Process
Monitoring
Process Support
© 2012 Intland Software 7
Scrum, Kanban V-Process, Waterfall, Hybrid
codeBeamer
codeBeamer´s Functions
© 2012 Intland Software 8
Project Management Dashboard
© 2012 Intland Software 9
Tracker – Workflows and Traceability
© 2012 Intland Software 10
SCM Repository – Source Code Management
© 2012 Intland Software 11
codeBeamer supports:
CVS
IT Management Ticketing, Escalation Management
© 2012 Intland Software 12
Release Management
© 2012 Intland Software 13
Document Management, Baselining
© 2012 Intland Software 14
Baselining
Document Versioning
Reports
© 2012 Intland Software 15
EXCEL SCrEEN
Excel Word PDF XML
Access Rights Management
© 2012 Intland Software 16
Indexing and Full Text Search
© 2012 Intland Software 17
Eclipse Integration
© 2012 Intland Software 18
Requirements Management
© 2012 Intland Software 19
RM Features:
• Document View
• Wiki Authoring of
Requirements
• Versioning
• Baselining
• Dependency
Graph
• Traceability Matrix
• Suspect Links
• Word Import /
Export
Change Management Change requests in codeBeamer
• Completely transparent, can be screened from start until closing.
• Full traceability by history function: Together with Version function and Issue con-nectivity it’s revealed which modules, requirements or versions are effected or which files are changed.
© 2012 Intland Software 20
Test Case Management
Testing & Quality Assurance
• codeBeamer’s centralized data repository maintains relationships between
releases, requirements, test and defects
• End-to-end traceability for the testing process is provided
© 2012 Intland Software 21
Working with Git & eGit
Working with Git & eGit
© 2012 Intland Software 22
Software development for
• mobile devices
• medical devices
• automotive systems
© 2012 Intland Software 23
Git – where is it used
• 20 millions line of code
• 100 repositories for different components
• Git version control system (DVCS)
© 2012 Intland Software 24
Android – Code Complexity
• Large code
• Git repositories used for components
• Traceability from requirements to code is complex
© 2012 Intland Software 25
Requirements Traceability with Android
DVCS Fork/Pull-Request Workflow Example
© 2012 Intland Software 26
Blessed repository
DVCS Fork/Pull-Request Workflow Example
© 2012 Intland Software 27
Blessed repository
A Developer public
B Developer public
Fork creation
DVCS Fork/Pull-Request Workflow Example
© 2012 Intland Software 28
Blessed repository
A Developer public
B Developer public
A Developer local
B Developer local
Integration Manager(s)
Creating a local clone
DVCS Fork/Pull-Request Workflow Example
© 2012 Intland Software 29
Blessed repository
A Developer public
B Developer public
A Developer local
B Developer local
Integration Manager(s)
Starting a Pull-request
Checkin changes Pull-request
DVCS Fork/Pull-Request Workflow Example
© 2012 Intland Software 30
Blessed repository
A Developer public
B Developer public
A Developer local
B Developer local
Integration Manager(s)
Merging changes in blessed repositoriy
Merge
DVCS Fork/Pull-Request Workflow Example
© 2012 Intland Software 31
Blessed repository
A Developer local
B Developer local
Integration Manager
Share changes with the team
eGit Eclipse Plugin
© 2012 Intland Software 32
eGit History
© 2012 Intland Software 33
eGit – Task / Bug Management Integration
© 2012 Intland Software 34