Unit of competency Outline

Date retreived
23/07/2026 12:23 AM AWST

Whilst all efforts are made to provide accurate and timely information from the relevant source/documentation, please be aware that the information supplied may not be the most current version. The accuracy of the detail has not been confirmed by the Department and therefore should not be relied upon without first confirming the contents.

Use version control systems in development environments

Use version control systems in development environments

Unit of competency
National Code
ICTICT449
State Code
OBU10
TGA Status
Current
DTWD Status
Approved
Current Release Number
1.00
Current Release Date
21/07/2020
State Implementation and Classification
Approved Date
15/01/2021
Field of Education
020399 - Information Systems, N.e.c.
Original Release Date
15/01/2021
Nominal Hours
25
Description
This unit describes the skills and knowledge required to use version control systems to track content, versions and maintain a code repository of work when developing in an ICT environment.It applies to individuals who work in a development environment and create a history of changes to track multiple versions of their own or team’s work. These development environments include processes of designing, building and testing code and product. No licensing, legislative or certification requirements apply to this unit at the time of publication.
Notes
Elements and Performance Criteria
1. Prepare to use version control systems (VCS)
  • 1.1 Research and choose version control system (VCS) according to organisational requirements
  • 1.2 Identify required subversion and VCS pre-installation factors
  • 1.3 Determine and communicate installation disruption to required personnel according to organisational policies and procedures
  • 1.4 Install VCS and create personal account and push changes from branch according to VCS service provider and organisational requirements
  • 1.5 Configure tools and user interface of VCS according to organisational requirements
2. Build files in VCS
  • 2.1 Create local repository according to service provider procedures
  • 2.2 Create required directory according to service provider procedures and organisational requirements
  • 2.3 Create and access required staging environment structures and branches
  • 2.4 Create and access files in the repository according to service provider procedures
3. Test VCS
  • 3.1 Add and commit files to staging environment
  • 3.2 Commit required files to local depository
  • 3.3 Locate track of initial version change and confirm new status according to service provider procedures
  • 3.4 Respond to remote pull requests according to service provider procedures
  • 3.5 Retrieve remote commits and locally merge according to service provider procedures
4. Finalise use of VCS
  • 4.1 Document VCS test outcomes according to organisational requirements
  • 4.2 Submit documented outcomes to required personnel
  • 4.3 Respond to feedback on documented outcomes from required personnel
  • 4.4 Obtain final task sign off from required personnel
No information
No information
No information