1

CONFIGURATION MANAGEMENT: WHAT DOES VERSION NUMBER TELL US?

2

WHAT IS BUILD

From ToProcessof conversion

Source code Artifactsrun at the end-user

workstation

3

WHY DO WE NEED TO BUILD?

Configuration

BuildRESULT OF

defined set of components or elements of specific versions

components = functional unitscomponents and their versions are chosen to

meet specific objectives or tasks

Main objectives

Functionality Performance

4

WHY DO WE NEED TO BUILD?

Conclusion. Why we need to build is: To incorporate additional functionality (feature)

To reach defined level of performance

Or implement other functional/non-functional requirements

5

WHY DO WE NEED TO MANAGE BUILDS?

When application grows in size, it becomes more complex

What means complex application?

From configuration management point of view,

most complex application incorporate all possible variant properties

6

BUILD VS VARIANT

AppName-1.1.8.en.x32_beta.msi

install.msiBuild:

Variant:

HTC_Touch_Diamond2_WM6.5_RUU_Topaz_S_HTC_RUS_2.16.411.2_Radio_Sign_Topaz_61.44tc.25.32_4.49.25.17_Ship.exe

Real world example:

7

CONNECTION BETWEEN CONFIGURATION AND VARIANTS

build

source code changes (changeset)

variant

configuration +

#1 #2 #3 #N…

Functional requirements for the variant being built

static runtime

version Maturity

Platform

OS

Localization

Build type

8

Variant is the result of the build characterized by the set of specific

properties and their values

WHAT IS VARIANT

9

VARIANT PROPERTIES

Version Build type: debug or release Operating system, hardware platform

(x32, x64, …) Localization (en, ru, ua, …) Platform (development, test, integration,

production) Maturity (alpha, beta, release candidate,

stable) …

10

It is possible to incorporate all variant properties into single version number

11

TELL ABOUT YOUR EXPERIENCE. HOW DO YOU MANAGE YOUR VERSIONS?

13

END OF THE SECTION