Unit of competency Outline
Date retreived
23/07/2026 5:09 AM AWST
23/07/2026 5:09 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.
Prepare software development review
Prepare software development review
Unit of competency
National Code
ICAPRG426A
ICAPRG426A
State Code
D8013
D8013
TGA Status
Replaced
Replaced
DTWD Status
Replaced
Replaced
State Implementation and Classification
Approved Date
04/11/2011
Field of Education
080317 - Quality Management
Original Release Date
04/11/2011
Nominal Hours
25
Description
This unit describes the performance outcomes, skills and knowledge required to establish standards associated with IT technical requirements in the context of quality assurance processes applicable to software development.
Notes
Elements and Performance Criteria
1. Review software standards
- 1.1 Ensure that stakeholders have an understanding of the organisational requirements
- 1.2 Document software standards according to project standards
2. Review implementation standards
- 2.1 Assign software standards to functions according to detailed technical plan
- 2.2 Take action to ensure that communication and distribution strategies are clear, coherent and meet overall project plan requirements
- 2.3 Monitor and report on implementation of standards against acceptance criteria and detailed technical specifications
3. Review software metrics and milestones
- 3.1 Define metrics related to the project milestones, and timeframe and cost considerations
- 3.2 Develop schedule of quality reviews
- 3.3 Determine quality considerations by identifying in-process measurement points that relate to critical organisational requirements
- 3.4 Determine method to benchmark and scale achievement against stated stakeholders requirements and cost considerations
- 3.5 Report metrics and milestones to stakeholders in a clear and coherent manner and take action to ensure written agreement
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.
Stakeholders may include:
development team
project team
sponsor
user.
Organisational requirements may include:
how and what the organisation wants in regard to work environment
preventative maintenance and diagnostic policy
problem solution processes
roles and technical responsibilities in the IT department
vendor and product service level support agreements.
Standards may include:
International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) standards
Java coding standards
GNU coding standards
organisational standards
project standards.
Project standards may include:
change control
delivery against required milestones and budget
development methodology
ease of modification and maintenance
project plan
quality of software modules
reporting mechanisms
sharing of code or libraries.
Communication may include:
non-verbal methods, such as written messages, emails and memos
verbal methods, such as telephone, meetings and video conferencing.
Stakeholders may include:
development team
project team
sponsor
user.
Organisational requirements may include:
how and what the organisation wants in regard to work environment
preventative maintenance and diagnostic policy
problem solution processes
roles and technical responsibilities in the IT department
vendor and product service level support agreements.
Standards may include:
International Organization for Standardization (ISO), International Electrotechnical Commission (IEC) and Australian Standards (AS) standards
Java coding standards
GNU coding standards
organisational standards
project standards.
Project standards may include:
change control
delivery against required milestones and budget
development methodology
ease of modification and maintenance
project plan
quality of software modules
reporting mechanisms
sharing of code or libraries.
Communication may include:
non-verbal methods, such as written messages, emails and memos
verbal methods, such as telephone, meetings and video conferencing.
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:
establish the standards associated with the IT technical requirements, taking into account quality assurance processes that are in place for the development of software
monitor the application of these standards within the project.
Context of and specific resources for assessment
Assessment must ensure access to:
technical specifications
organisational standards for documentation and version control
project management process and hierarchy
future organisational business processes
software requirement specifications
interface requirement specifications
system requirements
design specifications
project budget and timeframe
appropriate learning and assessment support when required
modified equipment for people with special needs.
Note: Data used in preparing the development review should be validated and come from other projects or related organisational activities.
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:
quality assurance
appropriate quality standards for software development
benchmarking
review of candidate’s documented software standards
evaluation of candidate’s report to 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:
establish the standards associated with the IT technical requirements, taking into account quality assurance processes that are in place for the development of software
monitor the application of these standards within the project.
Context of and specific resources for assessment
Assessment must ensure access to:
technical specifications
organisational standards for documentation and version control
project management process and hierarchy
future organisational business processes
software requirement specifications
interface requirement specifications
system requirements
design specifications
project budget and timeframe
appropriate learning and assessment support when required
modified equipment for people with special needs.
Note: Data used in preparing the development review should be validated and come from other projects or related organisational activities.
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:
quality assurance
appropriate quality standards for software development
benchmarking
review of candidate’s documented software standards
evaluation of candidate’s report to 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 |
|---|---|---|---|
| D0042 | ICAB4064B | Prepare software development review | Unit of competency |
Replaced By
| State Code | National Code | Title | Type |
|---|---|---|---|
| AUV73 | ICTPRG426 | Prepare software development review | Unit of competency |
| State Code | National Code | Title | Type |
|---|---|---|---|
| D557 | ICA40111 | Certificate IV in Information Technology | Qualification |