Scribd Logo
Upload

Welcome to Scribd!

  • 117 views

    Unit 4-Configuration Management

    Uploaded by

    Justin Gibbs
    Configuration management is the process of managing changes to software artifacts in a controlled manner. It involves establishing a configuration library to store artifacts like requirements, design documents, test cases, and more. Changes to configurable artifacts are reviewed and approved, while some artifacts like test results do not require tracking changes. Controlled artifacts also change in a managed way. The configuration management process involves drafting, reviewing, approving artifacts, and versioning them. Tools can help automate configuration management but also have limitations. Planning is needed to set up the configuration library and management process.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd

    Unit 4-Configuration Management

    Uploaded by

    Justin Gibbs
    117 views30 pages
    Configuration management is the process of managing changes to software artifacts in a controlled manner. It involves establishing a configuration library to store artifacts like requirements, design documents, test cases, and more. Changes to configurable artifacts are reviewed and approved, while some artifacts like test results do not require tracking changes. Controlled artifacts also change in a managed way. The configuration management process involves drafting, reviewing, approving artifacts, and versioning them. Tools can help automate configuration management but also have limitations. Planning is needed to set up the configuration library and management process.

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Configuration management is the process of managing changes to software artifacts in a controlled manner. It involves establishing a configuration library to store artifacts like requirements, design documents, test cases, and more. Changes to configurable artifacts are reviewed and approved, while some artifacts like test results do not require tracking changes. Controlled artifacts also change in a managed way. The configuration management process involves drafting, reviewing, approving artifacts, and versioning them. Tools can help automate configuration management but also have limitations. Planning is needed to set up the configuration library and management process.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    117 views30 pages

    Unit 4-Configuration Management

    Uploaded by

    Justin Gibbs
    Configuration management is the process of managing changes to software artifacts in a controlled manner. It involves establishing a configuration library to store artifacts like requirements, design documents, test cases, and more. Changes to configurable artifacts are reviewed and approved, while some artifacts like test results do not require tracking changes. Controlled artifacts also change in a managed way. The configuration management process involves drafting, reviewing, approving artifacts, and versioning them. Tools can help automate configuration management but also have limitations. Planning is needed to set up the configuration library and management process.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    You are on page 1of 30

    Unit 4 Configuration Management

    Configuration Managemnet
    Change is continuous proces in software development Many artifacts are created ,used and modified One needs to manage the changes in a controlled way Configuration means patterns, designs which affect the characteristics or attributes of the final product Controlling a change and managing the effect of one change on the other artifacts through impact analysis to produce desired patterns is termed Configuration Management

    Change Management
    Change management involves applying the approved changes under a controlled environment When changes are tracked, it becomes configuration management If changes are not tracked , it remains as change management

    Configurable Artifacts
    Some artifacts needs to be changed during the SDLC. Such artifacts are called configurable artifacts. Ex:SRS, design documents, test cases Changes in one may start a chain reaction and one may need to control it

    Nonconfigurable Arifacts
    There are few artifacts may change or may not change If there is any change nobody needs to track /control the results Ex: test results, minutes of meeting

    Controlled Artifacts
    There are few artifacts may change , but do not need any review Though change may not require any approval, the changes must happen in a controlled manner Ex:changes in structure of the organisation, contact people, changes in team members.

    Managed and controlled Artifacts


    Changes are controlled and tracked. Any such change needs someone to review and approve. Ex: SDLC Plans, requirement specification, design documents

    Cycle of Configuration Management


    Creation of Draft Review of Draft Baselining - Once the Final decision is reached on the review comments, actions are initiated accordingly to update the artifacts Versioning Methods xx.yy.zz--- xx represents a major change yy represents minor change zz represents a draft version xx.yy--- xx for all changes zz represents a draft version

    Configuration Management Process


    Draft-> Review->Rework->Baseline And further updations as and when essential Steps: -Establishing Configuration library -PM is the owner of CL -CL stores all configurable items and work products for the given project. -Structure of a configuration library -Planning artifacts -Source related artifacts -Requirements related artifacts -Design related artifacts -Testing artifacts

    continued Establishing definition of versions and processes for updation

    Definition of access privileges for users of configuration library -Administrative Access - Add/Delete Access -Check out/Check in access -Read Access -Drafting a configurable item -Review of Draft -Approval of Draft -Further Updation -Creation of documents -Check in/ Check Out -Get latest version -Working folder -Deleting Cofiguration artifacts -Recovery of deleted artifacts -Destroy/Purge for artifacts

    Auditing Configuration Library


    Status Accounting Configuration Management Audit

    Typical configurable item


    Requirements, Technology-.Jaya Complexity .Anupam Process.Upasana Complete services H/S---Bharat CompatibilityAbhijit Billing/Type of project, Testing----Girish Change in the process---Divya Constraints----Nileshwari Integration of different modules---Sonali Planning----Manoj Documenting---Ami Reliable and Accurate---Aman

    Few more concepts about configuration Library


    -Storage of configurable items in the library -Branching -Merging -Finding history -Comparison -Rollback -Labeling -Pinning -Sharing -Conflict Handling -Multiple checkout

    Using automated configuration management tools


    Visual Source Safe CVS Team foundation Server Source Depot Share Point Server

    Advantages of using a tool


    Automated Accuracy Ambiguity free Cost efficiency Performance User friendly GUI Abstract Regular backups Security Regular updation

    Disadvantages of Using Tools


    Experts required Errors Small projects Time consumed to learn the concept Cost for small projects Frequent usability? Platform issues Availability Complexity

    Configuration management Planning


    Is required to set up and use configuration Library. Basic areas of configuration management: 1.Introduction 2.Scope 3.Configuration management activities and responsibilities 4.Access privileges 5.Configuration management procedure 6.Configurable items with naming conventions 7.Change Control 8.Working folder definition 9.Commenting standards 10.Labeling standards 11.Tools and usage 12.Assumptions and risks 13.Configuration status reporting 14.Traceability matrix 15.Integration and build procedure 16.Configuration management audits

    Starts during the early phases of the project All products of the software process may have to be managed
    Specifications Designs Programs Test data User manuals

    Thousands of separate documents may be generated for a large software system

    Defines the types of documents to be managed and a document naming scheme Defines who takes responsibility for the CM procedures and creation of baselines Defines policies for change control and version management Defines the CM records which must be maintained Describes the tools which should be used to assist the CM process and any limitations on their use

    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

    The change management process


    Request change by completing a change request f orm Analyze change request if change is valid then Assess how change might be implemented Assess change cost Submit request to change control board if change is accepted then re peat make changes to sof tw are submit changed sof tw are for quality approval until sof tware quality is adequate create new system version else reject change request else reject change request

    Maintenance activities and configuration Management

    Applying a patch Updating source code

    Configuration Management Measurements

    Quality Tips
    Understand the limitations of tools and database used in automated tools for configuration management. Every tool may have some limitations and database size also matters to the maintain the integrity of software

    Create a configuration library only after understanding the customer specific and project specific requirements. Future requirements for the project must be considered while selecting a tool and setting up a library.

    Conduct baseline audits and configuration management audits as per the frequency defined. This can ensure that deliverables going to the customer are correct and the configuration management process is followed correctly

    Be careful while dealing with conflicts. As far as possible, conflicting situations must be avoided

    Key Points
    Configuration management is the management of system change to software products A formal document naming scheme should be established and documents should be managed in a database The configuration database should record information about changes and change requests A consistent scheme of version identification should be established using version numbers, attributes or change sets

    You might also like