Unit - IV Configuration Management, Maintenance & Reengineering.pptx

project

1. UNIT-IV: Configuration Management , Maintenance & Reengineering Software Configuration Management UNIT- IV: Configuration Management, Maintenance & Reengineering 1

2. UNIT- IV: Configuration Management, Maintenance & Reengineering 2 The SCM repository, SCM process, Configuration management for WebApps Maintenance & Reengineering: Software Maintenance, Software Supportability Reengineering , Business Process Reengineering, Software Reengineering Reverse Engineering Restructuring Forward Engineering

3. The SCM repository UNIT- IV: Configuration Management, Maintenance & Reengineering 3 software configuration management (SCM) is any kind of practice that tracks and provides control over changes to source code. Software developers sometimes use revision control software to maintain documentation and configuration files as well as source code. Revision control may also track changes to configuration files . It uses the tools which keep that the necessary change has been implemented adequately to the appropriate component. The SCM process defines a number of tasks: Identification of objects in the software configuration Version Control Change Control Configuration Audit Status Reporting

4. UNIT- IV: Configuration Management, Maintenance & Reengineering 4 Identification Basic Object: Unit of Text created by a software engineer during analysis, design, code, or test. Aggregate Object: A collection of essential objects and other aggregate objects. Design Specification is an aggregate object. Each object has a set of distinct characteristics that identify it uniquely: a name, a description, a list of resources, and a "realization." Version Control Version Control combines procedures and tools to handle different version of configuration objects that are generated during the software process .

5. UNIT- IV: Configuration Management, Maintenance & Reengineering 5 Suppose after some changes, the version of the configuration object changes from 1.0 to 1.1. Minor corrections and changes result in versions 1.1.1 and 1.1.2, which is followed by a major update that is object 1.2. The development of object 1.0 continues through 1.3 and 1.4, but finally, a noteworthy change to the object results in a new evolutionary path, version 2.0. Both versions are currently supported.

6. UNIT- IV: Configuration Management, Maintenance & Reengineering 6 Change Control A change request is submitted and calculated to assess technical merit; potential side effects, the overall impact on other configuration objects and system functions, and projected cost of the change. The results of the evaluations are presented as a change report, which is used by a change control authority (CCA) - a person or a group who makes a final decision on the status and priority of the change. The "check-in" and "check-out" process implements two necessary elements of change control-access control and synchronization control . Configuration auditing –  A software configuration audit complements the formal technical review of the process and product. It focuses on the technical correctness of the configuration object that has been modified. The audit confirms the completeness, correctness, and consistency of items in the SCM system and tracks action items from the audit to closure . Reporting –  Providing accurate status and current configuration data to developers, testers, end users, customers, and stakeholders through admin guides, user guides, FAQs, Release notes, Memos, Installation Guide, Configuration guides, etc .

7. UNIT- IV: Configuration Management, Maintenance & Reengineering 7