Configuration Management In It
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Configuration Management In It as PDF for free.
More details
- Words: 700
- Pages: 14
Use of configuration management in IT Presented bySiddharth Mepani-07030241031 Sourabh Soni-07030241032 Surbhit Bansal-07030241033 Vijay Chakule-07030241035
Agenda
Definition Configuration Standards SCM Components Goals of SCM Configuration Database Change management Change Tracking Tools Version Management Release Management System Building
Definition…
It is the art of identifying, organizing and controlling modifications to the software being built by a development team. It is the discipline of keeping evolving software products under control, and thus contributes to satisfying quality and delay constraints. Configuration management is concerned with managing evolving software systems: - System change is a team activity - CM aims to control the costs and effort involved in making changes to a system.
Configuration Standards
CM should always be based on a set of standards which are applied within an organisation Standards should define how items are identified, how changes are controlled and how new versions are managed Standards may be based on external CM standards (e.g. IEEE standard for CM) Some existing standards are based on a waterfall process model - new CM standards are needed for evolutionary development.
SCM Components
Repository Management
Engineering Support
Evaluating and Approval Management
Versioning
Re-engineering
Auditing and Reporting
Goals of SCM
Configuration Identification- What code are we working with? Configuration Control- Controlling the release of a product and its changes. Status Accounting- Recording and reporting the status of components. Review- Ensuring completeness and consistency among components. Build Management- Managing the process and tools used for builds. Process Management- Ensuring adherence to the organization's development process. Environment Management- Managing the software and hardware that host our system. Teamwork- Facilitate team interactions related to the process. Defect Tracking- making sure every defect has traceability back to the source. Eg JIRA, Atlas.
The Configuration Database
All CM information should be maintained in a configuration database. This should allow queries about configurations to be answered:
• Who has a particular system version? • What platform is required for a particular version? • What versions are affected by a change to component X? • How many reported faults in version T?
The CM database should preferably be linked to the software being managed.
Change management
Software systems are subject to continual change requests:
• From users; • From developers; • From market forces.
Change management is concerned with keeping track of these changes and ensuring that they are implemented in the most cost effective way.
Change Tracking Tools
A major problem in change management is tracking change status.
Change tracking tools keep track the status of each change request and automatically ensure that change requests are sent to the right people at the right time.
Integrated with E-mail systems allowing electronic change request distribution.
Some Examples: Cruise Control, VSS etc.
Version Management
Version: An instance of a system which is functionally distinct in some way from other system instances.
Invent an identification scheme for system versions.
Plan when a new system version is to be produced.
Ensure that version management procedures and tools are properly applied.
Plan and distribute new system releases.
Tool for versioning: VSS
Release Management
Release planning is concerned with when to issue a system version as a release.
Releases must incorporate changes forced on the system by errors discovered by users and by hardware changes.
They must also incorporate new system functionality
System Building
The process of compiling and linking software components into an executable system.
Different systems are built from different combinations of components.
System Releases
Not just a set of executable programs. May also include:
• Configuration files defining how the release is configured for a particular installation; • Data files needed for system operation; • An installation program or shell script to install the system on target hardware; • Electronic and paper documentation; • Packaging and associated publicity.
Systems are now normally released on optical disks (CD or DVD) or as downloadable installation files from the web.
Thank you
Agenda
Definition Configuration Standards SCM Components Goals of SCM Configuration Database Change management Change Tracking Tools Version Management Release Management System Building
Definition…
It is the art of identifying, organizing and controlling modifications to the software being built by a development team. It is the discipline of keeping evolving software products under control, and thus contributes to satisfying quality and delay constraints. Configuration management is concerned with managing evolving software systems: - System change is a team activity - CM aims to control the costs and effort involved in making changes to a system.
Configuration Standards
CM should always be based on a set of standards which are applied within an organisation Standards should define how items are identified, how changes are controlled and how new versions are managed Standards may be based on external CM standards (e.g. IEEE standard for CM) Some existing standards are based on a waterfall process model - new CM standards are needed for evolutionary development.
SCM Components
Repository Management
Engineering Support
Evaluating and Approval Management
Versioning
Re-engineering
Auditing and Reporting
Goals of SCM
Configuration Identification- What code are we working with? Configuration Control- Controlling the release of a product and its changes. Status Accounting- Recording and reporting the status of components. Review- Ensuring completeness and consistency among components. Build Management- Managing the process and tools used for builds. Process Management- Ensuring adherence to the organization's development process. Environment Management- Managing the software and hardware that host our system. Teamwork- Facilitate team interactions related to the process. Defect Tracking- making sure every defect has traceability back to the source. Eg JIRA, Atlas.
The Configuration Database
All CM information should be maintained in a configuration database. This should allow queries about configurations to be answered:
• Who has a particular system version? • What platform is required for a particular version? • What versions are affected by a change to component X? • How many reported faults in version T?
The CM database should preferably be linked to the software being managed.
Change management
Software systems are subject to continual change requests:
• From users; • From developers; • From market forces.
Change management is concerned with keeping track of these changes and ensuring that they are implemented in the most cost effective way.
Change Tracking Tools
A major problem in change management is tracking change status.
Change tracking tools keep track the status of each change request and automatically ensure that change requests are sent to the right people at the right time.
Integrated with E-mail systems allowing electronic change request distribution.
Some Examples: Cruise Control, VSS etc.
Version Management
Version: An instance of a system which is functionally distinct in some way from other system instances.
Invent an identification scheme for system versions.
Plan when a new system version is to be produced.
Ensure that version management procedures and tools are properly applied.
Plan and distribute new system releases.
Tool for versioning: VSS
Release Management
Release planning is concerned with when to issue a system version as a release.
Releases must incorporate changes forced on the system by errors discovered by users and by hardware changes.
They must also incorporate new system functionality
System Building
The process of compiling and linking software components into an executable system.
Different systems are built from different combinations of components.
System Releases
Not just a set of executable programs. May also include:
• Configuration files defining how the release is configured for a particular installation; • Data files needed for system operation; • An installation program or shell script to install the system on target hardware; • Electronic and paper documentation; • Packaging and associated publicity.
Systems are now normally released on optical disks (CD or DVD) or as downloadable installation files from the web.
Thank you
Related Documents
Configuration Management In It
June 2020 13
Configuration Management
November 2019 27
Configuration Management
June 2020 10
Configuration Management
June 2020 7
Knowledge Management In It
November 2019 30