Unit of competency Outline

Date retreived
22/07/2026 3:43 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 stakeholder requirements

Analyse stakeholder requirements

Unit of competency
National Code
ICTSAD606
State Code
AUW33
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
40
Description
This unit describes the skills and knowledge required to analyse stated requirements, determine potential solutions, and define possible features available to meet stakeholder needs.This unit applies to individuals who require high-level management, business and technical skills necessary to manage complex analysis efforts within the information and communications technology (ICT) industry, often as part of business critical ICT projects.No licensing, legislative or certification requirements apply to this unit at the time of publication.
Notes
Elements and Performance Criteria
1. Prioritise requirements
  • 1.1 Determine the basis for prioritisation of requirements
  • 1.2 Resolve challenges in facilitating the prioritisation
2. Organise requirements
  • 2.1 Articulate requirements at an appropriate level of abstraction
  • 2.2 Devise appropriate models to describe the solution scope, based on informational needs of stakeholders
  • 2.3 Document dependencies and inter-relationships among requirements
3. Specify and model requirements
  • 3.1 Develop textual requirements
  • 3.2 Generate matrices to convey or support identified requirements
  • 3.3 Create models to document and communicate requirements and improvement opportunities
4. Define assumptions and constraints
  • 4.1 Agree on assumptions to be defined and clarified as requirements are understood
  • 4.2 Document and examine business constraints to identify options no longer available
  • 4.3 Recognise and examine technical constraints that may restrict design or mandate standards to be followed
5. Verify requirements
  • 5.1 Establish characteristics of requirements’ quality
  • 5.2 Undertake verification activities iteratively throughout the requirements analysis process
6. Validate requirements
  • 6.1 Identify and define stakeholder requirement benefit assumptions so that associated risks can be managed
  • 6.2 Generate measurable evaluation criteria to assess success of requirements benefit post implementation
  • 6.3 Assign business value of requirements to assist in identifying candidates for elimination
  • 6.4 Determine requirement dependencies for benefits realisation
  • 6.5 Evaluate alignment with business case and opportunity cost to assist validation and decision making
No information
No information
Replaces
State Code National Code Title Type
D8118 ICASAD606A Analyse stakeholder requirements Unit of competency
Replaced By
State Code National Code Title Type
OBS77 ICTSAD610 Analyse stakeholder requirements Unit of competency
State Code National Code Title Type
AWA6 ICT60315 Advanced Diploma of Information Technology Business Analysis Qualification