Unit of competency Outline

Date retreived
22/07/2026 2:48 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.

Analyse software requirements

Analyse software requirements

Unit of competency
National Code
ICTPRG444
State Code
OBT12
TGA Status
Current
DTWD Status
Approved
Current Release Number
1.00
Current Release Date
21/07/2020
View on TGA
State Implementation and Classification
Approved Date
15/01/2021
Field of Education
020305 - Systems Analysis And Design
Original Release Date
15/01/2021
Nominal Hours
55
Description
This unit describes the skills and knowledge required to research and analyse client requirements, produce a range of options for business process efficiencies and create a software-requirements document.It applies to those who are required to perform an analysis role in formulating software requirements in a range of work environments. They may work as database or computer developers, business analysts, or project managers.No licensing, legislative or certification requirements apply to this unit at the time of publication.
Notes
Elements and Performance Criteria
1. Gather and confirm client requirements
  • 1.1 Confirm requirement and scope of project with required personnel
  • 1.2 Gather information regarding requirements via sources of information and business processes
  • 1.3 Analyse client requirements and problem context and opportunity faced by client
  • 1.4 Document client requirements, project scope, related problems and sources of information according to organisational procedures
  • 1.5 Submit document to required personnel and seek and respond to feedback
2. Analyse functional and related non-functional requirements and feasibility of project
  • 2.1 Map business processes using modelling tool including unified modelling language (UML)
  • 2.2 Determine opportunities in business process efficiencies
  • 2.3 Document functional and non-functional processes according to organisational procedures
  • 2.4 Analyse technical and operational feasibility of project
  • 2.5 Determine budget and schedule feasibility of project
  • 2.6 Examine purpose and intent of project within organisation
3. Develop high-level system solutions
  • 3.1 Develop and document feasible solutions according to client requirements
  • 3.2 Explore and document the feasibility of each solution
  • 3.3 Examine alternatives against project constraints
  • 3.4 Document assumptions, dependencies and required resources
  • 3.5 Produce a project risk analysis according to project requirements
  • 3.6 Document future requirements according to organisational procedures
4. Prepare and publish software-requirements documentation
  • 4.1 Develop software-requirements document according to organisational procedures
  • 4.2 Submit software-requirements report to required personnel and obtain project approval
No information
No information
Replaces
State Code National Code Title Type
AUV60 ICTPRG419 Analyse software requirements Unit of competency