Unit of competency Outline
Date retreived
22/07/2026 7:55 PM AWST
22/07/2026 7:55 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.
Validate an application design against specifications
Validate an application design against specifications
Unit of competency
National Code
ICAPRG520A
ICAPRG520A
State Code
D8034
D8034
TGA Status
Replaced
Replaced
DTWD Status
Replaced
Replaced
State Implementation and Classification
Approved Date
08/11/2011
Field of Education
020103 - Programming
Original Release Date
08/11/2011
Nominal Hours
40
Description
This unit describes the performance outcomes, skills and knowledge required to check the software application design against specifications and apply validation techniques across the system life cycle.
Notes
Elements and Performance Criteria
1. Evaluate software-requirement specification
- 1.1 Review software requirement specifications document to ensure that requirements are completely specified and correct before software design begins
- 1.2 Validate the software requirement specifications document
2. Create a proof-of-concept prototype
- 2.1 Use rapid application development tools to create prototype system
- 2.2 Present prototype system for demonstration to appropriate person
- 2.3 Validate proof of concept
3. Evaluate software design
- 3.1 Determine if the design is complete, accurate, consistent and feasible
- 3.2 Validate software design document
- 3.3 Validate database structure and elements
- 3.4 Validate user interface (UI)
- 3.5 Review software risk analysis
4. Evaluate source code
- 4.1 Validate consistency between code and software design document
- 4.2 Validate logical structure and syntax using static analysis tools
5. Evaluate testing requirements
- 5.1 Review and validate test plans
- 5.2 Review and validate test cases
6. Document validation
- 6.1 Document results of validation exercise
- 6.2 Recommend current software design or itemise required alterations
- 6.3 Submit report to appropriate person for action
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 requirement specifications document may include:
reports
risks and resourcing
software functions
software system inputs and outputs
timeframe.
Software design document may include:
module test plan generation
test-design generation
traceability analysis
update software risk analysis.
Database structure and elements may include:
database consistency
database integrity
database structure.
User interface may include:
appearance
consistency
design
functions
navigation.
Static analysis tools may include:
Blast (c language)
Checkstyle (for Java)
JSLint (JavaScript checker)
StyleCop (for .net languages).
Software requirement specifications document may include:
reports
risks and resourcing
software functions
software system inputs and outputs
timeframe.
Software design document may include:
module test plan generation
test-design generation
traceability analysis
update software risk analysis.
Database structure and elements may include:
database consistency
database integrity
database structure.
User interface may include:
appearance
consistency
design
functions
navigation.
Static analysis tools may include:
Blast (c language)
Checkstyle (for Java)
JSLint (JavaScript checker)
StyleCop (for .net languages).
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:
verify and validate software application design, including:
creating proof of concept (PoC) prototype
evaluating the technical specification and comparing against the PoC
interpreting and evaluating software design documentation requirements and confirming details with the client
analysing and validating user interface and database requirements
effectively using static analysis tools
walkthrough documents, test plans and test cases.
Context of and specific resources for assessment
Assessment must ensure access to:
tools to create prototype systems
static analysis tools
test plan and test cases
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:
review of candidate’s validation documents
evaluation of validation documents.
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:
verify and validate software application design, including:
creating proof of concept (PoC) prototype
evaluating the technical specification and comparing against the PoC
interpreting and evaluating software design documentation requirements and confirming details with the client
analysing and validating user interface and database requirements
effectively using static analysis tools
walkthrough documents, test plans and test cases.
Context of and specific resources for assessment
Assessment must ensure access to:
tools to create prototype systems
static analysis tools
test plan and test cases
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:
review of candidate’s validation documents
evaluation of validation documents.
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.
Replaced By
| State Code | National Code | Title | Type |
|---|---|---|---|
| AUV98 | ICTPRG520 | Validate an application design against specifications | Unit of competency |
| State Code | National Code | Title | Type |
|---|---|---|---|
| D573 | ICA50711 | Diploma of Software Development | Qualification |