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.

1. From Requirements Management to Release
with Git for Android System
ReConf 2012
Janos Koppany, Falko Dautel
Intland Software GmbH
© 2012 Intland Software 1

2. Agenda
• Introduction
• Intland and codeBeamer
• Requirements Management with codeBeamer
• Git
• (eGit)
© 2012 Intland Software 2

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
© 2012 Intland Software 3

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
mer
codeBea
ALM
RM +
codeBeamer
ALM
Integrations
SCMs, Prof.
Collaborative IDEs Services
Tool
Source Code Extensions
Engineering
Features
© 2012 Intland Software 4

5. 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

6. How do customers use codeBeamer?
• Requirements Management • Project & Process
• Distributed Software Management
Development • Issue Tracking
• Change Management • Ticketing System
• Knowledge Management • Business Process
• IT, ITIL, SLA Management Monitoring
© 2012 Intland Software 6

7. Process Support
Scrum, Kanban V-Process, Waterfall, Hybrid
© 2012 Intland Software 7

8. codeBeamer
codeBeamer´s Functions
© 2012 Intland Software 8

9. Project Management Dashboard
© 2012 Intland Software 9

10. Tracker – Workflows and Traceability
© 2012 Intland Software 10

11. SCM Repository – Source Code Management
codeBeamer
supports:
CVS
© 2012 Intland Software 11

12. IT Management Ticketing, Escalation Management
© 2012 Intland Software 12

13. Release Management
© 2012 Intland Software 13

14. Document Management, Baselining
Document
Versioning
Baselining
© 2012 Intland Software 14

15. Reports
EXCEL SCrEEN
Excel
Word
PDF
XML
© 2012 Intland Software 15

16. Access Rights Management
© 2012 Intland Software 16

17. Indexing and Full Text Search
© 2012 Intland Software 17

18. Eclipse Integration
© 2012 Intland Software 18

19. Requirements Management
RM Features:
• Document View
• Wiki Authoring of
Requirements
• Versioning
• Baselining
• Dependency
Graph
• Traceability Matrix
• Suspect Links
• Word Import /
Export
© 2012 Intland Software 19

20. 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

21. 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

22. Working with Git & eGit
Working with Git & eGit
© 2012 Intland Software 22

23. Git – where is it used
Software development for
• mobile devices
• medical devices
• automotive systems
© 2012 Intland Software 23

24. Android – Code Complexity
• 20 millions line of code
• 100 repositories for different components
• Git version control system (DVCS)
© 2012 Intland Software 24

25. Requirements Traceability with Android
• Large code
• Git repositories used for components
• Traceability from requirements to code is complex
© 2012 Intland Software 25

26. DVCS Fork/Pull-Request Workflow Example
Blessed
repository
© 2012 Intland Software 26

27. DVCS Fork/Pull-Request Workflow Example
Fork
creation
A Developer B Developer Blessed
public public repository
© 2012 Intland Software 27

28. DVCS Fork/Pull-Request Workflow Example
Creating a
local clone
A Developer B Developer Blessed
public public repository
A Developer B Developer Integration
local local Manager(s)
© 2012 Intland Software 28

29. DVCS Fork/Pull-Request Workflow Example
Starting a
Pull-request
A Developer B Developer Blessed
public public repository
Checkin changes Pull-request
A Developer B Developer Integration
local local Manager(s)
© 2012 Intland Software 29

30. DVCS Fork/Pull-Request Workflow Example
Merging changes in
blessed repositoriy
A Developer B Developer Blessed
public public repository
Merge
A Developer B Developer Integration
local local Manager(s)
© 2012 Intland Software 30

31. DVCS Fork/Pull-Request Workflow Example
Share changes
with the team
Blessed
repository
A Developer B Developer Integration
local local Manager
© 2012 Intland Software 31

32. eGit Eclipse Plugin
© 2012 Intland Software 32

33. eGit History
© 2012 Intland Software 33

34. eGit – Task / Bug Management Integration
© 2012 Intland Software 34