1 / 18

SOFTWARE CONFIGURATION MANAGEMENT

SOFTWARE CONFIGURATION MANAGEMENT. PRAKASH SAPKOTA(2008/BCT/524) ANIL MANDAL(2008/BCT/508) AMIT KARN(2008/BCT/506). TOPICS OF THIS TALK. How to obtain better quality DEFINITION & DESCRIPTION BENIFITS & DRAWBACKS mgmt process for Conventional software

breanna-hampson
Download Presentation

SOFTWARE CONFIGURATION MANAGEMENT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SOFTWARE CONFIGURATION MANAGEMENT PRAKASH SAPKOTA(2008/BCT/524) ANIL MANDAL(2008/BCT/508) AMIT KARN(2008/BCT/506)

  2. TOPICS OF THIS TALK • How to obtain better quality • DEFINITION & DESCRIPTION • BENIFITS & DRAWBACKS • mgmt process for Conventional software • Block diagram of configuration object

  3. How to obtain better software quality

  4. DEFINITION OF SCM • IN SOFTWARE ENGINEERING, SCM IS THE TASK OF TRACKING & CONTROLLING CHANGES IN THE SOFTWARE ITEMS. • SCM PRACTICES INCLUDE REVISION CONTROL & THE ESTABLISHMENT OF BASELINES (THE POINT AT WHICH A DOCUMENT OR OTHER OBJECT BECOMES A CONFIGURATION ITEM.)

  5. SCM ACTIVITIES • IDENTIFY UNIQUELY THE VERSIONS OF EACH SOFTWARE ITEMS • IDENTIFY THE BUILT STATUS OF SOFTWARE PRODUCTS IN DEVELOPMENT OR DELIVERED AND INSTALLED • CONTROL SIMULTANEOUS UPDATING OF GIVEN SOFTWARE • PROVIDE COORDINATION FOR UPDATING OF MULTIPLE PRODUCT • IDENTIFY AND TRACK ALL ACTION AND CHANGES RESULTING FROM A CHANGE REQUEST ,FROM INITIATION…..TO RELEASE

  6. SCM ACTIVITIES(cont'd….) • MANAGE CODE REPOSITIONS • BUILD SPECIFIC VERSIONS OF SOFTWARE • RECORD WHAT WAS BUILT, WHEN, WHY & BY WHOM • MANUFACTURES, DISTRIBUTE & INSTALL SOFTWARE

  7. MANAGEMENT PROCESS FOR CONVENTIONAL SOFTWARE

  8. BLOCK DIAGRAM OF CONFIGURATION OBJECT COMPOSITION RELATION DESIGN SPECIFICATION: DATA DESIGN ARCHITECTURAL DESIGN MODULE DESIGN INTERFACE DESIGN DATA MODEL: TEST SPECIFICATION: TEST PLAN TEST PROCEDURE TEST CASES MODULE N: INTERFACE DESCRIPTION ALGORITHM DESCRIPTION INTERRELATIONSHIP SOURCE CODE:

  9. A A A The Copy-Modify-Merge Solution ASHOK AND GITA BOTH CHECK OUT FILE A. HERE, CHECKOUT HAS NO LOCKING EFFECT – IT’S JUST A LOCAL COPY. Repository Read Read Configuration Management

  10. A Ashok Gita The Copy-Modify-Merge Solution BOTH EDIT THEIR LOCAL FILES. Repository Configuration Management

  11. Gita Ashok Gita The Copy-Modify-Merge Solution GITA CHECKS IN HER FILE TO THE REPOSITORY FIRST. Repository Write Configuration Management

  12. Gita Ashok Gita The Copy-Modify-Merge Solution NOW, ASHOK TRIES TO CHECK-IN HIS FILE. HE GETS AN “UP-TO-DATE CHECK ERROR” Repository Write Configuration Management

  13. Gita A’ (=Gita+Ashok) Gita The Copy-Modify-Merge Solution ASHOK UPDATES HIS LOCAL COPY TO CONTAIN THE CHANGES MADE BY GITA. CHANGES ARE ADDED TO THE LOCAL FILE. DURING THIS MERGE, CONFLICTS MAY OCCUR. Repository Read Configuration Management

  14. Gita B Gita The Copy-Modify-Merge Solution A NEW MERGED FILE IS CREATED ON ASHOK’S MACHINE. Repository Configuration Management

  15. B B Gita The Copy-Modify-Merge Solution ASHOK COMMITS HIS FILE TO THE REPOSITORY. Repository Write Configuration Management

  16. B B B The Copy-Modify-Merge Solution GITA UPDATES HER FILE FROM THE REPOSITORY. Repository Read Configuration Management

  17. THINGS THAT MAKE AN SCM PROCESS WEAK • NOT INTEGRATED : MONITERING & DEPLOYMENT ARE COMPLETELY DISTINCT PROCESS • POSES PROBLEM FOR LARGE PROJECTS • DESKTOP FOCUSED

  18. THANKS FOR LISTENING THANKS FOR LISTENING

More Related