This pilot has been carried out in Espotel. Espotel is a SME company working as a subcontractor in the telecommunication industry. Espotel has own products, such as, PROCKET testing platform and JiVe platform. Espotel had a challenge to coordinate development work in distributed development environment. This pilot focuses on solutions to support distributed version/configuration management and project management. The pilot has been carried out during 2nd half 2008 – 1st half 2009. Experiences have been collected and documented in cooperation with VTT. Espotel successfully applied Subversion (SVN) to support distributed version/configuration management.
The goal of the pilot was to evaluate Subversion and Trac to support distributed version/configuration management and project management.
In this case Subversion is used as a distributed version/configuration control tool and Trac is used for project management. However, these tools were not used as an integrated toolset.
The results of the pilot show that Subversion provides lightweight version/configuration management features for distributed SW teams. Trac was piloted and found promising tool. However, Trac could not be used since main contractor required the use MS Project for project reporting. This case showed that in some cases subcontractor needs to adapt to main contractor’s tool infrastructure. Therefore, maincontractor-subcontractor relationship may dictate the selection of tools for a project unless there are means to easily transfer project data between different tools (data export-import).
Baselining was stated as an important feature to ensure the traceability of product data e.g. for bug fixing. The planning of version/configuration management happens in the beginning of development project.
As a conclusion this pilot has shown that Subversion supports version/configuration management in Espotel and enables bug corrections in orderly manner leaving change history information. Version/configuration management can not prevent errors, but makes it easier to solve problems, such as:
– Keep track of changes
– Product and developer branches
– Revision tagging
– Revert back to old revision
– Update changes, synchronize work
– Backup mechanism
However, for version/configuration management, project management policy must ensure:
– Proper usage of version control software
– Communication
– Reasonable division of tasks, no overlapping effort
Position in the Domain
.jpg)
Used Methofds and Tools
Trac and SubVersion / TE-WP2-CBT-1-S1
Experience
- Cost saving was considerable
- Time-to-market was improved
- Reusability was improved
- Quality was improved
