Software Engineering

Size: px

Start display at page:

Download "Software Engineering"

Thomasine Johnston
8 years ago
Views:

1 1 Software Engineering Lecture 10: Configuration Management Stefan Hallerstede Århus School of Engineering 15 September 2011

2 2 Contents Configuration Management Basics Version And Release Management Release Management Building A System Example Concluding Remarks

3 3 Contents Configuration Management Basics Version And Release Management Release Management Building A System Example Concluding Remarks

4 4 Why Do We Need Configuration Management? Software may be produced for different computers for different operating systems for different customers with client-specific functions Example: Initial system Windows version Linux version Desktop version Server version

operating systems for different customers with client-specific

5 5 Configuration Management Planning Define what is to be managed, the configuration items, and a scheme to identify them (e.g. by their path in the file system) Set out who is responsible for the configuration management procedures Define the configuration management policies to be followed Specify the tools to be used for configuration management and the processes for using these tools Describe the structure of the configuration database that is used to record configuration information

configuration management policies to be followed Specify the tools to be used for configuration management and the

6 6 Typical Queries To A Configuration Database Which customers have taken delivery of a particular version of the system? What hardware and operating system is required to run a given system version? How many versions of a system have been created and what were their creation dates? What versions of a system might be affected if a particular component is changed? How many change requests are outstanding on a particular version? How many reported faults exist in a particular version? The configuration management plan determines what is stored in the database and what kind of queries are possible.

How many versions of a system have been created and what were their creation dates?

7 7 Contents Configuration Management Basics Version And Release Management Release Management Building A System Example Concluding Remarks

8 8 Version And Release Management Identifying And Keeping Track of Versions Of A System Objective is to ensure that versions of a system may be retrieved when required are not accidentally changed by the development team Functionality of versions: Enhanced performance Repaired software faults Targeted at different hardware or software platforms Versions with only small differences are also called variants

the development team Functionality of versions: Enhanced performance Repaired software faults

9 9 Version Identification Version numbering V1.1b V1.1.1 V1.0 V1.1 V1.2 V2.0 V2.1 V2.2 V1.1a Attribute-based identification vi (platform = Linux) vi (platform = Windows) for vi software variants for Windows or Linux

10 10 Contents Configuration Management Basics Version And Release Management Release Management Building A System Example Concluding Remarks

11 11 Release Management A release may contain: The executable software Configuration files (defining how the release should be configured for particluar installations) Data files (that are needed for successful system operation) An installation program (that is used to help install the system on target hardware) Electronic and paper documentation (describing the system) Packaging and associated publicity (that have been designed for that release)

operation) An installation program (that is used to help install the system on target hardware) Electronic and

12 12 Factors Influencing The Release Strategy Technical quality of the system Platform changes Competition Customer proposals change Serious system faults that have been reported may demand a fault repair release A new version of an operating system may require a new release A competing product may necessitate a new release Customers may have made and paid for a specific set of system change proposals

fault repair release A new version of an operating system may require a new release A competing

13 13 Contents Configuration Management Basics Version And Release Management Release Management Building A System Example Concluding Remarks

14 14 Building A System System builder Version management system Compilers Linker Build script Source code component versions Object code components Executable system All components in the appropriate version and all files must be available Building is usually an automated process (IDE or build script)

Executable system All components in the appropriate version and all files

15 15 Contents Configuration Management Basics Version And Release Management Release Management Building A System Example Concluding Remarks

16 A successful Git branching model 1 1 Vincent Driessen, 16

17 Distribution Of Repositories 17

18 18 Main Development Branches And Feature Branches Main Branches Feature Branches

19 Hotfixes 19

20 20 Contents Configuration Management Basics Version And Release Management Release Management Building A System Example Concluding Remarks

21 21 Concluding Remarks Configuration management manages system change Requires a scheme for referring to documents under version control System releases include Executable code Data files Configuration files Documentation A good strategy for configuration management is important Good strategies are available

Software Configuration Management, Software Product lines and Summary

Software Configuration Management, Software Product lines and Summary Peter Dolog dolog [at] cs [dot] aau [dot] dk E2-201 Information Systems March 29, 2007 2 Configuration management New versions of software