SCM variant version management

More documents

Recommendations

Info

Architectural approach: Software asset variant creation • A single source-code base from which all assets are created – With identified variation points at different levels • Compile time (e.g. makefiles resulting in different executables or libraries for the variants) • Installation time (e.g. COM registration of different component variant, installation of different set of configuration property files) • Configuration time (e.g. product engineering, service or end-user configuration elements) • Run time (e.g. hardware availability based variation) Philips Medical Systems, Egbert Algra, SASG Meeting 07/06/2005 20
Example: from sources to assets SourceFile A SourceFile B Makefile X Makefile Y Items under SCM Philips Medical Systems, Egbert Algra, SASG Meeting 07/06/2005 Asset variant X PropertyFile X Asset variant Y PropertyFileY Installer Y Installer X Product X Product Y DeploymentAsset X PropertyFile DeploymentAsset Y Property File Run-tim e initialisation 21
Page 1 and 2: Managing Software Assets in Product
Page 3 and 4: Introduction: PMS company • Emplo
Page 5 and 6: Product samples Philips Medical Sys
Page 7 and 8: Problem Description • Managing th
Page 9 and 10: Scope: operational aspects • Oper
Page 11 and 12: Requirements approach: requirements
Page 13 and 14: Architecture approach: product syst
Page 15 and 16: Known issue 1: Standards evolve •
Page 17 and 18: Known issue 3: Usage of incompatibl
Page 19: Known issue 4: Side-by-side deploym
Page 23 and 24: Lifecycle Approach: SCM variant ver
Page 25 and 26: Lifecycle Approach: Project managem
Page 27: Credits Part of this work has been

SCM variant version management

Create successful ePaper yourself

Delete template?

Save as template?