phone+91-87222 63165 / +1(510)-379-9024 contact@syncomint.com
Try Our Sample Training Videos

Course Info

Software Configuration Management

Software configuration management (SCM) is a process for facilitating and controlling changes to software products within an organization. A software and hardware prototype is used in the case study throughout the course, allowing the concepts of SCM to be applied during workshops and activities.

Benefits of the Program

This course program covers configuration activities such as: configuration planning, change control and management, system building, and version and release management. You learn how the application core processes of SCM contribute to the success of a software project. Syncomint provides you an extensive hands-on course on SCM.

Topic List

This course program will cover the entire SCM from the fundamentals. You’ll be working hands-on SCM which will make you a valuable software developer. Syncomint provides you Classroom Training as well as Live Virtual Training.

Course Content
[formac-acc title="Lesson 1: Configuration and Release"]Management, Analysing business factors driving CM, Demystifying core CM processes[/formac-acc] [formac-acc title="Lesson 2: Management"]Configuration identification, Configuration control, Configuration status accounting, Configuration auditing, Build management, Process management, Environment management, Teamwork, Defect tracking[/formac-acc] [formac-acc title="Lesson 3: Analysing business factors driving CM"]Determining causes of failure in project scenarios, Positioning strong internal CM controls, Controlling quality in the development life cycle, Releasing stable configurations[/formac-acc] [formac-acc title="Lesson 4: Demystifying core CM processes"]Configuration Identification, Version Management, Configuration Control, Change Management, Configuration Status Accounting, Reporting, Configuration Audits, Compliance, Build and Release Management[/formac-acc] [formac-acc title="Lesson 5: Identifying Configuration Items (CIs)"]Deriving candidate items for the project[/formac-acc] [formac-acc title="Lesson 6: Deriving candidate items for the project"]Extracting CIs from the product and the project, Itemising six steps to bring a work, product under configuration management control[/formac-acc] [formac-acc title="Lesson 7: Categorising and naming items"]Devising an effective naming scheme, Classifying items based on the nature of the project, Aligning a CI into one of four categories[/formac-acc] [formac-acc title="Lesson 8: Baselining CIs"]Defining baselining procedures and creating a checklist, Declaring configuration or phase baselines, Checking CIs into a repository[/formac-acc]

ClassRoom Schedule

Classroom Training - 10 Days

Day 1

11AM-5PM
Introduction
  • Background
  • Problem De_x001C_nition
  • Disposition Theory

Day 2

11AM-5PM
Method
  • Empirical study
  • Analysis & Conclusion
  • Software Development Practices
  • Extreme Programming

Day 3

11AM-5PM
Overview
  • Comparison
  • Architecture and Design through Increments
  • Test Driven Design
  • Feature Driven Design
  • Continuous Integration

Day 4

11AM-5PM
Minute Build
  • Refactoring
  • Coding Standards
  • Collective Code Ownership
  • Version Tracking
  • Source Code Management
  • Actions
  • Concurrent Editing
  • Version Control
  • Project Documentation

Day 5

11AM-5PM
Files in Source Control
  • Versioning
  • Branching
  • Perforce
  • Features
  • Technical Speci_x001C_cation
  • Internationalization
  • File support
  • Exclusive Locking and Concurrent Editing

Day 6

11AM-5PM
Usage Areas
  • Tool stakeholders
  • Di_x001B_erent Branch Conventions
  • Product Version Tracking
  • Method
  • Choice of method
  • Gathering of data
  • Selection of correspondents
  • Credibility of the study

Day 7

11AM-5PM
Possible Criticism Against The Method
  • Empirical Data 30
  • Extreme Programming
  • Continuous Integration
  • Minute Build
  • Collective Code Ownership
  • Architecture and Design through Increments
  • SCM and Perforce

Day 8

11AM-5PM
General
  • Users
  • Functionality
  • Perforce applicability for Extreme Programming
  • General
  • Communication
  • Risk Management
  • Features
  • Files in Source Control

Day 9

11AM-5PM
Version Control
  • Product Versioning
  • Analysis
  • Extreme Programming
  • Minute Build
  • Refactoring
  • Architecture and Design through Increments
  • Coding Standards

Day 10

11AM-5PM
Collective Code Ownership
  • SCM and Perforce
  • General
  • Users
  • Functionality
  • Version Tracking

Live Virtual Class Schedule

Virtual Training - 5 Days

Day 1

8AM-12PM && 1PM-5PM
Introduction
  • Background
  • Problem De_x001C_nition
  • Disposition Theory
  • Method
  • Empirical study
  • Analysis & Conclusion
  • Software Development Practices
  • Extreme Programming

Day 2

8AM-12PM && 1PM-5PM
Overview
  • Comparison
  • Architecture and Design through Increments
  • Test Driven Design
  • Feature Driven Design
  • Continuous Integration
  • Minute Build
  • Refactoring
  • Coding Standards
  • Collective Code Ownership
  • Version Tracking
  • Source Code Management
  • Actions
  • Concurrent Editing
  • Version Control
  • Project Documentation

Day 3

8AM-12PM && 1PM-5PM
Files in Source Control
  • Versioning
  • Branching
  • Perforce
  • Features
  • Technical Speci_x001C_cation
  • Internationalization
  • File support
  • Exclusive Locking and Concurrent Editing
  • Usage Areas
  • Tool stakeholders
  • Di_x001B_erent Branch Conventions
  • Product Version Tracking
  • Method
  • Choice of method
  • Gathering of data
  • Selection of correspondents
  • Credibility of the study

Day 4

8AM-12PM && 1PM-5PM
Possible Criticism Against The Method
  • Empirical Data 30
  • Extreme Programming
  • Continuous Integration
  • Minute Build
  • Collective Code Ownership
  • Architecture and Design through Increments
  • SCM and Perforce
  • General
  • Users
  • Functionality
  • Perforce applicability for Extreme Programming
  • General
  • Communication
  • Risk Management
  • Features
  • Files in Source Control

Day 5

8AM-12PM && 1PM-5PM
Version Control
  • Product Versioning
  • Analysis
  • Extreme Programming
  • Minute Build
  • Refactoring
  • Architecture and Design through Increments
  • Coding Standards
  • Collective Code Ownership
  • SCM and Perforce
  • General
  • Users
  • Functionality
  • Version Tracking