Component-Based Configuration, Integration and Delivery

1
Component-Based Configuration, Integration and
Delivery

• Tijs van der Storm

2
Introduction

• Me Tijs van der Storm
• Phd project Deliver
• Intelligent Knowledge Management for Software
  Delivery
• Collaboration CWI/University of Utrecht
• Focus
• Improving Software Configuration Management (SCM)
  in Component-Based Software Engineering (CBSE)

3
Component-Based SCM

• SCM know the state of the product at all times
• Controlled evolution of software artifacts
• Selection and configuration of artifacts
• CBSE components, interface, dependencies
• Reduce complexity (factoring)
• Increase time-to-market (parallelism)
• Problem no identification of compositions
• No support for architectural variation and
  evolution
• Impairs tracking, release and delivery

4
Traceability issues

• Lack of identification impairs tracing
• Which version of a dependency was used during
  this build?
• Which versions of components are installed at the
  customer site?
• What is the difference between release X and Y?
• How to produce an update between from X to Y?
• The answers are in the Bill of Materials (BOM)

5
Approach extend continuous integration

• BOMs derive from Continuous Integration
• Build compositions on every affecting change
• Identify the input to the build (transitively)
• Store results in database
• Benefits
• Fully automatic
• Fully reproduceable builds
• Push button releases
• Pure distributions

6
Results and ongoing work

• Sisyphus Continuous Integration Tool
• Incremental backtracking for optimal results
• Populates the Bills of Materials database
• Current work architectural evolution
• Temporary (branches)
• Permanent (variants)
• Towards compositional SCM

7
Thank you questions?

• More info http//www.cwi.nl/storm
• Sisyphus http//sisyphus.sen.cwi.nl8080