Unit of competency Outline

Date retreived
22/07/2026 8:56 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
ICTPRG419
State Code
AUV60
TGA Status
Replaced
DTWD Status
Replaced
Current Release Number
1.00
Current Release Date
25/03/2015
View on TGA
State Implementation and Classification
Approved Date
16/09/2015
Field of Education
020305 - Systems Analysis And Design
Original Release Date
16/09/2015
Nominal Hours
60
Description
This unit describes the skills and knowledge required to research and analyse client requirements, produce a range of options, and create a software-requirements document.It applies to individuals in a range of work environments who are required to perform an analysis role in formulating software requirements. 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 the requirements, and the scope, of the project 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 the client requirements, project’s scope, related problems, and sources of information
2. Analyse the functional and related non-functional requirements
  • 2.1 Map business processes using modelling tools such as unified modelling language (UML)
  • 2.2 Determine the 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 the software-requirements documentation
  • 5.1 Develop the software-requirements document
  • 5.2 Submit the software-requirements report to the appropriate person for project approval
No information
No information
Replaces
State Code National Code Title Type
D8011 ICAPRG419A Analyse software requirements Unit of competency
Replaced By
State Code National Code Title Type
OBT12 ICTPRG444 Analyse software requirements Unit of competency