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

Course Info

Version Control System

Version control systems (VCS) most commonly run as stand-alone applications. A version control system (also known as a Revision Control System) is a repository of files, often the files for the source code of computer programs, with monitored access. Every change made to the source is tracked, along with who made the change, why they made it, and references to problems fixed, or enhancements introduced, by the change.

Benefits of the Program

Version control system is a modern software development, and it is in demand right now. Syncomint provides you hands-on experience on version control system, here you will gain the practical knowledge about VCS and learn in detail about the 2 aspects of VCS that is perforce and subversion.

Topic List This course on VCS contains the entire concept of Perforce and Subversion. Syncomint provides you Classroom Training as well as Live Virtual Training. COURSE CONTENT
[formac-acc title="Lesson 1: Introduction to Perforce"] Background, Problem Dedefinition, Disposition, Theory.[/formac-acc] [formac-acc title="Lesson 2: Perforce Admin Basics"] Empirical study, Analysis & Conclusion, Software Development Practices, Extreme Programming.[/formac-acc] [formac-acc title="Lesson 3: Perforce Admin Advanced"] Comparison, Architecture and Design through Increments, Test Driven Design, Feature Driven Design, Continuous Integration.[/formac-acc] [formac-acc title="Lesson 4: Introduction to Subversion"] Minute Build, Refactoring, Coding Standards, Collective Code Ownership . Version Tracking, Source Code Management, Actions, Concurrent Editing, Version Control, Project Documentation, manage the ASm assistance, Setup initialization parameter files for ASM instance, Startup and shutdown ASM instances, Administer ASM disk groups.[/formac-acc] [formac-acc title="Lesson 5: Basics and command-line usage"] Files in Source Control, Versioning, Branching, Perforce, Features, Technical Specfication, Internationalization, File support, Exclusive Locking and Concurrent Editing.[/formac-acc] [formac-acc title="Lesson 6: Web access"] Tool stakeholder, Dierent Branch Conventions, Product Version Tracking, Method, Choice of method, Gathering of data, Selection of correspondents, Credibility of the study.[/formac-acc] [formac-acc title="Lesson 7: Time Travel"] Managing data concurrency, Data concurrency, Enqueue mechanism, Resolving lock conflicts, Deadlocks.[/formac-acc] [formac-acc title="Lesson 8: Resolving Conflicts"] 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.[/formac-acc] [formac-acc title="Lesson 9: Using Subversion in the course"] General, Users, Functionality, Perforce applicability for Extreme Programming, General, Communication, Risk Management, Features, Files in Source Control.[/formac-acc] [formac-acc title="Lesson 10: Getting Subversion for your Computer"] Version Control, Product Versioning, Analysis, Extreme Programming, Minute Build, Refactoring, Architecture and Design through Increments, Coding Standards.[/formac-acc] [formac-acc title="Lesson 11: Links"] Collective Code Ownership, SCM and Perforce, General, Users, Functionality, Version Tracking.[/formac-acc]

ClassRoom Schedule

Classroom Training - 10 Days

Day 1

11AM-5PM
INTRODUCTION
  • Background
  • Problem Dedefinition
  • 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
MANAGE THE ASM INSTANCE
  • Setup initialization parameter files for ASM instance
  • Startup and shutdown ASM instances
  • Administer ASM disk groups

Day 5

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

Day 6

11AM-5PM
Usage Areas
  • Tool stakeholders
  • Dierent Branch Conventions
  • Product Version Tracking
  • Method
  • Choice of method
  • Gathering of data
  • Selection of correspondents
  • Credibility of the study
MANAGING DATA CONCURRENCY
  • Data concurrency
  • Enqueue mechanism
  • Resolving lock conflicts
  • Deadlocks

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 Denition
  • 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

Day 3

8AM-12PM && 1PM-5PM
Files in Source Control
  • Versioning
  • Branching
  • Perforce
  • Features
  • Technical Specication
  • Internationalization
  • File support
  • Exclusive Locking and Concurrent Editing
  • Usage Areas
  • Tool stakeholders
  • Dierent 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