Google Links

Follow the links below to find material targeted to the unit's elements, performance criteria, required skills and knowledge

Elements and Performance Criteria

  1. Prioritise requirements
  2. Organise requirements
  3. Specify and model requirements
  4. Define assumptions and constraints
  5. Verify requirements
  6. Validate requirements

Required Skills

Required skills

analytical skills to review organisational and technical business solutions

communication skills to

conduct focus groups and requirements workshops

conduct research and interviews

liaise with stakeholders

analytical skills to prioritise requirements

technical writing skills to develop requirements documents and specifications

technical modelling skills to develop models of systems processes and solutions

Required knowledge

business rules analysis

data flow diagramming

data modelling

functional decomposition

organisation modelling

process modelling

risk management strategies

scenarios and use cases

scope modelling

user stories

Evidence Required

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

define specify and prioritise stakeholder and solution requirements to a standard that would allow construction of a business solution

verify and validate the requirements to ensure necessary quality and support for stakeholder needs

Context of and specific resources for assessment

Assessment must ensure access to

documentation including appropriate policies current business analysis practices tools and legislation

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

evaluation of a simulated or workplace project in a medium to large enterprise

direct observation of the candidate carrying out business analysis work

verbal or written questioning to assess required knowledge and skills

review of reports and plans prepared for the projects

evaluation of a portfolio of the project work undertaken

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 nonEnglish speaking background may need additional support

In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge


Range Statement

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.

Basis for prioritisation may include:

difficulty of implementation

relative value

likelihood of success

risk

regulatory or policy compliance

relationship to other requirements

stakeholder agreement

urgency.

Challenges may include:

non-negotiable demands, e.g. stakeholders wish to rank all requirements as high priority

unrealistic tradeoffs, e.g. difficulty or complexity of implementing certain requirements may be overstated.

Appropriate level is determined by:

particular methodology being used

whatever level of abstraction is appropriate for the audience.

Appropriate models may include:

data flow diagrams

data models

functional decomposition

organisation models

process models

scenarios and use cases

scope models

user stories.

Business constraints may include:

organisational restrictions

budgetary restrictions

limits on the number of resources available

restrictions based on skills of the project team and stakeholders

scope restrictions

time restrictions.

Technical constraints may include:

application software that must be used

architecture decisions that are made that may impact the design of the solution, such as:

development languages

hardware and software platforms

application software that must be used

restrictions, such as resource use

message size and timing

software size

maximum number of and size of files records and data elements

enterprise architecture standards that must be followed.

Characteristics of requirements’ quality may include:

cohesiveness

completeness

consistency

correctness

feasibility

modifiable

testable

unambiguous.