Software configuration management

660 views
445 views

Published on

Software configuration Management

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
660
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Software configuration management

  1. 1. IT 4102 C.I.E.Jayasooriya ATI - Kurunegala
  2. 2.  Functions of a version control system Components of a version control system Change Control Testing Developing the configuration management plan Subversion
  3. 3.  Pragmatic Version Control using Subversion by Mike Mason Configuration Management Principles & Practices by Anne Mette Jonassen
  4. 4.  Configuration Management is unique identification , controlled storage , change control & status reporting of selected intermediate work products product components & products during the life of a system
  5. 5.  Configuration management activities may be viewed as cyclic for each item class placed under configuration management
  6. 6.  Identification Storage Change control Status reporting
  7. 7.  The purpose of the identification activity is to determine the metadata for a configuration item Meta data –  It describes configuration items  Metadata for a configuration item may include its name, the name of the person who produced the item, the production date, and references to other related configuration items.
  8. 8.  Two incidents may initiate the identification process:  In the beginning identification starts with a need defined in the plans (eg: project plan)  When you have to change a configuration item, identification start with a change request
  9. 9.  Meta Data
  10. 10.  Methods, conventions, and procedures necessary for the activities in identification  Procedures for registration of metadata  Procedures for inheritance of metadata  Conventions for unique identification  Conventions for authorization  Conventions for identification of components in a delivery
  11. 11.  Project and year: SC.91 Document number: 009 Author : OA.ect Activity identifier: T2.3.1 Document type: RP (Report) Version: 02
  12. 12.  The purpose of storage is to ensure that a configuration item  will not disappear or be damaged  it can be found at any time  delivered in the condition in which you expect to find it  that a record is kept to indicate who has been given the item or a copy of it.
  13. 13.  Storage takes place in libraries. There are 3 types  Controlled library/configuration management library ▪ It is where configuration items are stored. ▪ It may be divided into a number of physical libraries such as documents, source code,etc  Dynamic library/development library ▪ It is where items are kept while they are being produced ▪ this will be in the producers own area
  14. 14.  Static Library/user library ▪ It is where items are used ▪ While being used in the static library, items must not be changed.
  15. 15.  Placement in storage from production Release from storage for usage Release from storage for production
  16. 16. The methods, conventions, and procedures necessary for activities in storage may be Procedures for placing items in storage and related updating of metadata Procedures for release for usage Procedures for release for production Templates for item approval Templates for release request
  17. 17.  change control is a set of processes and approval stages required to change a configuration items attributes The configuration control board (CCB) is responsible for change control.
  18. 18.  Event registration
  19. 19.  documented events change requests
  20. 20.  Creation of the event registration Analysis of the event registration Rejection or acceptance of the event registration. The change request initiates a new configuration item. A new configuration item is identified and created, and the change is implemented Closing of the change request. Closing of the event registration.
  21. 21. User Creation of event registrationDeveloper Analysis of event registration Implementation of changeCCB Evaluation of event Approval or registration disapproval of changeQA Validation of change
  22. 22.  Status reporting makes available, in a useful and readable way, the information necessary to effectively manage a products development and maintenance
  23. 23.  Output – status reports  Release notes  Item lists  Trace matrix
  24. 24.  Procedures for the production of available status reports Procedures for ad hoc extraction of information Templates for status reports

×