Version control Ashima Wadhwa Configuration management Vs Version

  • Slides: 11
Download presentation
Version control Ashima Wadhwa

Version control Ashima Wadhwa

Configuration management Vs. Version control • Configuration management attempts to identify and track all

Configuration management Vs. Version control • Configuration management attempts to identify and track all relevant elements of the configuration of a system, so that all possible errors can be identified, and possible solutions to the problems found. • Version control is a special case of configuration management, where we are concerned with maintaining multiple versions of a software system.

Version control • Version control is a process that documents a baseline for a

Version control • Version control is a process that documents a baseline for a component or module and also stores all revisions or changes to that component in a database for later use. Version control capabilities typically yield the ability to reproduce the precise state of a component at any point in time.

Key Version Control Features • Automatic" vs. "Explicit" Versioning. A snapshot can be taken

Key Version Control Features • Automatic" vs. "Explicit" Versioning. A snapshot can be taken in fundamentally two different ways: 1) automatically, every time a change is made; or, 2) explicitly after a certain set of changes have been instituted and a change set has been created. Both approaches are valid, though the automatic approach has obvious benefits in that it records every change without requiring intervention.

Key Version Control Features • Level of Versioning. Versions can also be created for

Key Version Control Features • Level of Versioning. Versions can also be created for the individual settings or parameters or for configuration files. Once again, the former approach is superior because it records all changes at a very finegrained level. With this approach, you can build up to a file-based version, but if you only record changes at the file level, you will not be able to drill down easily to find individual changes.

Key Version Control Features • Roll-back Capability. In order to be truly useful, the

Key Version Control Features • Roll-back Capability. In order to be truly useful, the configuration management solution must have the ability to isolate a version (either by level or by date and time) and then reintroduce those settings into the application infrastructure. This is alternately referred to as "roll-back".

Version Control • Version control systems support: – Multiple versions of a file –

Version Control • Version control systems support: – Multiple versions of a file – Multiple paths of file revision – Locking to prevent two people from modifying the same file at the same time – Recovery of any prior version of a file – Efficient storage Foo. java (1. 1) Foo. java (1. 2) Foo. java (1. 3) Foo. java (1. 4) Branch Foo. java (1. 2. 1) Foo. java (1. 2. 2) Foo. java (1. 5) Merge

Software metric • A software metric is a property of a software product, process

Software metric • A software metric is a property of a software product, process or related documentation that takes a numeric value that can be measured – Lines of code in a program, number of person-days required to develop a component, etc. • We are interested here in measuring (quantifying) the quality of a software product • Although some companies have introduced measurement programmes, the systematic use of measurement is still uncommon and there are few standards in this area

Relationship between metrics and quality attributes ?

Relationship between metrics and quality attributes ?

Queries?

Queries?