Sub conf 2010
0 likes•351 views
Elster Kromschröder is a company that develops software for embedded systems. They migrated their component management system from ClearCase UCM to Subversion to make all changes traceable and provide tooling support for common actions. Component management involves managing software packages, modules, and their dependencies across releases. The project addressed use cases like version control, change management and integration. It used tools like Visual SVN Server, TortoiseSVN, JIRA and Python to implement the new system. Lessons learned included that open standards enable integration, documentation is important for usability, default installations need customization, and it takes iterations to get a new system working properly.
Sub conf 2010
- 1. Component management for embedded systems via Subversion® and addons - report on successful migration from ClearCase® UCM Manuel Blechschmidt – SubConf 2010 – Munich
- 2. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?
- 3. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?
- 4. Who is Elster Kromschröder? (1)
- 5. Who is Elster Kromschröder? (2) Site Elster Kromschröder Hameln ● Development ● Production ● Quality management ● Service Development ~10 People Software Configuration Management for ● Development ● Service (planned)
- 6. Who is Elster Kromschröder? (3)
- 7. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?
- 8. What was the project? ● Replace current Component Management Solution ClearCase with Subversion ● Make all changes in a project traceable ● Provide tooling support for all common actions ● Establish a best practice workflow which can be used as an example for other departments ● Use a central installation which can be scaled across the whole company
- 9. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?
- 10. What is component management? (1) ● A component is a software package, a web service or a module that encapsulates a set of related functions or data ● It has well defined interfaces which can change during versions ● It can have dependencies to other components in specific versions
- 11. What is component management? (2) ● A Release is a set of components with specific versions which should be compatible with each other
- 12. What is component management? (3)
- 13. What is component management? (4)
- 14. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?
- 15. Which use cases were adressed by the project? (1)
- 16. Which use cases were adressed by the project? (2)
- 17. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?
- 18. Which software components were used? (1)
- 19. Which software components were used? (2) ● Visual SVN Server 2.1.1 ● Patched pysvn 1.7.2 extensions ● TortoiseSVN 1.6.8 ● with JIRA plugin
- 20. Which software components were used? (3)
- 21. Which software components were used? (4) ● JIRA 4.0.2 ● Connected to Active Directory ● Enabled WebServices ● Plugins ● Extended WebServices ● Subversion Plugin
- 22. Which software components were used? (5)
- 23. Which software components were used? (6) ● Python 2.6.5 ● Patched pysvn 1.7.2 ● ZSI Beta 2.1 Web Services Layer ● difflib ● SimpleHTTPServer
- 24. Which software components were used? (7)
- 25. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?
- 26. What lessons were learned? ● Open standards make the integration of independent systems possible ● Good documentation makes people happy and software usable ● Default installations never fullfil your requirements ● It never works the first time
- 27. Questions?