Unit of competency Outline
Date retreived
22/07/2026 1:14 AM AWST
22/07/2026 1:14 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.
Analyse software requirements
Analyse software requirements
Unit of competency
National Code
ICAPRG419A
ICAPRG419A
State Code
D8011
D8011
TGA Status
Replaced
Replaced
DTWD Status
Replaced
Replaced
State Implementation and Classification
Approved Date
06/10/2011
Field of Education
020305 - Systems Analysis And Design
Original Release Date
06/10/2011
Nominal Hours
60
Description
This unit describes the performance outcomes, skills and knowledge required to research and analyse client requirements, produce a range of options, and create a software requirements document.
Notes
Elements and Performance Criteria
1. Gather and confirm client requirements
- 1.1 Confirm requirements and scope with the client
- 1.2 Gather information regarding requirements via sources of information and business processes
- 1.3 Analyse client requirements to determine the project scope and the problem context or opportunity faced by the business
- 1.4 Document client requirements, project scope, related problems and sources of information
2. Analyse functional and related non-functional requirements
- 2.1 Map business processes using modelling tools, such as unified modelling language (UML)
- 2.2 Determine opportunities for business process efficiencies
- 2.3 Document functional and related non-functional processes
3. Analyse the feasibility of a project
- 3.1 Analyse the technical feasibility of the project
- 3.2 Analyse the operational feasibility of the project
- 3.3 Determine the budget and schedule feasibility of the project
- 3.4 Examine how the project will fit within the organisation
4. Develop high-level system solutions
- 4.1 Develop and document feasible solutions for client requirements
- 4.2 Explore and document the feasibility of each solution
- 4.3 Examine alternatives against project constraints
- 4.4 Document assumptions, dependencies and required resources
- 4.5 Produce a project risk analysis
- 4.6 Document future requirements
5. Prepare and publish software-requirements documentation
- 5.1 Develop software-requirements document
- 5.2 Submit software-requirements report to appropriate person for project approval
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.
Client may include:
external organisations
individuals
internal departments
internal employees.
Sources of information may involve:
business-strategic plans
change-management plans
current systems-design plans
project-management plans.
Project scope may include:
budget
features
hardware
policy and legal constraints
resource
software
time.
Unified modelling language may include:
activity diagram
class diagram
use-case diagram
use-case narrative.
Feasibility may include:
economic and schedule feasibility as well as the principal inputs and outputs
expected improvements and impacts
operational feasibility
physical requirements of each solution
revenue and cost-benefits
risks
technical feasibility.
Solutions may include:
hardware upgrades
new system implementation
new hardware
new software
software upgrades
user training.
Requirements may be in reference to:
application
business
network
organisational policies
people in the organisation
system.
Constraints may include:
budget
hardware
legal
organisational policy
resources
software
time.
Resources may include:
equipment
infrastructure
networks
personnel.
Software requirements document may include:
brochures
help references, such as online help
operational procedures
reports
solution design
solution feasibility
system design
system functionality
system or project specifications
technical manuals
training materials and self-paced tutorials
user guides.
Appropriate person may include:
authorised business representative
client
supervisor.
Project may include:
business improvement process
ebusiness solution involving the total organisation or part of the organisation
projects involving a business undertaking a total organisational change
systems-only change.
Client may include:
external organisations
individuals
internal departments
internal employees.
Sources of information may involve:
business-strategic plans
change-management plans
current systems-design plans
project-management plans.
Project scope may include:
budget
features
hardware
policy and legal constraints
resource
software
time.
Unified modelling language may include:
activity diagram
class diagram
use-case diagram
use-case narrative.
Feasibility may include:
economic and schedule feasibility as well as the principal inputs and outputs
expected improvements and impacts
operational feasibility
physical requirements of each solution
revenue and cost-benefits
risks
technical feasibility.
Solutions may include:
hardware upgrades
new system implementation
new hardware
new software
software upgrades
user training.
Requirements may be in reference to:
application
business
network
organisational policies
people in the organisation
system.
Constraints may include:
budget
hardware
legal
organisational policy
resources
software
time.
Resources may include:
equipment
infrastructure
networks
personnel.
Software requirements document may include:
brochures
help references, such as online help
operational procedures
reports
solution design
solution feasibility
system design
system functionality
system or project specifications
technical manuals
training materials and self-paced tutorials
user guides.
Appropriate person may include:
authorised business representative
client
supervisor.
Project may include:
business improvement process
ebusiness solution involving the total organisation or part of the organisation
projects involving a business undertaking a total organisational change
systems-only change.
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:
research and analyse client requirements in order to present a range of solution options
create a software requirements document applying content format and style according to relevant organisational standards.
Context of and specific resources for assessment
Assessment must ensure access to:
specific requirements, including client and functionality
word-processing software, such as Microsoft Word
modelling software currently used in industry
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 software requirements documentation
verbal or written questioning to assess candidate’s knowledge of modelling tools.
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:
research and analyse client requirements in order to present a range of solution options
create a software requirements document applying content format and style according to relevant organisational standards.
Context of and specific resources for assessment
Assessment must ensure access to:
specific requirements, including client and functionality
word-processing software, such as Microsoft Word
modelling software currently used in industry
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 software requirements documentation
verbal or written questioning to assess candidate’s knowledge of modelling tools.
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 |
|---|---|---|---|
| AUV60 | ICTPRG419 | Analyse software requirements | Unit of competency |
| State Code | National Code | Title | Type |
|---|---|---|---|
| D557 | ICA40111 | Certificate IV in Information Technology | Qualification |
| D561 | ICA40511 | Certificate IV in Programming | Qualification |
| D563 | ICA40711 | Certificate IV in Systems Analysis and Design | Qualification |