Unit of competency Outline
Date retreived
22/07/2026 3:13 PM AWST
22/07/2026 3:13 PM 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.
Implement configuration management strategies
Implement configuration management strategies
Unit of competency
National Code
ICASAS402A
ICASAS402A
State Code
D8064
D8064
TGA Status
Replaced
Replaced
DTWD Status
Replaced
Replaced
State Implementation and Classification
Approved Date
04/11/2011
Field of Education
031305 - Computer Engineering
Original Release Date
04/11/2011
Nominal Hours
25
Description
This unit describes the performance outcomes, skills and knowledge required to implement administrative and technical procedures throughout the software development and documentation life cycle.
Notes
Elements and Performance Criteria
1. Identify and clarify configuration management requirements
- 1.1 Develop and assemble identification standards for the naming and version control of software and documentation, and provide to stakeholders
- 1.2 Identify the software configuration tools and procedures for the required level of integration into the programming environment
- 1.3 Identify responsibilities for configuration management within the project and for ongoing support, including approval of changes
- 1.4 Take action to ensure that stakeholders are aware of their roles
- 1.5 Identify the point at which items are subjected to configuration control with stakeholders
2. Employ appropriate control mechanisms
- 2.1 Identify and document the method for identification and recording of change requests in line with organisational requirements and ensure this is maintained during development process
- 2.2 Take action to ensure that the evaluation criteria and process for approval of change requests are employed according to organisational requirements
- 2.3 Take action to ensure that other management, security and access control criteria are employed according to organisational requirements
- 2.4 Implement controls to ensure that necessary audit trials and alerts for variations or non-conformance are continuously maintained during development
3. Implement monitoring mechanisms
- 3.1 Implement controls to ensure that mechanisms to identify the status of software throughout the software development life cycle are continuously maintained
- 3.2 Document the development and maintenance of records and status reports required to show the history of baselines and their links to backups
- 3.3 Take action to ensure that the level of detail required in the status reports, and identification of target audiences, meets the configuration management procedures, International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) and organisational requirements
- 3.4 Integrate configuration management into general project management processes for monitoring and control purposes and document
4. Manage release of product
- 4.1 Take action to ensure the physical and functional completeness of items for the purpose of release to all stakeholders
- 4.2 Identify and implement the requirements for formal control of software products
- 4.3 Determine and document policies for retention of baseline or master copies, taking into account safety and security, legislative requirements and organisational guidelines
The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.
Software may include:
commercial applications
in-house or customised
organisation-specific
packaged.
Documentation may follow:
audit trails
ISO, IEC and AS standards
naming standards
project management templates
report writing principles
version control.
Stakeholders may include:
development team
management
project team
sponsor
testers
user.
Software configuration tools may include:
Baseline +Plus
ClearCase
Continuus/CM
CVS
PVCS Configuration Builder
PVCS Version Manager
PVCS Version Manager PLUS
RCS
SCCS
Source Integrity
TeamWare
Version +Plus
Version Stamper.
Organisational requirements may include:
how and what the organisation wants in regard to work environment
preventative maintenance and diagnostic policy, roles and technical responsibilities in the IT department
problem-solution processes
vendor and product service level support agreements.
Requirements may relate to:
application
business
network
people in the organisation
system.
Organisational guidelines may include:
communication methods
content of emails
dispute resolution
document procedures and templates
downloading information and accessing particular websites
financial control mechanisms
opening mail with attachments
personal use of emails and internet access
virus risk.
Software may include:
commercial applications
in-house or customised
organisation-specific
packaged.
Documentation may follow:
audit trails
ISO, IEC and AS standards
naming standards
project management templates
report writing principles
version control.
Stakeholders may include:
development team
management
project team
sponsor
testers
user.
Software configuration tools may include:
Baseline +Plus
ClearCase
Continuus/CM
CVS
PVCS Configuration Builder
PVCS Version Manager
PVCS Version Manager PLUS
RCS
SCCS
Source Integrity
TeamWare
Version +Plus
Version Stamper.
Organisational requirements may include:
how and what the organisation wants in regard to work environment
preventative maintenance and diagnostic policy, roles and technical responsibilities in the IT department
problem-solution processes
vendor and product service level support agreements.
Requirements may relate to:
application
business
network
people in the organisation
system.
Organisational guidelines may include:
communication methods
content of emails
dispute resolution
document procedures and templates
downloading information and accessing particular websites
financial control mechanisms
opening mail with attachments
personal use of emails and internet access
virus risk.
The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria, required skills and knowledge, range statement and the Assessment Guidelines for the Training Package.
Overview of assessment
Critical aspects for assessment and evidence required to demonstrate competency in this unit
Evidence of the ability to:
use quality processes, audit trails and version control to implement administrative and technical procedures throughout the software development and documentation life cycle
implement and maintain reliable and valid configuration management procedures for technical and administrative procedures for use during the software life cycle.
Context of and specific resources for assessment
Assessment must ensure access to:
configuration tools
evaluation criteria
process for approval of change requests
templates for status reports
appropriate learning and assessment support when required
modified equipment for people with special needs.
Method of assessment
A range of assessment methods should be used to assess practical skills and knowledge. The following examples are appropriate for this unit:
verbal or written questioning to assess candidate’s knowledge of:
software development
benchmarking methodologies
audit requirements
parallel development
review of candidate’s documentation, with particular reference to:
code identification in line with organisational requirements
change control
backup management
version control
release mechanisms
direct observation of candidate briefing stakeholders.
Guidance information for assessment
Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, where appropriate.
Assessment processes and techniques must be culturally appropriate, and suitable to the communication skill level, language, literacy and numeracy capacity of the candidate and the work being performed.
Indigenous people and other people from a non-English speaking background may need additional support.
In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge.
Overview of assessment
Critical aspects for assessment and evidence required to demonstrate competency in this unit
Evidence of the ability to:
use quality processes, audit trails and version control to implement administrative and technical procedures throughout the software development and documentation life cycle
implement and maintain reliable and valid configuration management procedures for technical and administrative procedures for use during the software life cycle.
Context of and specific resources for assessment
Assessment must ensure access to:
configuration tools
evaluation criteria
process for approval of change requests
templates for status reports
appropriate learning and assessment support when required
modified equipment for people with special needs.
Method of assessment
A range of assessment methods should be used to assess practical skills and knowledge. The following examples are appropriate for this unit:
verbal or written questioning to assess candidate’s knowledge of:
software development
benchmarking methodologies
audit requirements
parallel development
review of candidate’s documentation, with particular reference to:
code identification in line with organisational requirements
change control
backup management
version control
release mechanisms
direct observation of candidate briefing stakeholders.
Guidance information for assessment
Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, where appropriate.
Assessment processes and techniques must be culturally appropriate, and suitable to the communication skill level, language, literacy and numeracy capacity of the candidate and the work being performed.
Indigenous people and other people from a non-English speaking background may need additional support.
In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge.
Replaces
| State Code | National Code | Title | Type |
|---|---|---|---|
| D0044 | ICAB4076B | Implement configuration management | Unit of competency |
Replaced By
| State Code | National Code | Title | Type |
|---|---|---|---|
| AUW22 | ICTSAS402 | Implement configuration management strategies | Unit of competency |
| State Code | National Code | Title | Type |
|---|---|---|---|
| D557 | ICA40111 | Certificate IV in Information Technology | Qualification |