1. Version Control
Combination of procedures and tools to manage different versions of the software configuration.
Configuration management allows the user to specify alternative configurations of the software system through the selection of the appropriate versions. This is supported by associating with each software version, and then allowing configuration to be specified and constructed by describing the set of desired attributes.
Clemm

2. Software Engineering II
Lecture 34
Fakhar Lodhi

3. Evolution graph
Each node is an aggregate object, i.e. a complete version of the software
Each version of the software is a collection of SCIs
Each version may be composed of different variants

4. Recap

5. Evolution graph
1.3
1.4
1.0
1.1
1.2
2.0
1.5
1.5.1
1.1.1
1.1.2

6. Release Version Numbering
Act of making the product available to its intended customers
Release life cycle
After first release
New versions
Defect fixes – product updates
New features – product upgrades – includes updates

7. Release numbering
Each product release is viewed as being in a unique state which is the total set of functionality possessed by the product release
Release numbering is a mechanism to identify the product’s functionality state.
Each release will have a different product state and hence a different release number

8. Release numbering There is no industry standard
typically a three field compound number of the format X.Y.Z is used
The different fields communicate functionality information about the product release

9. Release Numbering X – major release number
Is incremented to indicate a significant change in the product functionality
Y – feature release number
Incremented when a set of features have been added or significantly modified from their originally documented behavior
Z – defect repair number
Incremented when a set of defects is repaired

10. Release Numbering
Conventionally the first release number would be 1.0.0
1.0.1
1.0.2
1.0.3
1.1.0

11. Internal release numbering
Used by development organization
Staging mechanism for functionality
Regular builds
X.Y.Z.B – X.Y.Z being the planned release
internal releases
Customer releases

12. 1.3
1.4
1.0
1.1
1.2
2.0
1.5
1.5.1
1.1.1
1.1.2

13. Change control – James Bach
Change control is vital. But the forces that make it necessary also make it annoying. We worry about change because a tiny perturbation in the code can cause a big failure in the product. But it can also fix a big failure or enable wonderful new capabilities. We worry about change because a single rogue developer could sink the project; yet brilliant ideas originate in the minds of those rogues, and a burdensome change control process could discourage them from doing creative work.

14. Balancing act
Too much or too little change control creates different types of problems
Uncontrolled change rapidly leads to chaos
Too much control leads to frustration.
Change control mechanism - procedures and tools